A roadmap that follows what you actually start
Every change you start is a transformation with an owner, an intended outcome and its evidence. The roadmap sequences those changes by the dependencies you saved between their opportunities. No second plan to keep in sync.
Source of truth: the transformations you started
Roadmaps generated separately from the work
Quarters ahead, derived from saved dependencies
How it works
Start a change from a reviewed opportunity. It becomes a transformation with an accountable owner, an intended outcome and a measurement plan. The roadmap reads those records; nobody re-types them.
Save a dependency between two opportunities and the roadmap moves the dependent change to the quarter after the one it waits on. A change with no prerequisites sits in the current quarter. A completed prerequisite counts as done.
Each item links to its transformation: the Overview, the Work view and the Results view are one click away. Paused, stopped and completed changes stay visible in a concluded list, never rewritten.
A roadmap generated before September 2026 stays readable, can still be ratified and cascaded, and is labelled as the earlier generated programme. It is never regenerated.
Quarter by quarter, from the work itself
Q1
Foundation
- CRM copilot pilot
- Governance v1 policy
- Exec AI literacy
Q2
Scale + compound
- Fleet CRM rollout
- Finance agent pilot
- Q1 review + refresh
Q3
Agents everywhere
- Deploy 3 dept agents
- Board pack goes live
- Culture tracking
Q4
Prove value
- ROI report to board
- Next-cycle assessment
- Strategy canvas v3
Illustrative data
Strategy decks don't execute themselves
With a separately generated roadmap
- The roadmap and the work drift apart within weeks
- Two programmes compete: the generated plan and the changes people actually started
- Regenerating rewrites the plan and nobody knows which version the team is on
- Re-typing strategy into a project plan every quarter burns leadership hours
With the derived roadmap
- Every roadmap item is a started transformation with an owner and an outcome
- Sequencing comes from dependencies you saved, not from a model's guess
- Nothing to regenerate: start or stop a change and the roadmap follows
- One record feeds the roadmap, the value brief and the board pack
What's on the roadmap
Quarters, derived
The current quarter holds the changes with nothing to wait for. Each saved dependency pushes the dependent change one quarter later, up to eight quarters ahead.
Started changes only
Ideas and deferred opportunities stay in the pipeline. Only a change somebody committed to appears here, with its owner and its current state.
Dependencies you control
Save 'depends on', 'blocked by' or 'enables' between opportunities. The roadmap re-sequences on the next read and names what each change waits on.
Honest states
Preparing, in progress, review results, paused, stopped, completed: the same states the transformation shows. A stopped change is listed, not hidden.
One click to the work
Each item opens its transformation. The work plan, the measurement and the review live there; the roadmap is the map, not a second editor.
Earlier roadmaps kept
A roadmap generated before the change stays readable, ratifiable and cascadable, labelled as the earlier generated programme.
From opportunity to roadmap
Review an opportunity
The pipeline names the workflow, the estimate and the evidence. Decide: start, not now, or not relevant.
Start the change
Confirm the owner and the intended outcome. The transformation is created once, with its preparation task and its measurement plan.
Save the dependencies
On the opportunity, record what this change depends on or enables. The roadmap sequences it accordingly.
Read the roadmap
Quarter by quarter, the changes you started and what each waits on. Review it when the work changes, not on a schedule.
“A roadmap written separately from the work is out of date the day it is ratified. Fronterio derives the roadmap from the changes the organisation has actually started and the dependencies it saved between them, so the roadmap and the board pack read from one record.”
How the Strategic Roadmap works
Included with Pro
The derived roadmap is part of every Pro plan, alongside the Strategy Canvas.
Start one change and watch the roadmap follow
Review your opportunities, start the first change, and the roadmap sequences it with everything that depends on it.