The evidence on organizational change is consistent across decades and industries: most change initiatives fail. Not because the strategy was wrong. Not because the execution was incompetent. Because the people who were supposed to implement the change were never convinced it was necessary — and nobody thought that was their job to address.

The operator who announces a new service sequence, a new scheduling model, a new standard for Guest interaction — and then watches their cast nod, agree, and go back to doing exactly what they were doing before — has not experienced resistance. They have experienced the predictable outcome of a change process that skipped the most important step.

The Case That Was Never Made

Before anyone in your operation will change their behavior, they need to understand three things: why the current situation is no longer acceptable, that there is a viable path forward, and what their role in that path actually is.

Most operators communicate the third one. They announce what is changing. Sometimes they communicate the first one — they describe the problem. Almost none of them spend adequate time on the second — demonstrating that the change they are asking for is not just necessary but achievable, and that the leadership driving it has a real plan for getting there.

In the absence of that case, rational people do what rational people always do: they wait. They give the change enough surface compliance to avoid conflict, and they wait to see if leadership is actually serious this time. Because in most operations, new initiatives arrive regularly, are implemented inconsistently, are enforced for a few weeks, and then quietly disappear as the next urgent thing arrives. The cast has learned that waiting is the optimal response. They are not being obstinate. They are being rational.

The operator who wants real change has to do the harder work first — making the case clearly enough that the cast understands not just what is changing but why it cannot stay the same, and that the person asking for the change has a credible plan for following through.

The Human Side Is Not Soft

The framework for change that researchers have studied most carefully identifies ten principles for managing it effectively. The one that gets the least attention from operators is the first: address the human side systematically.

Most operators treat the human side of change as a communication problem — if they explain it clearly enough, people will get on board. What the evidence shows is that change is not a communication problem. It is an alignment problem. People at every level of the organization need to understand not just what is changing but how it affects them specifically — what their job will look like, what will be expected of them, how they will be measured, and what success looks like for them personally.

The cast member whose role is changing needs to know what that change means for their day, their standing, their relationship with their colleagues. The shift leader whose authority is expanding needs to know what that authority actually includes and where its limits are. The manager who is being asked to hold a new standard needs to know what happens when they do and what happens when they do not.

None of that is soft. All of it is operational. The operator who addresses it directly produces an organization that can actually change. The operator who skips it produces a cast that agrees in the meeting and reverts in the shift.

Change Cascades — Or It Does Not

The research is equally consistent on this: change that starts at the top but does not cascade to every level of the operation does not produce lasting results. The senior team can be completely aligned on a new direction. If the shift leaders are not equipped to model it, hold it, and coach to it at the unit level, the shift is where it dies.

In a restaurant, the shift is always where it dies or lives. The service standard that the operator has articulated perfectly in a team meeting either shows up in the way a shift leader runs their section on a Thursday night — or it does not. The gap between the articulated standard and the delivered standard is almost always a leadership development gap, not a training gap.

This is the core argument for Leadership Team Coaching — building the layer of leadership between the operator and the cast that can actually carry the change into the operation and hold it there. Not because they were told to. Because they understand why it matters and have the skills to execute it.

What Changes Tomorrow

Before you announce the next operational change in your restaurant, answer three questions in writing:

Why can the operation not stay as it is?

What does the operation look like when this change is working?

What is the specific role of each person on the team in making it happen?

If you cannot answer all three clearly, you are not ready to announce the change. You have a plan. You do not yet have a case. The plan without the case will produce the same outcome as the last one.