Twenty minutes on Friday
A week goes wrong slowly. Nothing dramatic happens; three things quietly stop moving and nobody notices until the deadline does.
This is the only recurring meeting-with-yourself worth defending. Twenty minutes, once a week, and its purpose is noticing rather than planning.
Friday, not Monday
On Friday you still remember why something stalled. On Monday you have the same board in front of you and no memory attached to it, so you reconstruct instead of recalling — and reconstruction is where wrong explanations come from.
There is a second reason. A review that ends the week lets you leave with a decision made; one that starts the week competes with everything urgent and gets dropped by ten past nine.
Look in this order
What moved. Not to congratulate yourself but to see where progress actually came from — it is rarely where you spent the most hours, and noticing that changes next week more than any resolution will.
What did not move. Anything untouched for two weeks needs a decision, not another week: split it, hand it over, or drop it. Leaving it is also a decision, just an unexamined one.
What arrived without anyone deciding. Every week, work appears that nobody chose — a favour, a request in a message, something inherited. That is the category that quietly eats capacity, and it is invisible unless you look for it deliberately.
Change one thing, not five
Reviews that produce a list of improvements produce nothing. The list is read once, feels productive, and by Wednesday the week has reasserted itself.
Pick the single change most likely to be true again next week and make it now, in the system, not in your intentions. Move the recurring meeting, delete the column, tell someone the thing you have been avoiding telling them. One change that survives beats five that were only written down.
Doing it as a team is a different meeting
A shared version works, but only if it stays about what is stuck rather than what everybody did. The moment it becomes a round of status updates, it is a report read aloud and people stop bringing the awkward item.
Keep it to one question each: what is blocked and who can unblock it. Fifteen minutes, standing up if you are in a room. Anything longer turns into the planning meeting you were trying to avoid.
Questions people actually ask
When should the weekly review happen?
Friday. You still remember why something stalled; by Monday you reconstruct instead of recall, and reconstruction is where wrong explanations come from. A review starting the week also loses to whatever is urgent.
What should I look at?
In order: what moved, what did not move, and what arrived without anyone deciding. The third is the category that quietly eats capacity and stays invisible unless you look for it on purpose.
How many things should I change afterwards?
One, made immediately in the system rather than written on a list. A list of five improvements feels productive, is read once, and is gone by Wednesday.
