A review is not a second job
The weekly review should reduce Monday's ambiguity, not produce a perfect life dashboard. If the review takes an hour, requires tagging everything, or creates more tasks than it closes, the system is too heavy.
Use this as a 20-minute editorial pass on your own week: what is still true, what moved, what must happen next, and what can be ignored without consequence.
Quick answer
A useful weekly review should capture open loops, verify upcoming commitments, select a small number of outcomes and define Monday’s first visible action. It should not become a complete reorganization of every project.
The old article described a personal Friday practice without supplied logs. This version is an editorial checklist informed by planning research. Twenty minutes is a boundary, not a proven optimal duration.
Minute 0–5: collect
Gather loose notes, flagged messages, calendar reminders and tasks discovered during the week. Capture them in one temporary list without sorting every item.
Do not reread the entire inbox. The goal is to prevent a commitment from remaining only in memory.
Minute 5–9: close or clarify
Mark completed items, delete obsolete ones and rewrite vague entries into visible actions. If another person owns the next step, record a follow-up date rather than repeatedly reviewing the same blocked task.
Masicampo and Baumeister reported that making plans could reduce cognitive effects of unfinished goals in their experiments. That does not mean every written list reduces stress; the plan must be specific enough to be trusted.
Minute 9–13: scan forward
Review the next two weeks of the calendar, not just Monday. Look for preparation deadlines, travel time, care responsibilities and dependencies. Check whether the calendar and task list contradict each other.
Planning research on implementation intentions supports specifying when, where and how an intended action will begin. Use that structure for tasks likely to be forgotten: “After the 9:00 meeting on Monday, send the signed form from the project folder.”
Minute 13–17: choose outcomes
Select up to three meaningful outcomes for the week. An outcome describes a changed state, such as “proposal sent for review,” not an activity such as “work on proposal.”
Capacity is not the same as free calendar space. Leave room for routine administration and unexpected work.
Minute 17–20: prepare Monday
Choose one first action and place the required object or link where it will be used. Draft the email subject, open the document or write the question that must be answered.
Stop when the timer ends. Large project planning belongs in a separate session.
Review checklist
- Capture loose commitments.
- Mark completed and obsolete items.
- Convert vague tasks into next actions.
- Check the next two weeks.
- Identify deadlines and dependencies.
- Choose no more than three weekly outcomes.
- Write Monday’s first visible action.
- Schedule a separate block for complex planning.
Common failure modes
| Failure | Correction |
|---|---|
| Reviewing every email | Capture only unresolved commitments |
| Choosing ten priorities | Select three outcomes and a backlog |
| Ignoring calendar capacity | Add preparation and travel time |
| Rewriting the whole system | Record the issue for later |
| Treating blocked work as active | Name the owner and follow-up date |
When Friday is a poor fit
Run the review at the last predictable work boundary. Shift workers, caregivers and students may prefer Sunday evening or the first quiet period after a schedule is published. A stable trigger matters more than the weekday label.
Final recommendation
The weekly review earns its time when it changes what happens next. End with a short list, realistic calendar and one prepared action. If the review repeatedly exceeds 20 minutes, separate backlog maintenance from weekly planning.