The weekly review that survives a bad week

Everyone who has read a productivity book has started a weekly review. Almost nobody is still doing theirs a year later, and the reason is dull: it got too big.

It starts as ten minutes. Then somebody suggests adding a metrics section, and a list of open loops, and a projects pass, and gratitude, and a look at next quarter. Within two months the review is a ninety-minute ritual that requires a clear head and an empty Sunday. Neither is reliably available, so it gets postponed, and a postponed ritual is a dead ritual.

Design it for your worst Sunday

The mistake is designing the review for the version of yourself that is rested, on top of things and pleased with the week. That person does not need a review; they can already see the shape of things.

Design it for the other Sunday. The one after the week where a launch slipped and a client went quiet and you slept badly. If the ritual survives that Sunday, it survives everything. If it needs an hour, it does not survive, and it takes the good weeks down with it.

So the real constraint is not what would be useful to review? Almost anything would be. It is what is small enough that I will still do it when I feel like a fraud?

Three steps

In hokd the weekly anchor is three, and it stops there on purpose.

Name this week's courage. One thing that was uncomfortable and that you did anyway. Sent the invoice with the higher number. Said no. Made the call you had been circling since Tuesday. This is the single most under-recorded category of work in solo business, because it leaves no artefact: nothing ships, nothing appears in a folder. If you do not name it on Sunday, by Wednesday it is gone.

Set next week's anchor. One sentence about what matters most in the next seven days. Not a plan, not a list — a sentence. The point is not scheduling; it is having something to measure the week's noise against.

Check the mountain. Look at what the week actually added. Not to judge it. Just to see it, because your memory will not do this for you. Memory keeps the argument with the bank and drops the four quiet hours that moved the product forward.

Why the anchor stays on screen

A review that ends when you close the app changes nothing, which is why most of them feel like paperwork. The anchor you set on Sunday sits at the top of every screen for the next seven days. No notification, no badge, no streak riding on it. It is just there when you look, the way a note on a monitor is there.

That is enough. The function of an anchor is not enforcement; it is giving you something to compare against when a Thursday tries to fill itself with other people's priorities.

Review something real

A weekly review is only as good as the record underneath it. Doing one from memory is mostly an exercise in recalling how you felt, and feelings are a biased sample of a week.

Because every stage in hokd was logged in one line with the kind of work it was, Sunday starts from what actually happened. Five minutes, once a week, on evidence rather than mood. With Pro, the weekly synthesis drafts that summary from your entries so the review starts from a page that is already written.

Ten minutes a week is not much of an investment. The trick is picking a ten minutes that still fits in the weeks you would rather forget.