How to develop employees on the job, not on training day

I used to think developing my team was something that happened somewhere else, on the training days that never quite got scheduled, in the modules nobody had time for, in the annual review where I finally sat down and told a person how they had done all year. I waited for those windows, and they kept not coming, and meanwhile the actual growth of my people was happening or not happening right in front of me, every shift, in moments I was too busy to notice I was wasting. The day I understood that the shift itself was the training was the day I got better at this job.

Across night audit, a front desk in Waikiki, and rooms operations in San Francisco with teams of sixty to ninety and up, the people who grew fastest were almost never the ones who got the most formal training. They were the ones whose managers coached them in the small live windows an ordinary shift throws off constantly, if you are watching for them. This piece is about how to use those windows, because they are the real engine of developing employees on the job, and almost everyone lets them slide by.

The name for this is plain, even if the practice is not.

The rest of this piece is really three ways to use the windows an ordinary shift already hands you.

Why does formal training do so little?

I am not against training programs. They have their place, especially for systems and safety and the things that must be taught the same way every time. But formal training has a structural weakness that no amount of good content fixes: it happens away from the moment the skill is needed. You learn how to handle an upset guest in a quiet room on a Tuesday, and then three weeks later a real upset guest is in front of you at hour nine of a busy shift, and the calm classroom version has evaporated. The gap between knowing something in theory and doing it under pressure is enormous, and formal training lives entirely on the wrong side of that gap.

Live coaching lives on the right side. When I coach an agent thirty seconds after they handled a hard guest, the moment is still warm. They can feel exactly what I am talking about, because it just happened in their own hands. The lesson attaches to a real memory with real adrenaline in it, and that is the kind of learning that sticks. This is why I stopped saving my development energy for training days and started spending it on the floor, in the flow of the actual work. The desk is the classroom, and the class is always in session.

This is one of the four pillars of frontline hospitality leadership, and the one that pays off latest and matters most. You are not just running tonight's shift. You are quietly building the people who will run next year's, and the raw material for that is the ordinary hours you are already standing in.

The thirty-second debrief

The single most useful development tool I have is a habit that costs almost nothing: the short debrief in the quiet gap right after something happened. An agent walks a guest through a difficult room change. A minute later, when the lobby breathes, I catch them and say a version of "that was well handled, and I noticed one thing." Thirty seconds. Then back to work. Done a few times a week, per person, over months, this does more than any workshop.

What makes the debrief so efficient is that it costs almost none of the shift. I am not pulling anyone off the floor or scheduling anything or interrupting the flow of service. I am using a gap that already exists, the natural breath after a busy stretch, and spending it on one specific observation. Over a month those tiny investments compound into a person who is visibly sharper, and I never once had to find a free hour, because the hour was never coming and the gaps always do.

The reason it works is timing. Right after the moment, the person's memory of it is vivid and their defenses are down, because they are usually a little curious how they did. If I wait until a review three weeks later to mention it, the details have gone soft for both of us, the emotional charge is gone, and the feedback arrives as an abstract judgment instead of a live lesson. Proximity to the moment is most of the power. This is close cousin to giving feedback in the moment, and the two skills reinforce each other: the debrief is just feedback with a little reflection attached.

The classroom is the desk. The lesson is whatever just happened in their hands.

The debrief is not only for corrections. In fact I try to make most of them positive, because catching someone doing it right is at least as instructive as catching them doing it wrong, and it builds the relationship that makes the corrective ones land. When I name specifically what an agent did well, "the way you slowed your voice down when the guest got loud, that is exactly it," I am not just being nice. I am helping them see and repeat a thing they may have done by instinct, turning an accident into a skill they now own on purpose.

Hand people more than they think they can carry

People grow in the gap between what they can do alone and what they can do with support nearby. If I only ever give an agent tasks they have fully mastered, they stay exactly where they are, competent and stagnant. Growth requires stretch, which means handing someone a thing that is a little beyond their current reach and then staying close enough to catch a real fall without hovering over every step.

So I look for chances to hand off something real. Let the newer agent take the VIP arrival while I watch from six feet away, ready but not intervening. Ask the steady midlevel person to run the desk for twenty minutes while I step away, so they feel the weight of being the one others turn to. Give the quiet one who never volunteers the guest recovery that needs a careful touch. Each of these is a rep they could not get from a manual, and each one tells the person something more important than the task itself: I think you can handle this. People grow into the trust you extend to them, or they leave to find someone who will extend it.

How to stretch someone without setting them up to fail

