No teacher sets out to create a classroom culture in which students learn to perform compliance rather than develop genuine understanding. No organisation designs itself to suppress the information that would allow it to improve. And yet these things happen. Reliably, predictably, across contexts. Not because the people involved are incompetent or malicious, but because complex systems produce outcomes, emergent behaviours, that nobody designed and that often nobody wants. They emerge from the interaction of the system's components, and they could not have been predicted by examining the components individually.
This is one of the hardest things to hold in mind when you are trying to change something: the problem you are seeing is probably not anybody's fault. It is the system's output. And the people inside the system may be as frustrated by it as you are.
What Emergence Actually Means
Emergence refers to properties or behaviours that arise at the system level that cannot be reduced to the properties of the individual elements. In human systems, the equivalent is culture. A school culture in which students compete rather than collaborate does not emerge because any individual student is competitive by nature. It emerges from an assessment system that rewards individual performance, a resourcing model in which the top performers get the most attention, and a peer culture that has developed in response to those structural conditions.
In Designing Behaviour in the Classroom, I am often asking: what is the behavioural culture this room produces, and what conditions are generating it? The answer is almost never about individual students. It is almost always about the emergent properties of the system those students are sitting inside.
“The behaviour you are trying to change is often the logical output of conditions you have not yet examined. Change the conditions. The behaviour follows.”
The Information Gap
One of the most reliable sources of unintended emergent behaviour in organisations and institutions is the gap between the information available to the people making decisions and the information that would be relevant to making them well. In schools: behaviour data recorded at the incident level that does not capture the contextual pattern; student experience data that never reaches the people who set the timetable; teacher observations that are not connected to SEND assessment data.
Each of those information gaps is producing behaviours that the people inside the system experience as inexplicable. The SENCO who cannot understand why the student deteriorates each Tuesday after period three. The teacher who cannot understand why every class has the same difficulty with the same transition. The information is there. The system has not been designed to connect it. The emergent behaviour is the predictable result.
Seeing the Whole
Systems thinking, specifically the capacity to see the whole rather than just the parts, is the antidote to being managed by emergent behaviour. It requires the deliberate practice of stepping back from the immediate problem to ask what system is producing it.
The practical tool I use is the question sequence from the Pattern Before the Incident framework: what is consistently true about the context in which this behaviour occurs? What does the behaviour produce, for the person doing it, for the people around them, for the system itself? What is maintained by the current configuration that would be threatened if the behaviour changed? Those questions often reveal that the emergent behaviour makes sense, is even necessary, given the conditions. An uncomfortable insight. And a useful one. Because it points towards what would actually need to change.
Bart Reevers