Local Optimization Bias · Primary
Every team hits its targets. The product still misses.
How this principle feeds it
each fix is judged on its own step, which is the condition's core pattern.
Principles Library / Optimize the Whole
Optimizing the System as a Whole Improves and Sustains System Outcomes
Optimize decisions, improvements and resources based on their effect on the overall system rather than the performance of individual teams, functions, processes or components.
Improvements in one part of a system don't necessarily improve the whole. They can create delays, excess work, dependencies, rework or other unintended consequences elsewhere. Sustainable performance comes from understanding how the parts interact and judging local improvements against broader outcomes such as value, quality, reliability, responsiveness and flow.
Local improvements show up as better results for the whole system.
Leaders judge progress by system outcomes instead of component metrics.
A fix in one place stops pushing delays and rework onto another team.
Every team hits its targets. The product still misses.
each fix is judged on its own step, which is the condition's core pattern.
Everything is in progress. Nothing is finishing.
work piles up in front of each new bottleneck, so more is in progress and less finishes.
The team owns the commitment. Nobody owns the gap.
work that can only move with constant cross-team coordination is how the condition is defined.
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.
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.
Define and measure outcomes that reflect the performance of the overall system.
Start by asking your team: Which metrics tell us how individual components are performing, and which tell us whether the system is improving?
Team targets and overall outcomes move up and down together.
Evaluate each local improvement by what it does for broader system outcomes before you invest further in it.
Start by asking your team: Which step limits the whole system right now, and does this improvement touch it?
Local productivity gains show up in system performance.
Align team, functional and leadership incentives with system-level objectives.
Start by asking your team: Where are incentives encouraging teams to protect local performance at the expense of shared outcomes?
Decisions get made on shared outcomes more than functional KPIs.
Make dependencies, constraints, queues and downstream effects visible to the people making improvement decisions.
Start by asking your team: What local improvements have created unintended consequences elsewhere?
A fix in one area no longer piles delays or rework onto another.
Regularly examine whether improvements are removing problems or simply shifting them elsewhere.
Start by asking your team: When a constraint is removed, where does the next limiting condition emerge?
When a constraint is fixed, the team already knows where the next one will appear.
Have agents and automation optimize within system-level goals, constraints and feedback instead of isolated performance targets.
Start by asking your team: As AI increases the speed or volume of work in one area, what happens to the rest of the system?
Agents in a workflow pull toward the same outcome, and someone can see how their decisions interact.