What it is
A time-oriented plan communicating the intended sequence of outcomes, themes, or initiatives, and their rough priority, so stakeholders share expectations about direction.
When to use it
During Initiate for direction-setting, and revisited through Implement as reality updates the plan.
Why (value)
Aligns stakeholders on priorities and sequencing, communicates intent without over-promising dates, and connects daily work to larger goals.
How to run it
- Clarify goals and the outcomes that matter.
- Group work into themes or initiatives tied to outcomes.
- Sequence by priority, dependency, and capacity.
- Communicate confidence honestly (now / next / later).
- Revisit regularly as evidence changes priorities.
Inputs and outputs
- Inputs: Goals, prioritized opportunities, capacity and constraints.
- Outputs: A shared, outcome-oriented roadmap.
Time and effort
Medium. Ongoing; initial draft in days.
Evidence and limitations
A roadmap is a plan, not a promise or evidence. Prioritization should be traceable to evidence where it exists and labeled as assumption where it does not. See Evidence and limitations.
Tips and pitfalls
- Prefer outcomes and themes over hard date commitments.
- Use now/next/later to communicate uncertainty.
- Keep it living, a stale roadmap misleads.
Variations
Now-next-later, theme-based roadmaps, outcome roadmaps, Gantt (heavier).
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Impact-effort prioritization — Plot options by impact and effort to spot the quick wins and avoid the money pits.
- Design briefs — A one-page contract that aligns everyone on goals, scope, constraints, and success before design starts.
- Opportunity solution trees — Connect a desired outcome to the opportunities that drive it and the solutions that address them.
