Category: English

The meeting was not as quiet as it looked

The manager has reached the last slide.

“Any concerns before we go ahead?”

Nobody says anything. A few people look at the table. Someone closes a notebook. The manager waits for a moment and concludes that the team agrees.

Ten minutes later, in the corridor, an engineer tells a colleague that the schedule depends on a supplier assumption nobody has checked.

The information was in the room. It simply did not become available to the decision.

Why do employees not speak up at work? Usually not because they have nothing to say. They stay silent when they expect that speaking will achieve little and cost something. That expectation is built from experience: how leaders react, how disagreement is treated and whether earlier warnings changed anything.

The silence is not empty. It contains a calculation.

Asking for input does not make speaking safe

Leaders often believe they have opened the door because they asked a question.

“Any objections?” sounds like an invitation. Under hierarchy, it can sound like a test. The plan is finished, the presentation is polished and the senior person in the room has already committed to a date. Now the team is invited to challenge all of that in public.

People do not hear only the words. They read the situation.

Is there still a decision to influence? Does the manager want information, or confirmation? What happened to the last person who slowed the discussion down? Did a previous warning lead to examination, or to a debate about attitude and timing?

A formal invitation cannot erase those answers.

Silence is often learned in small moments

Most organisations do not tell employees to hide problems. They teach it indirectly.

An operator reports an unusual noise and is asked whether it is really worth stopping for. A planner questions a delivery date and has to defend their commitment. A technician raises a recurring defect and receives another reminder to follow the process.

Each response may appear reasonable in isolation. Together, they establish a pattern: uncomfortable information creates work for the messenger before it creates learning for the organisation.

People adapt. They wait for stronger evidence. They soften the message. They test it with trusted colleagues first. Eventually, they speak only when the problem can no longer be ignored.

By then, the organisation calls the issue a surprise.

People are not only protecting themselves

Fear of blame matters, but it is not the whole explanation.

Employees may stay quiet because they do not want to embarrass a colleague, derail a project or become known as the person who always sees a problem. They may believe that the team cannot act anyway. Some have raised the same concern before and watched it disappear into a meeting note.

Silence can therefore protect relationships, pace and the remaining belief that the work still makes sense.

This is why another communication campaign rarely changes much. The organisation asks for candour without changing what candour leads to.

If speaking produces no visible examination or decision, silence is not irrational. It is an efficient use of energy.

Hierarchy changes the weight of a sentence

The same observation does not carry the same risk for everyone.

A senior manager can call a plan unrealistic and be seen as decisive. A frontline employee can use the same words and be seen as negative. Expertise does not remove this difference. In some rooms, the person closest to the work has the best information and the least freedom to disturb the story.

This is where the usual advice to “be courageous” becomes too easy.

Courage may still be required. But an organisation that depends on repeated acts of personal courage to obtain routine operational information has designed a fragile information system.

The leadership task is not to demand bravery from below. It is to reduce the unnecessary social risk attached to relevant information.

The first response sets the price

Leaders cannot promise that every concern will be correct or that every objection will change the decision. Speaking up is not a veto.

They can make the first response useful.

When somebody raises a concern, resist the immediate defence of the plan. Ask what the person observed. Clarify what is known and what remains uncertain. Decide whether anything needs protection while the team checks the information.

Only then discuss the quality of the message, if that discussion is still needed.

The order matters. If people must first prove that they were entitled to interrupt, the next warning will arrive later.

A useful response does not mean agreement. It shows that relevant information can enter the system without the messenger becoming the problem.

Watch what happens after the question

In your next meeting, do not measure openness by the number of people who speak.

Watch the transition from information to response.

When someone introduces doubt, does the room become curious or impatient? Does the concern alter the conversation, even briefly? Can the team name uncertainty without immediately assigning blame? If nothing is raised, does the leader treat silence as agreement or check whether the decision can still be challenged?

One practical change is to ask before presenting the preferred answer. Explain what remains open and what is already fixed. Give people a real decision to influence, not a finished plan to endorse.

Then make the first inconvenient contribution visible in the work. Examine it. Decide. Return with an answer.

People learn from that sequence whether speaking is worth doing again.

The information already exists

The engineer in the corridor did not need another workshop on communication. The supplier assumption was already visible.

What was missing was a credible route into the decision.

Employee silence is therefore not simply a culture problem and certainly not a lack of engagement. It is evidence about governance. It shows whether local knowledge can reach authority while there is still time to act.

If leaders want people to speak up, they should stop asking only whether employees feel confident enough to talk. They should ask what their system does with a truth that arrives early, incomplete and inconvenient.

That is the point at which voice becomes organisational Capacity.

Further reading

