Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The 72-Hour Rule That Stopped Me Overcommitting
Transcript
- Lucas: There's a moment that I think a lot of us know. You're in a meeting, someone says, 'Hey, could you take a look at this deck by Friday?' And before your brain has fully processed the request, you hear yourself say, 'Sure, no problem.' And then you walk out of the room and immediately regret it. Luna: Yeah, that feeling is almost physical. The weight of an extra commitment you didn't really have time for, but you said yes because it was easier in the moment. Lucas: Exactly. And the research on this is pretty clear — we're terrible at making decisions under pressure. When someone asks us for something, our brain defaults to social agreement. We want to be helpful, we don't want to let the team down. So we say yes, even when a more considered answer would be no. Luna: So what's the fix? I assume there's a specific tactic you want to talk about. Lucas: There is. It's called the 72-hour rule. And the concept is dead simple: when someone asks you to take on a new task, project, or commitment, you do not answer immediately. You tell them you need 72 hours to check your calendar and priorities, and then you get back to them. Luna: Three full days. That's a long time in most workplace cultures where people expect answers within hours. Lucas: It is. And honestly, that's partly why it works. The rule forces you to break the urgency loop. Most requests aren't actually urgent — they just feel that way because they're asked in person or in a fast-paced meeting. 72 hours gives you enough distance to evaluate the request on its actual merits, not on social pressure. Luna: I want to hear how this plays out in real life. Do you have a case study? Lucas: Yeah, I talked to a project manager at a mid-sized software firm — let's call her Sarah. She was drowning in overcommitment. She tracked it for a month, and 80% of the requests she said yes to, she later regretted. Not because the work was bad, but because it pushed her core deliverables to evenings and weekends. Luna: Eighty percent. That's brutal. So she was basically saying yes four out of five times to things that didn't belong on her plate. Lucas: Exactly. And she knew she had a problem. But the habit was so ingrained that she couldn't stop herself in the moment. So she committed to a two-month experiment with the 72-hour rule. Every time someone made a request, she'd say, 'Let me check my workload and get back to you by end of day Thursday.' Or whatever three business days out was. Luna: How did people react? I can imagine some colleagues getting frustrated. Lucas: There was some initial pushback. A couple of people said, 'I just need a quick yes or no.' But Sarah held the line. And after about two weeks, something interesting happened. People started respecting the boundary. They knew she wasn't ignoring them — she was taking a thoughtful approach. And she found that most people actually preferred a thoughtful answer two days later over an immediate 'yes' that turned into a half-baked deliverable. Luna: Right, because the alternative to a delayed answer isn't a better immediate answer — it's a rushed commitment that often leads to missed deadlines or burnout. Lucas: Exactly. After two months, Sarah's overcommitment rate dropped from 80% to 30%. She was saying no to things that truly weren't her priority. And the things she said yes to, she had more energy for, because she'd consciously chosen them. Luna: What did she actually do during those 72 hours? It can't just be staring at the request. Lucas: Great question. She developed a three-question framework. First: Does this align with my top three priorities for this quarter? Second: If I say yes, what current commitment will I have to deprioritize or drop? And third: Is this a growth opportunity that moves me toward a skill I want to build, or is it just busywork? Luna: That third question is key. Because not all extra work is bad. Sometimes saying yes to the right thing can be a career accelerator. Lucas: Absolutely. The 72-hour rule isn't about never saying yes. It's about saying yes to the right things. And the delay gives you the space to distinguish between a genuine growth opportunity and a task that someone else could do, or that shouldn't be done at all. Luna: There's a psychological mechanism here too, right? The urgency hijack. Lucas: Yeah, it's well-documented. When a request comes with a sense of urgency — which most workplace requests do, even if artificially — our amygdala activates. We go into a fight or flight social response. Saying no feels like a social threat, so we default to yes. The 72-hour rule essentially bypasses that. By the time you respond, the amygdala has calmed down, and your prefrontal cortex — the rational part — is back in charge. Luna: So it's not just about checking your calendar. It's about letting your nervous system settle. Lucas: Exactly. And I think that's why the rule works even when you know intellectually that you should say no. The gap between knowing and doing in the moment is huge. The 72-hour rule bridges that gap. Luna: What about the social cost? Some people worry that delaying an answer makes them seem indecisive or unreliable. Lucas: That's a real concern. But in practice, most people I've talked to find the opposite. When you say, 'I want to give this the attention it deserves, let me get back to you,' it signals that you take commitments seriously. That's actually a sign of reliability, not indecisiveness. Sarah said her team's trust in her went up, because when she said yes, they knew it was a real yes, not a future fire drill. Luna: I could see this being especially useful for people who are naturally high-agreeability. The ones who hate disappointing others. Lucas: That's exactly the personality profile that benefits most. If you're someone who feels a strong emotional pull to be helpful, the 72-hour rule gives you permission to pause. It's a buffer between the emotional impulse and the rational decision. Luna: Is there any variation? Like, does it have to be exactly 72 hours, or could it be 48 or 24? Lucas: The principle is more important than the number. 72 hours works because it spans a weekend or a full three-day work cycle. It gives you at least one night's sleep, which is crucial for emotional regulation. Some people use a '24-hour rule' for smaller requests. But for anything that represents more than a couple of hours of work, I'd recommend the full three days. Luna: One thing I'm wondering about: what if the request truly is urgent? Like a client emergency or a deadline that's actually tomorrow. Lucas: Fair point. In those rare cases, you use judgment. If someone's house is on fire, you don't ask for 72 hours. But the key word is 'truly urgent.' In my experience, about 90% of requests that feel urgent are actually not. They're just poorly planned on someone else's part. The 72-hour rule helps you filter out the false urgency. Luna: There's a nice parallel here with the 'micro-yes' boundary we covered in Episode 71. That was about pausing before committing to small tasks in the moment. This is like the macro version. Lucas: Exactly. The micro-yes is for things like 'Can you answer this quick question?' The 72-hour rule is for substantial commitments — projects, recurring tasks, extra responsibilities. Think of it as a decision-making protocol for the things that could meaningfully shift your workload. Luna: So if someone wants to try this, what's the script? How do you actually ask for 72 hours without sounding weird? Lucas: It's simpler than you think. Something like: 'I want to give this the attention it deserves. Let me check my current priorities and I'll get back to you by Thursday.' If they push, you can add: 'I've found that when I rush into yes, I end up overcommitting, and I want to make sure I can deliver on this if I take it on.' That actually builds trust. Luna: And if the person still pushes after that? Lucas: Then they're not respecting your boundary, which is a signal in itself. You might say, 'I understand this is time-sensitive. I can give you a quick yes right now, but I want to be upfront — if I say yes, I may not be able to give it the quality it deserves. Which do you prefer?' That usually makes them pause. Luna: That's a good reframe. You're not being difficult; you're being responsible. Lucas: Right. And most managers actually appreciate that. They'd rather have a thoughtful yes than a rushed yes that leads to a mediocre output. Luna: Let's talk about what happens after the 72 hours. You've evaluated. Maybe you decide it's a no. How do you deliver that? Lucas: This is where many people stumble. They delay the no because they're afraid of the reaction. But Sarah had a straightforward approach: she'd say, 'Thank you for the opportunity. After reviewing my priorities, I can't take this on right now without compromising my current commitments.' And then she'd offer an alternative — 'Maybe X could help?' Or 'Could we revisit this next quarter?' Luna: That feels respectful. You're not just closing the door; you're pointing to other possibilities. Lucas: Exactly. And the 72-hour rule gives you time to think of those alternatives. If you say no on the spot, you don't have that space. Luna: I tried a version of this myself last week. A colleague asked me to join a working group that would meet weekly for three months. My first instinct was to say yes because I like the person. But I used the rule and realized I'd have to drop my Tuesday writing block. So I said no, but offered to review their output monthly instead. Lucas: That's a perfect example. The rule didn't lead to a hard no; it led to a smarter yes — a scaled-back version that actually works for both of you. Luna: And the colleague was totally fine with it. She said, 'That's actually better because we'll have an outside perspective.' Lucas: That's the counterintuitive thing. When you take time to think, you often come back with a more creative solution than just yes or no. Luna: So what's the one takeaway you want listeners to remember? Lucas: The next time someone asks you for something, before you answer, say: 'Let me get back to you.' Give yourself permission to pause. Even 24 hours can make a difference. You might find that the most powerful word in your vocabulary isn't 'no' — it's 'later.' Luna: And if today's episode was useful to you, the way we keep these episodes ad-free is through listener support. You can find us at buy me a coffee dot com slash fexingo. Just a small way to keep the conversations going. Lucas: Yeah, we appreciate everyone who's helped keep this show independent. It means we can spend time on the details that matter. Luna: So the challenge for this week: pick one request that comes your way and apply the 72-hour rule. See what happens. Lucas: And if you try it, let us know. We'd love to hear how it goes. For now, thanks for being here.