The quiet ones
The removals that belonged to nobody
Six procedures on this record had no owner. Every one passed without comment, and they connect the quiet removals to the expensive ones.
The quarterly reconciliation of the project ledger
week 3 · surfaced after 31 weeks
Shadowing new starters through their first week
week 6 · surfaced after 47 weeks
Reading supplier contracts before renewal
week 2 · surfaced after 22 weeks
Logging why a job was turned down
week 9 · surfaced after 64 weeks
Surfaced 4
Four removals were written down with the week each of them stopped. Every one of them produced an event inside the 78 weeks watched. Of these, four surfaced as a problem. The four removals nobody said a word about, all of which later surfaced as problems.
One property keeps appearing underneath the quiet removals, and it is worth isolating because it is more checkable than silence itself.
Six of the thirty-eight procedures had no owner. Not in the sense of nobody performing them — somebody performed all six — but in the sense that no particular person was answerable for whether they happened.
All six passed without a word being said.
The six
| procedure | who did it | who was answerable |
|---|---|---|
| the standing slot for ownerless work | whoever was free | nobody |
| logging why a job was refused | whoever refused it | nobody |
| the induction folder | whoever noticed it was stale | nobody |
| the spare key log | whoever took a key | nobody |
| re-sending the rota as a reminder | whoever thought of it | nobody |
| the suggestion box | nobody, latterly | nobody |
Two of the six are among the five expensive removals. Two crept back without a decision. Two were never missed.
Why ownerlessness produces silence
Three reasons stack, and none of them is about anybody's attitude.
There is no one for whom defending it is their job. An objection costs something to make. The person who makes one is spending attention and a small amount of social credit, and they do that for things that are theirs. A procedure that belongs to everybody belongs to nobody for this purpose.
Nobody can describe it fully. Each person who used the refusal log knew their own use of it. Nobody knew the whole of what it was doing, because the whole of it was distributed across people who never compared notes. The sentence that would have saved it did not exist in any one head.
Its value is only visible in aggregate. This is the sharpest of the three. Each individual act of logging a refusal is almost worthless; the value is entirely in the accumulation, and accumulation is invisible to each contributor.
The connection to the lag
The same property that makes a procedure hard to defend makes its absence hard to notice, and for the same reason.
If the value is in aggregate, the loss is in aggregate. Nobody experiences a shortfall at any particular moment. The refusal log failed by the same analysis being done four times by four people, none of whom experienced anything other than a piece of work they could manage. It took fourteen months for the pattern itself to become visible to somebody standing far enough back.
A procedure whose value nobody can see individually is a procedure whose loss nobody will feel individually. The two are the same property described at two different times.
Why this is more useful than counting silences
Because ownership is checkable on the day, and silence is not.
"Was this discussed?" is a fact about a meeting and it tells you what happened in the room. "Who is answerable for this?" is a fact about the organisation, it can be asked of any procedure at any time, and a blank answer predicts the silence rather than merely recording it.
On this record, asking that question of all thirty-eight before the transition would have produced a list of six. Two of the six became expensive. The list of seventeen silences contains the same two plus fifteen others, so the ownership question is a sharper filter — six names rather than seventeen, with the same hit rate on problems.
What to do with an ownerless procedure
Not give it an owner. That is the obvious move and it is mostly wrong: most of these were ownerless because they were genuinely collective, and appointing somebody to be answerable for the refusal log would have produced a person maintaining a log nobody reads.
What works is narrower. Before removing an ownerless procedure, ask one person who performs it what they personally use it for, and ask a second person the same question. If the two answers differ, the value is in aggregate and the removal belongs in the slow category regardless of how obvious it looks.
On this record the two answers would have differed for the refusal log and for the induction folder. They would have matched for the spare key log and the rota reminder, both of which were fine to remove.
Four questions, two minutes, and it separates the six into the two that mattered and the four that did not — which is more than anything else on this record manages in advance.