RICE vs Opportunity Solution Tree: A Founder’s Workflow to Prioritize Micro‑MVPs

RICE (Reach, Impact, Confidence, Effort) is a scoring model designed to convert initiatives into a single numeric priority. It shines when you need a repeatable way to compare feature backlog items or roadmap candidates using mostly quantitative inputs. Intercom’s original framing and modern explainers emphasize that RICE’s strength is in standardization and quick triage across many items.

The Opportunity Solution Tree (OST), popularized by Teresa Torres, is a discovery artifact: it starts with an explicit outcome, maps customer opportunities, then links candidate solutions to the assumptions you must test. OST’s value is not ranking — it’s surfacing risk and keeping teams focused on whether a solution will actually move the outcome.

Micro‑MVPs are experiments whose primary goal is learning, not shipping fully featured functionality. RICE treats confidence as a modifier but uses the same formula whether you’re estimating a revenue feature or a hypothesis test. If confidence scores are populated from intuition, RICE will rationalize gut bets into high scores—masking the real uncertainty you must resolve.

Because micro‑MVPs compress time and scope, founders need to prioritize based on expected information gain and the criticality of assumptions, not solely on projected reach or impact. An item with lower immediate reach but with a critical unvalidated assumption about product–market fit can be far higher priority for a two‑week micro‑MVP than a high‑reach feature whose assumptions are already proven.

OST makes implicit assumptions visible by forcing you to map outcome → opportunity → solution → assumption test. That mapping transforms vague confidence numbers into concrete, testable assumptions you can design a micro‑MVP around. For a founder, that means you see: which customer belief must be true, what evidence would invalidate the idea, and the minimum experiment to get that evidence.

By pairing OST with short assumption tests, you avoid two common failure modes: (1) prioritizing solutions that look good numerically but rest on brittle assumptions, and (2) overbuilding before a single key unknown is resolved. OST keeps discovery tightly coupled to outcomes, which in turn helps you pick experiments that produce decisive learning in 2–4 weeks.

This workflow combines OST to surface risky assumptions, and a constrained RICE-style score reweighted toward learning. Use it as a one‑page selection process you can run with cofounders or a two‑person product team in 1–2 working sessions.

Steps (approximate time): 1) Set a single measurable outcome (15–30 min). 2) Rapidly list 6–10 customer opportunities from recent interviews/data (30–45 min). 3) For top 3 opportunities, sketch 2–3 lightweight solutions each and write the single critical assumption per solution (45–60 min). 4) Score each solution with the Learning‑RICE variant and pick the top micro‑MVP to build today (30–45 min).

Paste the fields below into a doc or Miro board. Limit the page to three candidate solutions (the ones you generated from the OST) and fill the fields with short answers. Run a 10–20 minute calibration discussion for each solution and then compute the Learning‑RICE score.

After selection, spend the first 24–48 hours designing the micro‑MVP to keep development under the effort estimate: split work into 'build', 'measure', 'talk' tasks and plan a single decisive metric. Reassess at 2 weeks (quick pivot/stop) or at 4 weeks (deeper iteration).