The executive conversation

“A few weeks ago, I spent an afternoon with a couple of your engineers on one of your sites.”

That line alone got their attention.

“The engineers showed me around. Things looked good. Clean, well-lit, tidy, secure. A poster site for reliability, engineering precision, and control.”

The executives started to relax.

Then I told them I'd met ten of their colleagues over pizza in the training room, and asked: “can you tell me about when your work here is difficult?”

Everyone sat up straight again.

“Within fifteen minutes, those engineers told me, in unison, what and when they believed the next accident was going to be.”

You could hear a pin drop.

Before I moved into the day's agenda I said: “Your engineers told me it'll be a Monday morning. It'll involve a contractor visiting the site. And they won't be there to support and supervise.”

A couple of the executives nodded thoughtfully. Then we spoke about safety for 3 hours.

The above scene happened just a few weeks ago. And it contains something on multiple levels that is worth sitting with. The site looked safe. The metrics presumably looked fine. And then ten engineers, asked a simple question over pizza, could describe the next incident with a specificity that no dashboard had produced.

The gap between those two things, what the organisation looks like and what the people inside it actually know, is where many if not most executive safety conversations never go.

And I think the reason is how executives are typically brought into safety. Usually through one of two doors. The legal door: here are your obligations, here is your liability. Or the technical door: here are the regulations, the standards, the compliance requirements. Both are real and worth knowing. But neither produces the conversation that happened in that training room.

Both approaches treat safety as a domain. A specialised field with its own language, its own professionals, its own metrics. When safety is a domain, executives are expected to govern it from a distance. They ask how safety is going. They receive a report. They note the numbers. And they remain, in most cases, genuinely disconnected from what their people actually know.

That's a missed opportunity.

What those executives got was a different question. Not "how's safety going?" but something closer to: what do your people know that your systems don't?

Because safety, when you approach it this way, stops being a domain to manage and becomes a lens into how the organisation is actually functioning. It reveals where work is fragile, where decisions are unclear, where people are absorbing pressure the system doesn't officially know it's creating.

The engineers knew this. They were clear about the specific conditions, the specific time of the week, the specific gap in supervision that made an incident likely. That knowledge existed. It just had no channel to reach the people with the authority to act on it. Distance, geographical and structural, had done its work.

The executive safety conversation isn't about making leaders into safety experts or scaring them into action. Or at least I think there is a better opportunity. One that’s about closing that distance that turns safety into numbers and a problem to manage from afar. It’s a type of conversation that makes safety real and consequential, because it surfaces what the system isn't telling them. It treats safety as a conversation worth having. One that starts, usually, with how work is actually going rather than whether hazards and controls are in order. With stories from their own frontline.

That question, asked with genuine curiosity and followed by genuine silence, tends to go somewhere. As it did in that boardroom, and in the training room over pizza, without anyone opening a slide deck.

Daniel