SAFETY COACHINTERNATIONAL← Back to insights

Insights

Telling vs coaching

5 min read

Walk any high-hazard site and you'll hear it. A supervisor spots something. A missing step, a shortcut, a bit of rushing. And they do what feels responsible. They tell. "You need to follow the procedure. Slow down. That shortcut's going to get someone hurt one day."

It's fast. It's clear. And most of the time it changes nothing. The worker nods, waits for you to move on, and goes back to doing the job the way the job actually gets done. You corrected the moment. You didn't change anything underneath it.

This is the quiet ceiling on a lot of safety leadership. It isn't a lack of care. The telling comes from exactly the right instinct. It's that telling, as a tool, can only do so much. And the thing that breaks through the ceiling isn't a new programme or a tighter rule. It's a change in how the conversation works.

What telling can and can't do

Telling has a job. When someone is about to touch live equipment before the isolation is finished, you don't ask a thoughtful question. You step in, direct and immediate, because a question won't stop a hand in time. In a safety-critical moment, direction is the only responsible response.

So the mistake isn't telling. The mistake is telling as your default. Reaching for it in every conversation, including the ones where it gets in the way.

Most field conversations aren't the live-equipment moment. Most of the time you're talking to someone who already knows the task. Someone who has a reason for the workaround you just spotted. Someone who understands the conditions better than the procedure does. Tell that person what to do and you get compliance while you're watching, plus a worker who's learned there's no point explaining what really goes on. You closed the conversation at the exact moment it had something to teach you.

The difference is who does the thinking

Here's the cleanest way to see it. When you tell, you do the thinking and hand over the answer. When you coach, you help the other person do the thinking and reach their own.

That sounds like a small distinction. On the ground it changes everything. A worker who reasons their way to why a step matters will do it when no one is watching. A worker who was told will do it while you're there. One builds capability that stays. The other buys compliance that leaves when you do.

Coaching isn't a technique you bolt on. It's a different way of showing up in the conversation. Non-directive, genuinely curious, built on the belief that the person in front of you is capable even when they're struggling. It runs on a small set of learnable tools. Open questions that can't be answered yes or no. Listening without an agenda. Reflecting back what you heard. And the one that surprises everyone, silence. Most leaders fill silence without thinking. Learning to wait six seconds after a question, instead of rushing to answer it yourself, is often where the real thinking starts.

None of this needs a qualification or a formal session. It happens in the conversations you're already having.

Three hats, not one

The useful frame isn't "stop telling and start coaching." It's that you wear three hats, and the skill is knowing which one to reach for.

There's the manager, who directs, sets the expectation, and takes action. There's the mentor, who shares experience: "when I was in a similar spot, here's what I did." And there's the coach, who asks questions and helps the person work it out for themselves. Every safety leader moves between all three. None of them is always right.

The trouble is that under time pressure almost everyone defaults to the manager's hat. A culture that expects leaders to respond fast and direct makes it feel wrong to slow down and ask. So the manager's hat gets worn for conversations that needed the coach's. The worker who came to you with a real problem gets a quick instruction instead of a question, and learns not to bring you the next one.

Reading the situation is the actual craft. New worker who lacks the knowledge? Instruct, or support. Immediate hazard? Instruct, now. But a worker who already understands the task and just made a call you want to explore? That's where a question builds something an instruction never will.

What this looks like on Monday

You don't need to overhaul how you lead. You need to add one move to your range.

Pick one conversation a week where your instinct is to tell, and ask instead. Not a soft question, a real one. Instead of "you need to follow the procedure exactly," try "walk me through how this job actually goes, and where the procedure fits and where it gets in the way." Instead of "don't make that mistake again," try "what was going through your mind at the time?" Then wait. Let the silence do its work.

You'll notice two things. First, how much you learn about how the work really happens, the adaptations and the pressures and the reasons, that you'd never have heard while you were talking. Second, the worker starts to engage differently, because for once the conversation treated them as someone worth hearing rather than someone to correct.

That's the whole shift. Telling manages the moment in front of you. Coaching builds the judgement that works when you're not there. Safety leadership has always needed both. But the one most leaders are short on isn't the telling. Safer work starts with better conversations, and better conversations start with a question.