Teach new hires to make people feel seen, because training hospitality staff is more than the steps

Every new hire I have onboarded learns the property management system faster than I expect. The buttons, the room types, the checkin sequence, all of it clicks into place within a week or two, because it is finite and it is teachable and there is a right answer for every screen. Then I watch that same person stand at the desk, technically flawless, and completely miss the tired guest in front of them who needed a slower pace and a warmer word. They did everything right and the guest still walked away feeling processed. That gap is the whole reason training is hard.

Because the part that matters least is the part that is easiest to teach, and the part that matters most barely fits in a manual. Anyone can learn to run a checkin. Very few people arrive knowing how to make a stranger feel, in the space of two minutes, like the hotel had been waiting for them. That feeling is the actual product, and if all your onboarding does is teach the steps, you will produce agents who are correct and forgettable. What I want to lay out is how I try to teach the other thing, the instinct, because I do believe it can be taught even though it does not sit in a checklist.

I lead rooms operations across teams that run from sixty to ninety and more, front office and housekeeping together, which means I cannot personally be at every desk shaping every interaction. So the question is not just how I serve a guest well. It is how I build people who serve guests well when I am nowhere near them. That is a training problem, and it is the one I find most worth getting right.

Why do the steps come easy and the instinct come hard?

The steps are concrete. There is a screen, an action, a result you can check. You can watch a new hire do a checkin and know instantly whether they did it correctly. That feedback loop is fast and clean, which is exactly why the tasks land quickly. The instinct is the opposite. It is about noticing, about timing, about reading a person who is not going to tell you what they need. There is no screen for that, no clear right answer, and the feedback is slow and fuzzy.

So most onboarding defaults to the measurable part, because it is the part you can build a checklist around and sign off on. The new hire passes the system test and gets called trained. But the guest does not experience the system. The guest experiences whether the person behind the desk actually saw them. This is why I think about training as two curricula running in parallel: the tasks, which are the floor, and the judgment, which is everything above it. Teaching only the first produces a technically competent agent who has learned to serve a room number instead of a human, and that is the same failure I keep circling back to in what great hotel service actually is.

You are not really training someone to run a desk. You are training them to pay attention to people while the desk runs itself. Once I framed it that way for myself, the whole approach changed. The system training becomes the prerequisite you get out of the way quickly, so that the real teaching, the noticing, has room to happen.

Teach the why under every step

The single most important shift is to never teach a step without teaching what it is for. A new hire who is told "confirm the departure date at checkin" will do it mechanically and drop it the moment the shift gets busy. A new hire who is told "confirm the departure date because a guest who has to sort out a wrong checkout on their last morning leaves with that as their final memory" understands what the step is protecting, and now they will protect it even under pressure, and they will improvise around it when the situation does not fit the script.

This is the difference between a rule and a reason. Rules break the second reality gets messy, because the person following them has no idea which ones are load-bearing. Reasons bend and adapt, because the person carrying them knows what they are actually trying to achieve. Every standard I teach, I try to attach to the guest feeling it exists to create. When a new hire knows the why, standards stop being a cage and start being a shared language, which is exactly how service standards that don't feel scripted are supposed to work in the first place.

Teach someone the step and they follow it until it is inconvenient. Teach them the reason and they defend it when it is hardest.

The same step, taught two ways

It helps to see the difference laid side by side, because the phrasing of the training is what determines whether a new hire freezes or improvises when reality does not match the manual.

The left column produces compliance. The right column produces judgment, because the new hire now knows the target and can hit it a hundred different ways when the exact script does not fit the guest in front of them.

Can you actually teach the instinct?

I get asked this a lot, usually by people who believe warmth is something you either have or you do not. I think that is half right. You cannot install genuine care in someone who does not have it, which is why hiring matters so much and why I weight warmth and coachability over polish every time. Polish I can teach in weeks. The underlying disposition to care about a stranger's comfort is much harder to add later, so I try hard to hire for it at the door.

But given a person who has that care, the instinct itself, the practical skill of turning care into the right action at the right moment, absolutely can be taught. Instinct at the desk is really just attention plus permission. Attention means noticing the pace, the posture, the tone, the small signals a guest gives off about what they need. Permission means the freedom to act on what you noticed without checking with someone first. Both are coachable. I can teach a new hire to watch for the guest who is short and tired and to read that as fatigue rather than rudeness, and to respond with speed instead of chatter. That is a learnable read, not a personality trait.

It is worth pinning that idea down, because once you name it the training gets concrete.

Broken into those two parts, instinct stops being a personality trait and becomes a pair of things you can coach.

How I actually build the instinct on shift

