The phrase reached my office after a particularly difficult morning.
“The problem is front desk.”
I do not remember who said it first. It probably does not matter. Over the years, I had heard similar versions from almost every department in a hotel. Sometimes the problem was housekeeping; at other times, maintenance. Depending on who was explaining what had happened, there always seemed to be enough reasons to show that the difficulty had begun somewhere else.
That morning, however, front desk looked like a fairly convincing candidate.
The hotel was almost full, and we were going through one of those days when a large number of rooms had to change hands within just a few hours. While some guests were still finishing their packing, others had already begun to arrive. Housekeeping was trying to recover the rooms as they became vacant, while front desk simultaneously handled departures, early arrivals, luggage and people asking how much longer it would be before they could settle in.
Close to check-in time, several rooms were still pending. A family that had arrived earlier than expected was waiting in the lobby. They had left their luggage to one side and, every so often, one of them would approach the desk to ask whether there was any news. They were not making a scene or complaining in any particularly uncomfortable way, but their presence alone was beginning to create that quiet pressure every receptionist knows well: each time you looked up, they were still there.
Front desk called housekeeping.
“We need 204 as soon as possible.”
The Executive Housekeeper reorganised the priorities, and a housekeeper temporarily left the room she had been finishing to move to 204. Not long afterwards, the phone rang again. A room assignment had changed and now another room had become the priority.
I do not remember the exact room numbers, nor would there be much point in doing so. What I remember is the sequence: one urgency replaced the previous one before the first had finished being resolved. Housekeeping altered its route, front desk called again and every new request seemed to confirm that this was where the problem had begun.
From the floor, the situation was difficult to justify. Housekeepers had a distribution of rooms, a work sequence and times that could not be compressed indefinitely. Some rooms required little more than the usual cleaning; others were left after check-out in a condition that demanded much more work. One might be missing linen; another might reveal a lamp that was not working or some issue that required maintenance before the room could be released. Constantly changing priorities did not make rooms finish any faster and, at times, produced exactly the opposite result.
So when I was told that front desk was repeatedly disrupting the plan, the conclusion seemed reasonable. I spoke with the team and asked them to define priorities earlier, avoid changing assignments unnecessarily and respect, as far as possible, housekeeping’s work sequence. It was not a particularly sophisticated instruction; it seemed simply to be a matter of order.
Until I heard front desk’s version.
From behind the counter, there was no orderly sequence of pending rooms. There were people. The family waiting in the lobby needed a particular configuration. Another guest had arrived early because their flight landed in the morning. One reservation required rooms close to each other. Someone had requested an extra bed. A frequent guest had asked whether there was any possibility of checking in ahead of schedule and, while all of that was happening, more guests continued to arrive with reservations that said exactly the same thing: the room would be available from a certain time.
Front desk was not changing priorities simply because it failed to understand housekeeping’s work. It was changing them because the reality in front of the counter was changing as well.
That made my initial diagnosis considerably more complicated. From housekeeping, front desk appeared to be disrupting an operation that needed method; from front desk, housekeeping appeared to be defending a plan that was unable to react to what was happening with the guests. And both perspectives had enough evidence to support themselves.
For a long time, I interpreted situations like these as coordination problems between people. I thought those responsible needed to talk more, anticipate more, collaborate and understand the needs of the other department better. All of that was true, and I still believe that an important part of hotel operations depends on the quality of those relationships. Yet we could bring front desk and housekeeping together, review what had happened and agree that next time they would communicate better, only for the same argument to reappear weeks later, during another high-occupancy day, in a slightly different form.
I began then to pay attention not only to what the two departments were doing, but to what each of them was able to see.
Front desk knew who had arrived, who was still waiting, what characteristics a reservation required, which guest had requested an early check-in, who was beginning to become impatient and which room assignments could be changed without affecting the stay. Housekeeping held a different kind of information: it knew which rooms were actually close to being finished, which had just become vacant, which had required deeper cleaning, where linen was missing, which housekeeper was furthest along and which apparently straightforward room had just revealed a problem. Maintenance could add a third perspective by knowing whether a fault would take five minutes to resolve or leave a room out of service for an hour.
No one needed to be working badly for conflict to appear. Information was distributed throughout the hotel in much the same way as responsibility, and each department was making reasonable decisions from the part of reality it had in front of it.
That began to change my question. Until then, whenever an operation became stuck, my instinct had been to look for where the error had occurred. If front desk had changed priorities too many times, front desk needed correcting; if housekeeping delayed releasing a room, we had to understand what was happening in housekeeping. It was a natural logic and, many times, the correct one. But not always.
There were situations in which I could find no clear failure inside either department. The problem appeared when reasonable decisions, made from different information, collided at the same point in the operation.
Understanding that did not make procedures or responsibilities irrelevant. A room still had to be cleaned properly, statuses had to be updated, front desk needed to manage assignments with judgement and maintenance had to respond within reasonable timeframes. Some errors genuinely belonged to a department and had to be corrected there. What began to change was my tendency to assume that every conflict could be explained in that way.
I started paying closer attention to the places where one department’s work ended and another’s began. A room could be clean but not yet inspected; inspected but still carrying a maintenance issue; repaired but with the change not yet reflected in the system. Front desk could have a room that was technically available but unsuitable for the family waiting, while housekeeping could still be working on a priority that had stopped being one ten minutes earlier.
Between one status and the next, there was always a person, a communication or a decision. And very often it was there, in those small spaces between departments, that the difficulty appeared.
That also explained why some interdepartmental disputes could survive for years even as the people involved changed. One receptionist left and another arrived, an Executive Housekeeper changed or a new manager joined. For a while it seemed that the problem had disappeared and then, under certain conditions, it would return almost in the same words.
If the conflict survived the people involved, perhaps it did not always belong to them.
For whoever was managing the hotel, that possibility was less comfortable. It was much easier to ask two people to understand one another than to accept that the organisation itself might be leading them to make decisions from different versions of reality.
That was why we began working differently. It was no longer only a question of increasing communication, but of making sure the information capable of changing the other person’s decision actually travelled. Front desk did not merely need to know which rooms were pending; it needed to know which could realistically be finished first. Housekeeping did not need to receive only a room number accompanied by the word “urgent”; it needed to understand what problem front desk was trying to solve.
The difference might seem small. “I need 204 urgently” forced housekeeping to alter its sequence in order to produce one specific room. “I have a family waiting and I need a room with this configuration” opened other possibilities. Perhaps 204 would take forty minutes while 218 could be ready in ten. If both worked for the same reservation, no one needed to work faster; the two departments needed to share the problem more effectively.
The same applied in the other direction. Saying that a room “still wasn’t ready” gave front desk very little to work with. Explaining that it needed another ten minutes, that a maintenance intervention was still pending or that another room would be more practical made a decision possible.
Over time, I began to value those small differences in operational language. Not because they solved every conflict on their own, but because they forced us to stop transmitting only a demand and start sharing the reason behind it.
There were, naturally, days when front desk managed priorities badly, rooms that housekeeping took longer than reasonable to release, maintenance issues that were not reported in time and statuses someone forgot to update. No system turns hotel operations into a perfect sequence. What I stopped assuming was that every friction between departments had to end with one of them being right.
Over time, I recognised the same logic in other parts of the hotel. Each department inevitably built an image of the operation from the place where it worked. The difficulty appeared when any of us confused that partial image with the hotel as a whole.
Much later, during another high-occupancy morning, I passed through the front desk while several people were waiting to check in. Housekeeping still had rooms pending, and I heard a receptionist speaking on the phone with the Executive Housekeeper.
“I have a family waiting. Which is the first room you can actually give me?”
There were a few seconds of silence. The answer was a different room number from the one originally assigned.
The receptionist looked at the reservation, checked the room configuration and made the change.
“Perfect. Then I’ll reassign that one.”
The conversation ended there. A few minutes later, the status change appeared in the system. The receptionist prepared the key, placed the documentation in the small envelope and called the guest. The family stood up from the lobby chairs, picked up some of their luggage, approached the desk and shortly afterwards walked towards the lifts.
They never knew which room had originally been assigned, which housekeeper had been finishing which room, what priorities had changed or what conversations had taken place between front desk and housekeeping. For them, there was simply a room available and a key that had just crossed the counter.
For years, whenever something did not work, I had tried to discover where the problem was. Sometimes it was at front desk; at other times, in housekeeping, maintenance or any other department. But I had also made the mistake of looking inside a department for a failure that existed only in the space separating it from the next one.