Updated 28 October 2026
A roadmap can look convincing while asking the same people to deliver several incompatible priorities. Adding more initiatives rarely resolves that tension. The useful question is what the business can change, in what order, with the capacity and dependencies it actually has.
As products and channels multiply, improvements become connected. A simpler customer journey may depend on shared information, clearer service ownership and changes to how teams plan work. Treating those as separate projects can leave the customer waiting for the joins to catch up.
Start with an outcome and the constraint behind it
Choose a specific business concern. Perhaps customers repeat information when moving between products, or every roadmap depends on the same small specialist team. Describe the consequence before selecting a solution.
Then examine what prevents a better outcome. Is it missing information, a decision nobody owns, incompatible processes or capacity already committed elsewhere? Different explanations lead to different investments. Evidence helps distinguish a necessary dependency from an assumption that has become part of the plan.
Make the dependencies visible
The Stravus 8S framework helps examine the connections across Systems, Speed, Service, Scale, Synergy, Stability, Sense and Spirit. A business can be strong in one area and constrained in another. There is no universal maturity ladder or sequence that every organisation should follow.
For each proposed change, ask what it needs from elsewhere in the business and what it makes possible. A customer-facing feature may need a reliable service behind it. A shared capability may need an owner, funding and clear expectations before more products can depend on it.
These connections should shape the sequence. They should also expose work that can be reduced, deferred or stopped.
Build a sequence the business can support
A useful roadmap makes five things explicit:
Outcome: what should become better for customers or the business, and what evidence would show progress.
Dependencies: the decisions, capabilities and other work needed before a change can succeed.
Ownership: who can make the trade-offs and who will operate what is created.
Capacity: the people and attention available alongside day-to-day operations.
Review points: when to test assumptions and adjust the next step.
Shared capabilities deserve particular care. Some work benefits from common ownership; other work belongs close to a product because its customers, economics or controls differ. The roadmap should reflect that judgement rather than assume centralisation is the destination.
A conceptual illustration of connected routes and choices. It is an analogy for dependencies, not a prescribed sequence through the 8S dimensions.
Keep the route open to learning
A subway map is a useful analogy for dependencies and choices: more than one route may lead towards the outcome. It becomes less useful if every business is expected to visit the same stations.
As work progresses, customer feedback and operating evidence may change the route. A capability may be harder to share than expected. A small change in ownership may remove more friction than a large technology project. Review points allow leaders to respond without losing sight of the business purpose.
Start with one concern, make the constraints visible and agree a sequence that protects the business already running. The roadmap then becomes a practical basis for decisions, with room to learn as the work unfolds.
See how we help shape a practical transition roadmap, or explore the eight connected dimensions of the Stravus 8S framework.