When the routines belong to the organisation, not the individual
Inertia is what I call an unintentional FRICtion factor®. It’s about how hard we find it to break old habits and build new ones, even when we want to. This is true at the individual level, but anyone who has tried to change the way things are done in an organisation knows the organisation has habits of its own, and those habits can be even harder to shift. It connects with what Systems Thinking tells us about feedback loops being very good at dragging a system back to where it started. And of course there’s the pull of social norms across teams and organisations - we’re wired to go along with the majority.
Defensive routines and organisational learning
The idea of ‘organisational defensiveness’ comes from Chris Argyris who puts forward that organisations build up ‘face saving’ habits or “defensive routines” which get hardened into their workplace culture. These habits – like self-censorship – are intended to protect people from embarrassment or threat. But these same habits keep them making the same mistakes instead of learning from them.1 Never quite getting round to discussing why the last change failed, for instance, because that would raise awkward questions. Or the elaborate lengths people go to in order to avoid saying something everyone knows perfectly well but nobody wants to say out loud.
It’s this prevention of learning that causes a problem for change. Defensive routines make it hard to learn from changes that went before. There’s a link here with the concepts of Growth Mindset for individuals and psychological safety for teams – treating mistakes as useful data and a chance to improve, rather than as failures to be ashamed of. If your organisation has a history of restructures that didn’t deliver, plus a habit of never discussing why, the next one will almost certainly repeat the same mistakes.
It’s tempting to wade in as the brave truth-teller who breaks the silence. That rarely works; these routines are stable for a reason, and the person who confronts them often gets removed while the routine carries on quite happily. A safer bet is to build structured forums, such as pre-mortems and post-mortems (Sprint Retrospectives should do this job in Agile programmes, though they often just describe what happened rather than digging into why). The aim is to take the political risk out and frame the whole thing around learning rather than working out who to blame. An outside perspective helps here, whether that’s a consultant, NED, business advisor or mentor. They don’t carry the political and personal baggage an insider does, and they can move up and down the hierarchy in a way that nobody with a formal place in it can.
Collective immunity to change
Another useful tool with which to explore an organisation’s inertia is the Immunity to Change framework.2 It works with the concept of competing commitments. We see it at a personal level: someone might hold a stated commitment (‘I want to delegate more’) while a hidden commitment subconsciously works against it (‘and I’m also dead set on being indispensable’). Organisations do the same thing: ‘we want to be more agile’, running alongside ‘and we’re also committed to no department losing any budget’. The collective immune system is all the routines, rules and reward structures that protect those hidden commitments by subtly defeating the stated ones.
Surfacing a competing commitment is uncomfortable, because it means surfacing the gap between what we’d like to be true and what actually is. You might approach it with the question ‘if this change worked completely, what would we have to give up?’ Sometimes the answer is fine. Sometimes it isn’t, or it turns out to be far more painful than anyone had planned for. We rarely control whether a change goes ahead, but we can at least size up the impact more accurately and gently bring those contradictions into the open. Sometimes, much as in coaching or counselling, just holding up a mirror to those hidden commitments is enough to get the organisation moving.
| Practical example Great Place to Work?I once worked with an organisation that had been awarded the Great Place to Work badge for several years in a row. It mattered enormously to the leadership team, who saw it as a way of attracting and keeping the best people, and as proof of their world-class culture. The company spent heavily on staff events and beautiful offices, and no team meeting went by without a mention of how much employee wellbeing mattered. The badge started out as a genuine reflection of all that, a well-earned outside stamp on a real set of internal principles. Over time, though, it had become the end in itself. Managers were expected to hit 100% completion in their teams and, since submissions weren’t anonymous, any negative feedback got treated as a threat rather than as information the company could use to course-correct. |
Checklist
- Defensive routines are powerful sources of organisational inertia.
- Build structured forums like pre-mortems and post-mortems, take the political risk out of them, and frame them around learning
- Ask outright: ‘if this change worked completely, what would we have to give up?’ There’s almost always something, and the answers can surface the collective immune system.



