Roadmap Prioritization
Prioritizing Roadmap Features Using the RICE Framework
This prompt helps teams prioritize features for a product roadmap using the RICE framework (Reach, Impact, Confidence, Effort). It provides a structured approach to evaluate each feature based on its potential to drive user and business outcomes while considering resource constraints.
Responsible:
Product Management
Accountable, Informed or Consulted:
Product, Strategy, Customer Success
THE PREP
Creating effective prompts involves tailoring them with detailed, relevant information and uploading documents that provide the best context. Prompts act as a framework to guide the response, but specificity and customization ensure the most accurate and helpful results. Use these prep tips to get the most out of this prompt:
Collect data on user reach, feature demand, and current resource availability.
Define clear goals for the product or feature set (e.g., engagement, acquisition).
Break down feature requirements to estimate development and resource needs.
THE PROMPT
Help prioritize features for the product roadmap of [product/service name] using the RICE framework. For each feature, evaluate:
Reach: Estimate the number of users who will benefit from or be affected by this feature within a specific timeframe.
Impact: Assess the potential influence of the feature on key goals (e.g., engagement, retention, revenue) on a scale of low to high.
Confidence: Determine how certain we are about the Reach and Impact estimates based on available data.
Effort: Estimate the resources required to deliver this feature, measured in person-weeks or similar units.
Provide a calculated RICE score for each feature (Reach × Impact × Confidence ÷ Effort) and recommend a ranked list based on these scores. If additional details about features or product goals are needed, ask clarifying questions to refine the prioritization.
Bonus Add-On Prompts
Suggest ways to estimate Reach and Impact more accurately for features with limited data.
Identify features with high RICE scores that can be quick wins for the roadmap.
Propose strategies to reduce Effort for high-impact, low-confidence features.
Use AI responsibly by verifying its outputs, as it may occasionally generate inaccurate or incomplete information. Treat AI as a tool to support your decision-making, ensuring human oversight and professional judgment for critical or sensitive use cases.
SUGGESTIONS TO IMPROVE
Incorporate a user feedback component to refine Reach and Impact estimates.
Focus on specific product goals, such as retention or revenue, for Impact assessment.
Add stakeholder input to increase Confidence in the scoring process.
Tailor the RICE framework for multi-platform products (e.g., web, mobile).
Include a visual representation of scores, such as a prioritized matrix.
WHEN TO USE
To prioritize features using a structured, data-driven framework.
During roadmap planning sessions that require clear prioritization criteria.
When balancing high-impact features with limited development resources.
WHEN NOT TO USE
If data for Reach, Impact, or Confidence is unavailable or unreliable.
When the team prefers a more flexible or qualitative prioritization approach.