Rank your features with the RICE method

When ideas pile up, you need to choose what to do and when. The RICE method is one of the most used in product management to objectively prioritize features. This prompt automatically applies the RICE method and helps you make structured decisions quickly.

When to use this prompt

When preparing a product roadmap or sprint

To arbitrate between multiple user requests

During a prioritization workshop with the product team

During scaling phase to avoid dispersion

What this prompt allows you to obtain

A clear ranking of features according to their RICE score

Visualization of trade-offs based on your definitions

Brief justification of decisions (useful for internal communication)

A consistent basis for your next releases

Tips and mistakes to avoid

✓Do's

•Define criteria well from the start to maintain consistency
•Redo the exercise regularly based on new data

✗Don'ts

•Avoid "over-weighting" certain dimensions based on current mood
•Remember that RICE is a guide, not an absolute truth

Prompt Template

This is the base template with placeholders. Replace the placeholders with your specific information:

You are a Product Manager. Here is a list of features to evaluate: {{feature_list}}. Use the RICE method for each feature with the following parameters: Reach = {{reach_definition}}, Impact = {{impact_definition}}, Confidence = {{confidence_definition}}, Effort = {{effort_definition}}. Calculate the RICE score, rank the features by priority, and briefly explain the decisions. {{additional_context_block}}

Placeholder descriptions:

{{feature_list}}List of features to prioritize - ex: dark mode addition, onboarding redesign, Slack integration, reporting module

{{reach_definition}}Reach definition (number of users affected) - ex: monthly active users impacted

{{impact_definition}}Impact definition (value added for the user) - ex: improvement in engagement, satisfaction, conversions

{{confidence_definition}}Confidence definition (level of certainty on data) - ex: based on real data or assumptions?

{{effort_definition}}Effort definition (required resources) - ex: estimates in man-days or technical complexity

{{additional_context}}Additional context (optional) - ex: company strategic objectives or roadmap constraints

Example of generated prompt

Here's an example with filled-in values:

You are a Product Manager. Here is a list of features to evaluate: dark mode addition, Slack integration, onboarding redesign. Use the RICE method for each feature with the following parameters: Reach = monthly active users impacted, Impact = conversion improvement, Confidence = based on customer feedback + analytics, Effort = tech team estimate in man-days. Calculate the RICE score, rank the features by priority, and briefly explain the decisions. Also add these details: our goal is to increase activation and retention.

Share this prompt

Help others discover this useful prompt by sharing it on social media