Home › Systems › Principles
Reductionism Works Only for Non-Complex Systems
Systems / Principles
Take it apart to understand it — only when the parts don't interact strongly.
The Idea
Reductionism — decomposing a system into pieces and studying them separately — works for systems where components are loosely coupled. Clocks, engines, simple algorithms. It fails for systems where behaviour emerges from interactions: ecosystems, economies, organisations.
Why It Matters
- Engineers reach for reductionism by default.
- Applied to complex systems, it produces detailed knowledge of parts and blindness to the whole.
- Many management mistakes come from managing components individually in a complex system.
How to Apply
- Ask: do the parts behave roughly the same alone as together? If yes, reductionism works. If no, it doesn't.
- For complex systems, study interactions and patterns, not components.
- Use reductionism inside subsystems; use holism for the whole.
Examples
- Debug a clock by examining gears: works.
- Fix a culture by examining individuals: fails.
- Improve code by improving functions: sometimes. Improve architecture by improving modules: sometimes.
Related