A VP of engineering I coach received a performance review last year full of positive feedback. She met her targets, her manager had nothing but good things to say about her delivery, and the one piece of critical feedback she received was so vague she felt she couldn’t act on it. She was also passed over for the CTO role she’d been working toward. She told me she’d been the obvious choice, and she couldn’t understand why the decision went the other way. Her review said she was doing great work, so she didn’t know what else to do.
I’ve coached more than 1,000 technology professionals one-on-one, and a growing share of my practice is working with CIOs, CTOs and VPs of product and engineering. The pattern she described comes up often with the leaders I support. The leader performs, and the review confirms the results, yet the promotion goes to someone else. The review covers the job they have. The promotion decision is about a job they don’t have yet.
CIO.com has covered why VPs and IT directors with strong delivery records keep missing the CIO chair. In my coaching practice, the problem starts earlier. It shows up the first time an IT leader with a great review gets passed over for promotion and can’t get a straight answer about why.
Let’s explore why strong reviews and promotions measure different things, and what I assign leaders who get passed over, drawing on real examples from my own coaching practice and IT leaders in the industry.
The review and the promotion measure different things
When this client asked her boss why she wasn’t the obvious choice, she got a list of reasons. She agreed with some and disagreed with others. The feedback she didn’t agree with was the same vague feedback she’d received in her review, and nothing on the list told her what to do differently.
I hear some version of this from IT leaders at every level. The review rewards what they delivered over the last cycle, but the promotion decision asks whether the people above them can already picture this person one level up. This disconnect frustrates the leaders I coach, yet it’s how promotions get decided at most companies, large and small.
Ranjith Raghunath, CEO of CX Data Labs and a former leader at Amazon, GSK and Samsung Electronics America, described one of the hardest conversations he had during his time at GSK, when he decided not to promote his IT services coordinator to head of IT. The coordinator was excellent at running the support team, resolving tickets, training employees and handling the thousands of small tasks that keep laptops and software platforms working. The coordinator wanted an executive role. Raghunath told me he couldn’t replace that skill set or the rapport the coordinator had with his team, so the company hired externally for a higher-level, systemic thinker, who worked out well.
The coordinator was doing his current job well. The head of IT job needed different skills, and nothing in his day-to-day work showed he had them. Raghunath also told me his own mistake was failing to communicate clearly with the candidate, who felt let down and believed he was a perfect fit for the role, even though he wasn’t.
A 2026 Enhancv survey of 500 US managers found that 62% credited performance and results as the biggest factor in reaching leadership, and only 6% named education, yet 65% called their degree and credentials essential or very important in getting their current role. Volen Vulkov, Enhancv’s co-founder, told me that when strong people get passed over, they usually do more of what got them noticed in the first place. “More hours, more projects, another certificate. Our data says that’s rarely what’s missing. Almost nobody credited their credentials for their promotion,” he said. “The people deciding are asking a different question: is this person already making the calls the next role needs? So, look at the decisions your manager makes that you don’t. Then ask to take a few of them on.”
Vulkov’s advice matches what I see with my clients. The IT leaders who get promoted tend to be the ones who are already doing pieces of the next job before anyone hands it to them. The leaders who get passed over tend to be doing their current job extremely well and waiting for someone to notice.
Your work can’t speak for itself
My client, the VP of engineering, was convinced she had done enough to earn the promotion to CTO. I pushed back. The executive who hired her and championed her for years had left the company, and her new boss had far less history with her. He saw her as a strong VP, not as a C-suite leader, and that view, not her results, decided the promotion. In a promotion conversation, perception is reality.
A colleague then transferred onto her team from another part of the company and admitted they didn’t know what the team really did. Another executive at the company, they said, seemed to do everything. She disagreed, and she was right to. Her team owned the platform the rest of the company was built upon, while the other team shipped features dependent on her work. The point I made to her afterward was that this person now reported to her and still couldn’t describe the team’s work. If someone on her own team couldn’t, the executives deciding on promotions definitely couldn’t either.
Many of the IT leaders I coach started in roles where the code spoke for itself. The feature shipped or it didn’t. Senior roles don’t work that way. The people making promotion decisions see a fraction of the work, and they fill in the rest from what they hear about it.
What I assigned instead of more hours
When a client is passed over for a promotion, their instinct is often to deliver more, but Vulkov’s data says productivity is rarely what’s missing, and my coaching experience agrees.
With this client, I assigned two pieces of homework.
The first was a mini 360-degree review. She asked her boss and a few peers how well she was bringing them along and how they perceived her team. Their answers gave her more to work with than her formal performance review had. She learned that people couldn’t always follow how she reached her conclusions, so from the outside, her decisions looked like skipped steps.
The second was an internal PR campaign. I asked her to treat the executives around her as her most important stakeholders. In practice, that meant sharing more updates on what her team was building and why, giving more positive feedback to the people around her, hosting internal engineering sessions on where the platform was headed, presenting her team’s work at an all-hands meeting, and saying yes to external speaking engagements alongside other industry leaders so people inside the company saw her name attached to the function.
I assign some version of this homework to most clients who get passed over. The questions in the mini 360 change with the situation, and so do the moves in the PR campaign. The goal doesn’t change. The client stops producing more and starts making the work they’ve already done visible to the people who make decisions.
My client is still at the company and still on the path to the CTO role. She no longer assumes her review will make the case for her, so she makes it herself.
If you’ve just received a strong review and watched the promotion you wanted go to someone else, the review wasn’t wrong. It measured the job you have. Ask the people who decide promotions what they’d need to see from you in the next role, then start doing some of that work now. Tell the people around you what your team does and why it matters, because they’re filling in that story with or without you. The promotion rarely goes to the leader who did the most work. It goes to the one the decision makers can already picture in the job.
Read More from This Article: Why IT leaders who hit every target still get passed over for promotion
Source: News

