Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / The Invisible Tax Of Good Work
Transcript
- Lucas: There is a dangerous myth in modern corporate culture that if you do good work, the right people will eventually notice. It feels intuitively fair, like gravity pulling a ball downhill. But when I look at promotion data from the last quarter, specifically around September twenty twenty-six, that intuition is consistently wrong for high performers who fail to architect their own narrative. Luna: It’s not just about noticing; it’s about remembering. Humans are terrible at retaining granular details of other people’s daily labor unless those details are packaged into a story they can repeat to their boss. Lucas: Exactly. And the packaging is where most senior individual contributors trip up. They treat their self-evaluation or their one-on-one updates like a grocery list of completed tasks. Completed what? The problem is that completion is low-leverage. A stakeholder map or a meeting minute might show you were present, but it doesn’t prove you shifted the outcome. Luna: I see this all the time with engineers. They’ll say they refactored the codebase, which is great technically, but if they don’t translate that into reduced latency or lower cloud costs, the business side sees nothing. Lucas: Right. Let’s look at a concrete example from a mid-sized fintech firm we’ll call Nexus Financial. There was a senior product manager named Elena Rostova. Elena was brilliant. She led the redesign of the merchant onboarding flow, which cut drop-off rates by twelve percent. That is a massive number. Yet, when her annual review came up, her director gave her a solid four out of ten rating instead of the five she needed for a director-level promotion. Luna: That seems counterintuitive until you realize the director couldn’t articulate why that twelve percent mattered in the broader strategic picture during the budgeting cycle. Lucas: Precisely. Elena had written a report that said, 'I redesigned the onboarding flow, resulting in a twelve percent reduction in drop-offs.' Her director read that and thought, 'Okay, that’s nice operational maintenance.' He didn’t connect it to revenue retention or customer lifetime value because Elena hadn’t built the bridge. She did the work, but she didn’t sell the impact. Luna: So the invisible tax here is that she paid for her own success with her labor, but never collected the dividend in the form of recognition. Lucas: That is a perfect way to put it. The invisible tax is the gap between execution and perception. And in a remote or hybrid environment, that gap widens because there are no water-cooler moments where your boss overhears you solving a hard problem. You have to manufacture the evidence of your competence through structured storytelling. Luna: But isn’t there a risk of sounding arrogant when you start talking about your own impact? People can smell self-promotion if it’s too aggressive. Lucas: That is a valid concern, but arrogance comes from claiming credit for things you didn’t do or inflating results. What we are talking about is accuracy. If you drove a twelve percent improvement, stating that fact is not bragging; it is providing necessary data for your leader to advocate for you. You are actually making their job easier by giving them the ammunition they need to fight for your raise. Luna: I think the confusion often comes from conflating ego with documentation. Documenting impact is objective. Ego is subjective. Lucas: Let’s dig into the framework then. How should Elena have written that section? Because the difference between the two versions is subtle but critical. The first version was passive and task-oriented. The second version needs to be active and outcome-oriented. Luna: Walk us through the revised version. What does that look like on paper? Lucas: Elena changed her narrative to focus on the context, the action, and the delta. Instead of just listing the redesign, she wrote: 'To address the thirty percent churn rate at the onboarding stage, I led a cross-functional initiative to simplify the merchant verification process. By removing three redundant steps, we increased conversion by twelve percent, which directly contributed to an estimated four million dollars in additional annual recurring revenue.' See the shift? Luna: She moved from describing the feature to describing the financial consequence. Now the director has a dollar figure to take to the finance team. Lucas: And more importantly, she highlighted the cross-functional leadership. Promotions to senior roles are rarely about coding or designing alone; they are about influencing people who don’t report to you. By mentioning the collaboration, she proved she could operate at the next level. Luna: This brings up another point. Not everyone works on revenue-generating features. What about backend infrastructure, legal compliance, or HR operations? Their impact is harder to quantify in dollars. Lucas: Good question. For support functions, you swap revenue for risk mitigation or efficiency gains. A compliance officer might frame their work as preventing a potential regulatory fine worth fifty million dollars. An IT lead might frame their infrastructure upgrade as reducing downtime by ninety-nine percent, saving three hundred hours of lost productivity per month. Luna: It’s still translating technical or procedural output into business language. The metric changes, but the logic remains the same. Lucas: Exactly. You have to speak the language of your sponsor. If your sponsor is a CFO, talk about cost avoidance. If they are a CTO, talk about scalability and technical debt reduction. Tailoring your narrative is part of the executive presence game. Luna: Speaking of sponsors, how does this documentation help you find or cultivate a sponsor in the first place? Isn’t sponsorship usually about relationships? Lucas: Relationships are the entry ticket, but evidence is the fuel. A senior executive won’t publicly champion you if they don’t have clear, concise evidence of your impact to share in rooms you aren’t in. When you provide well-structured impact reports, you are essentially doing the heavy lifting for your potential sponsor. Luna: So you’re making it low-friction for them to pick you up. If they want to promote you, they just forward your email to the VP. Lucas: Precisely. It reduces the cognitive load for the person deciding your fate. If they have to reconstruct your achievements from memory, you lose points. If they can copy-paste your achievement into their update to their boss, you gain momentum. Luna: That feels almost transactional in a healthy way. You provide the data, they provide the platform. Lucas: It is a symbiotic relationship. But there is a trap here. Many people wait until performance review season to build this narrative. By then, it’s too late. The story should be built incrementally throughout the year. Luna: So the quarterly check-in isn’t just a status update; it’s a chapter in your ongoing case file for promotion. Lucas: Yes. Every quarter, you should have a living document that tracks these impact loops. Not just for yourself, but to share with your manager. This shifts the dynamic from surprise evaluation to aligned expectation setting. Luna: I love that. It turns the review from a judgment into a confirmation of facts already agreed upon. Lucas: Before we go deeper into the mechanics of that document, I want to pause for a quick honest thing regarding the production of this show. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these episodes without ads interrupting our conversation. It keeps the lights on and allows us to keep digging into these specifics. Luna: Yeah, it really helps sustain the research depth we try to maintain. Thanks to everyone who supports the network directly. Lucas: Back to the strategy. So we have this impact loop: context, action, delta. But how do you handle situations where your work is collaborative? You don’t want to claim sole credit for a team effort, but you need to highlight your specific contribution. Luna: That’s tricky. If you say 'we' too much, you disappear. If you say 'I' too much, you look like a jerk. Where is the balance? Lucas: The balance lies in specificity of role. You acknowledge the team outcome, but you define your unique lever. For example: 'Our team launched the new API integration. I specifically designed the error-handling protocol that prevented a critical outage during launch week.' You let the team win, but you own your distinct piece of the puzzle. Luna: It’s about being the author of your own subplot within the larger team narrative. Lucas: Exactly. And this requires a level of self-awareness that most people skip. We tend to minimize our own contributions because we view our daily struggles as normal. But to an outsider, or to a busy executive, those struggles are opaque. You have to illuminate them. Luna: So the advice is basically: stop assuming your boss knows how hard you worked, and start showing them exactly what the work achieved. Lucas: Not just how hard, but how strategically valuable. Effort is cheap. Results are expensive. Position yourself as a source of results. Luna: One final question on the format. Should this documentation be a formal report, or can it live in Slack or email threads? Lucas: It should live in a centralized place that is easy to retrieve. A shared drive, a personal wiki, or even a curated folder of emails. But it must be synthesized. Don’t just dump raw emails. Create a summary page that links to the evidence. Luna: Curated evidence. That’s the key. Raw data is noise; curated data is insight. Lucas: Insight is what gets you promoted. Insight is what makes you indispensable. Luna: So, if you’re listening and you feel like you’re working twice as hard as your peers but getting half the recognition, start building that impact loop today. Document the context, define your action, and measure the delta. Lucas: And remember, you are not asking for permission to be recognized. You are providing the information necessary for your organization to reward you fairly. It’s a professional service you owe to yourself. Luna: It’s less about climbing a ladder and more about building a bridge that others can walk across to see you clearly. Lucas: A strong bridge leads to higher ground. Next quarter, let’s look at how to negotiate the actual compensation package once you’ve secured the promotion title. Luna: Because the title is only half the battle. The money is the other half. Lucas: And we will need some very specific numbers to make that argument stick. Luna: We certainly do. Until then, keep documenting your deltas. Lucas: Thanks for listening to The Promotion Memo. We’ll see you next week.