• Model it live. I take the interaction while they watch, then name out loud what I noticed and why I adjusted.
• Hand it over early. They take real guests sooner than feels comfortable, with me close enough to catch anything.
• Debrief the human part, not just the system part. After a checkin we talk about the guest, not only the screens.
• Pair them with the strongest people, because instinct spreads by watching far faster than by instruction.
• Catch them doing it right. When a new hire reads a guest well, I name it immediately so they know what the target feels like.

That last one matters more than people expect. New hires are usually braced for correction, so when the feedback is "the way you slowed down for that guest was exactly right," it lands hard and it sticks. You are not just fixing errors, you are pointing at the moments where the instinct showed up so they can recognize it and do it on purpose next time.

The common mistakes I watch trainers make are worth naming, because avoiding them speeds everything up. The first is front-loading the system and never circling back to the human part, so the new hire concludes the tasks are the job and the noticing is optional. The second is correcting only the misses and never naming the hits, which teaches a hire what not to do but never what the target feels like. The third is rushing a hire onto the floor solo before anyone has debriefed a single real interaction with them, so they build habits nobody has checked. The fourth is modeling the read silently, taking a lovely interaction while the new hire watches but never saying out loud what you noticed or why you adjusted, which leaves them to guess at the invisible part. Every one of these produces a technically fine agent who never quite connects, and every one is fixable by slowing down and talking about the guest, not just the screen.

I also lean hard on the night shift as a teacher, when the schedule allows it. My own instinct was built doing audit at a Waikiki resort, where the lobby goes quiet and there is no manager to hand a guest to. Nights strip service down to the bones: it is just you, a tired guest, and whatever judgment you have. A new hire who gets a stretch of calmer overnight hours, paired with someone steady, learns to sit with a guest and actually read them, without the churn of a busy day shift pulling their attention in ten directions. It is not that nights are easy. It is that they force the noticing, because there is nothing else to hide behind, and that pressure teaches faster than any classroom module.

Permission is part of the training

Here is a piece that a lot of onboarding misses entirely. You can teach a new hire to notice everything and it will not matter if they do not believe they are allowed to act. A team that has learned it must escalate every exception has learned that its own judgment is not trusted, and a new hire absorbs that lesson fastest of all. So part of training the instinct is explicitly telling people, out loud and early, that they are trusted to solve a guest's problem without finding a manager first, and then backing them the first time they do.

That first backed decision is a training moment more powerful than any classroom hour. When a new hire takes a small risk to take care of a guest and the response from me is support rather than a lecture about process, they learn that the permission is real. After that they will keep reaching for it. If instead they get corrected for coloring outside the lines, they retreat to the safe, scripted, forgettable version of the job, and no amount of teaching the instinct will pull them back out. This is why so much of great training is really about trust, the same trust I write about in empowering the frontline to say yes. You cannot teach someone to make guests feel seen and simultaneously signal that you do not see or trust them. The two have to match.

How long does this really take?

The honest answer is that the tasks take days and the judgment takes months. I am wary of any program that promises a fully formed front desk agent in a week, because a week is enough to learn the system and nowhere near enough to build the read. What speeds it up is not compressing the training but tightening the feedback: real shifts, real guests, and a strong person debriefing the human moments close behind so the lessons land while they are fresh.

What I have learned to be patient about is the gap between competent and warm. A new hire will hit technical competence long before the instinct catches up, and that in-between stage, correct but not yet connecting, is uncomfortable to watch and tempting to rush. But rushing it just teaches them to fake warmth, which guests read as insincere instantly. The instinct arrives on its own timeline, sped along by good modeling and honest feedback, and one day you watch a hire you onboarded read a guest perfectly without being told, and you know the real training finally took.

The other thing patience buys you is retention, which matters more to service than almost anything else. A guest feels the difference between a team that has been together long enough to trust each other and a desk staffed by people who all started last month. When you invest real time in a new hire, teach the why, back their judgment, and celebrate the moments they get it right, they stay, and a team that stays keeps getting better at reading guests together. Rushing people through onboarding to fill a shift produces churn, and churn resets the instinct to zero over and over. The slow, patient version of training is not just kinder. It is the one that actually compounds, because the people you built stick around to build the next ones.

That moment is the whole point of the job for me now. Serving a guest well myself is satisfying, but it ends when the shift ends. Building a person who makes hundreds of guests feel seen, across every shift I am not there for, is the thing that actually lasts. The steps were never the curriculum. The steps were the price of admission to the real work, which is teaching someone to notice another person and to believe they are allowed to do something kind about it. Onboard the instinct, not just the tasks, and you are not staffing a desk. You are multiplying the reason guests come back.