---
name: Roadmap Planning
description: Theme-based, outcome-oriented roadmap.
---
# Roadmap Planning

A good roadmap communicates direction and priorities without becoming a fixed delivery commitment that breaks on contact with reality.

## Themes, not features
- Organize around **outcomes** ("reduce time-to-first-value") and **problems** ("onboarding leaks at step 3"), not a list of features with dates.
- Themes survive discovery — if you learn feature X is wrong, the theme still stands and you ship a better solution. Feature-roadmaps break the moment reality shifts.

## Time horizons
- **Now** (next 2-4 weeks): high confidence, in build.
- **Next** (1-3 months): problems identified, solutions in progress.
- **Later** (3+ months): direction only, no commitments.

The further out, the less specific. Promising exact dates months out is fiction.