What it is
A flock of starlings creates a murmuration - vast, fluid, beautiful. No starling is directing it. Each bird follows a few simple rules about how close to fly to its neighbours. The pattern emerges from interactions, not from a plan.
Emergence is what happens when parts of a system interact and the result is something that none of the parts could produce on their own. The key word is interactions. A pile of bricks isn’t emergent. A building is - it has properties (shelter, space, acoustics) that no individual brick possesses.
This is one of the most important ideas in systems thinking because it means you can’t understand a system by studying its parts in isolation. The behaviour you care about - the culture, the gridlock, the innovation, the dysfunction - lives in the connections between things, not in the things themselves.
What this looks like in organisations
Nobody decides to create a company culture. It emerges from thousands of daily interactions: who gets promoted, what gets celebrated, what’s tolerated, how meetings are run, how bad news travels. You can write values on the wall, but the real culture emerges from what people do, not what they say.
A team of talented individuals can produce terrible work if the interactions between them are wrong. Another team of ordinary individuals can produce extraordinary results if the relationships, rhythms, and trust are right. The performance isn’t in the people - it’s in what happens between them.
Traffic jams appear without any driver deciding to create one. Each person makes reasonable local decisions, and the collective result is gridlock. The jam is emergent. You can’t fix it by telling individual drivers to be better - you have to change the conditions that produce the pattern.
How to use this
Stop trying to design outcomes directly and start designing the conditions from which good outcomes can emerge. This means paying attention to three things: the rules of interaction (incentives, norms, processes), the connections between parts (who talks to whom, how information flows), and the diversity of the parts (homogeneous systems produce less interesting emergence).
When you see behaviour you don’t like in a system, resist the urge to blame individuals. Ask instead: what are the interactions that are producing this? The answer will almost always be structural, not personal.
When you see behaviour you do like, don’t take it apart to figure out which piece is responsible. That’s like pulling a starling out of a murmuration to study what makes it beautiful. The beauty is in the flock.
The thought to hold onto
You can’t install emergence. You can only create the conditions for it and then pay close attention to what shows up.
When you’re seeing this
When a culture feels real but nobody designed it. When a team produces something better (or worse) than the sum of its members. When a problem persists despite every individual doing their job well. When changing the people doesn’t change the pattern.