Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Ask for Time Off When You Are the Busiest Person on the Team
Transcript
- Lucas: We got a question this week from a listener named Sarah, and she says: 'I am the most senior person on my team, and I haven't taken a full week off in 18 months. Every time I think about booking a vacation, I get anxious about what will fall apart while I am gone. I am not even sure I can ask. What do I do?' Luna: Oh, I feel that in my bones. That feeling of being indispensable — it is a trap, but it is a very comfortable-looking trap. Lucas: It is. And the first thing I want to say to Sarah is: you are not actually indispensable. No one is. But that statement feels hollow when you are the one who knows where all the bodies are buried. So let's get tactical. Lucas: I want to walk through a specific approach. Sarah works at a mid-sized tech firm, about 300 employees, and she is a senior data analyst. She owns the quarterly reporting pipeline that the executive team depends on. That is real leverage. But it is also real risk — for her and for the company. Luna: Right — if she goes dark for a week with no preparation, that pipeline breaks and everyone notices. So the ask has to include a plan. Lucas: Exactly. Step one: document your coverage plan before you even schedule the conversation. Sarah needs to identify the two or three tasks that absolutely cannot slip — in her case, the raw data ingestion and the executive summary — and then identify who can be trained to handle each one for a week. Not perfectly, but safely. Lucas: She should also write a one-page runbook: logins, file locations, the one phone number to call if something breaks. That document is her insurance policy. It shows her manager that she has thought about continuity, not just her own vacation. Luna: And that is actually a leadership move. A runbook means the team is less fragile. It makes Sarah more promotable, not less. Lucas: Exactly. Step two: frame the request around business outcomes, not personal need. Most people walk in and say 'I need a break, I am burned out.' That is true, but it puts the manager in a defensive position. Instead, Sarah can say: 'I want to make sure our reporting pipeline is resilient enough that I can take a week off without it being a crisis. I have a plan to cross-train someone. Can I run it by you?' Luna: That reframes it from 'please let me go' to 'help me make the team stronger.' The manager hears: this benefits me. Lucas: And step three — this is the one sentence that makes it work. After she presents the plan, she says: 'I am planning to take the week of August 10th. Does that timing work for the team, or should we shift it by a week or two?' She is not asking permission. She is informing and negotiating timing. Luna: That is huge. The difference between 'Can I go?' and 'Here is when I am going, can we adjust?' is night and day. One is deferential, the other is collaborative. Lucas: And most managers will say yes to a collaborative request that also makes their own job easier. Especially if the coverage plan is solid. Luna: I want to push back a little, though. There is a risk that Sarah over-functions here. She builds the perfect runbook, trains the backup person, and then her manager just assumes she can always do that — and never gives her a real break. How does she avoid that? Lucas: That is a great point. The key is to treat the coverage plan as a pilot. She should say: 'Let me try this for one week. I will be completely offline — no Slack, no email — and if something breaks, we will debrief when I get back and adjust the plan.' That sets the expectation that this is a test, not a permanent doubling of her workload. Lucas: And if the manager resists even that — if they say 'we cannot afford for you to be offline' — then Sarah has a different problem, which is that her manager is managing through heroics, not systems. That is a red flag worth paying attention to. Luna: Speaking of red flags — there is actually some recent data on this. Microsoft released a WorkLab survey in 2025 that looked at PTO usage and retention. They found that teams where people take all of their allocated paid time off have 22 percent higher retention than teams where people leave PTO on the table. Luna: So Sarah is not just doing herself a favour by taking a week off. She is actually contributing to team stability. Lucas: That is a powerful number to have in your back pocket. If her manager pushes back on cultural grounds — 'we are all grinding here' — she can say: 'Actually, teams that use their PTO have lower turnover. I want to be part of this team for a long time, and that means modelling sustainable work.' Lucas: Let's talk about the emotional side for a second. Sarah said she gets anxious thinking about what will fall apart. That anxiety is real, but it is also a signal that she has been operating without a safety net for too long. Luna: And that anxiety is on her, but it is also on the system. She should not have to feel like she is abandoning ship by taking a vacation. Lucas: Right. And the antidote is preparation. When she has the runbook, the trained backup, and the manager's sign-off, the anxiety drops dramatically. Not to zero — but to a manageable level. Lucas: One more tactical piece: she should set an out-of-office autoreply that redirects urgent requests to her backup, and she should actually turn off notifications on her phone. If she checks Slack from the beach, she undermines the whole experiment. Luna: That is the hardest part for most people. The mental habit of checking. But if she has done the prep, she can afford to let go. Lucas: And if we have helped you think through a career move or a workplace conversation like this one, there is a simple way to help us keep these episodes coming. A couple of dollars a month at buy me a coffee dot com slash fexingo genuinely makes a difference — it is what keeps this show ad-free and focused on the questions you actually send in. Luna: Yeah, we read every question and we build episodes around them. So if you have gotten something out of this, that link is a really tangible way to say thanks. Lucas: Alright — back to Sarah. Let's say she gets the time off approved, takes the week, and comes back. The world did not end. Now what? Lucas: Now she has a responsibility to debrief. She should schedule a 15-minute check-in with her manager and her backup to say: 'What worked? What broke? What do we need to update in the runbook?' That closes the loop and makes the next vacation even easier. Luna: And it normalises the idea that she takes time off. The second time she asks, it is not a big deal — it is just what she does. Lucas: Exactly. The goal is to make taking a week off a routine operational event, not a crisis. And that starts with one well-prepared conversation. Luna: I think the bottom line for Sarah is: you are not a bad employee for wanting a break. You are a smart employee for building a system that lets you take one. Lucas: And that system benefits everyone — her, her team, and her manager. So go ahead and book the flight.