“Employee Voice and Silence: Taking Stock a Decade Later” by Elizabeth W. Morrison

Morrison reviews research into why employees share or withhold work-related information. The paper is a useful foundation because it treats voice and silence as choices shaped by context and expected consequences, not as fixed personality traits.

“Implicit Voice Theories: Taken-for-Granted Rules of Self-Censorship at Work” by James R. Detert and Amy C. Edmondson

Detert and Edmondson show how unwritten beliefs about hierarchy and appropriateness can suppress voice even when leaders formally invite employees to contribute.

“Psychological Safety and Learning Behavior in Work Teams” by Amy C. Edmondson

Edmondson connects psychological Safety with learning behaviour. The practical value lies not in making work comfortable, but in making uncertainty and mistakes discussable while the team can still learn from them.

Explore more in The Shift series

The Internal Market for Truth

Why every leadership response changes the social price of the next piece of bad news – and how silence becomes an operating cost.

Culture Is Not a Cozy Affair

Why psychological Safety is not comfort or permanent agreement, but the capacity to work with productive disagreement.

---

The wider argument

This article examines one mechanism behind The Capacity Shift. The book shows the wider work system: how leadership shapes the flow of information and makes responsible action possible.

Explore the book and its models

The Capacity Shift can be pre-ordered on Amazon (affiliate link).

As an Amazon Associate, I may earn from qualifying purchases. This does not change the price you pay.

“I don’t know if I’m allowed to”

A colleague once gave me an answer that I still think about.

She was well trained, intelligent and in a position where she could initiate real improvement. I had arranged for her to attend Toyota Kata training, and the company had paid for it. Coaching was part of the training and part of the practice.

In this context, coaching does not mean personal counselling or offering unsolicited advice. A Kata coach helps a colleague work towards a concrete improvement goal, examine the next obstacle and learn from the next step.

Her manager at the time had taken part in the training as well. She liked Kata, used it herself and had given my colleague a clear mandate to apply it. Shortly afterwards, she moved to another position. My colleague did not know what her new manager thought about her taking on the Kata-coach role.

About six months later, I asked whether she was still using Kata to support colleagues in their improvement work.

She said she had found the training excellent. She even used the Kata questions with friends in her private life. But she did not use them to support improvement work in the company.

Why not?

“I don’t know if I’m allowed to.”

I was speechless.

She had not asked and been told no. She had expected the answer to be no, so she had not asked at all.

I later spoke to her new manager and asked whether he had any objection to her supporting colleagues with Kata. His answer was clear: no. She still does not take on that role today.

Kata met the organisation

That answer bothered me for another reason. In Toyota Kata, one of the coaching questions asks:

When can we go and see what we have learned from taking that step?

The exact wording can vary, but the logic is always the same: because we do not yet know what will happen, we take a step and compare the outcome with what we expected.

My colleague did not dare to take the step that would have told her whether she was allowed to act as a Kata coach at work.

She had learned a routine for moving through uncertainty by experimenting. Then she returned to an organisation in which the uncertainty about permission stopped the first experiment before it began.

Of course, she could have asked. That was my first thought. But stopping there would have been too comfortable, especially for me. I had initiated the training, yet we had not made sure that her mandate survived the change in leadership.

The training had worked well enough for her to use the practice outside work. Inside the company, something else was stronger.

The expected answer is part of the system

We tend to look for decisions we can observe: a proposal is accepted or rejected, permission is granted or withheld. These events leave traces in an inbox or an approval process.

An expected rejection leaves no such trace.

People form an idea of what will happen before they raise a subject. They know how managers respond when someone crosses a departmental boundary. They have seen what happens when an initiative consumes time but does not immediately produce a result. A change of manager can make even a previously legitimate role uncertain again.

None of this needs to appear in a policy. It still shapes action.

Her new manager’s actual answer did not support her expectation. It did not matter. Nobody had made that answer available to her. She acted on the answer she anticipated, and the real answer was never tested in the work.

This is where the Permission Queue begins. Not with a request awaiting approval, but with an idea that never reaches the person who could approve it.

We paid for capability and left it unused

The purpose of the training, at least from my perspective, was not to improve her conversations with friends. We wanted her to use the practice in the business.

Yet sending someone on a course does not change the system to which they return.

Training can build competence, and a manager can provide a mandate. Neither guarantees that the mandate will remain usable when responsibilities change. The organisation has to make the role and its backing durable.

That gap is often hidden by positive course evaluations. If participants enjoyed the training, understood the method and would recommend the instructor, the intervention looks successful on paper even when daily work has not changed.

But what changed in the work?

The loss was larger than the cost of the course. A person who could have helped colleagues work through real obstacles kept that capability outside the factory gate.

