Latest / Career Coaching with Fexingo: Professional Coaches, Career Counselors, and Guidance for Workers / How to Use Career Contracts to Level Up Your Role
Transcript
- Lucas: You've been in your job for maybe two or three years. You're good at it. Your boss likes you. But you're starting to feel like you've plateaued — the same tasks, the same meetings, the same output. The typical advice is to start looking externally. But today I want to argue that sometimes the best career move is the one you negotiate right where you already are. Luna: So you're talking about the internal promotion path, but more specifically — what you've called before a 'career contract.' Can you define that? Lucas: Yeah. A career contract is a formal or semi-formal agreement between you and your manager — or between you and your organization — that defines a new scope of work, new responsibilities, specific learning outcomes, and a timeline. It's not a raise conversation, though it can lead to one. It's a growth conversation. You're essentially saying: I want to do X, Y, and Z over the next six months, and here's how that benefits the team. Luna: And before we go deeper — I know this is a free show, and if you've found our career conversations helpful, you can support us at buy me a coffee dot com slash fexingo. Just a simple way to keep this ad-free. Okay, Lucas, what's the first step someone should take if they want to propose a career contract? Lucas: First, be clear on what you want. Not just 'more responsibility' — that's too vague. You need a specific project, skill, or domain. For example, say you're a marketing manager and you want to move into data analytics. You don't just ask to 'do more analytics.' You propose: 'I want to lead the quarterly customer segmentation analysis, using SQL and Tableau. I'll take a two-week online course to get up to speed, and I'll deliver the first draft by the end of Q3.' That's concrete. Luna: So you're packaging it as a proposal — scope, resources, timeline. That sounds like something a manager can actually say yes to, because they see a clear deliverable. Lucas: Exactly. And you need to frame it in terms of what the organization gets. Not just 'I want to grow,' but 'If I develop this capability, the team can do X more efficiently.' Tie it to a business need. That's the difference between a request that feels like a personal favor and one that feels like a strategic investment. Luna: What about timing? When is the right moment to bring this up? Lucas: Ideally, during a one-on-one or a performance review — any time your manager is already thinking about your development. But also, if your team is about to launch a new project or you see a gap that no one is filling, that's your opening. You say, 'I notice we don't have anyone focused on the customer retention piece. I'd like to take that on over the next six months, and here's my plan.' Luna: That makes sense — you're solving a problem, not creating extra work for your boss. What about the risk? What if your manager says no? Lucas: A no is useful information. If they say no because the organization genuinely doesn't have capacity, that's one thing. But if they say no because they don't want you to grow — that tells you something about your future there. And even a no can be negotiated: 'Okay, can we start with a smaller version? What if I just shadow the data team for two hours a week?' The key is to keep the conversation going. Luna: So it's not a one-shot attempt, it's an ongoing dialogue. I've seen people use career contracts to move from individual contributor to team lead, or from one function to another, all without leaving the company. Lucas: Right. I know a case where a customer support rep at a software company wanted to move into product management. She drafted a three-month contract: she'd spend 20 percent of her time on user research, attend product team stand-ups, and then present a feature recommendation at the end of the quarter. Her manager agreed, she did great, and she eventually got a full-time product role. That's the model. Luna: And what if you're in a more formal or hierarchical company? Does this still work? Lucas: It works, but you may need to be more structured. In some companies, you might need to put it in writing and get HR approval. But the principles are the same: you're creating a mini apprenticeship within your current role. And honestly, many companies are hungry for people who proactively shape their own growth. It shows initiative. Luna: So the career contract is really about taking ownership of your own development, rather than waiting for someone to hand you an opportunity. Lucas: Exactly. One more thing: document everything. After your conversation, send a follow-up email summarizing what you discussed — the scope, the timeline, the success criteria. That creates a paper trail and makes it real. And six months later, when you've delivered, you have a strong case for a promotion or a title change. Luna: That's a great point. It turns a vague hope into something measurable. So if someone listening wants to try this, what's one concrete step they can take this week? Lucas: Pick one skill or project you want to develop. Write down a one-paragraph proposal: what you'll do, how it benefits the team, and a timeline. Then bring it to your next one-on-one. That's it. You don't need a 10-page deck — just a clear, focused ask. Luna: I like that. And if listeners want more on this topic, we'll link to some templates in the show notes. For now, the challenge is to think about one area where you want to grow and start that conversation. Lucas: Absolutely. Because you don't always need a new job to have a new career. Sometimes you just need a new contract with the one you've got.