Local Optimization Bias · Secondary
Every team hits its targets. The product still misses.
How this principle feeds it
a new solution improves one area while its constraints land elsewhere, so end-to-end flow may not improve.
Principles Library / Second-Order Effects
New Solutions Create New System Constraints
Every solution introduced to address a problem creates new constraints elsewhere in the system.
System health depends on anticipating and managing these second-order effects, not just solving the immediate issue.
Bottlenecks get cleared instead of moved somewhere else.
Teams know which constraints a change brings before it goes live.
Something old goes out each time something new comes in.
Every team hits its targets. The product still misses.
a new solution improves one area while its constraints land elsewhere, so end-to-end flow may not improve.
Everything is in progress. Nothing is finishing.
work queues at each new bottleneck, and compounding constraints leave more work in progress and less finishing.
The team owns the commitment. Nobody owns the gap.
each new part adds interfaces owned by different people, so work needs more coordination to flow.
Customers find defects before the team does.
failures from dependencies nobody knew about surface late as incidents, though the root is added coupling.
We know what happened. Nobody can explain why.
the failure is recorded against the team where it appeared, while the design decision that caused it goes untraced.
Accountability is assigned. Control is not.
downstream teams answer for failures created by changes they did not control.
Every quarter starts over. Nothing compounds.
leaders drop each backfiring initiative and start another, so improvement never compounds.
The review process still runs. It stopped meaning anything.
oversight sized for the original deployment cannot keep up with constraints added at machine speed.
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.
Local Optimization Bias: Every team hits its targets. The product still misses.
Workload Saturation: Everything is in progress. Nothing is finishing.
Dependency Density: The team owns the commitment. Nobody owns the gap.
Quality Fragility: Customers find defects before the team does.
Attribution Failure: We know what happened. Nobody can explain why.
Accountability Fragmentation: Accountability is assigned. Control is not.
Strategic Volatility: Every quarter starts over. Nothing compounds.
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.
Before you approve a solution, list the new constraints it's likely to create and where they'll land.
Start by asking your team: What new constraints will this solution introduce?
Bottlenecks clear instead of moving, and new fixes rarely catch teams off guard.
Before you implement, write down which teams or systems will absorb the shifted constraints.
Start by asking your team: Which teams or systems will absorb those constraints?
Bottlenecks stay put or disappear, and failures from recent changes are expected rather than surprising.
When you add a component, name who owns it and who owns the side effects it creates.
Start by asking your team: What new knowledge, ownership, or coordination will be required?
Knowledge and control spread beyond the new components, and recent changes stop surprising teams.
When you add a tool, process or layer, remove or simplify an existing element.
New layers are rare, and complexity holds steady while outcomes improve.
When you introduce agents, decide who monitors them, who steps in and who adapts them as constraints surface.
Start by asking your team: As automation increases, what new human responsibilities emerge?
Agent changes arrive with their constraints named and owned, and downstream surprises from them are rare.