← Back to blog

A review is for learning, not recording

A review is for learning, not recording

A weekly review is not for recording what happened. It is for understanding it well enough to decide what to do next. Those sound similar and are not. Recording restates the week. Understanding works out why it went the way it did, and that difference is most of the value of the hour.

This is where reviews quietly fail. They drift into reporting. You tally what got done, feel the small satisfaction of an accurate account of yourself, and change nothing. An accurate account that teaches you nothing is an expensive way to spend an hour, because it feels like diligence.

A review has two jobs that depend on each other. It is where you work out what last week taught you, and it is where you decide next week on the strength of it. Skip the learning and the decision is a guess. Skip the decision and the learning never gets used. The looking back and the looking forward are not two halves to choose between. One feeds the other, and it helps to know the order they come in.

Get the numbers honest first

The first job is the dull one. Pull your measures into one place and make them current. The habits, the lead indicators, the progress against each objective. Before you can think about any of it the data has to be true, because a review run on half-remembered numbers is a story you tell yourself with some figures attached.

This is also where most of the hour goes, mine included. Collecting, reconciling, building the graph that lets you see a trend instead of a single number. It is the least valuable part of the review and routinely the longest, which is worth saying plainly. The admin is not the review. It is the tax you pay to start it, and anything that lowers that tax is bought back for the part that matters. The real danger of a heavy setup is not the time it costs. It is that a review which takes that much effort to begin is the first thing you drop on a bad week.

Start with what you told yourself to do

Before the objectives, look at last week's list. You ended the previous review with a small set of things to focus on. The first question is whether they happened.

This closes a loop most tracking leaves open. The output of one review is the first input to the next. If the thing you committed to did not get done, that is information about the commitment, not only about the week. Either it was the wrong thing, or it was never concrete enough to act on, and both are worth knowing before you set the next one.

Go objective by objective

Then take the objectives one at a time. Not a single blurred impression of the week, but each goal in turn, because they are rarely all in the same state and a general feeling averages them into something useless.

For each one, start with what moved. Did a lead indicator shift the way the plan expected. Your easy pace at a given heart rate, your booked-call rate per hundred contacts. Did anything tick off or increment an OKR. A single data point tells you almost nothing, so the shape over several weeks is what you read, which is why a graph earns its place exactly when a bare number would mislead you.

What moved is the easy half. The learning is in why it moved. A booked-call rate that climbed because the new message is landing is a different fact from one that climbed because you simply made more calls, and only one of them is worth repeating. An easy pace that stalled across a full week of training tells you the plan is wrong. The same stall across a week you mostly lost to a cold tells you nothing. This is why the events matter. They are the difference between a number you can learn from and a number you would misread. A measure you cannot explain is not yet knowledge, and you cannot build next week's decision out of it.

Decide a small, closed week

This is the part that does the work, and the part people rush. The review now turns into next week's plan, and the discipline is keeping that plan short and finished.

Set detailed tasks where a goal needs them, and refuse anything open-ended. "Work on the website" is not a task. It is a worry written down. It cannot be completed, so it never is, and it rolls forward week after week collecting guilt while producing nothing. If you cannot tell from the wording whether it is done, it does not belong in the week. The review is where a vague intention either becomes something with an edge or gets left out on purpose.

Then narrow further. Across all the objectives, name the single thing each one most needs next week. One per goal. This sounds like a restriction, and that is the point. A week holds a handful of things that genuinely move, and a plan that lists twenty of them is not ambitious, it is unsorted. Most of the value of the hour is in what you decide not to carry into the week.

Then look at the whole thing

Last, step back from the objectives and take the week as one piece. This is the second place the learning lives, and it is a different kind. The per-goal pass is precise and slightly blind. It will not tell you that one objective has quietly eaten all the others, or that you were busy in every direction and moved in none, or that the same disruption has cost you three weeks running and is not the one-off you keep treating it as. No single objective holds that pattern. It only shows up from a distance. It is a short step and usually the most honest one, and it shapes the next week as much as anything in the detail does.

Why a week, and why it will not stay the same

A week is the cadence that makes the closed list work. Long enough that the trends mean something and the events have played out. Short enough that the decisions you made are still live when you sit down to check them. Decide daily and you react to noise and never test a commitment. Decide monthly and the drift has already happened by the time you look.

The review should also get lighter as you learn it. At the start you check whether each goal even points the right way, and you pull every number because you do not yet know which ones matter. Later the direction is settled, the question is execution, and you have stopped collecting half the measures you began with because you never once used them. A review that keeps growing is one you have not understood yet. The good version gets smaller.

A review that decides without reflecting is just shuffling tasks between weeks. A review that reflects without deciding is reporting in better clothes. The hour is worth protecting because it is the one place the two meet, where last week stops being something that happened to you and becomes something you understood well enough to do the next one differently.