Scores for Features

When prioritizing Features for your roadmap, you need a way to consider many criteria that are important to your business. With Feature Scores, you create formulas that use these criteria and generate a number (Score) for each Feature. You can then use these Scores to compare Features and identify top performers. 

Note: You must be on the latest version of our Product Management platform to use Features. Learn more about Features here.


Setup custom fields
Create numeric custom fields for rating Features on criteria that are important to you; for example, Development Effort, Strategic Fit, Impact on Goal X. To learn how to set up Feature Custom Fields, check out this article

Setup Segments
Optionally, create Segments to help you focus on your target customers. To learn how to set up Segments, check out this article

Create a Score
Build a Score formula that uses these fields. The formula can be as simple or as complex as you would like - it depends on how you choose to prioritize your roadmap.

Values you can use in Score Formulas:
  • Numeric custom fields on Features
  • Feature User count, Account count, and MRR, including by Segment
We'll walk through this process using a "benefit/cost" Score as an example.  

Creating a Formula

Navigate to the Scores Tab
  • Click the Features icon (lightning bolt) in the left-hand menu
  • Click the gear icon on the far right
  • Select the Scores tab
  • Click "Create Score"
Create your Score
  • Label: This is the name of your Score and will show as a column header on the Features list.
  • Formula: Use the formula builder to create a formula for your Score. 
In this example, we'll be creating a Score to measure the benefit/cost ratio for each Feature. Our formula will use Feature Custom Fields that we have previously created and populated with data for each Feature. 

First, we'll add together 2 numeric Custom Fields which represent the estimated impact of a Feature on 2 goals: 'reduce churn' and 'increase sales'. We'll then divide this sum by a Custom Field called "dev effort" which is our cost. The resulting Score will be a benefit/cost ratio. 

(reduce churn + increase sales) / dev effort

Click "Save" to finish creating your Score. A Score column will be added to your list of Features automatically and will be displayed by default for all admins on your account.

*Please note: complex Scores may take several minutes to be calculated. Refresh the page after 1-2 minutes if your score is not displayed immediately.

Pro tips: 
Some popular score and prioritization frameworks include...
  • RICE (user reach x total impact x confidence / effort)
  • Total Impact (goal 1 impact + goal 2 impact +...)
Weighted Values: You may have some criteria that are more important for your prioritization method than others. You can assign your values a "weight" in the formula builder to reflect this. The screenshot below shows an example where "increase sales" is twice as important as "reduce churn".

Use Scores to Prioritize your Roadmap

Sort your Features by Score

After you have created a Score you will see it added as a column in your Feature grid. You can sort the list of Features by your Score column for quick analysis. 

Visualize your Scores

Feature Scores can also be used with the Chart to visualize your data. Charts allow you to analyze your features based on multiple criteria at once. For example, you could see how your Features compare to one another based on a 'total impact' Score on the x-axis and a 'dev effort' Custom Field on the y-axis.

First, you'll need to be in the Features section of the admin console (lightning bolt icon).

To use the Chart, click the chart icon (pie graph) on the left. Use the drop downs to select the values for the x-axis, y-axis, and bubble size. 

Common questions

Q. Can I create a Score that is not shared with other admins from my team?
A. Not at this time. Scores are shared between all admins on your account. 

Q. Why is my Score column showing errors?
A. If your score column is showing errors, this means that the Score's formula is attempting to divide by zero or is referencing a missing value. The "missing value" or 0 may be in a custom field, user, account, or MRR field. 

Feedback and Knowledge Base