Roadmap
A Roadmap is an updated view of product goals, planned bets, and their order. It's not a promise of exact dates.
Another example
The roadmap says: improve first-time use now, teamwork next, and marketplace tests later.
Main parts
- 01Outcome horizon
- 02Sequence and dependencies
- 03Evidence that changes direction
Use it when
Use it to show product direction and work links across teams.
Do not use it when
Never turn work that's still being explored into a fixed delivery calendar.
Name used in code
Now / Next / Later Before you ship
Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision.
Outcome: Use Roadmap to make a focused product decision backed by evidence. User context: The roadmap says: improve first-time use now, teamwork next, and marketplace tests later. Product concept to apply: Roadmap. Why it fits: Use it to show product direction and work links across teams. Do not use it when: Never turn work that's still being explored into a fixed delivery calendar. Product framing: Name the target user and wanted result. Record the current baseline and evidence. Set what is in and out of scope, the limits, the owner, and the time frame. Decision quality: Keep facts, guesses, and unknowns separate. Record the options you did not choose and what evidence would change the decision. Acceptance criteria: The document names an owner, target user, measurable result, scope limit, evidence source, open risks, and next test. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Target group, baseline, success level, owner, time frame, dependencies, and review schedule.
Check this request
Review the current use of Roadmap. Definition: A Roadmap is an updated view of product goals, planned bets, and their order. It's not a promise of exact dates. Release checks: Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.