--- title: "6 Feature Prioritization Frameworks (With Examples)" summary: "RICE, ICE, Kano, MoSCoW, value vs effort and weighted scoring: how each feature prioritization framework works, when to use it, and a worked example." date: 2026-11-04 author: "Karthik Kamalakannan" canonical: https://featureos.com/blog/feature-prioritization-frameworks markdown: https://featureos.com/blog/feature-prioritization-frameworks.md categories: ["product-management","guides"] readingTime: 5 --- A feature prioritization framework is a repeatable way to rank what to build next, so the decision rests on shared criteria instead of whoever argues loudest. The six most used are RICE, ICE, Kano, MoSCoW, value vs effort and weighted scoring. Pick by the data you have: little data, use value vs effort or MoSCoW; usage data, use RICE; customer research, use Kano. None of them makes the decision for you. They make the trade-offs visible so the team can argue about the right thing. ## The 6 frameworks at a glance | Framework | How it works | Best for | Needs | Watch out for | |---|---|---|---|---| | RICE | (Reach x Impact x Confidence) / Effort | Long backlogs with usage data | Reach numbers, effort estimates | Guessed reach looks precise | | ICE | Impact x Confidence x Ease | Fast triage, growth experiments | Three 1 to 10 scores | Scores are opinions | | Kano | Sort features by how they affect satisfaction | Deciding what makes a product delightful vs table stakes | A customer survey | Takes time; results age | | MoSCoW | Must, Should, Could, Won't have | Fixed-scope releases and deadlines | Stakeholders in one room | Everything becomes a Must | | Value vs effort | Plot ideas on a 2x2 grid | Small teams, short lists | A rough sense of value and effort | Ties in the top-left box | | Weighted scoring | Score criteria, weight them, add up | Balancing several goals at once | Agreed criteria and weights | Weights can be gamed | ## RICE RICE scores an idea on Reach, Impact, Confidence and Effort. It comes from [Intercom's product team](https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/), and the formula is **(Reach x Impact x Confidence) / Effort**. Use it when you can count how many customers an idea affects. Reach is what separates it from ICE, and it is also where it breaks: if reach is a guess, the score is a guess with decimals. Votes and linked requests on a [feedback board](/glossary/feedback-board) give you a real reach number. Full explainer: [RICE scoring](/glossary/rice-scoring). ## ICE ICE multiplies Impact, Confidence and Ease, each scored 1 to 10. It is popular with growth teams for ranking experiments because it takes minutes. The cost of speed is that all three inputs are opinions, and Ease favors small changes over big bets. We compare RICE, ICE and value vs effort on the same backlog in [RICE vs ICE vs value vs effort](/blog/rice-vs-ice-vs-value-vs-effort). ## Kano model The Kano model, introduced by Noriaki Kano and colleagues in 1984, sorts features by how they affect customer satisfaction: - **Basic (must-be):** expected. Missing them makes people angry; having them earns no credit. - **Performance:** more is better, in a straight line. Speed is the usual example. - **Delighters (attractive):** unexpected. Missing them costs nothing; having them wins fans. - **Indifferent** and **reverse:** features people do not care about, or actively dislike. You classify features with a short survey that asks how a customer would feel if a feature were present, and how they would feel if it were absent. Kano tells you what kind of value a feature adds, not how much work it is, so pair it with an effort estimate. Over time, delighters become basic expectations. Full explainer: [Kano model](/glossary/kano-model). ## MoSCoW MoSCoW splits a release into **Must have**, **Should have**, **Could have** and **Won't have (this time)**. It came out of the DSDM agile method in the 1990s and works best when the deadline is fixed and scope has to give. The rule that keeps it honest: Musts are things the release fails without, not things someone wants badly. If more than about half the list is a Must, the exercise has not done its job. Full explainer: [MoSCoW prioritization](/glossary/moscow-prioritization). To sort your own list, try the free [MoSCoW tool](/tools/moscow-prioritization). ## Value vs effort Draw a 2x2 grid with value on one axis and effort on the other. Do high value, low effort first, plan high value, high effort carefully, and question everything that is low value. It is the quickest framework and the hardest to over-engineer. It stops helping when a dozen ideas land in the same box, and when the team has not agreed what "value" means (revenue, retention or something else). ## Weighted scoring Weighted scoring lets you rank against several goals at once. Pick three to five criteria, give each a weight that adds up to 100%, score every idea 1 to 5 per criterion, and sum the weighted scores. Here is a worked example. **The ideas, criteria, weights and scores are illustrative, made up for this post, not real customer data.** | Idea | Customer demand (40%) | Revenue impact (30%) | Strategic fit (20%) | Ease (10%) | Weighted score | |---|---|---|---|---|---| | SSO login | 3 | 5 | 4 | 2 | 3.7 | | CSV export | 5 | 3 | 2 | 5 | 3.8 | | Mobile app | 4 | 3 | 5 | 1 | 3.6 | | Dark mode | 2 | 1 | 1 | 4 | 1.7 | How the first row is calculated: (3 x 0.4) + (5 x 0.3) + (4 x 0.2) + (2 x 0.1) = 1.2 + 1.5 + 0.8 + 0.2 = 3.7. CSV export edges out SSO here because demand carries the most weight. Move 10 points of weight from demand to revenue and SSO wins. That sensitivity is the point: the weights are the real decision, so agree on them before anyone scores an idea. A related approach, [cost of delay](/glossary/cost-of-delay), puts a money value on waiting instead of using abstract scores. ## How to choose a feature prioritization framework 1. **You have little data and a short list:** value vs effort. 2. **You have a fixed deadline and too much scope:** MoSCoW. 3. **You need to rank experiments every week:** ICE. 4. **You can count how many customers want each item:** RICE. 5. **You want to know which features will delight vs which are table stakes:** Kano. 6. **You are balancing several goals, like revenue and retention:** weighted scoring. Many teams combine two: a quick 2x2 or MoSCoW pass to cut the list, then RICE or weighted scoring on what is left. To score your own backlog with RICE, ICE or value vs effort, use the free [feature prioritization calculator](/tools/feature-prioritization-calculator). ## Where the input data comes from Every framework above is only as good as its inputs. Reach, demand and confidence should come from what customers actually asked for, not from memory. A [feedback board](/feature-voting) collects requests and votes in one place, and a [public roadmap](/public-roadmap-software) shows customers what you decided. FeatureOS does both, and links each roadmap item to the requests behind it. For broader models beyond prioritization, see [seven product management frameworks](/blog/7-product-management-frameworks) and the [opportunity solution tree](/glossary/opportunity-solution-tree). Spot an error? Tell us on our [feedback board](https://feedback.featureos.app) and we will fix it.