Prioritise work
Product Feature Prioritisation
Compare features and improvements to determine which will create the greatest value for users and the organisation. Useful for product management, roadmap planning, and service development. The criteria can be changed, added to and weighted.
What the framework is
Product feature prioritisation compares proposed features and improvements to decide what to build next. The template starts with five criteria: Customer Value, Strategic Alignment, Ease of Implementation, Revenue Potential and User Demand. The criteria can be changed, added to and weighted.
What the result looks like
Overall
Overall with the criteria
| Rank | Options |
Customer Value
20%
|
Strategic Alignment
20%
|
Ease of Implementation
20%
|
Revenue Potential
20%
|
User Demand
20%
|
Overall
Weighted win rate
|
|---|---|---|---|---|---|---|---|
| 01 | Single sign-on |
63%
|
|||||
| 02 | Offline mode |
52%
|
|||||
| 03 | Custom reports |
35%
|
By the options
Scoring Explanations
When it earns its place
Use it for roadmap planning, quarterly reviews or triaging a long list of requests. It brings product, engineering, sales and support into one ranking instead of four separate ones.
The trap is user demand standing in for everything. The most requested feature is not always the most valuable. Comparing features on each criterion separately shows when demand and value point different ways.
How to run it with a group
- List the candidate features, each in a few words that everyone will read the same way.
- Agree the weights. Decide whether ease of implementation counts as much as value.
- Participants compare the features two at a time on each criterion. Participants do not need an account to respond. Include people from engineering and support, not only product. Three to six options keep it manageable: with five options and five criteria, each person makes 50 comparisons.
- Read the overall ranking, then the ranking per criterion, and check the top items against capacity before committing them to the roadmap.