Before You Replace Your Executive Chef, Look at the Kitchen They Inherited

Most hotels have had a version of this meeting. Food cost has drifted. Guest comments about the restaurant are getting sharper. Overtime keeps creeping up, the team looks tired, and the plate that went out on Tuesday does not look like the one that went out on Saturday. Someone finally says what others in the room may be thinking: we need a new chef.

Sometimes that is the right call. But before making it, it is worth asking a harder question first.

A replacement inherits the system, not just the job

When a hotel hires a new executive chef, it usually believes it is buying a fix. What it is also doing is handing a new person the same kitchen: recipes that live in the previous chef's head or in a binder nobody has opened since the last opening; prep pars set by habit rather than forecast; a schedule built around who wanted which shift; purchasing decisions split between the chef, purchasing and the F&B director with no one clearly accountable; and a reporting line in which the chef answers to the F&B director on paper and to the GM in practice.

A capable chef can spend the first months reverse-engineering all of this. A great one starts rewriting it. Either way, the hotel is paying a senior salary for a period of rediscovery, and the guest experience rarely improves while it happens.

Too often, the cycle then repeats. The new chef runs into the same structural walls, the numbers slide back, and the hotel concludes it hired the wrong person again.

Turnover is a cost the P&L does not show

Chef turnover rarely appears as a line item, but its cost is real: recruitment fees, the overlap or the gap, the months of inconsistency while a new leader learns the building, and the cooks who may leave with the departing chef because their loyalty was personal rather than institutional. When the knowledge of how a kitchen works lives mainly in one person, each departure can feel like a partial closure.

That is the structural risk. Not only that the chef left, but that the kitchen was not built to withstand the chef leaving.

What should exist before the next hire

Before an owner or GM posts the role, five things should ideally be in writing. None of them requires the new chef to exist.

1. Standard recipes and plate specs for every item on the current menu, with yields, portion weights and a photograph. Not a perfect library. A current one.

2. Production pars tied to forecast covers, rather than to the last chef's instinct. The prep list should come from the business, not from memory.

3. A staffing model built on covers by daypart. A schedule that cannot be explained by volume is very difficult for a newcomer to manage.

4. A decision map. Who approves menu changes, vendor changes, overtime and capital requests. Many conflicts between chefs and F&B directors are less about personality than about two people who were each told they own the same decision.

5. The numbers the role will be judged on, defined in advance: food cost, labor cost per cover, guest scores for the outlet, retention of key cooks. Stated before the hire, not discovered at the first review.

A hotel that has these five can hire for talent and leadership. A hotel that does not is, in effect, hiring someone to build infrastructure it should already own, and then judging them on results that infrastructure was supposed to produce.

Accountability runs both ways

None of this lets the chef off the hook. Building, documenting and maintaining these systems is part of an executive chef's job, not an optional extra. A chef who runs the kitchen from memory, resists writing things down or treats standards as personal preference is creating the same fragility described above, and the hotel is right to hold them to it.

The hotel's side of the agreement is just as concrete: the authority to make the decisions the role is accountable for, the resources to do the work properly, including time for documentation and training, and enough continuity in ownership, management and direction for systems to take hold. When either side fails to hold up its end, replacing the person rarely fixes the problem.

A proposal for the first 60 days

New F&B leaders are often evaluated on impressions in their first two months: energy, presence, how the tasting went. Those matter, but they say little about whether the operation is improving.

One way to make the early period more useful is to agree on a simple evaluation frame in advance, adjusted to the size and complexity of the operation. For example: by around day 30, the new chef has confirmed or corrected the written specs and pars, and flagged where reality diverges from paper. By around day 60, the outlet shows early, measurable signs of consistency: plate audits against spec, prep waste being tracked, a schedule that follows the volume curve. The guiding question shifts from "Do we like them?" to "Is the system tighter than when they arrived?"

This moves the conversation from personality toward performance, and it protects the chef as much as the hotel. A leader measured against clear, agreed standards can be coached. A leader measured against a general feeling is much harder to develop, and much easier to replace.

Why recruiting harder is rarely enough

The market for hotel executive chefs and F&B directors is tight, and many properties respond by widening the search, raising the offer or reaching for a bigger name. Those are reasonable moves inside a sound structure. Outside one, they often just raise the price of a similar outcome.

A strong chef dropped into an undocumented kitchen tends to spend much of their energy compensating for it. A solid, less celebrated chef placed into a well-documented one can often deliver consistency much sooner. Most owners would choose the second result. Fewer organize for it.

The human side of structure

This is not an argument against people. Kitchens are run by people, and the best ones are led by chefs who teach, set standards and earn loyalty. Structure is what allows that leadership to compound instead of resetting with every departure. Written systems do not replace a chef's judgment; they free it for the work that actually requires it: the menu, the team, the guest.

There is a retention argument too. Cooks rarely leave kitchens only because of pay. They also leave because nobody can tell them what good looks like, because the standard changes with every new boss, or because the schedule feels arbitrary. A kitchen with clear specs, fair staffing and defined decision rights is a better place to work, and that matters more every year the labor market stays the way it is.

The question for the next leadership meeting

When the restaurant underperforms, the conversation should not begin and end with who to replace. It should also ask what the next person would inherit. If the honest answer is "the same kitchen," the hotel may not be facing only a hiring decision. It is likely facing a structural one, and without addressing it, it risks paying for it again, one executive chef at a time.