I was the manager on duty during a busy Saturday at the museum, and a guest at the membership desk was visibly upset.
Her family had been members for years. She was trying to use a discount she swore had always applied, and our current system showed the discount as no longer active. She was tired, she was frustrated, and the line behind her was growing.
I was tired too. I looked at the screen, I looked at her, and I heard the words come out of my mouth before I had thought them through. "I'm sorry, that's just our policy."
She left without making the purchase. I went home that night embarrassed. I had not actually known whether her version of the discount had ever been real. I had not looked into it. I had not offered her anything else. I had reached for the easiest sentence in the staff handbook and used it as a way to end an uncomfortable conversation.
"That's just our policy," might be the four most expensive words in any guest-facing operation.
It does several things at once, all of them bad. It tells the guest you are an obstacle, not a problem-solver. It tells them the rule matters more than they do. It tells them you have stopped thinking about their actual situation and started defending a system you did not write. And it tells them, accurately, that the conversation is over.
Most operators do not realize how often their team defaults to this phrase, or to a small variation of it. "That's not something we can do." "I'm not authorized to override that." "Our system doesn't allow that." Same job, different words. Each one is a small door closing in the guest's face, and the guest hears all of them the same way.
Why This Matters
The phrase is not just expensive because it ends interactions badly. It is expensive because of what it reveals.
When a staff member defaults to "that's just our policy," the operation has usually failed them upstream. Either nobody told them what the rule was actually for, or nobody told them what to do when they encountered an edge case, or nobody made it safe to use judgment, or all three. The phrase is a symptom of empowerment that was never actually built.
The real cost is in what the guest does next. Some will escalate, which now costs you a manager's time on something that should never have reached a manager. Some will quietly leave and not come back, and you will never know what they decided. Some will tell other people about the experience, and the version they tell will be unkind to you in ways you cannot defend against.
All of that is downstream of four words your staff member did not even fully mean to say.
There is also a longer-term cost. A team that uses "that's just our policy" repeatedly is a team that is learning to hide behind it. Each time a staff member uses the phrase and the manager does not push back, the phrase becomes safer to use the next time. Over months, it becomes the default response to any guest situation that requires thinking. The team stops looking under the rocks because nobody has asked them to.
This is how culture quietly degrades. Not through a dramatic failure, but through a thousand small surrenders of judgment at the front desk.
What To Do Next
There is a framework I have come to rely on for exactly this situation, and it works because it gives staff a simple alternative to the default no. I learned this framework at Disney. It's called TRY.
The T is for Take time to listen. The single most common reason staff defaults to "that's just our policy" is that they have stopped listening before the guest has finished explaining. They have heard the first sentence, mapped it to a familiar rule, and stopped processing. Taking time to listen, even when you think you already know where the conversation is going, often reveals that the guest's actual situation is not what you assumed. The discount the guest thought she had might be a real one that someone in marketing forgot to update in the system. The complaint about the line might actually be a complaint about not knowing how long the line was. Listening fully is the first thing the phrase prevents.
The R is for Review your options. Before applying a rule, ask yourself what the rule is actually for. Most policies were written for a specific reason that the staff member has rarely been told. The no-outside-food rule is usually about contamination control, not about guests bringing in a water bottle for a kid with a medical condition. The advance-booking requirement is usually about capacity management, not about a returning member trying to add one person. Reviewing what the policy is meant to protect often reveals that the current situation is not actually what the policy was protecting against. The rule still exists, but applying it to this specific guest does not serve the operation.
The Y is for Yield something. Sometimes the answer truly is no. The exhibit really is closed. The refund really cannot be issued. The capacity really is full. The framework does not pretend otherwise. But even when the final answer must be no, there is almost always something small you can offer to show effort. A complimentary upgrade. A comp drink. A walk to a different exhibit. An offer to follow up by email. The Yield is not about overriding the no. It is about making sure the guest leaves knowing you tried.
TRY does not take longer than "that's just our policy." It takes about the same amount of time as the alternative. The difference is that the guest leaves the interaction feeling heard, even when the answer was not the one they wanted.
If you are a leader, the TRY framework is something you should teach explicitly. Model it yourself. Reward staff who use it visibly. Audit your policies and make sure your team knows what each one is actually for, so they can use judgment instead of defaulting to the easiest sentence.
The four most expensive words in guest experience are easy to say. Doing the slightly harder thing, every time, is what separates the operations guests trust from the ones they tolerate.
-Matthew
P.S. The membership desk guest from that Saturday eventually came back, weeks later, when a different staff member took twenty minutes to actually figure out what had happened with her discount. It turned out she had been right. The system was wrong. I think about that interaction often.