Track · PM Careers & Leadership5 min read
Why Strong IT Reviews Often Do Not Lead to Promotions
A 2026 survey of 500 US managers shows that results earn recognition, but promotions reward visible readiness for the next role and the decisions it requires.

Context
A 2026 Enhancv survey of 500 US managers found that 62% cited performance and results, while 6% cited education.
In the same survey, 65% called their degree and credentials essential or very important for their current role.
Nathan Brooks says he has coached more than 1,000 technology professionals one-on-one.
At GSK, Ranjith Raghunath hired externally for head of IT rather than promote the internal IT services coordinator.
The passed-over VP's plan used two assignments: a mini 360-degree review and an internal PR campaign.
By Nathan Brooks
A 2026 Enhancv survey of 500 US managers found that 62% credited performance and results as the biggest factor in reaching leadership, while only 6% named education.
Yet 65% called their degree and credentials essential or very important for their current role. Delivery earns recognition in the present job, but promotion committees judge whether a candidate can already operate one level up.
Volen Vulkov, Enhancv's co-founder, told me: “More hours, more projects, another certificate. Our data says that’s rarely what is missing. Almost nobody credited their credentials for their promotion.”
I have coached more than 1,000 technology professionals one-on-one; my clients increasingly include CIOs, CTOs and vice presidents of product and engineering. Their recurring problem is a strong review followed by a promotion decision that seems to ignore it.
What does a strong review actually prove?
One VP of engineering met every target and received positive feedback for delivery. Her only criticism was too vague to act on, yet she did not get the CTO role she wanted. She assumed excellent execution had already made her obvious for a broader job.
When she asked her boss why, she received a list of reasons; some persuaded her, while others repeated the vague criticism and offered no different action.
A performance review examines results from the previous cycle. A promotion asks whether leaders can picture the candidate making decisions, managing broader priorities and carrying the next role's accountability. The distinction operates at most companies, large and small, and often stays invisible.
Plainly, a review proves present performance; promotion requires evidence of next-level judgment.
Why can excellent operations still lose?
Ranjith Raghunath, CEO of CX Data Labs and a former leader at Amazon, GSK and Samsung Electronics America, described choosing an external hire for head of IT at GSK.
The internal candidate, an IT services coordinator, ran support well: he resolved tickets, trained employees and handled thousands of small tasks that kept laptops and software platforms working. He wanted an executive role. Raghunath could not replace that skill set or the candidate's rapport with the team. GSK hired a systemic thinker, and the choice worked.
Raghunath also identified his own failure. He did not communicate clearly enough, leaving the coordinator convinced that he was a perfect fit even though the role required different capabilities. Running the current function and leading the next one are separate proofs.
What is missing when work stays invisible?
In my VP's case, the executive who hired and championed her had left. Her new boss, who had far less history with her, saw a strong VP, not a C-suite leader. That perception, rather than her results, carried more weight in the promotion decision.
A transferred colleague could not explain what her team did, and another executive seemed to do everything. The reality was more consequential: her team owned the platform on which the company depended, while another group shipped features built on it.
If a colleague cannot describe the team's work, promotion decision makers cannot infer it from delivery data. Senior leaders receive only part of the evidence and fill the rest with what people tell them.
Many leaders began in roles where code spoke for itself: the feature shipped or did not. Senior roles do not work that way.
Vulkov recommends examining decisions your manager makes that you do not, then asking to take some on. Promoted leaders already perform pieces of the next job; operators who wait for notice often repeat what earned them recognition.
What should a passed-over leader do next?
I assign two forms of homework. The first is a mini 360-degree review: ask a manager and several peers how well you bring them along and how they perceive your team.
In the VP's case, this exercise revealed that colleagues could not always follow how she reached conclusions. From outside, her decisions looked as if they skipped steps. That gap was more actionable than her formal review.
The second assignment is an internal PR campaign. Treat executives as important stakeholders and make three kinds of evidence available:
- Explain what the team is building, why it matters and how the work connects to company priorities.
- Give positive feedback, host internal engineering sessions on platform direction, and present team results at an all-hands meeting.
- Accept selected external speaking engagements alongside industry leaders so internal colleagues connect the leader's name with the function.
I assign some version of this plan to most leaders who miss promotion. The questions and tactics vary, but the goal stays constant: stop producing more work and start making existing work legible to the people who decide.
Her internal PR plan did not guarantee the CTO title. It gave her a way to demonstrate next-role behavior before receiving it. She remained at the company and on the CTO path, and she no longer assumes her review will make the case: she makes it herself.
The right response to a strong review and a missed promotion is neither to accept the review as a verdict nor to work longer for the same evidence.
Ask promotion decision makers what they need to see in the next role, begin doing that work now and explain your team's impact to people who cannot see it from delivery metrics.
For product and engineering organizations, the practical direction is to build next-role evidence into current-role work now, rather than wait for a performance review to make the case.
via cio.com (Source)
More from Nathan Brooks
Show full bio
Senior reporter covering companies, deals and strategy in product management at Roadmap File.
56 articles