The Five-Minute Version of the Weekly Review, For the Weeks You Have Skipped Three

The weekly review has a failure mode built into it. Miss one week and the next review has two weeks of material, which makes it longer, which makes it more likely you skip that one too. Three weeks in, the review has become a project, and projects get scheduled for later. I have watched this happen to my own practice four separate times and to most people I have taught it to.

The fix is not more discipline. It is having a second, smaller review that is explicitly for this situation and that does not attempt to catch up.

Mine takes five minutes and has three questions. What is on fire right now. What did I promise someone that I have not done. What is the one thing I would regret not starting this week. That is all. No capture inbox processing, no going through the calendar, no updating project lists — the things a full Friday review does and the things that make the backlog version unbearable.

The critical design decision is that it does not look backwards. A normal weekly review is partly retrospective, and retrospection over three neglected weeks is where the time and the discomfort both come from. The recovery version declares the backlog closed. Whatever was in those three weeks and has not surfaced by now, by way of someone chasing it or something breaking, is now archived by default. This felt reckless the first time. In practice, nothing important stays quiet for three weeks; important things chase you.

The second question does most of the work and I would keep it if I could only keep one. Commitments to other people are the only category where the cost of dropping something is borne by someone else, and they are also the category most likely to be sitting in a chat thread rather than a task list. Answering it means scanning sent messages for anything shaped like “I’ll”, which takes about ninety seconds and has caught something roughly two weeks in three.

The third question is deliberately about starting, not finishing. When you are behind, the instinct is to pick something you can complete, because completion feels like recovery. But the things that decay while you are not reviewing are almost always the ones with no deadline and long lead times, and those need starting rather than finishing. Asking what I would regret not starting reliably surfaces a different item than asking what I should get done.

Once the five-minute version has run twice, the full review usually becomes possible again, and I think the mechanism is simply that the situation is no longer alarming. The reason a delayed review is avoided is not that it takes ninety minutes; it is that you do not know what is in it. Five minutes of looking removes the not-knowing, and the ninety-minute version stops being frightening.

I would suggest writing the recovery version down somewhere you will find it when you need it, which is a different place from where your normal review checklist lives — the normal one lives somewhere you visit weekly, and by definition you are not visiting it. Mine is a note pinned in the app I open most, with the three questions and nothing else, and the title is the honest one: “for when you haven’t.”

The broader point is that most personal systems are designed for the state where they are working. The interesting design problem is the state where they have already broken, because that is the state that determines whether the system exists in a year.