Latest / Career Coaching with Fexingo: Professional Coaches, Career Counselors, and Guidance for Workers / How to Use a Career Contract to Set Clear Expectations
Transcript
- Lucas: So you know how sometimes you start a new role or even a new project and a few months in you realize you and your manager have completely different ideas about what success looks like? Luna: Oh absolutely. That happened to me early in my career. I thought I was crushing it, and my manager thought I was missing the mark on priorities I didn't even know existed. Lucas: Right. That gap is incredibly common, and it's also incredibly costly — in terms of stress, wasted effort, and missed promotions. The fix is surprisingly simple on paper but takes some nerve to execute: you write a career contract. Luna: A career contract. You mean like a literal written document between you and your boss? Lucas: Exactly. Not a legal contract, obviously, but a one- or two-page document that spells out your responsibilities, your manager's support commitments, the metrics for success, and the timeline for review. It's like a role charter, but specifically tied to your career progression. Luna: I love this. Where did you first see it in practice? Lucas: A friend of mine — let's call her Sarah — was a marketing manager at a mid-sized tech company in Austin. She was frustrated because she kept getting pulled into fire drills and her strategic projects kept slipping. Her director was happy with her output, but she wasn't getting promoted. So she drafted a six-month career contract. Luna: What did she put in it? Lucas: She had four sections. First, her core responsibilities — the three big projects she owned. Second, the resources she needed, like dedicated design support and no more than one ad-hoc request per week. Third, the success metrics — things like campaign conversion rates and stakeholder feedback scores. Fourth, a clear promotion gate: if she hit all metrics in six months, she'd be promoted to senior manager. Luna: And her director just agreed to that? Lucas: Not immediately. She presented it as a tool to avoid misalignment. She said something like, 'I want to make sure we're both investing my time in the highest-impact areas. This document is my best guess at how to do that. Can we refine it together?' The director ended up tweaking a couple of the metrics but signed off on the whole thing. Luna: That framing is key. It's not a demand — it's a collaborative alignment tool. Lucas: Exactly. And the result was that Sarah had a clear north star. She could say no to distractions by pointing to the contract. And when her six months were up, she had a documented track record of exactly what she'd promised. She got the promotion. Luna: I can see how this would be especially useful in flat organizations or startups where roles are fluid. But what if your company has a formal performance review cycle? Doesn't that cover the same ground? Lucas: It can, but performance reviews are often backward-looking and generic. A career contract is forward-looking and specific to you. Plus, you don't have to wait for the review cycle — you can propose one at any time. Quarterly or even monthly check-ins against the contract keep things on track. Luna: So what are the essential clauses someone should include if they want to try this? Lucas: I'd recommend five. One: your primary responsibilities — no more than three to five bullet points. Two: the resources and support you need from your manager — specific things like budget, headcount, or protected time. Three: the measurable outcomes you'll deliver. Four: a career goal — like a promotion, a specific skill certification, or a stretch assignment. Five: a review date and the decision criteria. Luna: And how do you bring it up without making it weird? Lucas: You make it about shared efficiency. You say something like, 'I've been thinking about how to make sure our priorities are fully aligned so I can deliver the most value. I drafted a one-page role compact that I'd love to get your feedback on.' Most managers appreciate the initiative because it saves them from having to manage you more closely. Luna: That is so smart. I'm going to try this with my own team. One concern though — what if your manager sees it as a lack of trust or an attempt to box them in? Lucas: That's a real risk, especially with insecure managers. In that case, you might frame it more softly — 'I want to make sure I'm prioritizing the right things. Can we write down what success looks like in the next quarter so I don't miss anything?' If they still resist, you've learned something important about the culture. Luna: Right. It becomes a diagnostic tool too. If your manager won't commit to clarity, that's a red flag. Lucas: Exactly. And you can also use a career contract for yourself even without your manager's sign-off. Write your own version, share it informally, and use it as your personal compass. The act of writing clarifies your own thinking. Luna: That's a good fallback. So let's say I write a contract, get it signed, and then after three months the company pivots and my role changes. What then? Lucas: You treat it as a living document. Schedule a renegotiation. Say, 'Our priorities have shifted. Let's update the contract to reflect the new reality.' That's actually easier than starting from scratch because you have a framework in place. Luna: I like that — it normalizes iteration. It's not a failure of the contract, it's a feature. Lucas: Precisely. And the more you practice, the better you get at articulating your value and negotiating your terms. It's a career superpower. Luna: Okay, I'm sold. Let's talk about one more concrete example — maybe someone in a non-corporate role, like a teacher or a nurse. Lucas: Great point. A teacher could write a contract with their principal that defines their classroom responsibilities, the professional development they need, and the support for behavioral issues. For a nurse, it might include shift preferences, patient load limits, and a timeline for certification advancement. The structure is the same. Luna: And it works even if there's no formal promotion path. The contract can focus on skill-building or project ownership instead. Lucas: Exactly. I've seen people use it to negotiate a lateral move into a new department, or to secure a mentorship commitment from a senior leader. The key is writing it down. Luna: You know, this whole conversation reminds me that a lot of career advice is about navigating systems that weren't designed for us. But a career contract is something you create. It's proactive, not reactive. Lucas: That's exactly why I wanted to cover it. And if this show has helped you think through a career move or decision like that, it's worth mentioning that listener support is what keeps this podcast ad-free. A couple of dollars a month genuinely makes a difference — buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to say thanks if you've gotten real value. And it helps us keep doing episodes like this one — no sponsors, just practical tools. Lucas: So if you're inclined, that's the place. And back to the contract — one last tip: if you're not ready to share it with your manager, start by writing a personal career contract for yourself. Define what you want, what you'll deliver, and how you'll measure it. That alone can be transformative. Luna: I love that. A personal contract takes away the ambiguity and gives you agency. You're not waiting for someone else to define your success. Lucas: Exactly. Whether you use it with your boss or just for yourself, the act of writing forces clarity. And clarity is the foundation of a career you actually want.