Structured input, clear evidence, your decision to own
Most prioritisation decisions end up in one person's gut, or worse — a meeting where the loudest voice wins. Ibis Flow gives you a structured way to gather input from everyone who matters, review the evidence properly, and publish a decision people can trust because they could see how it was made.
A complete workflow from intake to published decision
This is not another spreadsheet exercise. Ibis Flow gives product teams one workflow that covers the whole exercise — from gathering evidence to making the call. The host reviews everything and decides. The stakeholders see the outcome. Everyone understands why.
One workflow, start to finish
Set up the session, gather input, review evidence, decide, publish, and carry the result forward without rebuilding the process in separate tools.
More voices, better evidence
Invite whole teams, leadership, delivery partners, and customers into the same structured exercise so decisions are grounded in real input — not just the product team's assumptions.
Connected to your backlog from the start
Use the work you already have in your backlog and move the output back into your delivery workflow without copy-paste or manual reconciliation.
How prioritisation works in Ibis Flow
The workflow is designed to keep contribution easy for stakeholders and judgement clear for the host.
Create the prioritisation session
Start a session from an estimation backlog, board filter, backlog view, manual list, or CSV import and define the scoring guidance and response window.
Invite stakeholders and customers
Stakeholders join through a secure link in their browser. No Ibis Flow subscription seat is required, which keeps participation friction low.
Collect structured stakeholder input
Stakeholders contribute through a guided experience — scoring with sliders for RICE or placing items into priority categories for MoSCoW. Live ranking feedback updates as they go, and they can ask questions publicly or privately to the host.
Review the evidence as host
Use statistical summaries, AI debriefing, comments, notes, and drag-and-drop banding across Now, Next, Later, and Won't Do to shape the final decision.
Publish the decision transparently
Generate and publish a final decision record for stakeholders to review, then carry the prioritised outcome back into your backlog and onward planning.
Step 1 — Set Up From Real Work
Start from the backlog you already have
Build the session from real delivery inputs instead of retyping items into another document. Hosts can pull in work from estimation sessions, boards, filters, manual entry, and CSV imports, then add scoring guidance, attachments, and response reminders in the same setup flow.
Start from an existing estimation session when prioritisation follows refinement
- Seed prioritisation directly from estimation sessions when sizing already happened
- Import from boards when the backlog is already team-shaped
- Use filters for targeted review sets, product areas, or release slices
- Add manual items or CSV rows for roadmap, OKR, and discovery work not yet tracked in your backlog
- Define scoring guidance, context, rich text notes, and supporting attachments before invitations go out
- Set response windows and automatic reminders from the same setup flow
Frameworks
Two frameworks live today, with more coming next
RICE scoring and MoSCoW categorisation are both available now — giving teams a choice between data-driven scoring and fast stakeholder alignment. WSJF, MaxDiff, and Buy a Feature are planned next so teams can grow into additional prioritisation methods on the same platform.
RICE
Collect Reach, Impact, Confidence, and Effort input through a guided stakeholder experience with live ranking feedback and host review.
WSJF
Weighted Shortest Job First for balancing value, urgency, and effort across competing work.
MoSCoW
Stakeholders place items into Must Have, Should Have, Could Have, and Won't Have categories through a guided experience with live category distribution and host review.
MaxDiff
Relative comparison scoring for sets where stakeholders need to make sharper trade-offs between options.
Buy a Feature
Budget-based prioritisation for workshops where stakeholders need to reveal what they value most.
Step 2 — Stakeholder Input
Make it easy for stakeholders to contribute properly
The stakeholder experience is built for participation, not training. People receive a secure link, score items with simple sliders, see the live ranking effect as they contribute, and ask questions publicly or privately. No Ibis Flow account required — which means you can include customers, delivery partners, and leadership in the same structured exercise, not just the people who already have a subscription.
Stakeholders see a clear queue of items they need to score
- Secure invite links with no stakeholder login or paid seat required
- Simple sliders instead of dense scoring forms so participation feels lightweight
- Live ranking feedback shows the effect of input as stakeholders contribute
- Questions can be raised publicly for the group or privately to the host only
- Track who has responded and nudge completion with automatic reminders
- Designed for internal teams and customer participation in the same structured exercise
Step 3 — Host Review
Evidence first. Your call last.
The host gets a decision workspace, not just a leaderboard. Review the statistical spread, stakeholder comments, and AI debriefing — then band items across Now, Next, Later, and Won't Do using drag and drop. The order is yours to set. The rationale is yours to record.
AI and statistics surface the main signals before the final call is made
- Review statistical spread and ranking movement, not just a raw total
- AI debriefing highlights themes, disagreement, and where judgement is still needed
- Drag items into Now, Next, Later, and Won't Do bands before finalising order
- Capture host notes and rationale alongside the review process
- Generate final decision wording in formal, concise, or narrative styles
- Prepare a publishable record built from rankings, comments, banding, and notes
Step 4 — Publish And Align
Close the loop — publish what you decided and why
When the call is made, publish the decision record. Stakeholders see the final ranking, the reasoning, and what happens next. Not a spreadsheet export — a clear record that closes the loop on the input they gave. That's what turns stakeholder contribution into real alignment, rather than just a box ticked.
- Publish an immutable decision snapshot that captures the final outcome clearly
- Give stakeholders a clean review view instead of expecting them to interpret internal tooling
- Carry final priority decisions back into your backlog for delivery planning and execution
- Transparency creates stronger alignment, clearer ownership, and better market-facing judgement
Use it wherever prioritisation decisions need broader evidence
The same workflow works for more than backlog grooming. It fits any product decision where you need structured input, transparent trade-offs, and a clear published outcome.
What's next
Coordinate delivery once the priorities are clear
Prioritisation tells you what to build. Team Planning — now in development — is where that list meets reality: which teams, in what order, by when.
Start running transparent prioritisation sessions
Free trial. No credit card required. Set up your first prioritisation workflow and invite stakeholders in minutes.