Why annual goals fail.
The Blueprint that fixes it.

Most annual goals are dead by February. The statistics on resolution failure are well-known — by mid-February something like 80% have been abandoned. The less-known statistic is that annual goals set without resolutions have similarly poor survival rates. The format of the annual goal is the problem, not the spirit of January. A goal written on the first of January cannot reliably survive contact with the third week of February. The goal hasn't done anything wrong; the planning artefact has.

The Annual Blueprint is the alternative. Not a goal-setting document — a planning architecture that connects values at the top to daily action at the bottom, with explicit translation layers between them. This post is what the Annual Blueprint does, why it survives where annual goals fail, and how it integrates with the rest of the Cascade.

Why annual goals fail structurally

A goal on its own is a wish. It states what you want to be true at the end of the year. What it doesn't do is structure the path from today to that end state. The path is what carries the work. Without the path, the goal sits at the top of a January page and slowly fades.

Three specific structural failures kill most annual goals:

• No connection to weekly action. You set the annual goal in January. You don't see it again until you write next year's goals in December. In between, the goal has no presence in any week. Your daily list is being filled by short-term pressure, not by anything traceable to the annual document.
• No domain spread. Most people set work goals because work is loud. Body, capital, and relationships get implicit or get omitted. By October the work goal has half-delivered while the body is in worse shape, the finances are about the same, and the marriage hasn't been actively invested in for nine months.
• No values anchor. The annual goal sits on its own without an explicit "why." Six months in, when the goal becomes hard, there's nothing underneath it to refer back to. The motivation runs out because there's no source.

The Annual Blueprint is built specifically to fix these three failures. It is not a goals page; it is a 24-page workbook that produces a connected architecture.

What the Annual Blueprint actually contains

Six sections, in order:

1. The previous year debrief. Ten questions, four hours, one written document. (See the post on the four-hour debrief.) Without this section the year ahead has no inheritance from the year behind.
2. The values revisit. Three to five values, rewritten or confirmed for this year. Linked to the Values Architecture if you're running the full Coaching series.
3. The central question. One question, in one sentence, that you intend to spend the year answering. The thematic spine.
4. The four domain outcomes. One outcome per domain — work, body, capital, relationships. The year's headline deliverables.
5. The four 90-day cycles. A one-page sketch of each of the four quarters. Q1 is detailed; Q2-Q4 are loose, to be filled in at the start of each quarter. (See how to plan a quarter.)
6. The annual review schedule. Dates for the four quarterly debriefs and the end-of-year debrief. Locked into the calendar before the year starts.

The whole document takes three to four hours to complete in one sitting. That is the upfront cost. The annual benefit is that every week of the year afterwards is operating from a structured architecture rather than from short-term pressure.

The cascade — what comes underneath

The Annual Blueprint is the second-from-the-top layer of the cascade. Above it sits the values document; below it sits everything else. The architecture flows downward:

• Values → what you organise life around. Three to five. Rewritten roughly annually.
• Annual Blueprint → four domain outcomes for the year, one central question, four quarterly sketches.
• 90-Day Goal Planner → three quarterly objectives drawn from the annual outcomes.
• Weekly Review → three weekly intentions drawn from the quarterly objectives.
• Daily Focus Sheet → three daily priorities drawn from the weekly intentions.

Each layer inherits from the one above. Nothing in the daily layer floats — every daily priority can be traced upward through weekly, quarterly, annual, to a value. This is the cascade. The Annual Blueprint is the layer where the year's overall shape gets defined; everything else inherits from it.

The first time you do it

The first Annual Blueprint takes longer than the subsequent ones. You're learning the framework while filling it in, and the debrief section in particular is hard the first time — you don't have a previous-year debrief to inherit from, so you're working from memory rather than from a structured prior document.

The honest expectation: first year takes six to eight hours, spread across one weekend. Second year takes four to five hours. Third year takes three. By year three the framework is internalised; the document is producing real returns; the central question is genuinely informing the year's decisions.

Don't try to do it perfectly the first time. The Annual Blueprint is a practice that gets sharper with reps. The first one is supposed to feel awkward. Write it anyway.

The honest next step

If you've never done an Annual Blueprint, block a weekend morning. Coffee, notebook, phone in another room. Walk through the six sections in order. By Sunday evening you have a document that didn't exist on Friday night — and the year ahead has a structure that gives every Monday a reason to open the planner.

The Annual Blueprint is £5.99 standalone. The complete Groundwork bundle at £54.99 includes it alongside every other layer of the cascade. The Groundwork OS at £19.99 runs the whole cascade live — the Annual Blueprint sits at the top, the daily priorities inherit from it automatically, and nothing in the system floats.

Annual goals fail because they sit alone. The Annual Blueprint succeeds because it sits inside an architecture that carries the work from January to December.