Weekly Review¶
Review ritual — instantiates Cadence Design
A recurring personal audit of commitments and open loops that catches what is slipping and updates the plan, keeping the whole system trustworthy week to week.
A Weekly Review is a recurring, self-owned audit in which one person (or a small team acting as one) steps back from doing the work to inspect the state of their commitments — closing loops, catching what's slipping, and re-planning the week ahead. Its defining move is reflection turned inward: unlike a live sync or a broadcast, its subject is your own system, and its purpose is to notice the signals that something has gone stale — a backlog creeping up, a commitment quietly dropped, a rhythm that stopped producing — and to correct course before the drift compounds. The output is an updated, trusted plan; the discipline is that it recurs whether or not anything feels urgent, because the drift it catches is exactly the kind that doesn't announce itself.[n1]
Example¶
A consultant runs everything out of a task system that only stays trustworthy if she tends it. Every Friday afternoon she blocks an hour for a weekly review. She works a fixed loop: empty the inboxes and notes to zero, walk every open project and confirm each has a real next action, scan the calendar two weeks back and three forward for loose ends, and skim her someday list for anything that's now live. It is entirely her own ritual — no one convenes it, no one else attends, and it produces no report for anyone else.
The value shows up in what it catches. This Friday she notices a client deliverable has had no next action for eight days — it silently stalled while she was heads-down — and a standing biweekly check-in she keeps has produced nothing useful for a month. The review surfaces both: she re-activates the stalled project and decides to kill the hollow check-in. She leaves with an updated plan she actually trusts and a lighter set of commitments. Nothing here was live coordination or an outward update — it was a private audit that kept the whole system from quietly rotting.
How it works¶
A weekly review is distinguished from other recurring touches by being an inward, self-owned inspection:
- Owned by the doer, for the doer. No one else convenes or attends; the person whose system it is runs it and is accountable for keeping it up. That personal ownership is what keeps it alive.
- It reads its own health signals. The review is the standing moment to catch the tell-tales of drift — stalled items, empty next-actions, a backlog trending up, a commitment or sub-cadence that's gone hollow — and to act on them.
- It ends in an updated, trusted plan. The occurrence isn't done until loops are closed and the week ahead is re-planned; a review that changes nothing was just re-reading.
The cadence's value is a trustworthy system: a weekly moment to re-anchor, so the day-to-day can run without the low hum of wondering what's been forgotten.
Tuning parameters¶
- Interval — weekly is the classic beat, but the right rhythm tracks how fast your commitments churn. Faster churn wants a tighter loop; a stable, slow-moving load can stretch it.
- Scope — a light triage versus a full audit of every project, list, and horizon. A deeper review catches more drift but costs more time and is easier to skip when busy.
- Checklist rigidity — a fixed loop you run identically each week versus a loose look. A rigid loop makes the review fast and complete but can feel mechanical; a loose one flexes but misses corners.
- Horizon span — how far ahead and behind you scan. A wide horizon catches slow-building issues early but dilutes focus; a narrow one is fast but near-sighted.
- Trigger sensitivity — how faint a drift signal (a slightly-growing backlog, one missed occurrence) prompts you to re-scope or retire a commitment. Sensitive catches decay early; jumpy churns your system needlessly.
When it helps, and when it misleads¶
Its strength is that it keeps a whole personal system trustworthy: a reliable weekly re-anchoring closes open loops before they're forgotten, catches quiet drift while it's still small, and — because it's the standing moment to ask "is this still working?" — is where hollow commitments and stale sub-cadences actually get retired.
Its failure modes are the ones every self-owned ritual faces. It is the first thing dropped when busy — precisely when the drift it guards against is worst — so the system rots exactly when it's under load. It can decay into going through the motions, a checklist run without honest reckoning, so loops are ticked but nothing is truly reconsidered. And it can turn into productive procrastination, endless tidying and re-planning that substitutes for doing the work. The discipline that guards against these is to protect the slot even (especially) when slammed, to keep the review honest enough to actually kill or re-scope what isn't working, and to timebox it so it re-anchors the week rather than consuming it.
How it implements the components¶
A Weekly Review owns the self-audit corner of the archetype — the inward, owner-run inspection that keeps a system trustworthy:
cadence_owner— the person whose system it is runs and sustains the review; there is no separate convener, and that personal ownership is what keeps the rhythm alive.review_trigger— it is the standing checkpoint that reads drift signals (stalled items, rising backlog, a hollowed-out commitment or sub-cadence) and decides what needs re-scoping or retiring.expected_output— each occurrence must end in closed loops and an updated, trusted plan; a review that produces no change is just re-reading.
It sets no participation_boundary — a weekly review is solo, so the live team sync belongs to Standup Meeting — and defines no exception_path for off-cadence urgencies (→ Governance Meeting Cycle). Its nearest twins are those recurring check-ins: unlike Standup Meeting's live, forward-looking team huddle, a weekly review is a solo reflective audit, and unlike Status Digest's outward broadcast, it turns inward — its whole subject is the health of your own commitments.
Related¶
- Instantiates: Cadence Design — the weekly review supplies the inward, owner-run audit that keeps a recurring system trustworthy week to week.
- Sibling mechanisms: Standup Meeting · Status Digest · Governance Meeting Cycle · Budget Cycle · Release Train · Recurring Inspection · Training Cycle · Maintenance Schedule
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Weekly Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a recurring personal audit of commitments and open loops that catches what is slipping and updates the plan, keeping the whole system trustworthy week to week.
Independent corroboration: The frozen evidence defines Weekly Review as 'A recurring personal audit of commitments and open loops that catches what is slipping and updates the plan, keeping the whole system trustworthy week to week', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: Carver and Scheier, Control Theory documents that psychological self-regulation compares present state with goals in repeated feedback-and-adjustment cycles. This is direct, mechanism-specific evidence for psychology as the best-evidenced historical home of the operation—A recurring personal audit of commitments and open loops that catches what is slipping and updates the plan, keeping the whole system trustworthy week to week.—rather than evidence merely that the operation is useful there. The retained alternates record genuine adjacent lineages; later portability is represented separately by domain_reach=universal.
Related originating lineages:
- Cognitive Science — Cognitive-science research on representation, learning, and recall supplies a parallel or contributing lineage for the mechanism's defining operation: a recurring personal audit of commitments and open loops that catches what is slipping and updates the plan, keeping the whole system trustworthy week to week.
- Operations Research — Operations research's allocation, scheduling, optimization, and decision-analysis tradition contributes a separate formative lineage to the mechanism's weekly review logic.
- Organizational & Management Science — Organizational Management supplies a historically relevant adjacent lineage or formative practice for the operation—A recurring personal audit of commitments and open loops that catches what is slipping and updates the plan, keeping the whole system trustworthy week to week.—but the adjudicated evidence more directly locates the defining lineage in psychology.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus psychology). The defining operation is: A recurring personal audit of commitments and open loops that catches what is slipping and updates the plan, keeping the whole system trustworthy week to week. The researched Carver and Scheier, Control Theory establishes that psychological self-regulation compares present state with goals in repeated feedback-and-adjustment cycles. That source therefore supports psychology as the historical origin. organizational management remains in the uncapped alternates where it contributes a formative practice, but application or governance is not itself proof of origin. origin_mode=single_lineage records lineage construction; domain_reach=universal separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] The Weekly Review is the linchpin practice of David Allen's Getting Things Done — a scheduled pass to get every commitment out of your head, current, and re-planned, so the rest of the system can be trusted. Its core claim is that a personal system is only as reliable as the regular review that re-anchors it, which is why the cadence recurs whether or not anything feels pressing. ↩