A few years ago, I wasn’t launching something new. I was walking into a five-year-old automation system that had survived three acquisitions, two redesigns, and zero clear ownership. Shuttle. Mini-load. Unit sorter. Putwalls. Shipping sorter - all stitched together.

On paper, things looked steady - uptime trending green-ish, alerts ‘quiet’.
But beneath it, every team carried history.

Maintenance had scars.
Ops had stories.
Engineering had opinions.
And the business? Exhausted from finger-pointing.

No one truly owned it.

That was the job I was hired to fix. To bring stability to a system that technically ran but culturally didn’t.

For a while, uptime metrics seemed okay, and alerts were quiet.

But one afternoon, a tote jammed in lane seven.
The lights flashed red, the conveyors froze, and the floor went still.

Ops stared at dashboards that confirmed what they already knew - something broke.
Maintenance was across the building.
Engineering was still logging in.

And I was standing there, watching a great system stall because people couldn’t reach each other fast enough.

That’s when it clicked: we didn’t need a pilot. We needed a pit crew.

It sounds funny now, almost laughable, but the real breakthrough wasn’t another integration or a sensor. It was radios.

We bought high-range radios, the kind you see clipped to belts across large sites.
They cost a couple of hundred dollars each, but they bought us something priceless: connection.

Channel 3 became “maintenance. And the rule was simple - if something broke, call it in.

No tickets. No dashboards. No waiting for permission.

And it worked. Downtime dropped. Tension eased and, importantly, trust grew.

That’s when I learned something I still hold on to:

Once people started talking, patterns surfaced. Every smooth recovery followed the same rhythm, what I now call the Three Ds:

1️⃣ Detect early - five minutes of silence costs an hour later.
2️⃣ Diagnose together - blame fixes nothing.
3️⃣ Deliver repeatability - so tomorrow’s shift doesn’t fight today’s ghost.

That rhythm changed everything. We stopped firefighting and started engineering calm.

Leading automation isn’t really about robots.
It’s about building a trust fabric between teams that speak different operational dialects.

Ops talks urgency.
Maintenance talks precision.
Engineering talks data.

If those languages never overlap, even the best system breaks down.

You can’t buy that alignment.
You build it. One conversation, one fix, one radio call at a time.

Don’t start with another integration or dashboard. Start with the connection.

Ask yourself:

That’s your foundation. That’s your pit crew.

When I look back, that small decision to hand out radios and rebuild trust changed how I lead. Because it taught me something I still see across warehouses today:

If your automation still feels fragile, don’t blame the code. Look around.
See who’s talking and who’s waiting for permission.

Because flow doesn’t fail when the robot stops moving. It fails when people stop talking.

And sometimes, the fastest fix is still the simplest one:

If this story hit home, share it with someone on your team who’s in the middle of a rollout or firefight right now.
Sometimes the fix isn’t more tech; it’s more trust.

And if you’re leading automation and trying to build that rhythm across Ops, Maintenance, and Engineering, this is the kind of work I help teams with.
Hit reply or message me on LinkedIn. I am always happy to compare notes or share what’s worked across sites.

Thoughts? Questions? Feedback? Reply to this email.