Spend a morning in the back of house of any hotel and you will find technology that was not designed for the people using it.
I don’t mean this as a complaint. I mean it as a diagnostic. When staff develop elaborate workarounds paper supplements, WhatsApp groups, handwritten sticky notes on monitor bezels it is because the software does not fit the workflow. The workarounds are evidence. They tell you exactly where the gaps are.
The people the software is not designed for
Hotel technology is mostly designed for two audiences: the guest, and the general manager reviewing reports. The people in between the front desk agent at 2am, the housekeeping supervisor allocating 28 rooms across 6 attendants, the maintenance engineer tracking a broken HVAC unit across three work orders are frequently an afterthought.
This shows up in the tools themselves. PMS interfaces designed for desktop screens, used on iPads in cramped housekeeping offices. Reporting dashboards with 40 filters, used by people who need to know one thing: which rooms are clean right now. Communication systems that require logging into a separate platform, used by people whose hands are full of cleaning supplies.
The result is predictable: staff use the official system for what they must, and route around it for everything else.
What a housekeeping supervisor actually needs
I spent several weeks studying housekeeping workflows while building the housekeeping demo project. What I found was that the job has a surprisingly small set of core information needs, and most technology meets none of them well.
The morning allocation. At the start of each shift, the supervisor needs to know: how many rooms need servicing, what type of service (checkout clean, stay-over, turndown), in what order, and assigned to which attendant. This is a scheduling and logistics problem. Most PMS housekeeping modules treat it as a reporting problem they show you the data, but the allocation logic is manual.
Real-time status. As the shift progresses, the supervisor needs to know where every attendant is and what every room’s current status is. Guests checking out late, rooms needing maintenance, attendants who have fallen behind all of these require rapid reallocation decisions. The data exists in the PMS; the problem is that it’s not surfaced in a form that supports fast decision-making.
Communication without friction. When a room needs something a maintenance report, a guest request, an inspection the supervisor needs to route that to the right person immediately. Most hotels use WhatsApp for this because it’s faster and more reliable than any purpose-built tool they have been given.
Exception handling. The routine cases clean this room, check this out are handled. The exceptions guest left pets in the room, maintenance blocked a bathroom, VIP arrival requires special setup are where things fall apart. Most systems have no exception workflow; staff improvise.
What a front desk agent actually needs
The front desk role is often the most over-tooled and under-supported position in the hotel.
Over-tooled: the agent typically has access to the full PMS, the channel manager, a separate messaging platform, a key system, a payment terminal, and possibly a CRM. None of these talk to each other fluently.
Under-supported: when a guest arrives with a problem wrong room type booked, billing dispute, special request that wasn’t communicated the agent has to navigate between systems to find the relevant information, often while the guest stands at the desk waiting.
What the agent actually needs in that moment: a single view of the guest’s reservation, history, preferences, and any notes readable in under 10 seconds. Most systems provide something closer to a relational database browser.
The design principle that most hotel tech vendors miss
The people using hotel staff tools are not sitting at a desk with time to think. They are moving, often carrying things, frequently interrupted, and making decisions at a rate that would overwhelm most office workers.
Every interaction with a staff tool needs to be completable in under five seconds with one hand. That constraint eliminates most of what hotel tech vendors consider “features.”
The tools that work in hotel operations share a specific quality: they reduce the number of decisions the user has to make, not increase them. A good room assignment interface doesn’t show you all the available rooms and let you pick it shows you the recommended assignment based on guest preferences, room status, and operational logic, and asks you to confirm or override.
The difference between a tool that reduces decisions and one that requires them is the difference between technology that gets adopted and technology that gets routed around.
Why vendors keep getting this wrong
The fundamental problem is that the people who buy hotel software are rarely the people who use it daily. A GM evaluating a PMS in a sales demo is seeing a curated workflow. The housekeeping supervisor who will use it every day for the next three years was not in that meeting.
Sales cycles optimise for features that are easy to demonstrate. Operational fit how the software behaves on a Tuesday afternoon when three rooms have maintenance issues, one attendant called in sick, and a bus group is checking out is hard to demonstrate and therefore rarely evaluated before purchase.
The result is a market full of software that looks good in demos and causes pain in operation. The opportunity for anyone building hotel staff tools is not to add more features. It is to remove the decisions that staff shouldn’t have to make.