Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Building a Career Case Study
Transcript
- Lucas: So there's this idea I keep coming back to: the career case study. Not a brag sheet, not a list of accomplishments — a structured narrative that opens with a problem, walks through what you did, and closes with a specific, measured result. Luna: Like a mini business school case, but about yourself. Lucas: Exactly. And I think it's one of the most underused tools in the promotion toolkit. Most people walk into a performance review or a job interview and they say things like 'I led the quarterly campaign' or 'I managed the social team.' That's a duty, not a story. Luna: Right. And the thing is, the person across the table — your boss, the hiring manager — they're not thinking in terms of duties. They're thinking in terms of problems solved. Lucas: So the career case study forces you to frame your work that way. Let me give you a concrete example. I talked to a marketing manager at a mid-size B2B SaaS company — let's call her Sarah. She was up for a VP of Marketing role, but she was competing against people who'd been at the VP level before. She had to prove she could operate at that altitude. Luna: So what did she do? Lucas: She built a case study around one specific project: relaunching their pricing page and the product tier structure. Not a sexy project, but high-stakes. The old pricing was confusing — three tiers with overlapping features — and conversion on the pricing page was below industry benchmark. She framed the problem as: 'The pricing page was costing us an estimated $2 million a year in lost revenue because leads couldn't figure out which tier to buy.' Luna: That's a strong opening. Numbers, stakes, clarity. Lucas: Then she walked through what she did. She ran a pricing study with fifty existing customers, A/B tested four different tier structures, and worked with product to rename the tiers based on customer language. The actual work took about six weeks. The result: a 22 percent increase in conversion rate on the pricing page, which translated to roughly $1.8 million in incremental annual revenue. Luna: And she told that as a story — not as an item on a resume. Lucas: She presented it in a slide deck for her VP interview. One slide per chapter: Problem, Approach, Execution, Result. Each slide had a single data point and a line of narrative. She told me that the CEO, who was in the room, leaned forward when she hit the revenue number. Luna: I bet he did. That's the kind of thing that changes a conversation. Lucas: So that's the framework. But there's a subtlety here: you have to pick the right project. Not everything you've worked on deserves a case study. The best ones have three attributes: measurable impact, clear ownership, and some kind of tension — a moment where it could have gone wrong. Luna: Tension is interesting. Most people sand down the rough edges in their stories. They present everything as this smooth, inevitable success. Lucas: And that makes it less believable. Sarah's story had a moment where the first A/B test showed a dip in conversion. She had to decide whether to kill the project or iterate. She iterated — changed the pricing display, tested again, got the lift. That's the kind of detail that signals judgment, not just execution. Luna: It also shows resilience. And that's a leadership trait. Lucas: Exactly. So the case study isn't just about the numbers — it's about how you think under uncertainty. And that's what executives are really evaluating when they consider someone for a promotion. Luna: But I want to push back a little. The Sarah example is great because she had a clean, quantifiable outcome. What about roles where impact is harder to measure? Like someone in HR, or legal, or internal communications? Lucas: Great question. I think there's always a way to quantify, but sometimes the metric is softer. For an HR business partner, maybe it's employee retention in the business unit they support, or time to fill for open roles. For a legal team, maybe it's the number of contracts reviewed per quarter or the reduction in legal risk exposure. The key is to find a proxy that ties to business value. Luna: But you have to be careful not to overclaim. If retention improved because the whole company got a big bonus, not because of your initiatives — that can backfire. Lucas: Absolutely. The best case studies acknowledge context. Sarah didn't say 'I alone generated $1.8 million.' She said 'the project contributed to a 22 percent lift in conversion.' You can be precise without being self-aggrandizing. Luna: And that actually builds trust. If you're too slick, people start to wonder what you're hiding. Lucas: Alright, I think we've laid out the case. Now, before we go deeper into how to build one of these from scratch, I want to mention something. You know, episodes like this — they take time to research and write. And one thing we're proud of is that we don't run ads on this show. Not because we don't get offers — we do — but because we think the content is better without interruptions. Luna: Yeah, and that's a choice we've made from the start. If you've gotten value from episodes like this — maybe you used one of these frameworks in a review or interview — and you want to support that approach, there's a simple way. Lucas: It's buy me a coffee dot com slash fexingo. No paywall, no subscription. Just a way for listeners who find this useful to chip in. It helps us keep doing what we're doing. Luna: And we appreciate it. Anyway, back to the mechanics. Lucas, you mentioned a template — what does a good career case study template look like? Lucas: It's four sections. First, the Problem: one sentence that defines the business challenge, ideally with a cost or opportunity attached. Second, the Approach: two to three sentences on what you did, including any key decisions or trade-offs. Third, the Result: one sentence with a specific metric — percentage, dollar amount, time saved. Fourth, the Takeaway: one sentence on what you learned or how you'd apply that thinking going forward. Luna: So it's compact. That's important — you don't want to ramble. Lucas: Right. If you can't tell your case study in under ninety seconds, you haven't distilled it enough. And you should have three of these ready — one for each major project in the last couple of years. Luna: Three feels right. More than that and you're probably including fluff. Lucas: Exactly. And you can adapt them for different contexts. If you're in a performance review, you might expand the Approach section. If you're in a job interview, you lead with the Result. If you're writing a cover letter, you lead with the Problem. Luna: One thing I'd add: the case study should be written down, not just in your head. I've seen people try to tell their story on the fly, and it comes out messy. Having a written version — even if it's just bullet points — forces you to be precise. Lucas: That's a good point. And I'd go a step further: share it with a trusted colleague or mentor before you use it. Ask them: 'Does this sound like me? Is the impact clear? Am I missing context?' A second pair of eyes catches the blind spots. Luna: Like the time you told me about your own case study and I pointed out you were taking credit for something the team did. Lucas: Yeah, that was humbling. But it made the story better. I changed 'I launched the program' to 'I led the cross-functional team that launched the program.' It's a small shift, but it's more honest and it shows leadership. Luna: And it actually makes you look better — because you're showing you can mobilize people, not just do tasks. Lucas: Exactly. So to wrap this part: the career case study is a tool for framing your work as business value. It's not about inflating your role — it's about making your contribution visible and understandable in the language that executives speak. Luna: And it's something you can start building today, even if you don't have a review coming up. Pick one project from the last six months and draft the four sections. It'll pay off. Lucas: Next episode, I want to talk about how to collect the raw material for these case studies — because you can't build one if you haven't been tracking your work. Luna: That's the impact log we mentioned a few episodes back. Looking forward to it.