The inbox is not a to-do list. It is a collection of other people's priorities, delivered to you in the order they were sent, regardless of their importance to your actual work. Treating it as a to-do list means working on other people's priorities in the order they arrived, which is rarely the most useful way to spend a day.
The four-category system
When processing email, every message falls into one of four categories:
- Act now: Requires a response or action that takes less than two minutes. Do it immediately.
- Act later: Requires a response or action that takes more than two minutes. Add it to your actual to-do list with a specific time to address it. Move the email out of the inbox.
- Read later: Informational. No action required. File it or archive it. Read it when you have time, not because it is in your inbox.
- Delete: Not relevant. Not useful. Not worth keeping. Delete it.
The inbox zero myth
Inbox zero is a state, not a system. Achieving it by reading and responding to every email as it arrives is not a system — it is reactive email management that interrupts focused work every time a new message arrives.
A more useful goal is processing the inbox at scheduled times rather than continuously. Twice a day is enough for most roles. Once in the morning, once in the afternoon. Everything else can wait.
The notification problem
Email notifications interrupt focused work. Each interruption costs not just the time to read the notification but the time to re-engage with the work that was interrupted. Turning off email notifications and checking email at scheduled times is one of the highest-leverage productivity changes available.
Most people find that nothing urgent was missed. Most urgent things are not communicated by email.
The unread count
A large unread count is not a measure of importance. It is a measure of volume. An inbox with 847 unread emails contains some important messages and many that are not. The unread count does not distinguish between them. You have to.
The reframe: The inbox is a communication channel, not a task manager. Use it to receive and send messages. Use a separate system to track what you need to do. The two functions are different and work better when they are separated.