Skip to content
lbd_article

Suppressed or Absent: The Capability Question

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.

A restaurant group has an opening playbook with forty checkpoints in it.

The playbook was not written in a conference room. It was assembled the hard way across the first four locations, and most of its items exist because something went wrong once and somebody wrote down what would have prevented it. Checkpoint nineteen is there because of a health inspection at location two. Checkpoint thirty-one is there because of a supplier who did not deliver at location three and a manager who did not have a fallback.

Location five opens strong. The playbook runs, all forty, and the opening goes better than any of the first four.

At location six the team skips three checkpoints. Not out of laziness — they are ahead of schedule, they have done this before, and three of the items look like belt-and-braces for a market they now understand. Location six opens strong too.

At location nine they skip eleven. By now there is a shared understanding, never written down, about which parts of the playbook are the real playbook. Location nine opens strong.

The group is now opening faster than any competitor in its market. Internally, that reads as the system working. Somebody says so in a board meeting, and they are not wrong about the speed.

Location twelve opens badly.

And here is what happens next, in every organization this happens to — including, if you have lived through one of these, yours: they investigate location twelve. The general manager, the market, the buildout, the hiring, the training calendar. They will find something, because there is always something to find at the site of a failure.

What they will not find is the decision that caused it, because that decision was made at location six by people who were right at the time.

How does an organization get faster and worse at the same time?

Because speed and repeatability are two different capabilities, and improving one can consume the other without anybody noticing the trade.

Leadership by Design calls this the tension between Execution and Momentum. Execution is the phase that runs on discipline — the same work, the same way, at a standard that holds when conditions are unfavourable. Momentum is the phase that runs on accumulated movement: the organization is already going, the going supplies its own confidence, and the confidence lowers the perceived cost of going faster.

Both are real capabilities and an organization needs each of them. An organization with Execution and no Momentum is careful and slow, and it loses to people who move. An organization with Momentum and no Execution is fast and it is building something that will not hold.

The tension is not a problem to solve. It is a permanent structural relationship, and what you get to decide is where the threshold sits between them.

What goes wrong is that the threshold moves on its own, in one direction, without you deciding anything.

Nobody in that company chose to stop running the playbook. Every individual choice was to skip three items on a schedule that was ahead.

Why can’t you tell a working control from an unnecessary one?

Because they produce the identical observable: nothing bad happens.

That is the mechanism underneath the whole pattern, and it explains something that otherwise looks like carelessness: why intelligent, experienced operators erode their own controls while paying close attention.

When you run checkpoint nineteen and the opening goes fine, you have learned nothing about checkpoint nineteen. It might have prevented a problem. There might have been no problem to prevent. From inside the result, those look the same.

When you skip checkpoint nineteen and the opening still goes fine, you have generated something that feels like information: evidence that the checkpoint was unnecessary. And that evidence is real evidence. It is an honest observation, honestly obtained, and it points in the wrong direction.

Controls are insurance. Insurance that does not pay out has not been proven unnecessary — it has been unused, which is what you were paying for. But an organization under schedule pressure does not experience it that way. It experiences a cost that was incurred and a benefit that never showed up.

So every successful skip strengthens the case for the next skip, and the case gets stronger the longer nothing goes wrong. Which means the strongest argument for abandoning your controls arrives right before you need them, assembled entirely from true statements.

Why does success erode discipline when failure tightens it?

Because consequence teaches, and success removes the consequence.

Failure is a fast, unambiguous teacher. Something goes wrong, everybody sees it, and you tighten the process — that is where the forty checkpoints came from in the first place. Every item on that list is a scar.

Success teaches too, and it teaches in the opposite direction. The skip that produced no consequence gets reinforced, because nothing punished it and it saved time, and saving time is visible and immediate. The behavior that gets rewarded is the one that removed the control.

That is not a failure of the people involved. It is reinforcement operating the way it operates everywhere else. Behavior that produces a favourable consequence becomes more likely, and faster with no downside is about as favourable as an operating environment gets.

