There is a particular kind of institutional knowledge that develops in any organization that has operated under difficult conditions for long enough. It is the knowledge of what to expect — and more specifically, what not to expect. Food cost that runs two to four percent over budget every month becomes an accepted range rather than a persistent problem. Turnover of sixty to eighty percent annually becomes a hiring challenge to be managed rather than a structural failure to be addressed. A third executive chef in five years becomes a narrative about the difficulty of finding the right person rather than a signal about the environment that keeps producing the wrong result.
This normalization is understandable. It is also one of the most expensive things that happens in premium hospitality operations.
The cost of normalized dysfunction
When dysfunction is normalized, it stops generating the urgency required to address it at its source. The food cost variance is managed through budget adjustments rather than design changes. The turnover is managed through continuous recruiting rather than operational redesign. The leadership instability is managed through succession planning rather than through an examination of what the operation requires of its leaders and whether that requirement is reasonable.
Each of these responses is rational given the constraints of day-to-day management. Each of them is also, in the longer term, significantly more expensive than addressing the underlying problem would have been. The cost of continuous recruiting, when calculated fully — search fees, onboarding time, the productivity loss during transition, the institutional knowledge that leaves with each departure — is almost always higher than the cost of building an operation that talented people choose to stay in.
The question for any owner or board member is not whether the current problems are manageable. It is whether the current problems are permanent features of an undesigned operation — or correctable features of one that can be designed.
What boards and owners need to know
The conversation that most boards and ownership groups have about F&B performance is a financial one. Revenue against target. Cost against budget. Member satisfaction scores. These metrics matter. But they are outputs — they tell you what the operation produced, not what produced it.
The input conversation — the one about how the menu is designed, how ingredients are architected, how training is structured, and how the system is built to protect its own standards — is the conversation that most ownership groups have never had with their F&B leadership. Not because they are not interested, but because no one has framed it as a financial conversation.
Framing it correctly
Menu design is a financial decision. The architecture of an ingredient system directly determines food cost variance. The design of a training system directly determines execution consistency, which determines guest experience scores, which determines member retention and new member acquisition. These are not operational details. They are the mechanisms through which the financial outcomes that boards and owners care about are produced.
An operation that has never been designed — that has been assembled over time through the accumulated decisions of successive leadership teams, each building on or reacting to what came before — is an operation that will continue to produce the same range of outcomes regardless of who is hired to run it. The only thing that changes those outcomes permanently is a change in the design.
That conversation starts with the menu. And it is a conversation worth having — because the alternative is continuing to pay, year after year, for problems that were never inevitable.
Ask yourself: How much has your operation spent in the last twelve months on problems you have quietly accepted as a normal cost of doing business?
Complimentary Assessment
Find out where your operation's gaps are.
The F&B Operational Stability Assessment evaluates standards ownership, leadership continuity, and execution consistency.