Ready-to-use prompts for Product Managers who need roadmap presentations drafted fast. Fill in the variables, paste into ChatGPT, and get slides you can present to leadership this week.
These prompts pair well with Jasper AI for Product Management-specific tone control, or Copy.ai for fast iteration.
Executive Summary Slides
You are a Product Manager presenting a quarterly roadmap review to the C-suite.
Product: {product_name} Quarter: {q1_q2_q3_q4} {year} Key metrics this quarter: {three_metrics_with_numbers} Major features shipped: {two_to_three_features} Next quarter priorities: {three_priorities} Biggest risk: {specific_risk} Budget ask: {dollar_amount_or_headcount}
Write a 400-word executive summary that opens with business impact numbers, explains what shipped versus what was planned, and closes with a clear ask. Use bullet points for the priorities section. Keep the tone confident but acknowledge the risk directly.
When to use it: Two days before your quarterly business review when you need the opening slide narrative locked down.
Pro tip: Lead with revenue or user metrics, not feature counts. Executives care about business outcomes first.
You are a Product Manager preparing an annual roadmap presentation for the board.
Company: {company_name} Product line: {product_category} 2025 revenue impact: {dollar_amount} 2026 revenue target: {dollar_amount} Top competitive threat: {competitor_name} Major technical debt: {technical_challenge} New market opportunity: {market_or_customer_segment} Team size: {current_headcount}
Write a 500-word strategic overview that positions the roadmap as a response to market opportunity and competitive pressure. Structure it as: Market context (150 words), Our response (200 words), Investment required (150 words). Use specific dollar amounts and avoid buzzwords.
When to use it: When the board presentation is next week and you need to connect product strategy to business strategy clearly.
Pro tip: Board members want to see how you’re thinking about competitive differentiation, not just feature delivery.
You are presenting a roadmap pivot to executive leadership after user research changed your assumptions.
Original roadmap focus: {previous_focus_area} Research finding: {key_insight_from_users} New strategic direction: {revised_focus} Features to deprioritize: {two_to_three_features} Features to accelerate: {two_to_three_features} Timeline impact: {weeks_or_months_delay} Confidence level: {high_medium_low}
Write a 350-word pivot explanation that acknowledges the change, explains the research insight, and presents the new direction as data-driven strategy. Open with the user insight, explain the implications, then detail the roadmap changes. End with timeline expectations.
When to use it: After user testing reveals your roadmap assumptions were wrong and you need buy-in for a course correction.
Pro tip: Frame pivots as learning wins, not planning failures. Show that you’re responding to real user needs.
You are a Product Manager presenting a resource allocation request to secure additional engineering capacity.
Current team size: {number_of_engineers} Requested additional headcount: {number_of_new_hires} Revenue opportunity: {dollar_amount_or_percentage_growth} Delivery timeline with current team: {months} Delivery timeline with additional team: {months} Competitive window: {urgency_factor} Hiring timeline: {weeks_to_hire}
Write a 300-word resource request that quantifies the opportunity cost of moving slowly. Structure as: Opportunity size, Current capacity constraints, Timeline comparison with/without resources, Competitive risk. Keep it numbers-focused and avoid emotional appeals.
When to use it: When leadership is asking you to deliver more with the same team and you need to make the economic case for hiring.
Pro tip: Always include the opportunity cost math. Show what revenue you’re leaving on the table by moving slowly.
You are updating the leadership team on roadmap progress after a major technical setback.
Affected initiative: {feature_or_project_name} Technical issue: {specific_problem} Original delivery date: {month_year} Revised delivery date: {month_year} Workaround solution: {alternative_approach} Customer impact: {how_customers_are_affected} Communication plan: {how_youll_update_customers}
Write a 250-word status update that explains the delay, presents the mitigation plan, and maintains confidence in the overall roadmap. Open with the timeline change, explain the technical context simply, detail the workaround, and close with customer communication approach.
When to use it: When a critical technical dependency breaks and you need to update stakeholders without creating panic.
Pro tip: Always come with a Plan B. Never present a problem without presenting your mitigation strategy.
Stakeholder Alignment Decks
You are presenting to Sales leadership about upcoming features that will impact their selling process.
Feature: {feature_name} Launch date: {month_year} Customer segment: {target_customer_type} Pricing impact: {how_pricing_changes} Sales cycle impact: {shorter_longer_same} Competitive advantage: {specific_differentiation} Training needed: {what_sales_needs_to_learn} Demo availability: {when_sales_can_show_it}
Write a 400-word sales readiness brief that explains the feature from a selling perspective. Structure as: Customer problem this solves, How it changes the sales conversation, Competitive positioning, What sales needs to know. Use language that sales can repeat to prospects.
When to use it: Six weeks before a feature launch when Sales needs to understand how to position the new capability.
Pro tip: Write the customer-facing value prop for them. Sales wants words they can use directly in prospect conversations.
You are aligning with Customer Success on features that will change the user experience for existing customers.
Feature: {feature_name} Affected customer base: {percentage_or_number} Change to workflow: {how_user_experience_changes} Migration required: {yes_no_partial} Support burden: {increase_decrease_same} Customer communication needed: {announcement_training_documentation} Beta feedback: {key_insights_from_testing}
Write a 350-word Customer Success brief that explains the user experience changes and support implications. Focus on: What customers will notice, Common questions to expect, How to position the change positively, Support resources needed. Keep the tone solution-focused.
When to use it: When rolling out UX changes that will generate support tickets and you need CS prepared with talking points.
Pro tip: Give CS the positive framing language first. They need to know how to explain why this change helps customers.
You are presenting roadmap priorities to the Engineering leadership team for technical feasibility input.
Proposed features: {three_to_five_features} Business priority ranking: {high_medium_low_for_each} Technical complexity estimates: {simple_medium_complex_for_each} Shared dependencies: {systems_or_components_affected} Performance requirements: {speed_scale_uptime_needs} Security considerations: {compliance_or_security_needs} Timeline pressure: {fixed_flexible_dates}
Write a 450-word technical planning discussion that presents the business priorities and asks for engineering input on sequencing and feasibility. Structure as: Business context, Feature overview with complexity notes, Dependencies and constraints, Request for technical input. Keep tone collaborative.
When to use it: During quarterly planning when you need Engineering to help sequence features based on technical dependencies.
Pro tip: Present business priorities first, then ask for technical input. Don’t assume you know the best technical sequence.
You are presenting to Marketing about upcoming features that need go-to-market support.
Feature: {feature_name} Launch date: {month_year} Target customer segment: {specific_customer_type} Key use cases: {three_primary_use_cases} Competitive response: {how_competitors_might_react} Pricing strategy: {freemium_premium_addon} Success metrics: {adoption_revenue_engagement_goals} Asset needs: {demos_case_studies_content_needed}
Write a 400-word marketing briefing that positions the feature launch as a marketing opportunity. Include: Customer problem and solution, Competitive differentiation, Target messaging themes, Marketing asset requirements. Frame it around customer value, not product features.
When to use it: Three months before launch when Marketing needs to start planning campaigns and content creation.
Pro tip: Give Marketing the customer problem statement, not just the feature description. They need to understand the pain point to create compelling campaigns.
You are presenting to Finance about roadmap investments and expected returns.
Initiative: {project_name} Development cost: {dollar_amount_or_team_months} Expected revenue impact: {dollar_amount_timeline} Customer acquisition benefit: {new_customers_expected} Retention impact: {churn_reduction_or_expansion} Time to ROI: {months_to_payback} Risk factors: {technical_market_competitive_risks} Alternative investment options: {other_priorities_competing}
Write a 300-word financial justification that presents the roadmap as an investment portfolio. Use: Investment size, Expected returns, Payback timeline, Risk assessment. Keep numbers specific and include confidence intervals where relevant.
When to use it: During budget planning when Finance needs to understand the economic case for product investments.
Pro tip: Always include the confidence level in your projections. Finance appreciates honesty about uncertainty.
Feature Deep-Dives
You are presenting a major feature to stakeholders who need to understand the user experience in detail.
Feature: {feature_name} User persona: {specific_user_type} Current user workflow: {how_they_do_this_today} New user workflow: {how_feature_changes_experience} Key screens: {three_to_four_main_interfaces} Success metrics: {usage_satisfaction_efficiency_measures} Edge cases handled: {two_to_three_complex_scenarios}
Write a 500-word user experience walkthrough that tells the story of a user completing a task with the new feature. Structure as: User scenario setup, Current state pain points, New workflow step-by-step, Quantified improvement. Make it narrative-driven, not feature-list driven.
When to use it: When demonstrating a complex feature to stakeholders who need to understand the user journey, not just the functionality.
Pro tip: Use a specific user scenario, not a generic one. Real stories are more convincing than abstract descriptions.
You are explaining the technical architecture of a new feature to non-technical stakeholders.
Feature: {feature_name} Technical approach: {api_database_frontend_architecture} Integration points: {systems_that_connect} Performance expectations: {speed_scale_reliability} Development phases: {what_ships_when} Risk mitigation: {backup_plans_for_technical_risks} Maintenance requirements: {ongoing_support_needs}
Write a 350-word technical overview that explains complex architecture in business terms. Focus on: What this means for users, How it connects to existing systems, Why this approach was chosen, What could go wrong and how we’re prepared. Avoid technical jargon.
When to use it: When non-technical stakeholders need to understand the technical complexity and risk profile of a major feature.
Pro tip: Translate every technical concept into a business implication. Don’t just explain how it works, explain why it matters.
You are presenting user research findings that informed a feature design decision.
Feature: {feature_name} Research method: {interviews_surveys_usability_testing} Sample size: {number_of_users} Key insight: {most_important_finding} Design changes: {how_insight_changed_approach} User quotes: {two_to_three_direct_quotes} Metrics impact: {expected_improvement}
Write a 400-word research-driven feature presentation that shows how user feedback shaped the product decision. Structure as: Research question, Methodology, Key findings with quotes, Design implications, Success predictions. Make the user voice central to the story.
When to use it: When stakeholders question a design decision and you need to show it’s based on real user feedback, not opinion.
Pro tip: Lead with the most surprising or compelling user quote. Real user words carry more weight than your interpretation.
You are presenting the competitive analysis that drives a feature priority decision.
Feature: {feature_name} Primary competitor: {competitor_name} Their approach: {how_competitor_solves_this} Our differentiation: {how_our_approach_differs} Market gap: {what_no_one_does_well} User preference: {what_users_want_differently} Competitive timeline: {when_others_might_catch_up}
Write a 350-word competitive positioning brief that explains why this feature matters for competitive advantage. Include: Competitive landscape, Our unique approach, Market opportunity, Timeline urgency. Focus on differentiation, not just feature parity.
When to use it: When justifying a feature investment based on competitive positioning and market differentiation needs.
Pro tip: Don’t just match competitors - explain how you’ll be different and better. Stakeholders want to see strategic thinking, not reactive development.
You are presenting the success metrics and measurement plan for a new feature launch.
Feature: {feature_name} Primary success metric: {adoption_revenue_engagement_measure} Supporting metrics: {three_to_four_additional_measures} Baseline performance: {current_numbers} Success targets: {specific_goals_with_timeline} Measurement approach: {how_youll_track_progress} Reporting frequency: {daily_weekly_monthly}
Write a 300-word metrics and measurement plan that defines success and explains how you’ll track progress. Structure as: Success definition, Baseline and targets, Measurement methodology, Reporting plan. Be specific about numbers and timelines.
When to use it: Before feature launch when stakeholders need to agree on success criteria and measurement approach.
Pro tip: Set both leading indicators (usage) and lagging indicators (business impact). You need early signals of success or failure.
Timeline and Dependency Management
You are presenting a complex project timeline with multiple team dependencies to project stakeholders.
Project: {project_name} Teams involved: {engineering_design_marketing_other} Critical path dependencies: {what_blocks_what} Major milestones: {four_to_five_key_dates} Risk factors: {what_could_cause_delays} Buffer time: {weeks_built_in_for_unknowns} Communication checkpoints: {when_youll_update_status}
Write a 400-word project timeline presentation that explains dependencies and manages expectations about delivery dates. Focus on: Key milestones, Critical dependencies, Risk factors, Communication plan. Be realistic about uncertainty and build in buffer time.
When to use it: At project kickoff when multiple teams need to understand their role in a complex delivery timeline.
Pro tip: Always show the critical path visually and explain which dependencies are most likely to cause delays.
You are explaining a roadmap delay to stakeholders after discovering new technical complexity.
Delayed project: {project_name} Original timeline: {planned_delivery_date} New timeline: {revised_delivery_date} Technical complexity: {what_made_it_harder} Scope adjustments: {what_youre_cutting_or_changing} Alternative solutions: {faster_approaches_considered} Impact on other projects: {what_else_moves}
Write a 350-word delay communication that explains the technical discovery, timeline impact, and mitigation plan. Structure as: What we learned, Timeline adjustment, Scope changes, Impact on other priorities. Keep tone professional and solution-focused.
When to use it: When technical discovery work reveals the project is more complex than originally estimated and you need to reset expectations.
Pro tip: Always propose scope adjustments alongside timeline delays. Give stakeholders options for how to respond to the complexity.
You are presenting quarterly roadmap progress and next quarter priorities to the broader product organization.
Quarter completed: {q1_q2_q3_q4} Delivered features: {three_to_five_shipped_features} Missed commitments: {what_didnt_ship_and_why} Next quarter themes: {two_to_three_focus_areas} Resource allocation: {how_team_time_will_split} Key dependencies: {what_you_need_from_other_teams} Success metrics: {how_youll_measure_progress}
Write a 450-word quarterly review that honestly assesses progress and clearly communicates next quarter priorities. Include: Delivery recap, Lessons learned, Next quarter focus, Resource needs, Success measures. Balance accountability with forward momentum.
When to use it: During quarterly all-hands meetings when the product organization needs alignment on priorities and progress.
Pro tip: Be honest about what didn’t work this quarter. Teams respect transparency and learn from mistakes.
You are presenting a roadmap re-prioritization after a major market shift or customer feedback changed your strategy.
Market change: {what_shifted_in_market_or_customer_needs} Previous top priority: {what_was_number_one} New top priority: {what_moves_to_number_one} Deprioritized initiatives: {what_moves_down_or_stops} Resource reallocation: {how_team_focus_changes} Customer communication: {how_youll_explain_to_users} Timeline impact: {what_speeds_up_or_slows_down}
Write a 400-word re-prioritization announcement that explains the strategic shift and new focus areas. Structure as: Market context, Strategic response, Priority changes, Resource implications, Customer impact. Frame changes as strategic agility, not indecision.
When to use it: When market conditions or customer needs change significantly enough to require major roadmap adjustments.
Pro tip: Connect the priority changes directly to the market shift. Show that you’re responding to real external factors, not changing your mind arbitrarily.
You are presenting end-of-year roadmap review and next year strategic planning to executive leadership.
Year completed: {year} Major achievements: {three_to_four_biggest_wins} Revenue impact: {dollar_amount_or_growth_percentage} User growth: {adoption_engagement_retention_numbers} Strategic learnings: {what_you_learned_about_market_or_users} Next year focus: {two_to_three_strategic_themes} Investment areas: {where_youll_spend_resources}
Write a 500-word strategic review that connects this year’s results to next year’s strategy. Structure as: Year in review with metrics, Strategic insights gained, Next year strategic direction, Investment priorities. Show how learning drives strategy evolution.
When to use it: During annual planning cycles when leadership needs to see how product strategy is evolving based on market learning.
Pro tip: Highlight the strategic insights, not just the feature deliveries. Show how shipping products taught you something about the market or customers.
Crisis and Change Management
You are presenting an emergency roadmap pivot after a major security incident requires immediate product changes.
Security incident: {type_of_breach_or_vulnerability} Affected features: {what_needs_to_change} Immediate actions: {what_youre_doing_this_week} Timeline for fixes: {when_users_will_see_improvements} Roadmap impact: {what_other_work_stops} Customer communication: {how_youre_explaining_to_users} Prevention measures: {how_youll_avoid_this_again}
Write a 350-word crisis response plan that explains the product changes needed to address the security issue. Focus on: Immediate response, Timeline for resolution, Impact on other work, Customer communication, Prevention strategy. Keep tone serious but confident.
When to use it: When a security incident forces immediate roadmap changes and you need stakeholder alignment on the emergency response.
Pro tip: Always include the prevention plan. Stakeholders need to know this won’t happen again.
You are explaining how new regulatory requirements will change your product roadmap and require feature modifications.
Regulation: {specific_law_or_compliance_requirement} Compliance deadline: {when_you_must_be_compliant} Affected features: {what_needs_to_change} New features required: {what_you_must_build} Development timeline: {how_long_compliance_work_takes} User experience impact: {how_this_changes_user_workflows} Ongoing compliance: {what_maintenance_is_required}
Write a 400-word regulatory compliance roadmap that explains the required changes and timeline. Structure as: Regulatory requirement, Compliance timeline, Product changes needed, User impact, Ongoing obligations. Present it as risk management, not bureaucratic overhead.
When to use it: When new regulations require significant product changes and you need buy-in for compliance-focused development work.
Pro tip: Frame compliance as competitive advantage - being compliant first can differentiate you in regulated markets.
You are presenting a post-mortem analysis after a major product launch failed to meet expectations and explaining the roadmap adjustments.
Failed launch: {feature_or_product_name} Expected results: {what_you_thought_would_happen} Actual results: {what_actually_happened} Root cause analysis: {why_it_failed} User feedback: {what_customers_actually_said} Roadmap changes: {how_youre_adjusting_strategy} Recovery plan: {how_youll_fix_or_pivot}
Write a 450-word post-mortem presentation that honestly analyzes the failure and presents the recovery strategy. Include: Results versus expectations, Root cause analysis, User feedback insights, Strategic adjustments, Recovery timeline. Take ownership while focusing on learning.
When to use it: After a major launch disappoints and you need to explain what went wrong and how you’ll recover.
Pro tip: Lead with accountability, then pivot to learning and recovery. Teams respect leaders who own failures and learn from them.
You are presenting roadmap changes required after losing a key team member or having major resource constraints.
Resource constraint: {team_departure_budget_cut_other} Affected capacity: {percentage_or_headcount_impact} Current commitments: {what_youve_already_promised} Priority framework: {how_youll_decide_what_to_cut} Scope reductions: {what_youll_deliver_with_less} Timeline adjustments: {what_takes_longer} Mitigation strategies: {how_youll_minimize_impact}
Write a 350-word resource constraint response that explains how you’ll adjust the roadmap to match available capacity. Focus on: Capacity impact, Prioritization approach, Scope adjustments, Timeline changes, Risk mitigation. Be realistic about what’s possible with reduced resources.
When to use it: When team changes or budget cuts force you to dramatically reduce roadmap scope and reset stakeholder expectations.
Pro tip: Present clear prioritization criteria. Stakeholders need to understand how you’re deciding what stays and what goes.
You are presenting the integration roadmap after your company acquired another company or was acquired.
Acquisition context: {acquired_or_acquiring} Integration timeline: {months_to_full_integration} Product overlap: {where_products_compete_or_complement} User migration plan: {how_users_move_between_products} Feature consolidation: {what_gets_combined_or_deprecated} Team integration: {how_product_teams