The first responsibility after a difficult service is not to find someone to blame. It is to rebuild the facts, protect the next service and understand what the operation must learn.
At the end of a bad service, everyone has a version of what happened.
The kitchen believes too many orders arrived together. The restaurant team says the food took too long. Banqueting reports that the event schedule changed. Purchasing points to a late delivery. One section says its preparation was incomplete because staff were moved elsewhere.
By the time the last guest has left, facts and frustration are often mixed together.
Consider a busy Saturday in a city hotel.
A conference dinner begins earlier than expected. The main restaurant fills quickly. Room service receives an unusual concentration of orders. One piece of equipment fails, a key preparation runs short and several tables experience long waiting times.
The culinary team finishes the evening tired and defensive. The service team has faced the guests directly and feels that the kitchen did not respond quickly enough. Management has received complaints but does not yet have a complete picture.
The next morning, the senior culinary leader can enter the kitchen ready to identify who failed.
That instinct is understandable. It is also where the next mistake can begin.
The day after a bad service, the first responsibility of an Executive Chef, Culinary Director or Chef de Cuisine is not to arrive with a conclusion. It is to restore enough calm and accuracy for the operation to understand what actually happened.
Begin With What Still Requires Immediate Attention
Before analysing the service, the leader should determine whether anything remains unresolved.
Was there a food safety concern, an allergen incident or a guest complaint requiring formal follow up? Are temperature records, incident reports or product traceability details incomplete? Does equipment still need repair? Has a guest been promised an explanation or response?
These matters cannot wait for a general meeting.
Guest safety, legal responsibilities and urgent recovery actions must be addressed first, with the appropriate manager, General Manager or Human Resources representative involved when necessary.
The same applies to the next service.
Guests arriving today should not pay for what happened yesterday.
Before beginning a long discussion, the culinary leader should confirm that today’s preparation, staffing, equipment and product availability are under control. If the same operational weakness is still present, an immediate temporary measure may be required.
This could mean simplifying part of the menu, adjusting reservation pacing, moving an experienced colleague to a vulnerable section, arranging emergency maintenance or increasing the frequency of communication between the kitchen and service team.
Analysis matters, but service continuity comes first.
Do Not Begin With a Public Trial
A team often expects anger after a difficult service.
Some people arrive ready to defend themselves. Others become quiet. Junior colleagues may wait to see who will be blamed before deciding what they are prepared to say.
A leader should acknowledge that the service did not meet the required standard. Avoiding the subject would weaken credibility.
The first message, however, should establish the purpose of the review:
Yesterday’s service did not meet our standard. We need to understand exactly what happened, correct what affects today and then decide what must change. I want facts, not excuses and not accusations.
This is not a promise that there will be no consequences. It is a commitment to reach conclusions after examining the evidence.
If the review begins as a public trial, people will naturally protect themselves. Information becomes selective, responsibility is pushed between departments and the leader may receive the version that feels safest to repeat rather than the version that is most useful.
Reconstruct the Service as a Timeline
“Everything went wrong” is not an operational explanation.
A difficult service should be reconstructed in sequence.
What was the original forecast? How many guests were expected? When did actual demand begin to differ from the plan? Was the mise en place completed and checked before opening? Did a banquet schedule or reservation pattern change? When did the first delay appear? At what point did the team recognise that it was losing control?
Useful evidence may include:
- covers by service period;
- reservation and arrival patterns;
- banquet event orders and last minute amendments;
- POS or kitchen display ticket times;
- room service order volumes;
- preparation and handover records;
- stock shortages and unavailable menu items;
- equipment failures;
- staffing deployment and unexpected absences;
- voids, complimentary items and guest complaints;
- observations from the pass, dining room and guest facing teams.
The objective is not to create an impressive report. It is to locate the point where the planned operation and the actual operation began moving in different directions.
Sometimes the decisive moment occurred during service. Often it occurred hours earlier.
A section may have opened behind schedule because the preparation plan was unrealistic. A delivery problem may have been known but not escalated. A conference timing change may have reached one department but not another. Staffing may have matched the forecast but not the complexity of the menu or guest profile.
The failure visible to the guest is not always where the failure began.
Listen to the People Closest to the Problem
The Executive Chef does not see every part of a service.
A commis may have noticed that a preparation was running low before anyone else. The Restaurant Manager may know exactly when guests began losing patience. The stewarding team may have experienced an equipment or supply problem that slowed production. The banquet chef may have received a revised timing that was never communicated clearly to the restaurant kitchen.
Useful questions are specific:
- What was the agreed plan?
- What changed?
- When did you first recognise the problem?
- Who was informed?
- What action was taken?
- What support was missing?
- What would have prevented the situation from becoming worse?
These questions are different from asking, “Who caused this?”
Listening does not remove leadership authority. It improves the accuracy with which that authority is used.
Separate the Individual From the System
After the facts are established, the leader must distinguish between different types of failure.
A team member may not have been trained adequately. A standard may have been unclear. The workload may have exceeded the capacity of the section. Communication between departments may have failed. The production plan may have been based on an unrealistic assumption.
Alternatively, an experienced person may have ignored a clear instruction, failed to escalate a known risk or repeated behaviour that had already been addressed.
These situations should not receive the same response.
A capability problem needs training. A planning problem needs a better system. A communication problem needs clearer responsibility. A repeated attitude or conduct problem needs accountability.
As explored in Correcting a Team Member Without Humiliating Them, respect does not mean removing consequences. It means making sure the consequence addresses what actually happened.
Correcting one person will not solve a broken production plan. Changing a system will not solve deliberate disregard for an agreed standard.
Good leadership must recognise the difference.
The Guest Experience Must Be Part of the Review
Operational teams sometimes evaluate a service only through ticket times, staffing and production.
The guest experienced something wider.
A delayed course may have interrupted a celebration. Poor communication may have made the wait feel longer. A conference organiser may have worried about the schedule of the entire event. A resort guest may have chosen a particular restaurant for an important evening and left disappointed.
Not every delay becomes a lost guest, but the operation should understand who was affected and what recovery has already taken place.
The General Manager and relevant department leaders should receive a concise factual update:
- what happened;
- how guests were affected;
- which recovery actions were taken;
- what has been stabilised for the next service;
- what still requires investigation;
- when the final corrective actions will be confirmed.
Owners and senior management do not need an emotional account or premature assignment of blame. They need to know that the operation recognises the seriousness of the failure and is responding with control.
Convert the Review Into Specific Actions
A meeting that ends with “we must communicate better” has achieved very little.
Each identified problem should lead to a defined action, an owner and a deadline.
If preparation was late, the production plan may need revised completion times and a formal readiness check.
If orders arrived in an unmanageable concentration, the restaurant and kitchen may need clearer reservation pacing or earlier communication about large tables.
If a banquet timing changed, the procedure for confirming and distributing event amendments should be strengthened.
If equipment failed, a temporary backup and maintenance decision should be documented.
If the problem involved individual performance, expectations and follow up should be recorded clearly.
The result should not be twenty new rules created in reaction to one difficult evening. Too many corrections can add complexity without improving control.
Identify the small number of changes most likely to prevent repetition. Then verify them during the next comparable service.
Do Not Carry Yesterday’s Anger Into Today’s Team
A bad service can damage confidence.
People may question themselves, their colleagues or the leadership of the operation. If the next day begins with uncontrolled anger, the team enters the next service still carrying yesterday’s failure.
A leader does not need to pretend that everything is fine.
The team should understand what was unacceptable and what is now expected. They should also know that the service has been examined, priorities have been established and the operation has a way forward.
Across restaurants, conference hotels, cruise ships and resorts, I have seen that teams recover more effectively when the leader gives them both accountability and direction.
Replaying the failure throughout the day does not strengthen the standard. A clear plan does.
Final Thought
A bad service costs the business once when the guest experiences it.
It costs the business again if the team learns nothing from it.
The morning after should not begin with a search for the most convenient person to blame. It should begin by protecting the guest, stabilising the next service and rebuilding the facts while they are still fresh.
Accountability must follow, but it should be based on what happened rather than who is easiest to accuse.
The strongest leader does not minimise failure. The strongest leader makes sure the operation understands it, corrects it and does not repeat it.
A difficult service should leave the team with more than frustration.
It should leave the business with better judgment.
About The Author
