references/time_blocking_method.md
6.1 KB查看排版效果| 1 | # The Time-Blocking Method — Plan Every Minute, Revise Without Guilt |
| 2 | |
| 3 | > Reference for `time_block_planner.py`. The mechanics of turning a task list into a |
| 4 | > time-blocked day: why every minute gets a job, how big blocks should be, why buffers and |
| 5 | > revision are part of the method (not failures of it), and why the day needs a hard stop. |
| 6 | |
| 7 | ## 1. Plan every minute |
| 8 | |
| 9 | Newport's core scheduling rule: **give every minute of the workday a job.** At the start of the |
| 10 | day (or the evening before), divide the hours into blocks and assign each block to an activity — |
| 11 | including lunch, buffers, and an explicit "flex" block. The point is not rigidity; it is that an |
| 12 | unassigned minute defaults to the path of least resistance, which is almost always shallow: |
| 13 | inboxes, feeds, "quick checks." |
| 14 | |
| 15 | Newport's own estimate from years of running this system: a time-blocked hour is worth roughly |
| 16 | **1.5-2x** an unstructured hour of the same nominal work, because decisions about *what to do |
| 17 | next* are made once, in batch, instead of continuously under depletion. |
| 18 | |
| 19 | The planner enforces this literally: its output timeline is gap-free from `--start` to `--end`. |
| 20 | Anything not claimed by a deep block, shallow batch, buffer, or lunch becomes a named **flex |
| 21 | block** — scheduled slack, not accidental drift. |
| 22 | |
| 23 | ## 2. Block sizes |
| 24 | |
| 25 | - **Deep blocks: 90 minutes minimum.** Entry into real concentration is slow (see the canon |
| 26 | reference on flow and attention residue); a 30-minute "deep" block spends most of itself |
| 27 | ramping. The planner widens any deep task below 90 minutes up to the floor and says so. |
| 28 | - **Shallow batches: consolidated, not sprinkled.** Shallow tasks are individually small; their |
| 29 | cost is the switch, not the task. Batching them into one late-morning and one end-of-day window |
| 30 | converts a dozen context switches into two. |
| 31 | - **Buffers: 10 minutes between work blocks.** Attention residue needs somewhere to drain. |
| 32 | Buffers are also where the tiny physical resets live — stand up, water, close the previous |
| 33 | block's tabs. |
| 34 | |
| 35 | ## 3. Implementation intentions — why written blocks beat willpower |
| 36 | |
| 37 | The psychology underneath time-blocking is Gollwitzer's research on **implementation intentions** |
| 38 | (1999): plans of the form "at time X in situation Y, I will do Z" dramatically outperform bare |
| 39 | goal intentions ("I'll write the spec this week"). Meta-analytic effect sizes are medium-to-large |
| 40 | (d ≈ .65 across ~94 studies in Gollwitzer & Sheeran's later review). A time-block is exactly an |
| 41 | implementation intention: the when and where are pre-decided, so the depleted 2 p.m. self doesn't |
| 42 | renegotiate the plan — it just follows it. |
| 43 | |
| 44 | Nir Eyal (*Indistractable*) builds his "timeboxing" chapter on the same foundation and adds the |
| 45 | inversion that matters for auditing: **"you can't call something a distraction unless you know |
| 46 | what it distracted you from."** Without a time-blocked plan there is no such thing as |
| 47 | off-plan behavior — which is why the planner runs *after* the shallow audit has decided what |
| 48 | deserves time at all. |
| 49 | |
| 50 | ## 4. Rescheduling without guilt |
| 51 | |
| 52 | Every practitioner's day breaks by mid-morning. Newport's rule (*The Time-Block Planner*): the |
| 53 | plan's value survives its own destruction. When a block is blown up — an incident, an overrun, a |
| 54 | surprise call — you do not abandon the system; you **redraw the remaining blocks at the next free |
| 55 | moment**. His planner pages literally provide columns for multiple revisions of the same day. The |
| 56 | goal, in his words, is not to win a fight against a changing schedule; it is "to maintain, at all |
| 57 | times, a thoughtful say in what you're doing with your time going forward." |
| 58 | |
| 59 | Two disciplines follow: |
| 60 | |
| 61 | 1. **Revision is normal.** Re-run the planner with the surviving tasks and the current time as |
| 62 | `--start`. Same rules, shorter day. |
| 63 | 2. **Overflow is a decision, not an accident.** If the redrawn day no longer fits, something gets |
| 64 | deferred by name. The planner's exit-2 overflow refusal forces that choice to be explicit. |
| 65 | |
| 66 | ## 5. Fixed-schedule productivity — the hard stop |
| 67 | |
| 68 | Newport's "fixed-schedule productivity" (first described on his Study Hacks blog, later formalized |
| 69 | in *Deep Work*, Rule #4): **fix the endpoint of the workday first — then work backward from it.** |
| 70 | The hard stop functions as a forcing constraint: it makes shallow-work budgets real, forces |
| 71 | ruthless triage of commitments, and converts "I'll just stay late" from a safety valve into a |
| 72 | visible system failure. |
| 73 | |
| 74 | Parkinson's observation (*The Economist*, 1955) — "work expands so as to fill the time available |
| 75 | for its completion" — is the mechanism the hard stop exploits in reverse: bounded time compresses |
| 76 | work back toward its true size. This is why `--end` in the planner is immovable and why shallow |
| 77 | overflow past it is a refusal (exit 2, naming what to defer) rather than a silent extension of the |
| 78 | evening. |
| 79 | |
| 80 | ## Sources |
| 81 | |
| 82 | 1. Cal Newport, *The Time-Block Planner: A Daily Method for Deep Work in a Distracted World* (Portfolio, 2020) — plan every minute, revision columns, the 1.5-2x estimate. |
| 83 | 2. Cal Newport, *Deep Work*, Rule #4 "Drain the Shallows" (Grand Central, 2016) — schedule every minute; fixed-schedule productivity as a forcing function. |
| 84 | 3. Cal Newport, "Fixed-Schedule Productivity: How I Accomplish a Large Amount of Work in a Small Number of Work Hours" (Study Hacks blog, calnewport.com, 2008) — the original formulation of the hard stop. |
| 85 | 4. Peter M. Gollwitzer, "Implementation Intentions: Strong Effects of Simple Plans," *American Psychologist* 54(7), 1999; and Gollwitzer & Sheeran, "Implementation Intentions and Goal Achievement: A Meta-analysis," *Advances in Experimental Social Psychology* 38, 2006. |
| 86 | 5. Nir Eyal, *Indistractable: How to Control Your Attention and Choose Your Life* (BenBella, 2019) — the timeboxing chapter; "you can't call something a distraction unless you know what it distracted you from." |
| 87 | 6. C. Northcote Parkinson, "Parkinson's Law," *The Economist*, November 1955 — work expands to fill the time available. |
| 88 | 7. Paul Graham, "Maker's Schedule, Manager's Schedule" (paulgraham.com, 2009) — why deep blocks must be defended as contiguous half-day units. |
文件内容是平台检查时读出的文本，只供查看。平台不会运行包里的任何脚本或程序。
