> ## Content Index
> Fetch the complete content index at: https://www.ariet.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# Protecting habits
- URL: https://www.ariet.net/protecting-habits/
- Published: 2026-10-29T18:17:46.000Z
- Updated: 2026-10-29T18:17:46.000Z
- Author: Richard Thackeray
- Tags: People and Organisation

**Who this is for:** If you are seeing a governance process that still exists on paper but no longer stops anything, or a restructure that kept the documents but lost the way things were done, this article may be for you.

**BLUF:** Organisations protect their structures and documents, but not the shared habits that make them work. Those habits span several roles and are passed on by those involved, so they disappear when people or circumstances change. Identify them, describe each by what it achieves, and check that they still happen and that new people are still learning them.

---

I've been watching Kevin McCloud's series on listed buildings. I didn't expect a line in it to spawn a post.

At the Regency Café in Pimlico, McCloud says, "Heritage law is very good at protecting bricks, buildings and cornices, and much less good at protecting habits, routines and the daily patterns of behaviour that make a place like this worth visiting. Take those away, and the idea falls apart". His answer is to protect it by letting the habits continue, day after day; the café, as he puts it, "renews its vows one breakfast at a time".  
  
The things we revere and the things we don't; it sounded like other work I am doing.

Listed building consent controls changes to the historic fabric. In England there is no general duty on an owner to maintain a listed building, and the law acts on neglect only once it shows. It cannot require anyone to keep serving breakfast; without it, the Regency would be a building, but the thing to preserve would be gone. Preserving the place requires habits, but only the people who keep doing them protect them. A ruin is different. Its original habits are gone, though it still depends on the habits of the people who care for it: clearing growth, repointing, inspecting. Some conservators go further and reenact the old use.

Look at your organisation: which parts are the Regency and which parts are a ruin, the stones still standing, perhaps still protected, but with no purpose left, no community using them, and none of the social fabric that once held them together.

Serving breakfast is not quite the habit, though. A chain could take the unit, keep every tile, and serve breakfast daily, and the place McCloud was describing would be gone. The café depends on a routine shared between the owners and the people who eat there. The owners keep it consistent; the regulars know how it works; and newcomers pick it up by watching. The experience is what that shared routine produces, and each sitting is both a performance of it and a lesson in it for whoever is new. In an organisation, capability sits here; in a choreography, several roles stay together, learned by taking part. No one owns it whole, so its loss often goes unnoticed, and documentation cannot replace it.

Most of that shared practice goes unprotected. We protect our artefacts reasonably well; the operating model is documented, the capability map is version-controlled, and the governance terms of reference are approved and filed. Approving them implies the routines that keep them working, and those routines rarely rest with one person. A design review that works depends on architects running it, delivery leads bringing things early, sponsors accepting a challenge, and new staff seeing this is how things are done here. None of that is recorded, and it relies on goodwill.

These routines are cheap to remove, and their removal is usually not approved, but it is an unintended consequence. A restructure redraws the chart and keeps the documents. The meeting stays in the diary, but enough people change at once, or enough newcomers arrive, that the routine disappears, and it stops being passed on. Nothing looks different for a year or so. Then someone makes the same decision twice, or misses a dependency, and the cause is hard to trace because the missing thing was never recorded as a thing.

Writing routines down helps, but only so far. A routine can be named, assigned an owner, and given a stated purpose, so removing it becomes a decision someone needs to make rather than something that happens by default. A capability model can capture this, though most record only what an organisation can do, not how it checks that it still does so. The record is not the protection. McCloud's point holds: the routine is protected by being practised, by new people joining in, and, as with the café's owner, by the people who hold it together being noticed and protected in their turn.

A useful exercise is to take one part of the organisation's structure you consider protected, such as a capability, a flow or a governance event, and list the habits it depends on. Describe each by what it achieves, not just that it happens: not "we hold a design review", but "changes come to the design review before build, and it can stop them". Then check when each last happened and whether anyone new has learned it since.

---

*A note on how I write. The observations, questions, message and arguments are mine; so is the experience behind them. I work with Claude, Google, and Grammarly on research and drafting, and I edit and check until I can stand behind each statement. Any errors are mine too.*