Category: Unkategorisiert

What comes after zero? During one of my assignments, the site celebrated five thousand days without a recordable safety incident.

On that day, across the site, the number was everywhere. Posters at the entrance. Speeches from leadership. Cake in the cafeteria. Congratulations from the board.

We once reached “zero” and stayed there for years.

But what was never discussed, hardly known in the company, was what happened on day 5001. Two men died. A third barely survived.

They were not numbers. They were colleagues. Friends.

Whilst the milestone was celebrated as a proof of safety, hardly anyone reflected on what brought us there. 

It was the team’s unspoken decision to never let something like this happen again. They took ownership. And not just improved safety but performance as well. The site was known for its cleanliness and praised for its strong customer relationships.

Taking the time to reflect on the catastrophe – years before – changed everything I believed about performance, culture, and leadership.

Counting vs. Practicing

For years, we had been counting days. But the number didn’t keep people safe. Practices did. Conversations did. Ownership did.

Culture wasn’t born in procedures or KPIs. It was created in daily patterns: Crews speaking up before starting a job, leaders walking the floor with curiosity instead of clipboards, and teams stopping work when something felt wrong.

None of that fit neatly into a dashboard. But all of it shaped the condition we called “safety.”

The truth is: a number shows the past, but a practice shapes the future.

From Mandates to Ownership

When management mandates safety, we start tracking incidents. When teams own their safety, they start shaping behavior.

After the tragedy, the people on site didn’t wait for new procedures or slogans.

They made a quiet, collective decision: Never again.

It wasn’t ordered from headquarters. It wasn’t even written down. But it was ingrained in the team, and it was lived.

They double-checked risk assessments. They refused to push when the plan was wrong.

They called each other out: not to shame, but to protect!

That difference between mandate and ownership is the difference between compliance and culture – the capacity that lives in people and forms a team.

Excellence Compounds

Something else happened, too. When the site became safer, it also became better in every other way. Housekeeping improved. Maintenance quality grew. Reliability increased. Costs went down. Trust went up.

Why? Because excellence is systemic. You can’t raise one part of the system and keep mediocrity everywhere else. Once people take shared responsibility, the effect spills over.

At our plant, safety was the door – and as the team improved it, performance rose beyond expectations.

The Limit of Zero

Maturity Curves, like the Bradley Curve, explain how reactive cultures evolve toward independence and interdependence. All the way to zero!

But it stops there.

If you look at safety like that, Zero is not the goal. Zero is a ceiling.

Without knowing what comes next, success becomes a trap. People stop challenging. Leaders stop listening. Workarounds sneak back in, and before long, the risk returns.

Zero is not proof of safety. Zero is proof that safety once happened. The question for the leadership is whether it will continue to happen.

From Avoidance to Aspiration

The turning point is this: stop defining success by what you want to avoid. Start defining it by what you want to become.

Fear can start a change, but only aspiration sustains it. 

That’s why safety is not an endpoint; it’s an entry point. The practices that keep people alive are the same that make organizations excellent:

Shared responsibility, open communication, and the courage to fix what’s broken.

What Comes After Zero

Day 5001 taught me this:

Culture is not a mandate. It’s a decision – made by teams, owned by individuals, reinforced by leaders who create space for ownership.

That is where Capacity Shift begins. When organizations stop controlling and start building capacity, they can see, decide, and act together.

Because performance doesn’t come from pressure. It grows from patterns. And those patterns start with choices. Every single day.

Further reading

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

This article provides scientific proof of the failure of ‘zero’. It explains the phenomenon of ‘surrogation’: why our brains tend to confuse the metric (5,000 accident-free days) with the actual goal (safety) and how this confusion blinds us to real risks.

Explore more in The Shift Series

• Silence is the loudest warning.
  Why did we celebrate the 5,000 days even though there was a risk? Because we remained silent. Learn why silence in teams is rarely a sign of harmony, but often the loudest warning signal for fear – and the harbinger of disaster.
• The Hero Reflex
  The accident on day 5,001 also happened because managers believed they could ‘order’ safety. Read why we need to stop playing the omniscient saviour so that our teams can start taking real responsibility.
  

The False Trade-off

Why the tension between Safety and productivity can be real in the moment – but becomes destructive when it is designed into the operating model.

Why Safety and Performance rise together

The line is running behind schedule when an operator notices that a guard no longer closes cleanly.

The shift has already lost an hour. The customer is waiting, the next batch is planned and the defect does not look dramatic. Stopping now will certainly cost output. Continuing may cost nothing at all.

Or it may cost considerably more.

This is the moment in which the old argument returns: Safety or productivity. Protection or production. Which side matters more today?

The tension is real. A necessary stop can reduce output during this shift. An inspection takes time. A safer method may initially require more preparation.

The mistake begins when a difficult decision in one moment becomes a general theory of how an organisation performs.

Safety and productivity can conflict in the short term. They are not opposing capabilities.

The seesaw is a management choice

Many organisations manage Safety and production like two people on a seesaw. If one side rises, the other must fall.

The image feels convincing because people experience it every day. A Safety initiative arrives as an additional checklist. A permit requires another signature. A meeting interrupts the work without resolving the problem that made the work risky.

Safety then appears to consume productive time.

Sometimes it does.

But that does not prove that protection and performance are natural enemies. It shows how the organisation has designed Safety.

When Safety is built as a parallel system, every protective act becomes extra work. Production owns the task. Safety owns the interruption. The people at the frontline are left to negotiate between them while the clock keeps moving.

The seesaw is not a law of nature. It is the result of governing one piece of work through competing systems.

The short-term conflict still matters

It would be dishonest to pretend that every Safety decision immediately improves output.

If a crane lift is stopped because the wind exceeds the agreed limit, the lift does not happen. If a team isolates an installation before investigating a leak, production waits. If a technician refuses a rushed restart, the dashboard may be red by the end of the day.

These are genuine trade-offs in time.

Mature organisations do not make them disappear with a slogan. They make the decision early enough to retain options.

The immature system keeps moving until the choice becomes more expensive. The guard fails completely. The uncertain measurement becomes a rejected batch. The leak becomes an outage, and the schedule pressure that discouraged the first stop now multiplies.

The question is therefore not whether stopping has a cost. It is whether the system can recognise the smaller cost before reality sends the larger invoice.

The compliance trap

The false trade-off becomes strongest in organisations that rely on external control.

Rules are added after incidents. Audits check whether the rules are visible. Specialists monitor compliance, and the people doing the work learn how to satisfy the evidence required by the system.

This can establish a necessary floor. It can prevent arbitrary practice and make important boundaries explicit.

It becomes a trap when following the rule replaces understanding the risk.

Then Safety is experienced as administration. A capable technician waits for a permit from someone with less context. Operators complete a checklist whose questions no longer fit the task. Managers ask for faster decisions while keeping authority several levels away from the information.

