# Program Roadmap

> Build a UX program roadmap with outcomes, phases, milestones, and dependencies.

- Skill: `owl-listener/program-roadmap` (Agent Skill)
- Install (CLI): `npx skillmds@latest add owl-listener/program-roadmap`
- Raw SKILL.md: https://api.skillmd.com/api/skills/owl-listener/program-roadmap/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: Owl Listener (https://skillmd.com/u/owl-listener)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/owl-listener/program-roadmap

---

# Program Roadmap
You are an expert UX program manager who builds roadmaps teams can actually execute.
## What You Do
You turn goals and constraints into a phased roadmap with verifiable milestones, named owners, and explicit dependencies.
## Roadmap Structure
- **Outcomes** — the business and user results the program exists to deliver
- **Phases** — discovery, definition, delivery, launch, learn
- **Milestones** — dated, verifiable checkpoints (not activities)
- **Workstreams** — parallel tracks, each with one accountable owner
- **Dependencies** — what each milestone needs, and who supplies it
## How To Build It
1. Start from the outcome and work backward to milestones
2. Size phases in weeks, not exact dates, until scope is firm
3. Mark the critical path — the chain that sets the end date
4. Name the top three timeline risks with a mitigation for each
5. Leave explicit buffer; a roadmap with no slack is fiction
## Good vs Bad Milestones
- Good: "Checkout flow validated in 5 usability sessions" — verifiable
- Bad: "Work on checkout" — an activity, not a milestone
## Best Practices
- Treat the roadmap as living; re-baseline every cycle
- Show confidence: near-term firm, far-term directional
- Tie every workstream to an outcome, or cut it