"You are there, but you are not here"

Knut, a fellow trainer and a guest in one of our sessions, heard that sentence from his wife years ago. At the dinner table, his son still small, himself physically present and mentally with unread mail and open project states.

That is the kind of feedback you cannot argue away. And it describes a problem that time management does not solve, because it is not a time problem.

Why your head keeps running in the evening

Your brain does not remind you of unfinished things because it wants to annoy you. It reminds you because it does not trust the place where the thing is supposed to be sitting. If a commitment is not captured cleanly anywhere, or if you have not looked at the system holding it for two weeks, your head takes the job on itself.

And it does not speak up during working hours, when you would be on it anyway. It speaks up when things go quiet. At dinner, in bed, on a walk with the children.

That is why mental absence in your private life is a symptom of a work system and not a question of mindfulness. You cannot decide to be present while forty open loops are running in the background.

The lever: separate deciding from doing

Knut’s approach reverses the usual order. He plans the next day the evening before, not in the morning.

It sounds like a small thing and it is not, because it solves four problems at once.

In the morning, the decision competes with the execution. Plan in the morning and you spend the clearest time of the day on a decision you could have made the night before. With the plan already standing, you start instead of choosing.

The evening has more information. At five o’clock you know what was left undone today, who has not got back to you, and what is realistic tomorrow. At eight in the morning you are reconstructing all of that.

Your head works on it overnight. If you know in the evening that you will write a particular concept tomorrow morning, you wake up with approaches to it. This is not an esoteric argument; anyone who has gone to bed with an open question knows it.

And the most important point: it is a line under the day. The working day gets an ending that consists of more than closing the laptop. What is due tomorrow is settled and therefore taken care of. That is precisely the condition for your head being free at dinner.

The third effect is the one Knut is after. The other three are by-catch.

What it looks like in practice

Five to ten minutes at the end of the working day:

• Look at tomorrow’s calendar. What is fixed, how much is left.
• Fix one to three tasks that genuinely have to happen tomorrow. The test is put harshly: if you do not do them tomorrow, you have a problem. Anything that description does not fit is a candidate, not a selection.
• Skim the waiting-for list. What has been open for more than a week and needs a call tomorrow.

Done. Laptop shut.

In the morning, the question of where to start simply disappears. You start. What pushes against the plan at that point usually comes from outside — more on that in saying no at work.

The cockpit: your software does not open where the requests are

The second part of Knut’s setup is a configuration hardly anyone makes, even though it takes five minutes.

His Outlook does not start in the inbox but in the calendar and task view. And it starts offline. Only once the one to three focus tasks are done does he go online.

The principle transfers to any tool. The opening view of your mail program decides what you see first, and what you see first determines what you think about first. If you work in a different program, you get the same effect through your browser start page, a different default tab, or simply by leaving the mail window closed in the morning.

The sentence behind it is the actual point: email is an asynchronous medium. It is built for sender and recipient not being present at the same time. Treat it synchronously and you have voluntarily set up a chat with an obligation to reply, using the worse tool for the job. How the inbox gets worked through afterwards is in process email instead of working it.

Friday, right after lunch

His weekly review sits on Friday afternoon, but deliberately straight after lunch and not at half past four.

The reasoning is unspectacular and therefore right: at half past four nobody has the energy left to resolve open ends. You skim, tick things off and go home. The review that actually does something requires the willingness to look at unpleasant projects and make decisions, and that willingness is still there in the early afternoon.

He describes the result as a holiday feeling. Friday evening does not start for him with a remainder in his head, but with a closed system.

That matches what I saw again and again in trainings: put your review too late and you lose it first in substance and then entirely. It does not fall away because there is no time, but because in the state you do it in, it achieves nothing — and you notice.

My own take

Two remarks, because at one point the model departs from the pure doctrine.

A fixed daily selection is not part of GTD, because it forces a pre-decision that can be obsolete by eleven o’clock. In practice it works anyway for people who otherwise lose themselves in options, under one condition: the selection comes out of the existing lists and does not become a second system alongside them.

And the number. One to three is considerably more realistic than the usual five or six, especially in a role with many meetings. Take on three things and finish two and you have had a good day. Take on six and finish two and you feel in the evening that you failed, at identical output.

Knut’s line on this, which I have been quoting ever since: it has to be stupidly simple so that it works in a storm. Any system that looks good on an ordinary Tuesday and collapses on a chaotic Thursday is too complicated.

Where it typically fails

• The evening review turns into a second work block. Answer three more mails in the evening and you have missed the line under the day and merely postponed the end of it. Five to ten minutes, then stop.
• The selection is made next to the system. A note with three items that exist nowhere else is a parallel system. Selecting means marking, not copying out.
• The focus tasks need more time than the day has. Three tasks on a day with six meetings is not planning. Look at the calendar first, then choose.
• The weekly review is missing. Without it you plan in the evening on the basis of lists that no longer hold, and your head notices faster than you do.

Common questions

Why should I plan my day the evening before?

Because you have more information in the evening, you no longer have to decide in the morning, and the working day gets a clear ending. That last point is the decisive one if work follows you mentally into the evening.

How long does evening planning take?

Five to ten minutes: tomorrow’s calendar, fix one to three focus tasks, skim the waiting-for list. Longer usually means you have started working again.

How many tasks should I fix for one day?

One to three, depending on the free time left after meetings. The test: if you do not get them done tomorrow, a real problem appears. Everything else is a candidate, not a selection.

Why should Outlook not open in the inbox?

Because the first view determines what you think about first. Start in calendar and tasks and you begin with your priorities instead of other people’s. Email is an asynchronous medium and tolerates an hour of delay.

When is the best time for the weekly review?

While there is still energy to resolve open ends. Early Friday afternoon works better than late, because a review without decision-making capacity does take place but changes nothing.

---

If work regularly follows you to the dinner table, it is rarely because too much is open. Usually it is because nowhere does it say what happens with it tomorrow.

For the evening pass to hold, calendar, lists and inbox have to fit together. That is what a workflow setup puts in place. Write to me if your day starts from zero every morning.