The client had a perfect system. And still no day of his own.

I regularly sit across from someone whose method is flawless. Project list maintained, contexts clean, weekly review every Friday. And still the same sentence: “I just never get to my own things.”

So we look at an ordinary Tuesday together. Almost always it goes like this: computer on, mail client open, and from there it is one after the next. One mail, one reply, the next mail. Something pops in that looks urgent, so deal with it now. By half past eleven the morning is gone and the client has not opened his own project list once that day.

The system is not the problem. On that day the system simply is not used.

Processing and working are two different modes

When you process, you decide. What is this, do I have to do something, and if so what exactly is the next physical action. That is thinking work at a rapid pace, many small decisions one after another.

When you work, you execute. One thing, a longer stretch, concentration.

These two modes demand completely different things of your head. Mix them and you do both badly. You decide sloppily, because you keep tipping over into execution, and you work without focus, because the next mail is waiting in the background. That is why a morning in the inbox feels like work and, by the evening, feels like nothing.

What David Allen means by Clarify is not “get through your mail”. It is “decide what this stuff means”. Doing comes later, in a different block, off a list.

Separate the two and you are not working harder. You have just stopped switching modes twenty times a day.

Why the inbox does not work as a task list

The inbox is sorted by arrival time. Your priorities are not.

On top of that: a mail never shows you the next action, it shows you a topic. Between “Quote for Miller” and what actually needs doing lies a decision that you make afresh every time you look at it. With one mail that does not matter. With eighty unread you make that decision eighty times without ever recording it. That is what makes you tired by the evening.

And the most expensive effect: whatever sits in the inbox appears on none of your lists. You now have two competing systems, and from that moment your head trusts neither.

The daily review: ten minutes before the day owns you

The weekly review stays the centrepiece, nothing changes there. The daily look is something else: not system maintenance but taking your bearings. It answers a single question. What does today realistically look like.

The calendar first. What are the hard edges, meaning the appointments I cannot move. How much free time is actually left. For most people that is the moment of sobering up: there are not six hours between the meetings, there are two.

Then the next-actions lists. Not all of them, only the contexts that come up today. What fits into those two hours.

Then the waiting-for list. The one place where something tips over daily. Something open for ten days becomes a phone call today.

Only after that, the inbox.

That takes ten minutes if your system is in order. If it takes longer, you do not have a daily-review problem, you have a weekly-review problem.

On the “five priorities for today”

A short daily list contradicts the pure doctrine. GTD has no daily to-do list, because it forces a decision in advance that can already be wrong by eleven.

It still works for a lot of people, and I recommend it when I see that someone stalls every morning under the weight of options. The condition is that the list comes off the context list and does not become a parallel system. And that three items are enough when the day only offers two free hours. Five items on a day with six meetings is not prioritising, it is self-deception with the character of a calendar.

What actually happens when you process

Two fixed blocks, for me late morning and early afternoon. In these blocks nothing gets worked on, things get sorted:

• Rubbish goes out
• Pure information gets archived, without folder archaeology, search will find it again
• If something needs doing: the next action gets phrased, goes onto the right list, and the mail moves to the archive
• If somebody else is up: out it goes, and onto waiting-for

The step where this fails is always the same. The next action does not get phrased, it only gets vaguely thought. “Quote for Miller” is not a next action. “Pull Miller’s costing out of the sheet and transfer it into the template” is. The difference costs twenty seconds when processing and saves five minutes of run-up when working. At fifteen mails a day, that is the whole effect.

The two-minute rule is the biggest trap in mail processing. Two minutes means two minutes, not “that will be quick”. I constantly see people write three replies inside a processing block, twelve minutes each, and then the block is over and the inbox is still half full. If you are unsure about a mail: it will take longer than two minutes.

When the inbox is done, it gets closed. Not minimised. Closed.

Expectations are negotiable, you just never negotiate

Almost everyone who believes they must reply within minutes has never discussed it with anybody. They trained themselves into it and then assume everyone else expects it.

The announcement is unspectacular: “I check mail twice a day. If it’s urgent, call me.” One line in the signature, said once in the team. In twenty years nobody has ever held it against me. What bothers people is not an answer after six hours, it is no answer and no idea where they stand.

One side effect that rarely gets mentioned: as soon as the phone is the escalation route, the number of urgent things drops noticeably. Calling costs the sender something. Marking a mail as high priority costs nothing.

Where it typically fails

The blocks are not in the calendar. A processing block that is only an intention does not happen on a full day.

The notifications keep running. If you set aside time twice a day to process and then glance over at every ping in between, you have gained nothing. The block replaces the interruption, it does not come on top of it.

The weekly review gets skipped and the daily review is supposed to cover for it. That goes wrong. The daily look only works when the lists are right, and Friday is what keeps them right.

The first block sits too early. Put your best hours of concentration into processing and you have the same order as before, just with a better name. For me the first real working session comes before the first mail block. Not possible for everyone, but check it honestly before you rule it out.

Common questions

What is the difference between processing email and working email?

When processing, you only decide what a message means and what the next action would be, and you record that on a list. When working it, you execute the tasks straight from the inbox. The first mode takes seconds per mail, the second consumes your morning.

How long should a daily review take?

Ten minutes with a maintained system. It covers the calendar, the next-actions lists relevant today, and the waiting-for list. If it regularly takes longer, the weekly review is missing.

How often should I check email?

Two fixed blocks a day are enough in most roles. What matters is not the number but that no notifications run between the blocks and the inbox stays closed.

Does the daily review replace the weekly review?

No. The daily look orients you inside a system that the weekly review keeps current. Without Friday you are looking at stale lists every day.

---

Where does your first glance land in the morning, the calendar or the inbox? And if it is the inbox: what would have to happen for that to be different next week?