Emails: Take Back Control of Your Inbox

The inbox, time thief number one

When Marc timed his week in chapter 5, one line dominated all the others: email. An hour and fifteen minutes a day on average, more than six hours a week — more than monitoring, minutes and spreadsheet cleanup combined. And that figure only measures the visible time: it doesn't count the interruptions. Every notification that pulls him out of a client file costs him several minutes of refocusing. Email isn't just time-consuming, it's fragmenting: it shreds the day into confetti.

The real problem isn't the volume, though — it's the processing mode. Marc reads his emails as they come, in order of arrival, replying on the spot to whatever seems pressing. The result: noisy messages get ahead of important ones, replies are written one by one as if each were unique, and complex threads are reread three times before he dares answer. It's exactly the kind of process the previous chapters taught you to spot: frequent, time-consuming, with stable steps — a perfect candidate.

Mind an important distinction: this chapter doesn't overlap with chapter 3. There, you learned to write delicate emails — a price increase announcement, a sensitive follow-up, an unhappy client — one by one, with their relationship stakes. Here, we're tackling the daily flow: the dozens of ordinary messages that, added up, devour your mornings. The logic is different: we're no longer chasing the perfection of one email, we're chasing the efficiency of a system.

Sorting in batches: the inbox review

First reflex to change: stop processing your emails one by one — process them in batches. Copy the list of your unread messages — sender, subject, first line are enough — and ask for a classification into four categories: handle today, schedule this week, delegate or forward, archive without reply. In thirty seconds you get a battle plan, where visually scanning 94 messages used to take twenty anxiety-inducing minutes.

The strength of this assisted triage is that it applies your rules, not generic ones. In your brief, specify who your priority senders are (clients with active engagements, the tax administration, your business partner), what counts as an emergency in your line of work (a filing deadline, a bank request, an audit) and what never does (newsletters, inbound prospecting). As always since chapter 1: the more precise the context, the more the classification looks like you.

You are my email triage assistant. Context: I run a 4-person accounting firm, clients are tradespeople. Always priority: clients with active engagements, the tax and social administration, my bank, my business partner. Never urgent: newsletters, prospecting, tool notifications.
Here is my list of unread messages (sender — subject — first line): <paste the list>.
Classify them into 4 categories:
1. Handle today (with a one-line reply suggestion)
2. Schedule this week
3. Delegate or forward (to whom, why)
4. Archive without reply
End with the 3 messages you would handle first in my place, with your reasoning.

flowchart TD
  B["Inbox: 94 unread"] --> T["Assisted batch triage"]
  T --> A["Handle today"]
  T --> P["Schedule this week"]
  T --> D["Delegate or forward"]
  T --> X["Archive without reply"]
  A --> R["Personalized canned replies"]
  R --> V["Human review then send"]

Canned replies that stay human

Once the triage is done, look at the "handle today" queue: in Marc's firm, 60 to 70% of these messages call for a reply he has already written a hundred times in barely different forms. "Which documents should I send you?", "Can you confirm the deadline?", "Where does my file stand?". The classic trap is the frozen canned replies of email software: everyone recognizes them, they smell like a robot, and they erode the relationship over time.

The assisted method is different: you build a bank of skeletons — the structure and substance of each recurring reply — and you let the personalization happen on the fly, based on the message received. The skeleton guarantees the accuracy of the substance (the right list of documents, the right procedure); the generation adapts the tone, picks up the client's words, mentions their context. It's the template-by-example technique from chapter 3, applied to your daily correspondence.

Here are 6 replies I regularly send my clients (copied from my sent messages): <paste the 6 emails>.
Analyze them and build my bank of canned replies:
1. Identify the recurring situations (document request, deadline question, file status update, etc.)
2. For each, extract a reusable skeleton: structure, essential information, opening and closing phrases that sound like me
3. Number each skeleton so I can later tell you "reply with skeleton 3"
Keep my tone: courteous, direct, no unnecessary accounting jargon.

In daily use, it becomes: "Here is the message from the client Atelier Bernard: . Reply with skeleton 2, mentioning that his VAT file is already up to date and only the March invoices are missing." Ten seconds of brief, a personalized reply, a quick review — the email goes out in under a minute instead of five. Multiplied by thirty replies a day across the team, the chapter 5 math applies all by itself.

Taming endless threads

Your inbox's worst enemy isn't the isolated message, it's the thread: 23 messages about the software migration, five participants, decisions made at message 9 then contradicted at message 17, and you having to reply without the courage to reread it all. The usual outcome: you postpone, the thread grows, and the final answer arrives late and off-target. This is precisely a synthesis job — chapter 2 territory, applied to your correspondence.

Paste the full thread and ask for three things: a chronological summary of the decisions, the list of still-open questions, and — the most useful — what the others expect from you precisely. You can follow up with the drafting of a reply that closes out the thread: it recaps what's settled, decides what can be decided, and clearly states the two remaining questions. A good synthesis email kills a 23-message thread; it's a service you render to everyone.

Here is a 23-message email thread about migrating our invoicing software: <paste the thread, oldest to newest>.
Save me time:
1. Summarize the chronology in 5 bullets maximum: what was decided, what changed along the way
2. List the still-open questions and who is supposed to answer them
3. Tell me precisely what is expected of me in this thread
4. Draft a reply that closes out the thread: what is settled, what I'm deciding, the 2 remaining questions with an owner and a deadline for each
Tone: constructive and decisive, 150 words max for the reply.

The 20-minute routine

The bricks are there; what remains is assembling them into a routine, otherwise you'll fall back into the as-it-comes flow within two weeks. Marc's recipe: two fixed slots a day, 9 a.m. and 4 p.m., twenty minutes each, notifications off the rest of the time. The slot's run sheet: five minutes of batch triage, ten minutes of replies in series with the skeleton bank, five minutes for the threads to close out. Delicate emails — the chapter 3 ones — leave the routine: they're scheduled as real tasks, with the thinking time they deserve.

After a month of this discipline, Marc's numbers are clear: from 75 minutes a day to about 35, and above all entire mornings without interruption — his deep work has found room again. The most unexpected effect is relational: his replies go out faster and more complete than before, because they're processed in series with method instead of being dashed off between two doors. Processing better and processing for less time aren't contradictory: they're the same motion.

The pitfalls of assisted email

First pitfall: over-automating sensitive messages. An angry client, a mistake by the firm, a contractual matter — those emails never go through the skeleton bank; they belong to chapter 3, with explicit relationship stakes and tone variants. Second pitfall: uniformity. If all your clients receive cookie-cutter replies, the surface-level personalization will eventually show; regularly feed your bank with new real examples so it stays alive. Third pitfall: making "inbox zero" a goal in itself. The objective isn't an empty inbox, it's time returned to your real job — if you're spending twenty minutes triaging newsletters, unsubscribe; don't delegate the sorting of what shouldn't exist.

One last deployment tip: file your triage brief and your skeleton bank in the chapter 5 workflow library, dated and versioned. The inbox review is probably the workflow your team will run most often — 250 times a year per person. It's also the one where every checklist improvement pays off fastest.