You set it for Sunday evenings. You did it for three weeks, then missed one, then did it again a fortnight later, and now it's the thing you feel vaguely bad about not doing.
The standard diagnosis is discipline, and the standard remedy is a calendar reminder and more resolve.
Neither is the problem. People are perfectly capable of sustaining twenty-minute habits that produce something. The review gets skipped because most weeks it produces nothing, and skipping something that produces nothing is not a failure of character.
What a useless review feels like
You open the list. You read down it. Each item gets a few seconds of attention and some mild recognition — yes, that's still there, yes, I should get to that — and twenty minutes later you've been past everything and made no decisions at all.
The output is a feeling. Usually a slightly bad one, because a list read end to end is mostly things you haven't done. And because the feeling has no object — no single goal you resolved anything about — it attaches to you rather than to the work.
Do that four Sundays running and skipping the fifth is the rational move. You're not avoiding a useful activity. You're declining to spend twenty minutes generating guilt, which is a reasonable thing to decline.
Then the skipping itself becomes the problem, because now there's a habit you've failed at on top of the goals you've failed at. People add reminders, move it to a different day, buy a different notebook. None of that touches the cause, and each attempt makes the next one heavier.
Why it produces nothing
Three causes, and they're all structural rather than personal.
The list is too long. Nineteen goals means each gets sixty seconds, which is enough to be reminded it exists and not enough to think about it. A review of nineteen things is a roll call, and roll calls produce attendance rather than decisions.
The order is wrong. Most lists are in creation order or an order you set, which means the goals you're comfortable with come first and get the attention while you're fresh. By the time you reach the one that's actually in trouble you've spent your energy, which is precisely what the ordering was unconsciously arranged to achieve.
And there's no question being asked. How's everything going has no answer and no action attached. A review needs to ask something specific enough to be answerable, and what's the state of my life is not that.
There's a fourth cause that's less structural and worth naming. A lot of reviews are secretly performances — a session where you demonstrate to yourself that you're the kind of person who reviews. Those have no output by design, because the output was the demonstration, and they get abandoned as soon as the novelty of being that person wears off. The tell is whether you'd still do it if nobody, including you, were watching.
The version that works
Two changes, both mechanical.
Sort by silence, longest gap first. Now the first thing you see is whatever you've been avoiding longest, examined while you're still fresh, and the goals you worked on this week sit at the bottom where they belong because you already know how they're going.
Then ask two questions per goal and nothing else. Why has this been quiet? And what's the smallest next thing? Naming the first is most of the work — you don't know the next step, you're waiting on somebody, you're frightened of it, you don't want it, or there's no room at the moment. The second should be finishable in half an hour.
Stop when the gaps get short. Once you're into things touched in the last few days there's nothing to diagnose, and continuing is how a review becomes tedious and then optional. Four goals is a good review. There is no requirement to reach the bottom of anything.
Write both answers on the goal. An unwritten diagnosis is gone by Wednesday, and next Sunday you'd do the same thinking from scratch.
When skipping is correct
Worth saying, because the tone of most advice on this is that a missed review is a small moral failure.
Some weeks there's nothing to review. If you've touched everything on a short list in the last four days, the review will tell you what you already know, and doing it out of duty is exactly the kind of ceremony that makes people abandon systems. A review is a diagnostic tool. You don't run diagnostics on something that's obviously working.
And in a genuinely bad week — illness, a crisis, no capacity at all — the review is likely to produce a list of things you can't act on, which is worse than not looking. The honest move there is to park what needs parking and leave the rest until there's room.
The failure mode isn't missing one. It's the pattern where you miss four, then restart with an elaborate two-hour catch-up session, which is unpleasant enough to guarantee you miss the next four.
Nineteen items, then four
Two Sundays, same person.
The first: nineteen goals in the order he created them. Ten minutes in he's at item nine, has recognised everything and decided nothing, and the dominant sensation is that he's behind on all of it. He closes the laptop, resolves to do better, and doesn't open it again for three weeks.
The second, after cutting the list: four live goals, sorted by gap. Top one is 34 days quiet — the pension consolidation. Why? He doesn't know the next step. Smallest thing: find the login for the old provider. Written down, four minutes on Tuesday.
Next, 19 days — the beta, waiting on a signed build since the 3rd. Nineteen days is well past reasonable. Chase today, and set Friday as the date to build it unsigned.
Next, 12 days — the second chapter. Next step clear, nobody blocking, dropping it would be awful. That's fear. Smallest thing: open the file, read it, add a sentence.
Fourth is four days quiet and needs nothing.
Eleven minutes. Three moves written down, one of which happens that evening. The following Sunday he does it again, because it worked.
What makes it survive
The review that lasts is the one that produces a decision you'd have missed otherwise. Everything else is ceremony, and ceremony gets dropped the first busy week — correctly.
Which is most of why goaldrift sorts itself and can't be reordered. The property that makes a review useful is available every time you open the app, not only on Sundays. If the weekly session gets skipped, the ordering is still doing its job on a Tuesday morning, and the thing you've been avoiding is still the first thing you see.
A review you can skip is a review you will skip. The ordering ought to survive that.
That's the safety net the whole thing rests on. A practice that only works when you keep it perfectly is a practice that stops in the first hard month, and hard months are not rare. Build it so that the useful part happens whether or not you turn up.
Related: Review by gap, not by list · Three goals, not thirty · The anatomy of a stuck goal
Share: