Break a Goal into a 12-Week Plan with One Prompt
What’s in this guide
The short version: twelve weeks is long enough to finish something real and short enough that the end is visible from the start. Decompose the goal into weekly outcomes rather than tasks, leave two weeks deliberately empty, and define what week one produces before anything else.
A year is too long to feel urgent and a month is too short for anything substantial. The productivity guide covers the weekly layer; this is the one above it.
Outcomes, not tasks
Each week gets a thing that will be true at the end of it, not a list of activities.
“Work on the website” is an activity and can absorb infinite time while producing nothing. “The about page is written and live” is an outcome — it is either true on Sunday or it is not, and if it is not you learn something in week two rather than week nine.
This is the entire difference between a plan that reports progress and one that reports effort.
Two weeks stay empty
Twelve weeks, ten outcomes. Weeks six and eleven have nothing planned in them.
Not buffer at the end — buffer at the end gets consumed by week three and then the plan is behind for the remaining nine, which is where the abandonment happens. Two empty weeks in the middle absorb the illness, the work crisis and the fortnight when nothing gets done, and the plan is still intact afterwards.
If the empty weeks are not needed, you finish early. That has never once been a problem.
The prompt
Week one has to be finishable in one sitting
The most dangerous week is the first, because a plan that starts with something big produces a week one that ends in “made a start”, and a plan that has never been finished once is much easier to stop.
Make week one deliberately small. Register the domain. Write the first page. Do the one phone call the whole thing has been waiting on. It should feel almost trivially achievable, and finishing it is what makes week two happen.
The smallest version worth doing
The last question in the prompt is the one people find most useful and least expect.
Knowing the reduced version in advance means that when the plan hits trouble in week seven, the choice is between the full version and a smaller real thing — rather than between the full version and nothing, which is how goals get abandoned rather than trimmed.
Running it week to week
The twelve-week plan is not a weekly system. Each Sunday, one of its outcomes becomes an input to the ten-minute reset — usually one of the three things — and the rest of the plan stays out of the way.
Check the whole plan once, at week six, in the empty week. Not weekly: a plan you review every week becomes a plan you edit every week, and a constantly edited plan is a way of doing planning instead of doing the thing.
If the goal is really a habit rather than a project — something with no end state — this is the wrong tool and a tracker is the right one. The tell is whether you can name what you will have at the end.
The printable
The Weekly Planner has a line for the week’s outcome at the top, which is where the twelve-week plan touches the ordinary week. The other eleven outcomes stay filed.
Questions about 12-week plans
Why twelve weeks rather than a year?
A year is too far away to feel urgent, so the work drifts to the last month. Twelve weeks is long enough to finish something substantial and short enough that the end is visible from week one, which is what keeps it from becoming background.
Why leave two weeks empty in the middle?
Because buffer at the end gets consumed by week three, and then the plan is behind for nine weeks, which is where people abandon it. Empty weeks at six and eleven absorb the illness or the work crisis and leave the plan intact. If you do not need them, you finish early.
What is the difference between an outcome and a task?
An outcome is either true or not true by Sunday — the about page is written and live. A task is an activity that can absorb unlimited time while producing nothing, like work on the website. Outcomes report progress; tasks report effort.
How accurate are the weekly estimates?
Treat them as a rough ordering rather than a schedule — it has no idea how fast you work. What it is genuinely good at is decomposition and sequencing, and at noticing when a goal you stated as one thing is actually two.
What if I fall behind by week seven?
That is what the smallest-version-worth-doing question is for. Knowing the reduced version in advance means the choice is between the full plan and a smaller real thing, rather than between the full plan and nothing — which is how goals get abandoned rather than trimmed.