Why Soft Skills Outlast Technical Skills on Product Teams - Mike Cohn

Why Soft Skills Outlast Technical Skills on Product Teams - Mike Cohn

Anyone who has worked in product development for more than a few years has seen the same pattern repeat itself.
The technical skills that once felt essential gradually—or sometimes suddenly—become obsolete. Tools change. Frameworks fall out of favor. Architectures that once seemed modern start to look dated.
This isn’t new, but it is accelerating.
The half-life of technical skills keeps shrinking, especially in technology. In the 1980s, it took ten years for half of what you knew to become outdated. Today, it is four years, and will soon fall below two years according to a Stanford professor.
This raises an important question for leaders:
Where does investment in people have the greatest long-term impact?
Technical skills are necessary, of course. But they are rarely durable.
Soft skills behave very differently.
When someone learns how to collaborate well, make good decisions, facilitate discussions, or lead others, those skills don’t decay at the same rate. Instead, they tend to compound. They become part of how that person works.
Learning how to learn is a good example. Once someone develops that capability, it stays with them. The same is true for decision-making, leadership, and collaboration. These are skills that can continue to improve over time—but they don’t become irrelevant.

I once saw just how important this was during a demo to a group of nurses.
A programmer demonstrated new functionality and showed text on the screen that suggested giving Saltine crackers to a newborn—clearly clinically inappropriate.
He tried to explain that it was just placeholder text. The real point, he said, was the workflow, not the words.
But to the nurses, the words mattered a great deal.
Their professional identity is grounded in “do no harm.” What they saw on the screen violated that principle. They were ready to escalate the issue and cancel the project.
What saved the project wasn’t a technical fix.
It was the project manager’s soft skills.
He calmed the situation, acknowledged the nurses’ concerns, explained what had happened, and persuaded them to come back a week later for a revised demo.
The failure wasn’t technical—it was a failure of empathy.

Product development is full of uncertainty. We work with evolving requirements, incomplete information, and users whose trust we must earn and keep.
Soft skills reduce risk in these environments.
Empathy helps teams understand users. Clear communication builds trust. Collaboration prevents small misunderstandings from becoming major setbacks.
And when these skills improve, the benefit isn’t limited to one person.
If someone learns a new technical skill, that benefit often stays with them. But when someone learns to collaborate better, the entire team benefits. Everyone gets better.

This is one reason leaders often underestimate the return on investing in soft skills.
The payoff isn’t always immediate or easy to measure. It tends to show up most clearly under pressure—when teams need to have hard conversations, discuss options honestly, and make good decisions quickly.
That’s also when the absence of soft skills is most costly.
Some leaders think these skills can wait until things slow down. In reality, pressure is when they matter most.
Teams with strong soft skills can disagree productively, make tradeoffs together, and move forward with confidence—because trust was built earlier.
Everyone on a product development team benefits from strong soft skills, but some roles depend on them especially heavily.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/