RICE.tools
Real-time feature prioritization for distributed teams
Upload your feature list
CSV: First column becomes features (header ignored)
MD: Every non-empty line becomes a feature
TXT: Each line is a feature
Share link with your team
Collaborate in real-time with clean, shareable URLs
Do it sync or async
Score features together live or work at your own pace
🎯 Ready to Get Started?
Upload your feature list and start making data-driven prioritization decisions with your team.
R
Reach
How many customers will be impacted within a specific time frame?
I
Impact
How much will it impact each user? Use scale 0.25-3 since this can be tough to assign.
C
Confidence
Assign a percentage to how sure you are that your product will resonate with consumers.
E
Effort
How easy or difficult is the project based on how many people you need on your team?
Why RICE Prioritization Matters
Product teams face an endless stream of feature requests, bug fixes, and improvement ideas. Without a systematic approach to prioritization, teams often fall into common traps: building features that seem exciting but don't move the needle, spending months on low-impact work, or making decisions based on whoever speaks loudest in meetings.
The RICE framework, developed by Intercom, provides a data-driven approach to cut through the noise and focus on what truly matters. By scoring features across four key dimensions, teams can make objective prioritization decisions that maximize impact while considering resource constraints.
RICE Scoring Reference
Impact Scale
RICE Score
Higher scores = higher priority
Ready to Start Using RICE?
The best way to learn RICE is by doing. Start with a small set of features, gather your team, and begin scoring. You'll quickly develop intuition for the framework and see how it transforms your prioritization discussions.
Common questions about RICE prioritization and using this platform
About RICE Framework
What does RICE stand for?
RICE stands for Reach (how many users), Impact (how much it helps each user),Confidence (how sure you are about your estimates), and Effort (how much work it takes). It's a framework created by Intercom to help product teams prioritize features objectively.
How is RICE different from other prioritization methods?
Unlike simple scoring methods or gut-feeling decisions, RICE forces you to consider multiple dimensions: user impact, business reach, your confidence level, and resource constraints. It's more comprehensive than "High/Medium/Low" systems and more structured than frameworks like MoSCoW or Kano model.
Should I use RICE for everything?
RICE works best for feature prioritization and product roadmap planning. It's not ideal for emergency fixes, compliance requirements, or strategic initiatives that must be done regardless of score. Use it when you have multiple competing features and need to decide what to build first.
Scoring & Calculation
How do I estimate Reach accurately?
Use your analytics data when possible. Look at monthly active users, feature usage stats, or customer segments. If you don't have data, make educated estimates based on user research, surveys, or market size. Be specific about the time frame (per month, per quarter) and document your assumptions.
What if I'm not confident in my Impact score?
That's exactly what the Confidence score is for! If you're unsure about Impact, lower your Confidence percentage. A feature with Impact=3 and Confidence=20% will score lower than Impact=2 and Confidence=80%. This prevents speculative high-impact features from dominating your roadmap.
How do I handle features that benefit different user types?
Consider breaking them into separate features or score based on your primary user segment. For example, "Admin dashboard improvements" might have low Reach (few admin users) but high Impact (saves them hours). "User onboarding flow" might have high Reach (all new users) but medium Impact.
Using the Platform
What file formats can I upload?
You can upload .txt, .md (Markdown), or .csv files, or simply paste your feature list directly. The format is flexible - just put one feature per line. You can use bullet points, numbers, or plain text. Headers and categories are automatically parsed. For CSV files, we'll extract feature names from the first column.
How does real-time collaboration work?
Share your session URL with team members and everyone can score features simultaneously. You'll see who's online, what features they're working on, and changes update in real-time. You can also work asynchronously - team members can join and contribute at different times.
Is my data saved? Can I resume later?
Yes! All sessions are automatically saved to the database. You can bookmark your session URL or use the "Save & Resume Later" feature to get an email with a secure resume link. Sessions remain accessible for 30 days.
Can I export my results?
Absolutely! Click the "Export Results" button to download a CSV file with all your features, scores, and priority rankings. This makes it easy to import into project management tools, spreadsheets, or share with stakeholders who weren't part of the scoring session.
Best Practices
How many features should I score at once?
Start with 5-10 features for your first session to get comfortable with the process. For regular roadmap planning, 15-25 features work well. Too many features (50+) can lead to scoring fatigue and less accurate estimates. Break large backlogs into themed sessions.
Who should be involved in RICE scoring?
Include diverse perspectives: product managers (business impact), engineers (effort estimates), designers (user experience), and customer-facing teams (user needs). Avoid having too many people (5-8 is ideal) as it can slow down the process and create analysis paralysis.
How often should I re-score features?
Review and update scores quarterly or when you have new data. Market conditions change, user needs evolve, and technical complexity becomes clearer. Don't re-score constantly, but do update when you have significantly better information about reach, impact, or effort.
What if my team disagrees on scores?
Disagreement is valuable! Discuss the reasoning behind different scores. Often, people have different assumptions or information. Use the average of scores or have the most knowledgeable person make the final call. Document the rationale for future reference.
Technical & Platform Questions
Is my data secure and private?
Yes! Your data is stored securely in Supabase with industry-standard encryption. Sessions are only accessible via their unique URLs. We don't track personal information beyond what's needed for collaboration (anonymous user IDs and chosen display names).
What happens if I lose my session URL?
Use the "Save & Resume Later" feature to get an email with a secure resume link. This creates a backup way to access your session. If you lose both the URL and didn't save it, unfortunately the session cannot be recovered as we don't store personal contact information.
Can I use this for large teams (20+ people)?
While technically possible, we recommend breaking large teams into smaller groups (5-8 people) for more effective discussions. You can have multiple scoring sessions and then consolidate results, or have representatives from each team participate in a final scoring session.
Does this work on mobile devices?
Yes! The platform is fully responsive and works on tablets and smartphones. However, for the best experience during collaborative scoring sessions, we recommend using a laptop or desktop computer due to the amount of information displayed.
Ready to Get Started?
The best way to learn RICE is by doing. Start with a small set of features, gather your team, and begin scoring. You'll quickly develop intuition for the framework and see how it transforms your prioritization discussions.