FROM THE FIELD

Close-up, low-angle view of a utility truck’s outrigger pad resting on a wet dirt road shoulder after rain. The mud has cracked along the front edge of the pad, and a thin stream of water is seeping out from underneath. A second outrigger, the truck’s rear tires, and a wet two-lane road fade into the background under a gray, overcast sky, with fallen leaves along the shoulder.

Back in February I told you about an apprentice who saw a bucket truck sitting with a slight lean. The outriggers weren't all the way out. He knew something was off. He ran it through his head. Would they think he was overreacting? Would they remember it the next time he spoke up?

He stayed quiet. The truck shifted with a man in the bucket.

I've thought about that kid a lot this year. Not because he did something wrong. Because he did exactly what most new people do. He read the crew, figured out what speaking up would cost him, and decided it cost too much.

This week is the other version. Same kind of truck. Same kind of kid. This time he says it.

But here's what I need you to see. The most important part of this story isn't what the apprentice says. It's what his foreman says the next morning.

Because people repeat what gets recognized. Every crew is running a recognition program right now, whether anybody named it or not. Most leaders just don't know what theirs is rewarding.

Incident Breakdown

This one's a composite. I built it from setups and mornings I've watched play out on crews over the years. The crew is put together. The ground, the pad, and what happened at the next tailboard are real, and some version of it happens every fall.

THE MOMENT

It's the first job after the first real rain of the season.

The crew is setting a replacement pole on the shoulder of a county road. Digger derrick on the shoulder, pads down, outriggers out, truck level. The ground had been hard as concrete all summer.

The foreman got promoted in the spring. This is his first fall running his own crew. He's got a journeyman with more than twenty years in, an operator, and an apprentice who's been on the crew for three weeks.

The tailboard was solid. The pick, the clearances, traffic control, the hole. Everybody signed. Nobody walked the ground under the curbside outrigger a second time. It looked like it always looked.

The pole is in the air. The apprentice is on the tag line. The journeyman is watching the butt and the hole. The operator is watching the boom and the pole.

The apprentice glances back at the truck and sees it. The curbside pad is sitting crooked. There's a fresh crack in the dirt along one edge, and a little water squeezing up out of it.

He looks at the journeyman. Eyes on the hole. He looks at the operator. Eyes on the boom. Nobody else sees it.

Three weeks in. He does the math every new person does. What if I'm wrong? What if it's nothing and I just stopped a pick on a road shoulder in front of everybody?

Then he says it.

"Hey. That pad's moving."

Not loud. Just loud enough.

The foreman calls all stop. The operator holds, then sets the pole back down. They walk over to the curbside outrigger.

The pad had settled into the shoulder. Under it was old trench backfill, softened by the night's rain.

Here's the part that matters. It wasn't sinking the way the kid thought. It had settled about an inch and stopped. The truck wasn't going over.

But it was sitting on ground nobody had checked twice, and it needed bigger cribbing before the next pick. So they re-cribbed, reset the truck, re-leveled, talked it through, and finished the set. It cost them about forty minutes.

At the truck, the foreman turns to the apprentice.

"You weren't a hundred percent right. It doesn't matter. You saw something change and you said something. That's the job."

The next morning, at the tailboard, in front of everybody, he says it again.

"Yesterday, during the pick, he saw the curbside pad move and called it. Turned out to be an inch of settling on old backfill. I don't care. That's exactly the call I want on this crew. If you see something change, say it. I'll stop every time. And starting today, after rain, we walk the outriggers again before the first pick."

That's it. Thirty seconds.

Two weeks later, on a setup the journeyman would normally wave through, he stops and says, "Humor me. Let's walk the outriggers again." A transfer in his first week asks a question about the grounding plan that he'd normally have kept to himself.

Nobody gave a speech about culture. Nobody rolled out a program. The foreman said one thing out loud at one tailboard.

THE MISS

