Email Triage Methods Compared: Seven Systems, Honestly Ranked

Every email triage method is really a theory about what email is. Get the theory right and the habits follow. Get it wrong and you’ll abandon the system inside a fortnight, like the last three you tried.

There are more named methods than most roundups admit, and they’re not all rivals. Some are decision rules, some are schedules, some are full workflows. Here are the seven you’ll actually encounter, who came up with each, and a verdict on which ones survive contact with a real inbox.

The 4 Ds: delete, do, delegate, defer

Microsoft has shipped this one in its Outlook best-practices guidance for years. For every message: delete it if it doesn’t matter, do it if it takes under two minutes, delegate it if it’s someone else’s, defer it otherwise. It’s essentially David Allen’s processing workflow filed down for corporate consumption, and as a reflex it’s fine.

The catch is that the 4 Ds are a decision rule, not a system. They tell you what to do with the message in your hand, and nothing about when to pick messages up or where “deferred” things live afterwards. In Outlook the official answer is flags and categories, which is where deferred email traditionally goes to die.

GTD and the two-minute rule

David Allen’s Getting Things Done treats email as an inbox of “stuff” to be clarified into next actions, projects and reference material. Its most portable idea is the two-minute rule: while you’re processing, anything that takes under two minutes gets done on the spot, because filing and tracking it would cost more than just doing it. Twenty years on, that rule is still the single best habit in all of email.

The full method is a harder sell. GTD wasn’t built for email and it shows: the canonical move is to get actions out of your inbox into a separate trusted system of lists and contexts. Now you’re maintaining two worlds and reconciling them. Most people manage it for a month, fall behind on the syncing, and quietly drop back to a messy inbox with a guilty task app on the side. If you already live in a task manager and love it, GTD works. Almost nobody else sustains it.

Inbox zero

Merlin Mann coined inbox zero on 43 Folders in 2006 and laid it out properly in his 2007 Google Tech Talk. His five verbs (delete, delegate, respond, defer, do) remain an excellent triage reflex. And the “zero”, he always insisted, meant zero attention spent worrying about your inbox, never zero messages. That nuance got lost almost immediately. Mann has spent years pointing out that the empty-inbox fetish was a misreading; he’s admitted his own inbox has never stayed empty.

As commonly practised, though, the method optimises for an empty list, a state you have to re-achieve every few hours. Worse, it has no home for “waiting on someone”: you reply, archive, and the thread vanishes into your sent folder along with the follow-up you owed it. We’ve written a longer teardown in why inbox zero is broken.

Yesterbox

Tony Hsieh, the late Zappos CEO, started experimenting with Yesterbox at the end of 2012. The premise: today’s to-do list is yesterday’s inbox. New mail is off limits except for deleting, filing or forwarding; you don’t reply to anything from today unless it genuinely can’t wait 48 hours. Yesterday’s inbox, by contrast, is finite. You know the count when you sit down, and there’s a real finish line.

That finite-list insight is genuinely clever, and it explains why the method has a devoted following. But look at the fine print: Hsieh blocked roughly three hours every morning for it and had an assistant defending that block. The 48-hour reply delay is a career-limiting move in most jobs. Yesterbox is a CEO’s system, built on a CEO’s calendar. Steal the finish-line idea; skip the rest.

Touch it once

Sometimes called OHIO (“only handle it once”), popularised by Robert Pozen in Extreme Productivity, with roots going back to paper-era time management. The rule: once you’ve opened a message, deal with it fully rather than re-reading it five times across the week.

As a nudge against inbox re-reading it’s sound. As an absolute it’s fantasy, because a huge share of email simply cannot be handled once. You reply and then wait on someone else, and no amount of discipline changes that. Touch-it-once has no answer for the waiting state, which happens to be exactly where email pain lives.

Timeboxed batching

Strictly speaking batching is a schedule rather than a triage method, but it earns its place as the only entry on this list with actual experimental evidence behind it. In a two-week field experiment, Kushlev and Dunn (2015) had 124 adults limit email checking to three times a day for one week and check as often as they liked the other. During the limited week, participants reported significantly lower daily stress, an effect the authors compared favourably with common relaxation techniques.

The mechanism is attention fragmentation: constant checking slices your day into confetti. Batching fixes the when of email and pairs with any of the other methods here. If you adopt one thing from this article, close the inbox and check it three times a day.

Kanban

Kanban treats each email as a small piece of work in a state (to do, doing, waiting, done) and gives every state a visible column you move messages through. It’s the same idea software teams borrowed from Toyota, applied to your inbox.

What it fixes is precisely what the others miss. There’s no second system to sync, unlike GTD, because the email is the card. There’s no empty-list treadmill, unlike inbox zero, because the board is correct whenever it reflects reality, regardless of message count. And “waiting” finally gets a column of its own instead of vanishing into the sent folder. The honest caveat: faked with labels or a Trello bolt-on, the seams show quickly. It wants a client that actually behaves like a board. Our kanban for email guide covers the setup in detail, and there’s a direct kanban vs inbox zero comparison if that’s the choice you’re weighing.

The verdict

Most of these aren’t systems so much as fragments of one. The two-minute rule is the best processing habit. Batching is the best schedule, and the only idea here with a controlled study behind it. Mann’s verbs and the 4 Ds are decent reflexes for the moment a message is in front of you. Yesterbox and touch-it-once each contain one good idea wrapped in constraints that don’t survive an ordinary job.

What none of the reflex methods provide is a place for work to live between decisions, and that’s the gap kanban fills. So the combination that actually holds: batch your checking, apply the two-minute rule while processing, and keep everything slower-moving on a board where its state stays visible.

If you’d rather not build that board out of labels and willpower, Kanmail is the native version: columns are your folders, every email a card, all your accounts in one view.