<aside>

**Use Cases | Frameworks | Leave a Review | Need help?**

</aside>

<aside>

The fastest way to prioritize what to build next with frameworks your team can trust.

Make high-stakes prioritization fast, fair, and evidence-based.

I use these best practices with my teams every day.

When to Use This

• Executive Alignment → Share a scored list for quarterly planning - no more feature fights.
• Sprint Planning → Use top-ranked epics in sprints - the team know why it matters.
• Ad‑Hoc Triage → Run surprise asks through the model - stay disciplined under fire.

Prioritization Principles

• Start with data, not opinions.
• If data is missing, trust your gut - briefly.
• Pick 1–3 frameworks and stick to them.
• Don’t over-analyze. Action beats perfect scoring.

[https://embed-v2.testimonial.to/badge/darpan-dadhaniya?backgroundColor=513dd9&starColor=ffa500&fontColor=ffffff&fontFamily=Roboto&reviewTerm=review&fontSize=16&avatarSelection=automated&reviewTermPlural=reviews&alignment=center&customTemplate=Loved+by+{total}+teams&data-resize="true" data-resize-width="true" style="width:fit-content"](https://embed-v2.testimonial.to/badge/darpan-dadhaniya?backgroundColor=513dd9&starColor=ffa500&fontColor=ffffff&fontFamily=Roboto&reviewTerm=review&fontSize=16&avatarSelection=automated&reviewTermPlural=reviews&alignment=center&customTemplate=Loved+by+{total}+teams&data-resize="true" data-resize-width="true" style="width:fit-content")

https://testimonial.to/darpan-dadhaniya

</aside>

<aside>

3 Frameworks for Every Stage

Choose one framework based on your product maturity.

<aside>

Value vs Effort

What it is: Expected benefit of each initiative against the resources required to deliver it

When to use: Quick sanity check when you lack detailed data. This is the best method for a pre-product market fit stage SaaS when you don’t have enough data.

<aside> <img src="/icons/light-bulb_orange.svg" alt="/icons/light-bulb_orange.svg" width="40px" />

Formula: $Value /Effort$

</aside>

Example

<aside>

Impact Confidence and Effort (ICE)

What it is: Lightweight score balancing potential benefit and certainty against cost.

When to use: Products or features with limited reach data. This is the best method for a product market fit stage SaaS when you have some data.

<aside> <img src="/icons/light-bulb_orange.svg" alt="/icons/light-bulb_orange.svg" width="40px" />

Formula: $(Impact * Confidence) / Effort$

</aside>

Example

<aside>

Reach Impact Confidence and Effort (RICE)

What it is: Data‑driven score adding a Reach multiplier to ICE.

When to use: When you can estimate how many users will be affected. This is the best method for a mature stage SaaS when you have a lot of data.

<aside> <img src="/icons/light-bulb_orange.svg" alt="/icons/light-bulb_orange.svg" width="40px" />

Formula: $(Reach * Impact * Confidence) / Effort$

</aside>

Example

<aside>

Best Practices

• Consistent scales: Use consistent 1–5 or 1–10 scoring scales.
• Set clear cut‑offs: Define “Now” cutoffs (e.g. ICE ≥ 5, RICE ≥ 3,000).
• Re‑score regularly: Refresh scores monthly or after big shifts.
• Annotate “why”: Add 1‑line “why” notes to each score. </aside>

<aside>

</aside>

<aside>

</aside>

<aside>

• Sitemap

  Playbooks

</aside>