Jira Product Discovery: Build an impact-effort matrix
Create a Jira Product Discovery impact-effort matrix through Views → + Create a view → Matrix view, then select Effort and Impact as the axes.
Ideas need values for both fields to appear. Use the matrix to inspect trade-offs and missing estimates rather than assuming the visually attractive corner is an automatic roadmap decision.
Step-by-step guide
Prepare comparable impact and effort values
Use a licensed creator or space administrator with Manage Views permission. Choose a shared scale for both axes and populate a few ideas in a list view. For example, rate customer impact and estimated effort consistently for an export-alert improvement, onboarding guide and billing redesign. Ask a space admin to create missing scoring fields; mark guesses in the supporting evidence.
Create and name the matrix
Choose Views → + Create a view → Matrix view. Set Effort on X and Impact on Y, then add an About this view explanation of the scales and intended audience. Verify orientation before interpreting any quadrant.
Populate and inspect the plotted ideas
Ideas with both field values appear in the matrix. Add an existing idea using the blue + control if needed. If an idea is missing, inspect its axis values and filters before assuming it was deleted or excluded by a product limitation.
Review trade-offs with the source evidence
Open high-impact, low-effort candidates and check their evidence and uncertainty. Bubbles based on custom formulas or multi-select fields cannot be dragged, so adjust the inputs rather than trying to reposition those bubbles manually.
Common mistakes
Reading blank inputs as low effort
An unplotted idea may simply lack an estimate. Resolve missing data before comparing the apparent shortlist.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.