Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How a Career Portfolio Landed a Promotion
Transcript
- Lucas: So we talk a lot on this show about how to make your case for a promotion—scorecards, executive summaries, user stories. But there's one tool I hadn't come across until a few months ago: the career portfolio. Specifically, how a senior analyst named Maria used one to land a manager role at a mid-sized tech firm. Luna: When you say 'portfolio,' I'm picturing an art student's binder full of prints. How does that translate to corporate? Lucas: Right, it's not a physical binder. It's a deliberate collection—usually a PDF—of your best work, with context, metrics, and stakeholder feedback. Maria's was four pages covering three major initiatives she'd led over two years. She opened with a one-paragraph summary of each project, then a table of hard numbers—revenue impact, time saved, headcount affected—and closed with short quotes from the VP and two directors she'd worked with. Luna: So she's essentially building a mini case for why she's ready. That sounds like a lot of editing. How long did it take her? Lucas: About six hours spread over two weeks. And she told me the biggest surprise was that her manager had never seen her full scope of work before. The portfolio forced her to connect dots that weren't obvious from month to month deliverables. Luna: I can see that. Especially in a mid-sized firm where you wear multiple hats—your day-to-day might look routine, but over two years the cumulative impact is substantial. Lucas: Exactly. Maria's lightbulb moment came when she realized her most impressive project—a cross-functional automation that saved the operations team 400 hours a quarter—was buried in a slide deck nobody had looked at in eighteen months. By pulling it into the portfolio, she made it visible and tangible for the promotion committee. Luna: That's a really concrete benefit. But I'm curious—how did she decide which three projects to feature? Was there a framework? Lucas: She used a simple filter: pick one project that shows technical skill, one that shows leadership, and one that shows business impact. She wanted to demonstrate she was well-rounded, not just a number-cruncher. The automation project checked the leadership box because she'd coordinated with four departments. The other two were a data pipeline that improved reporting accuracy and a client onboarding redesign that increased retention by 8 percent. Luna: That client retention number—8 percent—is great. But she probably had to frame it in context. An 8 percent lift means different things depending on the baseline. Lucas: She did. She included the baseline retention rate, the dollar value of retained contracts, and the timeframe. That kind of specificity is what separates a portfolio from a brag sheet. And here's the thing—if we've helped you think through a career move like Maria's, or if this show has given you a framework you've actually used, it's worth knowing that listener support is what keeps us ad-free and independent. A couple of dollars a month genuinely makes a difference—it covers hosting and lets us keep digging into stories like this. You can find that at buy me a coffee dot com slash fexingo. Luna: Yeah, and honestly, it's not about big pledges—even the price of a coffee helps us keep going. Now, back to Maria: once she had the portfolio built, how did she actually use it? Lucas: She didn't just email it to her manager. She scheduled a thirty-minute career conversation, framed as a check-in ahead of promotion cycles. She opened by saying, 'I wanted to share a document that captures my work over the past two years, so you have it for reference.' Then she walked through it page by page. That forced the manager to engage with the content rather than glance at a PDF. Luna: So it becomes a collaborative review, not a submission. That's a smart power dynamic. Lucas: Exactly. And the manager actually said, 'I didn't realize you led the automation project. I thought that was on your peer.' That's the kind of visibility gap a portfolio closes. Maria got the promotion three weeks later. Luna: Let's talk about the downside, though. A portfolio can also expose gaps if you're not strategic. What if your projects aren't that impressive? Lucas: That's a fair point. But I'd argue that even a so-so collection of projects—if framed honestly—can show self-awareness and growth. Maria admitted she nearly included a project that had good metrics but was actually a standard part of her role. She realized that would dilute the portfolio. So she left it out. The portfolio should highlight stretch work, not BAU. Luna: So the curation itself is a skill. You're essentially proving you can separate signal from noise. Lucas: Yes. And that's a skill that matters at the manager level. The promotion committee sees that as executive presence—someone who can distill complex work into a compelling story. Maria's portfolio wasn't just a record; it was evidence she could think strategically. Luna: One thing I'm wondering: could this backfire if the culture is very egalitarian and individual showcases seem like self-promotion? Lucas: That's a real risk. Maria works at a company that values humility, so she was cautious. She framed it as a 'reference document' rather than a 'look what I did' piece. She also included credit to her teammates in each project summary—by name. That signaled collaboration, not ego. In a culture where self-promotion is frowned upon, the portfolio can be positioned as a tool for your manager to advocate for you, not for you to brag. Luna: I like that nuance. It's not about shouting from the rooftops—it's about giving your boss the ammunition they need to make your case when you're not in the room. Lucas: Exactly. And that's the real takeaway from Maria's story. The promotion didn't happen because she shouted louder. It happened because she made it easy for others to see her value—and that's a lesson that applies whether you're an analyst or a director. Luna: So for someone listening who's thinking about their next cycle, what's the single most actionable piece? If they have six hours over two weeks, where should they start? Lucas: Start with a list of every project you've touched in the last 12 to 18 months. Rank them by impact, not effort. Then pick three that span different dimensions—technical, leadership, business. For each, write a one-sentence summary, then list the quantifiable outcome. Don't worry about formatting yet. Once you have the raw material, you can decide if a portfolio is even appropriate for your culture. But the act of inventorying your own work is valuable in itself—it forces you to see your career with fresh eyes. Luna: I'd add: ask a trusted colleague or mentor to review your draft before you show it to your manager. They'll catch blind spots—like Maria almost leaving out the automation project. Lucas: Great point. And if you're still uncertain, you can always start with a one-page version. The portfolio doesn't have to be epic to be effective. Sometimes a single, well-documented project can shift the conversation.