Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / Why High Performers Get Passed Over For Promotions
Transcript
- Lucas: Let’s talk about the most frustrating pattern I see in career coaching: the highly competent specialist who gets passed over for a promotion, while someone with half their technical depth moves up ahead of them. It happens every quarter, usually right before those critical year-end review cycles lock in. The common assumption is that meritocracy always wins, but in practice, it’s often about perceived scope rather than actual output. Luna: Right, and the person getting passed over usually thinks if they just work harder or fix more bugs, the decision will flip. They don’t realize the bar has moved from execution to influence. Lucas: Exactly. And here is where we can help our listeners, if this conversation gives you even one concrete lever to pull in your own performance review cycle today. If we've helped you think through a career move or decision, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. That's F. E. X. I. N. G. O. Luna: Thanks for keeping the feed clear and useful for everyone tuning in during their commute. Lucas: So let’s drill into a specific case. Imagine a senior software engineer named David. He spends eighteen months building a complex internal tool that saves his team forty hours a week. He documents everything, presents at three conferences, and mentors two junior hires. By all objective metrics, he is operating at a director level. Yet when the promotion packet goes to the executive committee, he gets rejected. Luna: That sounds like a classic case of doing the work but failing to translate it into the language leadership cares about. What was the actual reason given? Lucas: The feedback was vague: 'Not ready for the next level.' But when you dig into the committee notes, the real blocker was that David had not demonstrated cross-functional influence. His tool only helped his immediate department. Leadership saw him as a siloed expert, not an organizational leader. In October twenty twenty-six, companies are aggressively cutting headcount and restructuring, so they promote people who can navigate ambiguity across teams, not just within a single vertical. Luna: It’s almost like David built a better mousetrap but forgot to show the CEO why the warehouse needs more mice. Did he try to expand his scope later? Lucas: He tried, but too late. After the rejection, he spent six months trying to force collaboration with other departments. But by then, the narrative was set. He was labeled as 'difficult' or 'not a team player' because his outreach felt transactional rather than relational. The timing was wrong, and the framing was defensive. Luna: So the lesson isn’t just to do more work, but to strategically position your work earlier in the cycle? How do you define that strategic positioning? Lucas: Strategic positioning means aligning your daily tasks with the organization’s current pain points. If the company is focused on customer retention, your project should directly tie to reducing churn, not just improving internal efficiency. You have to speak the language of the executive who signs the check, not the language of your peers. Luna: That makes sense. It’s about translating your output into their metrics. But how do you convince a quiet specialist to start playing that game without losing their authenticity? Lucas: You don’t ask them to become someone else. You ask them to become more visible versions of themselves. Instead of hiding in the code, they need to write the design doc that others read. Instead of presenting only to their manager, they should volunteer to present to the broader engineering community. Visibility is a skill, just like coding or sales. Luna: I’ve seen this happen in marketing too. A brilliant analyst gets buried in spreadsheets while a less insightful colleague gets promoted because they’re better at storytelling. Is it really that simple? Lucas: It’s not simple, but it is deliberate. The marketer in your example didn’t just tell stories; they told stories that aligned with revenue goals. They made sure the CMO heard about their success before the VP did. It’s about managing upward visibility, not just downward delivery. Luna: Upward visibility. I like that phrase. But what about the risk of being seen as self-promotional? Many high performers fear that speaking up will make them look arrogant. Lucas: That fear is valid, but it’s based on a false dichotomy. There is a difference between bragging and reporting. Bragging is saying, 'Look how great I am.' Reporting is saying, 'Here is the outcome of this initiative, and here is how it helps us hit our quarterly targets.' One is ego-driven; the other is value-driven. Executives reward value, not ego. Luna: So the key is to detach your identity from the praise and attach it to the result. That shifts the focus from you to the business impact. Lucas: Precisely. And this brings us to another critical factor: sponsorship. Having a manager who likes you is not enough. You need a sponsor who is willing to bet their own political capital on your promotion. Sponsors are usually senior leaders who aren’t your direct manager but advocate for you in closed-door meetings. Luna: How does a mid-level employee find a sponsor if they don’t already know the C-suite? Isn’t that gatekept? Lucas: It feels gatekept, but it’s actually about proximity. You get proximity by volunteering for cross-functional projects, attending company-wide town halls, and asking thoughtful questions in open forums. When a senior leader sees you contributing meaningfully to a broader conversation, they remember you. Sponsorship is often a byproduct of visibility, not a separate quest. Luna: So you build the visibility first, and the sponsorship follows naturally. That removes some of the pressure to 'find' a mentor. It becomes about showing up where the decision-makers are. Lucas: Exactly. And this is especially relevant now because many organizations are hybrid or remote. Physical presence used to guarantee visibility. Now, you have to engineer it digitally. This means your written communication, your meeting contributions, and your documented achievements carry more weight than ever. Luna: Which goes back to the documentation piece we touched on in previous episodes. If it’s not written down, did it happen? Especially in a remote environment. Lucas: Absolutely. In a remote setting, your calendar and your commit history don’t speak for themselves. Your weekly summary email, your project post-mortems, and your shared documentation are your primary evidence. If you haven’t documented your impact, you haven’t done the work, regardless of how hard you worked. Luna: That’s a harsh truth. Most people document after the fact, if at all. Making it a habit requires discipline. Do you suggest a specific format for these updates? Lucas: I suggest a simple structure: Situation, Action, Result, and Impact. Keep it concise. Focus on the Result and Impact. The Situation and Action are context; the Result and Impact are the value. Executives skim for value. Give them exactly what they need to justify promoting you in one glance. Luna: Situation, Action, Result, Impact. Easy to remember. And it forces the writer to be specific about outcomes rather than just listing tasks. It turns a to-do list into a business case. Lucas: Right. And this brings us to the final piece: the promotion memo itself. Many people treat it as a resume update. It shouldn’t be. It should be a persuasive argument. It needs to anticipate objections and address them proactively. Why are you ready now? Why this role? Why not someone else? Luna: Addressing why not someone else is tricky. It can sound competitive or negative. How do you frame that without putting down colleagues? Lucas: You don’t put down colleagues. You highlight your unique combination of skills and experiences that fit the new role’s specific needs. It’s not about being better than others; it’s about being the best fit for the problem at hand. You position yourself as the solution to a specific organizational challenge. Luna: So it’s a match-making exercise, not a ranking contest. You’re proving that your profile solves a current business need. That’s a much more constructive way to frame it. Lucas: Yes. And this mindset shift—from competing to solving—is what separates managers from executives. Managers compete for resources; executives solve for value. If you want to move up, you have to start thinking like the role you want, not the role you have. Luna: That’s a powerful reframe. Start acting like the director, and the title might follow. But what if the organization just doesn’t have the budget or the open roles right now? Lucas: Then you create the role. Or you take on the responsibilities informally. You stretch into the gaps. Companies often promote internally because it’s cheaper and safer than hiring externally. If you can demonstrate that you’re already doing the job, you lower the risk for them. You make the promotion a no-brainer decision. Luna: Creating the role. I love that. It puts the agency back in the employee’s hands. Instead of waiting for permission, you demonstrate capability and let the organization catch up. Lucas: Exactly. It’s proactive career management. Waiting for the annual review cycle to dictate your trajectory is a passive strategy. Active professionals shape their path by identifying opportunities and filling them with their talent. Luna: So the takeaway is: document your impact, align with business goals, build visibility, seek sponsorship, and frame your promotion as a business case. It’s a lot of work, but it’s the only way to ensure your efforts are recognized. Lucas: It is a lot of work, but it’s also the only way to ensure your efforts are recognized. The alternative is hoping that someone notices, which is rarely a reliable strategy. In a market this tight, you have to be undeniable. Luna: Undeniable. That’s the goal. Not just good, not just competent, but undeniable. Thanks for breaking down the mechanics of that today. Lucas: My pleasure. Let’s see if you can apply this to your own next review cycle. The question is, what’s the one thing you’ll start documenting differently starting tomorrow?