How to Run a 12-Week Year: A Step-by-Step Guide

Meta description: A clear, step-by-step guide to running your first 12-Week Year — vision, goals, weekly tactics, scorecard, and the Week 12 review that closes the loop.

Tags: 12 week year, goal execution, weekly planning, planning system, how to

Reading about the 12-Week Year is easy. Running one requires a specific sequence that most overviews leave vague.

This guide covers the exact steps, in order, so that by the end you have a working cycle — not just a good understanding of the concept.

Why the First Week Determines the Next Eleven

The most common mistake people make when starting a 12-Week Year is treating week one as week one of execution. It isn’t. Week one is the design week.

Brian Moran and Michael Lennington are explicit about this in The 12-Week Year (2013): the planning work done in week one creates the architecture that the remaining eleven weeks execute against. Skimping on week one — writing vague goals, skipping the vision, producing an incomplete tactic list — means the scorecard has nothing rigorous to measure.

Spend two to three hours on week one. That is a small investment relative to the eleven weeks of execution it enables.

Step 1: Write Your 12-Week Vision

Start with vision, not goals. A vision is a concrete description of what you want your life or work to look like at the end of the 12 weeks — specific enough that a third party could assess whether you achieved it.

A poor vision: I want to be more productive and grow my business.

A useful vision: At the end of this cycle, I have signed three new enterprise clients, our product has shipped the billing integration, and I am consistently leaving the office by 6pm.

The vision does two things. It establishes direction — so that your goals point toward something coherent rather than pulling in different directions. And it creates a concrete end-state that makes the Week 12 review unambiguous.

Write this in one paragraph. If it runs to three paragraphs, it is a wish list, not a vision.

Step 2: Set No More Than Three Goals

From your vision, extract the two or three outcomes that, if achieved, would make the vision real.

Each goal should be:

• Outcome-specific: Not “improve our sales process” but “close five new clients.”
• Time-bound: “By the end of Week 12” is the only acceptable deadline.
• Personally controlled: Goals that depend entirely on other people’s decisions are not useful here.

If you have four strong candidates, drop one. The constraint is the point. Every goal you add dilutes the attention and energy available for the others.

Step 3: Build Your Weekly Tactic List

For each goal, identify the weekly activities — tactics — that will drive the outcome. These are not milestones or sub-goals. They are specific, repeatable, countable actions.

Goal: Close five new clients by Week 12.

Weekly tactics:

• Send 15 cold outreach messages
• Conduct two discovery calls
• Follow up with three warm leads
• Review pipeline for stalled deals

These tactics are the inputs. The goal is the output. Your scorecard measures the inputs because those are what you control.

A useful test: if you cannot count whether a tactic was completed by end of day Friday, it is too vague. “Think about pipeline” fails the test. “Review CRM for stalled deals and send follow-up to each” passes it.

Step 4: Create Your Scorecard

The scorecard is a simple weekly table. Across the top: weeks 1–11. Down the left: each tactic.

Each week you mark each tactic as done (1) or not done (0). Your weekly execution score is the percentage of tactics completed. If you had 12 planned tactics and completed 10, your score is 83%.

Moran’s target is 85%. In their practice across many clients, they observed that sustained execution at 85% or above reliably correlated with goal achievement. Below 85%, goal attainment dropped sharply.

You do not need a sophisticated tool for this. A spreadsheet with conditional formatting works fine. What matters is that you update it every week, honestly.

Step 5: Run the Weekly Review (15 Minutes)

Each week — not when you feel like it, every week — spend fifteen minutes on the review. Three questions:

What was my execution score? Calculate it. Write it down. Resist the urge to estimate.

What patterns explain the gaps? Did you miss the same type of tactic repeatedly? Did life events cluster around certain activities? Patterns are more useful than one-off explanations.

What is one adjustment for next week? Not a redesign — a micro-correction. If you planned 15 outreach messages but only sent 8, the adjustment might be blocking a specific two-hour window on Tuesday morning rather than leaving it unscheduled.

The review needs to stay at fifteen minutes. Longer reviews are usually a sign that you are relitigating goal choices rather than executing. Save strategic reconsideration for Week 12.

What to Do When the Plan Breaks

It will break. A project fires unexpectedly, a health issue disrupts a week, a priority shifts.

When this happens, the 12-Week Year is not an excuse to ignore reality and grind through unchanged. It is a system for making explicit decisions about trade-offs.

If a week is disrupted, mark it honestly on the scorecard. If you need to drop a tactic permanently because circumstances changed, revise the plan and document why. If a goal becomes irrelevant mid-cycle, you can replace it — but do this consciously, not by quietly abandoning it and hoping the scorecard doesn’t notice.

The system works because it creates accountability through visibility. Fudging the scorecard defeats the only mechanism that makes the urgency real.

Step 6: Run the Week 12 Review

The final week is for review, not execution. Clear your schedule of new project work as much as possible.

Assess four things:

Goal achievement: Did you hit the stated outcomes? Yes, partial, or no — be specific.

Average execution score: What was your mean weekly score across all 11 execution weeks? This is your single most diagnostic number.

Pattern analysis: Which tactics did you most consistently drop? Which goals were most and least aligned to what you actually spent time on?

What carries forward: Which goals roll into the next cycle, which are complete, and which you are deliberately dropping.

The Week 12 review takes roughly two hours. It is the best two hours you can spend before starting again.

The Buffer Week: Why to Take It Seriously

After Week 12 and before the next cycle starts, Moran recommends a break. Even a few days of operating without a scorecard allows the mental reset that sustains multi-cycle performance.

Practitioners who skip the buffer and run straight from one cycle into the next typically report declining execution quality and growing resentment of the system around cycle three or four. The buffer is not optional downtime — it is recovery that protects the next cycle.

A Sample Rhythm for the Whole Cycle

If you run four full cycles per calendar year (three months each plus a buffer week), you complete roughly four “years” of goal progress in twelve months. That is the arithmetic behind Moran and Lennington’s claim that the system produces results faster than annual planning.

Your next step: Open a document and write your 12-week vision. One paragraph, specific enough that you could hand it to someone else and they could tell you in Week 12 whether you hit it or not. That paragraph is all you need to start.