Template preview · Software
Product roadmap
Sequence product bets around outcomes, dependencies, and decisions.
A quarterly roadmap for a fictional product team.
Sample purpose
Sequence product bets around outcomes, dependencies, and decisions.
Audience: Product manager, Engineering manager- Structure
- 4 sections
- Criteria
- 12
- Sources
- 8
- Watches
- 5
- Default approach
- Review first
Set the purpose first. Then change every section, criterion, and agent setting before anything runs.
Fictional sample
Structure and criteria
Sample content shows the shape of a useful document. Copying it is optional.
01 Review firstStrategic outcomes
State outcomes that give roadmap work a reason to exist.
Criteria
- States a measurable result with baseline, target and date (42% to 65% by June)
- Links the outcome to a member problem such as front-desk dependence
- Contains no feature or ship date
Sources
- Roadmap guide atlassian.comOutcome-first roadmap framing.
- Harbor Desk booking friction (fictional) api.harbordesk.exampleCurrent self-service booking rate and drop-off points by member segment.
Watches
- Searches “coworking space member room booking experience” monthly
Agent may search the web.
Sample content
Harbor Desk will help members book rooms without front-desk help, aiming to move self-service bookings from 42% to 65% by June.
02 Review firstRoadmap sequence
Show the order, owner, and dependency of each bet.
Criteria
- Every item has an owner other than the roadmap steward and a planning window
- Every dependency names the item it waits for and why, or says there is none
- Each item says why it comes before the next
Sources
- Harbor Desk capacity plan (fictional) api.harbordesk.exampleTeam capacity and platform work that create real dependencies.
- Harbor Desk support trends (fictional) api.harbordesk.exampleBooking-related ticket volume that justifies the order.
Watches
- Follows Strategic outcomes
Sample content
- 2026-01-12 · Booking auditMina maps failed booking paths.
- 2026-02-09 · Availability betaDepends on calendar sync repair.
- 2026-04-06 · Member launchReview support volume after two weeks.
03 Review firstDecision log
Keep assumptions and trade-offs inspectable.
Criteria
- Each row ties a scope or sequence decision to evidence, not preference
- The revisit trigger is a measurable condition (cancellation rate above 8%)
- Each decision points to a roadmap item or outcome
Sources
- Architecture decision records adr.github.ioPattern for recording context, decision and consequences.
- Harbor Desk calendar quality by site (fictional) api.harbordesk.exampleEvidence behind launching to two sites first.
Watches
- Follows Roadmap sequence
Sample content
Decision Rationale Revisit when Launch to two sites first Calendar quality differs by site. Beta cancellation rate exceeds 8%. 04 Review firstRoadmap health
Track whether the roadmap remains credible.
Criteria
- Includes at least one leading indicator (e.g. calendar sync test passed) beside lagging ones
- Each metric has a baseline and a review window
- Each metric shows which outcome or dependency risk it protects
Sources
- Harbor Desk product health (fictional) api.harbordesk.exampleAdoption and error rates for items in flight.
- Harbor Desk delivery tracking (fictional) api.harbordesk.exampleMilestone confidence and blockers.
Watches
- Follows Strategic outcomes
- Follows Roadmap sequence
Sample content
- Self-service bookings
- 42%
- Committed bets with named dependency
- 3 of 3