There are two misses in this story. One almost happened. The other is the one I see on crews every week.

The first miss is the ground. The tailboard was written for summer. The first rain changed the ground under the truck, and nobody named it. Conditions changed after the brief, the same way they did in The Trail Was Gone by Morning and in Zobayan's cockpit last week. Ground is a living thing. It doesn't care what it was in August.

The second miss is what usually happens after a call like that. It wasn't made on this crew. But I want you to see how close it came.

The foreman felt the pull too. A road shoulder, flaggers out, traffic backing up, a pole in the air, and it turns out to be an inch. The easy move is "good eye" over his shoulder and back to work. Or worse, somebody laughs. "Easy, rookie. It's not going anywhere."

Either way, the call disappears.

And here's what the kid learns from that. Next time, wait until you're sure.

Here's what the rest of the crew learns. They're all watching how the new guy gets treated. That's how every one of us figured out what counts on a crew. Not from the safety manual. From what got said at the truck.

"Nice, you guys knocked that out fast." Everybody hears that one. Nobody hears "good call on the pad."

New people at every level are reading the crew from the first day. The new apprentice is learning what's safe to say. The new foreman is learning what to do when somebody says it. If nobody names the good call, both of them learn the wrong lesson.

That's the miss I see the most. Not ignoring the call. Letting it disappear.

THE FIX

Recognize the call, not the outcome.

This is the hard one, and it's why I built this story around a kid who was only half right.

If you only recognize the calls that turn out to be right, your crew will wait until they're sure. Out here, sure usually shows up late. If that pad had actually been sinking, waiting until he was sure means the truck is already moving with a pole in the air.

The apprentice wasn't right about how bad it was. He was right that something changed. That's the part you recognize.

Say it in public, at the next tailboard.

The shout-out at the truck was for the apprentice. The one at the tailboard was for everybody else. The journeyman heard it. The transfer heard it. The operator heard it. That's who you're really talking to. You're telling the whole crew what counts here.

Name what changed.

"After rain, we walk the outriggers again before the first pick." That one sentence proves the call mattered. It wasn't a pat on the head. It changed how the crew works. When people see their call change something, they make the next one.

In February I wrote that stop-work authority isn't proven when someone uses it once. It's proven when they use it a second time, because the second time means they trusted what happened the first time.

The journeyman asking to walk the outriggers two weeks later? That's the second time. The foreman bought it with thirty seconds at a tailboard.

Quick Field Note

What a call like this usually gets: "Good catch." Then back to work.

What it got on this crew: "Yesterday he saw the pad move and called it. It was an inch. I don't care. That's the call I want."

The first one is for the person. The second one is for the crew.

Toolbox Deep Dive

THE FIRST FIVE SECONDS

You don't need a recognition program. You need thirty seconds at the tailboard and the discipline to do it every day. I call it the Shout-Out. Three parts. Run it with AAA.

ASK. Who said something out loud? Before the tailboard, ask yourself one question. Who on this crew said something yesterday that made us safer? A stop. A question. A "humor me." A new guy asking what something is. Keep a pocket notebook and write it down when it happens, because by tomorrow morning you'll have forgotten.

Field script: "Before we start, who saw something yesterday that we should talk about?"

ADAPT. Build the shout-out. Three parts, every time.

  1. Name the person. Out loud. By name.

  2. Name what they saw and said. Specific. Not "good job," but "you saw the pad move during the pick and called it."

  3. Name what it changed. What we do now because of it. If nothing changed, say what we learned.

If they were only partly right, say so, and say it doesn't matter. That's the most important line on the card.

Field script: "It turned out to be smaller than we thought. I don't care. That's exactly the call I want."

ACT. Say it where the crew can hear it, and send it up. Say it at the next tailboard, within a day. Then tell one level up. When a general foreman or a supervisor hears a name and calls the apprentice out by name on the next site visit, that kid will never stay quiet again. Neither will anybody watching.

