Product Manager Interview (+ AI PM) · Strategy, Prioritization & Execution · Lesson 2 of 4
Prioritization: RICE & frameworks
Prioritization is the PM's signature skill: given more ideas than capacity, decide what to build next and defend it. Interviewers want an explicit framework, not gut feel.
- RICE: score = (Reach × Impact × Confidence) / Effort. Great for ranking a backlog with a defensible number.
- Impact vs Effort (value/effort): a fast 2×2 — do high-impact/low-effort first, question low-impact/high-effort.
- MoSCoW: Must / Should / Could / Won't — good for scoping a release.
- Kano: basics vs performance vs delighters — good for feature-mix and satisfaction.
State the framework, then apply itDon't just rank — name the lens: 'I'll use RICE. This item has high reach but low confidence, so…'. The framework makes your decision legible and defensible, which is exactly what's scored.
No framework replaces judgment. Weigh against strategy (does it serve the goal?), dependencies, and risk — and be ready to say what you'd not do.
◆ Lock it in
- RICE = (Reach × Impact × Confidence) / Effort — a defensible backlog ranking.
- Match the tool to the job: RICE backlog, value/effort 2×2 quick calls, MoSCoW scoping, Kano feature mix.
- Frameworks make decisions legible; still layer in strategy, dependencies, and risk.
Feynman drill — say it out loudExplain the RICE formula and why 'Confidence' and 'Effort' are in it.
Step 1 rate your confidence · Step 2 pick your answer
In the RICE framework, how is the score calculated?
Step 1 — how sure are you?