System behaviours and patterns

Emergence

When the whole does something none of the parts could do alone - behaviour that arises from interactions, not instructions.

Also known as: Emergent behaviour, Emergent properties

THE IDEA

What the parts can’t explain

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 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.

IN PRACTICE

Nobody planned this

Nobody decides to create a culture. It emerges from thousands of daily interactions: who gets rewarded, what gets celebrated, what’s tolerated, how meetings run, how bad news travels. You can write values on a wall, but the real culture emerges from what people actually do when nobody’s watching.

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.

A neighbourhood develops a “feel” over years - safe, creative, edgy, family-friendly. Nobody designed that feel. It emerged from the mix of people, businesses, architecture, and habits that slowly accumulated. Change enough of the ingredients and the feel changes, but you can never quite predict how.

WORKING WITH THIS

Design conditions, not outcomes

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, 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 INSIGHT

You can’t install it

You can’t install emergence. You can only create the conditions for it and then pay close attention to what shows up.

RECOGNITION

When changing the people doesn’t change the pattern

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 new people arrive and quickly start behaving like the people they replaced.

Connected concepts

Feedback loops

Feedback loops are the mechanism through which emergence often arises

Unintended Consequences

Emergent behaviour is often unintended - the system produces what nobody designed

Interconnections

Emergence arises from interconnections - behaviour the parts can't produce alone

Nonlinearity

Emergent behaviour is inherently nonlinear - the whole responds in ways the parts don't predict

Tipping Points

Emergent behaviour often appears suddenly at a tipping point - the system reorganises all at once

Complexity vs Complication

Emergence is the defining feature that separates complex from merely complicated systems

Cynefin Framework

In Cynefin's complex domain, outcomes emerge rather than being planned - emergence is the operating principle

Complex Adaptive Systems

Emergence is the defining property of complex adaptive systems - the whole does things the parts cannot

Self-Organisation

Self-organisation is emergence at the structural level - the system builds its own order from within

Co-evolution

Co-evolution produces emergent outcomes that neither system would have created alone

Irreducibility

Emergent behaviour is often irreducible - you can't predict it from the parts, you have to watch it happen

Reductionism

Emergence is what reductionism misses - behaviour that exists only in the interaction, not in the parts

Culture as System

Culture is an emergent property of interactions, incentives, and structures - it arises from the system, not from a statement

Holding Space

You can't design emergence, but you can hold the space where emergence is most likely to happen

complexity self-organisation culture design