Most teams think they're further along in quality maturity than they are. Not because they're wrong about what they've built — but because they're missing a clear framework for what "advanced" actually looks like.
This is the model I use to assess teams and plan their quality roadmap.
The Five Levels
Level 1 — Reactive
Characteristics: Testing happens after development, manually, often by the developer who built the feature. No test documentation. Bugs found in production are the primary quality signal.
What it feels like: Every release is stressful. Production incidents are frequent. The team doesn't know what "enough testing" means.
Level 2 — Repeatable
Characteristics: A defined testing phase exists. Test cases are written, if not always automated. A QA role exists, even if informal. Regression testing happens before major releases.
What it feels like: Quality is a phase, not a practice. The QA engineer is a gatekeeper, not a collaborator.
Level 3 — Defined
Characteristics: Automation exists for regression. CI runs tests on every commit. Coverage is measured. Processes are documented and followed consistently.
What it feels like: The pipeline is reliable. Developers trust the test suite. QA is involved earlier in the process.
Level 4 — Managed
Characteristics: Quality is data-driven. Defect escape rates, coverage trends, flakiness rates are tracked and acted on. QA is embedded in product planning. Shift-left is practiced, not just preached.
What it feels like: Quality is a shared responsibility. The team ships with confidence because the data supports it.
Level 5 — Optimising
Characteristics: AI-augmented quality processes. Shift-right monitoring in production. Continuous improvement of the quality system itself. QA strategy influences product architecture.
What it feels like: Quality is engineered into the organisation. The team spends almost no time on reactive quality work because the preventive systems are mature.
How to Use This Model
First, be honest about where you are. Most teams sit between Level 2 and Level 3.
Then, focus on the one or two practices that would move you to the next level — not the full set of everything Level 5 teams do. Maturity compounds; trying to skip levels creates fragility.
A Typical Roadmap
Level 2 → 3: Invest in a CI pipeline with required gates. Hire or develop automation skills. Define coverage thresholds.
Level 3 → 4: Add quality metrics to your team dashboard. Run Three Amigos sessions. Track and reduce flakiness systematically.
Level 4 → 5: Introduce AI-assisted test generation. Build synthetic monitoring for production. Make quality strategy part of architecture reviews.
Conclusion
Knowing where you are is more useful than aspirational visions of where you want to be. Assess honestly, pick the next rung, and execute. That's how quality maturity is built — one deliberate practice at a time.