Every January I used to write a plan for the year. By March I’d stopped looking at it, and by June I couldn’t remember where I’d saved it.
The plans weren’t bad. The container was. A year is long enough to always feel like there’s time, so nothing is urgent until it’s too late. What finally worked wasn’t a better app. It was a smaller container: twelve weeks, three goals, one page.
This is the practical version. The story of why I needed it is in Too many ideas, three at a time.
Why twelve weeks works
Three findings from psychology explain it better than I can:
- We underestimate how long things take. In a classic study, students expected to finish their thesis in about 34 days. It took them 56. This is the planning fallacy, and a year gives it months to hide.
- Effort rises near the finish line. Members of a café’s reward scheme bought coffee more often the closer they got to a free one. This is the goal-gradient effect, and a twelve-week cycle keeps the finish line in sight.
- Fresh starts motivate. People are more likely to act on a goal after a “temporal landmark”, such as a new week, a new month or a birthday. Every new cycle is one.
The twelve-week idea comes from Brian Moran and Michael Lennington’s The 12 Week Year. What I added is a hard limit.
Three goals, no more
Three is small enough to hold in my head, and the limit forces a choice, which is the part I always avoided. When a new idea turns up mid-cycle, and it always does, it doesn’t get deleted. It gets parked: written down, dated and left alone until the next cycle. “Not now” is far easier to say than “no”.
How it works
The system has four layers, and each one only looks one level up. On a Tuesday I don’t think about my ten-year vision. I look at this week’s page, which points to projects, which point to the cycle.
1. Goals. A short list of outcomes, each with a horizon and a reason.
2. The cycle. Twelve weeks of work plus a thirteenth week to review and rest, so four cycles fit in a year. For each of the three goals I write down what done looks like at week 12, the projects that will get it there, and how I’ll score the week.
3. Projects. Each has one status: focus (this cycle, three at most), active, next, parked or done. Parked is the important one. It’s where good ideas wait without stealing the cycle.
4. The week. One page for the whole cycle, newest week on top, and three focus tasks a week pulled from focus projects. Each day has the same shape, which I call 3-3-3: one block of deep work of about three hours, three short tasks that move something forward, and three maintenance tasks such as admin, email and errands. On clinical days the deep-work block is usually the job itself, and that’s fine.
The weekly review
This is the engine. Once a week, in about twenty minutes:
- Score the week: the share of planned tasks I actually did.
- Decide on every unfinished task: carry it
[>], send it back to its project[<], or drop it[-]. - Check each focus project. Is it still the right thing?
- Plan next week’s three focus tasks, each with a day and a time.
Moran and Lennington treat 85% as the mark of a good week. I’m happy around 80%. Hitting 100% every week means I’m planning too little. Below 60% for a few weeks means the plan is wrong, not me, and something gets cut.
The day and time in step four matter more than they look. “Work on the article” is a wish. “Tuesday, 6 am, kitchen table: draft the first section” is a plan. Psychologists call these implementation intentions, and deciding when and where makes people much more likely to follow through. James Clear builds part of Atomic Habits on the same idea.
What it borrows
Almost nothing here is original. Each piece fixed one problem for me:
| Idea | Source | How I use it |
|---|---|---|
| 12-week cycles and a weekly score | The 12 Week Year | The cycle and the score |
| The weekly review | David Allen, Getting Things Done | Twenty minutes, every week |
| Projects vs ongoing areas | Tiago Forte, the PARA method | Project statuses and parked |
| Protected focus time | Cal Newport, Deep Work | The daily deep-work block |
| The rule of three | J.D. Meier, Getting Results the Agile Way | Three goals, three focus tasks |
| Implementation intentions | Peter Gollwitzer; Atomic Habits | A day and a time for each task |
I keep all of it in my notes, linked the same way as my clinical ones (see Notes that grow instead of piling up), but nothing here depends on an app. It works on paper too.
If you want to try it
- Write down every goal you have, then pick three for the next twelve weeks.
- Mark everything else as parked. Don’t delete it.
- Make one page for your weeks and plan this one: three focus tasks, each with a day and a time.
- Review on Friday and score the week.
Do that for a single cycle before adding anything else. Most of the value comes from the limit, not the tools.
References
- Moran, B. P. & Lennington, M. (2013). The 12 Week Year: Get More Done in 12 Weeks than Others Do in 12 Months. Wiley. wiley.com
- Buehler, R., Griffin, D. & Ross, M. (1994). Exploring the “planning fallacy”: Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366–381. doi:10.1037/0022-3514.67.3.366
- Kivetz, R., Urminsky, O. & Zheng, Y. (2006). The goal-gradient hypothesis resurrected: Purchase acceleration, illusionary goal progress, and customer retention. Journal of Marketing Research, 43(1), 39–58. doi:10.1509/jmkr.43.1.39
- Dai, H., Milkman, K. L. & Riis, J. (2014). The fresh start effect: Temporal landmarks motivate aspirational behavior. Management Science, 60(10), 2563–2582. doi:10.1287/mnsc.2014.1901
- Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493–503. doi:10.1037/0003-066X.54.7.493
- Clear, J. Implementation intentions. jamesclear.com
- Allen, D. The GTD weekly review checklist. gettingthingsdone.com
- Forte, T. (2017, revised 2023). The PARA method. fortelabs.com
- Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central. hachettebookgroup.com
- Meier, J.D. (2010). Getting Results the Agile Way. The rule of 3, explained. gettingresults.com