Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The Boundary of Saying No to Extra Work Without Explaining
Transcript
- Lucas: So there is this boundary that I think most of us never even consider, and it has to do with how we say no when someone asks us to take on extra work. Luna: Is this about the classic 'I'm too busy' excuse? Because I feel like that never really works. Lucas: Exactly. The instinct is to justify our no. We say something like 'I can't take this on because I'm already stretched on Project X' or 'I have a hard deadline Friday.' And the thing is, by offering a reason, we actually weaken the boundary. Luna: Wait — so you're saying we should say no without any explanation at all? Lucas: That's the idea. There's a 2025 study in the Journal of Organizational Behavior that looked at this exact dynamic. Researchers had managers evaluate two types of refusals from employees: ones with a reason and ones without. And the no-reason refusals were actually perceived as more legitimate and more professional. Luna: That's counterintuitive. I would have guessed that giving a reason shows you're thoughtful. Lucas: I thought the same thing. But the researchers found that reasons invite negotiation. If you say 'I'm busy with Project X,' the other person can say 'Oh, can you shift X to next week?' or 'Let me talk to your manager.' The reason becomes a handle the other person can grab onto. Luna: Right — they treat it as an obstacle to be removed, not a boundary to be respected. Lucas: Exactly. And the study showed that when you just say 'I'm not able to take that on right now,' with no follow-up, the request typically ends there. The other person might be momentarily awkward, but they don't push back because there's nothing to push against. Luna: So what's the actual phrasing? I need to hear it. Lucas: The most effective version the study found was a three-sentence structure. First, acknowledge the request — 'Thanks for thinking of me for this.' Then, state your refusal cleanly — 'I'm not able to take that on.' And finally, redirect if appropriate — 'I hope you find someone who can.' No reason, no apology, no softening. Luna: And that worked in real workplaces, not just a lab study? Lucas: There was a field experiment too. A marketing director at a mid-size B2B software company tried this for three months. She was getting five to seven after-hours requests per week, usually for small tasks that could wait. She started responding with that three-sentence structure, no justification. By the end of the quarter, her after-hours requests dropped by 60 percent. Luna: Sixty percent — that's massive. And she didn't get in trouble? Lucas: That's the interesting part. She actually got a promotion during that period. The researchers interviewed her colleagues, and most said they respected her more. One person said 'She used to seem frazzled, and now she seems in control.' The boundary itself communicated competence. Luna: I can see how that works in a relatively flat culture, but I wonder if it holds up in a more hierarchical environment. Like, if your boss asks you to do something and you just say 'I'm not able to,' isn't that risky? Lucas: That's a fair pushback. The study did find that the effect was weaker in high power-distance cultures — places where subordinates are expected to defer to authority. In those settings, a no-reason refusal could be seen as insubordination. But even there, the researchers found that adding a deferential tone helped. Something like 'I understand this is important, and I'm not able to take it on at this time.' Still no reason, but with a recognition of hierarchy. Luna: So the key is still no justification. Just the acknowledgment and the refusal. Lucas: Right. The reason is the weak point. Once you give a reason, you invite a solution to the reason. And the person asking often genuinely wants to solve it — they're not being malicious. But the net effect is your boundary gets eroded. Luna: That makes me think of something I read recently about 'explaining as a form of overfunctioning.' That in an attempt to be helpful, we over-explain, and it actually creates more work for ourselves. Lucas: That's exactly the overfunctioning trap we talked about in Episode 62. And this no-reason refusal is a direct antidote. You stop doing the emotional labor of justifying your capacity. You just state the limit. Luna: You know, this show — and this whole podcast network — we keep it ad-free because listeners like you support it. A few dollars a month genuinely keeps these going. If this boundary conversation has helped you think about your own work, you can support us at buy me a coffee dot com slash fexingo. It's a small thing that makes a real difference. Lucas: Yeah, and we mean that. Even a couple of bucks helps us keep producing episodes without sponsors. So thank you to anyone who's contributed. Luna: Alright, back to boundaries. So let's talk about the psychological mechanism here. Why do we feel compelled to explain our no in the first place? Lucas: I think it's a mix of politeness and anxiety. We're trained from childhood to give reasons for our actions. 'Why can't you play?' 'Because I have homework.' And in professional contexts, we worry that a bare no will seem rude or lazy. But the research says the opposite — a clean no is actually perceived as more respectful of the asker's time. Luna: Because you're not wasting their time with a fake reason. They get a clear answer and can move on. Lucas: Exactly. The study measured something called 'decisional respect' — how much the asker felt the person took the request seriously. And the no-reason refusals scored higher. The theory is that a reason can feel like a deflection, while a simple no feels honest. Luna: That's a reframe I need to internalize. Every time I've given a reason, I thought I was being considerate. But maybe I was just giving a handle for negotiation. Lucas: And that handle is exactly what you don't want. So the practice for this week — try it once. Next time someone asks you to take on something you genuinely can't or shouldn't, use the three-sentence structure. No reason. Luna: I'm going to try it. But I'm also curious — what about the opposite? When someone says no to you without a reason, how do you react? Lucas: That's the revealing part. The study also surveyed people on the receiving end. Most said they felt a brief moment of discomfort, then acceptance. They didn't feel disrespected. They actually felt the person was being straightforward. So the discomfort is mostly in our own head. Luna: So it's a boundary that not only protects our time but also makes us seem more competent. That's a win-win. Lucas: It really is. And it's one of the simplest boundaries to implement. You don't need a new calendar system or an auto-responder. You just need to change four words from 'I can't because...' to 'I'm not able to.' Luna: I think the hardest part will be breaking the habit. I've been explaining my nos for years. It's almost automatic. Lucas: That's why the researchers suggested practicing in low-stakes situations first. Say no to a casual lunch invitation without giving a reason. Or decline a minor favor. Build the muscle before you use it with your boss or a big client. Luna: That's practical. I'm going to start with a colleague who always asks me to review her decks. I'll just say 'I'm not able to review that today' and stop there. Lucas: And watch what happens. My bet is she'll say 'Okay, no problem' and move on. And you'll have reclaimed a boundary without any drama. Luna: I'll report back next episode. I'm genuinely curious. Lucas: Please do. And I think this ties into a bigger question for us to think about going forward. If we stop explaining, what else changes? Do we start fewer conversations? Do we listen differently? The no-reason boundary is a small shift, but it might ripple into how we communicate overall. Luna: That's a good forward-looking question. For now, let's leave it there. Thanks, Lucas. Lucas: Thanks, Luna.