Field script for the GF or supervisor: "I heard you called the pad on the pole set last week. Good call. Keep doing it."

Who can give one: anybody. The foreman, the journeyman, the GF, the safety guy. And the apprentice can recognize the journeyman. Some of the best shout-outs I've heard came from the newest person on the crew.

What kills it, every time:

  • "Good job today, guys." Recognition nobody can repeat is recognition nobody learns from.

  • Only recognizing the calls that turned out to be right

  • Laughing it off. "Easy, rookie." Even when it's a joke, the crew hears the lesson.

  • Waiting a week. By then it's a memory, not a standard.

  • Turning it into a big ceremony that embarrasses a new hand. Short and factual beats loud.

  • Prizes for "zero incidents." If you pay people for nothing going wrong, you teach them not to report what almost did.

The rule: Every tailboard, one name. If you can't come up with one, either you aren't looking, or your crew has stopped talking.

Get the Recognition Playbook and the Shout-Out Card, free. 👇

The Recognition Kit: A Playbook and a Pocket Card for Naming the Good Call
The Recognition Kit: A Playbook and a Pocket Card for Naming the Good Call
Ten ways to recognize the people who name risks, and a thirty-second shout-out for the tailboard. Recognize the call, not the outcome. Letter and 4x6 pocket versions.
$0.00 usd

Leadership Reflection

For Field Leaders (on the crew): Tomorrow morning, name one person at the tailboard for something they said out loud. Then think about the last time a new hand called something that turned out to be nothing. What did you say? What did your face say? That moment taught your whole crew a lesson. Make sure it was the one you meant to teach.

For Supervisors (in your programs): If you're new in the role, your crews are watching for one thing: what you do the first time somebody stops a job on your watch. Get that one right and you'll hear about problems early for years. When you visit a crew this week, don't ask "how's production?" first. Ask "who spoke up this week?" Then go find that person and say their name. Look at what gets recognized in your crew meetings and weekly reports. If it's footage, poles set, and days without an incident, that's what you're going to get more of.

For Executives (at the system level): Look hard at what your recognition system rewards. Safety bonuses tied to "zero recordables" can teach crews to keep quiet about the near miss. Recognize the reports, the stops, and the good catches instead, and count them. When good-catch numbers go up, don't panic. The research on this goes back thirty years: well-led teams report more problems, not fewer, because they feel safe saying them out loud. A crew that names more isn't less safe. It's the one you can see.

❝

“If you only recognize the calls that turn out right, your crew will wait until they're sure. Out here, sure usually shows up late."

Lito Wilkins

Tailboard Challenge 

At your next tailboard, before the gear goes on, ask one question out loud:

"Who said something last week that made us safer?"

Then name them. Out loud. By name. What they saw, what they said, and what it changed.

Then reply to this email and tell me who you named. I read every one.

Bring this to your crews

Your crews already know what your company recognizes. They learned it at the truck. The question is whether your leaders know.

I sit down with your supervisors and foremen and walk through what actually happens after someone on your crews speaks up. The first five seconds. The next tailboard. What gets recognized, and what goes up the chain. We find where the good calls go to disappear, and we fix it, using your crews and the work they're doing right now.

Reply to this email with the word AFTER and I'll send you how it works and my open dates.

Or go straight here: [Book a Name It Stand-Down →]

Quick Question. One Click.

Read Next

Three from the archive that belong next to this one:

Want to build a culture where every worker goes home safe?

Let's talk. Reply to this email, or visit www.leadingsafelineworkers.com to book a keynote, training, or consultation. Because safety isn't a program. It's a leadership decision.

Share this with someone who needs it.

Forward this to a foreman, a safety manager, or a crew member who's trying to lead better. Let's build this together.

P.S. I'm booking 2027 safety kickoffs, stand-downs, and leadership sessions now. If you're building next year's plan this month, reply and I'll hold a date while you get approval.

Until next time,Lito Wilkins