And it compounds, because each successful skip lowers the bar for the next one. Location six skipped three items that looked defensible. Location nine skipped eleven, and the eleven included items nobody at location six would have touched — but location six had established that the playbook was a guideline, and once that is established the argument is no longer about which items are essential. It is about how far ahead of schedule you are.

That’s the erosion. Not a decision. A drift, with a reward attached to every step of it.

What is the difference between momentum and progress?

Progress is movement toward something. Momentum is movement that continues because it is already underway.

They feel identical from inside the vehicle, and that is not a figure of speech — it is the problem itself. An organization moving fast in a sound direction and an organization moving fast in an unsound one report the same experience: energy, pace, a sense that things are happening, a comparison to competitors that flatters you.

The distinguishing question is not how fast are we going. It is what would have to be true for us to notice we were wrong?

If your Execution is intact you have an answer, because your checkpoints are also detectors. Running the playbook does not only prevent problems; it brings conditions into view that would otherwise stay invisible until they became failures. Strip the checkpoints and you have not only removed the prevention. You have removed the instrumentation — and now the first thing you learn about a problem is that it has already happened.

Momentum does not feel like risk. It feels like competence — and it feels most like competence in the period immediately before it stops feeling like anything at all.

Why doesn’t the post-mortem find this?

Because the post-mortem investigates the failure, and the failure is not where the decision was made.

Location twelve gets the full treatment, and the review will produce findings, because a struggling opening always contains something to criticise. A manager who was underprepared. A hiring plan that slipped. A market that was harder than the model assumed. Every one of those will be true, and none of them is the cause.

The cause was a defensible decision made six locations earlier by people operating on real evidence, and there is nothing at location twelve that points back to it. The distance between the decision and the consequence is what makes this survivable as a pattern — if skipping three checkpoints had produced an immediate failure, the group would have stopped skipping checkpoints. The delay is not incidental. It is the enabling condition.

So the review concludes that location twelve had execution problems, which is accurate and useless, and the group tightens up at location twelve while continuing to run a nine-item playbook everywhere else. If you have ever fixed the site of a failure and watched the same failure appear somewhere else eight months later, you have run this loop.

This is the diagnostic descent in miniature: the fracture is not where it hurts, and the phase that produced the failure is upstream of the phase reporting it.

What holds when the organization is moving fast?

Not resolve, and not a reminder. Speed does not create discipline any more than pressure creates readiness — it reveals what was built into the process before the speed arrived.

What survives contact with momentum has a few things in common.

Skipping has to be visible rather than silent. The most useful change available to most organizations is not enforcing the playbook harder. It is instrumenting it, so a skipped item is recorded as a skipped item at the moment it is skipped. Not to punish anyone — to make the drift legible while it is happening, since nobody at location six believed they were starting anything.

Someone has to own the process separately from the schedule. When one person is accountable for both fidelity and speed, speed wins — because you measure speed weekly and you measure fidelity after something breaks. Separating those two is a decision-rights change and it is the highest-leverage structural move here.

The exceptions need a cost. A skip that requires a signature is not bureaucratic friction — it is a governor, and its whole job is to be mildly expensive at the moment when the argument for skipping is at its most persuasive. If it is easy to override, it will be overridden, and it will be overridden by intelligent people with good reasons.

And the review has to reach the decision, not the failure. When something breaks, the useful question is not what went wrong here. It is: when did we last change how we do this, and what evidence did we have at the time? That question is uncomfortable, because the answer usually implicates a period the organization remembers as a success.

Where this leads you

To a suspicion you should take seriously if your organization is currently moving well.

The four structural tensions in the Leadership by Design framework are the places an organization gives under load, and this one has a particular signature: it does its damage during the good stretch. The other tensions announce themselves through friction. This one announces itself through the absence of friction, which is why it is usually diagnosed in retrospect, from the far side of a failure that seemed to come from nowhere.

If you are faster than you were two years ago, the question is not whether that is good. It probably is. The question is which controls you are no longer running, when you stopped, and whether anybody made that decision on purpose.

Most organizations cannot answer the second part. That is the finding.


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.