A specialty construction firm has grown to two hundred people.
The founder hires four regional managers for the reason every founder hires them. He cannot be in four states at once, and the company needs people making calls he will never see. The hires are good. Two came from competitors where they ran larger books than this. One he promoted from inside and has watched for six years.
He also reviews every bid above a threshold, which is how the firm survived its first decade and is not a bad instinct even now.
Then a bid goes badly. He lowers the threshold — not dramatically, and for a reason he could defend to anybody. Fourteen months later another bid goes badly and he lowers it again.
Both decisions were reasonable. Neither was announced. There was no memo, because from where he sat there was nothing to announce: he had adjusted a number in his own head about when he wanted to see something.
Eighteen months on, the four regional managers route everything upward. Every bid, most staffing calls, some things that were never in scope. He is working later than he did at forty people and the company has stopped growing at the rate it was growing.
He tells his board he has an ownership problem — that he hired managers who will not own outcomes.
They tell each other they were hired to run regions they have never been allowed to run.
So he commissions a leadership development program, because that is what you do when your leaders will not lead. It will not work, and the money will burn, and the reason is not that the program is bad.
Nothing is missing.
Why won’t my managers make decisions?
Two possible answers, and they require opposite repairs.
The capability was never there. You hired for a level of judgment these people do not have, or you promoted on technical strength into a role that needs something else, or the role grew past them while they stood still. In that case development is the correct response, and so, eventually, is replacement.
The capability is there and it has been suppressed. These people can decide. They have decided before. What they have learned is that deciding produces a worse outcome for them than escalating does — because the decision gets reviewed, or reversed, or absorbed into a conversation they did not need to be having. So they stopped, and the stopping is not weakness. It is an accurate read of the incentives you have been running.
The second one is more common in organizations that are working, because organizations that are working attract people who can decide. And the repair for the second is the opposite of the repair for the first.
If you develop capability that is already present, you have spent money teaching people something they know while leaving the suppressor running. The program will produce a real improvement in a skill nobody was short of, and the behavior will not change, and the conclusion you draw at the end of that will be about your people.
Why do these two look the same from where you sit?
Because both produce the identical observable: the decision arrives on your desk.
This is the second time the framework runs into this shape, and it is not a coincidence. In the Execution and Momentum tension, a working control and an unnecessary control both produce nothing bad happens. Here, absent capability and suppressed capability both produce they brought it to me.
Opposite causes, identical symptom. That is the general condition the diagnostic descent exists to handle, and it is why the phase where a problem is visible is such an unreliable guide to where it started.
From the founder’s chair, four managers escalating bids looks the same whether the escalation is a limitation or an adaptation. He sees the same inbox either way. And the inbox is the only instrument he has, because everything else he might use — asking them, watching a meeting, reading a report — passes through people who have already learned what escalating is for.
How do I tell them apart?
Look at history, at the edges, and at what happens when you are unreachable.
History. Absent capability has no track record. Suppressed capability has one that stopped. Go back three years and find decisions these people made without you — not proposals, decisions. If they exist, capability exists, and something changed. If you cannot find any, you may be looking at the first answer.
The edges. Watch what they do below your threshold, in the territory that is unambiguously theirs. Somebody with absent capability is hesitant everywhere, including where nobody is watching. Somebody with suppressed capability is decisive in their own territory and careful at the boundary, and that shift — confident here, deferential there — is the signature. Capability does not have edges. Permission does.
And the tell most founders miss. Suppression does not stop decisions from being made. It stops them from being reported.
When you are unreachable for a week, the work does not stop. Things get decided, competently, by people who did not have the option of escalating. What you find out afterward is roughly nothing, because the same read that produced the escalation habit also produced a habit of not raising things that turned out fine.
If your organization runs smoothly while you are gone and you learn very little about what happened, you do not have a capability problem. You have a reporting consequence problem, and the capability has been there the whole time, operating quietly, in the gaps where your attention was not.
Capability does not have edges. Permission does.
What establishes authority?
Not the grant. The first override.
Delegation is a statement, and it lands the way every statement lands — as a claim to be checked against evidence. The evidence arrives at the moment somebody uses the authority in a way you would not have. That is the event the organization is waiting for, and it teaches more in ten minutes than the delegation did in a quarter.
There are three things that can happen at that moment, and each installs something different.
You reverse it and explain why. The manager learns the boundary is narrower than stated. If this happens more than twice, the stated boundary is dead and the real one is check first.
You let it stand and it goes badly. This is the expensive one and it is the only one that installs real authority. Everybody watches you absorb a bad outcome from a decision you did not make and did not agree with — and what they learn is that the authority is real, because you paid for it.
You let it stand and it goes fine. This teaches almost nothing, which surprises people. Nobody learns much from a case where nothing was at stake.
That is the asymmetry underneath the construction firm. The founder never announced the threshold changes, so the organization never got a statement to check. What it got was a pattern of overrides, read directly. And a pattern of overrides is a more reliable account of your authority structure than an org chart, because it is made of what happened rather than what was intended.
Why does this become a Vision problem?
Because the decisions did not disappear. They moved.
Every bid now gets decided at the top of the organization, by someone who is not in the market where it will be executed and does not know the crew, the client history, or which supplier has been slipping. He is deciding well, given what he can see. What he can see has narrowed, because the people who could widen it are now formatting things for approval rather than raising things for consideration.
That is the Authority and Vision tension: authority that pulls decisions toward the center also pulls them to an altitude where the detail that would inform them is no longer visible. The founder is not making worse decisions because he got worse. He is making them from higher up.
And Vision is where the symptom will present. The bids get less accurate. Commitments get made that the field knows are unachievable. Somebody eventually says the company has a strategy problem, and there will be evidence for that, and it will be the wrong finding — because the altitude problem is downstream of the authority problem, and the authority problem is downstream of two unannounced threshold changes made for defensible reasons.
What does the repair require?
Restoring the threshold is the easy part. Surviving the first bad decision under it is the whole job.
Announce the boundary — and announcing matters here, because the original changes were never announced and the organization has been navigating by inference for two years. A stated boundary at least gives them a claim to test.
Then hold it, and expect the test to come fast. Somebody will use the restored authority within a month, and they will use it on something that matters, because that is what testing a boundary means. If you override that first one, you have not returned to where you were. You are further back, because now there is a stated boundary and a demonstrated exception, and the organization has learned that the announcement was theatre.
Which is why the repair is structural rather than dispositional. What holds is not your resolve in the moment — a governor that makes the override expensive, a defined class of decisions that do not come to you regardless of your opinion, a review cadence that examines outcomes after the fact rather than approvals before it.
Anything that depends on you being disciplined at the moment a bad decision lands on your desk will fail, and it will fail in the quarter when it matters most. Pressure doesn’t create readiness. It reveals it — and what it reveals here is whether you built the structure while things were calm.
Where this leads you
To a question you can answer this week, before you spend anything.
Not are my managers capable. That question has an answer that will feel true whichever way you lean, and you are the least reliable person to answer it, because your inbox is the instrument and your inbox is the thing that has been shaped.
The question is: when did they stop?
If there is a when, the capability is there and something is sitting on it — and the something is almost certainly a pattern of overrides that were individually defensible and collectively legible. If there is no when, if you go back through three years and find nothing that looks like a decision made without you, then the first answer may be correct and development is the right spend.
Most founders who run that exercise honestly find a date.
The four structural tensions → Where organizations give under load, and how to read yours.
How to trace a failure back to its source → The diagnostic descent, worked end to end.
