Annual goals usually fail in a predictable way: a fast January, a quiet spring, and a scramble in November. The deadline is so far off that no single week feels like it matters, so the important work keeps losing to whatever is urgent today.
The 12-Week Year fixes this by shrinking the “year” to 12 weeks. You pick one to three goals, turn each into a short list of weekly actions, and score yourself every week on whether you did those actions. A 13th week closes the cycle with a review and a reset. Below is how to set it up, how it compares with other goal systems, and where it usually breaks.
Where the 12-Week Year comes from and why it works
The method comes from Brian P. Moran and Michael Lennington, whose book The 12 Week Year argues that annualized thinking is the problem: when you plan in years, there is always time to catch up later. Treat 12 weeks as the whole year and each week carries the weight a month used to.
The evidence on annual goals supports the diagnosis. In a study of New Year’s resolutions, fewer than half of resolvers were still on track six months in. Long horizons leave a lot of room for drift.
Three mechanisms explain why a shorter cycle helps:
- Proximity. A deadline 12 weeks out feels real. Moderate urgency raises norepinephrine and sharpens attention, though arousal follows an inverted-U curve: past a certain point, pressure turns into anxiety and performance drops. The goal is a steady push, not a permanent emergency.
- Specificity. Decades of goal-setting research show that specific, challenging goals combined with regular feedback beat vague “do your best” intentions. The 12-Week Year forces both.
- Fast feedback. You find out in week 3 that a tactic isn’t working, not in month 9.
Setting up your first cycle
1. Write a one-page long-term vision
Moran and Lennington start with vision because a 12-week goal with no larger purpose is easy to abandon in week 7. Write a few sentences about where you want your work and life to be in about three years, then one paragraph on what the next 12 weeks should contribute to that.
2. Choose one to three 12-week goals
For a first cycle, one goal is often enough. Each goal needs a number and a finish line: “40 paid sign-ups for the new course by week 12” works; “grow the course business” does not.
If a goal is too big for 12 weeks, carve out the slice that is achievable, using the approach in breaking big goals into actionable steps.
3. Turn each goal into weekly tactics
A tactic is an action you fully control, with a due week attached. “Record two lessons” is a tactic. “Get 10 sign-ups” is an outcome. Keep it to three to six tactics per goal; more than that and the weekly plan becomes a to-do list you can never finish.
Write each tactic with its frequency and the weeks it runs: “Send 5 personal outreach emails, Mon to Fri, weeks 2 to 12.” This is the core of the plan, and it is also where most people go wrong.
4. Block performance time
The book recommends three kinds of calendar blocks: a weekly strategic block of about three uninterrupted hours for your most important tactics, short daily buffer blocks for email and small requests, and a weekly breakout block of time off work entirely. If you already use time blocking, add these categories to your existing calendar rather than building a second system.
5. Score every week
At the end of each week, count the tactics you planned and the ones you completed. That percentage is your execution score. Moran and Lennington suggest that 85% or higher usually produces the outcome, even if you never hit 100%.
Write the score down and, if you can, share it. A meta-analysis of 138 studies found that monitoring progress improves goal attainment, especially when progress is physically recorded or reported to others. The book’s version is a short weekly accountability meeting with a peer or two; the guide to social accountability covers how to set one up.
6. Protect the 13th week
This final week is not spare capacity for unfinished tactics. Use it to review the full cycle, rest, and draft the next plan. Skipping it is how a 12-week sprint quietly becomes a 52-week grind.
Worked example: a week 5 scorecard
A yoga instructor is launching a paid online mini-course on morning mobility and has one 12-week goal: 40 paid sign-ups by week 12. Lead indicators are the tactics they control; the lag indicator is the result those tactics should move.
| Lead indicator (tactic) | Planned days | Completion | Lag indicator (outcome) |
|---|---|---|---|
| Film and edit 2 course sessions (90-minute block) | Tue, Thu | 2 of 2 (100%) | Sessions finished: 9 of 16 |
| Write one blog post answering a common student question | Mon, Wed | 1 of 2 (50%) | Waitlist sign-ups this week: 6 |
| Send 5 personal emails to past studio students | Mon to Fri | 4 of 5 (80%) | Free taster classes booked: 2 |
| Review landing page analytics, adjust one element | Fri | 1 of 1 (100%) | Page conversion: 3.1% |
| Week total | 10 planned | 8 of 10 (80%) | Paid sign-ups to date: 21 of 40 |
The score is just under the 85% line, and the gap is clear: the blog post tactic slipped. Halfway through, 21 of 40 sign-ups is roughly on pace, so the problem is execution, not strategy. Move the writing sessions into the strategic block instead of rewriting the plan.
Compare that with week 8, if the execution score sits at 95% but sign-ups stall at 24. Now the tactics themselves are the problem, and that is the moment to change them, for example swapping blog posts for two free live classes that end with a course invitation.
12-Week Year vs other goal systems
| Approach | Horizon | What you measure | Best when | Weak spot |
|---|---|---|---|---|
| 12-Week Year | 12 weeks plus a review week | Weekly execution score and outcome | You know what to do but keep not doing it | Heavy weekly admin if you track too many tactics |
| OKRs | Usually a quarter | Key results (outcomes) | You need ambitious targets aligned with a team | Says little about daily actions |
| Annual goals | 12 months | Year-end result | Slow, seasonal goals such as a degree | Drift and late-year cramming |
| Streak or chain tracking | Open-ended | Daily yes or no | A single habit, like writing daily | No finish line or outcome check |
These combine well. Many people set an OKR-style objective for the quarter and then run the 12-Week Year’s tactic scoring underneath it.
Scorecard mistakes that sink a cycle
- Tactics that are really outcomes. “Get 3 clients” can’t be scored as done or not done this week. Rewrite every tactic as an action that starts with a verb you control: send, record, draft, call.
- Too many goals. Three goals with five tactics each is 15 weekly commitments plus your actual job. If your first two scores are below 60%, cut a goal rather than trying harder.
- Scoring only outcomes. Outcomes lag by weeks. If you only look at sign-ups, a bad week 3 feels like failure even when you did everything right.
- Quitting after one bad week. A 40% week is information, not a verdict. Score it, note the cause, and plan next week normally.
- Redesigning the plan every Friday. Change tactics only when a high execution score isn’t moving the outcome, as in the week 8 example. Low scores call for better execution, not a new plan.
- Filling the review week with catch-up work. Unfinished tactics roll into the next plan, where you decide whether they still deserve a slot.
Checklist for planning your next cycle
Use this during week 13. It pairs well with a broader quarterly review if you want to check alignment across all areas of life.
- Average your 12 weekly execution scores and note which weeks fell below 85%, and why.
- Record each goal’s final outcome against its target.
- List the tactics that moved the outcome and those that didn’t.
- Reread your long-term vision and adjust it if your priorities have shifted.
- Choose one to three goals for the next 12 weeks, each with a number and a finish line.
- Write three to six tactics per goal, each with frequency and weeks.
- Put the strategic, buffer and breakout blocks on your calendar for week 1.
- Set the weekly scoring time and, if you use one, the accountability meeting.
Run one full cycle before judging the method. Most of the value shows up in the second cycle, when you plan with 12 weeks of real execution data instead of guesses.
