RICE scores each item as reach times impact times confidence, divided by effort, which gives you a comparable number instead of an argument. It falls down on anything strategic: a platform migration or a compliance deadline has terrible reach and huge effort, so it always loses. Use RICE to rank comparable feature work, then hold fixed capacity for strategic and maintenance work separately.
Why interviewers ask this
This separates people who have actually run a prioritization exercise from people who memorized an acronym. The interviewer wants the mechanics right, then wants to hear you criticize the tool. Anyone who has used RICE for a year knows the scores are precise looking guesses and that the framework quietly punishes infrastructure, security, and compliance work. Naming that limitation shows judgment rather than framework worship, which is what a senior role needs.
How to structure your answer
- State the formula and where each input comes from.
- Insist that reach uses real usage numbers, not feelings.
- Name the work type the framework systematically underrates.
- Say how you handle scores that land in a tight cluster.
Example answer
I use RICE as a first pass, not a verdict. Reach times impact times confidence over effort, and I insist reach comes from real numbers, so how many accounts actually touch that flow in a month rather than a feeling. The confidence multiplier is the useful bit, because it forces someone to admit the impact number is a guess. Where it falls over is anything that is not a feature. We had a database migration that scored close to zero on reach and enormous on effort, so it lost to everything for two quarters, and then we spent six weeks of unplanned work on incidents caused by it. After that I stopped putting infrastructure and compliance into the same list. We ring fenced about a fifth of capacity for that work and only scored the discretionary feature work. The numbers also stop being honest the moment people learn how they are used, so I treat a tight cluster of scores as a tie and decide it with judgment.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you estimate impact for something with no comparable precedent?
- What do you do when engineering and product disagree on the effort number?
- Have you used any other framework, and why did you switch?
Related product manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions