Score ideas with your team

Use Prioritize → Team scoring to collect independent opinions before deciding which ideas to pursue. You need a scoring model and the ideas you want to compare.

Start a session

  1. In Score ideas, select the ideas and choose Start team scoring, or open Team scoring → New session.
  2. Name the session, select its model and participants, and set a due date.
  3. Add context that helps everyone score the same question, then create the session.
  4. Participants open their invitation, enter their scores and submit them. They can include a rationale.

Individual answers remain private until the session closes. You can monitor completion without showing one person's scores to everyone else. At the due date, scoring closes and submissions become read-only.

Review and apply results

Open the closed session to inspect the results and team averages. Review differences before applying them. You can export revealed results as CSV.

Use the approval/apply action to bring agreed scores into Score ideas. Applying scores updates the prioritization values; it does not publish the feedback posts or promise that the work will be built.

Score together in a live workshop

Select up to twenty ideas and choose Start live workshop. The shared comparison lets participants discuss ideas, adjust criterion values and record the reasons for the decision. Progress can be saved before the final approval.

A workshop is useful when the team wants to work through tradeoffs together. Use independent scoring when you want each person's initial view before a discussion.

See scoring models and comparison views to choose the criteria and decide whether scores can also be edited directly.

Why can I not see or edit the scores yet?

  • The session is still open: individual submissions stay private until it closes. Use completion progress to see who still needs to respond.
  • The due date has passed: submissions are read-only. Review the revealed results rather than asking people to keep editing the closed session.
  • Results are visible but the main scores have not changed: review and apply the session results. Closing a session alone is not the same as applying its scores.
  • The scoring model uses approved sessions: update scores through that workflow rather than trying to edit them directly in the table.

A scoring result helps the team decide. To tell customers what is planned, separately link feedback to roadmap work.