The four ideas this whole blog is built on
Everything here comes back to these four topics. They're written in more depth than the homepage summaries, including the reasoning and the edge cases where the advice needs adjusting.
The two-minute rule that actually works
The original version of this rule, borrowed from general productivity advice, says that if a task takes under two minutes, you do it immediately instead of adding it to a list. Applied word-for-word to email, it causes problems. Treated as gospel, it means you stop whatever you're doing every time a short message lands, which is exactly the behaviour that keeps people glued to their inbox all day.
The version that holds up under real volume works differently. You still open and read the message when it's convenient, not the instant it arrives. Once you're reading, the two-minute question applies to the reply itself: can you answer, forward, or file it in under two minutes without needing to think, check something, or write more than three or four sentences? If yes, do it right then, during your scheduled email session. If it needs research, a decision, or more than a short paragraph, it goes into your real work queue instead of sitting half-answered in your head.
The distinction matters because most inbox anxiety comes from emails that feel small but aren't. "Quick question" often isn't quick. Running the two-minute test honestly, rather than optimistically, is what keeps the rule useful instead of becoming another source of interruption.
Why folders are mostly useless, and search is your friend
Folder systems were designed for a filing cabinet metaphor: physical space is limited, so you sort things to make room and to know where to look later. Email doesn't have that limitation. Storage is effectively unlimited for most business accounts, and modern search indexes the full content of a message, not just its subject line.
That changes the maths. Filing an email into a folder costs you a decision now, based on incomplete information about how you'll need to find it later. Search costs you nothing now and lets you find the message later using whatever detail you happen to remember, whether that's a sender's name, a phrase from the body, or roughly when it arrived. In practice, people rarely search using the category they'd have filed something under anyway.
There are exceptions worth keeping. A small number of top-level folders for things with a legal or compliance shelf life, such as signed contracts or tax correspondence, can be worth the manual effort because they're accessed differently, often by other people, and need to be browsable rather than searchable. Outside of that narrow case, the general habit worth building is: read, act if needed, archive. Stop inventing categories for messages that search will find for you in under two seconds.
How to write subject lines that get responses
A subject line does one job: it lets the reader decide, without opening the email, how urgent and how effortful the message is. Most subject lines fail at this because they describe the topic instead of the ask. "Project update" tells the reader what the email is about. It doesn't tell them whether they need to reply today or can leave it until Friday.
A more useful structure puts the action or the deadline first, then the topic. "Need sign-off by Thursday: venue contract" does more work than "Venue contract" ever will. If there's no action required at all, saying so removes any doubt: "FYI, no reply needed: updated pricing sheet." That single phrase can save a reader from opening, re-reading, and mentally flagging a message that never needed a response in the first place.
Two smaller habits help this land consistently. Keep the subject specific enough that it still makes sense a month later in a search result, rather than a generic phrase repeated across many threads. And update the subject line when the topic of a long thread shifts, rather than letting "Re: Re: Re: Quick question" drift three topics away from where it started.
Setting expectations about reply times without being rude
Instant replies train people to expect instant replies. That's not a criticism, it's just cause and effect. If you answer every email within minutes for a month, a slower response later can read as a problem even when nothing has actually changed on your end.
The alternative isn't to reply more slowly and say nothing about it. It's to state a normal response window plainly, once, in places people will see it: an email signature line such as "I check email twice daily, mornings and late afternoon," or a short note in a first reply to a new contact. This reads as organised rather than unavailable, because it gives the other person a concrete expectation instead of silence to interpret.
When a specific message needs a longer gap than usual, a short acknowledgment does more good than an eventual, delayed full reply. "Got this, will have a proper answer by Wednesday" takes fifteen seconds to send and removes the guesswork entirely. It also tends to prevent the follow-up chase email, which is often what turns one message into three.
How the four ideas work together
Triage tells you what kind of email you're looking at. Search removes the need to file it anywhere once you've dealt with it. A clear subject line means fewer messages need triage in the first place, because the sender has already told you what's needed. And a stated reply-time expectation means a slower response doesn't need to be individually explained, apologised for, or chased. None of these four ideas depend on the others to be useful on their own, but used together they tend to compound.