That is Capacity Tax in a very practical form. The organisation invests in judgement and then receives less of it than it paid for.

This was a governance problem

Supporting colleagues in their improvement work may sound harmless. Inside an organisation, however, it can raise legitimate questions.

Was Kata coaching part of her role now? Could she support colleagues outside her own reporting line? Would their managers welcome that, or regard it as interference? Which work should give way when this support required time?

I do not know which of these questions she had in mind. I do know that we had left enough unanswered for her to stop.

Her new manager’s “no objection” did not close that gap. It described his position when I asked him, but it did not make the existing mandate usable again. Her former manager had shared the training experience and explicitly supported the work. The new manager inherited the team, but not the conversation around her role. A mandate that had once been clear became uncertain without ever being withdrawn.

Calling for more courage would not have resolved that. Neither would a broad statement that everyone was “empowered”. She needed clarity about the space in which she could act and confidence that we would support responsible action within it.

This is why I see the incident as a matter of governance. A mandate that has to be guessed again after every leadership change is not a durable decision space. People need to know where they can act and whether that backing survives a change of manager.

Without that backing, the safest interpretation of almost any role is the narrowest one.

Initiative becomes real when it causes friction

Most organisations say they want initiative. That statement only becomes interesting when an initiative creates friction.

Someone spends time on an experiment whose result is uncertain, or a colleague from another function asks why this person is getting involved. The organisation now has to show what its invitation was worth.

Leaders do not have to approve every idea. A reasoned no can create more clarity than vague encouragement. What matters is whether people can bring forward a proposal without having to calculate a hidden personal cost first.

Research into employee voice describes this well. People carry assumptions about when speaking up is inappropriate or risky, even when leaders sincerely believe they are open to suggestions. The same mechanism applies to action. If an experiment is likely to leave someone exposed, avoiding it can be a perfectly rational response.

What I would do differently

Today, I would not end the process when the training ends.

Before the participant returns to normal work, I would agree where the new capability should first be used. We would choose a real case and make clear whose support is available if the work crosses an organisational boundary. Then we would set a date to look at what happened.

I would also treat that agreement as something the organisation owns, not as an informal understanding with one manager. If the manager changes, the mandate has to be discussed again and handed over deliberately. Otherwise, a change in the organisation quietly resets permission to zero.

This would continue the Kata rather than leave it in the classroom. The first step would not have to prove the entire approach. It would give us information from reality.

I would also ask a different question after a few weeks. Not whether the training was good, but where the person hesitated to apply it. The hesitation may reveal more about the organisation than another completed coaching cycle.

If the answer is “I wasn’t sure I was allowed to”, the first response should not be “Why didn’t you ask?”

The useful question is: What made you expect a no?

An empty inbox proves very little

My colleague could have asked. Her former manager could have handed over the mandate. Her new manager could have made his lack of objection visible to her. I could have closed that loop when I initiated the training. None of us did.

She had the competence and she had been given the mandate. Her new manager did not oppose it. Yet the work still stopped because the mandate had remained attached to one relationship instead of becoming a durable part of her role.

No request reached an inbox, and no manager had to say no. Daily work simply continued without the improvement support we had paid to develop.

That is the Permission Queue I want to understand: not only decisions waiting for a manager, but improvement work that disappears between two managers because nobody carries the mandate across the handover. An authority that has to be guessed again after every leadership change is not an authority people can reliably use.

Further reading

Toyota Kata by Mike Rother

Mike Rother’s work provides the foundation for the Improvement Kata and Coaching Kata used in this story. This example from the Lean Enterprise Institute shows how the coaching questions support the learner’s thinking rather than supplying the answer. That distinction matters here: the routine creates learning only when the organisation allows a real next step.

“Implicit Voice Theories: Taken-for-Granted Rules of Self-Censorship at Work” by James R. Detert and Amy C. Edmondson

Detert and Edmondson examine the unwritten beliefs people use when deciding whether it is safe or appropriate to speak up. Their work helps explain why a formal invitation is not enough. Employees act on what they expect the organisation to do, including when nobody has explicitly told them to remain silent.

Explore more in The Shift series

The Hero Reflex

The Permission Queue can grow when leaders answer every difficult question themselves. This article examines how useful intervention gradually teaches capable people to wait.

The Capacity Tax

Unused capability is one of the costs conventional accounting does not show. The Capacity Tax makes the delays and dependencies created by control visible as an operating cost.

---

The wider argument

This article examines one mechanism behind The Capacity Shift. The book shows the wider work system: how leadership shapes the flow of information and makes responsible action possible.

Explore the book and its models

The Capacity Shift can be pre-ordered on Amazon (affiliate link).

