When you change something in your operation — the menu, the service sequence, the room layout, the hours, the price — you are not just changing a process. You are changing a relationship.

The Guest who has been coming to your restaurant for three years has built expectations. Not consciously. They do not think about it. But they know where to sit, how the experience flows, what it costs, and what they are going to get. That knowledge is the foundation of the relationship. It is why they come back instead of evaluating their options every time. Loyalty is built on predictability, and predictability is built on the experience matching the expectation.

The moment you change something without bringing them along, you break that. Not because the change was wrong. Because the Guest arrived expecting one thing and experienced something different with no context for why. The relationship did not evolve. It just changed. And people do not stay in relationships that change without explanation.

The employee version of this is identical.

The Cast Member Who Was Not Told Why

The cast member who shows up to find a new service standard, a new sequence, a new expectation — posted on the board or announced in a pre-shift meeting — is in the same position as the Guest who walked in expecting the old menu. The implicit contract they had with the operation just changed. Nobody asked them. Nobody explained why. The message they received, whether the operator intended it or not, is: what you were doing before was wrong, and here is what you should do instead.

That message produces surface compliance and private resistance. The cast member executes the new standard while the operator is watching. They revert when they are not. Not because they are defiant — because they were never given a reason to believe the new standard was better than the old one. They were given an instruction. Instructions without reasoning produce compliance. Reasoning without instruction produces confusion. Both together — the why and the what — produce behavior that holds.

The research on organizational change is consistent on this point across decades of study: change initiatives fail not because the strategy is wrong but because the people asked to implement it were never convinced it was necessary. They agreed in the meeting. They reverted in the shift. The operator called it resistance. It was rational behavior in the absence of a compelling case.

The Same Ride, Two Different Passengers

When Guests experience a change in your operation without transition, they feel disoriented and sometimes betrayed. The restaurant they chose is no longer the restaurant they arrive at. Some will adjust. Many will not return. The ones who do not return will not tell you why — they will simply stop showing up, and by the time the pattern is visible in the numbers, the relationship is already over.

When employees experience a change without transition, they feel disoriented and sometimes devalued. The job they agreed to is no longer the job they are being asked to do. Some will adjust. Many will quietly disengage. The ones who disengage will stay on the payroll while executing below the standard you need — costing you more than the ones who leave, because the cost of disengagement is invisible until it shows up in the Guest experience.

Both problems have the same solution. Take them along for the ride.

What Taking Them Along Actually Means

For Guests: name the change before they experience it. A menu change that is introduced by a cast member who says “we updated a few things tonight — can I tell you what’s new?” is a conversation. The same change experienced without acknowledgment is a surprise. The conversation preserves the relationship. The surprise strains it. This is not complicated. It is a training decision and a culture decision — does your cast know that their job includes managing the Guest’s transition, not just delivering the new standard?

For employees: make the case before you announce the change. Not a memo. Not a meeting where you explain what is changing. A conversation where you explain why the current situation is no longer acceptable, what the operation looks like when the change is working, and what their specific role is in making it happen. The cast member who understands all three is not being asked to comply. They are being invited to participate. That is a different relationship — and it produces different behavior.

The operator who does this consistently builds something rare: an operation where change is not a disruption. It is a signal that the standard is evolving. Guests trust it because they have been brought along before. Cast members accept it because they have been given the reasoning before. The relationship with both absorbs the change instead of fracturing under it.

Change without transition is just disruption. The transition is not the soft part of the work. It is the work.