The weekly review, reduced to twenty minutes
By The Serena Team
Almost everyone who tries a weekly review abandons it, and usually for the same reason: the version they attempted was an audit. Sixty to ninety minutes, every project inspected, every list reconciled. That is a genuinely useful exercise and almost nobody sustains it, because it competes with rest at exactly the moment in the week when rest is winning.
A twenty-minute review that happens every week beats a ninety-minute review that happens twice a quarter. The trick is knowing which parts of the long version actually change your decisions, and cutting the rest.
The four passes
Run these in order and keep them separate. The separation matters more than it sounds: mixing capture with deciding is what turns a review into an hour of drifting.
Close last week (5 minutes)
Mark what finished. Look at what did not and write one honest reason. Not a plan, not a rationalization, just a reason.
Empty the inboxes (5 minutes)
Everywhere work accumulates: notes app, saved messages, email flags, the paper on your desk. Each item becomes a task, a note, a calendar entry, or nothing. Do not do the work; just place it.
Decide next week (7 minutes)
Pick the small number of outcomes that would make next week a good one. Check them against the calendar you already have, not the calendar you wish you had.
Check one habit (3 minutes)
One process question, not five. Rotate it week to week.
Pass one: close last week without relitigating it
The purpose here is an accurate record, not a verdict. Ticking off finished work takes a minute and matters more than it seems, because a week with nothing visibly closed feels like a wasted week even when it was not.
For anything unfinished, write one reason from a short list: it was not actually important, it was blocked, it was bigger than expected, or it lost to something urgent. The value is in the pattern across weeks rather than any single entry. Four consecutive weeks of "bigger than expected" means you are systematically underestimating, which is a scoping problem. Four weeks of "lost to something urgent" means your reactive buffer is too small, which is a capacity problem. Different diagnoses, different fixes.
Pass two: empty every inbox, including the analog ones
Anything holding an unprocessed commitment is an inbox. Most people have more than they realize.
- Notes taken during meetings, which usually contain commitments you have not extracted yet
- Saved or starred messages across chat and email
- Browser tabs left open as reminders, which is what tabs mostly are
- Voice memos and camera-roll screenshots
- Physical paper: notebooks, printouts, sticky notes
Every item gets exactly one of four destinations: a task with a clear next action, a note filed where you would look for it, a calendar entry if it is genuinely time-bound, or discarded. Discarded is a legitimate and underused option. If something has survived three reviews without being touched, that is information about its importance.
Pass three: decide next week against the real calendar
This is the pass that changes outcomes, and it is the one most often skipped because the first two feel productive. Open next week alongside your list and answer three questions.
What must be true by Friday?
Usually one to three things. If the list runs to eight, you are enumerating tasks rather than deciding priorities.
Where will the time come from?
Point at actual gaps in the actual calendar. A priority with no time behind it is a wish. If there is no room, something has to move or be dropped now, while it is cheap.
What is the first concrete step for each?
Reduce every commitment to something you could start in five minutes on Monday morning without further thought. Vague first steps are where good intentions die.
Finish this pass with everything you are not doing left visibly unpromised. The goal is not an empty list. It is knowing which items you have deliberately declined for the week, so you can stop carrying them as low-grade guilt.
Pass four: one process question, rotated
Three minutes on a single question about how you are working, not what you are working on. Rotating keeps it from becoming a ritual you stop reading.
- What did I say yes to that I should have declined?
- What has been on the list for over a month without moving, and why is it still there?
- Which recurring meeting produced nothing this month?
- What did I do manually more than three times that could be templated?
- Where did I lose the most time to switching context?
One answer. One small change. Then stop. The failure mode here is generating a list of process improvements that becomes its own backlog.
When to run it
Friday afternoon and Monday morning both work, and they work differently. Friday closes the week cleanly and lets you rest without a background hum of unresolved items, but you are tired and inclined to be harsh. Monday is sharper but spends your best focus of the week on planning rather than doing.
The reliable answer is whichever one you will actually keep. Pick a fixed slot, attach it to something that already happens at that time, and accept a mediocre review over a skipped one. Consistency compounds here in a way that quality does not. Serena AI can assemble the first two passes as a weekly recap of what closed and what did not, so the twenty minutes go on deciding rather than gathering.
Key takeaways
- Run four separate passes: close last week, empty inboxes, decide next week, check one habit.
- Keep the timer visible; the limits are the mechanism that keeps the review sustainable.
- Record one honest reason per unfinished item, and read the pattern across weeks rather than any single entry.
- Check next week against the calendar you actually have; a priority with no time behind it is a wish.
- Leave declined work visibly unpromised instead of trying to reach an empty list.
Frequently asked questions
What if I miss a week?
Run the normal twenty-minute review, not a double-length catch-up. Attempting to reconcile two weeks is how people quit. The inbox pass will take slightly longer and everything else is unchanged.
Should the weekly review include long-term goals?
Not weekly. Goal review works better monthly or quarterly, on a different cadence and ideally in a different sitting. Mixing the two makes the weekly review heavy enough that it stops happening, and quarterly thinking rarely benefits from weekly attention.
Does this work for teams?
The structure transfers, but the passes change. Team reviews spend most of their time on blockers and handoffs rather than inbox processing, since individual capture stays individual. Keep the same discipline of separating capture from deciding.
How is this different from a daily plan?
The weekly review decides what matters and where the time comes from; the daily plan allocates a single day against that decision. Doing only the daily version means constantly optimizing within priorities you never stepped back to question.