Choose the next request, together

A request can be popular and still be the wrong next step. Another request may be quiet but remove a problem that affects every new customer. A useful priority discussion makes these differences visible. The aim is to agree on the next piece of work and to leave enough context for someone who was not in the meeting.

Compare the problem before the solution

Start by describing the outcome each request would support. Ask who is affected, how often the problem appears, and what the customer does today. This keeps the discussion close to the work people need to complete. It also helps the team notice when several suggested features are responses to the same underlying difficulty.

Separate evidence from assumptions. A recorded conversation is evidence that a person encountered a problem. An estimate that hundreds of people share it is an assumption until you have a reason to believe it. Both can inform a decision, but they should have different labels.

Write a small decision record

• Name the outcome you want to improve.

• Record the evidence and the questions still open.

• Assign an owner and a date to review the choice.

We chose this request because it removes a repeated obstacle in the first week of use.

Keep the record next to the request. When another idea arrives, the team can revisit the earlier reasoning instead of starting from memory. A review date also makes it clear that the choice can change when the evidence changes.

The Felmio demo uses fictional requests to show this structure. Its votes, statuses, and estimates are illustrative. They are examples of how to record a decision, rather than a scoring method or a promise that the most requested feature should always come first.