The organisation pays for expertise and uses it to service permission.

Under those conditions, more Safety activity can indeed create more friction. The problem is not that Safety has become too important. The problem is that control has been confused with capability.

What changes after compliance

The shift begins when the organisation stops treating people as the variable that procedures must constrain and starts using their judgement as part of the control system.

That does not mean fewer boundaries. It means clearer ones.

People know what must be protected and when work must stop. Within those limits, authority sits close enough to the work for weak signals to become action. A concern does not need to complete a tour through the hierarchy before somebody checks it.

Leadership response matters here. If an early warning is met with irritation, the next warning arrives later. If it is met with curiosity, the organisation buys time.

Learning completes the loop. The team does not merely restart the line. It asks what allowed the weak signal to develop and changes the conditions for the next shift.

The same practices improve more than Safety.

A team that speaks early about a guard also speaks early about a doubtful measurement. People who can stop unsafe work can interrupt defective work. A system that learns from near misses can learn from rework, delay and customer complaints before they repeat.

Safety and Performance begin to rise together because they draw on the same Capacity.

What the two curves actually mean

The two curves are not a promise that every intervention pays back immediately.

They describe what becomes visible as an organisation develops the ability to notice, speak, decide and learn.

On one curve, serious events and preventable harm decline. On the other, reliable performance grows. Quality stabilises. Decisions become faster because fewer of them wait for distant approval. Problems are corrected while they are still small enough to offer choices.

The curves move in different directions. Their cause is the same.

This is the central point. Performance does not improve because Safety has been relaxed. Safety does not improve because production has been subordinated. Both improve when the work system becomes more capable of handling reality.

Research supports this distinction. In a study of 198 manufacturing plants, Mark Pagell and his colleagues found that Safety and operational effectiveness became complementary when organisations managed them through a joint system. The contradiction appeared when Safety and operations were governed as separate, unequal silos.

The false trade-off is therefore not resolved by choosing the correct side. It is resolved by changing the system that keeps presenting the choice.

Capacity is the missing variable

Traditional dashboards show the outcomes after work has happened. They count injuries, output, defects and downtime.

They rarely show whether the organisation had options before the outcome occurred.

Capacity is that missing variable: the collective ability to see weak signals, tell the truth early and act within clear boundaries.

When Capacity is low, the curves fight each other. Safety relies on controls that interrupt work because the work itself cannot be trusted. Production relies on workarounds because the controls do not fit reality.

As Capacity grows, protection moves into the work. Operators no longer have to choose between making the number and raising the concern. Raising the concern becomes part of how the number is made reliably.

This is also where psychological Safety matters. Amy Edmondson’s research did not show that feeling comfortable automatically creates performance. It showed a mechanism: psychological Safety supports learning behaviour, and learning helps teams perform.

The value lies in what people can do with the social space – ask, challenge, admit uncertainty and correct the work.

Where the argument has limits

Safety and Performance rising together does not remove every constraint.

Resources remain finite. Equipment has physical limits. Legal requirements are not optional, and some risks must be reduced even when no economic return can be demonstrated.

Nor should every reported concern stop an entire operation. Mature judgement includes proportionality. People need competence, shared intent and boundaries that distinguish an immediate danger from an issue that can be controlled while work continues.

The Capacity Shift is not an argument for less protection. It is an argument against forcing protection and production to compete through poor governance.

The goal is not a workplace in which trade-offs never occur. It is a system capable of seeing them early, making them consciously and learning from the decision.

Test the trade-off at the line

The next time somebody says that Safety is slowing the work, do not defend Safety in general. Follow the friction.

Ask which action takes time and what risk it is intended to control.

Check whether the requirement still fits the work. Find out who can change it and how long that decision takes.

Then ask what would need to be true for the protective action to become part of reliable execution rather than an interruption beside it.

The answer may be a better standard. It may be a clearer boundary or authority closer to the information.

If the only answer is another reminder to comply, the seesaw will remain.

Stop balancing. Start building.

The operator at the guard does not need a philosophical debate between Safety and productivity.

She needs clarity about the boundary, the authority to respond and confidence that an early stop will be examined rather than punished.

That response may cost output today.

What happens next determines whether the organisation merely paid for a stop or invested in Capacity.

Safety and Performance do not rise together because the tension is imaginary. They rise together when the organisation becomes good enough to handle the tension before it becomes damage.

The trade-off is not always false in the moment.

It is false as an operating model.

Further reading

“Are Safety and Operational Effectiveness Contradictory Requirements?” by Mark Pagell, David Johnston, Adriana Veltri, Robert Klassen and Jonathan Biehl

The study uses survey and archival data from 198 manufacturing plants. Its practical value lies in the mechanism it identifies: joint management systems make Safety and operations complementary, while separate and unequal routines create the trade-off organisations then experience at the frontline.

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

Edmondson links psychological Safety to learning behaviour and shows how learning mediates team performance. This matters because voice is not valuable as a feeling alone. It creates performance when teams use it to surface uncertainty and improve the work.

Managing the Unexpected by Karl E. Weick and Kathleen M. Sutcliffe

Weick and Sutcliffe explain how high-reliability organisations sustain performance under uncertainty. Their focus on weak signals, operational sensitivity and deference to expertise helps show why reliable performance and protection depend on the same organising practices.

Explore more in The Shift series

Safety Is Performance

How Safety reveals the governance and maturity of the entire work system.

Day 5001 – What Comes After Zero?

Why the absence of harm is not yet evidence that an organisation can respond when conditions change.

Flip the Curve

How organisations move from control and compliance towards distributed Capacity.

Friction is part of the work

The project meeting is calm. The milestones are green and nobody challenges the recovery plan.

Then the project fails exactly where several people had expected it to fail.

Afterwards, the warning signs appear in every reconstruction. The engineer had doubts about the design. Procurement knew the supplier was slipping. Operations did not believe the commissioning window was realistic.

The information existed. It never became a decision.

This is why culture is not the soft side of business. Culture determines whether the knowledge already present in the organisation can affect the work before reality makes the decision for you.

A quiet room can be expensive

Many organisations separate hard subjects from soft ones. Strategy, finance and technology belong to the serious agenda. Culture is discussed afterwards, often through values, surveys and workshops.

Daily work does not respect that separation.

A technical risk has to be voiced. A plan has to survive disagreement. A manager has to hear that the preferred solution will not work. The quality of these interactions changes the quality of the operating decision.

If people cannot challenge a weak assumption, the organisation has not removed the conflict. It has postponed it.

The later version usually costs more.

What Project Aristotle actually tells us

Google’s Project Aristotle asked what made teams effective inside Google. The researchers identified five team dynamics: psychological Safety, dependability, structure and clarity, meaning, and impact.

