# Roadmap One-Pager

## When to use

Use this template when you need to summarize and align a near-term roadmap, quarterly plan, or phase plan under resource constraints. It is especially useful when multiple requests compete and leadership needs to understand focus and trade-offs.

## Input needed

Prefer to gather the minimum useful context:

- planning period
- current stage goal
- candidate priorities
- resource constraints
- major dependencies
- known strategic timing pressure

If 1-2 critical premises would materially change prioritization, confirm those before locking the roadmap.

## Output goal

Produce a focused roadmap summary that makes the stage goal, top priorities, trade-offs, and success indicators clear.

---

# Roadmap One-Pager

## 1. Planning period

- What time window does this roadmap cover?
- What planning level is this: sprint, month, quarter, or phase?

## 2. Stage goal

- What is the single most important outcome for this period?
- What should be true by the end of this roadmap window?

## 3. What this roadmap is protecting

- Which scarce resource or strategic advantage is being protected?
- Focus, trust, engineering bandwidth, market timing, enterprise credibility, or something else?

## 4. Strategic focus

- What 1-3 themes define this roadmap?
- What are we intentionally trying to strengthen, fix, prove, or unlock?

## 5. Top priorities

List the top items in priority order.

### Priority 1

- What is it?
- Why is it top priority?

### Priority 2

- What is it?
- Why does it matter in this period?

### Priority 3

- What is it?
- Why is it still important, but after the items above?

## 6. Why these priorities

- How do these items connect to the stage goal?
- Why are these more important than other candidate work?
- Are we optimizing for growth, retention, monetization, quality, speed, or strategic positioning?

## 7. What is intentionally not prioritized

- Which items are being deferred?
- Why are they not in the top set right now?
- What would need to change for them to move up?

## 8. Constraints and dependencies

- What resource limits shape this roadmap?
- What major technical or organizational dependencies matter?
- Are there deadline, sequencing, or coordination constraints?

## 9. Risks and watchouts

- What may cause the roadmap to slip or fail?
- Which assumptions are fragile?
- Where may focus get diluted?

## 10. What would change this roadmap

- Which assumptions or external conditions would trigger reprioritization?
- What would force a new roadmap call?

## 11. Decide now vs validate next

- What should be aligned immediately?
- What still needs proof before larger commitment?

## 12. Success indicators

- How will we know this roadmap worked?
- What signals, metrics, or outcomes matter most in this period?

## 13. Review point

- When should this roadmap be reviewed?
- What decision or evidence should trigger reprioritization?

## 14. Immediate next steps

- What should teams align on now?
- What planning, scoping, or communication should happen next?

---

## Notes for use

A strong roadmap one-pager should:

- make the stage goal obvious
- show real prioritization, not a wish list
- explain what is not being done and why
- surface constraints honestly
- help leadership and teams align quickly
- make the sequencing logic easy to defend
