RICE
Live
When you need a relative ranking that balances reach, impact, confidence, and effort, with live ranking feedback as people score.
All modules
Async prioritisation
The loudest voice still sets the roadmap
Ranking meetings reward volume and seniority. Spreadsheets go quiet after the workshop. Run an async prioritisation exercise people can finish on their own time. Then review the evidence, make the call, and publish a decision you can stand behind.
RICE · MoSCoW · WSJF · MaxDiff
No paid stakeholder seats
Jira · Azure DevOps · GitHub · GitLab
Published decision record
Works with JiraWorks with Azure DevOpsWorks with GitHubWorks with GitLab
EU hosted Google & Microsoft SSO GDPR-ready operations
What usually goes wrong
These are the failures the workflow is built to avoid — with a clear host-owned exercise people can finish on their own time.
- Ranking meetings reward volume and seniority, not evidence.
- Stakeholder input arrives late, incomplete, or not at all.
- The “decision” disappears into a slide deck no one revisits when trade-offs resurface.
At a glance
One async exercise. Clear roles. A published outcome.
Create from your backlog
Pull the work you already have, pick the method, and set a response window before anyone is invited.
Invite stakeholders
People join with their own Google or Microsoft account. They are not billed as paid Ibis Flow seats.
Collect structured input
Stakeholders score or categorise on their own time. Each method has its own UI, with live ranking feedback as they go.
Review as host
See completion, comments, and an AI debrief. Band Now / Next / Later / Won't Do. You keep the final call.
Publish and carry forward
Share a decision record stakeholders can read, then push priority back into your backlog.
Create
Set up from your backlog
Start from the work you already track. Choose the method and response window, then invite people when the exercise is ready.
Host
Choose tickets from your backlog
Connected boards, filters, or a manual list
- Pull from Jira, Azure DevOps, GitHub, or GitLab
- Continue from an estimation backlog when sizing already happened
- Add short guidance so people score the same way
- Set a response window people can actually finish
Techniques
Techniques you can run today
Pick the method that fits the decision. RICE, MoSCoW, WSJF, and MaxDiff are live. Buy a Feature is next.
MoSCoW
Live
When release shape matters more than a ranked list: Must / Should / Could / Won't categories people can finish quickly.
WSJF
Live
When flow-based teams need Cost of Delay signals (value, time criticality, risk/opportunity) before job size.
MaxDiff
Live
When you need sharper trade-offs: most/least choices across focused sets, without rating-scale inflation.
Buy a Feature
Soon
Budget-based workshops where stakeholders reveal what they value most. Coming next on the same platform.
Invite & contribute
How stakeholders take part
Invited people sign in with Google or Microsoft and contribute on their own time. They are not billed as paid Ibis Flow seats.
Stakeholder
Live ranking updates while they score
RICE on their own pass: ranking moves as each score lands
Stakeholder
RICE scoring on desktop
Score the item, watch the ranking move
- Stakeholders use their own Google or Microsoft sign-in
- No paid Ibis Flow seat required for contributors
- Contribute on their time, not in a fixed meeting slot
- Live ranking feedback shows the effect of each score
- Ask questions publicly or privately to the host
- Same invite model across RICE, MoSCoW, WSJF, and MaxDiff
Review
Review responses, then decide
When responses are in, you see completion, comments, and an AI debrief. The debrief is advisory. You band items (Now / Next / Later / Won't Do) and set the order.
Host
Band items into Now / Next / Later / Won’t Do
Drag to shape what ships when
- See response spread and completion, not just a single score
- AI debrief surfaces themes; it does not decide for you
- Drag items into delivery bands before you publish
- Capture rationale so the decision survives the next debate
- The host makes the final call
Publish
Publish the decision and carry it forward
Publish an immutable snapshot stakeholders can read. Carry priority back into your backlog so the outcome stays with the work.
- Immutable published snapshot, not a spreadsheet export
- Contributors see the outcome of the input they gave
- Carry priority back into your backlog for delivery planning
- Everyone can refer to the same published record
Who takes part
Clear roles for the host and for people who contribute input.
Product owners & PMs
Run the exercise, keep decision ownership, and leave with a publishable record.
Engineering & delivery leads
Contribute structured signals without another ranking meeting.
Customers, partners & leadership
Join with Google or Microsoft, no paid seat, and finish on their own time.
How this differs from common alternatives
Compared with spreadsheets, ranking meetings, or tools that auto-rank for you:
A published record people can reopen
You leave with a decision linked to the backlog you already use — ready when trade-offs return.
Async input with quieter voices included
People finish on their own time. You review the evidence and publish once the picture is clear.
Scores inform; you still decide
You band, annotate, and publish. Judgement stays with the host.
Compare prioritisation approaches
Async stakeholder input—not another ranking meeting
Meeting facilitators, spreadsheets and auto-rank tools can all help. The useful question is whether quieter voices can contribute on their own time, and whether the published decision lives with your backlog.
Compare this
Ibis Flow Prioritisation
What to check in a focused tool
Compare this Primary job
Ibis Flow Prioritisation Structured stakeholder input and a host-published decision
What to check in a focused tool Is the product optimised for live facilitation, spreadsheet scoring, or automatic ranking?
Compare this How people contribute
Ibis Flow Prioritisation Invited stakeholders finish on their own time with Google or Microsoft sign-in
What to check in a focused tool Do contributors need a paid seat, a shared workshop slot, or a spreadsheet login?
Compare this Who decides
Ibis Flow Prioritisation Scores inform; the host bands, annotates and publishes
What to check in a focused tool Does the tool auto-rank, or leave the call with the product owner?
Compare this Decision record
Ibis Flow Prioritisation A published outcome tied to backlog work you already use
What to check in a focused tool Where does the final ranking live when trade-offs return next quarter?
Compare this Who is billable
Ibis Flow Prioritisation Contributors use their own sign-in—no paid seats for invited stakeholders
What to check in a focused tool Is pricing per active participant, per workshop, or per editor seat?
Compare this Wider workflow
Ibis Flow Prioritisation Sits with Story Studio and Estimation on the same connected backlog
What to check in a focused tool Do you need prioritisation alone, or a path from craft → rank → size?
A meeting or spreadsheet tool is enough when
- The whole group can meet live and facilitation is the main need
- A one-off ranking in a sheet is acceptable afterwards
- You do not need a published decision linked to the backlog
- Stakeholder seats or participant billing are not a concern
Choose Ibis Flow Prioritisation when
- Quieter voices need time to contribute without another ranking meeting
- Stakeholders should join with their own sign-in, without paid contributor seats
- You want scores that inform the host—not an automatic roadmap
- The published decision should sit next to crafting and estimation on the same backlog
Input is async. Judgement stays with the host.
Prioritisation collects structured signals so you can publish a decision you can reopen later—not so a model can set the roadmap for you.
Where this sits in your delivery loop
Prioritisation fits between shaping work and sizing it.
Estimation
Size the work you just ranked, or start prioritisation from an estimation backlog.
Take the ranking meeting out of the room
Free trial. No credit card. Invite stakeholders, keep the call, and publish a decision you can stand behind.