Compare and score customer requests

Open Prioritize in the sidebar. Prioritization is available on Pro and above. Use it to compare ideas using the same criteria, with customer demand alongside the scores.

Choose how to work

View Use it to
Score ideas Enter criterion values, compare scores and show customer-context columns
Compare Compare numeric criteria on a chart, or view ideas grouped by category
Team scoring Collect people's scores separately, then review and apply the results

Start with a small set of requests you understand. Use the filters to narrow the list and View to choose context columns. Sort by a score or criterion to compare the full filtered result set.

Choose a model

Open More → Scoring setup and select the framework you want to use.

Model What it compares
RICE Reach, impact and confidence against effort
ICE Impact, confidence and ease
Impact-Effort Expected impact against effort
WSJF Business value, time criticality and risk reduction/opportunity against job size
MoSCoW Must, Should, Could and Won't categories
Kano Categories describing how a feature relates to customer expectations
Custom weighted model Criteria and percentage weights you define

Use consistent meanings for values across the ideas you compare. Kano here is a category classification, not a customer survey that calculates categories from paired questions.

Enter scores or collect team input

In Scoring setup, choose how scores should change:

  • Edit in the table: team members with access can update scores directly.
  • Publish from team sessions: scores change after a team's results are approved and applied.

For direct scoring, enter the values in Score ideas and inspect the calculated score. AI suggestions can provide starting values for review. If several people should weigh in independently, start team scoring.

Compare ideas visually

Select ideas and open Compare. For numeric models, choose the X-axis, Y-axis, bubble size and color. Up to twenty ideas can be compared at once. When using impact and effort axes, the chart labels the four combinations, including quick wins and major projects.

Where direct editing is enabled, you can drag points or edit their values. Category-based models show groups instead of a numeric matrix. Use a live workshop to discuss the same set of ideas with your team.

Create a custom model

  1. Open More → Scoring setup → Add custom model.
  2. Name the model and add your criteria.
  3. Give each criterion a percentage weight. The total must be 100%.
  4. Set its direction and optional guidance so scorers know what a higher score means.
  5. Use Test your model to try example values and inspect the score breakdown.
  6. Save the model and select the scoring workflow.

Review scores alongside customer segments, revenue and comments. When you decide to pursue an idea, link it to roadmap work.

Run a first comparison with WSJF

WSJF compares the value of doing work soon with the size of that work.

  1. Open Prioritize → More → Scoring setup and choose WSJF. Use direct table editing if you want to enter the values yourself.
  2. Return to Score ideas and filter to the requests you want to compare.
  3. For each request, enter Business value, Time criticality, Risk reduction / opportunity and Job size. Use the same scale and meaning for every request.
  4. Check the calculated score and sort by Score to compare the requests.
  5. Open the strongest candidates and check their customer context before choosing what to put on the roadmap.

The score is (business value + time criticality + risk reduction) / job size. For example, values of 8, 5 and 3 with a job size of 4 give a score of 4. These are illustrative values, not suggested scores for your product.

If the score is blank, check that every required criterion has a value and that job size is greater than zero. A higher score helps compare these ideas; it does not automatically schedule the work or change a status.

Compare revenue or a particular customer group

In Score ideas → View, show the customer-context columns you need, such as votes, MRR or LTV. The revenue on a request comes from its voters, with each company counted once. It is separate from the chosen model's score.

Use customer segments when the question is about a plan or customer group. For the most requested features from one business, start with its company page, then bring that context into your scoring decision.