Why Change Doesn’t Stick on the Shop Floor: The Why, What, and How That Actually Works

You can train the team, hand them the new SOP, and walk them through every single step. But usually, somewhere between six days and six weeks later, they’re back to “the way we’ve always done it.”

Not because they’re stubborn. Because the rollout started with how, and we never circled back to why.

I see this every week. A leader rolls out a new tool, a new process, a new system. The team gets the training, signs the acknowledgement, nods through the meeting. Then adoption stalls. Usage rates are lackluster. Old habits creep back in. The leader assumes resistance. The team assumes another flavor-of-the-month from leadership.

Both reads of the situation are wrong. The problem is that the rollout was done backwards.

Prefer listening? Check out this week’s Solo Session where I go even deeper on the topic.

Why we keep starting at how

I’ll be the first one to admit it: I used to do this constantly, that’s how I know this happens… and how to fix it.

When you’re in leadership, the problems are in your face every day. You see them at every level. You’re consumed with them. You think about them in the shower, on the drive home, at the dinner table. You run through option after option, weighing the impacts, the costs, the tradeoffs.

By the time you’re ready to talk to the team, you’ve already done all that work. You know the why because you’ve been living with it for weeks or months. You know the what because you’ve already pictured every downstream effect. So when you finally pull the team together, you skip past both of those and lead with the part that’s still a bit unresolved in your head: how exactly are we going to do this thing.

It feels efficient. You’ve done the thinking. You’ve reached the answer. Why waste everyone’s time walking them through ground you’ve already covered?

Because the team hasn’t covered any of it. They’re starting where you started six months ago, except you’re showing up at the finish line and asking them to run.

That’s the first failure mode. The second one is what gets compounded right after it: when you skip the why and the what, you also miss your shot at bringing people into the how. The folks closest to the work usually have better ideas about implementation than the leader does. Sometimes the ideas are different. Sometimes they’re a refinement. Either way, you forfeit the input by treating the conversation as a delivery instead of an exchange.

The three questions every change has to answer

I’ve talked about Why, What, and How before as the three questions every change initiative has to answer. The frame is straightforward:

– Why are we doing this now? What’s the actual problem, who decided it was big enough to act on, and what happens to the business if we don’t?
– What does this mean for me? Not what’s changing in the org chart or the workflow diagram. What’s changing in my morning, my handoffs, my role, my pay, my hours.
– How are we going to make it work? Not the plan you hand down. The plan you build with the people who have to live in it.

Most rollouts answer one of those three. Sometimes two. Almost never all three, in that order.

What I want to argue here, on top of the basics, is that these three aren’t just questions you cover in a kickoff deck. They’re a sequence. The order is non-negotiable. Skip Why, and the What lands as another mandate from leadership. Skip What, and the How feels like a punishment. Try to deliver How without the first two and you get exactly the rollout pattern that ends with people quietly reverting to the old way.

The Why is the case for change, not the pep talk

When I say start with Why, I don’t mean a slide that says “Our Mission Is to Become a World-Class Manufacturer.” I mean the actual business case, in plain language, with no smoothing.

I’m working with a service business right now that’s about a $100 million operation managing two to three thousand active projects at any given time. Their entire competitive moat is being eaten by AI. The tools their customers can now access make a chunk of what they sell easier and cheaper to do without them. The leadership team sees it. They’ve been working hard on the what, the new offerings, the new workflows, the new pricing. Internally, change has been slow.

My read is that they’ve been strictly working on the tactics. They haven’t fully shared the why. They’re talking about the new process, the new tool, the new approach, but they haven’t sat the team down and said: here’s why our market is different than it was eighteen months ago, here’s what that means for the business, here’s the window we have to respond before this becomes a survival question.

When you’re talking about a change at that altitude, the why is brutal honesty. It’s saying out loud, “if we don’t do this, we don’t have a business in the timeframe we used to count on.” That sounds dramatic. It is dramatic. It also happens to be true, and the team can feel it whether anyone says it out loud or not. The difference between saying it and not saying it is the difference between a team that understands what they’re being asked to change and a team that feels like they’re being asked to do more for the same pay because someone in the corner office had a vision.

The Why is what gives the rest of the rollout permission to exist. Without it, every conversation about new processes is a conversation about extra work.

The What is “what about me”

Here’s where I think most rollouts go quietly off the rails. Leaders translate “what” into the description of the new process. The team translates “what” into “what about me.”

Those are two different questions. Only one of them matters at this stage.

When the change lands, the operator’s first thought isn’t *I wonder if this new workflow improves throughput by 12 percent.* It’s a stack of personal questions. Is my job at risk. Am I going to be asked to do more for the same pay. Are my hours changing. Am I going to be moved to a different shift, a different department, a different machine. Is this the thing that finally pushes me into looking elsewhere.

If the leader doesn’t get out in front of those questions, the team will answer them privately, in the break room, in the parking lot, on text threads after their shift, and the answers they invent are almost always worse than the truth.

The What done well is transparent and specific. Here’s what changes about your morning. Here’s what changes about your handoff to the next station. Here’s what changes about the hours, the pay, the role. Here’s what doesn’t change. Here’s what we don’t know yet, and here’s when we’ll know.

Even when the answer to “what about me” is hard, hearing it from the leader beats inventing it in the parking lot. Sometimes the answer is “two of these twenty roles are changing significantly, and here’s how we’re going to support those two people through it.” That’s a hard conversation. It’s still better than the team filling in the blanks.