As an Amazon Associate, I may earn from qualifying purchases. This does not change the price you pay.

What strong leaders stop doing

Monday morning. A customer project is slipping, but the deadline has not moved. The team looks to you.

The team explains what has happened and adds what people have seen on site. When the account is complete, the room goes quiet.

You know the routine. At the whiteboard, you turn the uncertainty into a task list. The meeting feels productive again. Yet another problem now has your name.

You may even have made the right call.

That is what makes the habit so difficult to break.

A hard ask is not another difficult request made to the team. It is the demand a leader places on themselves: resist the urge to provide the answer when doing so would make the system more dependent.

The hardest move in leadership is rarely learning one more technique. It is refusing to use a strength that has become a constraint on the system.

In complex work, leadership is sometimes defined less by the action taken than by the impulse deliberately overcome.

Competence made you valuable

Most leaders did not reach their position by remaining quiet when problems appeared.

They built expertise, made decisions and restored order. When a project drifted, they found a route back. When a machine failed or a customer escalated, they knew whom to call. Their ability to provide answers became part of their professional identity.

Organisations reward this behaviour. The person who resolves the crisis becomes visible. The person who creates a system in which fewer crises need escalation is harder to notice.

Over time, competence becomes more than a capability. It becomes the leader’s proof of value.

Then the role changes.

The leader is no longer responsible only for solving the problem in front of the team. The leader is also responsible for what the team learns about itself while the problem is being solved.

An answer can restore motion today and still reduce Capacity tomorrow.

If every difficult situation ends with the leader taking over, the organisation learns a reliable routine. Under pressure, people stop thinking together and wait for the person with the highest status. Expertise remains in the room, but authority pulls the work towards one desk.

The leader appears decisive. The system becomes dependent.

The leader is part of the system

It is easy to describe this as a personality problem. The leader should become less controlling. The team should show more initiative.

That explanation misses the mechanism.

The team escalates because escalation has worked before. The leader answers because answering reduces the immediate tension. The project moves again, which rewards both sides for repeating the same exchange.

Next time, the team escalates earlier. The leader receives more decisions and becomes even more convinced that the organisation cannot move without intervention. What looks like a demanding team and an overworked leader is one self-reinforcing system.

The movement of information makes the cost visible. Local knowledge travels upwards, stripped of context as it passes through briefings and meetings. A decision eventually travels back down. While both are moving, the work waits.

The system is not short of competence. It has organised competence around permission.

This is where refusing the automatic answer becomes a governance intervention. By leaving a decision closer to the work, the leader interrupts the loop. Authority can remain with the information, and the team must convert its expertise into judgement.

The first result is rarely speed. The first result is friction because an old operating pattern no longer receives its expected response.

Letting go is not a leadership technique

It is tempting to treat delegation as another skill to acquire. Learn the framework, ask a better question and assign the right decision level.

Those things help. They do not address the hardest part.

Letting go asks a successful person to surrender an immediate reward. Giving the answer produces relief. It shortens the uncomfortable pause and confirms that the leader is still needed.

Holding back offers none of that reassurance.

You have to watch somebody approach the problem differently from you. Their first explanation may be incomplete. Their pace may feel slow. They may choose a route that is sound but not the route you would have taken.

The discomfort is not evidence that delegation has failed. Often, it is evidence that ownership is moving.

This is why the Capacity Shift requires leaders to let go.

The leader does not give up responsibility. The leader gives up the automatic claim on every answer.

That distinction matters. Otherwise, letting go becomes either theatre or neglect. In the first case, the team may decide until the leader dislikes the decision. In the second, responsibility is pushed down without context, competence or protection.

Neither creates Capacity.

The silence after the question

Return to the Monday morning meeting.

The team has described the situation and is waiting for your decision. This time, you do not move to the whiteboard.

You say: “I can see the pressure. If I were not here today, what would your first step be?”

Then comes the moment most leadership advice leaves out.

Silence.

The team does not immediately become empowered. People look at you because years of experience have taught them that the answer will eventually come from your side of the table. They may be checking whether your question is genuine or merely a test with a correct answer already hidden behind it.

Your own habit responds as well. The pause feels inefficient. You can hear the clock and imagine the customer waiting. Your brain supplies a solution and urges you to end the discomfort.

This is the hard ask: do not rescue the room from thinking.

Stay present. Hold the question long enough for somebody else to take hold of the work.

If you fill the silence immediately, the old contract remains intact. The team provides problems. You provide direction.

If you hold the space, something different can begin. A technician may offer a first move. A project manager may name an assumption that needs checking. Someone who had been quiet may explain why the obvious solution will not work at the customer site.

