Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Building a Narrative Arc
Transcript
- Lucas: So there's this product marketing manager named Priya at a Fortune 500 enterprise software company. She's been in role for three years, strong performer by every metric, but she keeps getting passed over for director-level roles internally. Not because she's not capable — because her promotion packet reads like a laundry list. Luna: Right — 'Led Q3 launch, coordinated with sales, updated collateral.' It's accurate but it doesn't tell a story. Lucas: Exactly. So last year she decided to try something different. Instead of sending in bullet points, she mapped her past three projects onto what's essentially a narrative arc — setup, rising action, climax, falling action, resolution. Borrowed from Freytag's pyramid, which is usually for fiction and drama. Luna: Wait — she literally used a literary structure for her promotion packet? That's either genius or a huge risk of coming off as overly crafted. Lucas: That's the exact tension we need to talk about. Because done poorly, it looks like spin. Done well, it shows your leadership team that you think strategically about your own work. Priya didn't fabricate anything — she just reorganized what was already true into a shape that made the progression visible. Luna: Okay, break down the arc for me. What did the setup look like? Lucas: The setup is her first project: a small feature launch with a tight budget. She framed it as the 'status quo challenge' — the team had no process, cross-functional alignment was messy, and she had to build trust from scratch. That's the inciting incident, the thing that forced her to step up. Luna: And the rising action? Lucas: Second project — a mid-tier product refresh. She had more resources but also more stakeholders, competing priorities. The tension came from needing to negotiate scope with engineering while keeping marketing's timeline realistic. She described how she built a coalition, used data to make trade-offs, and delivered under a compressed schedule. Luna: So that's the part where the stakes get higher and the protagonist — her — shows growth. Learning by doing. Lucas: Exactly. Then the climax is the third project: a company-wide flagship launch with a six-month timeline, a cross-functional team of twenty, and executive visibility. She didn't just execute — she designed the entire go to market strategy, presented to the C-suite, and handled a last-minute competitive threat. That's the peak of her arc. Luna: And the falling action and resolution? How do you end a promotion packet? Lucas: Falling action: the post-launch metrics. Revenue exceeded target by 18 percent, customer acquisition cost dropped 12 percent quarter-over-quarter. Resolution: she reflects on what she learned — how to lead without authority, how to read the room with executives, why she's ready for the next level. It's not just 'I did this'; it's 'here's what it means for the business and for my growth.' Luna: I love that the arc gives her a chance to show self-awareness. Most promotion packets I've seen are all 'look at my wins' and zero 'this is what I learned from the hard parts.' Lucas: That's exactly the gap. Priya said her manager told her later that the narrative arc made it easy to champion her in the promotion committee. The committee sees dozens of packets, all bullet points. Hers had a through-line. They could retell her story in a meeting because she'd already done the work of structuring it. Luna: But here's the thing I wrestle with — doesn't this favour people who are good at storytelling over people who are just good at their jobs? I think about engineers or analysts who might not be natural writers but deliver huge impact. Are we saying they need to learn narrative structure too? Lucas: Honestly? Yes. And I say that as someone who finds it a little uncomfortable. The reality is that promotion decisions are made by humans, and humans understand stories better than spreadsheets. Priya's case is a perfect example — she didn't change her work, she changed how she communicated it. That's a skill, not a shortcut. Luna: I buy that. But let's talk about the risk of overselling. Where's the line between a narrative arc and, you know, just making your career sound more dramatic than it was? Lucas: The line is verifiability. Every claim in Priya's arc was backed by a specific metric or a named stakeholder who could corroborate it. The narrative didn't invent conflict; it highlighted real constraints that she navigated. If you're fabricating a villain or a crisis that didn't exist, you're not building an arc — you're lying, and that will backfire. Luna: Right, because the committee might ask your peers or your manager about that 'climactic moment' and if it's not real, you're done. Lucas: Exactly. So the framework only works if you're honest. Priya's projects genuinely had those elements — she just hadn't articulated them as a story before. I think most people's careers have an arc; they just haven't sat down to map it out. Luna: Speaking of sitting down to map it out — we should mention that this kind of work takes time. Priya didn't do it in an hour. She told me she spent about four hours over a weekend, with a whiteboard and a lot of sticky notes. Lucas: And that's exactly the kind of investment that a handful of our listeners tell us they've made after listening to this show. Quick honest thing — a few people chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making episodes like this without ads. We don't have sponsors, so listener support is what keeps us going. Luna: Yeah, it's a small group, but it makes a big difference. If the show has helped you think about your career differently, that's the way to keep it ad-free and independent. But back to Priya — she actually built a simple worksheet to structure her arc. She called it the 'narrative arc worksheet'. Lucas: Did she share it? I'd love to see what it looks like. Luna: She did. It's basically four columns: project name, role and scope, the challenge or tension, and the outcome plus learning. You fill one row for each major project, then you arrange them in order of increasing complexity to see the arc. It's a practical tool, not just theory. Lucas: That's smart because it forces you to be specific. The 'challenge' column especially — most people skip that because they don't want to admit things were hard. But that tension is what makes the story compelling. Without it, you're just listing accomplishments. Luna: Exactly. And the 'learning' column is where you show growth. I think that's what separates a narrative arc from a brag sheet. It's not just what you did; it's how you changed. Lucas: Let's talk about timing. When should someone build an arc like this? Right before promotion season feels reactive. Priya started six months before her company's formal review period. Luna: That makes sense. If you start early, you can test the narrative with your manager in informal conversations. 'Hey, I've been thinking about my trajectory — does this arc resonate with what you've seen?' That way you get feedback and adjust before the packet is due. Lucas: And it also gives you time to fill gaps. If your arc has a weak middle because you haven't taken on a project with enough scope, you know you need to volunteer for something bigger before the review cycle closes. Luna: That's a great point. The arc becomes a diagnostic tool for your own career, not just a communication tool. It tells you where you need to stretch. Lucas: So let's bring it back to Priya. She got the promotion. Director of product marketing. Her VP told her later that the arc made it easy to advocate for her because he could tell the story to the head of HR in under two minutes. That's the power of narrative — it's portable. Luna: I think that's the most important takeaway. Your promotion packet has to work when you're not in the room. Your boss has to be able to retell your story effectively. If you make that easy for them, you've already won half the battle. Lucas: Exactly. So the assignment for listeners — if you're thinking about your next promotion — is to map your own arc this week. Take your last three projects, fill in the four columns, and see if they tell a story of increasing complexity and impact. If they don't, you know what to work on. Luna: And if they do, you're ready. Next episode, we'll talk about how to test that narrative with a trusted colleague before you submit it. Because a story that only makes sense to you isn't ready for prime time. Lucas: Perfect. Priya's arc worked because she validated it with her manager and a mentor before she submitted it. We'll dig into that feedback process next time.