Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How a Career Contract Landed a Director Promotion
Transcript
- Lucas: So I was digging through my notes from a leadership workshop I ran last quarter, and there was one story that kept coming back to me. An engineering manager at a mid-sized SaaS company — I'll call her Priya — who had been passed over for promotion twice. Not because her work was bad, but because every conversation with her boss ended with the same vague promise: 'you're on the right track, let's revisit next cycle.' Luna: That is the most frustrating loop in corporate America. Vague feedback, no timeline, and you're just supposed to keep grinding and hope. Lucas: Exactly. So Priya did something that surprised me. She didn't just ask for feedback again. She wrote a one-page document she called a career contract. It wasn't a formal legal thing — it was a clear, written agreement between her and her boss about what she would deliver, what she needed, and when the promotion would actually happen. Luna: A career contract. That's a bold move. How did her boss react to being handed a document? Lucas: That's the thing — she didn't hand it over cold. She spent two weeks drafting it, then asked her boss for a dedicated thirty-minute meeting to discuss her growth. She framed it as a way to make their conversations more productive. And when she walked in, she had the document printed, but she didn't lead with it. She started by summarizing her three biggest wins from the past year, then said, 'I want to align on what needs to happen for me to be promoted in the next review cycle.' Luna: So she's setting the agenda, and the document is the tool. What was actually in that contract? Lucas: Three sections. First, outcomes — three specific, measurable deliverables she would complete, like 'reduce customer onboarding time by twenty percent' and 'launch the new analytics dashboard with a four-star internal satisfaction rating.' Second, resources and support — what she needed from her boss, like direct access to the VP of product, a budget for a part-time data analyst, and bi-weekly check-ins. Third, the trigger — a clear statement that if she delivered those outcomes on time and met the performance bar, she would be promoted to director in the next fiscal year. Luna: That last part is the guts of it. Most people ask for a promotion without defining what success looks like to their boss. She basically turned it into a deal. Lucas: Right. And the reaction from her boss was interesting. At first, a little defensive — 'I don't think we should put dates on these things.' But Priya had done her homework. She pointed to the company's published promotion criteria and showed how her deliverables mapped directly to the director level requirements. She didn't ask for a favor. She asked for clarity and a commitment. Luna: So did the boss sign it? Did it actually work? Lucas: He did, eventually. They revised a couple of the outcomes together — he wanted one of the deliverables to be tied to a cross-functional project that was already in flight. But by the end of the meeting, they had a signed document. And here's where the magic happened: that contract changed the entire dynamic of the next six months. Every one-on-one started with 'how are you tracking against the contract?' instead of 'so, what's new?' Luna: It's like you're turning the promotion conversation from a subjective judgment into a project with milestones. But I wonder, does this work outside tech? In, say, a more traditional corporate environment where promotions are more seniority-based? Lucas: It's harder, but not impossible. The key is to frame it as alignment, not as a demand. In a traditional environment, you might call it a 'development agreement' or a 'growth roadmap.' The structure is the same: outcomes, support, and a timeline. What changes is the language. You're less likely to get a signed commitment in a law firm, but you can still get a verbal agreement with clear milestones that you document in a follow-up email. Luna: That's a nice bridge. And speaking of documentation, I've noticed that a lot of listeners have been reaching out saying the show has helped them prepare for these kinds of conversations. It's one of the reasons we've been able to keep putting out episodes every single day. Lucas: Yeah, it's genuinely humbling. A small group of listeners already chips in monthly through buy me a coffee dot com slash fexingo, and that's what covers the editing, the hosting, the research — everything. No ads, no corporate sponsor. Just people who find the show useful and want to keep it going. Luna: And if you're one of those people, thank you. It really does make a difference. If you've ever thought about supporting the show but haven't yet, that link is the simplest way to do it. No pressure, but it's appreciated. Lucas: So back to Priya — what happened in the actual review? She hit her numbers, but the VP tried to kick the can down the road, saying the budget wasn't there for a new director role. But because she had that signed contract, she could politely point out that the agreement was made six months ago and the company's own promotion guidelines said she met the bar. It didn't make her popular, but it made her effective. Luna: She used the contract as leverage, but in a calm, professional way. Did she get the promotion? Lucas: She did. Three weeks later, the title change went through. The VP later admitted in private that he had been holding out because he didn't want to lose her to another team — but the contract made it clear she wasn't going to stay without the promotion. It forced the decision. Luna: That's a powerful story. But what about the risks? What if your boss won't engage with a contract at all? Or what if you deliver everything and they still say no? Lucas: The first risk is easier to handle. If your boss refuses to define what promotion looks like, that's a signal — they either can't articulate it, which is a capability issue, or they don't want to commit, which is a will issue. Either way, you've learned something important about your situation. The second risk is harder. If you deliver and they still say no, you have to decide: do you escalate, or do you start looking externally? The contract gives you a clear record of what was agreed, which is useful in both cases. Luna: So it's not a guarantee, but it's a way to force clarity. And in a world where promotions are often ambiguous, clarity is power. Lucas: Exactly. And one more thing I loved about Priya's approach: she didn't write the contract in isolation. She asked a mentor from a different department to review it, which caught a couple of blind spots. For example, her first draft only listed outcomes, but her mentor pushed her to add the resource section. That was the part that made her boss take the conversation seriously — it showed she was thinking about what the company needed to invest in her success, not just what she would do. Luna: That's a great insight. The resource section is often the missing piece in these conversations. People think asking for help looks weak, but actually it shows you're thinking strategically about the bigger picture. Lucas: Right. And it also flips the conversation from 'you're not doing enough' to 'here's what we both need to invest to make this work.' It makes it a partnership, not a request. Luna: So for someone listening who wants to try this, what's the first step this week? Should they just start drafting a contract? Lucas: I'd say start with the outcomes. Take your current role and write down the three things you think would make the biggest difference to your team or the company in the next six months. Then, separately, write down what you need from your manager to achieve those — whether it's budget, authority, or access. Don't even think about the timeline yet. Just get clarity on those two pieces. Luna: And what about the timing? When should you actually bring this up with your manager? Lucas: The best time is at least three months before your company's review cycle. That gives you enough runway to deliver on the outcomes and for the manager to see the progress. But honestly, even if the cycle is two months away, starting now is better than waiting. The conversation itself is valuable, because it forces you to articulate your value proposition in a way that's hard to ignore. Luna: I love that. And I think the biggest takeaway for me is that a career contract is really about respect — respect for your own time and ambition, and respect for the manager's need for clarity and evidence. Lucas: That's a perfect way to put it. Priya didn't demand anything. She just asked for a fair process. And that's what a contract does — it replaces guessing with structure. It turns a vague hope into a measurable plan. Luna: So if you're listening and you've been waiting for the right moment to have the promotion talk, maybe this is your sign to write down what you want and what you'll deliver. You might be surprised at how much clarity that brings. Lucas: And if you try it, let us know how it goes. We're on social media as Fexingo, and we read every message. Who knows, your story might end up in a future episode.