Product Roadmap Generator

Your Roadmap Is Probably a Feature List. Here's How to Fix That.

At Amazon, every product roadmap starts with a press release written from the customer's perspective. Not a Gantt chart. Not a list of Jira epics. A narrative about what the customer will experience and why it matters. Most teams never get there — they ship a spreadsheet of features sorted by quarter and call it strategy.

I've reviewed hundreds of roadmaps from PM teams at startups and mid-stage companies. The pattern is depressingly consistent: a wall of features with no connective tissue. No "why." No explicit bets. No acknowledgment that some of this might be wrong.

The Roadmap Problem Nobody Talks About

A 2023 Gartner study found that 72% of product initiatives fail to deliver their expected business outcomes — and the most common cause isn't bad execution but bad prioritization at the roadmap level. Teams build the right things wrong, or worse, the wrong things right.

The underlying issue is that most roadmaps conflate output with outcome. "Launch SSO" is an output. "Reduce enterprise deal cycle by 30% by removing the #1 security objection" is an outcome. The first tells engineering what to build. The second tells the entire organization why it matters and how you'll know if it worked.

Marty Cagan has been saying this for years: the best product teams work on problems, not features. But translating that philosophy into an actual roadmap document that satisfies executives, keeps engineering aligned, and communicates honestly about uncertainty — that's the hard part.

How This Prompt Helps

This prompt forces you to build a roadmap in the format that actually works: organized by time horizon (Now/Next/Later), with explicit prioritization rationale, dependency mapping, and resource requirements for each initiative. It starts with product context — vision, stage, team size, strategic goals — and produces a document you can present to your CEO or share with engineering.

The Now/Next/Later structure is borrowed from how teams at Spotify and Intercom operate. It communicates commitment levels honestly: "Now" means we're building it this quarter, "Next" means we're confident it's coming, "Later" means it's a bet we haven't fully validated yet.

When to Reach for This

• You're preparing for a quarterly or annual planning cycle and need a structured starting point
• Your current roadmap is a Jira board that nobody outside engineering understands
• You need to align multiple stakeholders (CEO, engineering, sales, marketing) around a single document
• You're joining a new team and need to build your first roadmap from scratch with limited context
• A board meeting or investor update requires you to present product direction clearly

What Good Looks Like

A strong roadmap output connects each initiative to a strategic goal, includes a one-sentence rationale for why this is prioritized above alternatives, maps dependencies between initiatives, and explicitly states what you're choosing NOT to do. The best roadmaps are opinionated — they reveal the bets you're making and the assumptions behind them.

Sources

• Delivering What Customers Value Most — Gartner
• Product Roadmaps: How to Set Direction While Embracing Uncertainty — Silicon Valley Product Group
• The Now/Next/Later Roadmap — ProdPad