HOLIXORAThe first version of Hanoman check-in was built by engineers who had talked to hotel operators but had not actually stood behind a front desk during a busy morning. It was technically sound. It did everything it was supposed to do. And the feedback from early users was consistent: it was too slow.
Not slow in a performance sense. Slow in a workflow sense. The interface required too many steps to complete a check-in under real operating conditions.
What Fast Actually Means at the Front Desk
During a check-in rush — when multiple guests arrive simultaneously, when the phone is ringing, when a previous guest is asking a question — the interface needs to reduce cognitive load, not add to it. The worst thing a system can do is require the front desk agent to remember where things are, or to complete a sequence of steps that could have been collapsed into fewer.
The original Hanoman check-in required the agent to move through four separate screens to complete what should have been a two-screen workflow. Room assignment, ID verification, rate confirmation, and payment method were on separate pages with no smart defaults.
What We Changed
We rebuilt the check-in screen as a single-page workflow with contextual defaults. The system pre-fills room assignment based on reservation details and room status. Rate confirmation is inline. The only fields requiring manual input are the ones that actually vary per guest.
We also added a keyboard-first navigation mode that experienced front desk staff could use to complete check-in without touching a mouse. Hotel staff who process dozens of check-ins per shift prefer keyboards. The interface had not accounted for that.
The Design Principle We Took Away
Building for the experienced user is different from building for the new user. Onboarding UX and daily-use UX are not the same thing. Hanoman now has different modes — a guided mode for new staff learning the system, and an optimized mode for staff who know what they are doing and want to move fast.
That distinction came directly from watching real users operate in real conditions.