Application/Major Feature Prioritization Matrix
This file is part of the 280 Group Product Roadmap Toolkit™.
LEARN MORE ABOUT THE PRODUCT ROADMAP TOOLKIT
NOTE: Purchase All 8 of the 280 Group Toolkits and save 50%!
LEARN MORE
Instructions:
1.) The Feature Prioritization Matrix lets you rank features within a product against your business criteria to make trade-off dec
If you need to rank across major projects and initiatives, you should use the "Prioritization Matrix for Multiple Projects."
2.) The "Matrix Example" worksheet provides an illustration of how to fill out the prioritization matrix for a fictitious software com
3.) Switch to the "Blank Matrix" to start creating your own feature prioritization
4.) Assign a weight for each criteria in cells E13 through L13 (make sure they add up to 100.) Build consensus with all stakeho
and executive team as to the weights for each criteria. This is an important step in assuring buy-in with the prioritization.
5.) Enter the details for each Application, Major Feature, Feature Set, or Service on its own line.
6.) Assign a priority for each criteria for each application/feature (0 to 5.) These ranking must be defensible
and it is a good idea to involve key stakeholders in the ranking process.
7.) When finished adding and prioritizing all applications/features, sort results by selecting all filled in rows starting at column B
8.) Then sort the data in descending order based on column M (Total score )
9.) You now have a prioritized and ranked list of applications and features to work with your engineering and other teams to de
*********************************************************************************************
280 Group and the Product Roadmap Toolkit™ are licensed trademarks of the 280 Group LLC.
Copyright 2003-2014, 280 Group LLC. All Rights Reserved
This file I governed by a SINGLE USER LICENSE and may not be used by more than one person. For multiple user licenses cont
This file and its contents may NOT be distributed without written consent from the 280 Group.
Legal Disclaimer: Use this at your own risk. No warranty is implied, and it is not intended to provide legal, marketing or any ot
280 Group LLC will not be responsible for any losses incurred due to the use of this file.
usiness criteria to make trade-off decisions and build consensus.
on Matrix for Multiple Projects."
on matrix for a fictitious software company.
00.) Build consensus with all stakeholders
ring buy-in with the prioritization.
ust be defensible
all filled in rows starting at column B15 to column M39
ur engineering and other teams to determine where the cutoff line should be.
rson. For multiple user licenses contact the 280 Group.
to provide legal, marketing or any other type of advice.
The company in this example has weighted the criteria towards delighting the user (removing pain points) and retaining existing
customers as their highest priorties.
If new buisness was more important, or if the financial buyer was not the end user, then the company might have emphasized Key
Product Differentiatior and competitive necessity higher. Changing the wieghtings would yeild different priorities.
It is important to understand your priorites and get buy-in across all stakeholders.
Prioritization Matrix
0 =low
5= high Total points
Weight1 25 20 15 15 15 10 0 0 100
Upsell revenue
% of customers from existing Revenue from new <add your own criteria <add your own
Application/Major Pain for User2 impacted3 customers4 customers Key product differentiator Competitive necessity here> criteria here> TOTAL
Feature/Service Details Requestor (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) SCORE
Reduce launch time Customers, Tech
1 Launch performance to <2 second support 5 5 0 0 0 5 0 0 55
Pull data from other
applications to
2 Auto-entry for signup reduce signup time Customers 3 5 2 1 2 4 0 0 58
Full data
import/export with
3 Integration with SF.com SF.com database Sales, Customers 4 2 0 0 5 0 0 0 43
Full compatibilty with
IE 7 plus support for Customers,
4 IE 7.0 support new security features Management 4 3 2 5 0 5 0 0 63
5 #N/A
6 #N/A
7 #N/A
8 #N/A
9 #N/A
10 #N/A
11 #N/A
12 #N/A
13 #N/A
14 #N/A
15 #N/A
16 #N/A
17 #N/A
18 #N/A
19 #N/A
20 #N/A
21 #N/A
22 #N/A
23 #N/A
24 #N/A
25 #N/A
1
weights shoulud total 100
2
consider how difficult a feature is to use and how frequently that feature is used in assessing pain
3
must take into account the % of customers impacted and their importance
4
You should count retaining customer who would otherwise leave as $
Remember to adjust the weight of the
criteria, ensuring they add up to 100.
Prioritization Matrix
0 =low
5= high Total points
Weight1 20 20 15 15 15 15 0 0 100
Upsell revenue
% of customers from existing Revenue from new <add your own criteria <add your own
Application/Major Pain for User2 impacted3 customers4 customers Key product differentiator Competitive necessity here> criteria here> TOTAL
Feature/Service Details Requestor (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) (0 - 5) SCORE
1 #N/A
2 #N/A
3 #N/A
4 #N/A
5 #N/A
6 #N/A
7 #N/A
8 #N/A
9 #N/A
10 #N/A
11 #N/A
12 #N/A
13 #N/A
14 #N/A
15 #N/A
16 #N/A
17 #N/A
18 #N/A
19 #N/A
20 #N/A
21 #N/A
22 #N/A
23 #N/A
24 #N/A
25 #N/A
1
weights shoulud total 100
2
consider how difficult a feature is to use and how frequently that feature is used in assessing pain
3
must take into account the % of customers impacted and their importance
4
You should count retaining customer who would otherwise leave as $
CAUTION: This lookup table (name = score) is necessary for scoring. Do not alter or erase.
0 0%
1 20%
2 40%
3 60%
4 80%
5 100%
Do not alter or erase.