The How is built with, not handed down

Once the Why has landed and the What is on the table, the How earns the right to exist.

Earlier this month I came across a LinkedIn post from an operations leader who had rolled out new tools across their team a few months earlier. Adoption was about half what they expected. They asked the question every operations leader asks at that point: how do you really create buy-in?

What they tried was simple and good. They started a thirty-minute, company-wide tech meeting every Tuesday morning. One topic at a time. Updates, questions, open discussion. Talking about the new tools, but also talking about the old ones. They reported that what had felt like a “black box” became more transparent, the team felt included, and skepticism started shifting into momentum.

I dropped a comment on the post. The version of what I said is this: as change agents, it’s our responsibility to share the Why early and often, and as we’re doing that, we have to answer the question that’s already on everyone’s mind, which is *what about me*.

That post is exactly the move. Not because Tuesday mornings are magic. Because the leader stopped treating the rollout as a delivery and started treating it as a conversation. They went back, found the gap, and built a structure that let people surface their own questions, contribute their own ideas, and work through the change in real time.

That’s what the How looks like when it’s done well. The plan isn’t presented. It’s developed in the room with the people who have to make it work. Sometimes the operator who’s been running the line for fifteen years has a better idea than the team that designed the workflow. Sometimes the new hire spots a friction point nobody else noticed. Either way, when the How is co-created, two things happen: the plan gets better, and the people who helped build it have a stake in seeing it work.

The order is non-negotiable

I’ve watched leaders try to recover a stalled rollout by leading with How. It doesn’t work.

If the team didn’t get the Why, more detail on the How just feels like more pressure to comply with something they don’t believe in. If the team didn’t get the What, more detail on the How sounds like the punishment is being designed in real time.

Skip the Why, and the What lands as another mandate.

Skip the What, and the How feels like a punishment.

Try to deliver How alone, and you get the pattern this whole article is about. Trained team. Signed acknowledgements. Six weeks of compliance. Quiet reversion.

The fix isn’t more training. It isn’t more accountability. It’s going back to the start of the sequence and delivering it in the right order.

How this fits with Clarity, Consistency, Accountability

A quick note for readers who follow the Crysler Club content closely.

Clarity → Consistency → Accountability is the lens I use for almost everything. It’s the universal diagnostic. When performance breaks down, you work backward through it: was there accountability, was there consistency, was there ever clarity. The answer almost always reveals where the system failed.

Why → What → How is more specific. It’s the discipline you apply when the operational problem you’re solving is rolling out a change. Same parent toolkit, different job. CCA tells you whether the foundation is solid. Why → What → How tells you how to roll out the change so the foundation actually gets built.

If you want the deeper version of the accountability side, the shop floor accountability piece is the sister to this one. That piece is about managing performance after standards are set. This one is about delivering the standard so it sticks in the first place.

A note on trust

One thing underneath all of this is trust, and trust is built one moment at a time.

Brené Brown has an analogy I think about often. Picture a mason jar full of M&Ms. Trust gets built one M&M at a time. Every act of transparency adds an M&M. Every skipped Why, every “we’ll explain it later,” every change rolled out without warning takes one out. The jar doesn’t fill up overnight. It also doesn’t empty overnight. But the level in the jar is what determines how much credit you have when you’re asking the team to do something hard.

Leaders who consistently deliver Why and What before How are filling the jar. Leaders who keep skipping straight to How are emptying it. The team can tell which one is happening, even if nobody ever names it out loud.

What to do Monday morning

If you’re reading this and a recent rollout didn’t land the way you wanted, here’s the move.

Reflect on it honestly. Did you share the Why with enough depth that the team could explain it back to you in their own words? Did you answer the What in terms of what changes for them, not what changes in the workflow? Did the How get built with input from the people on the floor, or did you hand it down?

If the answer to any of those is no, rally the people involved. The leader who needs to own it is the one who calls the meeting. The format doesn’t matter. What matters is that you start with the observation and the admission, in your own voice.

It can sound like this: I noticed we haven’t really been using the new tool, and that’s on me. I don’t think I shared with everyone why we settled on implementing it in the first place. Let me back up.

Or this: Last time we met I said we’d share more in the coming weeks. It’s been five months and I haven’t shared much. Let me explain why, where we’re at, and what my plan is moving forward.

The room will be skeptical at first, but mostly open, assuming there’s actual follow-through on the other end of the meeting. The meeting itself doesn’t earn anything. It sets the tone. The real work is what happens in the days and weeks after, when the team is watching to see whether you actually meant it.

That part takes self-reflection. It takes owning a mistake out loud. It takes the discipline to deliver Why and What every time, not just on the rollouts where you remember to slow down. None of that is easy. It is, however, simple.

Final Thoughts

Most change initiatives don’t fail because the change was wrong. They fail because the rollout started at the wrong end. Why is the case for change. What is the impact on the person doing the work. How is the plan built with the people who have to live in it. In that order.

Skip the order, and you’ll spend the next year wondering why nothing sticks. Run it in sequence, and you’ll start watching changes hold long enough to actually compound.

Pick your next rollout. Before you write the SOP, write the Why and the What. Then walk into the room and let the team help you build the How.

That’s it for today.

See you all again next week!

Dave