Psychological Safety came first. Team members needed to believe that interpersonal risk would not be punished when they asked a question, admitted uncertainty or offered an idea.

That finding is useful. It is not a universal law proving that talent or team composition never matter. Google itself presents the work as a way to think about effective teams and explicitly notes that other organisations may find different patterns.

The practical lesson is narrower and stronger: expertise creates value only when the interaction around it allows the expertise to enter the work.

A brilliant engineer who withholds a doubt contributes less than the organisation has paid for. A diverse team whose members edit themselves before speaking cannot use its diversity.

Psychological Safety is not comfort

The word “safety” invites a common misunderstanding. A psychologically safe team is not a room in which everyone feels comfortable and nobody is challenged.

Often the opposite is visible.

People ask the question that slows the meeting. They admit that an estimate is weak. A technician tells a senior manager that the proposed restart crosses a boundary.

These moments create discomfort. What psychological Safety changes is the personal price attached to that discomfort.

The work can become harder in the room because it becomes less dangerous outside it.

This is also why niceness is not enough. A polite team can avoid every difficult issue. Respect matters, but respect without candour protects harmony rather than performance.

Productive conflict needs boundaries

Permission to disagree does not mean every debate should continue indefinitely.

Teams need a shared purpose and enough technical context to understand what is being protected. Decision rights must be clear. Someone remains accountable for closing the discussion and choosing a course of action.

Without those conditions, voice can become noise. People repeat preferences, defend territory or reopen decisions without new information.

Psychological Safety does not remove the need for leadership. It changes the work of leadership.

The leader has to make dissent usable. They ask for the observation behind the objection. They distinguish a violated boundary from a different preference. Then they decide or place the decision where the best information sits.

The aim is not agreement. It is a decision that has had contact with reality.

Culture becomes visible in the first response

Values do not determine whether people speak next time. Reactions do.

A manager can invite challenge and still close the market within seconds. They roll their eyes, defend the plan before asking a question or explain how much effort has already gone into the decision.

The room learns quickly.

The reverse is equally concrete. A leader can pause, ask what the person sees and check whether the new information changes a boundary or assumption. The objection may still be rejected. What matters is that it was examined rather than socially punished.

Culture is built in this sequence, not in the poster beside the meeting room.

The hard currency is earlier truth

Calling culture “hard currency” does not mean inventing a financial value for every conversation.

Its economic effect lies in timing.

An early contradiction leaves choices. The design can change before procurement. The maintenance window can move before customers are promised a date. A weak signal can be inspected before it becomes an outage.

When disagreement is socially expensive, the same information arrives later. Options disappear while the eventual correction becomes more disruptive.

This is the connection to the Capacity Tax. Silence converts an avoidable conversation into delay, rework or damage. The invoice appears in operations, although the cause began in an interaction.

Culture is therefore not separate from performance. It governs when reality is allowed into the decision.

Put one decision under pressure

Do not begin with another culture programme.

Choose one important decision that appears settled. Ask the people closest to the consequences what would make it fail.

Do not defend it while they answer.

Then examine the strongest objection. Is it new information, a misunderstood boundary or merely a different preference? Decide what changes and explain what does not.

Finally, watch what happens at the next meeting. Do people bring difficult information earlier, or did they learn that the invitation was ceremonial?

That is a harder test of culture than a value statement.

The room should not always feel easy

A capable organisation does not eliminate tension. It prevents tension from going underground.

People can disagree without turning the disagreement into a personal contest. Leaders can remain accountable without pretending to hold all relevant knowledge. Teams can close a decision without silencing the information needed to revisit it later.

This is not a cosy affair.

It is disciplined contact with reality.

Further reading

Google re:Work: Understand team effectiveness

Google’s own guide describes the five dynamics identified in Project Aristotle and presents psychological Safety as the first. It is also valuable for its restraint: the findings came from Google teams, and other organisations may discover different drivers in their own context.

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

Edmondson’s study connects psychological Safety to learning behaviour rather than comfort. The mechanism matters: teams perform better when people can ask for help, discuss errors and test uncertainty in the work.

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

Morrison reviews why employees speak up or withhold work-related information. The article adds an important guardrail: voice is a discretionary behaviour shaped by hierarchy, context and expected consequences, not something leaders create by issuing an invitation.

Explore more in The Shift series

The Internal Market for Truth

How leadership reactions set the social price of bad news and determine whether local information arrives in time.

The Hero Reflex

Why an answer-giving leader can dominate the room even while asking other people to contribute.

Delegation architecture. ‘Just do it’ is not a strategy. Delegation without architecture is chaos. This article explains how to clearly separate decision-making and execution so that your team can truly take action.

‘I told my team to make more decisions themselves. But nothing happens. In the end, everything ends up back on my desk.’

I hear this sentence often. The frustration is real. But the diagnosis is usually wrong. The problem is not the team (that they ‘don’t want to’). The problem is not the manager (that they ‘can’t let go’). The problem is the lack of a delegation architecture for decision-making.

A recent article in the Harvard Business Review puts it bluntly: ‘Simply handing over power offers little guarantee that something positive will come of it.’ Delegation does not require a retreat from leadership. It requires a new design for work.

The deadly mix of operations and policy

Why does delegation fail in everyday life? Because we mix two completely different states of work in our meetings:

1. Operational firefighting (operations): Who will do what by tomorrow? The acute problem. The pressure.

2. Work on the system (policy/governance): How do we want to work together in principle? The rules. The principles.

If you put both in one meeting, operational firefighting always wins. The pressure of the ‘now’ supplants the “important”. The ‘power over’ logic of day-to-day business (quick commands) crushes the delicate plant of self-organisation.

Separating decision-making areas, the basis for effective teams

Research on organisational development (including Van Baarle) suggests not a soft but a hard structural separation here:

Mode 1: Operations (execution)

Speed is what counts here. Hierarchies are okay here. When the ship is in a storm, we don’t discuss the seating arrangement. The captain is in command. The rule here is: execute within the limits.

Mode 2: Policy (control)

This is where the rules are made. This is where ranks take a back seat. This is where the principle of ‘voice’ applies. We negotiate together the ‘boundaries’ and ‘intents’ within which the boss and the team will later be allowed to operate.

The capacity shift happens in Mode 2. Many managers try to coach empowerment during the crisis. That is too late. They need to build capacity before the crisis in Policy Mode.

Why freedom needs delegation architecture

