The complaint is rarely the root cause
A Hospitality Assured thought leadership article on investigating service failures thoroughly and using the findings to achieve lasting improvement
When a customer complains, the natural response is to correct the immediate problem. The meal is replaced, the room is revisited or the delay is explained with an apology.
These actions may recover the customer’s confidence, but they do not necessarily prevent the same failure from happening again. Unless the organisation investigates why the problem occurred in the first place, it risks repeatedly treating the symptoms while leaving the underlying cause hidden.
A story told by Horst Schulze, co-founder of The Ritz-Carlton Hotel Company, illustrates this particularly well.
One hotel was receiving persistent complaints about slow breakfast room service deliveries. The initial response was to focus on the room service operation. Managers spoke to the relevant colleagues, reinforced expectations and even introduced additional resources. Nevertheless, the complaints continued.
Eventually, a manager followed a breakfast order through the complete service journey. The order was taken correctly, the food was prepared on time and the tray left the kitchen as expected. The delay occurred when the colleague reached the service lift and waited much longer than anticipated.
The investigation could easily have stopped there, with the lift identified as the problem and engineering asked to examine it. However, the manager continued to delve and investigate. He used the stairs to observe what was happening to the lift on the upper floors. It became apparent that housekeeping colleagues were lodging the lift doors open with laundry trolleys while they collected and turned around linen.
Once again, it would have been easy to conclude that housekeeping colleagues were causing the delay and instruct them to stop. Instead, the manager asked why they needed to hold the lift. Housekeeping was short of linen was the answer. Colleagues were under consistent pressure to recover used linen and return it to the floors quickly enough to prepare rooms. Holding the lift was their practical response to an operational problem.
The investigating manager then asked why the department was so short of linen.
The answer took them back to a decision made before the hotel opened. As the opening budget came under pressure, the planned purchase of additional linen had been shelved. A decision intended to save money had created an operational constraint that affected housekeeping, restricted the service lift and ultimately caused room service breakfasts to arrive late.
The guest experienced a late breakfast. The root cause was a purchasing decision made elsewhere in the organisation, long before the tray left the kitchen.
Looking beyond the point of failure
This example demonstrates why proper root cause analysis matters. Service failures rarely occur in isolation. They are often the final, visible consequence of several connected decisions, pressures and processes.
If the investigation had concentrated only on the colleague delivering the breakfast, the hotel might have concluded that the individual needed further training or needed to work more efficiently. That would have been both unfair and ineffective.
If it had stopped at the lift, the organisation might have called an engineer to examine equipment that was operating correctly.
If it had stopped with housekeeping, colleagues might have been told not to obstruct the lift without anyone addressing the linen shortage that caused them to do so.
Each of these responses would have created activity. None would have removed the root cause.
This distinction is important. Completing an action is not the same as solving a problem.
Root cause analysis should not become a search for blame
Effective investigation requires an environment in which colleagues feel able to explain what is actually happening. People are less likely to speak openly if they believe the purpose is to identify who should be blamed.
The housekeeping colleagues in this example were not deliberately undermining room service. They were trying to meet another customer requirement: preparing bedrooms on time despite insufficient linen stock.
Their actions made sense when viewed from within their own area of responsibility. The wider problem only became visible when the complete tray journey was examined across departmental boundaries.
Leaders should therefore approach root cause analysis with curiosity rather than judgement. The most useful questions are not ‘Who caused this?’ or ‘Who failed to follow the procedure?’ They are:
- What happened?
- Where in the customer journey did performance begin to depart from the required standard?
- What conditions made that happen?
- Why did the actions taken by colleagues appear necessary at the time?
- Which earlier decision, process or resource constraint contributed to the failure?
- What must change to prevent it from recurring?
The familiar Five Whys technique can support this process, but the value does not come from mechanically asking the same question five times. It comes from continuing the investigation until the organisation reaches a cause it can meaningfully address.
Follow the evidence
Good root cause analysis combines information from several sources. Customer feedback identifies how the failure was experienced. Performance data may reveal its frequency or pattern. Process mapping shows where delays and handovers occur. Most importantly, conversations with the colleagues doing the work explain the operational reality behind the process.
There is particular value in physically following the service journey. Procedures describe how a service is intended to operate; observation reveals how it actually operates.
This may expose competing priorities, workarounds, unclear responsibilities, resource shortages or decisions made within one service area that unintentionally affect another. These connections can remain hidden when departments review performance separately.
Closing the loop
Identifying the root cause is only part of the process. The organisation must agree an action, allocate responsibility, set a timescale and subsequently confirm whether the action has resolved the problem.
This means returning to the original evidence. Have complaints reduced? Has the delivery time improved? Do colleagues report that the obstacle has been removed? Has the change created any unintended consequences elsewhere?
The findings should also be shared with the colleagues involved. Too often, people contribute to an investigation but never hear what was decided or what changed as a result. Closing this loop demonstrates that their knowledge is valued and encourages greater participation in future improvement.
Hospitality Assured encourages organisations to use customer and colleague feedback as a source of learning and continuing improvement. This requires more than recording complaints and confirming that an immediate response was provided. Strong organisations examine patterns, involve the people closest to the work and follow the evidence across traditional departmental boundaries.
A late breakfast may appear to be a room service problem. As Schulze’s example shows, however, its origins may lie several decisions away from the moment the customer was frustrated by a late breakfast.
The question is not simply whether the complaint was resolved. It is whether the organisation understood why it happened and made certain that it would be less likely to happen again.
