Annual Planning Template

Why most annual plans stop being used

An annual plan usually starts as a good document in January and turns into background noise by March. It survives in a slide somewhere, gets mentioned once at a town hall, and then has almost no bearing on what anyone actually does for the next nine months. It happens for a small number of predictable reasons, and none of them are about ambition. They're about structure.

The list is too long to be a decision. Twelve themes on a board is not a plan. It's everything anyone thought of, unfiltered, dressed up with priority labels that don't hold under pressure. A theme only means something once something else was deliberately left off, and a list of twelve rarely reflects a single trade-off having been made.

Nothing forces a second look. The plan gets written once, filed somewhere, and read again only when someone asks what happened to it, usually around budget season, usually with some discomfort. Without a checkpoint on the calendar, drift is silent. Nobody decides to abandon a theme; it just stops coming up.

The themes never touch the boards where work actually happens. They live in a deck while the team's real boards run on a completely separate list of tickets and tasks, so the year's stated direction and the week's actual work have no structural connection to each other, only whatever connection someone remembers to draw by hand.

There's no single owner for each theme. When a theme belongs to "the leadership team" collectively, it belongs to nobody specifically, and the first competing priority that shows up wins by default because there's no named person whose job it is to defend it.

How to use it

1. 01Start a workspace. A sample project loads automatically so you can see the columns working before you commit real themes to it. Free for up to five people, permanently.
2. 02Limit yourself to three to five themes. If a sixth one feels essential, something on the list has to move to next year or get folded into another theme, write down which.
3. 03Assign one owner and write the reasoning for each theme in its wiki page before the year starts, not after someone in a meeting asks why it's on the board.
4. 04Set the quarterly checkpoint date for each theme when you create it, not as an afterthought once the quarter has already started and it's easier to skip.
5. 05At each checkpoint, break the theme into that quarter's concrete goals. This is where annual planning hands off to quarterly planning, and it should happen four times a year, not once, at the end.

None of this requires a particular tool. A capped themes column, a named owner and a scheduled checkpoint work in a spreadsheet if that's what a team already trusts. It's written down here because most annual plans skip the checkpoint specifically, and that's the one part that keeps a plan alive past January instead of becoming a document nobody opens again.