In a recent LinkedIn discussion, questions were asked about the short-comings of prioritization matrices. I would like to highlight the strengths and weaknesses of using such a tool for portfolio management. Firstly, a prioritization matrix differs from a more traditional scoring approach in that it offers a limited number of priority selections. The most simplistic prioritization matrix has three choices, low, medium, and high. Of course, to be effective, every choice should have some predefined criteria. Otherwise, the matrix is of little value because decision makers can have wildly different views for what is of high importance versus low importance.
Prioritization matrices have three primary strengths: simplicity, speed, and applicability to all types of work. Prioritization matrices are easy to understand and simple to use. Calculations are not required for determining the relative priority of a project. Basic criteria should be developed for each part of the matrix, but once complete, decision makers can apply the criteria to various types of work. Because of its simplicity, prioritization becomes a much faster exercise and allows decision makers to quickly distinguish important projects from less important projects. In addition, various kinds of work can be prioritized using a prioritization matrix. With a traditional scoring model, it is difficult to evaluate “keep the lights on” type of work, but with a prioritization matrix it is easier to compare priorities for project and non-project work.
Prioritization matrices are unable to produce a rank ordered list of projects in a portfolio. At best, such a matrix can provide a categorical ranking of projects in the portfolio, but this won’t help prioritize projects within the same category. Prioritization matrices cannot do a good job of evaluating projects based on multiple criteria, and therefore cannot do a thorough job of distinguishing important projects from less important projects. When evaluating multiple large projects, a scoring system will provide a more accurate analysis over a prioritization matrix.
When Should a Prioritization Matrix Be Used?
Prioritization matrices are good for organizations new to the portfolio management process. Due to the simplicity, organizations can quickly get the benefit of prioritization without spending the time to do a thorough scoring of each project. Even in organizations where projects are scored and ranked, prioritization matrices can be used for “pre-screening” purposes to do a preliminary prioritization. This would be commonly used in a stage-gate process before a formal business case has been developed. A governance team could quickly determine a categorical priority for the project at an early gate review. Prioritization matrices can also be used to triage large volumes of project requests to focus the organization on the hottest projects. I have seen this approach used in an organization that received a high volume of small project requests. In this case, scoring would be an over-kill; the organization just needed to determine the most important work at that time.
My personal approach is to right-size portfolio management processes to fit an organization's culture and maturity to be effective without creating a bureaucracy. Please contact me if you would like to know more about how project portfolio management (PPM) can help your organization achieve its strategic goals.
Latest posts by Tim Washington (see all)
- Know The Difference Between Work Intake Versus Stage-Gate - April 1, 2018
- Beware of Project Dependencies - July 9, 2017
- Portfolio Optimization—Data and Constraints - September 27, 2016