The Operation Nobody Can Describe

Ask the owner of a six-practitioner clinic how their practice runs and you will get a good answer. Ask them to write it down and you will get a different, shorter, less accurate one. Ask them what happened to the eleven people who enquired last month and did not book, and the answer will not exist anywhere they can reach, it will exist in the memory of whoever was on the desk, and only for as long as that person stays.

This is not a failure of diligence. It is the ordinary condition of a well-run organisation. One system holds the appointments. Another holds the money. A third holds what was actually said. Each of them is doing its job correctly and none of them is wrong. What none of them holds is the join, and the join is where the operation lives.

The same shape appears in places that have nothing else in common. A small law firm can tell you what is billed and what is filed but not which matters have gone quiet. A children's nursery can produce every ratio return and still not know which member of staff is three weeks from a lapsed check. A veterinary group runs four sites under one brand and cannot say whether a client seen at one last spring has been seen at another since. In each case the information exists, the people are competent, and the question is still unanswerable.

The habit is invisible precisely when it is working

What produces this is not bad software selection. It is that every organisation solves the join with a person, and then never writes down how, because that person is doing it well enough that nobody notices it is being done at all.

It becomes visible on the Monday after they leave, when the enquiries stop being followed and nobody can say what changed. Which raises the question that matters more than any question about tooling: if the operation is held in somebody's memory, what exactly is being managed?

Remembering is not the same as being able to show

An organisation can remember a great deal and still be unable to demonstrate any of it. Memory is a private faculty. Accountability is a public one, it means somebody who was not present can establish what happened, on what basis, and who allowed it. The gap between those two is not a gap in effort. It is a gap in kind, and no amount of conscientiousness converts one into the other.

An operation that can only be described from memory can be remembered, but it cannot be governed.

This is why the instinct to fix it with another tool consistently fails. Something that automates one more task inside one more system does not move the join anywhere. It leaves the join exactly where it was, in the head of the person who now has one more thing to reconcile. A task automated without the surrounding context is not an improvement. It is a liability that arrives faster.

What it costs to leave alone

Three costs, and only the first is the one organisations notice.

The revenue. Work leaks out of the gaps between systems continuously and silently, the enquiry nobody returned, the client who quietly stopped coming, the balance nobody chased. None of it appears in a report, because no individual system knows it happened. An organisation in this condition is not underperforming against its plan. It is underperforming against a figure it has never seen.

The dependence. An operation that lives in a person's head cannot be handed over, cannot be improved deliberately, and cannot survive a resignation intact. Every organisation in this state is one departure away from a step change in performance that it did not choose and cannot reverse quickly.

The exposure. When somebody with statutory authority asks what happened, the honest answer is a reconstruction. It will usually be accurate. It will also be visibly assembled after the fact, by somebody senior who was taken off their actual job to do it, and being visibly assembled is itself the finding.

What has to change

Not the systems. They are mostly fine, they are paid for, and replacing them is eighteen months of risk in exchange for the same problem in newer software.

What has to change is that something other than a person has to occupy the position above them, able to see the whole operation at once, allowed to act on what it sees within limits the organisation sets, and leaving behind an account of what it did. That is a different category of thing from an application, and no amount of buying more applications produces it.