strategyplaybook.aiSqwyz
Sign in
← All 124 tools
Futures · Explore, Plan

Backcasting

Starts from a defined future and works backwards to now, which surfaces dependencies that forward planning hides. Only as good as the future you start from.

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
02 Explore, 04 Plan
Works at
Corporate, Business
Maturity
Early startup → Large organisation
Time
Half a day

What it is

A planning method that begins with a defined future state and reasons backwards to the present, asking at each step what must already be true. It surfaces long-lead dependencies that forward planning tends to discover late, and it makes infeasible timelines visible early.

End state
A specific, dated, measurable description of the future you intend. Vague destinations cannot be backcast, which is itself a useful filter.
Preconditions
What must be true immediately before the end state is reachable. Each becomes the subject of the next step backwards.
The chain
The sequence of preconditions running back to the present. Where forward planning produces a list of initiatives, this produces dependencies.
Lead times
How long each precondition takes to establish. Long-lead items dominate the critical path and are the reason to do this at all.
Start dates
When each element must begin in order for the chain to hold. Several are usually earlier than anyone expected, and one or two are usually in the past.
The mistake people makeBackcasting from a future nobody has agreed produces a rigorous plan for a fantasy. It also has no opinion on whether the destination is a good idea — pair it with something that tests the desirability of the end state, not just the route to it.
What it’s forYou have a clear picture of a desired future and need the path back to now.
What it’s not forThe desired future is not agreed. Backcasting from a fantasy produces a fantasy plan.

How you run it

  1. Define the end state properlySpecific, dated, and measurable. "Market leader by 2030" cannot be backcast; "£30m revenue with 40% direct by 2029" can.
  2. Ask what must be true immediately beforeWork one step back at a time. What conditions must hold for the end state to be reached? Then what must be true for those?
  3. Keep going until you reach todayThe chain ends when you arrive at something already true or something you could start this month.
  4. Mark the long-lead itemsSome preconditions take years — capability, certification, relationships, plant. These determine whether the date survives, and they surface early in backcasting and late in forward planning.
  5. Test the timeline honestlyAdd up the lead times along the critical path. If they exceed the time available, say so now: the value of backcasting is finding that out before the plan is signed.

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

Your playbook

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

You’ll need

  • An agreed and specific end state, with a date
  • People who understand the delivery constraints
  • Willingness to conclude it cannot be done in the time

You’ll end up with

  • A backwards chain of preconditions
  • The earliest thing that has to start, and when
  • Where the timeline breaks

Runs well with

Acquisition screen and synergy thesisAdjacency mapAI operating model optionsAI risk classification and governance