Quality Fragility · Primary
Customers find defects before the team does.
How this principle feeds it
problems are found after they reach customers, which is the core of the condition.
Principles Library / Observe Before Expanding
Greater Observability Enables Safer Expansion of Autonomy
Make AI systems observable and understandable before granting them autonomous action.
Humans must be able to see, interpret and learn from AI behavior before autonomy is expanded.
Problems show up in the signals before customers or operations feel them.
Each expansion of agent autonomy rests on behavior people can see and explain.
Confidence in agents comes from knowing how they decide, so it doesn't swing with every incident.
Customers find defects before the team does.
problems are found after they reach customers, which is the core of the condition.
Accountability is assigned. Control is not.
people remain accountable for agents whose decisions they can no longer explain or control.
We know what happened. Nobody can explain why.
with decision paths uninspectable, some outcomes cannot be traced to the choices that caused them.
Work is done. Approvals are not.
re-checking agent work by hand adds a review layer that delays work without reducing the risk of misread behavior.
The review process still runs. It stopped meaning anything.
oversight sized for the first deployment stays in place as agent power outgrows it.
AI signs are on by default. Use the AI switch to exclude them. This principle applies once agents produce or act on work in your delivery.
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.
Accountability Fragmentation: Accountability is assigned. Control is not.
Attribution Failure: We know what happened. Nobody can explain why.
Governance Drag: Work is done. Approvals are not.
Oversight Erosion: The review process still runs. It stopped meaning anything.
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 5 practices. Answer the Diagnose questions and the most relevant come first.
Make agent decisions, state changes and outcomes observable in near real time.
Start by asking your team: Where do we see outcomes without understanding what caused them?
People can see agent reasoning and decision paths, and problems show up before customers feel them.
Define which agent behaviors must be visible before you expand autonomy.
Start by asking your team: What agent behaviors can we observe and explain today?
New autonomy waits until existing agent behavior can be explained, and approvals look at decision paths as well as outputs.
Review agent behavior continuously, not only after something fails.
Start by asking your team: Which failure modes do we understand, and which do we just tolerate?
Someone reads the monitoring signals and acts on them, and failures are caught before they reach customers.
Expand an agent's autonomy only as far as people have shown they understand its behavior.
Start by asking your team: Which autonomous actions would be unsafe if we misread the agent's behavior?
Trust holds steady through incidents, and autonomy grows only as fast as people can explain what agents do.
Make sure people can step in, pause or constrain agents based on what the signals show.
Start by asking your team: Which signals arrive early enough for us to step in?
Agent state and signals are visible, and people can pause or roll back a running agent before failures reach customers or operations.