THE IDEA
The power and the trap of taking things apart
Reductionism is the approach of understanding something by breaking it into smaller pieces. Want to understand a car? Take it apart. Study the engine, the transmission, the brakes. Understand each component and you understand the whole. This approach has been spectacularly successful. It built modern science, modern medicine, modern engineering. It works.
Until it doesn’t.
Reductionism works when the behaviour of the whole is the sum of the behaviour of the parts. A car engine works this way. So does a bridge, a circuit board, and a balance sheet. But a family doesn’t. A neighbourhood doesn’t. An ecosystem doesn’t. A company doesn’t. In these systems, the behaviour of the whole emerges from the interactions between parts, and those interactions disappear when you separate the parts to study them. You can understand every organ in the human body and still not understand health. You can understand every employee in a company and still not understand the culture.
The trap of reductionism isn’t that it’s wrong. It’s that it’s so successful in its domain that people apply it everywhere, including where it fails. The engineer who can take apart a machine and fix it tries to take apart an organisation and fix it. The analyst who can decompose a problem into components tries to decompose a social issue into components. The precision that works for machines creates an illusion of understanding when applied to living systems - an illusion that leads to confident interventions in the wrong places.
IN PRACTICE
When the parts don’t add up to the whole
A healthcare system tries to improve patient outcomes by optimising each department separately. Emergency care gets faster. Surgery gets more precise. Pharmacy reduces errors. But patient outcomes don’t improve as expected because the handoffs between departments - where most errors and delays occur - aren’t any department’s responsibility. Reductionism optimised the parts. The problems live in the connections between them.
A school improves each subject independently: better maths teaching, better science resources, better English curriculum. Each department reports progress. But the students’ overall experience doesn’t improve because nobody is looking at the total homework load, the conflicting assessment schedules, or the fact that the best teachers are concentrated in one department. The parts got better. The whole didn’t, because the whole isn’t the sum of the parts.
A farmer analyses soil composition, water levels, sunlight exposure, and pest populations - each in isolation. The recommendations are sound: add this nutrient, irrigate at this rate, apply this pesticide. But the pesticide kills beneficial insects that were pollinating the crops. The irrigation changes the soil pH, which affects nutrient uptake. The nutrients feed the wrong plants. Each analysis was correct in isolation. The system’s response to the combined interventions was something no isolated analysis could predict.
WORKING WITH THIS
Knowing when to zoom in and when to zoom out
Reductionism isn’t wrong - it’s incomplete. The skill is knowing when to use it and when to step back.
Use reductionism when the system is truly decomposable - when the parts can be understood and fixed independently without affecting each other. Mechanical systems, accounting systems, standardised processes. These are legitimate domains for analytical thinking.
Step back when you see signs that the interactions matter more than the parts: when optimising each component doesn’t improve the whole. When fixing one thing breaks another. When the problem sits in the gaps between responsibilities rather than within any single one. When people say “everyone’s doing their job but the system isn’t working.” These are signals that reductionism has reached its limit and you need to zoom out to the level of relationships, flows, and feedback.
The complement to reductionism is synthesis - putting things together to see what emerges. Both skills are needed. Analysis without synthesis gives you a pile of understood pieces and no idea how they fit together. Synthesis without analysis gives you a vague sense of the whole with no understanding of the parts. The best systems thinkers move fluidly between the two.
THE INSIGHT
The line to remember
Taking a system apart tells you what the pieces are. It tells you nothing about what they do together - and together is where the behaviour lives.
RECOGNITION
When this is in play
You’re seeing reductionism’s limits when each part of a system is performing well but the system as a whole isn’t. When a reorganisation improves every department’s metrics but makes cross-departmental collaboration worse. When a problem persists despite each contributing factor being addressed individually. When the phrase “that’s not my department” is the most common explanation for why things don’t work. When the org chart shows clean boxes but the work happens in the messy spaces between them.