Key takeaways
- Inbox zero is about how much of your attention the inbox holds, not how many messages are in it; Mann's series began in 2006 and the Google talk was in July 2007.
- Every message gets one of five actions, delete, delegate, respond, defer or do, and processing happens in short sessions, not all day.
- Checking three times a day lowered stress in a randomised trial; batching only helps if each session is short.
- Filters that skip the inbox, three labels, and dated deferrals get you there in Gmail or Outlook; fixed sessions and a reviewed Waiting list keep you there.
Inbox zero has been misread for nearly twenty years as an empty folder. It was never that. It is a way of processing email so that the inbox stops holding your attention between sessions. Here is what Merlin Mann actually meant, the five actions that make it work, what the research says about whether it is worth it, and a step-by-step for Gmail and Outlook that gets you there and keeps you there.
What does inbox zero actually mean?
Merlin Mann coined the term on his site 43 Folders, where the Inbox Zero series began in March 2006, and gave the talk that made it famous at Google's Mountain View campus on 23 July 2007, a 58-minute presentation that Google let him publish as video and audio. The zero was never the number of messages. In Mann's framing, it is how much of your own brain is in that inbox, especially when you do not want it to be.
So an inbox with thirty threads that are all waiting on other people is at zero, and an empty inbox you reached by archiving everything unread is not. The test is whether, when you close the tab, anything in there is still pulling at you. The method is a way of processing, done in short sessions, so that the answer is no.
The size of the problem it solves is in how much time we spend on email: around a quarter of the working week, most of it not reading but deciding, drafting and chasing.
The five actions: delete, delegate, respond, defer, do
Mann's own early posts listed the options as delete, archive, defer, generate an action, or respond immediately if it takes under two minutes, with delete first because half or more of what arrives should not survive the first question. The five-verb version that the talk is usually summarised as is the same idea with sharper edges. Every message gets exactly one of them, in order:
- Delete (or archive). Newsletters you did not read, notifications, receipts you have filed. Most mail. Decide in a second and move on.
- Delegate. It is someone else's. Forward it with one line saying what you need and by when, then archive it and track the ask, not the message.
- Respond. If the reply takes under two minutes, write it now. Short answers sent immediately beat long answers drafted later.
- Defer. If it needs more than two minutes, it is a task. Put it on the task list with a date, archive the message, and come back to it in a work block, not an inbox session.
- Do. If the message is itself the task and takes under two minutes, do it: approve the thing, book the slot, pay the invoice.
| Action | Rule of thumb | Where the message goes | What you keep |
|---|---|---|---|
| Delete / archive | No reply, no task | Archive or bin | Nothing |
| Delegate | Someone else owns it | Forwarded, then archived | A follow-up on the person, dated |
| Respond | Under two minutes | Replied, then archived | Nothing, unless you need their answer |
| Defer | Over two minutes | Archived with a label or flag | A task with a date |
| Do | The email is the task, under two minutes | Archived once done | Nothing |
The thing that makes it work is that processing is a separate phase from reading and from working. You do not process while you write code, and you do not write code while you process. Mann's suggestion was to firewall processing into short sessions no more than every hour or two; the research since points to fewer.
Does inbox zero work? What the research says
Three studies answer different halves of the question. Mark, Gudith and Klocke found that interrupted work was done faster but with more stress and higher workload; the widely cited figure from Mark's field work is about 23 minutes to return fully to a task after an interruption. An inbox that is open all day is an interruption generator, and processing in sessions removes it.
Kushlev and Dunn then ran the experiment: 124 adults, one week limited to checking three times a day, one week free. Stress was significantly lower in the limited week. That is the "sessions, not a feed" half of inbox zero, with a randomised trial behind it.
The caveat comes from Mark and colleagues in 2016: in 40 information workers logged over 12 workdays, batching went with higher rated productivity, but there was no evidence that batching by itself lowered stress. Stress tracked total daily time in email. So inbox zero works when the sessions are short, which means the deciding has to be fast and the drafting and chasing mostly done before the session starts. The full picture is in how often you should check email.
How to get to inbox zero in Gmail
- Declare bankruptcy on the backlog, once. Select everything older than two weeks and archive it. It is still searchable. Nothing older than two weeks that mattered is waiting for you in the inbox; it is waiting in someone's follow-up, which is their problem or a task you already have.
- Turn off the inbox categories you do not read and instead build filters. In the search box, open the search options, enter a sender or a phrase such as "unsubscribe", and choose "Create filter". Tick "Skip the Inbox" and apply a label such as Newsletters. Do the same for notifications from tools, for receipts, and for any automated sender.
- Make three labels that match the actions: Waiting for threads you delegated or asked something in, Deferred for tasks over two minutes, and Read later for things that are neither. Archive the message when you label it; the label is the list, the inbox is not.
- Use "Snooze" sparingly and only with a date you chose for a reason. A snoozed message is a deferred decision, and a hundred of them is an inbox again.
- Process in sessions. Two or three a day, each one top to bottom, each message gets one of the five actions, and the session ends when the inbox is empty or the time box is up.
How to get to inbox zero in Outlook
- Archive the backlog. Sort by date, select everything older than two weeks, and move it to Archive. Search still finds it.
- Use Focused Inbox as the first filter and teach it: right-click a message and move it to Other, and Outlook learns the sender. Then add rules for the senders Focused gets wrong: from the message, choose Rules, "Create rule", and move mail from that sender, or with a word in the subject, to a Newsletters or Notifications folder.
- Create the three folders or categories: Waiting, Deferred, Read later. Categories are better than folders in Outlook because a message can carry one and still be found in Archive.
- Flag with a date, not just a flag. An undated flag is a wish. A flagged message with a due date appears in To Do, which is where deferred items belong.
- Turn off the desktop alert and the badge. Notifications are the opposite of sessions. Then process two or three times a day, top to bottom, one action per message.
The same five actions apply whichever client you use. The filters just reduce how many messages reach the session, which is what keeps the session short.
How to stay at inbox zero
Getting there takes an afternoon. Staying there is a set of habits, and the habits are what most guides skip.
- Fixed sessions, notifications off. Two or three a day, in the calendar. The randomised evidence is for three. Outside the sessions, the tab is closed, not minimised.
- One action per message, always. The failure mode is "I'll come back to this", which is a sixth action called "leave it in the inbox", and it is the one that undoes everything.
- A Waiting list you actually review. Once a week, go through the threads waiting on others and chase them. Or let a follow-up sequence do the chasing on day 3, 7 and 14 so the Waiting list empties itself.
- Drafts before the session. If every reply has to be written from scratch, a session of twenty threads is an hour and the discipline breaks by Wednesday. A template, a snippet or an assistant that drafts in your voice turns that into fifteen minutes of editing. Which assistants do that, and for which mailbox, is in the comparison of AI email assistants.
- Fewer decisions, decided once. The filters, the labels and the session times are decisions you made once so that you never make them again. It is the same logic as a work uniform, covered in why a uniform works: remove the recurring small decisions and the attention goes to the large ones.
| Habit | Frequency | Time |
|---|---|---|
| Processing session, one action per message | 2-3 times a day | 10-20 minutes each |
| Review the Waiting list and chase | Weekly | 15 minutes |
| Add a filter for a new automated sender | As they appear | 30 seconds |
| Re-archive the backlog if it slips | Whenever it is over fifty | 5 minutes |
How PeakLook keeps the inbox decided
PeakLook does the two things that make the sessions short. Between sessions, its drafter scans the Focused inbox in Microsoft 365, skips the newsletters, and saves a Reply-All draft threaded into every conversation that needs one, so "respond" becomes editing rather than writing.
And the Waiting list stops being a list you review: enrol a thread in a sequence and the follow-ups go out from the server on day 3, 7 and 14, in your voice, stopping the moment the other person replies. Anything the machine wrote or will send is shown in gold, so the inbox stays yours to decide.
Want this answered from your own data?
That is what PeakLook does. Drafts the reply. Keeps the follow-up going. In private beta — the waitlist is free.
Questions
What is the inbox zero method?
How do I achieve inbox zero in Gmail?
Is inbox zero actually worth it?
How many times a day should I check email for inbox zero?
What is the difference between archiving and deleting?
What do I do with emails I am waiting on?
Sources
- Mann M. 43 Folders series: Inbox Zero (2006-2007). https://www.43folders.com/43-folders-series-inbox-zero
- Mann M. (2007). Video for Merlin's "Inbox Zero" talk at Google, 23 July 2007. 43 Folders. http://www.43folders.com/2007/07/25/merlins-inbox-zero-talk
- Mark G., Gudith D., Klocke U. (2008). The cost of interrupted work: more speed and stress. CHI. https://www.ics.uci.edu/~gmark/chi08-mark.pdf
- Kushlev K., Dunn E.W. (2015). Checking email less frequently reduces stress. Comput Human Behav. https://www.sciencedirect.com/science/article/abs/pii/S0747563214005810
- Mark G., Iqbal S., Czerwinski M., Johns P., Sano A. (2016). Email duration, batching and self-interruption: patterns of email use on productivity and stress. CHI. https://www.microsoft.com/en-us/research/publication/email-duration-batching-and-self-interruption-patterns-of-email-use-on-productivity-and-stress/
- McKinsey Global Institute (2012). The social economy: unlocking value and productivity through social technologies. https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy