A year is too long to plan and too long to stay focused. That is the quiet flaw in every annual resolution: twelve months is an abstraction, and abstractions do not create urgency. By March, “this year” still feels infinite, so there is always tomorrow. The 12-week year fixes this by changing the unit of planning: instead of one 12-month marathon, you run four 12-week sprints, each with its own goals, its own scorecard, and its own finish line. Twelve weeks is short enough to feel urgent and long enough to accomplish something real. This guide walks you through the complete system β the philosophy, the sprint design process, the weekly execution rhythm, the scorecard, a fully worked example, and how to handle the sprints that go sideways.
The concept comes from the business world, where the “12-week year” framework reframed annual planning around the insight that urgency drives execution: most annual goals get 80 percent of their effort in the final quarter because deadlines concentrate action. Twelve-week cycles distribute that deadline energy across the whole year β every twelve weeks has the focus of a Q4. For personal New Year planning, the translation is natural: your resolutions get divided into seasonal campaigns, each short enough to sustain intensity and each ending with a built-in fresh start. Pair it with SMART goals for goal design, monthly check-ins for the review layer, and habit trackers for daily execution, and you have a complete operating system for the year.
Why 12 weeks works: the psychology of the sprint
Annual goals fail for predictable structural reasons, and the 12-week format addresses each one directly. Urgency: a deadline twelve months away creates no pressure today; a deadline eleven weeks away does. Parkinson’s law β work expands to fill the time available β means annual goals get annual timelines, most of them wasted. Twelve weeks compresses the timeline and concentrates effort. Focus: a year invites ten goals; a sprint forces two or three. The constraint is the feature β fewer goals mean deeper attention, and deeper attention means faster progress. Fresh starts: a stalled annual resolution dies quietly in March; a stalled sprint gets redesigned every twelve weeks. Four fresh starts a year means four chances to get it right, and the research on fresh-start motivation suggests each new beginning carries a real motivational boost. Feedback speed: annual goals give you one data point per year about what works; sprints give you four. Faster feedback means faster learning about your own patterns β which strategies work for you, which obstacles recur, which goals were wrong. Forgiveness: a bad month ruins an annual plan’s math; in a sprint system, it ruins three weeks of one quarter, and the next sprint starts clean. The system is resilient because its unit is small.
Designing your sprint: the 6-step setup
Set aside 90 minutes before each sprint (the week between sprints is ideal β more on that below). Work through these six steps in order.
Step 1: Choose 1β3 sprint goals (20 minutes)
A sprint holds one to three goals β never more. If you are new to the system, start with two: one outcome goal (lose 8 pounds, save $1,500, finish the certification) and one process goal (work out 4x/week, write 500 words daily). Look at your annual ambitions and ask: which two or three, pursued intensely for twelve weeks, would change my year the most? Everything else goes on the parking lot β a visible list of goals assigned to future sprints, so “not now” feels like sequencing rather than abandonment. Write each chosen goal as a SMART goal with a 12-week deadline; the sprint is short enough that vague goals get exposed fast.
Step 2: Define the tactics (20 minutes)
Goals are destinations; tactics are the weekly actions that get you there. For each goal, list the 3β5 recurring tactics β the behaviors you will execute weekly. “Lose 8 pounds” becomes: four workouts per week, meal-prepped lunches, 8,000 daily steps, no unplanned snacking after 8 p.m. “Finish the certification” becomes: three 90-minute study blocks weekly, one practice exam every other week, flashcards daily. Tactics must be fully within your control (you control workouts; you do not control the scale) and scheduled into your actual week β a tactic without a calendar slot is a wish. This is also where you write if-then plans for the sprint’s predictable obstacles: travel weeks, work crunches, holidays.
Step 3: Build the scorecard (10 minutes)
The scorecard is the sprint’s nervous system: a weekly record of tactic execution. Simple format β rows are tactics, columns are weeks 1β12, cells get the completion mark. Each week you compute an execution score: tactics completed divided by tactics planned, as a percentage. The target is 85%+; below 60% for two consecutive weeks triggers the mid-sprint review (Step 6’s troubleshooting). Crucially, you score execution of tactics, not achievement of the goal β because tactics are what you control. A sprint at 90% execution that misses the outcome still taught you something valuable about the goal’s design; a sprint at 40% execution teaches you only that the plan did not survive reality.
Step 4: Schedule the weekly review (5 minutes)
Pick a fixed 20-minute slot each week β Sunday evening works for most people β and put all twelve on the calendar now. The weekly review has a fixed agenda: score the week’s tactics, note what worked and what broke, confirm next week’s tactic schedule against the actual calendar (adjusting for travel, events, deadlines), and recommit. Twenty minutes, same time, every week. This is the heartbeat of the system; everything else is commentary. If you have an accountability partner, this is the natural slot to share your score.
Step 5: Plan the buffer week (10 minutes)
Between sprints, schedule a buffer week β the “13th week.” No new tactics, no pressure. Its jobs: score the finished sprint honestly, celebrate and extract lessons, rest deliberately, and design the next sprint using this same six-step process. The buffer week is what makes the system sustainable year-round: it prevents sprint fatigue, gives achievements their proper recognition, and ensures each sprint starts with a real plan rather than momentum fumes. Treat it as sacred β skipping the buffer week to “get a head start” is how people burn out by sprint two.
Step 6: Write the sprint commitment (15 minutes)
End setup by writing a one-page sprint commitment: the 1β3 goals, the tactics, the why behind each goal (five-whys deep β the sprint is short and intense, so the why must be strong), the known obstacles with if-then plans, and your signature and date. Post it where you will see it daily. This sounds ceremonial because it is β the written commitment converts intention into obligation, and the daily visibility keeps the sprint mentally present through week seven, when novelty has faded and the finish line still feels far.
The weekly execution rhythm: what the 12 weeks actually feel like
A sprint has a natural arc. Knowing it in advance helps you navigate each phase instead of being blindsided.
Weeks 1β2: Launch energy. Motivation is high, tactics feel novel, the scorecard fills satisfyingly. Use this phase to lock in the mechanics: confirm every tactic has a working cue and calendar slot, fix anything awkward now (the gym bag that is never packed, the study block that collides with a standing meeting). Do not add tactics in the excitement of week one β the sprint is designed at setup; execution is for following the design.
Weeks 3β6: The grind. Novelty fades; this is where sprints are won. The weekly review becomes essential β it is the external structure that carries you when internal motivation dips. Watch for the first broken week (it usually lands here) and respond with the never-miss-twice protocol, not with overhaul. If execution drops below 60% for two consecutive weeks, run the mid-sprint diagnostic: is it the tactics (too many, wrongly scheduled), the goal (no longer relevant), or life (a genuinely hard season)? Adjust tactics freely; question goals only in the buffer week.
Weeks 7β10: The acceleration. Something shifts around week seven: the finish line becomes imaginable, tactics start feeling automatic, and the scorecard shows a real record. Many people find these the most productive weeks of the sprint β the combination of established routine and approaching deadline is potent. Protect this phase: do not add new commitments, do not let others’ urgencies colonize your tactic slots. If you are behind on the outcome, this is the window for a focused push β add intensity to existing tactics rather than inventing new ones.
Weeks 11β12: The finish. Sprint to the line. In week 11, assess honestly what is achievable in the remaining days and focus tactics on the highest-leverage actions. Week 12 is for completion and documentation: finish strong, record final metrics, and write preliminary lessons while they are fresh. Then stop. The buffer week begins, and the discipline of stopping β of not bleeding the sprint into the buffer β is what keeps the system sustainable.
A fully worked example: one 12-week sprint, start to finish
Meet a composite example β Daniel, whose Sprint 1 (JanuaryβMarch) targets fitness and finances:
Sprint goals: (1) Lose 10 pounds by March 31. (2) Build a $1,500 emergency fund top-up by March 31. Tactics for goal 1: four 45-minute workouts per week (Mon/Wed/Fri/Sun mornings), 8,000 daily steps, meal-prepped lunches on weekdays, no unplanned food after 8 p.m. Tactics for goal 2: $125 automatic transfer every Friday, one no-spend weekend per month, sell unused electronics by February 15. If-then plans: if traveling, then hotel-gym bodyweight circuit + 10,000 steps; if a work dinner lands on a workout day, then the workout moves to 7 a.m. next day; if an unexpected expense hits, then the transfer drops to $75 that week (never zero).
Execution: Weeks 1β2 at 95% β launch energy. Week 4 dips to 62% (a work crunch kills two workout weeks); the weekly review diagnoses it, and Daniel moves Friday workouts to mornings permanently β execution recovers to 85%+. Week 8: the electronics sell for $340, ahead of schedule. Weeks 9β10: acceleration β workouts feel automatic, the fund crosses $1,000. Final scores: execution 87% average; outcomes: 9 pounds lost (goal: 10 β close, and the trajectory is clear), $1,620 saved (goal exceeded). Buffer week lessons: morning workouts survive work crunches, evening ones do not β Sprint 2 schedules everything before 9 a.m.; the no-spend weekend was miserable and unnecessary β dropped in favor of a weekly spending cap. Sprint 2 (AprilβJune): maintain fitness at 3x/week, add the professional certification goal. The year is now a series of winnable games, and Daniel has won the first one.
Mapping your year: the four-sprint calendar
Here is how a full year of sprints might flow. Adapt the themes to your own goals β the structure matters more than the specific allocation:
Sprint 1 (JanβMar): Foundation. Health and systems. This is the classic New Year sprint: establish the keystone habits (sleep, movement, planning ritual), stabilize finances, set up tracking. Goals that make every later sprint easier belong here. Buffer week: late March.
Sprint 2 (AprβJun): Growth. Career and skills. With health habits running on autopilot, attention frees up for the professional push β the certification, the portfolio, the promotion case, the side project launch. Spring energy helps; the lengthening days are a natural tailwind. Buffer week: late June.
Sprint 3 (JulβSep): Relationships and restoration. Summer is socially rich and routinely chaotic β plan for it rather than fighting it. Goals: deepen key relationships, take the real vacation, tackle the home project, restore energy. Lighter professional load by design; this sprint prevents the burnout that kills Q4. Buffer week: late September.
Sprint 4 (OctβDec): Finish and harvest. The year’s culminating push: complete the big professional goal, hit the financial target, finish the creative project. Holiday obstacles get if-then plans in advance. Buffer week: late December β which doubles as your annual review, feeding directly into next January’s Sprint 1 design. The year closes as a loop, not a cliff.
Notice what this calendar does to the traditional resolution arc: there is no March death, because Sprint 1 ends in March with a review and a fresh start. There is no “I’ll restart in January,” because every twelve weeks is January. And there is no December panic, because Sprint 4 was designed in September with full knowledge of the year’s trajectory.
Troubleshooting: when sprints go sideways
“I chose too many goals.” The classic setup error. If execution is below 60% by week 3 across the board, you overcommitted. Fix: demote the lowest-priority goal to the parking lot immediately β mid-sprint. A sprint with one goal at 90% beats a sprint with three goals at 50%. Note the lesson for next sprint’s setup: your capacity is now a measured fact, not a guess.
“Life exploded in week 5.” Illness, crisis, chaos. Fix: declare a sprint pause β one to two weeks of maintenance mode (minimum viable tactics only), then resume. If the disruption lasts longer, end the sprint early, take the buffer week, and design a recovery sprint with gentler goals. The system bends; the annual plan would have broken.
“I am executing at 90% but the goal is not moving.” The tactics are wrong, not the effort. This is actually good news β it is a design insight, not a discipline failure. Fix in the weekly review: interrogate the tactic-goal link. (Daniel’s hypothetical: workouts consistent but weight static β the nutrition tactic needs upgrading, not the workout count.) Adjust tactics mid-sprint freely; this is exactly what the fast feedback loop is for.
“I dread the weekly review.” Usually means the review has become a shame ritual. Fix: enforce the wins-first order, keep it to 20 minutes with a timer, and remember you are scoring tactic execution β a neutral operations metric, not your worth. If dread persists, the goal may be wrong; park the question for the buffer week rather than suffering through eight more reviews.
“The buffer week keeps getting skipped.” You finish a sprint and immediately start the next one. Fix: schedule the buffer week’s activities (the scoring session, the lessons write-up, a genuine rest day) as calendar appointments with the same seriousness as tactics. The buffer week is load-bearing β it is where learning compounds. Skipping it turns four sprints into one long grind, which is exactly what the system was designed to prevent.
Sprint zero: starting mid-year
You do not need January to start. If you are reading this in May, your Sprint 1 begins next Monday β twelve weeks from a date you choose, not a date the calendar chose. Run the six-step setup exactly as written, but scale the ambition slightly down for the first sprint: you are learning the system and your own capacity at the same time, and a modest sprint won cleanly teaches more than an ambitious one abandoned. Many practitioners actually prefer off-calendar starts β a September sprint that ends before the holidays, a June sprint built around summer β because the system was designed to make every twelve weeks a fresh January. The best sprint start date is the one you will actually honor, and that date is always now.
In Pictures: Planning in 12-Week Sprints
Twelve months is an abstraction, and abstractions don’t create urgency. Twelve weeks is a deadline you can feel.

The 12-week sprint: this year’s goals, compressed into quarters that create real urgency.
Watch: Planning in 12-Week Sprints
How to achieve in 12 weeks what you’d normally aim for in a year β the execution system behind the book.
At a Glance: Planning in 12-Week Sprints
The concepts behind the 12-week year, from periodization to the weekly scorecard.
| Concept | Detail | Source |
|---|---|---|
| The book | Brian Moran and Michael Lennington | The 12 Week Year |
| The idea | Periodization: treat 12 weeks as your βyearβ | Borrowed from athletic training cycles |
| Execution | A weekly scorecard on lead measures | Score your execution, not just results |
| Cycles | Four βyearsβ per calendar year | Four chances to win instead of one |
| The sprint | A 6-step setup plus a weekly rhythm | The post’s fully worked example |
Frequently Asked Questions
What is the 12-week year?
The 12-week year is a goal-setting framework that treats 12 weeks as a “year”: you set 1β3 goals per 12-week sprint, define weekly tactics, score execution weekly, and review and redesign every sprint with a buffer week between. It creates the urgency and focus of an annual deadline four times a year, so goals get consistent effort instead of a January burst and a December panic.
How is the 12-week year different from quarterly goals?
Quarterly goals share the timeframe but usually lack the system’s engine: the weekly execution score, the tactics-level planning, the fixed weekly review, and the buffer week for redesign. A quarterly goal without weekly scoring is just an annual goal cut into four pieces β it inherits the same drift. The 12-week year’s power is in the weekly rhythm and the execution score, not just the shorter horizon.
How many goals should I set per 12-week sprint?
One to three β never more. Each goal needs 3β5 weekly tactics, and tactics are what you actually execute, so three goals can mean fifteen weekly commitments. Start with two if you are new to the system. The constraint is deliberate: fewer goals mean deeper focus, and deep focus is what twelve weeks rewards. Everything else waits in the parking lot for a future sprint.
What do I do with my annual New Year resolutions in this system?
Divide them across the four sprints. Assign each resolution to the sprint where it fits best (health habits to Sprint 1, career push to Sprint 2, etc.), and convert each into a 12-week SMART goal with weekly tactics when its sprint arrives. Your annual vision becomes the parking lot’s organizing principle; the sprints become the execution vehicle. Review the annual vision each buffer week to keep the sprints aligned with the year you actually want.
What is an execution score and what is a good one?
Your execution score is the percentage of planned weekly tactics you actually completed β computed each week from your scorecard. Aim for 85% or higher; 60β80% means the sprint needs tuning; below 60% for two consecutive weeks triggers a diagnostic (wrong tactics? too many goals? life disruption?). Score execution, not outcomes β tactics are what you control, and high execution with a missed outcome is valuable data about the goal’s design.
Can I use the 12-week year alongside a word of the year or vision board?
Absolutely β they operate at different levels and combine beautifully. Your word of the year provides the compass (the quality you are cultivating), your vision board keeps the destination visible, and the 12-week sprints provide the engine (the tactics, scores, and deadlines that move you there). Compass, map, engine: direction, vision, execution. Together they cover everything a year needs.




