Build Quality In
Category: Flow & Delivery Dynamics
Principle Intent
Design the system so defects are unlikely to occur and quickly visible when they do. Quality is shaped by how work is created, verified, and learned from across human and AI-assisted delivery.
Warning Signs — When This Principle Is Being Violated
These observable signals indicate the principle is not operating effectively in your delivery system:
- Defects or regressions are primarily discovered late, after merge or release
- Teams depend on downstream testing, reviews, or approvals to ensure correctness
- Known risks are repeatedly found rather than systematically prevented
- AI-generated changes receive lighter scrutiny than human changes
- There is no clear signal showing whether system quality is improving or degrading
These signals indicate that quality is being assessed after the fact rather than reinforced upstream.
Systemic Consequences if Ignored
When this principle is absent or routinely violated, the following patterns tend to emerge over time:
- Rework and instability become recurring features of delivery
- Systems grow fragile, making change slower and riskier
- Confidence in releases declines, increasing coordination and approval overhead
- Regulatory, reputational, or customer impact increases
- In AI-assisted systems, small errors propagate quickly and surface abruptly
Over time, the organization loses its ability to distinguish progress from accumulated risk.
Left unaddressed, these patterns can potentially form following Unintended System Conditions (USC): Quality Fragility (Primary), Batch Amplification (Contributing), Implementation Drift (Contributing)
When quality is treated as an inspection step rather than a built-in property, defects accumulate silently and surface late. That is the structural definition of Quality Fragility. Large batches (Batch Amplification) compound the problem by extending the gap between introduction and discovery.
Coaching Lens — Questions to Surface the Violation
Use these questions to diagnose whether this principle is being violated in your current situation:
- Where do we first learn that something is wrong?
- What assumptions are we making about correctness, and how are they validated?
- Which risks are being tolerated until late because earlier feedback is inconvenient?
- How do we know quality is improving, not just output increasing?
Anti-Patterns — What Not to Do
Common mistakes leaders make when trying to apply or restore this principle:
- Treating QA, reviews, or approvals as substitutes for design quality
- Deferring known issues to maintain delivery speed
- Assuming automation or AI output is acceptable by default
- Equating coverage, checklists, or gates with real confidence
- Believing quality can be verified once and then trusted indefinitely
Recommended Practices
Actions and approaches that help make this principle a real system property:
- Move quality left using executable tests (unit, integration, TDD)
- Automate verification for known and recurring failure modes
- Keep test feedback fast and unavoidable for all changes
- In agentic systems, use evaluation frameworks (evals) for probabilistic AI outputs to detect regressions early
- Increase automation and autonomy only after quality signals are understood
These practices ensure quality is built into the system rather than inspected after failures occur.
Apply This Principle with the PPA Method
When this principle is violated in your delivery system, use the PPA Method to respond deliberately:
- Problem: Diagnose the system-level behavior producing recurring symptoms. Use the warning signs above to confirm the violation.
- Principle: Identify that this principle—Build Quality In—is the root explanation for why the behavior persists. The coaching lens questions above help surface this.
- Action: Choose deliberate actions from the recommended practices above that reinforce this principle within your real constraints.