Putting it back, but not all of it

Procedures have dimensions

Every procedure has at least four, and most organisations have never examined any of them:

• Frequency. How often. Usually set at the start and never revisited.
• Scope. Which cases it applies to. Usually all of them, because nobody wrote a rule.
• Distribution. Who receives the output. Usually everybody who was on an email list a decade ago.
• Ceremony. How it is done — standing or sitting, written or spoken, timed or open-ended.

None of these was chosen. They were set once, by somebody solving a problem, and the procedure ran at those settings because there was no occasion on which anybody had to justify them.

The removal is the occasion.

What came off, dimension by dimension

Of the twelve reduced returns on this record:

The scope reductions are the ones worth copying. A second reviewer on every routine change is a rule treating all changes alike; when it came back it came back with a threshold, and the threshold is a piece of knowledge the organisation now has written down and did not have before.

The four questions

When something is being put back, before agreeing to put it back:

How often does the thing it guards against actually happen? Frequency is usually set to a guess made years ago. If the event is annual, a quarterly procedure is covering it four times over.

Which cases does it actually matter for? If there is a size, a value or a type above which it matters and below which it does not, that threshold is the most valuable output of the whole exercise.

Who actually uses the output? Ask them, not the list. On this record a circulation to about forty people was used by four.

What part of it is the part that works? Three of the twelve reductions removed ceremony and kept the substance — the stand-up timed at ten minutes does the same job as the one that ran to twenty-five.

When not to ask them

Immediately after an incident.

A procedure that failed and is being restored under pressure is not a good moment for a conversation about thresholds, and on this record the attempt was not made in any of the incident-driven cases. Five of the six full-weight restorations followed an incident.

Two of those five look oversized in retrospect — the contract review went back as a full annual review of every agreement when only two had changing terms, and the shift handover went back for a class of job where nobody had ever read the note.

The realistic handling is to restore at full weight, note on the entry that it was restored under pressure, and revisit the dimensions three months later when the four questions can be asked without sounding like an argument for the thing that just failed.

Nobody did that here. Both oversized restorations are still running at full weight.

The general shape

A removal does not save anything by itself. It creates a moment at which somebody has to say out loud what a procedure is for, and that moment is where the saving is made.

An organisation that removes thirty-eight things and restores twenty-four at half weight has resized twenty-four procedures and abolished fourteen. By the usual accounting — how many had to go back? — that looks worse than removing eight and keeping all eight out.

The second organisation has abolished eight procedures and examined nothing.

The case against asking at all

There is an argument on the other side and this record half supports it.

Eleven of the twelve reductions happened without anybody asking anything. Somebody restarted a thing at the size they needed, and the result was a median of forty per cent — better than most deliberate reductions achieve, arrived at by nobody, in no meeting.

The argument runs: four questions take a conversation, a conversation takes a decision, a decision takes an approval, and the thing that emerges will be larger than what one person would have quietly rebuilt. Leave it alone and you get the reduction free.

What that misses is durability. The eleven unasked reductions are held in one person's practice. They are undocumented, unowned, and will drift or disappear with the person. The single reduction that went through a conversation is a written rule.

So the honest position is that quiet reductions are better sized and worse secured, and the four questions are worth asking not to improve the size but to turn a habit into something the organisation knows it has.