Key Performance Indicator (KPI)

Key Performance Indicator (KPI) image
A key performance indicator (KPI) is a measurable value a team or organisation tracks to judge progress towards an important goal. In software and quality engineering, KPIs might cover things like escaped defects, lead time, test pipeline stability or customer-reported issues.

Why it matters: Well-chosen KPIs help teams see where they are improving and where they are not, and give leaders evidence for decisions. Poorly chosen ones do harm: when metrics are imposed from above, the people doing the work rarely buy into them or feel accountable for them, and the numbers end up ignored or gamed. The phrase "if you can't measure it, you can't manage it" is often quoted to justify KPIs, though the original idea was closer to the opposite.

In practice: KPIs work best when they are built with the team rather than for it. Leaders can ask the team what successes were missed, what failures could have been avoided and where they want to improve, then agree a small set of measures that reflect those answers. The team reviews the KPIs on a regular basis, adding, changing or dropping them so they stay relevant.

Examples:

  • A team that agrees to track production incidents caused by changes after noticing too many weekend call-outs.
  • Engineers choosing to measure flaky test reruns because pipeline delays were their biggest frustration.
  • A set of managers' metrics nicknamed after the person who wrote them, a sign the team never adopted them.

Common pitfalls:

  • Creating KPIs in a managers-only meeting and presenting them to engineers as finished, so nobody feels ownership.
  • Setting KPIs once and never reviewing them, so they keep measuring problems the team has already solved.

What is the difference between a KPI and a metric? Any measurement is a metric. A KPI is a metric the team has chosen because it tracks progress towards a goal they care about.

What are good KPIs for a testing team? That depends on the team's goals, which is why the team should help choose them. Common starting points include escaped defects, time to detect issues and pipeline reliability.
Explore MoT
Test Forward 2027 ยท Software Quality in the age of AI image
Tue, 19 Jan 2027
Test Forward is one afternoon at Station F with the QA and engineering people closing that gap in their own teams.
Introduction To Modern Testing image
Learn the Modern Testing principles that will help the whole team deliver high quality software
This Week in Quality image
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community
Subscribe to our newsletter