The shift rarely looks dramatic. It sounds like a conversation that no longer needs to travel through a single brain.

Not every silence means the same thing

Silence can indicate thought. It can also indicate fear.

A leader needs to know the difference.

When people are considering a problem, the room has tension but also movement. They look at the facts, test an idea and begin to respond to one another. The pause is part of the work.

Silence driven by fear feels different. People search the leader’s face before speaking. They offer safe fragments, retreat from disagreement or wait for clues about the preferred answer.

The answer is not to talk more. It is to lower the social cost of being wrong or inconvenient.

Ask what you may be missing. Make the boundaries explicit. Respond to an unfinished proposal with curiosity rather than correction. When someone challenges your assumption, do not punish the act by becoming defensive.

Letting go also means giving up the privilege of an unchallenged interpretation.

You are still accountable for the quality of the decision. You are no longer entitled to be its sole author.

The vacuum needs architecture

Removing control without replacing it creates confusion. A leader cannot simply stop deciding and call the result empowerment.

The space must be held by clear governance.

People need to understand the intent: what outcome matters and why. They need boundaries that are specific enough to protect the customer, the organisation and the people doing the work. Decision rights must sit with people who have the information and competence required to exercise them.

They also need to know what happens afterwards.

Will the leader support a responsible decision that produces an imperfect result? Or will authority be pulled back as soon as the choice becomes uncomfortable?

Teams learn from the answer much faster than they learn from an empowerment workshop.

One reversal can undo months of careful delegation. It tells people that ownership is temporary and that difficult decisions still belong upstairs. The next time uncertainty appears, they will wait earlier.

Letting go is therefore not an absence of leadership. It is a different use of authority.

The leader defines intent, protects the boundaries and keeps the system able to learn. Within that space, authority follows information.

This architecture draws on several established lines of thought. L. David Marquet shows how the language of intent moves ownership towards the people who hold operational knowledge. Steven van Baarle distinguishes power over people from the power to act. Stanley McChrystal describes the leadership stance as Eyes On, Hands Off: information remains shared while decisions become more distributed.

The Capacity Shift connects these ideas to the reinforcing loop of dependency. A leader’s intervention is not only a response to the current problem. It also changes how the system will behave when the next problem arrives.

Where strong leaders step back

The visible change begins with ordinary moments.

An expert asks for approval that is no longer required. The leader does not provide it out of habit. She asks for the expert’s assessment and intended action.

A project team presents two options. The leader does not choose merely because the team is in the room. He clarifies which consequence cannot be accepted and leaves the decision where the relevant knowledge sits.

During a disruption, the senior person notices a mistake in the team’s approach. If no boundary has been crossed and no immediate danger exists, she resists taking over. The team is allowed to see the consequence, correct the course and retain ownership of the learning.

These are small acts of deliberate restraint. Each one removes a little dependency from the operating system.

The result is not a passive leader. It is a leader whose intervention becomes more precise.

When the ship is genuinely at risk, act. When legal or ethical boundaries are threatened, step in. If the team lacks the required competence, build it before transferring the decision.

But do not confuse your discomfort with an emergency.

The Monday Morning Test

Choose one decision that routinely travels to you even though the team has better information.

When it arrives next Monday, try this sequence:

1. Name the problem and acknowledge the pressure without taking ownership of the answer.
2. Clarify the intent and the boundaries that cannot be crossed.
3. Ask: “What do you see, and what do you intend to do?”
4. Let the first silence stand. Do not turn a genuine question into a short delay before your own solution.
5. Intervene only if there is immediate danger, a missing capability or a boundary the team cannot yet see.
6. Back the decision visibly. Review what the system learned after the immediate issue has passed.

Do this once and the room may simply feel awkward.

Do it consistently and people begin arriving with judgement rather than requests for permission. Information travels less. Decisions move closer to the work. The leader is still present, but no longer functions as the central nerve of the organisation.

That is the operational proof of letting go.

The real measure of leadership

Leadership is often measured by the quality of decisions made in the leader’s presence.

That measure is incomplete.

The stronger test is what happens when the leader does not provide the answer, leaves the room or becomes temporarily unavailable. Does judgement remain distributed across the system, or does work begin to queue?

Competence qualifies you to lead a functioning system. Capacity becomes visible when you can hold uncertainty without taking the system’s thinking back into your own hands.

The hardest part is not knowing what to do.

It is knowing when not to do it – and staying accountable for the space that remains.

Further reading

Turn the Ship Around! by L. David Marquet

Marquet shows how changing the language of authority can move ownership towards the people who hold the information. His account is useful here because it makes clear that decentralisation depends on technical competence and shared intent, not on a leader simply stepping away.

Beyond Command and Control by Steven van Baarle

