The weird pattern nobody mentions
When you look at job descriptions for IT leadership roles, you see the expected lineup: strategic thinking, budget management, vendor relationships, digital transformation experience. All legitimate. All useful. And somehow, they miss what actually separates the leaders who move organizations forward from the ones who just manage the current state.
The gap isn't in what they know. It's in what they do with what they don't know.
Reading the room when the room doesn't know what it needs
One thing that strikes me after three decades in this field is how often the actual problem isn't what people say it is. A service desk manager complains about ticket volume. A CFO worries about cloud costs. A department head fusses about outdated systems. But the real friction? Usually it's somewhere underneath, and it only surfaces if someone bothers to listen carefully enough to notice.
Great IT leaders seem to have this almost quiet ability to ask the question that makes everyone pause. Not the obvious question. Not the one that validates what people already think. The one that makes someone go, "Oh. Yeah, that's actually the real thing we're stuck on."
It's not mind reading. It's more like... noticing patterns in what people aren't saying. Where conversations keep bumping up against the same unspoken frustration. Where the official problem and the real problem have quietly drifted apart.
Tolerating ambiguity without broadcasting the anxiety
Here's something that's gotten more interesting over time: technology moves faster, priorities shift more often, and the future gets hazier. Budget cycles that used to make sense for planning now feel like they're guessing in the dark. AI came in and suddenly nobody was quite sure which decisions would matter next year. It's genuinely more uncertain now.
What I notice is that some leaders broadcast their uncertainty like it's breaking news. They escalate it, debate it, wait for clarity before acting. Other leaders seem to sit comfortably in not knowing what the right answer is, and still move forward with good judgment anyway.
That's not confidence. That's something different. It's the ability to act decisively while acknowledging that you might be wrong, and to structure decisions so that finding out you were wrong doesn't mean the whole thing explodes. It's maybe the most underrated survival skill in modern IT leadership.
The skill of translating without dumbing down
There's a type of IT leader who can talk to a board about risk frameworks and then turn around and help a department head understand why their request is technically impossible without once making that person feel stupid for asking. And they do it without using tech jargon as camouflage.
It sounds simple until you notice how rare it actually is. Most people either talk down (which makes everyone feel small) or talk sideways in technical terminology (which makes them feel excluded). The best ones somehow find the actual concern underneath and address that, in language that fits the person they're talking to.
It's not about being a good communicator in the broad sense. It's specifically about seeing that the job title and technical literacy tell you nothing about how to explain something meaningfully to another person. You have to actually look at them and figure out what frame of reference would make it click.
Knowing when to push back on "urgent"
One pattern that's stayed constant for decades: urgent and important are not the same thing, but they spend a lot of time looking identical in an email subject line.
A certain kind of IT leader seems to develop almost an instinct for which fire is actually a fire and which one is just very loud. Not because they're cynical or dismissive. But because they've sat with enough burning questions long enough to know which ones actually burn.
This shows up as the ability to say no to things that seem critical but aren't, and yes to things that don't feel urgent but shape everything downstream. It's not contrarian for its own sake. It's just pattern matching that's gotten sharper over time.
The thing that actually matters
What keeps coming back to me is that the IT leaders who move the needle seem to share something that doesn't appear on any competency framework: they're genuinely curious about how things actually work on the ground. Not just technically. Organizationally. Politically. Human-wise.
They notice what's real. They sit with what's uncertain. They translate without condescending. They know when urgent is a lie. And they do all of this without announcing it.
It's the kind of thing that's hard to hire for because you can't really test it in an interview. But after enough years in this industry, you start to spot it pretty quickly when you see it. And you notice almost immediately when it's missing.