Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The Email Response Time Expectation That Is Burning You Out
Transcript
- Lucas: So I want to start with a number that stopped me cold when I first saw it. Microsoft published a study a few years back that tracked what happens after an email interruption — not a phone call, not a Slack ping, just an email that you actually stop to read and maybe reply to. Luna: I think I know where this is going, and it's not flattering for most of us. Lucas: It takes an average of twenty-three minutes to return to the same state of focus you were in before the interruption. Twenty-three minutes. That's not the time you spend writing the email, that's the cognitive cost of context-switching back into whatever you were doing. Luna: So if you get four emails in a morning that you feel compelled to answer right away, you've essentially lost an hour and a half of deep work before lunch. Lucas: Exactly. And the really insidious part is that we've all internalized this expectation that a reply should come within a few hours — or, in some cultures, within minutes. That expectation didn't exist twenty years ago. It wasn't even possible. Luna: Right, the BlackBerry era is what started it. Before that, email was something you checked maybe twice a day, on a desktop computer. Lucas: The BlackBerry gave us push notifications in the early 2000s, and suddenly your boss could email you at nine PM and know you'd see it before you went to sleep. Then the iPhone, then Slack, and now we're at a point where a one-hour gap in response can prompt a follow-up: 'Hey, just checking in on my previous email.' Luna: And the follow-up itself is a second interruption, so the recipient pays twice. So what's the fix? Because I've tried turning off notifications and it works for about two days before my boss calls me. Lucas: The fix I've seen work — and I've been doing this for about six months now — is something I call the batch-reply buffer. You designate specific windows each day for email and messaging, and you communicate those windows to the people you work with most closely. Luna: But doesn't that just shift the anxiety? Now I'm worried about disappointing people during the four hours I'm 'offline.' Lucas: It can, if you don't set expectations explicitly. The key is to be transparent. I literally have a line in my email signature that says: 'I check email at 10 AM and 3 PM. If something is urgent, please call or text.' And I train my main collaborators on that. Luna: Has anyone ever abused the 'urgent' exception? Lucas: Almost never. And when they do, it's actually urgent — server down, client crisis, that kind of thing. The vast majority of what lands in my inbox can wait four hours. The world does not end. Luna: I tried something similar but with a four-hour response window for internal emails only. I told my team: 'I'll reply to internal emails within four hours during business days.' And I was terrified I'd seem unresponsive or lazy. Lucas: And what happened? Luna: My stress dropped noticeably in the first week. And my output actually went up because I was blocking two-hour chunks in the morning and afternoon. Nobody complained. One person even said they appreciated the clarity. Lucas: That matches the data. A study from the University of California Irvine found that people who checked email in batches rather than continuously experienced lower heart rate variability — a physiological marker of lower stress — and reported feeling more in control. Luna: So why doesn't everyone do this? I think the main barrier is fear. Fear that you'll miss an opportunity, fear that you'll seem lazy, fear that your boss will think you're not pulling your weight. Lucas: And that fear is rational in some workplaces. Certain industries — law, finance, emergency services — genuinely require fast response. But for most knowledge workers, the cost of constant availability far outweighs the benefit. Luna: Let's talk about the cost more concretely. What are you actually losing when you're always-on? Lucas: You're losing the ability to do what Cal Newport calls 'deep work' — cognitively demanding tasks that require sustained attention. Writing a strategy document, analyzing a spreadsheet, coding a feature, editing a podcast script. Those tasks need at least sixty to ninety minutes of uninterrupted time to reach a productive flow state. Luna: And every email notification resets that clock. So by 2 PM, you've maybe had one decent deep work session, and the rest of the day is fragmented into five-minute increments. Lucas: Right. And the ironic thing is that many of us started using email and Slack to be more productive. The tools themselves are neutral. The norms around them have become pathological. Luna: I want to get tactical here. If a listener wants to start pushing back on the instant-reply expectation, what's the first step they should take? Not a big overhaul, just one thing. Lucas: Turn off all email and Slack notifications on your phone. Not the apps — delete them or disable notifications entirely. And then set a personal rule: you check email from a computer, not from your pocket. That alone will break the Pavlovian loop. Luna: I did that two years ago. It was uncomfortable for about a week. Now I can't imagine going back. Lucas: And then the second step: pick one communication channel where you will set a response time expectation. If you're mostly an email person, put the batch times in your signature. If you're a Slack shop, set your status to 'Focus time, replies in 2-4 hours' and actually mean it. Luna: What about people who worry they'll miss something urgent? Like a client issue or a system outage. Lucas: That's a legitimate concern, but it's also a symptom of a broken notification system. If something is truly urgent, it should come through a channel that's designed for urgency — a phone call, a dedicated emergency line, a specific Slack channel with an escalation protocol. Not a general email inbox. Luna: So the real fix isn't just individual willpower. It's about redesigning how your team communicates what's actually urgent. Lucas: Exactly. And that's a conversation you can have with your manager: 'I want to be more responsive to truly urgent things. Let's define what counts as urgent and give it its own channel.' Most reasonable managers will appreciate the clarity. Luna: I want to bring up one more thing. There's a social cost to being slow to reply. In some workplaces, response speed is a proxy for commitment or competence. Lucas: It's a terrible proxy, but it exists. And if you're in a culture where that's deeply entrenched, you might need to move more slowly. But even there, you can find allies. You can propose a team trial: 'Let's try asynchronous afternoons for two weeks and see if our output changes.' Data is persuasive. Luna: And if the data shows better output and lower stress, then you have ammunition for making it permanent. Lucas: Exactly. The goal isn't to be rude or unresponsive. It's to reclaim the cognitive space that lets you do your best work. And that's not just good for you — it's good for your employer too. Luna: We've talked a lot about the mechanics of boundaries on this show — hard stops, time audits, energy maps. But this one feels like the most foundational, because it's about the basic rhythm of your day. Lucas: Yeah. If you can't protect your attention, none of the other boundaries matter very much. Luna: And I think that's a good note to land on. But before we wrap, Lucas, I want to mention something quickly. If this episode helped you think about your own email habits — or if any episode from this show has ever made a difference in how you approach your career — there's a simple way to support what we do here. Lucas: Yeah, and it's genuinely small. If today's conversation was worth the price of a coffee to you, you can find us at buy me a coffee dot com slash fexingo. That's buy me a coffee, dot com, slash fexingo. It's what keeps this show ad-free and independent. Luna: No pressure at all. Seriously. We're just grateful you listen. And we'll be back next week with another real conversation about work. Lucas: Alright, let's leave it here. The challenge this week: pick one day where you batch your email into two windows and see what happens. Even just one day. Report back to us if you want — we'd love to hear how it goes.