Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / The Art of the Invisible Promotion Memo
Transcript
- Lucas: If we've helped you think through a career move or decision this week, remember that small support makes a big difference. A couple of dollars a month is genuinely what keeps these going, so check out buy me a coffee dot com slash fexingo if you want to keep the signals clear. Luna: Thanks for the reminder. It really does help us stay focused on the quality of the research without chasing clicks. Lucas: Let's get back to the core tension in career progression today. Most people treat a promotion like a reward for past behavior. They assume that if they have done good work, the system will naturally recognize it and elevate them. But in reality, systems are lazy. They default to inertia unless someone actively forces a change in the status quo. Luna: Exactly. And most people try to force that change with a conversation, which feels vulnerable and open to rejection. Lucas: Right. The conversation is the trap. The better approach is to draft a document first. I call this the invisible promotion memo. It is not a self-evaluation form provided by HR. It is a standalone business case written by you, addressed to your manager, arguing why promoting you is the lowest-risk, highest-reward decision they can make right now. Luna: So it shifts the framing from I need this job to this role creates value for the company. Lucas: Precisely. When you write a business case, you speak the language of executive leadership. You stop talking about effort, hours worked, or loyalty. You start talking about unit economics, risk reduction, and scalability. Let's look at a concrete example from a senior product manager I know who was stuck at her level for two years. Luna: What did she do differently in that memo compared to her usual review process? Lucas: She stopped listing tasks. Instead, she opened with a single paragraph defining the problem her current role could no longer solve. She wrote: 'The current team structure creates a bottleneck in our deployment pipeline, costing approximately three weeks per quarter in delayed releases.' That is a financial and operational problem, not a personal grievance. Luna: That is a powerful opener because it immediately quantifies the cost of the status quo. Lucas: It is. Then she laid out three specific initiatives she had already led informally that solved parts of that problem. She didn't say I did X, Y, and Z. She said, 'Initiative X reduced latency by twenty percent. Initiative Y improved cross-team alignment, reducing rework by fifteen percent.' She presented data, not anecdotes. Luna: So the document becomes evidence of capability before the title is even changed. Lucas: Exactly. The third section is often the hardest for people to write, which is the transition plan. She explicitly mapped out who would take over her old responsibilities and how she would train them. This removes the fear of loss. Managers are terrified that promoting someone creates a hole in the boat. By filling that hole in the paper first, she made the promotion feel safe. Luna: That addresses the operational anxiety that usually blocks promotions more than performance issues do. Lucas: It does. And the final section was the ask. She didn't ask for a raise. She asked for a title change and a budget increase for one junior hire to support the new scope. She tied the compensation directly to the revenue protection she described in the first paragraph. It was a closed loop. Luna: I love that structure. Problem, Evidence, Solution, Ask. It feels almost like a startup pitch deck but for an internal role. Lucas: That is the best analogy. Startups fail when they talk about passion. They win when they talk about market fit. Your career is a market. Your boss is the investor. If you talk about how hard you worked, you are talking about passion. If you talk about the efficiency gains you created, you are talking about market fit. Luna: But doesn't writing a formal document like that come across as arrogant or presumptuous in some cultures? Lucas: It only looks arrogant if you send it unsolicited without context. The trick is the cover note. You email the memo saying, 'I have been thinking about how to scale our output next quarter. I drafted a brief outline of a potential structural shift that might help us hit our goals. I would appreciate your feedback on whether this direction aligns with your vision.' Luna: So you frame it as seeking guidance rather than demanding a decision. Lucas: You frame it as collaboration. You are inviting your manager into the design process. If they reject it, you still have a document that proves you were thinking strategically. You haven't lost face; you have simply pivoted based on their feedback. But nine times out of ten, they will engage with it because it saves them mental energy. Luna: It takes the burden of figuring out the solution off their plate entirely. Lucas: Exactly. Executives are overloaded. They don't have time to invent the next step for every direct report. If you bring them a fully formed proposal that makes their life easier, you become indispensable. The memo is not just a request for a title; it is a demonstration of executive presence. Luna: And it filters out managers who are unwilling to invest in your growth. If they ignore a well-written business case, you know the ceiling is political, not merit-based. Lucas: That is a crucial insight. The memo acts as a diagnostic tool for your organization. If the response is positive, you proceed. If the response is vague or dismissive, you have data to decide whether to stay or leave. You are no longer guessing; you are operating with information. Luna: So the value isn't just the promotion itself, but the clarity it provides about where you stand. Lucas: Always. Now, let's drill into the language. There is a specific trap people fall into when writing these memos. They use passive voice. They say 'Responsibilities were handled' or 'Mistakes were avoided.' This distances them from the outcome. Luna: Active voice owns the result. 'I reduced latency' versus 'Latency was reduced.' Lucas: Precisely. You must use active verbs. Led, Designed, Negotiated, Mitigated, Accelerated. These are power words that signal agency. Passive language sounds like you were a passenger in your own career. Active language sounds like you were the driver. It matters subconsciously to the reader. Luna: And it forces you to be honest about what you actually did, rather than hiding behind team achievements. Lucas: Yes. Team achievements are fine, but they are diluted. A promotion is granted to an individual. You need to isolate your specific contribution within the team success. 'Our team launched the feature' is weak. 'I architected the backend logic that allowed the team to launch the feature two weeks early' is strong. Luna: It creates a clear line of sight between your action and the business result. Lucas: It does. Another common error is failing to quantify the future. People list past wins but then just ask for the title. The memo must project forward. What will happen in the next twelve months under the new title? You need to outline three key objectives you will tackle. This shows you have a roadmap, not just a desire. Luna: It turns the promotion from a static reward into a dynamic investment opportunity. Lucas: Correct. You are selling the next year, not just reviewing the last one. And finally, keep it short. One page maximum. Two pages if you include charts. If your boss has to read a novel to understand why you deserve more money, you have failed the test of executive communication. Clarity is kindness. Luna: Respecting their time is part of demonstrating the seniority you are asking for. Lucas: Absolutely. So, to recap: define the problem in financial terms, present your past actions as proof of capability, map the transition to remove risk, and propose a forward-looking roadmap. Write it clearly, keep it short, and send it as a collaborative proposal. Luna: It transforms the promotion from a plea into a partnership discussion. Lucas: That is the shift. You stop waiting for permission and start leading the conversation. The question for you this week is not whether you deserve a promotion, but whether you have documented the business case for it yet.