The weekly review that keeps work out of the weekend

A week that ends by simply stopping leaves everything open. Unfinished work has no recorded state, decisions half made are still half made, and the list is a mixture of things done, things abandoned and things that were never realistic. None of that is written down anywhere, so it stays in your head.

That is the actual mechanism by which work leaks into a weekend. It is usually not that you sit down and work — it is that you keep thinking about it, because anything unresolved and unrecorded has to be held mentally in case it matters. The relief people describe after a proper review is mostly this: the things are written down, so they no longer need to be remembered.

And Monday inherits the same problem from the other side. Arriving with no plan means the week begins by reading messages, which means the first thing you engage with sets the agenda, which means the week's shape is determined by whoever sent something over the weekend. 30 minutes on Friday is the cheapest available intervention on both of those, and it is the first thing dropped in a busy week.

The timing does real work here, and Friday afternoon is not an arbitrary choice.

Doing it before the end of the working week means the information is current — you can still remember why something stalled on Tuesday, which you will not by Monday. It also means the closing happens before the break rather than after it, which is the entire point if the goal is not carrying the week home.

Friday afternoon is also a poor window for demanding work in most people's day, which makes it close to free. Reviewing is not cognitively hard; it is mostly reading, sorting and deciding small things, which is exactly what a low-capacity window supports.

Monday morning is the common alternative and it is a worse trade. It solves the planning half and none of the closing half, and it spends prime attention on administration.

Thirty minutes is enough once the habit is established, and the first few will take longer because there is a backlog of unrecorded state. Setting a fixed slot on the calendar matters for the usual reason: a review held when there is time is a review held on quiet weeks, which are the weeks with least to close.

What got done. Read it out, briefly, to yourself. This is not ceremonial — a week generally contains more completed work than it feels like from inside it, and the gap between the two is where a lot of unnecessary discouragement lives. It also catches the item that has been nearly finished for three weeks, which is the single most useful thing this question surfaces.

What did not, and why. The why is the part that matters, and it needs one honest word: no time, blocked, avoided, or should never have been on the list. That word is what makes the pattern readable over a month.

What rolls over. Explicitly, and with a decision attached. Rolling something over for a fourth consecutive week is a decision to either schedule it properly or drop it, and making that decision consciously is the point.

What next week looks like. The two or three things that must happen, placed in the week rather than listed. Not a full plan — the commitments, so Monday begins with a position rather than an inbox.

Anything beyond these four tends to expand until the review is a project nobody sustains.

The mechanical half of the review is emptying the places where things have accumulated during the week, and it is worth doing after the four questions rather than before, because the questions are the part that gets skipped when time runs short.

The places are usually the inbox, notes made on your phone, whatever was written on paper, and the task list itself, which by Friday contains items in three states with no distinction between them.

Emptying does not mean doing. Every item gets one of four outcomes: do it now if it takes two minutes, schedule it, delegate or pass it on, or delete it. The fourth is used far less than it should be. A meaningful share of what accumulates during a week is no longer relevant by Friday, and carrying it forward means re-reading and re-deferring the same item indefinitely — which costs a little attention every single time.

The reason to do this weekly rather than continuously is that a week is long enough for irrelevance to become obvious. Something that felt urgent on Tuesday and has resolved itself by Friday can be deleted without thought, whereas the same item processed on Tuesday would have been scheduled.

The completed list is satisfying and the blocked list is where the information is, which is the reverse of how most people run a review.

A single blocker is an event. The same blocker three weeks running is a structural fact about how you work, and it will not appear unless it is written down each week — memory smooths repetition into a vague sense that things keep getting in the way, without ever identifying what.

What tends to show up: one recurring meeting that reliably destroys an afternoon, a dependency on one person who is always over-committed, a category of work that is consistently underestimated, or a slot in the week that never survives contact with reality.

Each of those has a fix, and none of the fixes are available while the pattern is invisible. This is the highest-value output of a personal review and the one most often skipped, because writing down that something was blocked feels like a complaint with no recipient.

One line per week is sufficient. The value appears at a month, not at a week, which is worth knowing so that the first four reviews do not feel pointless — they are accumulating the data rather than producing it.

A review that produces the same findings every week has done its job and is now waiting on a decision somewhere else.

If the same work rolls over repeatedly, one of three things is true: it is not actually a priority and should be dropped, it is larger than the slot it keeps being given, or something is systematically taking its time. All three are addressable and none are addressed by rolling it over again.

If every week ends with substantially more not done than done, the issue is intake rather than execution. No review improves this — it will report it accurately and indefinitely, which after a couple of months becomes a weekly reminder of an unmade decision.

And if the review itself keeps getting skipped in busy weeks, that is worth reading as the signal it is. The weeks with most to close are the weeks it gets dropped.

One boundary worth stating: this is a planning practice. It surfaces patterns in workload, priorities and blockers, and it is not a tool for anything beyond that. A review that keeps reporting that everything is too much, week after week, has identified something a rearranged week may not resolve — and that is a point to talk to someone rather than to refine the format.