Van Baarle distinguishes power over people from the power to act. This helps expose the weakness in conventional empowerment: authority remains borrowed when the centre can withdraw it at any moment.

Team of Teams by General Stanley McChrystal with Tantum Collins, David Silverman and Chris Fussell

McChrystal explains why complex environments require shared consciousness and decentralised execution. The principle of Eyes On, Hands Off is especially useful for understanding how leaders can remain accountable without becoming the system’s decision bottleneck.

The Power of Habit by Charles Duhigg

Duhigg’s model of cue, routine and reward helps explain why the Hero Reflex survives even after leaders understand its cost. A crisis triggers the familiar routine of taking control, while the immediate relief rewards the behaviour. A different leadership practice must replace that routine in the moment.

Explore more in The Shift series

The Hero Reflex

Why the instinct to intervene can turn a capable leader into the most expensive bottleneck in the system.

Delegation Architecture

How clear decision rights move authority towards information without turning decentralisation into ambiguity.

Emancipation Instead of Empowerment

Why borrowed authority preserves dependence and what it takes to build agency that does not need to be granted again.

The Internal Market for Truth

How a leader’s first response sets the price of every warning that follows.

The tool

Get the Capacity Protocol – seven heuristics for leadership in complex systems.

---

The wider argument

This article examines one mechanism behind The Capacity Shift. The book shows the wider work system: how leadership shapes the flow of information and makes responsible action possible.

Explore the book and its models

The Capacity Shift can be pre-ordered on Amazon (affiliate link).

As an Amazon Associate, I may earn from qualifying purchases. This does not change the price you pay.

Operators know the moods of their equipment. They hear when a pump sounds different. They know which workaround will keep the line moving – and which repair would solve the problem for good.

And still, they cannot decide.

But the deviation travels upwards: first to the shift leader, then to the department head, and finally into a meeting. Emails follow. Slides appear. Calendars fill.

Meanwhile, the equipment keeps failing or producing scrap.

At best, the organisation eventually approves what was obvious at the start. At worst, it buys an expensive, complicated solution that cannot survive contact with the frontline.

You will not find this process in the accounts. Its hours are scattered across cost centres, its delays absorbed into daily business. We call it alignment, governance or simply due diligence. Soon, the cost feels unavoidable.

The company pays for it all the same.

What looks like order has turned Capacity into waiting time. I call that hidden bill the Capacity Tax.

What is the Capacity Tax?

Companies do not hire capable people merely to follow instructions. They hire them to notice deviations, understand context, assess risk and act responsibly when reality refuses to follow the plan.

Then the system gets hold of them. It pulls decisions upwards, makes bad news unattractive and rewards procedural compliance more reliably than sound judgement.

The company pays for judgement and uses obedience. The difference is the Capacity Tax.

By Capacity, I mean the collective ability to notice weak signals, speak the truth early, act within clear boundaries and learn from deviation. Capacity is not a personality trait. It is not a soft addition to the operating model. It is an operational resource.

The Capacity Tax is what the organisation loses when its work system fails to turn that resource into responsible action. The bill arrives as waiting, rework, escalation, report maintenance, slow decisions and risks discovered too late.

Six patterns make the bill visible:

1. We polish the image of control instead of improving the work.
2. Relevant truth is withheld or voiced too late.
3. Decisions wait far away from the information they require.
4. Process replaces professional judgement.
5. Repeated intervention trains dependency.
6. Unclear intent creates fast starts and expensive rework.

This is not an argument against control. Rules protect people. Standards preserve the best-known way. Some decisions belong at the centre. Good governance creates a dependable space in which people can act.

The Capacity Tax begins when control adds neither protection nor clarity. It begins when process replaces thought, authority is separated from relevant information, or people learn that waiting is safer than acting.

1. The cost of illusion

The dashboard is green like a watermelon – on the outside. Cut it open, and operational reality is bright red.

Experts spend time classifying deviations, explaining trends and turning reports into something presentable. Not all of that work is waste. Measures can reveal patterns and direct attention.

The trouble starts when presenting control consumes more energy than improving the work. Measurement becomes theatre. The organisation perfects the picture while the operation waits backstage.

And every individual task looks legitimate. Someone must prepare the slide. Someone must explain the variance. Someone must make the wording fit. Skilled time flows into presentation instead of causes, and management receives reassurance without the system becoming any better at noticing or responding.

This is the cost of illusion: paying to maintain a convincing image while reality waits for attention.

The warning sign is not necessarily a false report. It is a formally correct report that hides the question that matters: What can we see, decide or handle better today than we could yesterday?

Metrics are not the problem. Confusing counting with leading is.

2. The cost of silence

