Is Institutionalizing a Loss of Control

Immediacy and control are not the same thing

When institutionalizing comes up, a founder's first move is usually a defence: "I built this company, and now I am supposed to ask a procedure for permission inside it." The sentence sounds like pride, but underneath it sits something concrete — the fear of losing control. Once that fear is named out loud in the coaching room, the same distinction surfaces almost every time, and it decides more than it appears to: what is being lost is not control.

Control is the power to determine an outcome. Immediacy is the ability to reach into the process at any moment, without telling anyone first. What a founder has held for years is mostly the second one, and while the company was small the two never needed separating. A founder who can change a price while walking down a corridor has both touched the process and settled the outcome; the two collapse into a single motion, and that motion repeats for years.

What a founder's day is actually made of

At scale they come apart, and nobody announces the day it happens. A founder answering questions from three departments between morning and evening looks, from outside, like a man in control of his company; the calendar is full, every subject has passed his desk, nothing has moved without him. What he does not decide is which subject the day will be about — that is settled by whoever knocks first. The right to touch everything is intact; the power to determine outcomes has been handed to other people's sequencing.

Immediacy feels exactly like control

The reason immediacy passes for control is emotional: both produce the same sensation, the sensation of being able to change an outcome. When a founder walks into a meeting and reverses a decision, what he experiences is real rather than imagined; the decision has genuinely changed. But for that sensation to keep recurring, the team has to have not decided anything — and in time the team learns to oblige.

A place that can be overridden is a place where nothing is decided

A team that knows the founder may change his mind at any moment starts doing three things, each of them reasonable on its own:

• It seeks approval before deciding, which ties the company's decision speed to one person's calendar.
• It leaves its own decisions half-made, since the matter will be reopened anyway.
• It stops proposing the risky option and proposes the approvable one, and the pool of ideas narrows without anyone noticing.

Put those three together and the founder's influence does not grow; it shrinks. The volume of decisions the company can make gets pinned to one person's capacity for attention, and that capacity does not grow with the company; the founder works longer hours and holds the line for a while, and then he cannot. The loss of control begins there — not when institutionalizing starts, but years earlier, without a single procedure being written.

The measure is a fortnight out of reach

Who actually holds control cannot be measured while the founder is in the room. With him there, everything looks the way he wants it, because whenever something does not, he intervenes, and the intervention destroys the measurement. The measurement is only available in his absence, which is why the question asked in the coaching room is usually this one: when were you last unreachable for two weeks, and what did you look at when you came back.

What to look at when the fortnight ends

The question on return is nearly always "what broke", and it is the wrong question; finding the breakage only proves to a founder that he was needed. The more uncomfortable question is what decisions were made in those two weeks, and how many of them he would have made the same way. If that second number is high, institutionalizing has not taken control away — it has multiplied it, because the founder's judgment is now running at several desks at once rather than only at his.

If the number is low, the problem is still not institutionalizing as such. A low number says the system is carrying the wrong judgment, which is a fault in the content of the rules rather than in their existence, and it is fixed by correcting them rather than removing them. A third picture is worse than either: no decisions were made at all, and the company spent a fortnight waiting.

The one version of the fear that is right

It would be dishonest to call the fear baseless; if it were, it would not recur in the same shape in so many founders. There is exactly one version of it that holds, and it has nothing to do with institutionalizing itself and everything to do with whose hands are doing it.

Whose judgment is writing the rule

When the procedure is written by someone who does not share the founder's judgment, institutionalizing really is a transfer — and it is a silent one, because nobody ever says "we make the decisions now" in a meeting; all that happens is that the handling of exceptions gets written into a document. Institutionalizing does not take control; it makes visible whose judgment control has been running on, and what becomes visible is sometimes not the founder's.

So the founder's real work in this period is neither staying away from the system nor resisting it, but auditing whether the system carries his own judgment: checking whether the written rule produces the same outcome he produced the last ten times he decided by hand. That work is one of the functions his role moves through in sequence, and it is never finished in one pass; every new rule asks for the same audit.

From the room

This subject almost never enters the coaching room as "I am losing control." It arrives in a more acceptable costume: a worry that institutionalizing will slow the company down, make it heavy, cost it whatever made it good. The worry deserves to be taken seriously on its own terms. But when the sentence underneath it is asked for, what usually surfaces is not speed — it is a founder who no longer knows where his own place in the company is.

What we do in the room is name the two halves separately: what leaves is immediacy, and what arrives is judgment that keeps working while he is not there. Without that distinction, a founder experiences every procedure as a loss and quietly makes the system unworkable with his own hands. With it, his relationship to the same procedure changes, because he now knows what has been exchanged for what.

The real test of institutionalizing, for a founder, is not obeying rules but being able to turn his own judgment into one. Requesting a conversation often starts from that question: of the decisions you made in the last month, which one could have been written down as a rule instead.