Working product managers building feature prioritization frameworks that actually get used by their teams and approved by stakeholders. These prompts generate finished prioritization documents, stakeholder communications, and framework implementations you can use immediately.
These prompts pair well with Jasper AI for Product Management-specific tone control, or Copy.ai for fast iteration.
RICE Framework Implementation
You are a product manager implementing a RICE prioritization framework for your team’s next quarter planning.
Product: {product_name} Features to prioritize: {list_of_5_to_8_features} Team size: {number_of_engineers} Quarter: {Q1_Q2_Q3_Q4} {year} Key business metric: {revenue_growth / user_retention / conversion_rate} Confidence level for estimates: {high / medium / low} Stakeholder audience: {engineering_team / leadership / cross_functional}
Create a complete RICE prioritization analysis in 400-500 words. Start with a brief framework explanation. Present each feature with Reach, Impact, Confidence, and Effort scores in a clear format. Include your scoring rationale for the top 3 features. End with a recommended build order and timeline for {quarter}.
When to use it: When you have 5-8 competing features and need to present a data-backed prioritization to stakeholders within 24 hours.
Pro tip: Set your Effort scores relative to your team’s velocity. A 3-month feature for a 5-person team should score differently than for a 2-person team.
You are a product manager defending RICE scores to skeptical stakeholders who want their pet features prioritized.
Framework: RICE Controversial feature: {feature_name_stakeholders_want} Its RICE score: {numerical_score} Top-ranked feature: {winning_feature_name}
Top feature’s score: {winning_score} Stakeholder concern: {why_they_disagree} Business context: {current_company_priority} Meeting type: {email_response / verbal_explanation / presentation_slide} Tone: {diplomatic / data_driven / firm}Write a 200-250 word explanation defending your RICE prioritization. Address their specific concern while reinforcing why the framework serves the business goal. Include one concrete example of how the top-ranked feature better serves {business_context}. End with a path forward that acknowledges their input.
When to use it: When stakeholders push back on your RICE rankings and you need a diplomatic but firm response within an hour.
Pro tip: Always offer to re-examine one specific RICE component (usually Reach or Impact) rather than defending the entire score. It gives stakeholders agency while protecting your process.
You are a product manager adapting the RICE framework for technical debt and infrastructure work.
Technical initiatives: {list_of_3_to_5_tech_debt_items} Engineering team feedback: {main_pain_points_they_report} Customer-facing impact: {performance_issues / outages / slow_features} Business pressure: {ship_features / fix_stability / both} Timeline: {current_sprint / next_quarter} Audience: {engineering_lead / CTO / CEO} Tone: {technical / business_focused}
Create a modified RICE analysis in 300-400 words that treats technical debt as product features. Reframe Reach as “systems affected,” Impact as “developer velocity improvement,” and Confidence as “implementation risk.” Score each initiative and recommend which technical debt to tackle first. Justify your top recommendation in business terms that {audience} will understand.
When to use it: When engineering is pushing for technical debt work and you need to prioritize it alongside feature requests using a consistent framework.
Pro tip: Frame technical debt Impact scores around developer velocity and customer experience metrics, not just “code quality.” Leadership needs business outcomes.
You are a product manager creating a RICE scorecard template that your entire product organization will use.
Company size: {startup / mid_stage / enterprise} Product portfolio: {single_product / multiple_products / platform} Team structure: {pod_model / feature_teams / centralized} Scoring consistency problem: {different_teams_score_differently} Standardization requirement: {quarterly_reviews / monthly_planning} Rollout timeline: {next_two_weeks / next_month} Change management concern: {team_buy_in / leadership_adoption}
Write a 400-500 word RICE implementation guide for your product organization. Define what each RICE component means specifically for your {company_size} company. Provide scoring anchors (what makes a Reach score of 3 vs 5). Include a calibration process where teams can align their scoring. Address the main {change_management_concern} with a specific adoption strategy.
When to use it: When you’re rolling out RICE across multiple product teams and need consistent scoring standards everyone will actually follow.
Pro tip: Create scoring anchors based on your actual historical data. “High Impact = 20%+ improvement in our key metric” is more useful than generic 1-5 scales.
You are a product manager running a RICE calibration workshop with your cross-functional team.
Workshop duration: {60_minutes / 90_minutes / half_day} Attendees: {PM_eng_design / full_cross_functional / leadership_team} Sample features: {3_to_5_real_features_to_score} Team’s RICE experience: {never_used / some_experience / experienced} Main calibration issue: {reach_estimates / impact_scoring / effort_estimates} Desired outcome: {aligned_scoring / framework_buy_in / process_agreement} Workshop format: {in_person / remote / hybrid}
Create a {workshop_duration} RICE calibration workshop agenda with specific activities. Include a hands-on scoring exercise using the {sample_features}. Design discussion prompts that will surface and resolve the {main_calibration_issue}. End with concrete next steps and agreements about how the team will use RICE going forward. Format as a facilitator script with timing for each section.
When to use it: When your team’s RICE scores are inconsistent and you need to get everyone aligned in a single focused workshop.
Pro tip: Start with the feature everyone agrees should be lowest priority. It’s easier to align on what not to build, then work toward consensus on high-priority items.
Value vs Effort Matrix Communication
You are a product manager presenting a value vs effort prioritization to leadership who wants everything built immediately.
Features mapped: {5_to_8_feature_names} High value, low effort (quick wins): {list_quick_wins} High value, high effort (strategic): {list_strategic_features} Leadership pressure: {launch_by_specific_date / beat_competitor / hit_revenue_target} Team capacity: {current_sprint_velocity / team_size} Business context: {fundraising / product_launch / competitive_threat} Meeting type: {executive_presentation / email_update / planning_meeting}
Write a 350-400 word value vs effort analysis that acknowledges the {leadership_pressure} while protecting team capacity. Present quick wins as immediate opportunities. Position strategic features as requiring trade-offs with current roadmap. Include a specific recommendation for the next 30 days that balances business needs with realistic delivery. Use language that shows you understand the {business_context} urgency.
When to use it: When leadership wants to accelerate everything and you need to show trade-offs without seeming obstructionist.
Pro tip: Always lead with what you can deliver in 30 days. Leadership needs to see forward progress before they’ll accept longer timelines for bigger features.
You are a product manager explaining why a high-value feature is in the “high effort” quadrant to frustrated stakeholders.
Feature: {specific_feature_name} Why it’s high effort: {technical_complexity / integration_challenges / design_unknowns} Stakeholder expectation: {thought_it_was_simple / competitor_has_it / customer_is_asking} Effort reality: {actual_timeline / resource_requirements} Alternative approaches: {MVP_version / phased_approach / different_solution} Team capacity: {current_commitments} Business impact of delay: {revenue_loss / competitive_disadvantage / customer_churn}
Write a 250-300 word explanation that validates why {feature} matters while being clear about effort reality. Break down the {why_it’s_high_effort} in terms stakeholders can understand. Present {alternative_approaches} as ways to capture some value sooner. End with a specific timeline and resource requirement for the full feature versus alternatives.
When to use it: When stakeholders assume a valuable feature should be quick to build and you need to reset expectations without killing the initiative.
Pro tip: Use analogies from their domain. “This is like asking for a mobile app when we quoted a responsive website” resonates better than technical explanations.
You are a product manager defending why low-effort features shouldn’t automatically get prioritized.
Low effort features: {list_of_3_to_5_small_features} Why they’re low value: {limited_user_impact / technical_debt / maintenance_overhead} Team’s preference: {wants_to_build_them / sees_them_as_distractions} Opportunity cost: {high_value_work_we’d_delay} Stakeholder argument: {easy_wins / customer_requests / competitive_parity} Decision deadline: {this_week / next_sprint / end_of_quarter} Audience: {team_lead / product_director / cross_functional}
Create a 300-350 word argument for why effort alone doesn’t determine priority. Explain the hidden costs of {low_effort_features} including maintenance, user confusion, and opportunity cost. Show what {high_value_work} gets delayed if we chase easy features. Provide criteria for when low-effort features make sense versus when they’re distractions. End with a clear recommendation for {decision_deadline}.
When to use it: When your team wants to build easy features instead of tackling high-value complex work, and you need to refocus them on impact.
Pro tip: Calculate the maintenance cost of small features over 12 months. Five “quick” features often require more ongoing effort than one strategic feature.
You are a product manager facilitating a value vs effort mapping session with conflicting stakeholder opinions.
Session length: {90_minutes / half_day} Participants: {roles_attending} Features to map: {6_to_10_feature_names} Main disagreement: {value_estimates / effort_estimates / strategic_importance} Conflicting stakeholders: {sales_vs_eng / marketing_vs_product / leadership_vs_team} Facilitation challenge: {dominant_voices / analysis_paralysis / political_tensions} Desired outcome: {prioritized_roadmap / alignment_on_top_3 / framework_adoption}
Write a facilitation script for a value vs effort mapping workshop. Include specific questions to surface the {main_disagreement} constructively. Design activities that give all {participants} equal input despite {conflicting_stakeholders} dynamics. Address the {facilitation_challenge} with concrete techniques. End with a clear process for reaching {desired_outcome} by session end. Format as step-by-step facilitator guide with timing.
When to use it: When stakeholders can’t agree on feature priorities and you need a structured process to reach alignment in one session.
Pro tip: Use silent individual mapping before group discussion. People commit to positions more strongly when they’ve written them down, preventing groupthink.
You are a product manager updating a value vs effort matrix after customer feedback changed your assumptions.
Original prioritization: {what_you_planned_to_build} Customer feedback source: {user_interviews / support_tickets / usage_data} Changed assumptions: {what_you_learned_was_wrong} Features that moved quadrants: {specific_features_that_shifted} Timeline impact: {delayed_launch / scope_change / resource_reallocation} Stakeholder communication need: {explain_the_pivot / get_new_approval / update_expectations} Urgency: {communicate_today / update_this_week}
Write a 300-400 word update explaining how customer feedback changed your feature prioritization. Acknowledge what assumptions were wrong without dwelling on the mistake. Show how {features_that_moved_quadrants} now map to the matrix differently. Explain the {timeline_impact} and present options for moving forward. Frame the change as responsive product management, not planning failure. Include next steps for stakeholder alignment.
When to use it: When customer research invalidates your current prioritization and you need to communicate the pivot to stakeholders without losing credibility.
Pro tip: Lead with the customer insight that drove the change. Stakeholders accept prioritization shifts better when they understand the user need behind them.
Stakeholder Alignment Documentation
You are a product manager creating a prioritization rationale document for a contentious roadmap decision.
Controversial decision: {what_you_decided_not_to_build} Stakeholder opposition: {who_disagrees_and_why} Framework used: {RICE / value_vs_effort / OKR_alignment} Supporting data: {user_research / analytics / business_metrics} Alternative considered: {other_options_you_evaluated} Decision timeline: {when_this_gets_revisited} Distribution: {leadership_team / full_stakeholder_group / public_team_update} Tone needed: {transparent / diplomatic / firm}
Write a 400-500 word prioritization rationale document. Start with the decision and framework used. Present the {supporting_data} that led to this conclusion. Address {stakeholder_opposition} by acknowledging their perspective and explaining why other factors outweighed their concerns. Include {alternative_considered} to show thorough evaluation. End with when and how this decision gets revisited at {decision_timeline}.
When to use it: When you’ve made a prioritization decision that upset key stakeholders and need to document your reasoning for future reference.
Pro tip: Include the criteria you’d need to see to reverse the decision. It shows you’re data-driven, not stubborn, and gives opponents a clear path to reopening the discussion.
You are a product manager getting buy-in from engineering leadership for a feature prioritization that requires significant technical work.
Engineering-heavy features: {list_of_technical_features} Business justification: {revenue_impact / user_retention / competitive_advantage} Technical scope: {backend_changes / infrastructure / third_party_integrations} Engineering concern: {technical_debt / complexity / maintenance} Timeline pressure: {customer_deadline / launch_date / competitive_response} Engineering leader: {CTO / tech_lead / senior_engineer} Relationship: {collaborative / needs_convincing / generally_supportive}
Write a 350-400 word pitch to {engineering_leader} for why {engineering_heavy_features} should be prioritized. Connect technical work to {business_justification} with specific metrics. Acknowledge {engineering_concern} and show how you’ve factored it into timeline and scope. Present the {timeline_pressure} as context, not ultimatum. Include specific support you’ll provide to make the technical work successful. End with clear next steps for moving forward together.
When to use it: When your prioritization requires significant engineering investment and you need technical leadership to commit resources enthusiastically.
Pro tip: Offer to prioritize technical debt work alongside the feature. Engineers support business features more when they see product investing in platform improvements too.
You are a product manager explaining feature prioritization to disappointed customers who expected different functionality.
Customer request: {specific_feature_they_wanted} What you’re building instead: {actual_roadmap_priority} Why you chose differently: {user_data / business_priority / technical_constraints} Customer relationship: {key_account / vocal_user_group / general_feedback} Communication channel: {direct_email / community_forum / customer_call} Customer emotion: {frustrated / understanding / threatening_to_leave} Timeline for their request: {next_quarter / next_year / not_planned}
Write a 250-300 word response to {customer_relationship} explaining your prioritization decision. Acknowledge that {customer_request} is valuable and thank them for the input. Explain why {actual_roadmap_priority} serves the broader user base better, using {why_you_chose_differently} without overwhelming them with internal details. Address their {customer_emotion} appropriately. Be clear about {timeline_for_their_request} so they can plan accordingly.
When to use it: When customers are upset that their requested features aren’t being built and you need to maintain the relationship while explaining your prioritization.
Pro tip: Show how the feature you are building solves part of their underlying problem, even if it’s not their preferred solution. Customers accept trade-offs better when they see partial value.
You are a product manager creating quarterly prioritization summary for leadership review.
Quarter: {Q1_Q2_Q3_Q4} {year} Prioritization framework: {RICE / OKRs / value_vs_effort} Features shipped: {list_of_completed_features} Features deferred: {what_got_pushed_back} Key metrics impact: {specific_business_results} Stakeholder feedback: {what_you_heard_from_teams} Framework effectiveness: {what_worked / what_needs_improvement} Next quarter priorities: {top_3_focus_areas} Leadership audience: {CEO / CPO / executive_team}
Write a 450-500 word quarterly prioritization review. Start with key outcomes from {features_shipped} tied to {key_metrics_impact}. Explain why {features_deferred} were the right trade-offs. Analyze how well {prioritization_framework} worked based on {framework_effectiveness} and {stakeholder_feedback}. Present {next_quarter_priorities} with clear rationale. End with any framework adjustments for better prioritization going forward.
When to use it: During quarterly business reviews when leadership wants to understand how your prioritization process is performing and what you’re planning next.
Pro tip: Include one specific example of a prioritization decision that surprised you with its impact (positive or negative). It shows you’re learning from data, not just following process.
You are a product manager aligning cross-functional teams around a new prioritization framework implementation.
New framework: {specific_framework_name} Teams affected: {engineering / design / marketing / sales} Current prioritization problem: {inconsistent_decisions / stakeholder_conflicts / unclear_criteria} Implementation timeline: {next_sprint / next_month / next_quarter} Training required: {framework_workshop / scoring_calibration / tool_setup} Resistance expected: {teams_happy_with_status_quo / too_much_process / different_priorities} Success metrics: {how_youll_measure_adoption} Rollout approach: {pilot_team / full_adoption / gradual_rollout}
Create a 400-450 word change management communication for implementing {new_framework}. Explain why the current {prioritization_problem} hurts everyone’s work. Show how {new_framework} solves specific pain points each team experiences. Address expected {resistance_expected} with concrete benefits. Outline {training_required} and {implementation_timeline} clearly. Define {success_metrics} so teams know what good looks like. End with immediate next steps for {rollout_approach}.
When to use it: When you’re introducing a new prioritization framework and need cross-functional teams to adopt it willingly rather than grudgingly.
Pro tip: Start with a pilot team that’s already frustrated with current prioritization. Early success stories make organization-wide adoption much easier.
Data-Driven Prioritization Analysis
You are a product manager building a prioritization case using user analytics and business metrics.
Feature under consideration: {specific_feature_name} Supporting analytics: {user_behavior_data / conversion_metrics / engagement_stats} Business context: {growth_target / retention_goal / revenue_objective} User segment: {power_users / new_users / churning_users} Metric impact projection: {expected_improvement_percentage} Confidence level: {high / medium / low} Alternative features: {competing_priorities} Decision makers: {product_leadership / exec_team / board}
Write a 350-400 word data-driven prioritization argument for {feature_under_consideration}. Lead with the {supporting_analytics} and how it connects to {business_context}. Show why {user_segment} needs this feature based on behavioral evidence. Project the {metric_impact_projection} with clear reasoning for your {confidence_level}. Compare briefly to {alternative_features} using the same data lens. End with a clear recommendation and success metrics you’ll track post-launch.
When to use it: When you have strong analytics supporting a feature and need to make a compelling case to data-driven decision makers.
Pro tip: Include the sample size and time period for your analytics. Decision makers trust data more when they understand its statistical foundation.
You are a product manager prioritizing features when user research contradicts usage analytics.
Analytics insight: {what_the_data_shows} User research finding: {what_customers_said_in_interviews} Contradiction: {why_they_dont_align} Sample sizes: {analytics_users_vs_interview_count} Feature implications: {which_features_each_source_supports} Team debate: {who_believes_analytics_vs_research} Decision needed by: {specific_deadline} Stakeholder pressure: {leadership_preference / customer_requests}
Create a 300-350 word analysis that reconciles conflicting data sources for prioritization. Acknowledge both {analytics_insight} and {user_research_finding} as valid inputs. Explore possible reasons for {contradiction} including user segment differences, survey bias, or behavioral vs. stated preferences. Recommend which {feature_implications} to prioritize based on {sample_sizes} and business context. Address {team_debate} by showing how both sources inform the decision. End with next steps to resolve the data conflict for future prioritization.
When to use it: When quantitative and qualitative data point toward different priorities and you need to make a defensible decision quickly.
Pro tip: Look for user segment differences that explain the contradiction. Power users often behave differently from survey respondents, and both perspectives matter.
You are a product manager using A/B test results to reprioritize your feature roadmap.
A/B test feature: {what_you_tested} Test results: {conversion_lift / engagement_change / user_behavior_shift} Statistical significance: {confidence_level_and_sample_size} Unexpected findings: {what_surprised_you} Roadmap impact: {features_now_higher_priority / features_now_lower_priority} Resource reallocation: {engineering_time / design_focus / marketing_support} Timeline changes: {what_gets_accelerated / what_gets_delayed} Stakeholder communication: {who_needs_to_know_about_changes}
Write a 350-400 word roadmap update based on A/B test learnings. Present {test_results} with {statistical_significance} clearly. Explain how {unexpected_findings} changed your assumptions about user behavior. Show the logical connection between test insights and {roadmap_impact}. Detail {resource_reallocation} needed and {timeline_changes} required. Frame changes as data-driven optimization, not plan failure. End with updated priorities and next experiments to run.
When to use it: When A/B test results require significant changes to your planned feature prioritization and you need to communicate the pivot to stakeholders.
Pro tip: Include what you’ll stop doing, not just what you’ll start. A/B test insights often mean killing planned features, and stakeholders need to see those trade-offs clearly.
You are a product manager creating a prioritization framework weighted by customer lifetime value data.
Customer segments: {enterprise / mid_market / SMB / freemium} LTV by segment: