Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How a Quiet Employee Got a Promotion by Redefining Their Role
Transcript
- Lucas: You ever notice how most job descriptions are basically fiction by the time you've been in a role for six months? Luna: Oh, absolutely. Mine said 'manage vendor relationships.' Within a year I was basically running a mini P&L. Lucas: Right. And that gap between what you actually do and what HR wrote is exactly where promotions live — if you know how to formalize it. I want to talk about a specific move today: rewriting your own job description as a promotion strategy. Lucas: Yeah. Before we go deep, I want to mention something. We keep this show completely ad-free. No sponsor reads, no interruptive ads. If that kind of independent career advice is valuable to you, the show stays free because of listeners who choose to support at buy me a coffee dot com slash fexingo. No pressure, just a note. Luna: Totally. And it's nice knowing there's no hidden agenda when we talk about what works. Lucas: Exactly. So let's get into the case. There's a supply chain analyst at a Fortune 500 manufacturer — let's call her Priya. She was hired to track inventory levels. But within two years, she'd built a forecasting model that saved the company close to two million dollars in warehousing costs. Luna: Classic scope creep, but the good kind. So her official title was still 'Supply Chain Analyst I' while she was doing work that was more like a senior data scientist. Lucas: Right. And she went to her manager and said, 'I'd like a promotion to Senior Analyst.' And the manager said, 'Your role description doesn't support it.' Basically, HR had no category for what she was doing. Luna: That's the moment most people give up. She didn't, right? Lucas: No. Instead, she wrote a new job description. She literally sat down and drafted the role she wanted to be promoted into — responsibilities, qualifications, impact metrics. Then she built a business case showing that her current work already matched that description. Luna: That is bold. I love it. So she essentially said, 'The organization has evolved, and my role needs to reflect that.' Lucas: Exactly. And here's the smart part: she didn't just draft it for herself. She framed it as a proposal to create a new role — 'Senior Supply Chain Analyst, Data & Forecasting' — that she argued would benefit the whole team. She even included a line about how this would help attract and retain talent in analytics. Luna: So she made it about the company's needs, not just her own ambition. That's a subtle but huge shift. Lucas: It's the difference between asking for a favor and presenting a solution. Her manager took it to HR, and within three months she had the new title and a 15 percent raise. Luna: Nice. So walk me through the framework. If someone wants to try this, what's the first step? Lucas: Step one is what I call a scope audit. Take your current job description and your actual calendar from the last three months. Highlight everything you do that's not in the job description. Priya realized she was spending 60 percent of her time on data modeling, which wasn't even mentioned. Luna: So you need the receipts. That makes sense. What's step two? Lucas: Step two is a gap analysis. Look at the next role you want — maybe a Senior Analyst or a Manager — and see what skills or deliverables you're missing. For Priya, she was already doing the analysis, but she lacked experience presenting to executives. So she proactively asked to present at the quarterly review. Luna: She filled the gaps before asking for the promotion. That's smart. Lucas: Exactly. Step three is the business case. Write a one-page memo that says: here's the role I'm proposing, here's how it aligns with company goals, and here's what I've already accomplished. Use numbers. Priya had the two million in savings, but she also documented time saved — like fifty hours per month in manual reporting. Luna: That's concrete. I think a lot of people skip the numbers part because they're not in finance. But even rough estimates are better than nothing. Lucas: Agreed. And the final piece is a sponsorship strategy. Priya didn't just hand her manager the memo. She first shared it with a VP she'd worked with on a cross-functional project, got that person's buy-in, and then had the VP mention it to her manager. It wasn't a surprise. Luna: So she built a coalition. That's key. One person can say no, but two people saying yes is harder to ignore. Lucas: Right. And the VP didn't just support — they actually co-signed the memo. That made it much easier for HR to approve a new role because they saw executive demand. Luna: I want to ask about the risk. What if your manager says, 'No, we need you to stay in your current role because it's cheaper'? Lucas: That happens. And if that's the case, you have a choice. But Priya's approach actually makes it harder for them to say no because you've reframed the conversation from 'give me more money' to 'let's optimize the org chart.' If they still say no, you know it's not about your performance — it's about the system. And that's useful information for your next move. Luna: Interesting. So even a 'no' gives you data. I like that. Lucas: Exactly. And one more thing: this strategy works best when you've been in a role for at least eighteen months, and you have clear metrics of impact. If you've only been there six months, it's too soon. Luna: Yeah, you need credibility first. But once you have the receipts, I think this is one of the most underused tactics. Most people wait for their manager to write a new job description for them, which never happens. Lucas: Exactly. So if you're listening and you feel like your job description is outdated, you have more power than you think. Write the job you want, build the case, get a sponsor. It's not guaranteed, but it's a much better bet than hoping someone else notices. Luna: And if you try it, let us know how it goes. We'd love to hear a success story. Lucas: That's the show. We'll be back next time with another promotion playbook.