The Mistake You See May Not Be Where the Problem Started

Leadership in Practice · Leadership

A guest arrives at the hotel at the expected check-in time.

The room is not ready.

They may have travelled for hours, perhaps after a long flight, and the last thing they want to hear is that they need to wait.

The complaint reaches Front Office. Someone calls Housekeeping.

Why isn’t the room ready?

Attention quickly moves towards the room attendant, the supervisor or whoever was responsible for releasing it.

Sometimes that is exactly where the problem is.

But not always.

The previous guest may have left late. Engineering may have needed access to the room. A last-minute room change may not have been communicated properly. Housekeeping may have received updated departure information too late. The team may have started the day short-staffed.

Or the room attendant may simply have failed to meet the expected standard.

Every one of those situations produces the same visible result:

the guest is waiting.

But they are not the same problem.

And if leadership reacts only to what is visible at the end, the cause may still be there tomorrow.

The problem may have started earlier

Hospitality is full of situations like this.

The guest sees a room that is not ready.

The manager sees the employee closest to that room.

But the sequence that caused the delay may have started hours earlier.

This is where judgment matters.

The immediate responsibility is still the guest.

Apologise. Give a clear answer. Find the best possible solution.

Once the situation is under control, however, another job begins.

Understand what happened.

Not who can be blamed fastest.

What happened.

That distinction changes the quality of the decision that follows.

What could the person actually control?

When I look at a performance problem, one of the first things I want to understand is what the person could reasonably control.

A room attendant can control the quality and pace of their work.

They cannot control a late departure that was never communicated.

A receptionist can control how clearly they speak to the guest.

They cannot update a room status they have not received.

A chef can control the production in front of them.

They cannot accurately produce for numbers that keep changing without reaching the kitchen.

This does not remove accountability.

It helps place it where it belongs.

If the person had the right information, enough time, proper training and the necessary tools, then their choices matter.

If some of those conditions were missing, that has to be considered as well.

Look at the conditions around the work

The conditions surrounding performance are often less visible than the mistake itself.

Was the information accurate?

Did it arrive on time?

Was the workload realistic?

Were responsibilities clear?

Had priorities changed during the shift?

Were several departments working from the same information?

Sometimes this is where a manager discovers that what looked like an individual failure was partly created somewhere else.

There is also a more uncomfortable possibility.

Sometimes the manager is part of the system.

If priorities keep changing, instructions are inconsistent or information is passed badly, repeatedly telling the team to “communicate better” will not fix much.

The communication problem may be above them.

It is easier to correct the employee standing in front of you than to admit that the way the operation is being managed is contributing to the result.

But easier does not mean correct.

Look for what repeats

One late room can be one late room.

Five late rooms, involving different attendants on different days, deserve a different kind of attention.

What do those situations have in common?

Perhaps the same floor.

The same departure period.

The same handover.

The same communication gap between Front Office and Housekeeping.

The same staffing issue.

The same weak point in the workflow.

When the names change but the problem does not, the common elements become more important.

That does not prove the system is responsible.

It tells you where to look next.

The same logic applies across the operation

A kitchen repeatedly overproduces for dinner.

The first reaction may be that the chefs are not controlling quantities properly.

Maybe they are not.

But what information are they producing from?

If occupancy numbers arrive late, restaurant covers keep changing, groups appear at short notice and par levels are unclear, the problem cannot be understood simply by looking at the chef standing beside the excess food.

The same applies when receptionists repeatedly give different information to guests.

Or when managers keep missing the same report.

Or when the same item runs out during service even though different people prepared the mise en place.

At some point, repeating the same correction stops being enough.

Someone has to look further back.

The system cannot become an excuse

There is another side to this.

Once we start examining process, communication and working conditions, it can become too easy to explain away poor performance.

That would be equally wrong.

Sometimes the information was clear.

The standard was understood.

The training was done.

The tools were available.

The workload was reasonable.

And the person still did not do what was required.

Leadership has to recognise that too.

Looking beyond the individual is not about avoiding difficult conversations.

It is about making sure we are having the right conversation, with the right person, for the right reason.

Change the conditions, then watch

If the conditions appear to be contributing to the problem, change what can reasonably be changed.

Improve the handover.

Clarify the room priority list.

Change when departure information is shared.

Adjust staffing where possible.

Remove an unnecessary step.

Make sure two departments are not working from different versions of the same information.

Then observe what happens.

What changes on the next busy arrival day?

Do the same delays continue?

Does most of the team improve while one person still struggles?

Does the problem largely disappear?

Once something in the operation has changed, the next result becomes useful evidence.

And that evidence is usually more valuable than another warning delivered immediately after a difficult service.

Be careful with easy labels

Hospitality has a few words that can close an investigation very quickly.

Careless.

Slow.

Lazy.

Negative.

Bad attitude.

Sometimes those words may eventually describe a real problem.

But once a label is attached to someone, it can become difficult to see anything else.

A mistake confirms the label.

A question sounds like resistance.

A difficult day becomes proof of poor attitude.

That is why I prefer labels to come late.

First understand what happened.

Then look at the conditions around it.

Then see whether the problem repeats.

Only after that should judgment become firmer.

Control. Conditions. Pattern.

I do not believe every operational problem needs a complicated framework.

But before making a serious judgment about someone’s performance, three things are worth understanding.

What could the person reasonably control?

What conditions were they working under?

Does the problem follow that person, or does it keep appearing without them?

Sometimes those questions will confirm that the problem is individual.

Sometimes they will show that the operation needs attention.

Often, responsibility will sit on more than one side.

That is normal.

Hospitality is rarely as simple as the incident we see at the end.

The guest is waiting. The leader has two problems to solve.

Go back to the guest whose room was not ready.

There are really two responsibilities.

The first is immediate: look after the guest.

The second comes afterwards: understand why the room was late.

If the attendant failed, deal with it.

If the handover failed, fix it.

If the planning was unrealistic, change it.

If leadership contributed to the confusion, acknowledge that too.

Correcting the wrong person may close today’s incident.

It will not prevent tomorrow’s.

The mistake we see is sometimes only the final step in a much longer sequence.

A leader needs to understand where that sequence actually began.

About The Author