7.6Leading vs Lagging Quality Indicators

Definitions

Type	Definition	Example
Leading indicator	Predicts future quality. Changes before quality changes.	Code review coverage, test automation ratio, requirement clarity score
Lagging indicator	Reflects past quality. Changes after quality changes.	Production defects, customer complaints, escaped defect rate

Why Leading Indicators Matter More

Lagging indicators tell you what already happened. By the time you see a spike in production defects, the damage is done. Leading indicators warn you before the damage occurs.

Key Leading Indicators for QA

Leading Indicator	What It Predicts	How to Measure
Code review coverage	Fewer bugs in tested code	% of PRs reviewed by at least one person
Requirement clarity score	Fewer ambiguity-related bugs	% of stories with testable acceptance criteria
Test automation growth rate	Faster feedback, fewer regressions	New automated tests per sprint vs new features per sprint
Flaky test trend	Pipeline reliability and trust	Flaky rate trend direction (up/down)
Technical debt trend	Long-term quality trajectory	Test debt items created vs resolved per sprint
Build success rate	Development stability	% of CI builds that pass on first attempt

The Balanced Quality Scorecard

Use a mix of leading and lagging indicators:

Category	Leading Indicator	Lagging Indicator
Defects	Code review coverage, static analysis violations	Escaped defect rate, customer-reported bugs
Speed	Automation ratio, pipeline execution time	Lead time for changes, deployment frequency
Reliability	Flaky test rate, environment uptime	MTTR, MTTF
Coverage	Test automation growth rate, requirement coverage	Risk-weighted coverage, mutation score