This is the operational core of Intent over Instruction (Heuristic #4 in the Capacity Protocol). In the policy meeting, we define the intent and the boundaries (Power-To). That is the framework. Within this framework, day-to-day operations are then executed quickly, decisively and autonomously – without further consultation.

Designing delegation correctly: the Capacity Shift

Freedom is not the absence of structure. Freedom is the result of clear structure. ISO certification or an organisational chart often only prove that you can follow rules. The Capacity Shift proves that you can make rules that empower your team to act.

Stop misunderstanding delegation as ‘laissez-faire’. Simply saying ‘go ahead’ creates fear. Saying ‘here is the framework, there is the goal, you are in control’ creates leadership.

Build the bridge before you need it.

Weiterführende Literatur

“10 Principles of Effective Organizations” by  Michael O’Malley Published on HBR.org / August 8, 2022

Michael O’Malley uses the ‘teenager car keys’ metaphor to vividly illustrate that empowerment without prior competence building and structure is negligent. It provides external evidence for your thesis that true autonomy does not arise from the absence of hierarchy, but is only made possible in the first place by crystal-clear role definitions.

„Beyond Command and Control: Designing for Voice and Empowerment.“ by Van Baarle, S. (Technische Universiteit Eindhoven 2021)

Van Baarle’s research shows how organisations that relax command-and-control and strengthen clarity, participation and empowerment become more resilient and effective. Precisely the shift from control to capacity.

Explore more in The Shift Series:

• Shield or cage?
  Why standards help when they are used as a floor rather than a ceiling.
• The Hard Ask
  Delegation architecture creates the framework. The cornerstone explains why it fails when the leader still reaches for the answer at the decisive moment.

Emancipation instead of empowerment: Empowerment is often just a nice way of exercising control. What we need, however, is genuine emancipation. Because emancipation in organisations means that people are not merely given the ability to act, but are allowed to use it: without permission, but with clarity.

It sounds so enlightened: ‘We must empower our employees.’ It’s in every mission statement. It’s nodded to at every management conference. But if we’re honest, the term ‘empowerment’ has a fundamental flaw.

It implies a direction: from the top down. I, the powerful one, give you, the powerless one, a piece of my power. That sounds generous. But it cements the very hierarchy that we actually want to make more flexible. Because what is granted can be taken away again at any time. In many companies, empowerment is not real freedom. It is ‘letting go of the leash’. And whoever holds the leash remains the owner of the dog.

The grammatical error of leadership

I call this the ‘grammatical error’ of modern leadership: ‘If power has to be granted, then it never belonged to the people who do the work.’

As long as employees believe that their ability to act is a loan from their boss, they will hesitate in a crisis. They will ask themselves: ‘Am I really allowed to do that now? Or does that only apply when the going is good?’ This hesitation is fatal in complex systems. It is the moment when the octopus’s arm waits for the brain – and is eaten.

From empowerment to emancipation

Power over vs. power to – two completely different logics

We need to change the term. We don’t need empowerment, we need emancipation. Organisational research (including Dr Steven Van Baarle) makes a precise distinction between two types of power:

1. Power over (someone): This is classic hierarchical power. It is based on coercion and position. Empowerment often still operates within this logic (‘I allow you to do something’).
2. Power-to (act): This is the generative ability of a person or team to achieve results. This power is not conferred. It is inherent. It does not need to be given, but rather unleashed.

Emancipation in business means removing obstacles

Emancipation in business means recognising that the “power to” already exists in the experts on the front line. The task of leadership is not to distribute power, but to remove the obstacles (bureaucracy, fear, micromanagement) that block this power.

Adults, not children

Empowerment often treats employees like teenagers who are lent the car keys in the hope that they won’t wreck the car. Emancipation treats employees like adults.

The Hard Ask – The test for your leadership

Check your language. If you say, ‘I’m giving my team more responsibility,’ you’re still playing the hero who hands out favours.

Instead, try a new mindset: ‘I’m clearing the obstacles out of the way so you can take the responsibility you deserve.’

Stop conferring power. Start freeing up capacity.

Further reading

„Beyond Command and Control: Designing for Voice and Empowerment.“ by Van Baarle, S. (Technische Universiteit Eindhoven 2021)

Van Baarle’s research demonstrates how organizations that loosen command-and-control and strengthen clarity, voice, and empowerment become more resilient and more capable, exactly the shift from control to capacity.

Explore more in The Shift Series

• The Hero Reflex
  Why managers find it so difficult to let go and how ego, speed, and status keep cultures dependent.
• Don’t be a head. Be an octopus.
  Read how to build an organisation where intelligence and power reside where they belong: at the front line.
• The Hard Ask
  Emancipation describes the destination. The cornerstone examines the moment when a leader must create space without giving up responsibility.

Shield or cage? ISO certification proves that you can follow rules. It does not prove that you are capable of acting in a crisis. Because of this, standards should not replace thinking.

Many COOs and quality managers have the same ambivalent relationship with standards. They know that ISO, audits and regulations are essential. They create legitimacy and basic order. At the same time, they sense that something about them paralyses the organisation.

Meetings revolve around evidence rather than results. Audits generate hectic activity – but little real insight. And in critical situations, everyone suddenly looks up instead of solving the problem.

This is not a failure of leadership. It is a systemic effect that I call the ‘compliance trap’.

The floor and the ceiling

ISO standards were created to establish a floor below which performance must not fall. They are the foundation. The problem begins when organisations mistakenly consider this floor to be the ceiling – the maximum achievable goal.

In this ‘dependent’ maturity phase, certification becomes an end in itself.

• People ask, ‘What does the regulation say?’
• Instead of, ‘What is right here and now?’

When the standard becomes the ceiling, people stop thinking. They replace judgement with compliance.

Compliance is not capacity

This is the crucial error in thinking that lulls many companies into a false sense of security until disaster strikes: certification proves that a system can follow rules. It does not prove that it can act in a crisis.

ISO measures compliance. It does not measure capacity. Capacity is the ability of a system to recognise weak signals, act without consultation and turn mistakes into learning experiences – even when the standard no longer covers the situation.

It is precisely these skills that are often systematically trained out of people in highly regulated cultures.

‘Don’t make too many rules’

Megaproject expert Bent Flyvbjerg sums it up brutally in his heuristics for ‘master builders’: ‘Don’t make too many rules.’

Not because rules are bad, but because too many rules stifle thinking. The more we try to cover every eventuality with a regulation, the more we train our employees to be helpless. We suggest: ‘There is a process for everything.’ But when reality deviates from the process (and it does so more and more often in the VUCA world), employees stand still.

From cage back to shield

Standards are intended as a shield. They are meant to protect. A good standard is like a railing at the edge of a precipice: it marks the boundary so that we can move freely and quickly within the safe area.

But in many companies, the shield becomes a cage. The bars of bureaucracy are so narrow that no movement is possible. The standard no longer serves the work; the work serves the standard. ‘That’s not possible; it’s not part of the process’ becomes the universal excuse for not taking responsibility.

The hard ask: the test for your standards

Take a look at your process landscape. Do your standards serve to enable decisions? Or do they serve to prevent decisions?

If your employees first look for the rule before using common sense in an unforeseen situation, you do not have a secure system. You have a bureaucratic one.

The path to true excellence (Capacity Shift) does not lie in more rules. It lies in clarity. Use standards as solid ground on which to stand – in order to reach for higher things.

Further reading

“Heuristics for Masterbuilders: Fast and Frugal Ways to Become a Better Project Leader”, Bent Flyvbjerg, July 2022

Flyvbjerg warns that too many rules stifle personal responsibility and creativity, and recommends: ‘Don’t make too many rules; most don’t need them; address those who do directly.’

Explore more in The Shift Series

• The Hero Reflex
  Why is everyone looking up? Because the boss (the hero) has always solved it before. If you want to understand why your team is silent, you need to read this article.
• Safety Is Performance: One System, One Maturity
  Why the same standard shapes Safety, Quality and Performance – because only one work system sits underneath them.

Why silence is the loudest warning

The measurement is outside its usual range. Not far enough to stop the line, but far enough to deserve attention.

An operator mentions it during the shift meeting. The manager looks at the production board, then at the clock. “Is it really a problem?”

Nobody tells the operator to be quiet. Nobody needs to.

She changes the sentence. The measurement is probably still acceptable. The team can keep an eye on it. The meeting moves on.

By the next shift, a concern has become an observation. A day later, it is no longer mentioned at all.

This is how organisations lose the truth. Rarely through a formal order. More often through a series of small calculations made by people who have learned what a bad message costs.

Silence is learned

It is easy to blame a quiet team. People should speak up. They should show courage. They should take ownership.

That explanation is comforting because it leaves the system untouched.

People observe what happens when somebody challenges a plan, admits uncertainty or brings a risk into the room. Does the manager become curious? Does the meeting make time? Or does the messenger have to defend the interruption before anyone examines the information?

These reactions teach faster than any value statement.

If raising a concern repeatedly creates irritation, delay or loss of status, silence becomes a competent response to the environment. The operator has not stopped caring about the work. She has learned to protect herself from the organisation around it.

Silence is often an active, calculated choice.

Every organisation has a market for truth

An internal market for truth exists wherever one person holds information that another person needs in order to decide.

The exchange is simple. An employee offers local knowledge. Leadership responds.

The response sets the price for the next exchange.

The price is not measured in money. It may be embarrassment in front of colleagues, being labelled negative or the quiet damage done to a career. Sometimes the cost is smaller: another exhausting discussion with a manager who already knows the answer they want.

When that price stays low, information moves early. A doubtful reading can still be checked. A customer complaint can reveal a process weakness before it becomes a pattern.

When the price rises, information waits. People soften it, route it through trusted colleagues or hold it until evidence becomes impossible to dismiss.

At that point, the organisation does not have an engagement problem. Its market for truth has stopped working.

Leadership sets the exchange rate

Leaders often search for silence in dramatic events: retaliation, public blame or a whistleblower case.

The market usually changes through smaller moments.

A question is answered with a sigh. A concern is described as resistance. The person who reports a delay is asked why they did not protect the schedule. A red indicator triggers an investigation into the reporting discipline before anyone investigates the work.

None of these reactions bans the truth. Together, they make it expensive.

The reverse is equally practical. A leader can ask what the person saw, what remains uncertain and what decision is needed now. They can protect the messenger without treating every message as correct. They can separate the quality of the information from the discomfort it creates.

Psychological Safety begins here. It is not an invitation to be comfortable or agreeable. It reduces interpersonal risk so that the team can address operational risk while options still exist.

Silence has an operating cost

The first cost of silence is delay.

While information waits, reality continues. The unusual vibration develops. A planning assumption hardens into a commitment. A weak supplier signal becomes a missing part on the day production needs it.

Early information is valuable because it creates choices. The team may inspect, adjust or prepare a fallback. Late information arrives after those choices have disappeared.

What remains is usually more expensive: rework, an outage, a customer escalation or a decision made under pressure with incomplete information.

This is the Cost of Silence within the Capacity Tax. The organisation appears to save time by avoiding an uncomfortable conversation. In reality, it finances a later problem at compound interest.

The accounting system will record the repair, delay or lost order. It will not show that the original information was available much earlier and became unusable because speaking was socially expensive.

Green dashboards can hide a broken market

Silence becomes especially dangerous when the numbers look good.

A long period without incidents or a stable quality curve can be evidence of good work. It can also increase the social cost of being the person who changes the colour.

Teams begin to protect the record. Near misses are reclassified. Doubts become private conversations. The dashboard remains calm because the information that could disturb it never enters the system.

This is not an argument against metrics. Numbers help us orient and learn. The mistake is treating a clean result as proof that the organisation can still hear what does not fit the result.

A green dashboard tells you what was recorded. It cannot tell you what people decided not to say.

Voice is not the same as noise

An open market for truth does not mean every opinion is right or every objection stops the work.

Some concerns will prove unfounded. People can misunderstand a situation, defend their own interests or use endless questions to avoid a decision.

Leadership still has to judge. Clear boundaries and technical competence remain necessary. Speaking up provides information; it does not transfer accountability to the loudest person in the room.

Nor does every quiet moment indicate fear. A team may be thinking. People may lack enough context to contribute. Agreement can be genuine.

The test is not whether the room is noisy. It is whether relevant information can contradict authority without the messenger paying a personal price.

Listen to the first response

Culture surveys can reveal patterns, but the internal market is rebuilt in ordinary work.

Start with the next piece of bad news.

Notice your first response before you improve the employee’s communication. Do you defend the plan? Question the timing? Explain why the problem is inconvenient?

Then slow down. Ask what was observed and what remains uncertain. Decide what needs protection now. Return later to the quality of the message if that conversation is still useful.

The order matters. If the messenger must first survive your reaction, the information will arrive later next time.

Leaders do not create voice by asking people to speak. They create it by making truth usable when it appears.

The silence after the meeting

The operator in the shift meeting will remember more than the doubtful measurement.

She will remember whether the room made space for it. Her colleagues will remember too. One response becomes part of the price of every future warning.

That is why silence is the loudest warning. It tells you that local knowledge may still exist, but the organisation can no longer access it in time.

The greatest risk is not disagreement.

It is a system in which people know more than leadership can hear.

Further reading

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

Morrison reviews a decade of research into why employees speak up or withhold work-related information. The article is useful because it treats voice and silence as choices shaped by context, hierarchy and anticipated consequences rather than as fixed personality traits.

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

Across four studies, Detert and Edmondson examine the unwritten beliefs people use when deciding whether speaking up is risky or inappropriate. Their work explains how self-censorship can persist even when leaders formally invite suggestions.

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

Edmondson shows the mechanism between psychological Safety and performance: it supports learning behaviour. This distinction matters here because lower interpersonal risk creates value only when people use it to surface uncertainty and improve the work.

Explore more in The Shift series

The Capacity Tax

How silence, approval loops and dependency turn paid expertise into hidden operating cost.

Counting vs Practicing

Why a reassuring dashboard cannot replace the daily practices that make weak signals visible.

The Hard Ask

What leaders must stop doing if they want other people to think and act without waiting for permission.

Culture Is Not a Cozy Affair

Why productive disagreement is hard operational work rather than a feel-good exercise.

Safety, Quality and Performance begin in the same work

A technician notices an unusual vibration and stops the line.

Production wants to know when it will run again. Maintenance needs access to the drive. Someone from Quality is already checking the material that passed through the machine. Before long, Safety joins the conversation as well.

The organisation has split one event into several professional views. The machine, meanwhile, is still standing in front of everyone.

The vibration does not care which department owns the dashboard. Neither does the work.

One of the more persistent illusions in modern organisations is the idea that Safety, Quality and Performance are separate systems. We give each function its own dashboard and ask its specialists to explain a different part of what happened.

The separation is understandable.

Safety became its own kingdom through regulation. Quality built a court around standards and certification. Operational Excellence arrived later, carrying methods, coloured belts and a language that often made perfect sense inside the programme and much less sense outside it.

The kingdoms developed specialists, rituals and proof that the rituals had taken place. Certificates appeared in the foyer. Charts covered the walls. Meanwhile, the people doing the work became fluent in recognising which version of reality was expected in which meeting.

This architecture can create expertise. It can also hide something fundamental.

The work itself is indivisible.

An unclear handover may first show up as a damaged product. Under slightly different conditions, the same weakness stops the line. If somebody is standing in the wrong place at the wrong moment, it becomes a Safety event. The category appears later, when the organisation decides where to book the consequence.

At the moment of work, there is only one system.

Results are separate. Causes are not.

Imagine the technician raises the concern about the vibration.

What happens next tells you more about the organisation than any culture survey.

Perhaps the supervisor listens. Perhaps he dismisses the concern as excessive caution. The team may be allowed to stop the equipment, or it may need permission from a manager who is sitting in another meeting. What matters is not the formal process on paper. What matters is how the system behaves while the equipment is still vibrating.

These are not questions for Safety alone.

They reveal how information travels and where authority sits. They also show what happens to the person who brings inconvenient news. Expertise either becomes action or joins an approval queue.

That is governance.

Safety is not something added to operations. It is one of the clearest ways to see how operations are governed when the consequences become real.

The same governance shapes quality and performance.

If people hesitate to report a hazardous condition, they are unlikely to become outspoken when the concern is about quality. A technician who cannot stop unsafe work without escalation will face the same hierarchy when defective material is moving through the line. The label on the meeting changes. The price of bringing bad news does not.

The outputs look different. The underlying behaviour does not.

Safety is the lens on governance

When I want to understand an organisation, I do not begin in the boardroom. I go to the line.

I speak with the people who maintain drives, open valves, seal flanges, approve work and keep production moving when the procedure no longer fits the situation perfectly.

That is where the system becomes visible.

I watch whether people warn one another and whether somebody can stop the work without first calculating the personal consequences. I listen to how criticism is received. Some routines help the work. Others come alive only when an auditor approaches.

Above all, I look at movement. Does authority move towards the information, or does the information travel upwards while the problem waits below? When something goes wrong, where does the conversation go first?

These are Safety questions. They are also Quality questions, Reliability questions and Performance questions.

They expose the organisation’s actual operating model.

This distinction matters because Safety figures can look reassuring while the system remains fragile. A low incident rate may reflect good practice. It may also contain a generous portion of luck. Perhaps exposure was low. Perhaps people decided that disturbing the number was not worth the response it would trigger.

Safety metrics are not automatically honest.

Safety as observable practice is.

Watch what happens when a plan meets reality. Follow a weak signal through the organisation and see where it slows down. Then watch the leader’s face when somebody says that the work needs to stop.

There is your culture.

Not on the poster. In the response.

One system. One maturity.

Organisations often speak as if they could be mature in Quality, advanced in Operational Excellence and still have a weak Safety culture.

For a while, the numbers may support that story.

A capable team can compensate for poor governance. Experienced people work around unclear roles. Technicians prevent failures despite slow decisions. Operators protect quality while targets pull in another direction. A few trusted individuals hold the system together through attention, relationships and sheer effort.

That can look like maturity.

Often, it is hidden overburden.

Remove one experienced person. Add time pressure. Introduce an unfamiliar problem. Suddenly the different kingdoms discover that they were relying on the same informal capacity all along.

An organisation does not have one maturity for Safety and another for Performance. Its maturity shows in how people coordinate work under uncertainty.

A dependent system waits for instructions. As it matures, individuals begin to solve more problems within their own areas. That is progress, but it can produce capable islands.

Interdependence goes further. People retain the confidence to act locally while understanding how their decisions affect the wider system. Shared intent connects their judgement across functional boundaries.

The highest level is not autonomy for its own sake. It is interdependence.

This is why Safety and Performance cannot be improved sustainably through separate campaigns. Both depend on the same collective capability to see, speak, decide and learn.

There is only one system and only one kind of maturity.

How the same Capacity creates Safety and Performance

The connection is not inspirational. It is operational.

When people can speak early, the organisation gains time. The strange vibration becomes an inspection instead of a breakdown. A team can correct a doubtful measurement before an entire batch is rejected.

Clear intent keeps more decisions close to the work. The team does not need to send every deviation upwards and wait for authority to return. People know what they are protecting. They also know where their room to act ends.

Expertise can then be used as judgement rather than being reduced to servicing the procedure. Standards remain essential, but they become the floor for good work – not the ceiling of thought.

Leadership response decides whether this information keeps moving. Curiosity makes an early warning worth the social risk. Blame teaches the next person to wait.

Over time, these moments change more than the Safety result. Decisions arrive sooner because fewer of them take a tour through the hierarchy. Quality concerns surface before they become rework. The line becomes more reliable because learning improves the work instead of merely restoring the plan.

What appears to be Safety is Excellence in motion.

Not because every safe act immediately increases output. Not because trade-offs never occur. A necessary stop can cost production today.

A mature system recognises when work needs to stop and makes the decision while it still has options. The alternative is to keep moving until reality decides instead.

The short-term number may fall. The long-term capability rises.

When separate programmes simulate maturity

The three kingdoms become dangerous when each begins to protect its own proof of success.

Safety improves reporting compliance while Quality works on complaints. Production keeps pushing output. Each dashboard can move in the desired direction even though the frontline still receives conflicting instructions.

Do not stop the line, but never compromise Safety. Follow the standard, unless the customer needs something else. Decide faster, although uncertainty must still be escalated. Take ownership after obtaining approval.

The contradiction is not solved. It is delegated to the people doing the work.

People learn to translate between programmes. They service the reporting demands and work out for themselves which target matters today. Management sees control. The frontline experiences friction.

This friction carries a cost.

It appears as another approval. Later, more time is spent aligning the story after the fact.

The organisation pays people for judgement, then consumes their time administering the boundaries between its own functions.

That is part of the Capacity Tax.

The answer is not to remove specialist expertise. Safety, Quality and Operational Excellence professionals contribute knowledge that the system needs.

The answer is to stop treating their disciplines as competing operating systems.

Experts should strengthen one shared system of work. That requires common intent and boundaries that do not contradict one another. Decision rights must fit the reality of the work, while learning has to travel beyond the function where the organisation recorded the event.

The organisation does not need three versions of reality. It needs enough shared language to act on one.

Five questions for your next walk to the line

You do not need another culture programme to begin this diagnosis.

Ask about the last time somebody stopped the work.

What did they notice? Who decided? How did leadership respond? What changed afterwards?

Ask for the last piece of bad news that travelled upwards early.

Was the person thanked, challenged or quietly marked as difficult?

Ask where work is currently waiting for a decision.

Does authority sit with the person who has the best context, or somewhere higher in the hierarchy?

Ask which rule people work around to get the job done.

Is the workaround reckless, or is it evidence that the standard no longer fits reality?

Ask what Safety, Quality and Production are trying to improve this month.

Can the team explain how the objectives support one another, or are people left to negotiate the conflict during the shift?

Do not use the questions as an audit.

Use them to understand the system.

The quality of the answers matters. The speed with which people are willing to give them matters even more.

What the system reveals

Safety is not the brake pedal. Nor is it a separate engine attached to the business.

It is a lens.

It shows how the organisation behaves when plans meet uncertainty and consequences become real. Follow the information. See whether judgement is trusted and what the organisation does with a deviation after the immediate problem has passed.

Read that practice carefully and you will see more than risk.

You will see the maturity of the entire work system.

The same Capacity creates Safety and Performance.

Further reading

“Understanding Safety Culture Through Models and Metaphors” by Frank W. Guldenmund, in Safety Cultures, Safety Models, 2018

Guldenmund examines how different models and metaphors shape our understanding of Safety Culture. The chapter is useful here because it moves the discussion away from a programme or checklist and towards the deeper social patterns through which work is interpreted and carried out.

Understanding Safety Culture, Queensland Department of Justice and Attorney-General, 2013

This practical guide connects Safety performance with leadership, communication, reporting and organisational behaviour. It provides a useful foundation for examining Safety not as an isolated compliance activity, but as evidence of how the wider system operates.

Explore more in The Shift series

The Capacity Tax: The Hidden Cost of Control

How silence, approval loops, rigidity and dependency convert paid expertise into delay, rework and hidden operating cost.

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?

How standards protect people and performance when they remain a floor for judgement rather than a ceiling on thought.

Dashboards calm nerves. They don’t change work.

The Comfortable Lie of Measurability

Walk into almost any management review and the script is predictable: Lights dim. Screen flickers. Dashboards march across the wall. Green, yellow, red. Executives nod. Everyone feels informed. Everyone feels in control.

But that comfort is deceptive. Because dashboards show outcomes, they don’t shape the behaviors that create them.

Behind every perfect chart sits a messy, human system: people who hesitate, teams that stay silent, leaders who look at numbers instead of listening to conversations.

And that’s the trap: we confuse counting effects with creating causes.

The Meeting That Taught Me the Difference

Years ago, I visited a plant that proudly showcased its dashboards. Everything was tracked. Everything was color-coded. Compliance was immaculate.

But as I walked the site, I saw the real story: empty earplug dispensers, ashtrays in non-smoking zones, handrails so dusty they hadn’t been touched in weeks.

The charts were green. The culture was not.

What struck me most was the gap: the numbers told one truth, the workplace told another.

When I mentioned this to the plant manager, he said: “Weren’t you here to review Lean? Shouldn’t you focus on performance?”

I shook my head. “This is performance. When basics are ignored in safety, they’re ignored everywhere.”

That moment crystallized something I had sensed for years: Dashboards don’t improve work. Practices do.

Why Counting Creates Blind Spots

1. Dashboards measure what’s easy, not what matters

Near-miss reports, audits completed, safety talks held. All countable. None a guarantee that people actually feel safe to speak up.

2. Numbers give the illusion of precision

A percentage feels objective. A conversation feels subjective. But in culture work, that equation is reversed.

3. When the number becomes the target, truth gets distorted

Reporting delays. Reclassification. Selective visibility. Not out of malice, out of survival. Goodhart’s Law in action: When a measure becomes a target, it ceases to be a good measure.

4. Silence becomes strategy

When leaders celebrate “Zero,” teams protect the number, not the learning.

What Actually Changes Work

Culture doesn’t shift because numbers improve. Numbers improve because culture shifts. What changes work is not counting:

• the pause before a high-risk job
• the courage to surface a weak signal
• the conversation after something almost went wrong
• the decision to stop instead of push
• the leader who listens before acting

None of these show up cleanly on a dashboard. But all of them change tomorrow.

That’s the essence of the Capacity Shift: moving from proving performance to practicing the behaviors that create it.

Counting vs Practicing – Why This Matters

If leaders want cultural maturity, they must stop confusing what is visible with what is real. Dashboards will always have their place, for orientation, not for truth.

The real indicators of culture are audible, not countable: in what people say, in what they hesitate to say, and in whether the system makes learning safe.

That’s how you flip the curve: from measuring absence to cultivating presence, from counting to practicing.

Further reading

„Don’t Let Metrics Undermine Your Business“ by Michael Harris and Bill Tayler (HBR (September–October 2019)

The article shows how organizations fall into the so-called surrogation trap, i.e., confusing strategy with the metrics they are supposed to measure. In other words, how well-intentioned metrics can destroy the actual intention: people optimize the number, not the purpose. The article explains why this happens structurally and how teams start working on the metric score instead of the behavior that the score is supposed to represent.

„Goodhart’s Law, Campbell’s Law, and the Cobra Effect.“ on psychsafety.com (July 19, 2024)

The article shows in a simple way why metrics become dangerous as soon as they are made into targets: people optimize the number instead of the behavior, and that is precisely why counting is not enough to generate real learning, maturity, or quality.

Explore more in The Shift Series

• The Hero Reflex
  Why people act—or stop acting—when leadership is too present.
• Counting vs Practicing
  Why does the same culture that prevents accidents also improve quality and performance.

The Internal Market for Truth

A dashboard cannot reveal the information people decided was too costly to share.

When the leader becomes the bottleneck

It was one of my first days in charge of the department when the phone rang.

The shift leader reported smoke in one of our main control rooms. It might be a fire.

“What shall I do?” he asked.

Adrenaline took over. This was what leadership was for: assess the situation, decide and give clear instructions. I did exactly that. Before ending the call, I told him I would be there in fifteen minutes.

When I arrived, the incident was already under control. A light fitting had started to smoulder. Nobody was hurt. Production had not stopped.

I felt relieved and, if I am honest, proud. I had passed my first test under pressure.

Only later did the question become uncomfortable.

Why had this man called me before acting? He was a highly experienced shift leader. Outside work, he commanded his local volunteer fire brigade. In that situation, he had more relevant competence than I did.

He did not need my judgement. He needed my permission.

And by answering immediately, I confirmed that he had been right to wait for it.

A correct answer can still damage the system

My instructions were not necessarily wrong. That is what makes the Hero Reflex difficult to recognise.

The Hero does not usually enter because everybody else is incapable. The Hero enters because intervention works. A decision is made, uncertainty drops and the organisation moves again.

The immediate result rewards the leader. It also teaches the team.

The next time something unusual happens, people escalate a little earlier. They bring less of their own judgement because the decisive judgement will arrive from above. The leader sees more questions coming upward and concludes that the team still needs close guidance.

The loop feeds itself.

Each rescue makes the next rescue more likely. What began as a useful intervention becomes an operating model built around one person’s availability.

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

The bottleneck that looks like a strength

Organisations often reward this pattern.

The leader is responsive. Important issues land on their desk. They know the details and can remove obstacles quickly. During a crisis, everybody knows whom to call.

From the outside, this looks like control.

Inside the system, work is forming a queue.

Information moves upward to authority. Decisions travel back down. Meetings wait for the senior person, projects slow when they are unavailable and capable people learn to prepare recommendations for approval instead of decisions for action.

The leader becomes the most expensive bottleneck in the organisation. Their competence has not disappeared. It has been placed where it limits the use of everybody else’s competence.

This is part of the Capacity Tax. The organisation pays for expertise across the system but routes judgement through a single constrained point.

The cost is not only delay. Repeated intervention trains dependency. People stop exercising the decision muscles the organisation later complains they do not have.

Why the reflex feels so good

The Hero Reflex is rarely driven by bad intent.

Sometimes it comes from responsibility. A leader knows that the consequences will carry their name, so taking control feels safer than trusting an uncertain process.

Sometimes speed is the attraction. Giving the answer is faster than allowing somebody else to work through the problem.

There can also be status in being needed. Solving the difficult issue confirms the identity on which a successful career was built. The engineer who always knew the machine becomes the manager who still knows the machine, only now every problem across the department can reach them.

None of this requires vanity. Competence itself can become the trap.

The behaviour that earned the leadership role may be exactly what prevents the system from growing beyond the leader.

Not every intervention is a mistake

Letting go is not a principle to apply blindly.

If life is in immediate danger, boundaries have been crossed or the team lacks essential competence, a leader may need to intervene directly. In a genuine emergency, clarity and speed matter.

The fire call was not the moment for a long coaching conversation.

But that does not end the analysis. A necessary intervention today can still reveal a governance weakness that must be repaired tomorrow.

The question is not simply, “Should I step in?” It is also, “Why does this decision need me, and what must change before the next one?”

A mature leader distinguishes the emergency from the dependency the emergency exposes.

From Hero to Host

The opposite of the Hero is not an absent leader.

The Host creates the conditions in which other people can act responsibly. They make the intent clear, protect non-negotiable boundaries and ensure that authority sits close enough to the information.

When a problem arrives, the Host does not automatically provide the missing answer. They first ask what the other person sees and what they intend to do.

This changes more than the conversation. It changes who is expected to think.

Imagine the fire call again. The shift leader reports smoke. Instead of beginning with instructions, I ask: “What is your assessment, and what action are you taking now?”

If his response respects the boundary, I confirm the action and offer support. If the boundary is unclear, we clarify it. If immediate danger demands command, I command.

The Host does not surrender accountability. The Host stops confusing accountability with making every decision personally.

Move authority before the crisis

Distributed judgement cannot be improvised during an emergency.

People need to know what the organisation is protecting and which limits must never be crossed. Decision rights must be explicit enough to survive pressure. Competence has to be built and tested in ordinary work.

Most importantly, leaders must back responsible decisions after the fact. Authority on paper disappears quickly when the first unpopular decision is punished.

This work happens before the phone rings.

If the only person who understands the intent is the leader, the team will wait. If every exception requires approval, the leader has not delegated authority. They have delegated preparation.

Capacity grows when people repeatedly make real decisions within clear boundaries and learn from the result.

The pause that changes the loop

The Hero Reflex moves fast. Interrupting it requires a small pause.

Before giving the answer, ask yourself whether the situation truly requires your authority or merely triggers your desire to be useful.

Then ask the other person for their assessment and intended action. Listen for the missing element. Is it competence, clarity about the boundary or confidence that the decision will be supported?

Respond to that gap instead of taking the whole problem back.

Sometimes you will still decide. Sometimes you will stop the work. The difference is that the intervention becomes deliberate rather than automatic.

Afterwards, examine what the system learned. Can the next comparable decision happen closer to the information? If not, the rescue is incomplete.

What remains when you leave?

On the day of the control-room incident, the technical problem ended well.

The leadership problem did not.

I had shown that I was available and decisive. I had also reinforced a system in which a more qualified person waited for me before using his judgement.

The real test of leadership is not how many problems move when you enter the room. It is what the system can handle when you are no longer there.

Kill the Hero does not mean abandoning the team.

It means building a system that does not need to be rescued from its own dependence.

Further reading

“Self-Management as a Substitute for Leadership” by Charles C. Manz and Henry P. Sims Jr.

Manz and Sims describe self-management as a capability leaders can deliberately develop. Their work is useful here because it shifts attention from delegation as a single decision to the practices through which people learn to direct and evaluate their own work.

“Two Faces of Empowering Leadership: Enabling and Burdening” by Minyoung Cheong, Seth M. Spain, Francis J. Yammarino and Seokhwa Yun

This study is an important guardrail against romanticising empowerment. More autonomy can enable performance, but it can also create strain when responsibility is transferred without sufficient support. Host leadership needs clarity and capability, not withdrawal.

“Following the Chain of Command?” by Floor Rink and colleagues

The study examines how managers balance the benefits of local knowledge against perceived loss of control when granting autonomy. It supports a central practical point: authority is more likely to move when leaders trust competence and when the surrounding system also grants them room to delegate.

Explore more in The Shift series

The Hard Ask

Why not giving the quick answer is one of the most demanding leadership practices.

Flip the Curve

How authority moves towards information as an organisation develops Capacity.

The Capacity Tax

How bottlenecks and dependency turn capable people into an expensive waiting line.