Nobody Told Me IT Leadership Was 40% Therapist
There is a moment that happens to every IT professional who steps into a leadership role, usually somewhere around week three, when you realize that the job description was missing an entire section. It was not the section about managing vendors, though that is its own graduate-level course in patience. It was not the section about budget justification, though explaining why the organization needs to spend $80,000 on something nobody will ever see is a spiritual experience. It was the section that should have read: "Will spend significant portion of working hours managing the emotional relationship between humans and technology." Nobody warned me. I am warning you now.
The calls, the tickets, the walked-in crises, almost none of them are actually about the technology once you get past the surface. The user who comes to IT furious about a system outage is rarely furious about the outage itself. They are furious because they had a deadline, and the outage made them feel out of control, and you are the nearest available representative of the system that let them down. The executive who escalates a two-hour-old ticket to your director isn't impatient about the technical resolution. They are communicating that they feel invisible, and the escalation is the loudest tool they have available. Understanding what people are actually expressing underneath what they are technically reporting is the single most underrated skill in IT leadership, and it is nowhere on the CompTIA exam.
The therapist comparison sounds like a joke until you catalog what IT leaders actually do in a given week. We mediate between departments who blame each other for process failures that live in the technology gap between their systems. We counsel users through the grief cycle of a system migration, because yes, people genuinely grieve when you take away the software they have used for eight years, even if the new software is objectively better. We de-escalate situations that started as technical problems and became interpersonal ones by the time they reached our inbox. We deliver bad news about timelines, budgets, and capabilities to stakeholders who did not want to hear it, and then we manage the reaction. None of that is in the network architecture textbook.
The good news is that the skills transfer in both directions. IT professionals who develop genuine emotional intelligence become dramatically more effective at the technical work too, because technology problems in organizations are almost never purely technical. The system nobody uses isn't a technology failure. It's an adoption failure, which is a people problem wearing a technology costume. The security policy nobody follows isn't a policy failure. It's a communication failure. The implementation that went sideways didn't fail because of the software. It failed because someone didn't manage the change and the humans who had to live inside it. Every single one of those outcomes is addressable with the same skills your therapist uses, minus the couch and the hourly rate.
If you are building an IT team and you are only hiring for technical certifications, you are leaving the most important capability off the job description. The person who can troubleshoot a network AND de-escalate a panicked executive AND translate business frustration into a workable technical requirement is not a unicorn. They are what the role actually requires. The technical skills set the floor. Everything above it is people skills all the way up.
