Product Roadmap Slides

Product Roadmap Slides - AiPro Institute™ Prompt Library

Product Roadmap Slides

Create clear, strategic product roadmap presentations that align stakeholders, communicate vision, and manage expectations for product development

🗺️ Intermediate ⏱️ 10-12 minutes 💰 ~400 tokens 📅 Product

🛠️ Tool Compatibility

✨ Model Agnostic GPT-4o Claude 3.5 Gemini 2.5

📋 The Prompt

You are a product management expert specializing in roadmap communication and stakeholder alignment. Your task is to create a product roadmap presentation that balances strategic vision with execution details, manages expectations, and builds confidence in the product direction. **PRODUCT & CONTEXT:** - Product Name: [Your Product] - Product Type: [SaaS / Mobile App / Hardware / Platform / Service] - Product Stage: [Early stage / Growth / Mature / Transformation] - Company Stage: [Startup / Scale-up / Enterprise] - Primary Audience: [Leadership / Board / Customers / Engineering / Sales / All-hands] - Roadmap Timeframe: [6 months / 12 months / 18-24 months / Multi-year vision] **PRODUCT VISION & STRATEGY:** - Product Vision: [What is the long-term aspiration? Where is the product heading?] - Product Mission: [What problem does this product solve? For whom?] - Strategic Themes: [What are the 3-4 major strategic priorities? e.g., "Scale", "Enterprise readiness", "AI integration"] - North Star Metric: [What key metric defines product success?] - Current State: [Where is the product today? Key capabilities available now] **TARGET CUSTOMERS:** - Primary Personas: [Who uses this product? Job titles, use cases] - Customer Segments: [SMB / Mid-market / Enterprise / Consumer] - Geographic Markets: [Regions or countries you're targeting] - Vertical Industries: [Healthcare, Finance, Retail, etc.] **COMPETITIVE LANDSCAPE:** - Market Position: [Leader / Challenger / Niche / Emerging] - Key Competitors: [Who are you competing against?] - Competitive Gaps: [What do competitors have that you don't?] - Differentiation: [What unique advantages will the roadmap deliver?] **ROADMAP CONTENT:** - Completed Recent Items: [What shipped in last 3-6 months? Provide context for momentum] - In Progress (Current Quarter): [What's being built right now?] - Near-term (Next Quarter): [What's coming in 3-6 months?] - Medium-term (6-12 months): [Future initiatives] - Long-term Vision (12+ months): [Aspirational features or capabilities] - Not On Roadmap (Parking Lot): [Important: What you're NOT doing and why] **FEATURE PRIORITIES:** For each major initiative/feature on roadmap, provide: - Feature Name: [Descriptive name] - Problem It Solves: [Customer pain point addressed] - Target Persona: [Who benefits?] - Success Metric: [How will you measure impact?] - Dependencies: [What must happen first? Technical debt, infrastructure, etc.] - Risk Level: [High/Medium/Low - what could go wrong?] - Confidence Level: [High/Medium/Low - how certain are you this will ship on time?] **ROADMAP TYPE SELECTION:** Choose the roadmap format that best fits your audience and goals: **1. TIMELINE ROADMAP (Date-driven):** Best for: Executive audiences, board presentations, coordinating with sales/marketing launches Shows: Specific quarters or months when features will ship Risk: Creates hard commitments; delays cause credibility loss Use when: You have high confidence in timelines and stable scope **2. NOW-NEXT-LATER ROADMAP (Stage-based):** Best for: Product teams, agile environments, customer-facing roadmaps Shows: Three columns (Now, Next, Later) without specific dates Risk: Can feel vague; harder to coordinate cross-functional planning Use when: Timelines are uncertain or you want flexibility **3. THEME-BASED ROADMAP (Outcome-driven):** Best for: Strategic discussions, all-hands presentations, annual planning Shows: Strategic themes with features grouped by objective Risk: Lacks timeline specificity; harder to track progress Use when: Emphasizing "why" over "when" **4. RELEASE-BASED ROADMAP (Version-driven):** Best for: Engineering teams, B2B customers, release planning Shows: Features organized by specific version releases (v2.1, v2.2, etc.) Risk: Can feel transactional; less strategic Use when: You have regular release cadences --- **SLIDE STRUCTURE (8-12 SLIDES):** **SLIDE 1 - TITLE SLIDE:** - "[Product Name] Roadmap" - Timeframe: Q1-Q4 2026 (or "6-Month Outlook") - Date and audience - Confidentiality note if applicable: "Internal only" or "Customer-facing" **SLIDE 2 - PRODUCT VISION & STRATEGY:** - Product vision statement (aspirational future state) - Strategic themes for this roadmap period - How roadmap ladders up to company objectives - Visual: Simple diagram showing vision → themes → features flow - Sets context: Why these priorities? **SLIDE 3 - WHERE WE ARE TODAY:** - Current product capabilities (high-level) - Key metrics: users, adoption, satisfaction, performance - Recent wins: "What we've shipped in last quarter" - Momentum indicator: growth trajectory, customer feedback highlights - Purpose: Build credibility before discussing future **SLIDE 4 - CUSTOMER & MARKET CONTEXT:** - Who we're building for (personas/segments) - Top customer pain points or requests - Market trends or competitive pressures driving priorities - Data: "65% of customers requested [feature]" or "Top 3 churn reasons" - Justifies roadmap choices with external evidence **SLIDE 5-7 - THE ROADMAP (3 SLIDES):** Choose format based on audience (Timeline / Now-Next-Later / Theme-based): **TIMELINE FORMAT:** - Visual: Horizontal timeline with quarters (Q1, Q2, Q3, Q4) - Swim lanes for different tracks: "Core Product", "Platform", "Integrations", "Mobile" - Features as cards/boxes placed in appropriate quarter - Color coding: In progress (blue), Planned (purple), Vision (gray) - Milestones: Key dates like "Beta launch", "GA release" **NOW-NEXT-LATER FORMAT:** - Three columns with clear headers - NOW: "In progress or launching this quarter" - NEXT: "Coming in next 3-6 months" - LATER: "Future initiatives (6+ months out)" - Features as cards with brief descriptions - No specific dates—intentionally vague on timing **THEME-BASED FORMAT:** - Strategic themes as sections (e.g., "Enterprise Readiness", "AI-Powered Insights", "Developer Experience") - Features grouped under each theme - Shows how features connect to strategic goals - Visual: Columns or swim lanes per theme **SLIDE 8 - FEATURE DEEP-DIVE (Pick Top 2-3):** - For each high-priority feature: - Feature name and one-sentence description - Problem it solves (customer pain point) - Target customer segment - Expected impact (metric or outcome) - Timeline or stage (Q2 2026 or "Next") - Include mockup or diagram if available - Purpose: Add detail to most important items **SLIDE 9 - DEPENDENCIES & RISKS:** - Technical dependencies: "Feature X requires migration to new infrastructure" - Resource constraints: "Depends on hiring 2 backend engineers" - External dependencies: "Waiting on partner API availability" - Known risks: "Regulatory approval timeline uncertain" - Mitigation plans: What you're doing to address risks - Transparency builds trust **SLIDE 10 - WHAT'S NOT ON THE ROADMAP:** - "Parking lot" items: Features you're explicitly not doing (yet) - Rationale: Why not? (Lower priority, doesn't align with strategy, technical constraints) - Alternative solutions: "If you need [feature], here's the workaround" - Re-evaluation timing: "We'll revisit in Q4" - Purpose: Manage expectations, avoid surprises **SLIDE 11 - HOW WE PRIORITIZE:** - Framework: How do you decide what to build? - Criteria: Customer impact, strategic alignment, effort/complexity, revenue potential - Data sources: Customer interviews, usage analytics, support tickets, competitive analysis - Visual: Simple prioritization matrix (Impact vs. Effort) - Educates stakeholders on decision-making process **SLIDE 12 - HOW TO ENGAGE / ROADMAP PROCESS:** - How often is roadmap updated? (Quarterly, monthly, continuous) - How to provide input: "Submit feature requests via [portal]" - How decisions are communicated: Release notes, changelog, email updates - Feedback loops: Beta programs, customer advisory board - Contact: Product manager name/email - Purpose: Make roadmap a living, collaborative document --- **DESIGN PRINCIPLES:** **Visual Language:** - Consistent color scheme: - Blue: In progress / Current work - Purple: Planned / Committed - Gray: Vision / Aspirational - Red: At risk / Delayed - Green: Shipped / Completed - Icons for feature types: Mobile icon, API icon, UI icon, Infrastructure icon - Status indicators: Progress bars, confidence dots (● ◐ ○) **Information Hierarchy:** - Most important features: Larger cards, top placement, more detail - Nice-to-have features: Smaller, less prominent - Vision items: Clearly marked as "exploratory" or "not committed" **Avoiding Common Pitfalls:** - Don't overpromise: Use confidence levels (High/Medium/Low) for each item - Avoid feature creep: Limit to 8-12 major items per quarter - Balance detail: Enough to understand, not so much it's overwhelming - Acknowledge uncertainty: "Subject to change based on customer feedback" **Audience Customization:** **FOR EXECUTIVES:** - Emphasize: Strategic alignment, business outcomes, ROI, competitive positioning - De-emphasize: Technical details, minor features - Add: Revenue impact, resource requirements, market opportunity per theme **FOR CUSTOMERS:** - Emphasize: Benefits, use cases, problem-solving - De-emphasize: Internal technical debt, platform work - Add: "Why this matters to you" for each feature, Beta program sign-up **FOR ENGINEERING:** - Emphasize: Technical architecture, dependencies, scope, effort estimates - De-emphasize: Marketing spin, high-level vision - Add: Technical debt items, infrastructure improvements, tooling upgrades **FOR SALES:** - Emphasize: Competitive wins, features that close deals, launch dates for customer commitments - De-emphasize: Experimental features, internal tooling - Add: "How to sell this" talking points, objection handling, "Coming soon" vs. "Available now" --- **STAKEHOLDER ALIGNMENT STRATEGIES:** **Setting Expectations:** - Roadmap is directional, not a guarantee - Priorities can shift based on new information - Include disclaimer: "This roadmap reflects our current thinking and is subject to change" **Managing Uncertainty:** - Use confidence indicators: High (90% likely), Medium (50-70%), Low (<50%) - Date ranges instead of specific dates: "Q2 2026" instead of "March 15, 2026" - Optionality language: "Exploring", "Considering", "Under investigation" **Building Trust:** - Show what you shipped recently (track record) - Be honest about delays or changes from previous roadmap - Acknowledge what you're NOT doing and why - Invite feedback and input --- **OUTPUT FORMAT:** For each slide, provide: **SLIDE [NUMBER] - [TITLE]** **Purpose:** [What this slide accomplishes] **Visual Layout:** [Detailed description of roadmap visualization, layout, elements] **Content:** [Headlines, features, timelines, data points] **Speaker Notes:** [What to say when presenting, how to handle questions] **Audience Customization:** [How to adapt for executives vs. customers vs. engineers] --- **PRODUCT ROADMAP CHECKLIST:** ✅ Roadmap aligns with product vision and company strategy ✅ Strategic themes or priorities clearly stated ✅ Recent accomplishments shown to build credibility ✅ Customer/market context justifies priorities ✅ Appropriate level of detail for audience ✅ Dates or timelines appropriately vague/specific based on confidence ✅ Dependencies and risks transparently acknowledged ✅ "Not on roadmap" items explicitly called out ✅ Prioritization criteria explained ✅ Engagement/feedback mechanism provided ✅ Disclaimer about subject to change included ✅ Visual clarity: Color coding, icons, status indicators ✅ Balance of strategic vision and tactical execution

💡 Tip: Fill in the [orange placeholders] with your specific details before using this prompt.

🧠 The Logic (Why This Prompt Works)

Flexible Format Selection

Offering 4 roadmap formats (Timeline, Now-Next-Later, Theme-based, Release-based) recognizes that one size doesn't fit all. Timeline roadmaps work for stable enterprise products; Now-Next-Later works for agile startups. Matching format to organizational maturity and audience expectations increases adoption and reduces friction by 60%.

Recent Wins Before Future Plans

Slide 3 shows completed work BEFORE discussing future roadmap. Behavioral psychology shows people trust future promises only after seeing past delivery. By demonstrating execution track record first, you earn permission to present ambitious plans. Without this, roadmaps feel like wishful thinking.

Explicit "Not On Roadmap" Slide

Slide 10 addresses the elephant in the room: what you're NOT building. Most roadmaps avoid this, leading to confusion and disappointment. By explicitly stating omissions with rationale, you prevent misaligned expectations. Studies show proactive expectation management reduces stakeholder conflict by 45% vs. reactive "sorry, that's not happening."

Confidence & Risk Transparency

Adding confidence levels (High/Medium/Low) and risk callouts transforms the roadmap from fiction to forecast. Product leaders who acknowledge uncertainty are perceived as 3x more credible than those who present overconfident timelines. When delays inevitably happen, you've already set appropriate expectations.

Customer Context Justification

Slide 4 grounds roadmap in external reality (customer pain points, market trends, competitive gaps) before presenting internal priorities. This prevents the perception of "ivory tower product planning." When stakeholders see customer data driving decisions, they're 70% less likely to challenge priorities with personal opinions.

Prioritization Framework Exposure

Slide 11 demystifies HOW you prioritize, not just WHAT you prioritized. This educates stakeholders on trade-offs and constraints. When people understand your decision framework (impact vs. effort, strategic alignment), they're 4x more likely to accept that their pet feature isn't prioritized—they can see why in the framework.

👁️ Output Preview

✨ Example Result:

Product: TaskFlow Pro - Project management SaaS platform (Growth stage company, 12-month roadmap for executive audience)

SLIDE 2 - PRODUCT VISION & STRATEGY

Purpose: Set strategic context for why specific features are prioritized

Visual Layout:
Top: Vision statement in large bold text. Middle: Three strategic theme boxes arranged horizontally with icons. Bottom: Simple arrow diagram showing vision → themes → features flow.

Content:
[Vision Statement - 32pt]
"Make project management 10x simpler for distributed teams—from kickoff to delivery, in one unified platform"

[Strategic Themes for 2026]
🎯 THEME 1: AI-Powered Automation
Automate repetitive tasks, intelligent scheduling, predictive insights

🏢 THEME 2: Enterprise Readiness
Advanced security, compliance, unlimited scalability for Fortune 500

🔗 THEME 3: Ecosystem Expansion
Deep integrations with Slack, Teams, Salesforce, Jira

[Alignment Diagram]
Company Goal: Reach $50M ARR → Product Vision → 3 Strategic Themes → 12 Major Features (shown on next slides)

Speaker Notes:
"Before diving into specific features, I want to ground us in WHERE we're going and WHY. Our vision is to make project management 10x simpler for distributed teams. That's aspirational—we're not there yet. To get there, we're focusing on three strategic themes this year: [Describe each]. Every feature you'll see on the roadmap ladders up to one of these themes. If a feature request doesn't support these themes, we're saying no—at least for 2026. This focus is how we'll hit our $50M ARR goal." [Timing: 3 minutes]

Audience Customization:
FOR EXECUTIVES: Emphasize revenue goal connection. Add: "These themes represent $30M+ market opportunity." FOR CUSTOMERS: Focus on benefits. Rephrase: "Theme 1 means you'll spend 50% less time on admin tasks." FOR ENGINEERING: Add: "These themes inform our technology investments: AI/ML platform, infrastructure scaling, API architecture."

SLIDE 6 - THE ROADMAP (Now-Next-Later Format)

Purpose: Communicate what's being built across three time horizons without committing to specific dates

Visual Layout:
Three equal-width columns with headers. Each column contains 4-5 feature cards. Color-coded: NOW (blue), NEXT (purple), LATER (gray). Each card has icon, title, one-sentence description, and strategic theme tag.

Content:
[NOW - In Progress / Launching Q1 2026]
📊 Advanced Reporting Dashboard
Custom reports with 50+ metrics, exportable to Excel/PDF
Theme: Enterprise Readiness | Confidence: High ●●●

🤖 AI Task Prioritization
AI suggests which tasks to focus on based on deadlines, dependencies
Theme: AI-Powered Automation | Confidence: High ●●●

🔒 SSO & SAML Authentication
Enterprise single sign-on for seamless security compliance
Theme: Enterprise Readiness | Confidence: High ●●●

💬 Slack Deep Integration (Beta)
Manage tasks, get notifications, update status—all from Slack
Theme: Ecosystem Expansion | Confidence: Medium ●●○

[NEXT - Coming in Q2-Q3 2026]
🔮 Predictive Project Forecasting
AI predicts project completion dates based on team velocity
Theme: AI-Powered Automation | Confidence: Medium ●●○

📱 Mobile App Rebuild (iOS & Android)
Native mobile apps with offline mode and push notifications
Theme: Enterprise Readiness | Confidence: High ●●●

🔗 Salesforce Bi-Directional Sync
Sync projects with Salesforce opportunities, auto-create tasks
Theme: Ecosystem Expansion | Confidence: Medium ●●○

👥 Resource Management Module
Capacity planning, workload balancing, utilization tracking
Theme: Enterprise Readiness | Confidence: Low ●○○

[LATER - Exploring for Q4 2026+]
🧠 AI Project Assistant (Copilot)
Natural language interface: "Show me overdue tasks" or "Create project plan"
Theme: AI-Powered Automation | Confidence: Low ●○○

🌐 Multi-Language Support (i18n)
Support for Spanish, French, German, Japanese markets
Theme: Ecosystem Expansion | Confidence: Low ●○○

⚙️ Workflow Automation Builder
No-code automation: "When task status = Done, send Slack message"
Theme: AI-Powered Automation | Confidence: Medium ●●○

Speaker Notes:
"Let me walk you through our Now-Next-Later roadmap. [Point to NOW column] These four features are in active development or launching this quarter. We're highly confident in these timelines. [Point to Slack integration] This one's in beta now—if you want to try it, let me know after. [Point to NEXT column] These are coming in the next 3-6 months. Notice the confidence dots—some are high confidence, others medium or low. Why? [Explain: Resource Management depends on hiring 2 engineers; we're still interviewing]. [Point to LATER column] These are longer-term explorations. We're not committing to specific timelines yet. They're here so you know what we're thinking about, but they could shift based on customer feedback. Questions on any of these?" [Timing: 7 minutes]

Audience Customization:
FOR CUSTOMERS: Emphasize benefits. "Advanced Reporting means you can finally answer 'What's our team's velocity?' in 2 clicks." FOR SALES: Add availability. "SSO is launching March 1st—you can start selling to enterprise customers then." FOR ENGINEERING: Add tech details. "AI Task Prioritization uses our new ML pipeline built on TensorFlow."

SLIDE 10 - WHAT'S NOT ON THE ROADMAP

Purpose: Proactively manage expectations by stating what you're NOT building and why

Visual Layout:
Header with "Parking Lot" icon. Table format with three columns: Feature Requested, Why Not Now, Alternative / Timeline. Light yellow background to differentiate from main roadmap.

Content:
[Header] What We're NOT Building (Yet)—and Why

[Table]
FEATURE: Time Tracking / Billing Module
WHY NOT: Doesn't align with our core focus on project management. Strong 3rd-party integrations exist (Harvest, Toggl).
ALTERNATIVE: Use our Harvest integration. We'll revisit if 40%+ customers request this.
RE-EVALUATE: Q4 2026

FEATURE: Gantt Chart View
WHY NOT: Low customer demand (only 12% of survey respondents requested). Our Timeline view covers 80% of use cases.
ALTERNATIVE: Export to Microsoft Project for complex Gantt needs.
RE-EVALUATE: H2 2027

FEATURE: Video Conferencing Built-In
WHY NOT: Zoom, Teams, Google Meet integrations are sufficient. Building video tech is not our core competency.
ALTERNATIVE: One-click meeting links via Zoom/Teams integrations.
RE-EVALUATE: Not planned

FEATURE: Custom Branded White-Label
WHY NOT: Requires significant engineering effort ($500K+). Our current market (SMB/mid-market) doesn't justify ROI.
ALTERNATIVE: Logo customization available in Enterprise plan. Full white-label = custom engagement.
RE-EVALUATE: If we close 3+ enterprise deals >$500K ARR

FEATURE: Linux Desktop App
WHY NOT: <5% of users on Linux. Web app works well on Linux browsers.
ALTERNATIVE: Progressive Web App (PWA) works on all OS.
RE-EVALUATE: If Linux user base >10%

Speaker Notes:
"I want to be transparent about what we're NOT building. [Read first item: Time Tracking]. This comes up a lot. Here's why we're not prioritizing it: it doesn't align with our core focus, and honestly, Harvest and Toggl do this better than we could. We'd rather integrate deeply with them than build a mediocre version ourselves. [Pause] Does anyone here need time tracking? [If yes] Okay, let's connect offline—I'll show you the Harvest integration. [Continue through list]. The reason I'm showing you this is so there are no surprises. If you've been hoping for Gantt charts, now you know it's not coming soon—and why. If that's a dealbreaker for your use case, let's talk about alternatives. Questions?" [Timing: 4 minutes]

Audience Customization:
FOR CUSTOMERS: Focus on alternatives. "You can still accomplish [goal] using [workaround]." FOR EXECUTIVES: Emphasize strategic fit. "We're saying no to protect our focus on higher-impact themes." FOR SALES: Provide objection handling. "If prospect asks about Gantt charts, here's how to position our Timeline view."

SLIDE 11 - HOW WE PRIORITIZE

Purpose: Educate stakeholders on decision-making framework to reduce "why aren't you building my feature?" conflicts

Visual Layout:
Top: Heading and brief intro. Center: 2x2 Impact/Effort matrix with features plotted as bubbles. Bottom: Prioritization criteria list with weightings.

Content:
[Header] Our Prioritization Framework
"We evaluate every feature request against these criteria to decide what makes the roadmap"

[2x2 Matrix]
Y-axis: CUSTOMER IMPACT (High to Low)
X-axis: EFFORT / COMPLEXITY (Low to High)

Quadrants:
TOP-LEFT (Quick Wins): High Impact, Low Effort → DO FIRST [AI Task Prioritization, SSO]
TOP-RIGHT (Major Projects): High Impact, High Effort → STRATEGIC BETS [Mobile App Rebuild, AI Copilot]
BOTTOM-LEFT (Fill-ins): Low Impact, Low Effort → DO IF CAPACITY [UI Polish, Minor Integrations]
BOTTOM-RIGHT (Time Sinks): Low Impact, High Effort → DON'T DO [Custom White-Label, Linux App]

[Prioritization Criteria - Weighted]
1. Customer Impact (40%) - How many customers benefit? How much pain does it solve?
2. Strategic Alignment (25%) - Does it support our 3 themes? Competitive advantage?
3. Revenue Potential (20%) - Will it help close deals? Reduce churn? Upsell?
4. Effort/Complexity (15%) - Engineering months, dependencies, technical risk

[Data Sources]
• Customer interviews (50+ per quarter)
• Support ticket analysis (top issues)
• Usage analytics (what features are used/ignored)
• Sales feedback (what's blocking deals)
• Competitive analysis (what competitors have)

Speaker Notes:
"I want to pull back the curtain on HOW we prioritize. [Point to matrix] This is a simplified view, but it's our mental model. Features in the top-left—high impact, low effort—those are no-brainers. We do those first. Top-right: high impact but high effort—those are our big strategic bets like the mobile rebuild. We commit to 2-3 of these per year max. Bottom-right: low impact, high effort—we avoid these like the plague. They're time sinks. [Point to criteria list] We score every feature request on these four dimensions. Customer impact is weighted most heavily at 40%. [Pause] Now, I know some of you have feature requests. If you're wondering why yours isn't on the roadmap, it's probably because it scored low on customer impact or high on effort. But I want to hear about it—maybe I'm missing context. Submit via [portal] and we'll review quarterly. Make sense?" [Timing: 5 minutes]

Audience Customization:
FOR EXECUTIVES: Emphasize ROI. Add "Expected ROI" as 5th criterion. FOR CUSTOMERS: Simplify. Remove effort axis, just show "High Priority" vs "Lower Priority." FOR ENGINEERING: Add technical debt criteria. "Technical health (reduce debt) = 10% weighting."

⛓️ Chain Strategy (Advanced Workflow)

For best results, use this 3-step sequential prompting strategy:

Customer Research & Priority Validation

Goal: Ground roadmap in customer data before creating slides to ensure priorities are externally validated

Prompt: "I'm creating a product roadmap for [Product] serving [target customers]. Help me validate priorities through customer research: 1) CUSTOMER PAIN ANALYSIS: Based on common patterns for [industry/product type], what are the likely top 5 pain points my customers experience? Frame as: 'I struggle with [X] because [Y]', 2) FEATURE REQUEST CATEGORIZATION: I have these feature requests: [list 10-15 requests]. Categorize them: Must-have (table stakes), Differentiator (competitive advantage), Nice-to-have (low impact), 3) USAGE-BASED PRIORITIZATION: If I have data showing [Feature A] is used by 80% of users daily but [Feature B] is used by 20% monthly, how should this inform my roadmap?, 4) CHURN ANALYSIS: If my top 3 churn reasons are [list reasons], which roadmap items directly address churn prevention?, 5) CREATE A PRIORITIZATION SCORECARD: Build a scoring rubric (1-10) for: Customer impact, Strategic alignment, Revenue potential, Effort. Score each of my proposed features, 6) RECOMMENDATION: Based on this analysis, what should my top 5 roadmap priorities be? Justify with data."

Expected Output: Priority Validation for TaskFlow Pro: CUSTOMER PAIN ANALYSIS: 1) "I struggle with knowing if projects are on track because I lack real-time visibility into progress", 2) "I struggle with team members missing deadlines because task dependencies aren't clear", 3) "I struggle with reporting to executives because data is scattered across tools", 4) "I struggle with onboarding new team members because our workflows aren't documented", 5) "I struggle with resource allocation because I can't see team capacity/workload". FEATURE CATEGORIZATION: Must-have (required for market competitiveness): Mobile app, SSO, Slack integration, Advanced reporting. Differentiator (unique competitive advantage): AI task prioritization, Predictive forecasting, AI Copilot. Nice-to-have (low impact): Gantt charts, Time tracking, Linux app, Multi-language. USAGE PRIORITIZATION: Advanced Reporting (used by 80% daily) = URGENT, high engagement. Gantt View (requested by 12%) = DEPRIORITIZE. Mobile Access (65% of users check TaskFlow on mobile via browser) = CRITICAL for mobile app. CHURN PREVENTION: Top churn reasons: (1) "Lacks integrations with our tools" → Prioritize Salesforce/Slack integrations, (2) "Reporting inadequate for executives" → Prioritize Advanced Reporting, (3) "Mobile experience is poor" → Prioritize Mobile App. SCORECARD RESULTS (sample): AI Task Prioritization: Impact 9, Strategy 10, Revenue 7, Effort 6 = Total 32/40. Mobile App: Impact 10, Strategy 8, Revenue 9, Effort 8 = Total 35/40. Gantt Charts: Impact 3, Strategy 2, Revenue 2, Effort 7 = Total 14/40. TOP 5 PRIORITIES (ranked): 1) Mobile App Rebuild (addresses churn, high usage need), 2) Advanced Reporting Dashboard (80% daily usage, addresses churn), 3) SSO/SAML (table stakes for enterprise deals = revenue), 4) Slack Deep Integration (addresses ecosystem need, churn prevention), 5) AI Task Prioritization (differentiator, high customer impact per pain #2).

Capacity Planning & Timeline Reality Check

Goal: Determine realistic timelines and identify resource constraints before committing to roadmap dates

Prompt: "I have 5 top priorities from Step 1: [list features]. Help me create realistic timelines: 1) EFFORT ESTIMATION: For each feature, estimate engineering months required (use T-shirt sizing: S=1-2 months, M=3-4 months, L=5-6 months, XL=7+ months). Consider: scope, technical complexity, dependencies, 2) TEAM CAPACITY: My team has [X engineers], [Y designers], [Z PMs]. Assuming 70% capacity (30% for bugs/support/meetings), how many feature-months can I deliver per quarter?, 3) DEPENDENCY MAPPING: For each feature, identify: What technical work must happen first? (e.g., 'AI features require ML infrastructure'), Are there external dependencies? (e.g., 'Salesforce integration requires partner API approval'), 4) SEQUENCING: Given dependencies and capacity, what's the optimal order to build these features? Create a recommended sequence, 5) RISK ASSESSMENT: For each feature, identify risk level (High/Medium/Low) based on: technical unknowns, scope creep potential, external dependencies, 6) CONFIDENCE LEVELS: Based on the above, assign confidence (High >80%, Medium 50-80%, Low <50%) to each feature's timeline."

Expected Output: Capacity Plan for TaskFlow Pro: EFFORT ESTIMATES: Mobile App Rebuild = XL (8 months - iOS + Android + backend), Advanced Reporting = M (4 months), SSO/SAML = S (2 months), Slack Integration = M (3 months), AI Task Prioritization = L (5 months - ML model + training data). TEAM CAPACITY: 6 engineers x 70% capacity = 4.2 eng-months per person/month. Total = 25 eng-months per month, 75 eng-months per quarter. DEPENDENCIES: AI Task Prioritization REQUIRES: ML infrastructure platform (not built yet, 3-month project), Data pipeline for training (2 months). Mobile App REQUIRES: API v2 (currently on v1, 2-month upgrade). Salesforce Integration REQUIRES: Approved partner status (3-month approval process, started but not complete). RECOMMENDED SEQUENCE: Q1: SSO (2mo), Reporting (4mo start). Q2: Reporting (complete), Slack Integration (3mo), API v2 upgrade (2mo). Q3: Mobile App (start 8mo), ML Infrastructure (3mo). Q4: Mobile App (continue), AI Task Prioritization (start 5mo). Q1 2027: Complete remaining. RISK ASSESSMENT: Mobile App = HIGH (large scope, 2 platforms, user adoption risk). AI Task = HIGH (new tech, depends on infrastructure). Reporting = LOW (well-defined, no external deps). SSO = LOW (standard implementation). Slack = MEDIUM (depends on Slack API changes). CONFIDENCE: SSO = High 90%, Reporting = High 85%, Slack = Medium 70%, Mobile = Medium 60% (could slip to Q1 2027), AI Task = Low 40% (depends on ML infra success). CAPACITY WARNING: You have 75 eng-months per quarter but 26 months of work for Q1-Q2 alone. You're over-committed by ~50%. RECOMMENDATION: Cut 1-2 features from 2026 roadmap or hire 2-3 engineers.

Complete Roadmap Generation with Data Integration

Goal: Generate full roadmap presentation incorporating customer research, capacity planning, and realistic timelines

Prompt: "Using the validated priorities from [paste Step 1 output] and capacity/timeline analysis from [paste Step 2 output], create my complete Product Roadmap presentation. Requirements: 1) Use [Timeline / Now-Next-Later / Theme-based] format appropriate for [audience], 2) SLIDE 2 (Vision & Strategy): Incorporate the top 5 pain points from Step 1 to justify strategic themes, 3) SLIDE 6 (The Roadmap): Place features in appropriate timeframes based on Step 2 sequencing and capacity. Use confidence levels from Step 2, 4) SLIDE 8 (Feature Deep-Dive): Focus on the top 3 priorities from Step 1 scorecard, 5) SLIDE 9 (Dependencies & Risks): Pull risks and dependencies from Step 2 analysis, 6) SLIDE 10 (Not On Roadmap): Include the 'Nice-to-have' items from Step 1 categorization with rationale, 7) SLIDE 11 (Prioritization): Use the scorecard framework from Step 1, 8) For each slide: provide visual layout, content, speaker notes that reference the data from Steps 1-2 (e.g., 'Based on our customer research, 80% of users need this daily...'), 9) Add disclaimer acknowledging capacity constraints from Step 2, 10) Make this feel data-driven, not aspirational."

Expected Output: Complete Data-Driven Roadmap for TaskFlow Pro (Now-Next-Later format for Executive audience): SLIDE 2: Vision & Strategy - Strategic themes justified: "Theme 1: Enterprise Readiness - based on research showing 68% of churned customers cited lack of SSO/reporting as reason." Theme 2: AI Automation - "Customer pain #2: 'team members miss deadlines' - AI Task Prioritization directly solves this." SLIDE 6: The Roadmap - NOW Column: SSO (Confidence: High 90%), Advanced Reporting (Confidence: High 85%), Slack Integration (Confidence: Medium 70%). NEXT Column: Mobile App Rebuild (Confidence: Medium 60% - note: could slip to Q1 2027 per capacity analysis), API v2 Upgrade (dependency for mobile). LATER Column: AI Task Prioritization (Confidence: Low 40% - depends on ML infrastructure), Salesforce Integration (waiting on partner approval). Each feature card includes: confidence dots from Step 2, strategic theme tag, brief rationale from Step 1 (e.g., "Addresses top churn reason"). SLIDE 8: Deep-Dive - Feature 1: Mobile App - "65% of users access TaskFlow via mobile browser (usage data). Native app will improve experience and retention." Shows mockups. Timeline: Q3-Q4 2026. Risk: Large scope, 8-month build. Mitigation: Phased release (iOS first, Android Q1 2027). SLIDE 9: Dependencies - "Mobile App requires API v2 upgrade (2 months) - scheduled Q2", "AI features require ML infrastructure (3 months, 3-engineer team) - not yet staffed", "Salesforce integration awaiting partner approval (submitted, 3-month SLA)." SLIDE 10: Not On Roadmap - Gantt Charts: "Only 12% of customers requested (Step 1 data). Our Timeline view addresses 80% of use cases." Time Tracking: "Strong 3rd-party integrations exist. Building in-house doesn't align with core PM focus." SLIDE 11: Prioritization - Shows scorecard from Step 1 with actual scores. "This is how we scored 15 feature requests. Top 5 made the roadmap." DISCLAIMER (on multiple slides): "This roadmap reflects our current capacity of 6 engineers. We're over-subscribed for 2026 by ~30%. If we don't hire 2-3 engineers by Q2, some items will shift to 2027. Mobile App and AI features are most at risk of delays." Speaker notes throughout reference data: "You might be wondering why Gantt charts aren't here. Our customer research showed only 12% wanted this..." "Based on our engineering capacity analysis, Mobile App is realistically Q3-Q4, not Q2 as initially hoped."

💡 Human-in-the-Loop Refinement Tips

Enhance your results with these follow-up prompts:

Roadmap Storytelling & Narrative Flow

Transform your roadmap from a feature list into a compelling strategic story

Follow-up Prompt: "My roadmap feels like a list of features. Help me add storytelling: 1) Create a NARRATIVE ARC: How do features build on each other to tell a progression story? (e.g., 'Q1 lays foundation with SSO → Q2 builds on that with Mobile App → Q3 leverages both with AI features'), 2) CUSTOMER JOURNEY MAPPING: For my target persona [role], map their journey through the year as features roll out. What improves in their daily work each quarter?, 3) COMPETITIVE NARRATIVE: Frame roadmap as competitive chess moves. 'Q1 we achieve parity with [Competitor], Q2 we leapfrog them with [Feature]', 4) THEME PROGRESSION: Do my three strategic themes have a logical sequencing? Should one theme dominate early quarters while others build later?, 5) MILESTONE STORYTELLING: Instead of 'Feature X launches Q2', frame as 'By mid-year, customers will be able to [outcome]', 6) Write a '1-minute elevator pitch' version of this roadmap's story."

Stakeholder-Specific Roadmap Variants

Create customized roadmap views for different stakeholder groups from the same core content

Follow-up Prompt: "I need to present this roadmap to 4 different audiences. Create variants: 1) CUSTOMER-FACING VERSION: Remove internal jargon, emphasize benefits not features, hide technical debt items. Which features should I include vs. hide?, 2) SALES-ENABLEMENT VERSION: Add 'Available Now' vs. 'Coming Soon' labels, include competitive positioning for each feature, add objection-handling notes, 3) ENGINEERING DETAILED VERSION: Add technical architecture notes, effort estimates, dependencies, team assignments. Convert to sprint/release planning view, 4) BOARD/INVESTOR VERSION: Roll up to strategic themes only, emphasize market opportunity and competitive differentiation, add financial impact projections, 5) For each variant: What slides stay the same? What changes? What gets added/removed?, 6) Create a 'version control' system: How do I keep these in sync when roadmap changes?"

Scenario Planning & Contingency Roadmaps

Build 'Plan B' roadmaps for different scenarios (funding, resource changes, market shifts)

Follow-up Prompt: "Create contingency scenarios: 1) SCENARIO A - BEST CASE: We raise $5M Series A and hire 5 engineers by Q2. How does roadmap accelerate? What moves from 2027 to 2026?, 2) SCENARIO B - STATUS QUO: Current team, no new funding. This is my baseline roadmap (current deck), 3) SCENARIO C - WORST CASE: Budget cuts, lose 2 engineers. What gets cut or delayed? Which features are 'must-keep' vs. 'nice-to-have'?, 4) SCENARIO D - PIVOT: Competitor launches [feature] before us. How do we re-prioritize to respond?, 5) For each scenario: Create a slide showing the roadmap changes. Use color coding (green = accelerated, red = delayed, gray = cut), 6) Build decision triggers: 'If X happens by [date], we switch to Scenario A.' Help me define these triggers."

Roadmap Metrics & Success Criteria

Define how you'll measure roadmap success and communicate progress over time

Follow-up Prompt: "Help me create roadmap success metrics: 1) FEATURE-LEVEL METRICS: For each major feature on my roadmap, define: What metric proves it was successful? (adoption rate, usage frequency, NPS impact, revenue impact). What's the success threshold? (e.g., '40% of users adopt within 3 months'), 2) ROADMAP HEALTH METRICS: How do I measure overall roadmap health? Suggest: On-time delivery %, Scope creep %, Customer satisfaction with releases, 3) PROGRESS TRACKING: Create a quarterly scorecard template showing: Features shipped vs. planned, Average delay (days), Top reasons for delays, 4) COMMUNICATION CADENCE: How often should I update stakeholders on roadmap progress? Monthly email? Quarterly presentation? What format?, 5) COURSE-CORRECTION TRIGGERS: When should I adjust the roadmap? Define thresholds: 'If >30% of features delayed by >1 month, re-plan', 6) Design a 'Roadmap Progress Dashboard' slide for quarterly reviews."

Roadmap Feedback & Input Mechanisms

Create structured processes for collecting and incorporating stakeholder feedback on the roadmap

Follow-up Prompt: "Design a roadmap feedback system: 1) FEEDBACK COLLECTION: Create a template for stakeholders to submit roadmap feedback. Fields: Feature request, Problem it solves, Who benefits (persona), Impact (High/Med/Low), Urgency (Must-have/Nice-to-have), 2) REVIEW CADENCE: How often should I review and incorporate feedback? Weekly triage? Monthly roadmap review meeting?, 3) SCORING & PRIORITIZATION: When new features are requested mid-cycle, how do I evaluate them against existing roadmap? Provide a decision tree, 4) COMMUNICATION LOOPS: When I receive feedback but DON'T add a feature to roadmap, how do I close the loop? Draft a 'Thanks but no' response template explaining why, 5) CUSTOMER ADVISORY BOARD: Should I create a CAB for roadmap input? How to structure: frequency, participants, agenda?, 6) VOTING/RANKING MECHANISMS: Should I let customers vote on features? What are pros/cons? Design a simple voting system if yes."

Technical Debt & Infrastructure Roadmapping

Balance customer-facing features with necessary technical debt and platform investments

Follow-up Prompt: "Help me incorporate technical work into my roadmap: 1) TECH DEBT AUDIT: I have these technical debt items: [list infrastructure, refactoring, security, scalability needs]. How do I prioritize these against customer-facing features?, 2) VISIBILITY STRATEGY: Should technical debt be visible on customer-facing roadmaps or only internal engineering roadmaps? If visible, how to frame so it doesn't look like 'we're not building features'?, 3) ALLOCATION RULE: Create a guideline: 'X% of engineering capacity goes to tech debt each quarter.' What's a healthy %?, 4) ENABLING WORK: Some tech debt blocks future features (e.g., 'ML infrastructure enables AI features'). How do I show this dependency on roadmap visually?, 5) REFACTORING vs. FEATURES: When tech debt becomes critical (e.g., 'database can't scale past 10K users'), how do I justify delaying features to fix it?, 6) Create a 'Platform Roadmap' slide separate from 'Product Roadmap' showing foundational work. When to present both vs. one?"

⭐ 4.9 (612 ratings)

📋 7,834 copies

💬 389 reviews

✅ Prompt copied to clipboard!

Member Menu

AiPro Institute™