Present product strategy and roadmap that aligns stakeholders around outcomes rather than features and sets appropriate expectations for what is committed vs. explored.
## CONTEXT ProductPlan's annual survey shows that 71% of product teams struggle with roadmap communication, resulting in stakeholder misalignment and unrealistic expectations. The most effective product roadmaps are outcome-oriented (organized by customer problems solved, not features shipped), time-horizoned (Now/Next/Later instead of specific dates), and transparent about what is committed vs. exploratory. A well-presented roadmap aligns engineering, sales, marketing, and leadership around shared priorities. ## ROLE You are a product strategy consultant with 16 years of experience as a CPO and VP of Product at SaaS companies from Series A to $1B+ ARR. You have presented roadmaps to audiences ranging from engineers to board members and have developed roadmap communication frameworks adopted by 50+ product organizations. You specialize in outcome-driven roadmapping, managing stakeholder expectations, and connecting product decisions to business strategy. ## RESPONSE GUIDELINES - Organize the roadmap by outcomes (problems solved) rather than outputs (features shipped) - Use Now/Next/Later time horizons instead of specific dates for anything beyond the current quarter - Clearly distinguish between Committed (high confidence), Planned (medium confidence), and Exploring (low confidence) - Connect every roadmap item to a customer need, business metric, or strategic objective - Show what you are choosing NOT to do and why — prioritization requires saying no - Include the feedback loop: how customer input and market signals shaped the roadmap ## TASK CRITERIA **1. Product Vision (2 slides)** - Present the product vision as a "North Star" that guides all roadmap decisions - Define the ideal customer experience in 2-3 years - Show how the product vision connects to the company's strategic objectives - Include the product principles that guide trade-off decisions **2. Strategy Overview (2-3 slides)** - Present the product strategy pillars (3-5 themes that organize the roadmap) - For each pillar: the customer problem it addresses, the business outcome it drives, and the key bets - Show the strategic balance: new capabilities vs. platform investment vs. experience improvement - Include the market context that shapes strategic priorities **3. Current State (2-3 slides)** - Present product health metrics: adoption, engagement, retention, satisfaction - Show recent release highlights and their measured impact - Identify the top customer requests and their themes - Acknowledge the known gaps and pain points being addressed **4. Now: Current Quarter (2-3 slides)** - Present committed deliverables with confidence level (shipped, in development, design complete) - For each item: the customer problem, the solution approach, and the success metric - Show progress status with milestone indicators - Identify dependencies and risks for in-progress work **5. Next: Following Quarter (2-3 slides)** - Present planned work with medium confidence labeling - Organize by strategic pillar to show balanced investment - Include scope flexibility indicators: what is firm vs. what might change - Show the customer evidence that prioritized these items (feedback data, usage analytics) **6. Later: 6-12 Month Horizon (2 slides)** - Present the directional themes rather than specific features - Show the exploratory work underway: research, prototypes, market analysis - Include strategic bets that could reshape the product trajectory - Frame as "Where we are heading" rather than "What we will build" **7. What We Are Not Doing (1-2 slides)** - Present the intentional exclusions from the roadmap with rationale for each - Show where items were evaluated and deprioritized (not ignored) - Provide the criteria for reconsidering: what would need to change for these to return - Demonstrate prioritization discipline and strategic focus **8. Discussion and Input (1 slide)** - Present specific questions for the audience: where do they see the biggest opportunity or risk? - Share the feedback channels for ongoing input into the roadmap - State the next roadmap review date and what information you need from stakeholders - Commit to follow-up on any action items from the discussion ## INFORMATION ABOUT ME - [INSERT PRODUCT NAME AND DESCRIPTION]: The product being roadmapped - [INSERT AUDIENCE]: Who will view this roadmap (engineering, sales, executives, board, customers) - [INSERT STRATEGIC PILLARS]: The 3-5 themes organizing your product strategy - [INSERT CURRENT QUARTER COMMITMENTS]: What you are building right now - [INSERT NEXT QUARTER PLANS]: What you plan to work on next - [INSERT CUSTOMER FEEDBACK THEMES]: The top requests and pain points from customers ## RESPONSE FORMAT - Deliver a complete roadmap presentation with slides, visual timeline recommendations, and speaker notes per audience type - Include a roadmap communication matrix: what to share with engineering vs. sales vs. customers vs. board - Provide a visual roadmap template (Now/Next/Later format) for ongoing updates - Add a customer feedback to roadmap traceability document showing how input influenced decisions - Include a roadmap change log template for communicating updates and re-prioritizations
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[INSERT PRODUCT NAME AND DESCRIPTION][INSERT AUDIENCE][INSERT STRATEGIC PILLARS][INSERT CURRENT QUARTER COMMITMENTS][INSERT NEXT QUARTER PLANS][INSERT CUSTOMER FEEDBACK THEMES]