3D render of seven stacked paper task slips in a loose column on a plain sand-coloured background
Field notes · Planning

Plan around the week you actually have

Treat the week as a container with a fixed size, then ask a gentler question: what will reasonably fit?

Planning advice often assumes an empty calendar and limitless energy. Most of us have neither. These notes start from the time and attention you genuinely have, and build a plan that can bend when Wednesday arrives.

Why plans overflow

In 1979 Daniel Kahneman and Amos Tversky described the planning fallacy: our tendency to underestimate how long tasks will take, even when we know similar tasks ran late before. Roger Buehler, Dale Griffin and Michael Ross tested the idea in 1994 by asking students to predict when they would finish their theses. Most finished later than their own "realistic" estimates, and many finished later than their worst-case estimates too.

The British historian C. Northcote Parkinson offered an opposite warning in a 1955 essay for The Economist: work expands to fill the time available. Taken together, these ideas suggest that loose plans drift and tight plans break. The useful middle ground is a plan with honest estimates and deliberate slack.

A good plan is not the one with the most items. It is the one that survives Wednesday.

Start from capacity, not ambition

Oliver Burkeman's Four Thousand Weeks (2021) argues that the to-do list will never be finished, and that accepting this is freeing rather than defeatist. In practical terms, it means choosing what to leave undone on purpose, instead of letting the week choose for you.

A simple capacity audit helps. Count the hours already committed — meetings, commuting, caregiving, regular admin — and subtract them from your working week. What remains is the real budget for focused work, and it is usually smaller than the plan you had in mind.

An open paper weekly planner beside a pencil and a mug of coffee on a light wooden desk
A paper week makes trade-offs visible in a way an endless digital list rarely does.

Experiments to try

  1. Run a capacity audit on Monday morning. Write down the free hours for each day. Plan no more than one meaningful task for any day with fewer than two free hours.
  2. Choose one anchor per day. An anchor is the single task that would make the day feel worthwhile. Everything else is welcome but optional.
  3. Add a buffer. Leave roughly a fifth to a third of your free time unplanned. If the buffer goes unused, it becomes time for the next item — a pleasant surprise rather than a broken promise.
  4. Hold a ten-minute Friday review. David Allen's Getting Things Done (2001) popularised the weekly review. A short version — what moved, what stalled, what to drop — is often enough.
  5. Record one sign of progress each day. Teresa Amabile and Steven Kramer's The Progress Principle (2011), drawing on nearly 12,000 diary entries, found that progress in meaningful work was closely linked to good days at work.

Comparing planning approaches

Four planning approaches and where they fit
ApproachBest suited toPossible frictionOrigin
Time blockingPredictable days with calendar controlBreaks easily when meetings movePopularised by Cal Newport
Weekly reviewMany open loops across projectsCan grow into an hour-long ritualDavid Allen, GTD
Urgent/important sortTriage of a long listUrgent items still tend to dominateEisenhower matrix, popularised by Stephen Covey
One anchor per dayLow-energy or interrupted weeksLess suited to deadline sprintsCommon practice, adapted here

When the week falls apart anyway

Some weeks will be swallowed by illness, a family emergency or an urgent project. A plan with an anchor and a buffer degrades gracefully: you keep the anchor and let the rest go. If every week falls apart, the issue may be workload rather than planning skill, and that is worth naming plainly, to yourself and to whoever sets your priorities.

What this evidence cannot establish is the right number of tasks for you, or that any planning method will create more hours. Planning tends to help by reducing decisions and making trade-offs explicit, not by expanding capacity.

Sources mentioned

  • Kahneman, D. & Tversky, A. (1979). Intuitive prediction: biases and corrective procedures. TIMS Studies in Management Science.
  • Buehler, R., Griffin, D. & Ross, M. (1994). Exploring the planning fallacy. Journal of Personality and Social Psychology.
  • Parkinson, C.N. (1955). Parkinson's law. The Economist.
  • Burkeman, O. (2021). Four Thousand Weeks. Farrar, Straus and Giroux.
  • Allen, D. (2001). Getting Things Done. Viking.
  • Amabile, T. & Kramer, S. (2011). The Progress Principle. Harvard Business Review Press.