The trail we'd been standing on at 2 AM was buried under trees by sunrise.

I want to tell you how we weren't standing on it when they came down, because the answer has nothing to do with luck and everything to do with what a crew is built out of.

Around 2014. Northern California. A 60kV circuit was out in the mountains and we were patrolling it on foot in the middle of the night.

The storm hadn't let up. The wind was still blowing hard enough that you had to lean into it. We'd hiked a long way in, flashlights on the structures, looking for the problem.

I was a journeyman on that crew. Not the foreman. Just one of the guys with a light.

Somewhere up the line we stopped. I don't remember who stopped first. I remember that we all ended up standing in the same spot, looking at each other, and nobody was saying anything for a second.

Then one of the other journeymen said it. "We should probably come back tomorrow. This is getting worse."

I need you to understand how easy it would have been to say the other thing. We were already there. We'd already done the hard part, the hike in. Every one of us had the same thought sitting right behind our teeth: we're here, let's just finish the patrol.

Nobody said that. We all agreed it wasn't safe, and we walked out.

There was something in the air that night. I can't describe it better than that. You could feel that something could happen. After enough years you learn that feeling is information, not nerves. It's also the easiest information in the world to talk yourself out of when you've already hiked in.

We came back at first light.

The path we'd been walking was gone. Covered in trees. Big ones, down across the trail in the exact stretch we'd been standing in a few hours before. They'd come down in the dark while we were driving home.

I've thought about that night a lot. Not because of the trees. Because of how fast the decision was.

Nobody argued. Nobody pulled rank. Nobody had to be brave. One man said it, the rest of us agreed, and the whole thing took about ten seconds.

That's not luck. That's not a good crew having a good night. Ten seconds like that get built over months. Every tailboard where somebody raised a concern and got a real answer instead of a sigh. Every time a foreman said "good catch" and meant it. Every time a journeyman's "I don't like this" was treated like information instead of a complaint.

The receiving end did its work long before that night. That's why the sending end worked when it counted.

Storm season's here again. Different kind than the calendar promised. Wind events. PSPS calls. The first atmospheric river of the year is coming, and your crews are going to be standing on a mountain at 2 AM with that same thought behind their teeth.

Whether they say it out loud was decided a long time ago. It was decided the last time one of them spoke up and you answered.

This one's mine, so there's no composite to disclose. Every detail above is how it happened.

But I want to run it the way I'd run any near-miss, because the thing that saved us isn't the thing most people see first.

A crew on a foot patrol. Storm still active. Circuit out, which means pressure. Not pressure from the office. Nobody was calling us. The pressure was the outage itself. Customers in the dark, a problem somewhere up the line, and a crew that had already paid the price of the hike in.

Sunk cost is the most dangerous thing on a mountain. Not the wind. The feeling that you've already spent too much to turn around.

One man named the conditions. "This is getting worse."

The rest of us had to do something with that sentence. We had about two seconds to decide whether it was a concern or a complaint.

We treated it as a concern. We walked out. The trees came down.

Here's the miss, and it's not on my crew. It's the version of this story I've watched play out on other crews for twenty years.

Same mountain. Same wind. Same sentence. "We should probably come back tomorrow."

And the foreman says, "We're already here."

That's it. That's the whole miss. Three words. He didn't yell. He didn't call anybody weak. He just answered the concern with the sunk cost, and the crew heard what he actually said: the hike in matters more than what you're feeling in the air.

On that crew, the next man with a concern keeps it. Not that night. Forever. Because he watched what happened to the last one.

I've been on crews where "we're already here" was the standard answer. I never heard a stop-work call on those crews. Not because there was nothing to stop for. Because everybody had learned it wasn't worth saying.

The fix is not training people to speak up. Your crew already knows how to speak up. They did it as apprentices, and somewhere along the way they learned whether it was worth the cost.

The fix is training the person on the receiving end. What you do in the first five seconds after a concern lands is the only safety training that matters for the next one.

On my crew that night, the receiving end was a group of guys who'd been answering each other's concerns right for a long time. So when the sentence came, it didn't have to fight anything. It just landed.

Name It cuts both ways. Somebody has to say it. And somebody has to hear it like it matters.

What complacency sounds like: "We're already here. Let's just finish the patrol."

What vigilance sounds like: "You're right. It's getting worse. We're walking out."

Same crew. Same mountain. Same sentence from the same journeyman. The only variable is what came back.

A concern lands mid-job. Wind's up, you're behind, and somebody says the thing you didn't want to hear. You have about five seconds before your face answers for you.

This is what to do with those five seconds.

1. Stop moving. Hands off the tool. Turn toward the person. If you keep working while they're talking, you've already answered.

2. Say it back. "You're saying the wind's getting worse and you don't like where we're standing." That's it. You are not agreeing yet. You are proving you heard it.

3. Say what it's worth. "Good. That's what I need to hear out here." Five words. Costs you nothing. Buys you the next one.

4. Make the call out loud. "We're walking out." Or, "Here's why I think we're okay for ten more minutes, and here's what changes my mind." Either one is fine. What's not fine is silence, or "we're already here."

5. Close it later. Back at the truck, on the drive, next tailboard: "That was the right call on the mountain." Say it where the rest of the crew hears it. You're not thanking one man. You're telling everybody what happens when they speak up.

What kills it, every time:

Any one of those, once, and you've trained your crew for the next storm. Just not the way you wanted.

The rule: Every concern raised mid-job gets steps one through four before anybody moves. Not as discipline. As the standard. Print this page. Tape it in the truck.

Field leaders. Think about the last three times somebody on your crew raised a concern mid-job. Not at the tailboard. Mid-job, when you were behind and it cost you something to stop. What did your face do? Your crew remembers. They're going to decide what to say at 2 AM in the wind based on those three moments, not on anything in your safety program.

Supervisors. Pull your stop-work log for the last ninety days. If it's empty, that is not good news. Your crews are not working in conditions that never call for a stop. They're working for foremen who taught them it isn't worth saying. The number you want is not zero. The number you want is one that goes up when the weather gets bad.

Executives. Your storm response plan has a chapter on crew rest and a chapter on PSPS. Does it have a chapter on what a foreman says when a journeyman wants to walk off a mountain? Every outage puts pressure on the crew, and nobody has to call them for it to be there. Nobody called us that night. The pressure was there anyway. Your foremen are the only thing standing between that pressure and the trail. If you've never trained the receiving end, you've trained half the conversation and left the other half to chance.

Storm season is here. Your crews are going to be standing somewhere in the dark with a concern they haven't said yet, and the only thing that decides whether it gets said is what your foremen did with the last one.

I run a 90-minute Name It Stand-Down on your site, with your crew, at your shift time, using the work you're actually doing that week. I tell the story straight. We run your job through Ask, Adapt, Act. Your people leave with tailboard cards and one thing they're going to say out loud tomorrow morning.

Then your foremen run the First Five Seconds for ten working days. After that, you and I get on the phone for thirty minutes. If you can't name one concern your crew raised that they wouldn't have raised before, I refund the session fee.

Reply to this email with the word STORM and I'll send you the session outline and my open dates.

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

This week, the first time anybody on your crew raises a concern mid-job, stop moving and say it back before you answer. Then tell them it's what you needed to hear.

Then reply to this email and tell me what happened next. I read every one.

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 holding two dates in Q4 for on-site stand-downs, and I'm booking Q1 2027 now. If you're building next year's training plan this month, reply and I'll hold one while you get approval.

Until next time,

Lito Wilkins