Departments can meet their targets while customers wait longer, inventory rises, quality falls, or total cost increases. The contradiction appears when performance is measured locally but work and consequences flow across boundaries.
This article uses a systems lens: it examines behavior over time, interacting causes, delayed effects, incentives, and the conditions that make the pattern persist. The goal is not to attach a systems label to the topic, but to build a more useful explanation for action.
What the concept means
Local optimization improves a component against its own objective without accounting for system-wide constraints, interactions, or displaced cost.
The related glossary definition of Local Optimization provides a concise reference.
The system structure behind the problem
Local targets drive protective behavior; protective behavior creates queues and handoff cost; poor end-to-end outcomes generate more pressure for local control.
- Map the full value or service flow.
- Find the system constraint.
- Use shared outcome measures with local diagnostic measures.
A practical way to analyze it
- Define the outcome and draw its pattern over a meaningful time horizon.
- Identify important stocks, flows, decision rules, information sources, and delays.
- Map who receives benefits, who bears costs, and whose knowledge is missing.
- Form competing explanations instead of treating the first map as proof.
- Choose indicators for both intended results and displaced or delayed harm.
- Start with a reversible intervention and update the model from evidence.
Example
Procurement reduces purchase price through large batches, while operations absorb inventory, storage, obsolescence, and slower response.
Common mistakes and safeguards
A system metric should not erase local knowledge or accountability. Use nested measures that connect local work to shared outcomes.
Useful safeguards include explicit assumptions, disaggregated measures, decision review points, and monitoring across the system boundary. See also End-to-End Metrics: Measuring Flow Without Hiding Quality or Equity and this related foundation article.
Questions to ask before acting
- What pattern are we trying to change rather than merely suppress?
- Which feedback process could recreate the problem?
- Where are the longest delays and weakest signals?
- Could local improvement shift cost or risk elsewhere?
- What evidence would cause us to revise the intervention?
Frequently asked questions
Is one system map enough?
No. A map is a testable explanation shaped by its purpose and boundary. Compare it with data and stakeholder experience.
Does systems thinking replace specialist expertise?
No. It helps connect specialist knowledge across relationships, scales, and time.
What makes an intervention systemic?
It changes a structure, rule, information flow, incentive, capacity, or feedback process while monitoring consequences.
Further reading
- Meadows, D. H. (2008). Thinking in Systems. Chelsea Green.
- Sterman, J. D. (2000). Business Dynamics. Irwin/McGraw-Hill.
- UK Government Office for Science: Systems Thinking Toolkit.
Discussion