There is a particular frustration that most practitioners, leaders, and educators will recognise. The problem gets solved. The intervention works. And then, three months later, the problem is back, sometimes in exactly the same form, sometimes slightly disguised as something new.
If that pattern is familiar, you are not dealing with a discipline problem, a motivation problem, or a resources problem. You are dealing with a feedback loop that nobody has examined.
Feedback loops are the mechanism through which systems maintain their own behaviour. They are what makes a problem self-sustaining, and what makes a solution, if it is not designed at the loop level, ultimately temporary.
What a Feedback Loop Actually Is
A feedback loop is a circular process in which an output of a system feeds back into the system as an input, influencing future behaviour. The simplest version: a thermostat. The room gets cold, the heating switches on, the room warms, the heating switches off. The output regulates the input. The system maintains its desired state.
Most human systems, schools, teams, relationships, habits, work on the same principle. The difference is that the loops are harder to see, often operate with significant time delays, and frequently produce outcomes nobody intended or wanted.
There are two fundamental types. A reinforcing loop amplifies change in one direction. Things getting better make them better still. Things getting worse accelerate the deterioration. These loops produce exponential patterns, virtuous cycles when the direction is desirable, vicious cycles when it is not. A balancing loop resists change and seeks equilibrium. It pushes back against any departure from a set point.
The Vicious Cycles Nobody Names
In Designing Behaviour in the Classroom, I argue that most persistent behaviour challenges in educational settings are sustained by reinforcing loops that adults in the system cannot see because they are too close to the individual incident rather than the pattern.
Here is a common one. A student consistently disrupts. The classroom relationship deteriorates. The teacher responds with increasing firmness. The student, who often disrupts due to an experience of disconnection or threat, experiences the increased firmness as further disconnection. The disruption increases. The relationship deteriorates further. The loop tightens.
No one in that loop is wrong, exactly. Both the teacher and the student are responding rationally to the conditions they are experiencing. The loop is the problem. And the loop is structural, not personal.
“Solving a problem inside a loop without changing the loop is just pressing pause. The system will reload it.”
Why Solutions Fail
Most interventions fail for one of two reasons: they treat symptoms rather than loop structure, or they introduce new feedback that creates its own unintended consequences.
The second is what systems thinkers call the Cobra Effect, a colonial-era policy in India that paid a bounty for dead cobras to reduce the population. Enterprising people began farming cobras. When the policy ended, the farmed cobras were released, making the problem considerably worse. The intervention fed back into the system in ways the designers had not anticipated.
Education is full of equivalent examples. Behaviour policies that rely heavily on exclusion reduce disruption in the short term and reliably produce more complex, entrenched need in the longer term. Data from the Centre for Social Justice shows that children on SEN support have a suspension rate of 11.09 per 100 pupils, nearly five times the rate of non-SEN children. The intervention that removes disruption has, at scale, a loop that produces disproportionate harm to the most vulnerable.
The Pattern Before the Loop
The diagnostic framework I use, the Pattern Before the Incident, developed in Designing Behaviour in the Classroom, is essentially a tool for mapping the loops operating in a given situation. What conditions precede the incident? What does the incident produce? Who responds, and how? What does the response change? And critically: what does it leave unchanged?
If the response reliably removes the incident without changing the underlying conditions that produced it, the loop is intact. The incident will return. This is why relationship-based approaches, which address the actual disconnection driving the behaviour, tend to produce more durable outcomes than consequence-based approaches, which address the behaviour without touching the loop that generates it.
Designing at the Loop Level
Changing a loop requires identifying the feedback mechanism and intervening at the structural level rather than the symptomatic one. Donella Meadows, in Thinking in Systems, identifies this as operating at a leverage point, a place in the system where a small intervention produces large, lasting change.
In practice this means asking: what is this system designed, intentionally or not, to produce? Then: what would need to be different in the structure for the output to change? The leverage is always in the loop, not the symptom. Once you can see the loop, the intervention becomes obvious.
Bart Reevers