writing-product-roadmaps

A Now/Next/Later roadmap organizes initiatives into "Now" (committed), "Next" (prioritized), and "Later" (aspirational) buckets with defined commitment levels and time horizons, reducing confusion and improving strategic alignment.

Documenting dependencies and assumptions during product strategy communication ensures critical external and internal factors are considered, aligning feature prioritization and roadmap updates with expected customer outcomes.

Authoring a `roadmap.md` file involves documenting initiatives, dependencies, and open questions using the Now/Next/Later format, which can then be synchronized with your `product.yaml` to maintain product strategy alignment.

Outcome-oriented framing guides you to describe roadmap initiatives based on customer value and outcomes rather than just features, ensuring the temporal planning format communicates true product strategy effectively.

You need temporal planning when kicking off a new product strategy or updating a roadmap, as the Now/Next/Later format establishes clear commitment levels and time horizons, ensuring stakeholders understand direction and priorities.