How to triage your inbox in 15 minutes

The average worker already gets 117 emails a day, and most of them don’t need fifteen minutes of your attention. They need about two seconds, sorted correctly. Triage means deciding what deserves an answer at all, before you start typing.

Run these five steps in order. Skipping the order is the most common way this breaks. If you answer before you sort, you spend your first ten minutes on whatever landed at the top. The messages that matter wait.

Sort before you read

Open the inbox and scan subject lines and senders only. Don’t open a single message yet. Build a mental map of three things: what’s clearly junk, what’s clearly urgent, and everything else.

Say your inbox has forty new messages. A newsletter, three calendar notifications, a client asking about an invoice, and a coworker’s one-word “thanks!” are all identifiable from the subject line alone. You don’t need to open any of them to know roughly where they belong. This first pass usually takes under a minute for forty messages, because you’re matching patterns instead of reading.

Kill the two-second no

Now go back through and deal with everything that needs no reply and leaves no record worth keeping: newsletters you skim, automated notifications, the “thanks!” that doesn’t need a response. Archive it or delete it the instant you see it.

The test is simple. If nobody would notice you never opened this message, don’t open it. A shipping confirmation for an order you already know is coming is a two-second no. So is a calendar reminder for a meeting you’re already planning to attend.

Answer what takes under two minutes

For everything left, ask whether a full reply takes under two minutes to write. If it does, write it now. A colleague asking “are we still on for 3pm?” gets a one-line “yes” immediately, before it turns into a mental note to answer later.

This is the step people skip, because it feels like it interrupts triage with actual work. It doesn’t. A two-minute reply written now costs you two minutes. The same reply, revisited after you’ve lost the thread’s context, usually costs five, because you have to re-read it first.

Batch what’s left into three piles

Sort whatever remains into exactly three piles: needs a real reply, needs a decision, and needs someone else. A detailed question from a client that needs a considered answer goes in the first pile. A vendor proposal that needs you to choose between two options goes in the second. A request that belongs to your teammate goes in the third, forwarded immediately.

Keep the limit at three piles. With more categories, you spend your fifteen minutes deciding which pile something belongs in, and the inbox stays full.

Set the next look, then stop

Decide when you’re checking email again, out loud or in writing, and close the tab. This step makes the other four worth doing. Without it, you re-scan the piles an hour later out of habit, and that erases the time you just saved.

“Back to this at 1pm” is enough. You don’t need a perfect schedule, just one specific enough that an early check feels like a choice you made on purpose.

Where this breaks

This method assumes you control when you check email. That isn’t true for every job. If you’re expected to respond within minutes during working hours, shrink the “set the next look” step to about thirty minutes. Don’t drop it, or the rest of the method stops applying to you.

It also assumes a single inbox. Your two-minute replies and your real-reply pile might sit across email, a chat tool and a ticket queue. If so, sorting each one separately eats the time this method saves. The method still works per inbox. It just doesn’t automatically merge across them.