Bad news carries a price in every organisation. The only question is who pays it, and when.

If raising a risk makes someone look difficult, threatens a bonus or challenges a manager’s decision, truth becomes socially expensive. People calculate that cost. They do not necessarily withhold information because they do not care. Silence may be a rational response to the system around them.

The problem does not disappear. It simply chooses a more expensive moment to return.

A quality defect discussed today may require a correction. The same defect discovered weeks later may bring rework, delay or a lost customer. A weak technical signal can trigger an inspection today. After failure, it becomes downtime, repair and overload for everyone absorbing the gap.

A system saves nothing when bad news fails to travel. It merely moves the bill into the future – usually on worse terms.

The cost of silence is more than a culture issue. It is the premium an organisation pays because relevant information enters the decision too late. As time passes, options tend to narrow and the remaining choices become more expensive.

A quiet meeting does not prove alignment. It may show that disagreement costs more than silence.

3. The cost of bottlenecks

In many organisations, information sits close to the work while authority sits several levels away.

The operator sees the problem. The supervisor may remember the same work from years ago, but is already further removed from today’s reality. The planner sees the dependencies, but not how the fault behaves on site. The project team understands the consequences, but not the cause.

With every step upwards, the view grows wider – and the local detail fades. Yet the final decision sits at the top.

Information travels up. It is condensed, explained and fitted into a manager’s calendar. The decision then travels down. Every stop adds waiting and another opportunity for context to be lost.

Central decisions are sometimes essential. Several functions may be affected. The commitment may be large. Ethical, strategic or legal boundaries may be involved. But many organisations do not centralise only the exception. They centralise by habit.

The leader becomes the most expensive decision bottleneck in the system – not because that person works too little, but because too much work must squeeze through one point.

The cost of bottlenecks includes more than the decision-maker’s time. The company also pays for waiting teams, delayed milestones, blocked equipment, extra inventory and all the coordination surrounding the delay.

The better question is not, “How can leaders decide faster?” It is, “Which of these decisions need to be here at all?”

Authority should follow relevant information, inside clear intent, boundaries, competence and accountability.

4. The cost of rigidity

Standards matter. They preserve the best-known way, create shared language and stop every shift from solving the same problem again.

A good standard protects the work. A bad standard protects itself.

The line is crossed when process no longer supports professional judgement but replaces it. Capable adults feed forms and approval loops while the real situation calls for a reasoned adjustment. The official process drifts away from the work. People create workarounds. The organisation responds with more rules to control the workarounds created by the earlier rules.

Bureaucracy rarely begins with bad intent. Every new step has a story. Every signature made sense when it was added. But stacked together, these sensible precautions can build a system that protects against the exception by making normal work painfully expensive.

The cost of rigidity appears as duplicate work, accepted workarounds, slow adaptation and improvements that never happen. The most expensive result is not always the additional signature. It is the lesson people absorb: trust the process more than your perception.

That is the wrong lesson. Standards should be shields, not cages. They are the floor from which learning starts, not the ceiling where thinking stops.

5. The cost of dependency

A leader steps in and solves an urgent problem. In that moment, it may be the right thing to do. Time pressure sometimes demands a fast, unambiguous call.

But when intervention becomes a pattern, the system changes.

The team learns quickly: the leader will decide anyway. So people send recommendations upwards instead of carrying responsibility within their own space. Why think a difficult question through to the end when the final thinking will happen elsewhere?

The leader, meanwhile, sees that little moves without intervention. That observation confirms the urge to act. The more often the leader rescues, the more dependent the system becomes. The more dependent the system becomes, the more necessary each rescue appears.

You have not built a capable team. You have built a waiting line.

The cost of dependency reaches far beyond slow decisions. It chains leadership attention to recurring operational questions. Others never build decision experience. The organisation becomes fragile whenever the central person is unavailable or the number of problems grows.

And the higher the decision climbs, the more space it takes from the calendar and attention of people who should be dealing with questions of strategic consequence. Dependency does not only slow the frontline. It paralyses the top.

The Hero solves today’s problem and damages tomorrow’s Capacity.

6. The cost of blind action

Not every Capacity Tax begins with waiting. Some of it begins with starting too fast.

A project must finally move. The pressure is visible, so the teams launch. Purpose, boundaries and decision rights can be clarified later.

Except later is when the bill arrives. Each function has translated the assignment through its own logic. Local solutions collide. Interfaces must be renegotiated, work repeated and decisions escalated.

From a distance, it looks like speed. Activity has been mistaken for progress.

The cost of blind action is the price of missing clarity at the start: friction, changes of direction, rework and the eventual delay created by an apparently fast launch.

