roadmaplisted

# Roadmap A roadmap is a statement of intent, not a delivery contract. Its job is to communicate *what outcomes you're betting on, in what order, and with how much confidence* — not to promise dates for a list of features. This skill helps you update, reprioritize, or build a roadmap in Now / Next / Later format, and it will make you say out loud what moves when you add something new. Most "roadmap updates" go wrong because people quietly inflate scope without admitting the trade-off. Don't let that happen. **Grounded in:** *Product Roadmaps Relaunched* — Lombardo, McCarthy, Wills & Connors: outcome-themed Now/Next/Later, not a dated feature list. **Go deeper (The Product Channel):** [How to Build an Effective Product Roadmap](https://sidsaladi.substack.com/p/week-15-how-to-build-an-effective) ## When to use this - Adding a new initiative and you need to decide what gets bumped to make room. - Priorities shifted after new information (a competitor move, a data point, a leadership ask). - A dependency slipped and timelines need to move. - Building a Now / Next / Later view from scratch. - A stakeholder is treating the roadmap like a commitment and you need to reframe it as intent. ## Before you start (gather these) - **Current roadmap** — in whatever form it exists. If there isn't one, say so; this skill can build from scratch. - **The change** — the new initiative, the new information, or the slipped dependency that triggered this. - **Capacity** — rough team size / numbe