A roadmap discussion often contains several reasonable demands that cannot all be met. A customer needs an integration, support wants an awkward workflow repaired, and the team has an idea that could attract a new audience. The difficulty lies in comparing those claims without allowing the loudest advocate to decide by default.
Feature prioritisation makes that comparison explicit. It considers the outcome a change might create, the people affected, the effort and dependencies involved, and the strength of the supporting evidence. The process is useful when it reveals why a choice has been made and what could change it.
Establish the decision before scoring ideas
A team trying to improve first-time adoption will judge work differently from one addressing reliability for long-standing customers. State the objective and relevant constraints before choosing a scoring framework. Essential maintenance or a serious accessibility problem may require action regardless of how an optional feature scores.
It can also help to move back from proposed features to the problems they address. Several requests might point to the same difficulty, with a simpler response available than any of the suggested solutions. An opportunity solution tree provides one way to explore that relationship.
Make estimates inspectable
Intercom’s RICE framework compares reach, impact, confidence and effort. Its value is partly conversational: it asks the team to state assumptions that might otherwise remain hidden. A calculation cannot make an unsupported impact estimate reliable, and a small numerical difference should not be treated as precision the evidence does not warrant.
An illustrative team comparing an import repair with a new dashboard might find that the repair affects fewer people but resolves a documented barrier to starting work. The dashboard has broader potential reach, yet little evidence that customers need it. Depending on the objective, that uncertainty may justify testing the dashboard concept before committing to delivery.
Use research to improve the assumptions. Observed difficulties, usage patterns and customer circumstances offer different evidence from request counts alone. A request submitted by several contacts at one company is not necessarily a problem shared by the wider market.
Leave a record that can be revised
Document the decision, its main assumptions and the evidence that would prompt reconsideration. Dependencies may change, an estimate may prove wrong, or new research may reveal a more important need. Revisiting priorities is easier when the reasoning survives beyond the meeting.
The result need not be a finely ranked list of everything the team could ever build. A clear choice about what to do next, what to investigate and what to defer is often more useful. Prioritisation earns its time when it directs effort towards a meaningful outcome and makes the trade-offs understandable to the people affected.