Quality Fragility · Primary
Customers find defects before the team does.
How this principle feeds it
recurring solved failures are defects found late, after they are expensive to fix.
Principles Library / Original Intent
Understand the Original Intent Before Removing or Replacing Existing Capabilities
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.
Governance Drag: Work is done. Approvals are not.
Attribution Failure: We know what happened. Nobody can explain why.
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.
Before removing or replacing existing capabilities, understand why they were introduced and what risks they were designed to manage.
Many systems encode historical learning that is no longer obvious but still relevant.
Safeguards nobody remembered keep doing their job after the change.
You can modernize a system without trading away the protections that matter.
When an agent rewrites logic, you still know what went and why.
Customers find defects before the team does.
recurring solved failures are defects found late, after they are expensive to fix.
Work is done. Approvals are not.
fear of regressions adds change-control layers that slow work more than they cut risk.
We know what happened. Nobody can explain why.
outcomes are recorded but the decision that caused them is not.
The agents are building. Nobody is sure it still matches the plan.
each unacknowledged substitution becomes the new baseline while outputs look locally correct.
Showing all 5 practices. Answer the Diagnose questions and the most relevant come first.
Before anything is removed, find out why the capability was introduced and what risk it manages. Write that down.
Start by asking your team: What problem was this capability originally solving?
Capabilities are removed for known reasons, and the history stays on record when experienced people leave.
Review past incidents, outages and failures tied to the capability before deciding to remove or replace it.
Start by asking your team: What failure or risk did it protect against?
Teams know which failures a capability prevents before they touch it, so old failures don't catch them out.
Remove or replace capabilities a piece at a time, with safeguards in place at each step.
Start by asking your team: What evidence tells us it is now safe to remove or replace?
Simplifications land without surprise regressions, and any regression traces back to one small change.
When you modernize an implementation, carry its critical protections into the new version.
Start by asking your team: What assumptions have changed since it was introduced?
New implementations keep the protections that matter, and nobody trades them away for elegance or speed.
Before an agent removes or rewrites a capability, require someone to capture its original intent explicitly.
Start by asking your team: As automation speeds up change, how are historical safeguards preserved?
No agent removes or rewrites a capability until its intent is on record, and that record keeps pace with the change.