references/gtd_weekly_review_canon.md
6.3 KB查看排版效果| 1 | # The GTD Weekly Review Canon |
| 2 | |
| 3 | > Why David Allen calls the weekly review the "critical success factor" of the whole method, what |
| 4 | > the three phases actually contain, and why the cadence matters more than the format. |
| 5 | |
| 6 | ## The claim: the review is the keystone, not an accessory |
| 7 | |
| 8 | Getting Things Done rests on one psychological bargain: your mind will stop nagging you about |
| 9 | commitments **only if** it trusts that the external system holds all of them and that the system |
| 10 | gets looked at. Capture alone doesn't buy that trust — a list nobody reviews is just a graveyard |
| 11 | with better formatting. Allen is explicit that the weekly review is "the critical success factor" |
| 12 | and that people who fall off GTD almost always fall off here first: they keep capturing, stop |
| 13 | reviewing, watch the lists rot, and then stop trusting the lists — at which point everything moves |
| 14 | back into their head and the whole system collapses. |
| 15 | |
| 16 | The corollary this skill enforces: a review that skims is not a review. Marking the ritual "done" |
| 17 | while the core steps went unwalked actively *damages* trust in the system, because now the lists |
| 18 | are stale **and** carry a false freshness stamp. Hence the hard gate: unaccounted-for GET CURRENT |
| 19 | steps always force an INCOMPLETE verdict. |
| 20 | |
| 21 | ## The three phases |
| 22 | |
| 23 | Allen's own material organizes the checklist into three movements, in a deliberate order: |
| 24 | |
| 25 | ### 1. GET CLEAR — return to ground zero |
| 26 | |
| 27 | - **Collect loose papers and materials.** Physical and digital strays: receipts, notes, downloads, |
| 28 | screenshots, business cards. Everything into an inbox. |
| 29 | - **Get "in" to zero.** Process every inbox — email, notes app, task inbox, desk tray — by |
| 30 | *clarifying*, not doing. Each item becomes a next action, a project, a waiting-for, a |
| 31 | someday/maybe, reference material, or trash. The two-minute rule is the only exception: if |
| 32 | acting takes under two minutes, do it now. |
| 33 | - **Empty your head.** A mind sweep: write down every new project, task, or nagging thought still |
| 34 | riding in working memory. This is the step that converts psychic RAM into system entries. |
| 35 | |
| 36 | ### 2. GET CURRENT — make the system match reality (the mandatory core) |
| 37 | |
| 38 | - **Review next-action lists.** Mark off what's done, prune what's dead, notice what's stuck. |
| 39 | - **Review the previous calendar.** Look back over the past week or two for missed commitments, |
| 40 | follow-ups spawned by meetings, promises made in passing. Each becomes a captured item. |
| 41 | - **Review the upcoming calendar.** Look ahead so preparation happens now instead of panic later. |
| 42 | - **Review the waiting-for list.** Everything delegated or pending from others: chase it, re-date |
| 43 | it, or drop it. Unreviewed waiting-fors are where other people's slippage becomes your surprise. |
| 44 | - **Review project lists.** The load-bearing step: every active project must have **exactly one |
| 45 | next action** on a list. A project with none is a wish; a project whose next action is buried is |
| 46 | stalled. This step is why GTD projects keep moving without daily replanning. |
| 47 | |
| 48 | ### 3. GET CREATIVE — lift your eyes off the runway |
| 49 | |
| 50 | - **Review someday/maybe.** Activate what's become timely, keep what still sparks, kill what |
| 51 | doesn't. This list only works if it's periodically culled — otherwise it becomes a guilt museum. |
| 52 | - **Capture new ideas.** With a clear head and a current system, ambition is safe again. Allen's |
| 53 | point: creativity shows up *after* clearing, not instead of it. |
| 54 | |
| 55 | ## Cadence discipline |
| 56 | |
| 57 | - **Weekly is the resolution of most working commitments.** Allen's observation is pragmatic, not |
| 58 | mystical: most people's world shifts materially over a week — meetings compound, projects drift, |
| 59 | promises accumulate. Daily is too granular to see project-level drift; monthly lets loops rot. |
| 60 | - **Same time, same trigger.** The canonical recommendation (echoed by every serious GTD guide) is |
| 61 | a recurring, protected block — commonly Friday afternoon or Sunday evening — anchored to an |
| 62 | existing rhythm so the review doesn't depend on motivation. |
| 63 | - **Timeboxed.** One to two hours. A review that regularly takes three hours gets skipped the |
| 64 | moment a week is busy, and skipped reviews are how the habit dies. Better a 45-minute honest |
| 65 | pass with steps explicitly skipped-with-reason than a marathon that happens twice and never again. |
| 66 | - **The review is steering, not rowing.** Forte's periodic-review framing and Allen's original |
| 67 | agree: during the review you decide and route; you do not execute (two-minute items excepted). |
| 68 | A review that turns into a work session never finishes. |
| 69 | |
| 70 | ## What "done" means |
| 71 | |
| 72 | The review is complete when: every inbox is empty, every open loop found is on a list, every |
| 73 | active project has one next action, both calendars have been swept, every waiting-for has been |
| 74 | touched, and someday/maybe has been consciously kept or culled. That definition is checkable, |
| 75 | which is why this skill gates it with a script instead of a feeling. |
| 76 | |
| 77 | ## Sources |
| 78 | |
| 79 | 1. David Allen, *Getting Things Done: The Art of Stress-Free Productivity* (Penguin, original |
| 80 | edition 2001; revised edition 2015) — chapter on the power of the weekly review; the "critical |
| 81 | success factor" claim; the two-minute rule; the project/next-action distinction. |
| 82 | 2. David Allen, *Ready for Anything: 52 Productivity Principles for Getting Things Done* (Viking, |
| 83 | 2003) — principles on review cadence and why unrenegotiated commitments erode self-trust. |
| 84 | 3. GTD® methodology guides, gettingthingsdone.com (David Allen Company) — the official Weekly |
| 85 | Review® checklist with the GET CLEAR / GET CURRENT / GET CREATIVE structure used here. |
| 86 | 4. Tiago Forte, *Building a Second Brain* (Atria, 2022) and the PARA method essays (fortelabs.com) |
| 87 | — periodic review as the maintenance loop of any personal knowledge system; weekly review as |
| 88 | routing, not execution. |
| 89 | 5. Doist, "The Complete Guide to Getting Things Done" (todoist.com/productivity-methods) — a |
| 90 | widely used practitioner's walkthrough of the weekly review steps and common adaptations. |
| 91 | 6. Cal Newport, *Deep Work* (Grand Central, 2016) and the weekly-planning essays at |
| 92 | calnewport.com — weekly planning as the scale at which meaningful work is steered; the |
| 93 | shutdown-ritual analogue of closing loops before rest. |
| 94 | 7. Francis Wade, *Perfect Time-Based Productivity* (2014) — on why review cadences fail and how |
| 95 | habit load, not intention, predicts whether a review sticks. |
文件内容是平台检查时读出的文本，只供查看。平台不会运行包里的任何脚本或程序。
