COO's / Operations leader's view

Because every layer it passes through has a reason to soften it. The frontline knows first; supervisors patch locally because escalation reads as failure; middle managers aggregate problems into averages. The lag between floor knowledge and dashboard visibility is not an IT problem — it is a courage problem, and it closes when the cost of escalating early drops below the cost of sitting on it.

They are the same culture measured differently. A site where people hesitate to report near-misses is a site where people hesitate to challenge anything. Under-reporting of near-misses relative to incidents is the clearest operational symptom of a courage gap — and building the Four Steps of Courage (Step Up, Step In, Step Forward, Step Together) raises reporting because it changes the calculation, not the poster.

Because CI systems assume people will name real problems, and the culture quietly prices that too high. When kaizen boards fill with safe suggestions while real issues stay in the break room, the mechanism is intact and the courage is missing. Restoring it means leaders visibly rewarding the first person to raise an uncomfortable problem — and courage practice that makes raising it a norm.

It compounds: near-misses that become incidents, workarounds that become quality escapes, escalations that arrive after options have narrowed, improvement ideas that never surface. McKinsey’s organisational health research links top-quartile leadership environments to roughly three times the long-run performance of the bottom quartile — in operations, the mechanism is simply earlier truth.

Two lenses combined: the Organisational Courage Audit (systemic diagnostic across the Four Steps, site-scoped, benchmarked against the Courage Index) triangulated with your own operational signals — near-miss reporting rates, time-to-escalation on significant events, tier-meeting problem-surfacing rates, and the spread between anonymous and attributed reporting.

A one-day, in-person workshop (8–24 participants) for the operations leadership team, run as a circuit through the Four Steps of Courage on your real operational material: the chronic problem everyone works around, the escalation that came too late, the site nobody wants to name. Each leader leaves with four commitments; the team leaves with a shared Courage Map and an escalation norm.

The one-day Catalyst is for the leadership tier; below that, the practice is designed to ride existing rhythms — tiered meetings, huddles, gemba walks — rather than adding sessions. Team Courage Sprint cohorts for site and shift leadership run in 90-day cycles with facilitated sessions slotted into the meeting structure you already operate.

Behavioural safety trains observation and hazard recognition; courage work trains declaration and escalation — saying the thing once you have seen it, especially when it is inconvenient. The two are complementary: your safety programme supplies the eyes; the Four Steps supply the voice. Sites typically see the effect first in near-miss reporting volume and quality.

Yes — that is the recommended design. Baseline two comparable sites on the audit plus your operational speak-up indicators; run the Catalyst and a sprint cycle on one; compare movement at 90 days. Courage work is behavioural infrastructure, and it should be held to the same evidence standard as any other operational investment.

Three moves: pull your near-miss-to-incident ratio and time-to-escalation on the last five significant events (your baseline is probably already in the data); commission the site-scoped Organisational Courage Audit; and run the one-day Courage Catalyst with your operations leadership team, anchored to the real events those numbers describe.