Author: Torsten Dederichs

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.

The Paradox of Control

Control feels safe. It creates order, predictability, and the comfort of being “on top of things.” That’s why most organizations build layers of procedures, approvals, and reports. It looks like discipline. It feels like leadership.

Until something unexpected happens.

Then you see the real effect of control: people stop acting. They wait for permission, hesitate to decide, or look upward instead of outward. What was meant to create safety starts producing silence.

That’s what I once experienced in a power plant — a highly competent shift leader called me to ask, “What shall I do?” He was a volunteer fire brigade commander in his hometown. He didn’t need my answer. He needed clarity and our system hadn’t given it to him.

What Control Builds and What It Breaks

Control builds stability, but it breaks maturity. It keeps things predictable but prevents people from learning how to adapt.

When authority becomes too present, even competence becomes conditional. People stop owning problems. They start managing impressions. The organization looks orderly from the outside — and hollow from within.

That’s the hidden cost of control: every layer added to reduce uncertainty also reduces agency.

What Clarity Does Differently

Clarity doesn’t mean chaos. It means knowing what matters, what’s off-limits, and who decides what.

It’s the invisible architecture that lets people move confidently even when the leader isn’t there. Clarity scales; control doesn’t.

When intent, boundaries, and decision rights are visible, teams act faster, safer, and smarter. They don’t need constant approval because they understand the frame.

That’s the Capacity Shift: from managing by control to leading through clarity. From preventing mistakes to enabling good judgment. From procedures that enforce compliance to principles that invite ownership.

Flip the Curve: Why This Matters

In complex systems — power plants, hospitals, ships, or teams under pressure — control will always reach its limits. You can’t command agility. You can only create the conditions where people can act with confidence.

Flipping the curve means seeing leadership not as steering from the center, but as shaping the space where others can move — safely, decisively, together.

That’s how capacity grows. Not by counting how tightly we hold on, but by noticing how freely people step up when we let go.

Further reading

“Letting Go” by Timothy W. Firnstahl (HBR September 1986)

Firnstahl describes how painful it is to relinquish control. Not for the system, but for one’s own ego. His candor reveals why control stabilizes us, but never allows us to grow. It is a timeless look behind the scenes of letting go.

“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.
• Counting vs Practicing
  Why numbers often seem calmer than they are and why culture always becomes visible in conversation.