The answer is not endless planning. It is a short, demanding clarification: What outcome are we trying to create? Which boundaries hold? Who can decide inside them? Which assumptions must we test early?

That clarity creates decentralised speed. Think slowly enough for the system to act fast.

Why the Capacity Tax never appears as one number

The Capacity Tax refuses to stay in one account. Part of it appears as labour. The rest hides in delay, inventory, downtime, rework or turnover. Some of it never appears at all: the concern left unspoken, the decision avoided, the improvement nobody bothers to suggest anymore.

Every item comes with a plausible local explanation. Extra inventory? Uncertain supply. Rework? An unclear specification. Another meeting? Necessary alignment. Another lost day? The approval was still pending.

Those explanations may be correct. They can still hide the shared pattern: the system fails to convert available information and competence into timely, coordinated action.

There is no credible universal percentage for the Capacity Tax. It is not an accounting line and it should not become another doubtful ROI calculator. It is a diagnostic model. It connects scattered friction to a common cause and directs attention to the mechanisms behind the numbers.

Where does your system pay Capacity Tax?

Ask these six questions in your next meeting:

1. How much expert time goes into presenting control rather than improving the work?
2. Which bad news reaches leadership later than it was known operationally?
3. Which decisions wait for people further away from the problem?
4. Where does process replace reasoned professional judgement?
5. Which problems return because a leader keeps solving them personally?
6. Where does a fast start create alignment work, changes of direction or rework later?

Then ask the question that makes the conversation useful:

Which specific delay, rework loop or escalation could we avoid if relevant information met clear decision rights earlier?

Resist the urge to launch a company-wide programme. Choose one recurring workflow instead. Follow the information. Where does it stop? Who needs permission from whom? What reaction do people expect when they bring bad news?

Then capture one concrete consequence: hours lost, additional handovers, rework or delay.

That makes the Capacity Tax visible without pretending to calculate the whole organisation.

How to reduce the Capacity Tax

The answer to less control is not less leadership. It is better clarity.

Clarity starts with shared intent. What outcome matters? Why does it matter? Which ethical, technical and commercial boundaries apply? Once that frame is clear, decision rights can move towards the relevant information.

This requires more than handing out tasks. People need competence, access to context and confidence that responsible action inside the agreed frame will be supported. Leaders remain accountable for the system. They stop taking every individual decision away from it.

Standards change their role as well. They still preserve the best-known way, but they remain open to challenge. A reasoned deviation is not automatically disobedience. It may be the first visible sign of a gap in the system.

Finally, the response to bad news determines whether truth remains available early. Punish the messenger and the system will pay the cost of silence later. Seek to understand first, and you reduce social risk before operational risk becomes larger.

Shared language creates clarity. Clarity creates Capacity. Capacity creates Excellence.

The bill gets paid either way

The Capacity Tax does not disappear because no report carries its name. The organisation pays it every day – in waiting, rework, unnecessary escalation and unused judgement.

Leadership begins by making that bill visible. The next step is not to remove control without replacement. It is to design governance so people understand what must be achieved, which boundaries apply and where they can act responsibly.

Organisations do not lose performance only through a lack of competence. They also lose it through systems that convert existing competence into dependency, silence and waiting.

The Capacity Tax is the price of that loss.

The Capacity Shift begins when you stop treating the price as unavoidable.

Further reading

“Don’t Let Metrics Undermine Your Business” by Michael Harris and Bill Tayler, Harvard Business Review, September–October 2019

Harris and Tayler explain how organisations begin to treat a measure as a substitute for the strategy it was meant to represent. It provides the research background for the cost of illusion: people improve the number while the underlying purpose slips from view.

“Beyond command and control: tensions arising from empowerment initiatives” by Steven van Baarle et al., Organization Studies, 2021

The study examines the tension between “power over” and “power to”. It helps explain why simply handing over responsibility is not enough – and why leaders can reproduce dependency even while trying to create agency.

Explore more in The Shift Series

Counting vs. Practicing

Why polished metrics can calm management while the practices that create reliable work remain unchanged.

Silence Is the Loudest Warning

How the expected reaction of leadership determines whether weak signals travel early or return later as expensive surprises.

Shield or Cage?

Why standards create value as a floor for good judgement – and create rigidity when they become the ceiling for thought.

The Hero Reflex

How well-intended intervention solves today’s problem while teaching the organisation to wait for tomorrow’s answer.

---

The wider argument

This article examines one mechanism behind The Capacity Shift. The book shows the wider work system: how leadership shapes the flow of information and makes responsible action possible.

Explore the book and its models

The Capacity Shift can be pre-ordered on Amazon (affiliate link).

As an Amazon Associate, I may earn from qualifying purchases. This does not change the price you pay.