Most explanations point to people — the wrong attitudes, leadership, or mindset. In nearly every case I’ve worked, the real cause was in the operating structure: unclear decision authority, standards handed down rather than built, and leaders reinforcing different things on different days.
Decisions that were made last month get re-made this month. Standards that were clear in the meeting aren’t consistent on the floor. What starts with agreement around the room ends with people going back to old ways of doing things. Escalations keep rising even as you keep pushing authority down.
These situations are well-known in manufacturing. What’s less common is a clear path through them.
Early in my career, working on large-scale change projects in the U.S. and abroad, I watched well-resourced teams fail at the same place: getting people to actually change what they did. The typical response was more persuasion — better communication plans, stronger executive sponsorship, more compelling presentations.
I took a different approach. Instead of figuring out how to get people to accept the change, I spent time finding out what they actually wanted. What I found surprised me at first. People almost always shared the same core goals, no matter what their roles were. The only difference was whether people believed that their perspectives really mattered. Once they saw they had a real say, the so-called resistance largely disappeared — because it had never been resistance in the first place. It was a rational response to being handed a solution they had no stake in.
I’ve spent the years since applying that logic to manufacturing operations. Most of what I do involves building the conditions for people to help shape how the work actually gets done. I work alongside leaders to build the reinforcement habits and decision clarity that make new behaviors stick — whether that means applying a new escalation standard, following a revised handoff process, or adapting to new systems.
"People don't resist change. They resist change that feels forced on them — change they had no part in shaping."
This isn't a philosophy. It's an observation from shop floors, conference rooms, and conversations with people at every level of the organization.
When the floor is not running like it should, more training, better onboarding, and more routines often seem like the right moves. Yet all the training in the world won’t help your team when the routines they thought were solid seem to change when the pressure’s on. Fix the gaps in the operating structure, and people start to perform better.
Fewer unresolved issues finding their way to your desk. Decisions made at the right level, by the right people, without constant upward referral. Standards that hold across shifts without you personally enforcing them.
Less rework. Fewer surprises three steps downstream. Change that doesn’t have to be re-launched six months later because it quietly stopped.
And the thing most leaders say they want but rarely get: the floor running consistently, even under pressure — because the people running it helped build it, and they own what they built.
That’s what execution that actually holds means. Not a methodology. Fewer phone calls and a floor you can trust.
No slide decks. No proposals. Just a conversation about what’s happening in your operation — and how to fix it.