That's Just How It Is
InnSight: The Business of Exceptional Hospitality
This is the fifth in a six-part series showing how a framework designed to destabilise nations explains why hospitality venues eat themselves alive. Dive in here or start with The Hotel That Ate Itself, then come back.
The Settlement
There is a stage in the decline of a hospitality venue that is more dangerous than any crisis. It is the stage where the decline stops feeling like decline and starts feeling like reality.
Not because things are fine. Because things have been not-fine for long enough that the people inside the operation have adjusted to it. The dysfunction has been absorbed. The standards have quietly settled. And the language has shifted from “we need to fix this” to “that’s just how it is.”
Bezmenov called this stage normalisation. In geopolitics, it is when a destabilised society stops resisting and accepts the new baseline as permanent. In hospitality, it is when an operator stops fighting the churn, the inconsistency, the drift, and starts treating them as the cost of doing business rather than the consequence of choices that were never made.
This is not about the structural realities of the industry. Hospitality is hard. The hours are real. The pressure is real. The people who choose this work understand what they signed up for. Normalisation is not the difficulty of the work. It is the moment leadership stops distinguishing between what is genuinely inherent to the industry and what is the result of their own tolerance. High churn is not inherent. Inconsistent standards are not inherent. A team that does the tasks without owning the experience is not inherent. Those are leadership outcomes dressed up as industry conditions.
The settlement is quiet. It doesn’t announce itself. And that is what makes it the hardest stage to reverse.
What Normalisation Looks Like on the Floor
It doesn’t look like failure. That’s what makes it so hard to fight.
A normalised venue still trades. Still fills tables on Friday and Saturday. Still posts to social media. Still has staff who show up. The revenue hasn’t collapsed. The reviews aren’t terrible. There’s nothing catastrophic enough to trigger a rethink.
But the standards have quietly settled to a level that would have been unacceptable two years ago. The table touch that used to happen on every cover now happens on some. The pre-service briefing that used to be tight is now loose or skipped entirely. The recovery when something goes wrong is slower, less instinctive, more dependent on one or two people noticing. The team is doing the work. Nobody is owning the experience.
The owner has stopped walking the floor with the same intensity because the intensity was exhausting and the returns felt diminishing. The manager has become the permanent correction layer, stepping into issues that should never have reached her, carrying the room through force of will rather than operating inside a system that holds without her. Staff wait to be told. Supervisors correct things only when prompted. If a table looks unhappy, people notice but don’t always move unless someone senior signals it.
Everybody is doing their job. Nobody is carrying the guest experience as a shared outcome.
And the language protects the pattern. “That’s just hospitality.” “You can’t get good staff anymore.” “The labour market is cooked.” “Young people just don’t care.” Every one of those sentences is a normalisation mechanism. It shifts the cause outside the building so nobody inside has to own it.
Why Ownership Is Not What Most People Think
Ownership in hospitality is not enthusiasm. It is not a team that gets pumped before a big service. It is not loyalty to the brand or the operator. It is not tenure.
Ownership is a mindset. It is the person who sees a problem on the floor and fixes it because it is their problem, not because someone told them to. It is the server who notices a guest scanning the room for attention and is already moving before the guest has to raise a hand. It is the floor manager who notices the kitchen is under pressure and adjusts the seating pace without needing to be told, because she understands her job is not just managing the floor but protecting the whole service. It is the sommelier who notices a first-date couple hesitating over the wine list and reads the table well enough to recommend something that makes them feel looked after rather than out of their depth, without being asked and without making it a performance.
You cannot manufacture that with a pep talk. You cannot create it with an employee of the month programme. You cannot motivate it into existence. It is either built into the operating environment or it is not. And building it requires something most hospitality operators have never done: making the standard explicit enough to transfer.
The Tolerance Issue
This is the part most operators don’t want to hear.
If your team doesn’t own the guest experience, it is not because they are the wrong people. It is because you have made ownership a hope rather than a standard. The standard has never been written down, demonstrated, reinforced, and defended clearly enough for the team to carry it without you standing over them.
Everything important still lives in the heads of the owner and the manager. The team operates on guesswork, habit, and whatever they can get away with on a busy shift. Shared common sense fills the gap, and shared common sense is a fantasy when the room is under pressure.
That’s not a morale issue. It is a tolerance issue. What you accept without naming, you embed without knowing. Every time a short cut goes unchallenged, the standard resets. Every time an inconsistency is absorbed instead of addressed, normalisation deepens. The team is not ignoring the standard. The team is performing to the standard you are actually enforcing, which is almost certainly lower than the one you believe you have set.
The inverse applies with equal force. Every time a team member holds the standard under pressure and someone above them names it immediately and specifically, that standard gets reinforced faster than any training programme ever could. Normalisation is not only broken by calling out what is wrong. It is broken by recognising what is right, in the moment, so the team knows exactly what the real standard looks like in practice.
Built To Own™ exists for exactly this problem. Not as a philosophy. As a methodology. One clear standard. One real conversation. One specific move. Then repetition until it stops being a conscious effort and becomes normal. You don’t build ownership by motivating people. You build it by defining what ownership looks like, by role and by moment, and then reinforcing it until the team defends it without you.
What It Looks Like When It Turns
I was brought into a late-night restaurant and bar where dysfunction had been normalised so completely that the owners barely noticed it anymore. High staff churn was dismissed as “just hospitality.” Inconsistent service depended on who happened to be rostered. The manager acted as the permanent correction layer, stepping into issues that should never have reached her, while the team did the work without truly owning the guest experience.
The problem was not that people were unwilling. It was that ownership had never been installed as a standard. Everything important still lived in the heads of the owner and manager, and a bunch of batshit boring documents no one ever read, so the team operated on guesswork, habit, and whatever they could get away with on a busy shift.
The turning point came when they stopped treating it as a morale issue and made it a standards issue. We wrote down what ownership actually looked like by role and by moment: what a floor staff member owned without asking, what a supervisor owned when service slipped, what recovery looked like, and what “I saw it, so I handled it” meant in real terms. Then we reinforced it relentlessly through service rhythm, post-service reviews, and direct conversations with specific people. Not vague team talks. Direct, individual, accountable conversations.
But the real shift came from something simpler than any of that. They started asking every person on the floor, at the end of every service, two questions. What did you see tonight that was not right? And what did you do about it? Not what did you report. Not what did you escalate. What did you do. The first week, most of them had nothing. They had seen plenty but done little because doing something had never been their job. By the third week, they were coming to post-service with answers. By the sixth week, the questions were redundant because the behaviour had already changed. They were not waiting for the debrief to act. They were acting during service because the expectation had shifted from “notice and report” to “notice and own.” That is the difference between a team that follows standards and a team that holds them.
The moments that told the truth were small and specific. A waiter saw a two-top cooling off after a delayed mains course and fixed it without waiting for the manager. A bartender stepped out from behind the bar to reset a table issue because the floor was stretched and he understood the guest experience was his business too. One of the younger supervisors started calling out sloppy handover behaviour from older staff. Not performatively. Matter-of-factly. Because the standard had become real enough to defend. That was the tell. Not enthusiasm. Not team-building noise. Peer-to-peer accountability.
The venue did not become perfect. It became accountable. Fewer avoidable escalations. Faster recoveries. Cleaner closes. Less emotional drag on the manager. Staff turnover eased because stronger people no longer felt they were carrying passengers in silence. Guests felt a more coherent room. The owner stopped treating every service as a tension-filled inspection exercise.
The room got quieter in the right way. And in hospitality, that’s when pride stops being performance and starts becoming real.
The Test
One question. Honest answer.
If you stepped away for 90 days, would the standards hold, improve, or decay?
If they would hold or improve, you have built ownership. The team carries the standard because it is theirs, not because you are watching.
If they would decay, you have not built a business. You have built a dependency on yourself. And that’s not leadership. It is a bottleneck with a title.
Ownership in hospitality is not a culture initiative. It is not a workshop outcome. It is the product of standards that are named, written, demonstrated, and defended until the team stops needing you to hold them up.
That build starts with one standard. This week.
Next in the series: The Full Inversion. All four stages examined. Both playbooks laid out. The choice is yours.