Soft Skills Are Just Skills. Stop Calling Them Soft.
The phrase "soft skills" has always bothered me in the way that useful but imprecise language bothers anyone who works with systems for a living. It implies a hierarchy where the skills required to configure a firewall are hard, meaning real, measurable, and valuable, and the skills required to explain the firewall's purpose to a non-technical executive, get organizational buy-in for the security policy it enforces, and build the cross-departmental trust that makes compliance actually happen are soft, meaning supplementary, secondary, and somehow less rigorous than the technical work. This framing is wrong, and it has quietly limited the career trajectories of technically excellent IT professionals for decades by suggesting that the interpersonal and communication capabilities required to lead at a senior level are personality traits rather than learnable disciplines.
The communication skills required to translate technical risk into business consequence are not soft. They are a specific, learnable craft with better and worse practitioners, measurable outcomes, and a body of knowledge behind them. Explaining to a CFO why a $200,000 security investment is worth making requires an understanding of risk quantification, business impact modeling, the CFO's specific priorities and concerns, and the narrative structure that makes a complex argument land in a fifteen-minute conversation. Getting that explanation wrong has consequences that are as real and as measurable as getting a network configuration wrong. The stakes are different but the skill requirement is not less rigorous. It is differently rigorous, which is not the same thing.
The negotiation skills required to manage vendor relationships, scope projects with stakeholders, and navigate competing organizational priorities are not soft. They are negotiation skills, a discipline with frameworks, research, best practices, and outcomes that are directly tied to the deals you close and the ones you don't. The IT leader who consistently secures favorable contract terms, manages scope creep before it becomes a crisis, and builds vendor relationships that produce preferential treatment when supply is constrained is deploying a specific and valuable capability. The IT leader who treats vendor management as a procurement checkbox is leaving measurable value on the table in ways that show up in the budget. Call that what it is: a skill gap, not a personality gap.
The leadership and people management capabilities required to build a high-functioning IT team are not soft. They are the most technically complex part of any IT leadership role, because humans are considerably more unpredictable than infrastructure, do not have vendor documentation, and cannot be rolled back to a previous version when a configuration change produces an unexpected result. Developing another person's technical capability, managing performance in a way that improves outcomes rather than damaging the relationship, building a team culture where people bring problems to the surface rather than hiding them: these are skills that take years to develop, produce dramatically different outcomes depending on how well they are applied, and have an enormous body of research and practice behind them. The word "soft" does not honor what they actually are.
The reframe that serves IT professionals best is straightforward: there are technical skills and there are human skills, and both are required, both are learnable, and both get better with deliberate practice. The IT professional who invests in developing their human skills with the same seriousness they bring to a certification exam will find that the return on that investment compounds in ways the certification rarely does. The certification opens a door. The human skills determine what you build once you are inside.
