Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How to Craft a Promotion Case That Gets Approved
Transcript
- Lucas: We talk a lot about getting noticed, but let's be honest: noticing is cheap. Approval is expensive. And the bridge between those two states is almost always a written document, not a casual conversation in the hallway. Luna: Right. You can have the best track record in the department, but if you can't articulate it in a format that fits the company's budget cycle, you're just busy, not promotable. Lucas: Exactly. And here is the trap most people fall into: they treat their promotion case like a resume update. They list responsibilities. They say, I managed the team, I hit the targets, I fixed the process. But management doesn't care about what you did. They care about what changed because you did it. Luna: So the difference is output versus outcome? Because anyone can tell you what they produced, but only a few can explain the ripple effect. Lucas: Precisely. Let's look at a concrete example from a mid-level operations manager I advised last quarter. She was up for a director role. Her initial draft said she reduced operational costs by ten percent. That's good. It's solid. But it's also generic. Any competent manager should reduce costs by ten percent. Luna: It sounds impressive until you realize it's table stakes. What did she actually do differently? Lucas: She rewrote it to focus on scalability. She explained that by automating a specific reporting workflow, she didn't just save money this year, she freed up forty hours of senior analyst time per month. That meant her team could take on two new product launches without hiring additional headcount. Suddenly, she wasn't just a cost saver. She was a capacity multiplier. Luna: That shifts the narrative from maintenance to growth. Executives are under pressure to grow revenue or expand capabilities without bloating the payroll. That hits both buttons. Lucas: And that is why the document matters. It forces you to think in terms of leverage. When you write down 'I saved forty hours,' you have to prove it. You have to show the data. You have to connect it to the broader business goals. That proof is what separates a manager who gets promoted from one who gets praised. Luna: But writing it well isn't enough if no one reads it. How do you ensure the right eyes see this case before the decision is made? Lucas: This brings us to the second pillar: sponsorship. Visibility gets you on the radar, but sponsorship gets you in the room. Most people confuse visibility with socializing. They attend every meeting, they post on internal channels, they make sure their name is in the email signature. That's noise. Luna: Noise is easy to tune out. Strategic visibility is harder. What does that actually look like in practice? Lucas: It looks like volunteering for the projects that scare other people. It looks like offering solutions to problems that haven't been solved yet, rather than waiting for instructions. I saw this at a tech firm where a senior engineer was stuck in the same band for three years. He started leading cross-functional workshops on technical debt reduction. He wasn't asked to do it. He identified a bottleneck that was slowing down sales, proposed a fix, and led the implementation. Luna: He created a problem he could solve. That makes him indispensable. It also gives his sponsor a tangible win to point to when defending his promotion. Lucas: Spot on. His sponsor didn't have to guess if he was ready. The evidence was public, documented, and tied to revenue. The key is that the sponsor needs ammo. If you walk into your one-on-one and say, I think I'm ready for more responsibility, you're asking them to take a risk. If you walk in with a portfolio of results, you're giving them cover. Luna: So the promotion packet isn't just a brag sheet. It's a risk mitigation tool for your boss. Lucas: It absolutely is. Leaders are afraid of promoting someone who fails. It reflects poorly on their judgment. Your job is to lower the perceived risk of that promotion. You do that by showing consistency, by showing impact, and by showing that you've already been operating at the next level. Luna: That requires a shift in mindset. Most people wait for permission to operate at the next level. But the packet proves you've already been doing it. Lucas: Yes. And that brings us to the structure of the document itself. Too many people dump everything they've done into a single PDF. It becomes a novel. Nobody has time to read a novel. You need a one-page executive summary, followed by detailed appendices. The summary must answer three questions in plain English: What did I achieve? Why does it matter to the business? What will I do next? Luna: The third question is crucial. It shows forward thinking. It signals that you aren't resting on your laurels. You're already planning your next contribution. Lucas: Exactly. It turns the promotion from a reward for past performance into an investment in future value. That is a much easier sell for a finance committee. They love investments. They hate rewards. Luna: Let's pause here for a moment. I want to check in with our listeners. We produce these episodes independently, without ads, relying entirely on listener support. If this kind of deep-dive career advice helps you navigate your own path, consider supporting us directly at buy me a coffee dot com slash fexingo. It keeps the lights on and allows us to keep bringing you these conversations. Lucas: It really does. And for those who do chip in, thank you. It means the world to us and ensures we can keep digging into these topics without corporate interference. Luna: Back to the document. You mentioned the one-page summary. What are the common pitfalls people make when trying to condense their achievements? Lucas: Jargon is the biggest killer. People try to sound smart by using buzzwords. They talk about synergistic paradigm shifts and agile deliverables. It reads like filler. Write for a smart outsider. If a colleague from a different department can't understand the value in thirty seconds, you've lost them. Luna: Clarity over cleverness. Always. Because if they don't get it, they can't advocate for it. Lucas: Right. Another pitfall is ignoring the negative. Every project has challenges. Acknowledging them adds credibility. For example, instead of saying we launched the product on time, say we launched it on time despite supply chain disruptions by renegotiating vendor contracts. It shows resilience and problem-solving, not just luck. Luna: It humanizes the achievement. It shows you were in the trenches, not just watching from the sidelines. Lucas: Precisely. Now, let's talk about the timeline. When should you start drafting this? Most people wait until their annual review. By then, it's too late. You need to build the packet continuously. Keep a running log of wins, feedback, and metrics. Update it monthly. Then, six weeks before your review cycle, refine it into the final package. Luna: That takes the pressure off. Instead of scrambling to remember what you did in October, you have a curated archive. It also prevents recency bias, where your boss only remembers the last two months. Lucas: Recency bias is real. And it punishes consistent performers who have quiet periods. A continuous log levels the playing field. It shows the full arc of your contribution, not just the highlight reel. Luna: So the packet is part strategy, part history, part future planning. It's a comprehensive argument for your growth. Lucas: And it requires feedback. Don't draft it in a vacuum. Share a rough outline with your manager early. Ask, Is this aligned with what you see as my potential? Their response will tell you if you're on the right track or if you're missing the mark. Luna: That turns the process into a collaboration rather than a confrontation. It gives your manager a chance to guide you before the formal review happens. Lucas: Exactly. It signals that you respect their perspective. You're not demanding a title. You're seeking alignment. That is a hallmark of executive maturity. Luna: What about the visual presentation? Does the design of the document matter, or is content king? Lucas: Content is king, but design is the crown. If it looks messy, it suggests your work is messy. Use clean headings, bullet points, and plenty of white space. Charts and graphs are powerful if they are simple. Avoid cluttered spreadsheets. Summarize the data visually so the trend jumps off the page. Luna: First impressions count. Even in a digital document. You want the reader to feel relaxed, not overwhelmed. Lucas: Absolutely. Think of it as user experience design. You are the product. Make it easy for them to consume you. Luna: One last thing. What if the company doesn't have a clear promotion criteria? How do you adapt the packet then? Lucas: Then you define the criteria yourself. Look at the people who have already been promoted. Analyze their work. Identify the patterns. Was it innovation? Stability? Team building? Mirror those patterns in your packet. Show them that you embody the traits of the next level, even if the company hasn't written them down yet. Luna: You become the standard. That's powerful. It moves you from hoping for a seat at the table to setting the agenda. Lucas: It does. And ultimately, the goal isn't just the title. It's the recognition of your value. The packet is the vehicle for that recognition. Build it well, present it clearly, and back it up with action. Luna: So the next time you feel overlooked, ask yourself: have I given my leader the tools to fight for me? Lucas: If the answer is no, start writing. The rest follows.