Tools
Prioritization — RICE, MoSCoW, Kano & the 90% Rule
Prioritization lives in the Elaborate & Evaluate phase. Open the Prioritization hub from the board to see everything ranked and grouped in one place. Each method is also a tool you can add individually.
RICE
Score an item by Reach × Impact × Confidence ÷ Effort. Sandbox computes the score for you and the hub ranks items high-to-low. Great for comparing a backlog of features objectively.
- Reach — how many people, per period.
- Impact — Massive (3) → Minimal (0.25).
- Confidence — how sure you are (100% / 80% / 50%).
- Effort — person-months.
MoSCoW
Classify each item as Must, Should, Could, or Won't (this time). Fast and great for scoping a release. The hub groups items into the four buckets. Add a short rationale — and note what would change the call.
Once you've made a call, Challenge the call plays devil's advocate: Sandai argues for the category it would pick — often "is this really a Must-have, or scope creep?" — and proposes that category and a defending rationale as a reviewable suggestion. Your call stands unless you apply the change.
Kano
Understand how customers feel about a feature. Capture two reactions:
- Functional — how they feel with the feature.
- Dysfunctional — how they feel without it.
Sandbox maps the pair to a Kano category — Attractive, One-dimensional, Must-be, Indifferent, Reverse, or Questionable — so you can tell delighters from table-stakes.
The 90% Rule
A critical screen for which experiments to even start. Define:
- 3 minimum criteria — all must pass.
- 3 ideal criteria — must pass 2 of 3.
Sandbox returns a verdict: Start, Hold, or Drop. Use it to be ruthless before you spend time building.
Which should I use?
- Comparing many features objectively → RICE.
- Scoping a release fast → MoSCoW.
- Deciding what will delight vs. what's expected → Kano.
- Filtering experiments before you commit → 90% Rule.