A VP of engineering who works with the author, a coach, got a glowing performance review last year. She met her targets, her manager praised her delivery, and the only criticism was too vague to act on. She was still passed over for the CTO role she had been working toward, and she couldn’t understand why.

The author has coached more than 1,000 technology professionals one-on-one, a growing share of them CIOs, CTOs and VPs of product and engineering. The pattern is common. The review covers the job the leader has, while the promotion decision is about a job they don’t have yet. CIO.com has covered why strong performers miss the CIO chair, but the author sees the problem start earlier, the first time a leader with a great review is passed over and can’t get a straight answer about why.

Reviews and promotions measure different things

When the VP asked her boss why she hadn’t been the obvious choice, he gave her a list of reasons. She agreed with some and rejected others, and none of them told her what to change.

Reviews reward what a leader delivered over the last cycle. Promotion decisions ask whether the people above them can already picture that person one level up.

Ranjith Raghunath, CEO of CX Data Labs and a former leader at Amazon, GSK and Samsung Electronics America, described a hard decision at GSK. He chose not to promote his IT services coordinator to head of IT. The coordinator excelled at running the support team, resolving tickets and training employees. But the head of IT role needed a higher-level, systemic thinker, so the company hired externally, and the hire worked out well. Raghunath said his own mistake was not communicating clearly with the coordinator, who felt let down and believed he was a perfect fit.

A 2026 Enhancv survey of 500 US managers found that 62% named 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. Enhancv co-founder Volen Vulkov said strong people who are passed over usually do more of what got them noticed: more hours, more projects, another certificate. He argued that decision makers are really asking whether the person is already making the calls the next role needs. His advice is to look at the decisions your manager makes that you don’t, then ask to take on a few of them.

The author sees the same thing. Leaders who get promoted are often already doing parts of the next job. Those who are passed over tend to do their current job extremely well and wait to be noticed.

Your work can’t speak for itself

The VP believed she had earned the CTO job. The author pushed back. The executive who had hired and championed her had left, and her new boss had far less history with her. He saw a strong VP, not a C-suite leader, and that perception decided the outcome.

A colleague who transferred onto her team admitted not knowing what the team did and said another executive seemed to do everything. In fact, her team owned the platform the company was built on, and the other team shipped features that depended on it. The author’s point was that if someone on her own team couldn’t describe her work, the executives making promotion decisions certainly couldn’t.

Many technical leaders start in roles where the code speaks for itself, because a feature either shipped or it didn’t. Senior roles don’t work that way. Decision makers see only a fraction of the work and fill in the rest from what they hear.

What I assigned instead of more hours

When passed over, clients often want to deliver more. Vulkov’s data suggests productivity is rarely the missing piece, and the author’s experience agrees. The VP got two assignments instead.

The first was a mini 360-degree review. She asked her boss and several peers how well she brought them along and how they perceived her team. The answers gave her more to work with than her formal review. She learned that people couldn’t always follow how she reached her conclusions, so her decisions looked like skipped steps.

The second was an internal PR campaign. She treated the executives around her as her most important stakeholders. That meant:

  • Sharing more updates on what her team was building and why
  • Giving more positive feedback to colleagues
  • Hosting internal engineering sessions on the platform’s direction
  • Presenting her team’s work at an all-hands meeting
  • Accepting external speaking engagements alongside other industry leaders, so people inside the company saw her name tied to the function

The author gives some version of this homework to most clients who are passed over. The questions and tactics change, but the goal doesn’t. The client stops producing more and makes existing work visible to the people who decide.

Make the case yourself

The VP is still at the company and still on the path to CTO. She no longer assumes her review will make her case, so she makes it herself.

If you’ve received a strong review and watched a promotion go to someone else, the review wasn’t wrong. It measured the job you have. Ask the people who decide promotions what they would need to see from you in the next role, then start doing some of that work now. Tell people what your team does and why it matters, because they are 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 decision makers can already picture in the job.