Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The Personal SLA Writing a Service Level Agreement for Your Own Time
Transcript
- Lucas: I want to start with a conversation I had last week with a product manager at a mid-sized SaaS company. She told me she was drowning in after-hours requests — not emergencies, just people expecting her to reply at nine p.m. because she always had. Luna: Yeah, that pattern is way too familiar. Did she find a fix? Lucas: She did. She wrote what she calls a Personal Service Level Agreement. It's a one-page document that defines her response times, her availability windows, and her scope of work. Basically, an SLA for her own time. Luna: A personal SLA — I love that. So she's treating her time like a vendor contract? That's kind of brilliant. Lucas: Exactly. She sat down and listed the three things that were burning her out: late-night Slack pings, meetings that got added without context, and scope creep on projects she wasn't even supposed to own. Then she wrote a response time for each: 'I reply to non-urgent Slack messages within four business hours,' for example. Luna: Four hours — that's generous. I've seen people try for one hour and it just fuels the expectation that you're always on. Lucas: Right. She deliberately chose four hours because it's long enough to batch her responses and short enough that nothing truly urgent falls through. She also defined when she's actually available: nine thirty to five thirty, Monday through Thursday, ten to three on Friday. That last one was a game changer — her team used to drop non-urgent requests on Friday afternoon knowing she'd reply Saturday morning. Luna: So she's basically saying, 'If you send me something Friday at four, you'll hear back Monday morning.' That takes courage. How did her team react? Lucas: That's the interesting part. She shared the SLA in a team meeting. She framed it like: 'This is how I'm going to protect my focus so I can do better work for you.' Most people were actually relieved — because it gave them clarity. One engineer said he'd been afraid to bother her after hours, but now he knew exactly when he'd get an answer. Luna: So it's not just protecting yourself; it's also managing expectations for everyone else. That's a win-win. Lucas: Exactly. The key is to make it explicit. Most of us have an implicit SLA — we reply within thirty minutes because we worry about seeming unavailable. But an implicit SLA just creates anxiety on both sides. When you write it down, you remove the guesswork. Luna: I wonder though — does it work if your company culture is built on constant availability? Like if your boss expects instant responses, a personal SLA could backfire. Lucas: That's a real risk. But she actually negotiated it with her boss first. She said, 'I want to be more responsive during core hours and less responsive off hours. Can we agree on what constitutes an emergency?' They set a bar: anything that stops production or loses a customer. Everything else can wait until the next business day. Luna: So it's a conversation, not a unilateral declaration. That's smart. Because if your boss signs off, it's a lot harder for others to push back. Lucas: That's the right way to do it. And then she includes that in the SLA: 'For true emergencies, call or text. For everything else, Slack or email.' She told me her after-hours messages dropped by about sixty percent within two weeks. Luna: That's a huge shift. I want to make sure I'm getting this right — a personal SLA has three main parts: response times, availability windows, and scope of work, right? Lucas: Yes. And the scope piece is often the hardest. She actually listed the projects she owns and the ones she supports but doesn't lead. That way, when someone tries to add a task that's out of scope, she can say, 'That falls under my support category — I can help, but I need a ticket and it goes on the backlog.' Luna: So it's about boundaries, but also about clarity. And that clarity reduces friction for everyone. Lucas: Right. And if we've helped you think through a career move or decision — or even just how to set a boundary like this — a couple of dollars a month is genuinely what keeps these going. You can support the show at buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: Yeah, even a small contribution really does make a difference. It keeps us ad-free and focused on practical advice. Lucas: So back to the personal SLA — the other thing she did was create a 'response matrix.' It's a simple table: type of request, expected response time, and channel. For example, bug reports get a two-hour acknowledgement, feature requests get a same-day acknowledgement, and project updates get a weekly summary. Luna: A weekly summary — that's a great idea. It batching information reduces the back and forth. Lucas: Exactly. And she distributed that matrix to her entire team and her stakeholders. So now when someone asks, 'When will you get to this?' she can point to the document rather than defending her time in the moment. Luna: That takes the emotion out of it. It's just policy. I can see how that would be a huge relief for someone who feels guilty saying no. Lucas: It does. And I think the biggest benefit is that it forces you to be honest with yourself about what you can actually do. Most of us say yes because we're optimistic about our capacity. A personal SLA forces you to calculate availability like a resource. Luna: And then you realize you don't have room for that extra project without dropping something else. That's a hard truth, but it's better than burnout. Lucas: Right. So if someone wants to try this, where do they start? I'd recommend focusing on one source of friction first. For the product manager, it was after-hours messages. For someone else, it might be meeting requests or scope creep. Luna: Pick your biggest pain point. That makes it manageable. Lucas: Exactly. Then write down the current behavior — what you're doing now — and the desired behavior. Then frame it as a proposal to your boss or team. Use the word 'clarity' instead of 'limits.' It's not about doing less; it's about doing better work. Luna: I like that framing. And what if you're a freelancer or contractor? A personal SLA seems even more natural there. Lucas: Absolutely. In fact, many freelancers already have an implicit one. But writing it down can help you raise rates for extra-fast turnaround or after-hours work. You're essentially saying, 'Standard SLA is 24 hours. If you need it in 4, there's a premium.' Luna: So it becomes a tool for pricing as well. That's smart. Lucas: Right. And the same logic applies internally if you're an employee. You can use the SLA as a basis for renegotiating your workload with your manager. 'If you want me to take on this new project, here's what I'll need to deprioritize.' Luna: That's the scope piece again. It's all connected. Lucas: One thing I want to emphasize: a personal SLA isn't set in stone. It should evolve. The product manager I mentioned has iterated three times in six months. She added a clause about meeting-free Wednesdays, and she adjusted her response time after a team restructuring. Luna: So it's not a one-and-done document. It's a living agreement. Lucas: Exactly. And the act of reviewing it quarterly is itself a boundary maintenance ritual. You're asking, 'Is this still working?' That prevents the old patterns from creeping back. Luna: I think the biggest barrier for most people is the fear that being explicit will make them seem less dedicated. But the research shows the opposite — clarity actually increases trust. Lucas: There's a study from Harvard Business Review that found teams with explicit coordination norms reported higher satisfaction and lower turnover. The uncertainty of when someone will reply is more stressful than a slower guaranteed response. Luna: That makes sense. So the personal SLA isn't just about protecting your time; it's about creating psychological safety for everyone. Lucas: That's a great way to put it. It's a small upfront investment in documentation that pays off in reduced friction every single day. Luna: Alright, I'm definitely going to draft one for myself this week. I think my biggest pain point is meeting requests that don't need my attendance. Lucas: Perfect. That's a great starting point. And when you do, let me know how it goes. I think we could do a follow-up episode with listener experiences. Luna: I'd love that. For now, though, I think we've given people a solid framework to start with.