strategyplaybook.aiSqwyz
Sign in
← All 124 tools
Execution · Plan

Roadmap on a page

Shows what happens when, and what depends on what. Useful as a communication of sequence, dangerous when a set of estimates hardens into a set of commitments.

The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.

Stage
04 Plan
Works at
All levels
Maturity
Early startup → Large organisation
Time
Half a day

What it is

A single-page view of what happens when, ordered by dependency and grouped by outcome. It is a communication artefact: its job is to let someone understand the shape of the plan in a minute, not to schedule the work.

Timeline
The horizontal axis, usually quarters. Specific in the near term and deliberately coarse further out.
Streams
Horizontal bands grouped by outcome rather than by team, so the page shows what the business is achieving rather than who is busy.
Dependencies
What must complete before what can start. The actual content of a roadmap; without these it is a list with dates.
Confidence
Visual indication that later items are less certain. Without it, month eighteen gets quoted back as a commitment.
Decision points
Moments where a choice changes what follows. Their absence implies a plan immune to learning.
The mistake people makeA roadmap built on unknown dependencies is a set of guesses that will be quoted back as promises. If the dependencies genuinely are not known, show the next two quarters and mark the rest as undetermined rather than inventing it.
What it’s forYou need the sequence visible — what comes before what, and why.
What it’s not forDependencies are genuinely unknown. A roadmap of guesses gets treated as a commitment.

How you run it

  1. Sequence by dependency firstWhat must finish before what can start. Sequence is the roadmap's actual content; dates are a consequence.
  2. Group by outcome, not by functionA roadmap organised by department shows what each team is busy with. Organised by outcome it shows what the business is trying to achieve.
  3. Show confidence decreasing with distanceThe next quarter can be specific; month eighteen cannot. Draw it that way — widening bars, fading colour — or the far end gets read as a commitment.
  4. Mark the decision pointsWhere a choice gets made that changes what follows. A roadmap without them implies a plan that runs unchanged for two years, which none do.
  5. Keep it to one pageThe constraint forces the prioritisation. A twelve-page roadmap is a project plan and belongs elsewhere.

The prompt

Two ways to run it

Run this tool in your own Claude

The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.

🔒 Prompt locked

Everything above is free — what this tool is, what it is for, what it is not for, and how to run it as a workshop. Three tool prompts a month are free with an account; beyond three, and for the printable canvas, it is the paid part.

See plans — from £19 a month

Your playbook

It lands in the earliest stage this tool suits. Move it on the Playbook page.

You’ll need

  • An agreed set of moves
  • Honest dependencies and lead times
  • Someone willing to show uncertainty rather than hide it

You’ll end up with

  • Sequence across time, on one page
  • Dependencies marked
  • Confidence indicated, decreasing with distance

Runs well with

AI risk classification and governanceAlliance and partnership designAssumption logBackcasting