Keep the reasoning,
not just the plan.

A goal is where you want to end up. A plan is the sequence of things you intend to do. A strategy is the choice about how you will win given limited resources and real competition, and crucially about what you will not do. The confusion matters practically: teams that mistake goals for strategy end up with ambitious targets and no theory of how to hit them, and teams that mistake plans for strategy execute a long list without the ability to tell which items matter when capacity runs short. The test is whether the document says no to anything. If everything reasonable fits inside it, it is a plan or a wish list, and it will not help anyone prioritise in the week when it is needed.

The core should fit on one screen and the supporting material can be as long as it needs to be. The diagnosis, guiding policy, and the three to five things you are actually doing are the plan, and if they cannot be read in two minutes they will not be read at all, which is the practical fate of most fifty-page documents. Everything else, meaning the research, the financial model, the competitor analysis, the rejected options and their reasoning, is supporting material that should be one scroll away rather than absent. This is precisely what a canvas is good at: the argument stays legible at a glance and the depth sits beside it, instead of the usual choice between a slide that is too thin and a document nobody opens.

Not during early access. Storyflow is paid-only right now, with plans from $7.99 a month billed annually, and a Free plan launches before the end of 2026. Anyone a paid member invites to a board joins free today, so a co-founder, a board member, or the team can read and contribute without paying. If you need something free this minute, a single page written in any editor covering diagnosis, policy, actions, and rejected options is a genuinely good strategic plan and costs nothing. What a canvas adds is that the reasoning and the work stay connected as the year goes on, which is where written plans usually lose their grip.

Review quarterly, rewrite rarely. The quarterly review should ask three questions against the original board: has the diagnosis changed, have the assumptions each option depended on turned out to be true, and is anything we are spending time on connected to nothing. That is a short meeting when the board still exists and a long one when the plan has to be reconstructed from memory. Rewriting the strategy itself should be uncommon, because a strategy that changes every quarter was not a strategy, it was a reaction. The exception is a genuine change in the diagnosis, meaning the underlying problem is now a different problem, in which case starting from the same board with the old reasoning visible produces a much better second attempt than a blank page.

It can do the parts around the decision and it cannot make the decision. What it does well is generate options you have not considered, which is genuinely useful because it has no stake in the approach you have already committed to emotionally, and list the assumptions each option depends on, which turns vague optimism into things you can go and check. It is also good at first-draft structure, so you begin by arguing with a laid out board rather than filling in a template. What it cannot do is know your appetite for risk, what your team is actually capable of, what your customers have told you in the last month, or which trade-off you can live with. Storyflow is built on that split: the AI proposes and arranges, and the choice stays with the person accountable for it.

Constraints are the limits an option has to survive: cash, headcount, a contract, a technical dependency, a regulatory requirement, the founder's own time. Mapping them matters for two reasons. First, an option ruled out by a constraint is often ruled out by a constraint that could be changed, and that is a much more useful conversation than accepting the exclusion silently. Second, constraints expire. The reason you could not do something in January frequently stops applying in July, and if the constraint was never written down nobody notices. On a canvas, put each constraint on its own card and connect it to the options it blocks, so both the current shape of the decision and the trigger for revisiting it are visible.

Draw the connection literally, and then look at what has no line. Each initiative sits under the part of the guiding policy it advances, which takes minutes and produces two findings almost immediately. The first is work that serves nothing, which is usually the largest single source of recoverable capacity in a small team, and it is nearly always something inherited rather than chosen. The second is a part of the strategy with no work under it at all, meaning something you said was essential that nobody is doing. Both findings are invisible in a task list, because a task list shows what is being done and never shows what it is for. The reason to keep both on the same canvas is that the connection has to be maintainable, not just made once in a workshop.

Yes, and it changes the quality of the questions. Send a view-only link and anyone opens the whole board in a browser with no account and no download, including the rejected options and the reasoning behind the choice. A board reading a summary tends to ask whether the target is achievable; a board that can see what you turned down asks about the trade-off, which is the more useful conversation. Comments attach to the card they concern, so a question about a specific assumption stays on that assumption. For a formal board pack that needs a document, export the canvas as a high-quality image or PDF, and keep the live board as the thing you actually work from.

Strategic planning decides where to compete and how to win; operational planning decides how the chosen work gets done, by whom, and when. They need different tools and it is worth not forcing one to do the other's job. Operational planning wants assignees, dependencies, dates, and workload views, which is what a project management tool is built for and what Storyflow deliberately is not. Strategic planning wants the argument visible: diagnosis, options, trade-offs, constraints, and the connection between a piece of work and the reason it exists. The common failure is running strategy inside an operational tool, where everything becomes a task and the reasoning has nowhere to live, and the result is a well tracked list of activities nobody can justify.