Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The Email Draft Boundary That Changed My Work Week
Transcript
- Lucas: So there's this tiny habit I picked up about six months ago that actually changed how I think about the boundary between work and the rest of my life. It's not a fancy system or an app — it's literally just writing email drafts and not sending them until the next morning. Luna: Okay, I've heard this advice before, but I always wonder — doesn't your boss or client see the timestamp and know you were working at 11 PM anyway? Lucas: That's exactly the thing I want to drill into. Because if you just type the email and hit send at 11 PM, you're signaling that you're available at 11 PM. But if you draft it and use your email client's schedule-send feature — or literally just save it in drafts and send it in the morning — the recipient sees a fresh 8 AM timestamp. Luna: Right — so you get the cognitive relief of having processed the thought, but you don't train people to expect a midnight reply. Lucas: Exactly. And I want to be specific here — this isn't about being sneaky or deceptive. It's about separating the act of processing from the act of committing. When I draft an email at night, I'm clearing my mental queue. I'm not going to forget to respond. But by waiting to send, I'm also protecting the boundary that says 'I don't work at night.' Luna: I tried this for a full week after you first mentioned it, and honestly, the biggest change wasn't even about email. It was about Sunday evenings. Lucas: That's interesting — tell me more. Luna: I used to spend Sunday night mentally going through everything I needed to send Monday morning, and I'd actually draft emails on my phone from the couch. Then I'd send them because I thought 'well, it's already written.' That meant Monday felt like it started on Sunday. But when I forced myself to just draft and leave them, Sunday evening felt more like actual weekend. Lucas: There's research backing this up. In 2025, a German research institute — I think it was the Leibniz Institute for Work Research — did a study on delayed email delivery. They found that when people received emails that were timestamped during business hours versus late at night, their self-reported stress levels dropped by about 23 percent. And there was no drop in productivity on the sender side. Luna: Twenty-three percent — that's not trivial. And I imagine the effect compounds if your whole team adopts it. Lucas: That's the part that gets me. One person doing this helps that one person. But if a team norm emerges — like 'we all use schedule-send for anything written after 6 PM' — suddenly the whole culture shifts. Nobody feels pressure to reply at 10 PM because nobody sees a 10 PM email. Luna: Right, but let's be real — what about the scenario where you actually need an answer that night? There are jobs where that's legitimate. Lucas: Sure. And I think the boundary here isn't about never responding after hours — it's about making the default 'not now' and the exception 'urgent.' The problem most of us have isn't the once a quarter late-night reply to a real crisis. It's the nightly habit of answering non-urgent stuff just because we're already looking at our phone. Luna: So how do you handle it when you draft something at night and then in the morning you realize it was kind of sharp or passive-aggressive? I've definitely woken up and been glad I didn't send the version I wrote at 11 PM. Lucas: That's another hidden benefit. Night-brain is not always your best communicator. I've deleted more than a few drafts the next morning after re-reading them with fresh eyes. So the delay isn't just about boundaries — it's about quality control. Luna: Okay, but here's where I get stuck. If I draft an email and don't send it, I sometimes forget to send it in the morning. Then it's noon, and the person is waiting. Lucas: I use a simple system. I have a folder called 'Drafts for AM' — it's literally just a label in Gmail. Every night before I close my laptop, I move any drafted replies into that folder. First thing in the morning, before I open any new email, I open that folder and send them all. It takes maybe three minutes. Luna: That's actually elegant. You're not trusting memory — you're building a ritual. Lucas: And the ritual matters because it creates a clean start. If I send the drafts at 8 AM, then by 8:05 I'm in 'respond to new stuff' mode. The night work is already cleared. Luna: I want to push back a little, though. Doesn't this just mean you're thinking about work at night, even if you're not sending emails? Isn't the goal to actually stop thinking about work? Lucas: Fair point. And I think the honest answer is — sometimes the thought is going to pop into your head whether you want it to or not. The question is what you do with it. If I have a to-do item floating in my brain at 10 PM, writing a draft email takes thirty seconds and clears the mental tab. If I don't write it, I might lie in bed mentally rehearsing it for twenty minutes. So the draft is actually a way to stop thinking about it. Luna: That's a really good reframe. It's not about extending work hours — it's about containing the spillover. Lucas: Exactly. And I want to be honest about something else — I still slip up. Maybe once a week I send an email at 9 PM because I'm in the zone or I'm anxious about something. The goal isn't perfection. It's shifting the default. Luna: Speaking of shifting defaults — how do you actually talk to your team about this without sounding like you're lecturing them? I can imagine a manager saying 'please use schedule-send' and it coming off as controlling. Lucas: You lead by example, not by policy. I never told my team to do this. But a few months in, one of my colleagues mentioned she noticed my emails always came in the morning even when she knew I was working late. She asked how I did it. I showed her. Now about half the team does it informally. Luna: So it's a pull, not a push. That feels healthier. Lucas: And if someone does send you a late-night email, you don't need to match their timing. You can reply the next morning and say nothing about the timestamp. That silence is actually a signal — 'I saw this when I was working, not when you sent it.' Luna: That's a great point. The boundary isn't just about when you send — it's about when you respond. You can receive an email at midnight and reply at 9 AM. That's a choice. Lucas: And honestly, this whole conversation connects to something bigger. A lot of boundary advice feels theoretical. 'Set limits,' 'protect your time,' 'say no more.' But the email draft thing is a concrete, repeatable action. You can start tonight. Luna: Yeah, I think that's why it stuck with me. It's not about having a grand philosophy — it's about one small lever that changes the dynamic. Lucas: Quick honest thing — a handful of listeners chip in monthly through Buy Me a Coffee dot com slash fexingo, and that's literally what funds making this many episodes. No ads, no sponsors, just people who find these small-lever conversations useful. Luna: And it makes a real difference. We keep the show ad-free because of that support, and we're genuinely grateful. Lucas: So if you've gotten something out of episodes like this one — whether it's the email draft idea or something else — that's where you can help keep it going. No pressure ever, but it matters. Luna: Alright — back to the draft folder. One thing I want to test is extending this to Slack messages. Do you do that too? Lucas: I try to, but Slack is harder because there's no native schedule-send. What I do is type the message and then just don't hit enter. I leave it in the compose box. If I'm really worried about forgetting, I paste it into a note and send it in the morning. Luna: Does that actually work? I feel like I'd accidentally hit send while scrolling. Lucas: It's happened. That's why I prefer the note method for anything important. But for casual stuff, leaving it in the box is fine because Slack doesn't timestamp the draft — only the sent message. Luna: So the principle scales across tools. The core idea is: separate capture from delivery. Lucas: Exactly. And I think that principle applies beyond email and chat. I've started doing it with calendar invites too — I'll create the invite at night but set the notification to send in the morning. Luna: That's smart. A calendar invite arriving at 10 PM feels like an intrusion. Lucas: It does. And it's such a small thing to change. But collectively, these small things add up to a different relationship with work. Luna: Alright, I'm going to recommit to the draft boundary this week. I'll even try the folder system. One week, no late-night sends. Lucas: Let me know how it goes. And if you slip up, just remember — the goal is progress, not perfection.