A prioritization matrix is a grouping option on any features board that lets you visualize the value/effort tradeoff across all features related to a given objective, making it easy to spot low-hanging fruit (features with high value and low cost).
In this article:
Warning: This is only available on the Legacy experience (that means features boards or older roadmaps). It is not available on grids, timelines, column boards, or other parts of the New experience. If your workspace was created in 2025, you don't have access to the Legacy experience.
- Creating a matrix
- Prioritizing within objectives on the matrix
- Data always stays in sync
- Displaying additional measures of effort on the horizontal axis
- See also
Creating a matrix
- On the header of any features board, click Grouped by.
- Select Matrix from the dropdown.
Prioritizing within objectives on the matrix
Matrices are based on objectives but they display features, which are represented by circles. The color of a circle is its priority relative to your selected objective, and bigger circles have higher User Impact Scores.
- Select an objective to see all the features that have been added to it.
- Drag features vertically to update their value to the objective. (Hold shift to lock horizontal position.)
- Drag features horizontally to update their effort estimates.
- Reference bubble size, representing each feature's user impact score.
- Set each feature's final priority to the objective, and add it to a release.
With the final priority set, you can then update a feature's status/release to indicate when it will be worked on. See all your features grouped by objective on your Roadmap.
Data always stays in sync
If a feature's value or effort data is updated somewhere else in Productboard, or even in a synced story points field in Jira, its position on the matrix is updated in real-time.
Displaying additional measures of effort on the horizontal axis
In addition to the standard effort field, you can create your own custom dropdown fields to capture additional measures of effort and display these on the horizontal axis of your matrix.
This could be especially helpful for tracking preliminary high-level effort estimates (e.g. t-shirt sizes) before receiving final estimates.