Where the week went, and how to read it without flinching

Most people track time and never read it. The data accumulates, the week ends, and the only thing anyone remembers is that it felt busy. Four minutes on a Friday fixes that, and the ritual is small enough to survive a bad week.

The four minutes

Open the week. Look at three things in this order.

The total, against nothing. Not against a target, not against last week. Just the number. Most people are surprised by how small it is, and the surprise is the useful part: four to five focused hours a day is a strong week, not a poor one. If you were expecting eight, you were counting presence, not work.

The split by project. One project almost always ate more than you thought. Name it out loud. That is usually the whole insight.

The sentences. Read the session goals top to bottom. Six weeks from now this is the only record that explains anything, and reading them weekly is what keeps them worth writing.

Why Friday, and why four minutes

Friday, because the week is finished and you have not yet started telling yourself a story about the next one. Monday morning is too late: by then the review competes with the work, and the work wins.

Four minutes, because a review that takes twenty gets skipped in exactly the weeks that most need it. A ritual has to survive a bad week to be worth having, and the bad weeks are when your memory of what happened is least reliable and your data is most valuable.

If you only ever do the first item on the list, open the week and look at the total, you have got most of the value. Everything else is refinement.

The three numbers that mislead

• Daily average across seven days. Dividing by weekend days you never intended to work makes every week look like a failure. Average over the days you actually logged something.
• Completion percentage on its own. A low number can mean your blocks are too long, or it can mean you are honest about stopping when a meeting lands. It only means something read next to the sentences.
• Any comparison with last week. Weeks are not comparable. A week with three days of interviews is not a worse week, it is a different job.

The question is not whether you worked enough. It is whether the hours went where you would have sent them.

Reading it without flinching

The flinch is the real obstacle. Most people avoid their own time data because they expect to be indicted by it, and the expectation is usually based on a bad assumption about what a normal week looks like.

So calibrate first. Focused, single-tasking work is not the same as being at your desk, and nobody sustains eight hours of it. Four to five hours a day, most days, is a genuinely good week for someone doing demanding work. Three is normal in a week with a lot of meetings. Six sustained over a month is unusual and often followed by a bad month.

Once that is the baseline, the numbers stop being an accusation and start being a description. A 19-hour week is not a failure; it is a week with eleven hours of meetings in it, and the useful question is whether those eleven hours bought anything.

Two more habits help:

• Read the split before the total if the total worries you. Where the hours went is almost always more actionable than how many there were.
• Do not review someone else's week. If you manage people, this ritual is theirs. A manager reading it over a shoulder turns an honest record into a performance, and the record stops being honest within a fortnight.

What to change

Usually nothing. The ritual earns its keep by making Monday's decision cheaper: you already know which project is starving, so you do not spend the first hour deciding. When it does suggest a change, it is almost always the same one fewer things in flight, not more hours.

What it looks like after a month

The first review is uncomfortable and tells you one thing you already suspected. The fourth is fast, unemotional and occasionally startling.

By then you have a rough shape you recognise: your normal total, your usual split, the project that always overruns. and the value moves from the numbers to the deviations. A week that looks wrong stands out immediately, and you can usually name the cause before you have finished reading.

That is the whole return on four minutes: not a productivity gain, but the end of the vague feeling that the week got away from you. It went somewhere specific. Now you know where.

A note on teams

Everything above is written for one person reading their own week, and that is not an accident. The same four minutes done to someone else is a status meeting with extra steps.

If you run a team, the version that works is the totals per project, read by you, and the sentences read by whoever wrote them. Project totals answer the question a lead actually has, is this thing costing what we thought, without turning a colleague's Tuesday into an exhibit. The moment individual hours become a topic in a group setting, the sentences get written for the audience, and the record you were relying on quietly stops being true.

The two-minute version

If four minutes is still too many, and on some Fridays it will be, there is a version that fits in the time it takes a kettle to boil.

Open the week. Read the total. Read the project split. Close it.

You will skip the sentences, which is the part that pays off later, but you will keep the habit alive, and a habit that survives the bad weeks is worth more than a thorough ritual you abandon in November. The full version can wait for a Friday that has room in it.