A weekly review — a regular pause to look back at the past week and plan the next one — is one of the most consistently recommended habits across time-management systems, from GTD's insistence on it as a load-bearing step to the role-based planning in First Things First, both discussed elsewhere on this shelf. It's also one of the most commonly abandoned habits, and the reason is usually structural: the template that worked fine during a calm week becomes the first thing dropped during a genuinely busy one, which is exactly the week the review would have been most useful.
Why a detailed template fails under load
A thorough weekly review template — reviewing every project, every list, every goal — takes real time to complete properly, and that time cost is roughly constant regardless of how busy the week has been. On a calm week, that cost is easily absorbed. On an overloaded week, the same fixed cost competes directly with everything else demanding attention, and a review that can't be compressed tends to simply get skipped rather than done partially, because most templates don't have an obvious 'short version' built in.
The fix isn't a shorter template used every week — that wastes the depth a calm week could actually support — it's a template with an explicit fast path: a minimal, five-minute version that still captures the most important information, reserved specifically for weeks too busy for the full version, so that skipping the full review doesn't mean skipping the review entirely. For a practical software example related to employee write-up form guidance, see it here.
A minimal version that still does the essential work
The essential core of a weekly review, stripped to what actually matters most, is small: what got missed or pushed from this week's plan, what's genuinely urgent or important for next week, and one honest note about what made this week harder or easier than expected. Everything else — detailed project-by-project review, long-term goal check-ins, full inbox processing — is valuable but not essential to do every single week, and can be reserved for a monthly review, discussed separately on this shelf, rather than crammed into every weekly cycle.
- Build two explicit versions of the review: a full one for a normal week, and a five-minute fast path for an overloaded one — not just one template used inconsistently.
- The fast-path version should still happen every week without exception; consistency at a smaller scope beats thoroughness done sporadically.
- Schedule the review at a fixed time, protected the same way a focus block is, rather than 'whenever there's a gap' — an unscheduled review is the first casualty of a busy week.
- Reviewing what got missed matters as much as planning what's next — a review that only looks forward loses the calibration value of noticing repeated slippage.
Where the review connects to everything else on this shelf
A consistent weekly review is what actually operationalizes several of the ideas covered elsewhere here — the plan-versus-log comparison needs a regular moment to happen, role-based prioritization from First Things First needs a weekly point to place its big rocks, and GTD's trust in a captured task list depends entirely on the review step to stay current. None of those ideas require a review to work in theory; in practice, almost none of them survive without one.
The habit is less about any specific set of questions and more about protecting a consistent, recurring moment to ask them — which is why the fast-path version matters as much as the full one: it's the version that keeps the habit alive through exactly the weeks that would otherwise break it. For additional background on this subject, consult Todoist’s productivity methods.