Performance matrix (IPMA): A guide for engineering leaders
How to weigh performance against importance so you invest where it counts, and why that's harder to judge now that AI is reshaping the metrics themselves.
Importance-performance matrix analysis (IPMA) is a technique for analyzing and visualizing data to help inform decisions on where to focus.
IPMA is widely used in marketing research and can be a powerful tool for determining investments in improving developer experience.
What is a performance matrix?
A performance matrix, more formally an importance-performance matrix analysis (IPMA), plots two things against each other for a set of items: how important each one is, and how well it’s currently performing. The result is a quadrant chart that turns a long list of possible investments into a single, visual priority map.
IPMA typically looks like the chart below, where performance is plotted along one axis and importance on the other. These charts are sometimes called performance matrices, since the same layout applies whether you’re comparing one item or many.
Performance and importance can mean different things depending on the context. For developer productivity metrics, performance refers to a specific metric (say, PR review time or deployment frequency), while importance is based on statistical regression using PLS or Pearson’s, showing how strongly that metric relates to an outcome you care about, like developer satisfaction or throughput.
How to read the chart
Start with the bottom-right quadrant
Interpreting an IPMA chart can be tricky. Generally, you want to focus first on items plotted in or near the bottom-right quadrant: these are your highest-importance and lowest-performing areas. That’s where the same investment of time or budget returns the most improvement.
Items in the top-right (high importance, high performance) are worth protecting, not fixing. Items in the left half of the chart, regardless of performance, are lower-leverage places to spend your next quarter.
Numbers point, they don’t decide
But as with any statistical analysis, it’s important to be mindful that numbers are only that. Decisions should be made based on evaluations of feasibility, business goals, and further investigation of causality.
IPMA in the age of AI-assisted engineering
AI coding assistants have made this kind of prioritization more important, not less. It’s now common to see “speed” metrics climb (more code, more PRs, faster first drafts) while quality and ease metrics stay flat or even dip. Without a way to weigh performance against importance, teams risk celebrating a metric that moved while missing the one that actually predicts developer experience or business outcomes.
IPMA helps separate real gains from AI-inflated ones. If AI adoption has pushed a low-importance metric up, that’s not where to keep investing. If a high-importance metric is still underperforming despite AI adoption (code review time, for instance), that’s your signal to dig into process or tooling, not just add more AI usage on top.
Where DX fits
DX builds IPMA charts directly into the platform so leaders aren’t just looking at metrics, they’re seeing which ones are worth acting on. The idea was originally suggested by Dr. Nicole Forsgren, based on her experience applying IPMA to early DORA survey work. Today, DX plots IPMA against the DX Core 4, the more complete framework that replaced DORA as the industry standard for measuring speed, effectiveness, quality, and impact.
That same logic now extends into AI. AI Impact Analysis shows whether AI coding assistants are actually improving performance, not just usage. AI Usage Analytics shows adoption by team and tool, which is the “importance” half of the picture. Run both through an IPMA lens and it’s clear whether an AI investment is high-importance and underperforming (worth fixing) or already paying off (worth protecting).
On the developer experience side, the Developer Experience Index (DXI) captures the conditions developers need to deliver effectively, and Workflow Analysis helps pinpoint where friction is concentrated. Executive Reporting turns all of this into the kind of prioritized view leaders need when deciding where to invest next.