Defensive Routines
The unspoken patterns that protect us from learning something uncomfortable.
The team meeting is supposed to be a review of the last project. The project went badly. Everyone in the room knows it. The discussion goes for forty-five minutes. By the end, nobody has actually said what happened, no decision has been made about doing things differently, and the meeting wraps up with a vague commitment to “communicate better next time.”
Everyone leaves slightly relieved. The meeting was uncomfortable, but the genuinely uncomfortable conversation didn’t happen.
That’s a defensive routine.
What a defensive routine is
A defensive routine is a pattern of behaviour — usually unspoken, often shared by a whole group — that protects everyone involved from a piece of information that would be uncomfortable to face.
Chris Argyris, who spent decades documenting how organisations actually behave, coined the term to describe something he kept seeing: the same groups that said they wanted to learn from mistakes had highly developed systems for making sure no real learning happened.
The systems weren’t hidden. They were ordinary. Long meandering discussions. Vague action items. “Let’s take this offline.” “I think we all know what really happened.” Apologies that lead nowhere. Praise that softens criticism into nothing. Each individual move looks reasonable. The collective effect is that nothing changes.
Why they’re so hard to spot
The hard part about defensive routines isn’t recognising them in someone else. The hard part is recognising them in yourself.
Defensive routines feel, from the inside, like ordinary good manners. Smoothing over a tense moment in a meeting feels like leadership. Avoiding the specific question that would make someone defensive feels like emotional intelligence. Letting a tough conversation drift into the abstract feels like keeping the temperature down.
All of these moves can be the right thing to do in the moment. They become a defensive routine when they happen *every* time the team gets close to a real learning conversation — and when nobody can name that pattern out loud.
A few defensive routines that show up often in small businesses
The collective shrug. Something went wrong. No one person is clearly responsible. The team talks about it abstractly — “we should communicate better” — and moves on. The thing that actually happened is never described in concrete enough terms to learn from.
The procedural fix. Something went wrong because of a judgment call. The team responds by creating a new procedure. The new procedure addresses the symptom, leaves the underlying judgment problem untouched, and adds friction for everyone. Six months later a similar problem happens, and a new procedure gets added on top.
The strategic vagueness. The owner says something like “we need to be more accountable.” Everyone agrees. Nothing changes — because nobody has said what they specifically want to be different, what they specifically want to stop happening, or who specifically would do what.
The protected exception. Everyone in the team can name the colleague whose behaviour is undiscussable. There are reasons not to discuss it — they’re going through something, they’re a long-serving employee, they’re a good performer otherwise. The reasons may be valid. But the cost of the exception is that the team has now learned that some behaviour can’t be talked about, which spreads.
Why defensive routines compound
The most expensive thing about defensive routines is what they teach.
A new person joins the team and watches what happens after a mistake. They learn, very quickly, what can be said and what can’t. They learn whether honest disagreement is welcome or merely tolerated. They learn what happens to colleagues who break the routine.
Within a few months, they’ve adapted. They’ve stopped doing the things that don’t get rewarded and started doing the things that do. The defensive routine has just replicated itself in another person, without anyone consciously teaching or learning it.
This is why defensive routines are so durable. They aren’t sustained by any individual. They’re sustained by everyone, slightly.
What to do about them
You can’t dismantle a defensive routine by deciding not to have one. You dismantle it by naming it, in the moment, in concrete terms.
That sounds simple. It isn’t. Naming a defensive routine breaks it — which means the discomfort it was protecting everyone from is suddenly in the room. People may push back. The first few attempts may go badly. The skill is real.
But the alternative is that the routines stay in place, and your team continues to have polished meetings where nothing important gets said.
A useful test: in the last three months, what’s the most uncomfortable thing that genuinely got discussed in your team? If you can’t name one, that’s not a sign your team is unusually harmonious. It’s a sign the routines are doing their job.
Where this fits
Defensive routines are part of Argyris’s broader work on Model I and Model II behaviour — Model I being the defensive pattern most people default to under pressure, Model II being the pattern that actually allows learning.
They’re closely linked to the gap between theory-in-use and espoused theory: defensive routines are how groups protect their espoused theory from being challenged by what’s actually happening.
Sources
The concept comes from Chris Argyris, particularly Overcoming Organizational Defenses (1990) and Knowledge for Action (1993).