In 30 seconds
- Look at how parts interact, not just the parts.
- Most problems come from the system, not individuals.
- Fixing one part can make the whole worse.
Key ideas
- The whole matters more than the parts: optimizing one team can slow the system
- Feedback loops: reinforcing loops amplify, balancing loops stabilize
- Delays: effects appear long after causes
- Structure drives behaviour: fix the system, not the people
Local optimization
A development team that writes code faster than testing can absorb just builds a queue. Look at end-to-end flow with value stream mapping before optimizing any one step. The theory of constraints applies the same idea.
Practical tools
- Causal loop diagrams
- Value stream maps
- "Five whys" in blameless reviews
Systems thinking is the fifth discipline in Peter Senge's learning organization.
Myth vs reality
Myth · Problems are caused by individuals.
Reality · Most are caused by the system people work in.
Myth · Improving every part improves the whole.
Reality · Local improvements can hurt overall flow.
Myth · Systems thinking is too abstract.
Reality · Simple tools like value stream maps make it practical.
FAQ
Who influenced systems thinking in management?
W. Edwards Deming and Peter Senge, among others.
How does it relate to lean?
Lean's "optimize the whole" is systems thinking.
How do we start?
Map one end-to-end flow and look for loops and delays.