• Pick the right size of stretch. Just beyond their reach, not miles past it. Too small and nothing grows; too large and you set them up to fail publicly, which teaches fear, not skill.
• Stay close, not on top. Be near enough to step in before a real guest is harmed, far enough that the person genuinely owns the outcome. Ownership is where the learning lives.
• Let them keep the win. When it goes well, make sure the credit is theirs, out loud. When it wobbles, debrief it privately and without heat, as a rep, not a verdict.
• Debrief either way. Success and struggle both teach, but only if you close the loop with a short conversation about what happened and what to try next time.

Ask more than you tell

The fastest way to solve a problem on a busy floor is to solve it myself. I know the answer, I say the answer, the guest is handled, we move on. And every time I do that, I have solved today's problem and taught the agent nothing, because I did the thinking for them. If I do it enough, I train a team that brings me every decision instead of making their own, and then I wonder why no one on my desk can handle anything without me.

So when the stakes allow it, and often they do, I try to ask instead of tell. An agent comes to me with a stuck situation, and instead of handing them the solution, I ask "what are you thinking?" or "what are your options here?" Most of the time they already have the answer and just wanted permission or reassurance, and the question hands both of those to them while leaving the thinking in their hands. Over time this builds judgment, which is the thing you actually want in your people, the ability to decide well when you are not there.

This takes patience and a tolerance for the extra thirty seconds it costs in the moment. When the lobby is on fire, I will just give the answer, because the guest comes first and a live crisis is not a teaching moment. But most of the shift is not on fire, and in the ordinary stretches the question is almost always the better move. The manager who answers everything builds dependence. The manager who asks the right questions builds people who no longer need the questions. That patience is also how you start to see who is ready for more, which connects directly to learning to identify leadership potential in the agents already on your floor.

A worked example: coaching one agent across one shift

To make this less abstract, here is a single ordinary evening with one newer agent, and the three small windows I used without ever leaving the floor or scheduling a thing.

1. The stretch, early. A VIP arrival came up that she had never handled alone. Instead of taking it myself, I told her it was hers and moved six feet away to my own guest, close enough to step in, far enough that she owned it. She got through it with one small wobble on the room preferences and recovered on her own.
2. The debrief, a minute later. When the lobby breathed, I caught her for thirty seconds: "The way you confirmed the arrival by name before you pulled the folio, that is exactly right. One thing for next time, preload the preferences from the profile before they reach the desk." Named the win first, one specific tweak, then back to work.
3. The question, an hour on. She came to me stuck on a rate dispute. Instead of solving it, I asked, "What are your options here?" She already had two and just needed permission to pick one. I handed the thinking back, and she made the call herself.

None of that cost me a scheduled minute. The stretch, the debrief, and the question all fit inside the shift I was already running, and by the end of the night she had done three things she could now repeat without me. That is development on the job: not a program, a way of using the windows the work keeps handing you.

Development is a habit, not an event

The habit sits inside the same minutes as the managing, which is why it is so easy to skip. Seeing the two next to each other helps.

Good floor leaders do both at once, and the coaching column is the one that quietly disappears under pressure unless you protect it.

The thread through all of this is that developing people is not a thing you schedule. It is a way of paying attention that runs underneath everything else you do on the floor. The debrief, the stretch task, the question instead of the answer, none of these require a program or a budget or a free afternoon. They require you to hold, alongside the work of running the shift, a second quiet question: who is growing right now, and what is the next small thing I can hand them?

I will be honest that this is hard to sustain, because the operational pressure of a live shift always argues for the fast path. It is faster to do the task myself. It is faster to give the answer. It is faster to let the strong agent handle everything while the newer one watches. Every one of those fast choices is a tiny loan against the future, borrowed from the growth of my team, and a floor run entirely on fast choices eventually finds itself thin, with one or two people who can do everything and a bench that never developed. The managers I respect most are the ones who pay a little tax of slowness now, in the reps they hand out, so that in a year they have a deep team instead of a fragile one.

So if you take one thing from this, let it be that you already have everything you need to develop your people. You do not need a training day to arrive. You need to notice the windows the shift is already handing you, the quiet gap after a hard guest, the arrival you could let someone else take, the problem you could ask about instead of solve. Use those windows, one small rep at a time, per person, over months, and you will look up one day to find a team that is visibly better than the one you started with, grown not on a training day but on a thousand ordinary shifts, which is the only place people have ever really grown. Coach in the windows you have, and the classroom takes care of itself.