Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / How a Career Commitment Contract Reshapes Work Boundaries
Transcript
- Lucas: So we talk a lot on this show about setting boundaries, and one thing that keeps coming up in listener questions is — how do you actually stick to them when the pressure comes? When your boss emails at 9 PM and says 'hey, can you just...' Luna: Right, the 'just' is doing a lot of work there. Lucas: Exactly. So today I want to talk about a specific tactic that I've seen work really well for people in demanding roles. It's called a career commitment contract. And it's exactly what it sounds like — you write down your boundary rules, you share them with someone, and you treat it like a real agreement. Luna: Before we go deep on this — and I'm genuinely curious about it — I just want to mention something. If you're listening and you've used any of the ideas from this show to rethink your own work habits or make a career move, we'd love it if you considered supporting the show. It's what keeps us ad-free and independent. You can do that at buy me a coffee dot com slash fexingo. Lucas: Yeah, that's a big help. And honestly, the reason I bring it up here is that this whole idea of a contract is about making a commitment public — and listener support works the same way. It's a small gesture that keeps us accountable to keep making content that's useful. Luna: Exactly. So back to the contract. Where does this come from? Lucas: The concept isn't new — it's borrowed from behavioral economics. There's research showing that when people write down a goal and share it with someone, they're significantly more likely to follow through. It's the same reason gym-goers who tell a friend they'll be at 6 AM actually show up. Luna: So this is basically the 'commitment device' idea applied to work boundaries. Lucas: Exactly. And I have a concrete example. A software engineer I know — let's call him Dan — was getting constantly interrupted by Slack messages during his deep work hours. He'd block off 9 to 11 AM for coding, but every morning someone would ping him with a 'quick question' and he'd lose focus for an hour. Luna: Classic attention residue problem. Lucas: Right. So Dan wrote a one-page contract that stated: 'From 9 to 11 AM, I will not respond to any non-urgent messages. I will check Slack at 11 AM and prioritize responses. If something is truly urgent, please call or text my mobile.' He printed it, put it on his desk, and — here's the key — sent it to his team lead and three close colleagues. Luna: Did it work? Lucas: It did, but not immediately. The first week, a couple of people still pinged him. But because he had the contract, he felt empowered to say 'Hey, I mentioned in my contract that I'm unavailable until 11 — can this wait?' And after two weeks, the interruptions dropped by about 80 percent. Luna: I like that the contract gave him a script. It's not 'please don't bother me' — it's 'per our agreement, I'll get back to you at 11.' That's much harder to argue with. Lucas: Exactly. And that's the psychological mechanism. When you make a public commitment, you've effectively created social accountability. Your colleagues now have an explicit understanding of your boundaries, so when you enforce them, it's not personal — it's just following the rules you all agreed to. Luna: But I want to push back a little. Doesn't this assume a pretty supportive culture? What if your boss doesn't care about your contract? Lucas: That's a fair point. And I think the contract works best when you have at least some control over your schedule. But even in less supportive environments, the act of writing it down clarifies your own priorities. You're forced to decide what's actually non-negotiable. And you can still share it with a peer — doesn't have to be your boss. Luna: So what goes into a good contract? Lucas: I'd say three things. First, specific behaviors — not 'I'll be more focused,' but 'I will not check email between 8 and 10 AM.' Second, the consequences or backup plan — like 'if I must respond, I'll do so within 2 hours.' And third, the sharing step — who you're going to send it to and how often you'll review it. Luna: I know a marketing director who did something similar around response times. She was expected to reply to client emails within 30 minutes, even on weekends. So she wrote a contract with her team: 'I will respond to all emails within 24 hours on weekdays, and within 48 hours on weekends. For urgent issues, please call.' And she shared it with all her clients. Lucas: How did clients react? Luna: Most were fine. One client pushed back, but she explained that this would actually improve her quality of responses because she'd have time to think. And she used the contract as a reference point in meetings. Over time, it just became the norm. Lucas: That's a great example. The contract doesn't have to be rigid — it can be updated. In fact, I'd recommend reviewing it every quarter, because your priorities shift. What was non-negotiable in Q1 might be less important in Q2. Luna: So this is a living document, not a stone tablet. Lucas: Exactly. And I think that's part of why it works — it's a deliberate, conscious choice, not just a vague intention. When you write down 'I will not take work calls after 7 PM,' it's much harder to ignore that boundary at 7:05 when your phone rings. Luna: What if someone doesn't have a supportive manager or team at all? Is a contract still useful? Lucas: I'd say yes, but with a caveat. If your workplace is genuinely toxic, no contract is going to fix that. But for most people in reasonably functional environments, the contract is a tool to negotiate your boundaries more explicitly. And even if no one else signs it, you're still making a commitment to yourself. Luna: So it's partly a self-accountability device. Lucas: Right. In fact, the research on 'implementation intentions' shows that simply specifying when and where you'll perform a behavior dramatically increases follow-through. So even if you never share the contract, the act of writing it down helps. But sharing multiplies the effect. Luna: I want to circle back to something you said earlier about enforcement. What's the hardest part of sticking to the contract? Lucas: The first time you have to enforce it. That's when the social pressure is highest. You've told people your boundary, and then someone tests it — either intentionally or just out of habit. If you cave, the contract loses its power. But if you hold firm, it gets easier every time. Luna: So you need to be prepared for that moment. Have your script ready. Lucas: Exactly. And that's where the contract helps again — because you're not making up a rule on the spot. You're referencing something you both agreed to. It depersonalizes the 'no.' Luna: I can see this being particularly useful for people who have a hard time saying no. The contract does the saying for them. Lucas: That's a really important point. For people who are conflict-averse, a written agreement is a huge relief. You're not rejecting a person — you're following a plan. And most reasonable people will respect that. Luna: Alright, so let's talk about how to actually create one. Do you have a template you like? Lucas: I do. It's simple. Four sections. First, the boundary itself — what are you committing to? Second, the rationale — why does this matter? This is important because it helps others understand your motivation. Third, the exceptions — when might you break this rule? And fourth, the review date — when will you revisit this? Luna: I think the exceptions section is crucial. If you say 'I never check email after 6 PM,' but then you do it once because of a genuine emergency, you undermine your own credibility. Better to build in a realistic escape hatch. Lucas: Exactly. For example, 'I will not check email after 7 PM, except for pre-scheduled on-call weeks or known project launches.' That way, when you do respond late, it's not a violation — it's within the agreed framework. Luna: So the contract actually increases your flexibility in a way, because it clarifies when you're available and when you're not. Lucas: Right. It's not about being rigid — it's about being intentional. And that's the core message here. Boundaries aren't walls; they're doors that you control. The contract just makes the control explicit. Luna: I'd love to hear from listeners who try this. Have you written a work contract? Did it help? We might do a follow-up episode with your stories. Lucas: Absolutely. And in the meantime, if you want to support the show so we can keep doing episodes like this, you know where to find us — buy me a coffee dot com slash fexingo. No pressure, just a small way to keep this going. Luna: Yeah. And if you're not ready to do that, no worries — just try writing a contract this week. Even if you never show it to anyone, I think you'll be surprised at how clarifying it is. Lucas: Alright, that's it for today. We'll be back on Thursday with another episode. Until then, take care of your boundaries — and yourselves.