Getting to the bottom of the inbox
The short version
- The messages left unanswered are usually not the boring ones. They are the ones that need a decision, and the ones where the reply has consequences.
- After a while the pile stops being a list of tasks and becomes a single object you feel rather than read, which is why looking at it is harder than doing it.
- The part that actually changes this belongs to the team: agreeing what an email requires, what a response time means, and which channel is for what.
Forty unread. You open it, deal with the room booking and the calendar invitation and the one that needed the word "yes", and close it. Thirty-seven unread, and the three still sitting there are the three that mattered. Tomorrow it will be forty-four.
Why the hard ones are the ones left
An email is a container, and what is inside might be four words or half a day. Nothing outside tells you which. The room booking has a known cost and a known ending. The one asking what you think about the restructure means taking a position on the record.
So the reply gets postponed until you have time to do it properly, and that time never arrives as a labelled block. Meanwhile the message ages, and an aged message is worse to answer, because the reply now has to account for the delay as well as the question. The cost goes up daily, which is the opposite of how most tasks behave.
The pile stops being a list
Past a certain size, an inbox is no longer information. You do not read it, you register it — a quantity of unfinished obligation, with two or three dreaded items near the surface and the rest fused into a mass. That is why "spend twenty minutes on it" often fails: twenty minutes is a proposal about a list, and this is not experienced as a list. Turning it back into one comes before answering anything.
Mechanics that work
Separate deciding from answering. Label only: two minutes, needs a real answer, not mine, dead. Reply to nothing while you do it. Mixing the two is why the pass never finishes.
Two minutes means two minutes. The two-minute rule comes from David Allen's Getting Things Done — a useful heuristic rather than a research finding, and it only works if you are honest about what qualifies.
The real answers go in the calendar, not the inbox. Three of them, with a time. An email needing forty minutes of thought is work, and work that lives only in an inbox does not get done.
Send the holding reply. Got this, thinking about it, will come back Thursday. Ten seconds, and it removes the ageing problem — the other person has a date, and you no longer owe an apology alongside the answer.
Take the notifications off. Every arrival that pulls you out of something has a cost you pay on the way back in.
Where the delay costs and where it pays
The cost lands on other people first. Someone is blocked on your answer and cannot say so without sounding like a complaint, so they wait, then chase, then work round you — and being worked round is how a person quietly stops being consulted. It costs you too: the reply you send in week three is worse than the one you would have sent in week one, because it carries an explanation for the silence.
The delay is also doing something useful. A number of hard emails answer themselves, get overtaken, or turn out to have been someone thinking out loud, and some of what looks like avoidance is an accurate reading that the message did not yet have an answer in it. What separates the two cases is whether anyone is waiting. A reply nobody is blocked on can sit a week at almost no cost. A reply someone needs before they can start is not an email, it is a handover.
What the team can change
This is the substantive adjustment, and it does not belong to the reader.
Say what the message requires. A subject line convention: for information, needs a decision by Friday, action: yours. The sender always knows which it is; the recipient has to work it out one message at a time.
Agree what a response time means. Most teams have never said, so one person believes same-day is the standard and another believes two days, and both are anxious. Write it down, including that there is no expectation outside working hours.
Decide which channel is for what. Where chat, email and the ticket system all carry every kind of message, everyone has to watch everything. Email for things needing a considered answer, chat for things needing a fast one, and decisions written somewhere findable by people who were not on the thread.
Small things to try this week
- Do one labelling pass with no replying. Ten minutes, four labels, nothing sent.
- Send three holding replies today, to the three you are most avoiding.
- Raise the response-time question once in a team meeting: what do we actually expect? The answers will not match, and that is the point.
If the inbox refills to the same place after a few weeks, that is worth knowing. It usually means the volume and the expectations are structural rather than personal, which makes it a conversation for the team rather than a habit to correct alone.
Written for Thought Club as general guidance, not medical advice. Free to read, print, and share.