Quality Fragility · Primary
Customers find defects before the team does.
How this principle feeds it
problems found after several stages are found after they are cheap to fix.
Principles Library / Upstream Quality
Upstream Quality Reduces Downstream Failure Propagation
Design quality into the earliest stages of delivery so defects, weak assumptions, and invalid outputs are detected or prevented before they propagate through the system.
The later a quality issue is discovered, the more downstream work may already depend on it. Upstream quality controls reduce rework, instability, and the cost of correction.
Problems show up close to where they're made, before other work depends on them.
Teams spend less effort undoing work that was built on early mistakes.
Automation and agent autonomy grow only as fast as the quality signals people trust.
Customers find defects before the team does.
problems found after several stages are found after they are cheap to fix.
Problems are found at release, not before it.
the more stages an error crosses, the later it surfaces, typically at release.
Work is done. Approvals are not.
approval layers added for weak signals delay finished work without cutting risk in proportion.
The agents are building. Nobody is sure it still matches the plan.
each agent handles the flawed input correctly, so output looks locally right while the whole drifts from the plan.
AI signs are on by default. Use the AI switch to exclude them.
For each consequence: Not seen / Sometimes / Persistently / Not sure.
Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.
Quality Fragility: Customers find defects before the team does.
Batch Amplification: Problems are found at release, not before it.
Governance Drag: Work is done. Approvals are not.
Implementation Drift: The agents are building. Nobody is sure it still matches the plan.
What else have you observed? Optional. Shared only if you choose to start coaching.
Start a Diagnosis session: review and edit a draft containing your note, conditions you recognized in Step 3 (including whether they match partly), warning signs and consequence ratings before sending it. No scores or principle files are sent.
Showing all 6 practices. Answer the Diagnose questions and the most relevant come first.
Validate assumptions and requirements before other work starts to depend on them.
Start by asking your team: What assumptions are we accepting without early validation?
Defects turn up before merge, and quality feedback lands while the decision can still change.
Put executable tests, automated checks and fast feedback close to the point where work is created.
Start by asking your team: Which quality risks could we detect closer to the point of creation?
Defects turn up before merge, and a change can ship without a long manual regression pass.
Automate verification for the failure modes you already know and keep seeing.
Start by asking your team: Where do we first learn that something is wrong?
Known failures stop coming back, and fewer defects are found after release.
Make quality signals visible and unavoidable for every meaningful change.
Start by asking your team: How far can an error travel before it becomes visible?
Teams can see work is correct before downstream approval, and review layers start to come off.
Use AI evaluation frameworks to catch regressions and probabilistic failure modes early.
Start by asking your team: Where could a single upstream error create several downstream consequences?
Agent evaluations are current, and AI output that passes checks holds up downstream.
Increase automation and agent autonomy only when the team understands and trusts its quality signals.
Start by asking your team: Are our quality signals keeping pace with growing automation and AI-generated work?
Quality gates fit agent work, and people review agent output before errors pass through several stages.