What it is for:Roadmapping is a planning session where a team lays out how an idea will reach its intended outcome over time. You leave with a one-page roadmap that links each milestone to an outcome, shows what depends on what, and names an owning role and review date for each piece of work.
Who it helps:Service owners and leads from several contributing teams who need a shared, realistic view of how an approved idea will get running.
When to use it
An idea has been tested and approved, and the team needs a shared view of how to get it running.
Several teams or partners must contribute and depend on each other's work.
Leaders want to see the plan at a glance without reading a long project document.
How to use it
Write two to four outcomes as changes in the world.
List milestones for each outcome as finished states.
Mark dependencies and order milestones along broad time bands, leaving space.
Name one owning role per milestone and set review dates and triggers.
Check the draft with every owner and dependent team before you publish it.
Tip:Keep outcomes visible on every version, so any new item has to show which outcome it serves.
Credits and sources:Original Tiremesù worksheet and wording. Further reading: IDEO.org Design Kit https://www.designkit.org/methods.html
Full guide and film:https://www.tiremesu.com/guides/roadmapping
