Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How To Write A Promotion Memo That Wins
Transcript
- Lucas: The most common mistake I see in promotion cases isn't a lack of competence. It is a failure of framing. People submit a list of tasks they completed last year instead of a argument for why they are ready for the next role. Luna: Right. They send a resume update when the boss needs a business case. It is a fundamental mismatch in format. Lucas: Exactly. When you ask for a promotion, you are asking someone to take a risk on you. Your job is not to remind them you worked hard. Your job is to prove that the risk is low because you have already solved the problems associated with the higher level. Luna: So it is less about looking back at what you did and more about demonstrating forward momentum. Lucas: Precisely. Let us look at a concrete example. Imagine an individual contributor who has been a senior engineer for three years. They want to move into a staff engineer role or a tech lead position. The standard approach is to highlight every bug fixed and every feature shipped. Luna: Which sounds impressive but does not actually explain why they should be leading others. Lucas: Correct. A staff engineer role requires cross-team coordination, architectural decision-making, and mentoring juniors. If your memo only lists coding tickets, you are proving you are a great coder, not a great leader. The gap between your evidence and the requirement is where you get rejected. Luna: That is such a clear way to put it. You are providing proof for the wrong job. Lucas: It happens all the time. So we need a different structure. I call it the scope impact readiness framework. First, you define the scope of the new role. Second, you map your past actions to that scope. Third, you demonstrate readiness through specific examples of ambiguous problem solving. Luna: Does the first step usually involve copying the official job description? Lucas: Partially, but you must go further. You need to interpret the job description into behaviors. A job description says 'drives technical strategy.' That is vague. In your memo, you translate that to 'identified three critical bottlenecks in our deployment pipeline and designed a solution that reduced latency by twenty percent across two teams.' Luna: See, that second part is where people struggle. They know they did strategic work, but they do not know how to write it down without sounding arrogant. Lucas: Arrogance comes from using 'I' as the sole agent of success. Competence comes from showing how your actions moved the needle for the organization. Notice I said 'reduced latency across two teams.' That implies collaboration and impact beyond your immediate ticket. Luna: It shifts the focus from personal effort to organizational value. Lucas: Exactly. Now let us talk about the third pillar: Readiness. This is where most candidates fail. They show they can do the current job well. But promotion is about doing the next job before you have the title. Luna: So you have to show you have already started operating at that level informally. Lucas: Yes. Did you mentor a junior engineer? Did you lead a post-mortem for a failed project? Did you negotiate a vendor contract? These are leadership activities. If you have done them, you must explicitly state them. Do not assume your manager noticed. They did not. Luna: Managers are busy. They remember the big wins, but they forget the quiet leadership moments. Lucas: And those quiet moments are often the deciding factor. When two candidates are technically equal, the one who demonstrates soft skills and political awareness gets the promotion. Your memo must surface that awareness. Luna: This feels like it requires a lot of upfront work. Writing a whole business case document. Lucas: It takes time, but it saves months of rejection. Think about the cost of staying in your current role for another six months while waiting for a generic review cycle. The opportunity cost is huge. Luna: Definitely. And if you do it right, you might trigger a conversation sooner. Lucas: You might. Sometimes the act of writing the memo forces the manager to realize you are underutilized. It creates a moment of clarity that a standard annual review never provides. Luna: Before we dive deeper into the formatting details, I want to pause here for a moment. Lucas: Sure. Luna: If we've helped you think through a career move or decision, we would appreciate your support. Keeping these episodes ad-free allows us to keep digging into these specific, practical topics without compromise. If you want to help us continue producing this content, you can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Lucas: Thank you. It really does make a difference to the quality of the research we can do. Now, back to the structure. Luna: Let us talk about the actual layout. How long should this document be? Lucas: One page. Maximum two pages if you include data appendices. Executives skim. If they have to read five pages of prose, they will not read any of it. Use headers, bullet points, and bold text for key metrics. Luna: What about the opening statement? Should it be emotional or factual? Lucas: Factual and direct. Start with: 'I am requesting a promotion to based on my demonstrated impact over the last twelve months and my readiness to assume additional responsibilities.' No fluff. No apologies. Luna: Just straight to the point. What about addressing gaps? Like if there is a skill they want that you do not have yet. Lucas: Address it proactively. Say: 'While I am still developing my public speaking skills, I have taken steps to improve by leading weekly team demos.' It shows self-awareness and a growth mindset. Ignoring gaps makes you look blind to your own weaknesses. Luna: That is smart. It turns a weakness into a demonstration of development. Lucas: Exactly. Now, let us discuss the 'Invisible Labor' trap. Many people do work that is essential but not visible. Covering for absent colleagues, cleaning up messy code, onboarding new hires. Luna: The glue work. The stuff that keeps the ship running but does not get a trophy. Lucas: Right. You must quantify that. 'Onboarded three new engineers, reducing their ramp-up time by forty percent.' That is a measurable efficiency gain. It is not just helping; it is improving the system. Luna: It reframes service as optimization. Lucas: Precisely. Service is good. Optimization is promotion-worthy. Make sure your language reflects that distinction. Luna: What about feedback from peers? Should you include testimonials? Lucas: Briefly. One or two quotes from stakeholders who were impacted by your work. 'Jane Doe, Product Manager, noted that your API redesign improved our sprint velocity.' Attribution adds credibility. It shows external validation. Luna: It proves you are not just talking to yourself. Lucas: Yes. Self-promotion feels awkward to many people. External validation makes it objective. It is no longer 'I think I did well.' It is 'Others experienced my impact.' Luna: That is a powerful psychological shift for the reader. Lucas: Now, timing is everything. Do not send this during a crisis. Send it after a major win. When your manager is in a positive mood and remembering your successes, that is the moment to insert the request. Luna: Ride the wave of success rather than fighting against doubt. Lucas: Exactly. Also, schedule a dedicated meeting. Do not email it and expect a response. Say: 'I have prepared a summary of my contributions and my path to the next level. Can we schedule thirty minutes to review it?' This signals seriousness. Luna: It commands respect. It treats your career as a serious business matter. Lucas: It does. And be prepared for pushback. They might say 'not yet' or 'we do not have budget.' Have a counter-response ready. Luna: What is a good counter-response? Lucas: Ask for the gap analysis. 'I understand the timing may be difficult. Can we outline the specific milestones I need to hit in the next quarter to make this happen?' This keeps the door open and gives you a roadmap. Luna: It turns a rejection into a plan. Lucas: It does. And if they cannot give you a plan, you have valuable information about whether this company is the right place for your growth. Luna: That is a crucial insight. The memo is not just for getting the promotion. It is for evaluating the environment. Lucas: Spot on. It is a diagnostic tool. If your manager ignores it, deflects it, or dismisses your achievements, you know where you stand. Luna: So the worst outcome is actually very useful data. Lucas: Absolutely. Data is better than ambiguity. Ambiguity keeps you stuck. Clarity, even bad clarity, lets you make a move. Luna: I love that. Clarity over comfort. Lucas: Here is a final tip. Review your memo with a peer who is already at the level you want. Ask them: 'Does this sound like someone at that level?' Their feedback will catch tone issues or missing context. Luna: A dress rehearsal before the main event. Lucas: Exactly. And check for jargon. Ensure that non-technical stakeholders can understand the value you created. Broaden your audience within the document. Luna: Make it accessible. That is part of executive presence too. Lucas: It is. Executive presence is largely about translation. Translating complex work into simple value. Your memo is the ultimate test of that skill. Luna: So if you can write a clear promotion memo, you are already thinking like a leader. Lucas: You are. And you might just convince them to agree with you. Luna: A worthy goal for anyone feeling stuck. Lucas: Indeed. The question is whether you will wait for permission or present the case.