The annual plan
your team still uses in June.

Storyflow does this one end to end: three themes across the top, five to seven bets as cards with a measure, a quarter and a named owner on each, four quarter columns, and the no list in the same size text beside them. The AI drafts a first version from last year's results. Scoring goals and rolling up progress automatically is still a job for a goal tool such as Lattice or Perdoo.

Three themes and five to seven bets under twenty people. The limit is not ambition, it is attention: a plan everyone can recite is a plan that gets used in the middle of a busy week. Nineteen priorities means the real priorities are whatever turned up most recently.

A theme says what the year is about and does not have a number on it. A bet is a specific thing you could fail at, with a measure, a quarter and an owner. Two or three bets sit under each theme. If a bet serves no theme, either the theme list or the bet is wrong.

Because a plan with no no list is a plan that assumes infinite time. Writing the second office, the rebrand and the conference on Storyflow's board in the same size text is what gives the six real bets room. It also stops the same ideas being relitigated every six weeks.

Storyflow's AI drafts one: paste your year-end notes, last year's results or a list of candidate ideas and ask for themes and bets. It reads attached files. What comes back is a first version to argue with, and the arguing is the part of annual planning that does the work.

Storyflow's annual board stays at the level of bets and quarters. It is not where sprints, tickets and assignees belong: keep those in whatever tracker the team already uses. When the year board fills with weekly tasks, people stop being able to see the year, which was the only reason to make it.

Storyflow is where the year is decided and where the quarterly review is held against something you can see, with each bet marked moved, done or dropped by hand. It does not score goals or roll progress up automatically. A goal tool such as Lattice, Perdoo or Mooncamp does that.

Once a quarter, for about twenty minutes. Open the board, mark each bet moved, done or dropped, and write one line saying why. Four short reviews keep the plan honest; one long review in December turns the whole year into an argument about what people meant in January.

Mark it dropped and write the reason next to it. Leaving a dead bet on Storyflow's board as if it is alive is what teaches a team that the plan is decoration. Dropping things on purpose, with a sentence, is what teaches them it is real.

Yes. Costs per theme, hiring and revenue targets go in a table with a currency column and a Sum footer, so the total moves when a row does. Keeping the money next to the bets it funds is what stops a plan that is arithmetically impossible from being agreed.

Storyflow lays the four quarters out as columns and you move bet cards between them by dragging. It cannot sort a table, so cards and rows stay where you put them. In a planning session that is usually what you want: the order comes out of the conversation about who is carrying which quarter, not out of a column.

A view-only link opens in any browser with no account, so the whole team and any advisor can read it. Leaving a comment does require signing in, and anyone a paid member invites to a board joins free.