A year gives procrastination too much room to negotiate. The 12 Week Year brings the finish line close enough to shape this week’s choices.
Brian Moran and Michael Lennington’s system connects a longer-term vision to a short execution cycle: choose a few outcomes, plan weekly actions, score what you did, and adjust. Twelve weeks is 84 days; “90-day plan” is a common shorthand, not the exact duration.
Copy the plan · See the scorecard · Handle a bad week
Copy your 12-week plan
Begin with one goal. Add another only if you can show where its work fits.
MY 12-WEEK PLAN Start date: End of week 12: Why this matters beyond the next 12 weeks: One outcome I want by the finish: Current starting point: This week’s actions — include frequency and a clear finish 1. 2. 3. Calendar slots: What I will stop or defer to make room: Weekly review Actions completed / actions planned: What changed in the outcome: What got in the way: One adjustment for next week: After week 12 What I will review, celebrate, and carry forward: When I will rest and plan the next cycle:
The plan is not credible until it says what will leave your calendar. A shorter deadline does not create extra hours.
The chain: vision, goals, tactics, score
Imagine you want to publish a small newsletter. Your longer-term aim is to build a useful body of writing. For this cycle, choose “publish six useful issues over twelve weeks,” starting from zero.
A two-week publishing rhythm gives each issue time for research, drafting, feedback, and editing. Subscriber growth can be watched, but it is not fully under your control.
For the first week, choose actions such as:
- Draft the opening Tuesday, 7:00–7:30.
- Draft the practical example Thursday, 7:00–7:30.
- Ask one intended reader for feedback Friday.
- Read the response and choose one revision Sunday.
The following week has a different plan: finish, edit, and publish. Tactics should serve the stage of the project, not recur forever because a template says so.
Score actions without gaming the number
The weekly execution score is completed planned actions divided by planned actions, multiplied by 100.
| Planned action | Completed? |
|---|---|
| Draft the opening | Yes |
| Draft the example | Yes |
| Request feedback | Yes |
| Review the response | No |
Three out of four is 75%. If you split every small step into a separate task, you can inflate the score without improving the result. Define meaningful actions before the week begins and use the same level of detail throughout it.
The authors use 85% as an execution benchmark. Treat it as a prompt to review the plan, not a scientific threshold or a guarantee of success. With four equally weighted actions, the possible scores jump from 75% to 100%; chasing exactly 85% would be pointless.
When the score and the result disagree
Low execution does not prove the plan was good. Perhaps Sunday was unavailable, the action was too big, or the feedback had not arrived. In that last case, note the dependency and choose a follow-up; do not invent a completed review.
High execution does not guarantee the right tactics. You can finish every planned action and publish something readers do not find useful. Watch the outcome as well: issues shipped, reader feedback, and whether the work serves the original aim.
One quiet result week does not prove failure. Some results lag behind effort. Use the review to distinguish delay from a pattern that calls for a change.
In the example, a missed Sunday review might move to Monday lunch. If feedback repeatedly arrives late, request it earlier or find another reader. The next plan should reflect the actual obstacle.
Where people actually quit
Too many goals. Carrying six annual ambitions into twelve weeks creates an impossible weekly plan. Start with one meaningful outcome.
Too much scoring. You need a few actions and a clear count, not a dashboard with twenty metrics. A note is enough.
No room to recover. If a week disappears, calculate what remains and reduce scope or change the date when needed. Do not double the workload automatically.
No end to the cycle. Reserve time after week twelve to review, recover, and decide what deserves another cycle. The system should create a rhythm you can continue.
Use the weekly review template for the conversation, and the goal-tracking guide for a numerical example of adjusting pace.
Where TaskCoach.AI fits
TaskCoach can hold the goal, its scheduled tasks, and the completion record you use at review time. Keep the four planned actions visible and calculate the execution score from that agreed set. Do not substitute a general app score or XP total for the method’s percentage.
Premium goal features and AI reports offer additional structure and reflection on recorded activity. They do not replace your decision about whether the tactics are working. We build TaskCoach; the core task and manual planning tools are free.
Start one cycle with one goal. Make week one small enough to execute and specific enough to learn from.