The advice to “specialize technically” is good advice for the first five years of a career and increasingly bad advice after that. Multiple decades of workforce research point in the same direction: people who plateau professionally usually have plenty of technical capability and missing soft skills. The pattern holds across engineering, medicine, finance, and creative industries, and it’s not because technical skills don’t matter โ they do โ but because they’re rarely the bottleneck at higher levels.
What the long-run data actually shows
Harvard Business Review and McKinsey have both published longitudinal studies tracking career progression in large companies. The consistent finding is that promotion to senior roles correlates more strongly with collaboration ratings, communication clarity, and judgment under uncertainty than with technical evaluations. Google’s Project Oxygen, which examined what made effective managers at the company, found that technical expertise ranked last among the eight characteristics most strongly associated with managerial effectiveness.
This isn’t a soft endorsement of being likeable. The skills in question are concrete: writing clearly, running productive meetings, giving useful feedback, building cross-functional alignment, managing up, recognizing when a project should be killed. They’re learnable but rarely formally taught, which is why people who acquire them early tend to compound advantage.
Why technical skills hit a ceiling earlier
Technical skills are bounded by the problem set in front of you. A senior engineer can be excellent at one stack and still face diminishing returns from getting more excellent at it. Soft skills, by contrast, scale with the complexity of the people and organizations you work with โ a domain that essentially has no ceiling.
Technical skills also depreciate faster. A specialist in a hot framework five years ago may now be working in a stack that didn’t exist then. Communication and judgment are durable; the ability to lead a difficult conversation or structure ambiguous decisions doesn’t go obsolete. People who treat their technical specialty as the entire bet often find themselves rebuilding from scratch every several years.
Where the conventional wisdom is wrong
The phrase “soft skills” itself is part of the problem. It implies the skills are optional, fuzzy, or feminine-coded โ connotations that have caused generations of high-performing technical workers to under-invest in them. A more accurate framing is “skills that compound across roles” versus “skills that depreciate with the technology.” Calling them soft minimizes their actual difficulty.
The fix is structural. Reading widely outside your domain, joining cross-functional projects, taking writing seriously, seeking feedback on how you come across in meetings โ these are concrete practices, not personality traits. People who think they’re “just not good with people” usually mean they haven’t practiced.
The takeaway
Technical excellence will get you hired and promoted into your first managerial role. After that, the curve flattens fast unless you’ve developed the skills that scale with people and organizations rather than with code or spreadsheets. The earlier you start treating soft skills as serious work, the earlier the compounding starts. Treating them as optional is the most expensive career mistake high performers make.
Leave a Reply