How should I make the decision?

Score a small backlog together and inspect whether changing one uncertain input reverses the order. Record the evidence and remaining uncertainty before committing.

ICE vs RICE for growth prioritization

The decision belongs in your wider saas growth plan. Start with the customer task and operating constraint, then compare the options against that context.

Where each option fits

ICE scoring

ICE can support a lightweight comparison using impact, confidence and ease when estimates are rough and the backlog is small.

RICE scoring

RICE adds explicit reach and effort, which can help compare work affecting very different audience sizes.

The comparison that matters

Dimension	What changes the decision
Inputs	Impact confidence ease versus reach impact confidence effort.
Use	Fast discussion versus more explicit exposure and capacity.
Risk	Subjective scales versus false precision in estimated reach.

The table is a decision framework, not a claim that one option always wins. A useful choice accounts for the work your team can perform, the customer experience it must support and the evidence available today.

Avoid this mistake

Multiplying uncertain estimates does not turn them into objective truth. Scores should expose assumptions, not hide judgment.

Before comparing results, align the scope. Write down what is included, who does the work and which time period matters. If a comparison uses different definitions on either side, resolve that mismatch before interpreting the numbers.

Run a practical evaluation

Score a small backlog together and inspect whether changing one uncertain input reverses the order.

Choose one representative workflow or customer situation. Avoid a demonstration that removes the difficult part of your actual case.
Define the required outcome and the conditions that would make an option unsuitable. Include operational and customer-experience constraints.
Collect evidence under the same scope for both options. Record implementation effort, dependencies and unresolved questions.
Review the result with the people who will operate the choice. A decision that requires unavailable skills or capacity needs a different plan.
Record the choice and a review trigger. New customer needs, product changes or a different scale can justify revisiting it.

Document the decision

Item	Your evidence
Customer task	What the choice must help someone accomplish
Required capability	The condition that cannot be compromised
Full cost	Money, internal effort and ongoing responsibility
Main risk	What could make the choice fail in your context
Validation	The observation or test supporting the decision
Review trigger	The change that would justify another evaluation

Continue the evaluation

Browse the comparison library and working resources for related decisions.

Apply ice vs rice for growth prioritization in a working review

Choose a representative customer task and compare both options under the same constraints. Keep required capabilities separate from preferences, and document the cost of moving as well as the cost of staying. An attractive feature does not resolve a missing requirement. Leave unknown evidence visible and identify the test that could change the choice.

For this topic, involve the experiment owner and the analyst responsible for design integrity and work from hypothesis, assignment rules, metric definition and decision record. The relevant unit is the prespecified eligible user or account cohort. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

Check the design before interpreting a result. Assignment, exclusions, outcome timing and stopping rules can change the meaning of an apparently precise statistic. Separate practical effect from statistical evidence and keep guardrails beside the primary outcome.

Review field	What to record
Topic	ICE vs RICE for growth prioritization
Decision	The specific action this explanation should help you choose
Working evidence	hypothesis, assignment rules, metric definition and decision record
Unit and scope	the prespecified eligible user or account cohort
Responsible people	experiment owner and the analyst responsible for design integrity
Remaining uncertainty	The missing fact that could change the decision

Two situations that can change the interpretation

When the growth model assumes unlimited capacity

A model can become unrealistic when every new customer requires assisted onboarding but the implementation team never expands.

Use this check: List the operating resources required at each projected volume level. Do not present a planning scenario as a prediction or guaranteed trajectory.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When the experiment backlog ignores the main constraint

Changing a button color is unlikely to fix a workflow that requires an unavailable integration before any value can be reached.

Use this check: Map the current customer path and identify where suitable users fail to progress. A large drop-off is not automatically the best target if the users are intentionally ineligible.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

A higher signup rate is not automatically a better activation path if the removed step helped users reach a useful workflow. Review the complete sequence and the relevant customer outcome. A bundled product change can be evaluated as a bundle without claiming to isolate every component.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.