How to hold the difficult conversations with employees

There is a specific weight I used to carry through a whole shift when I knew a conversation was coming. An agent had done something I needed to address, nothing dramatic, a checkin that skipped a step or a tone with a guest that was a little short, and I would spend the next four hours rehearsing, softening, finding reasons the timing was not quite right. The lobby was busy. The person seemed to be having a hard day. Maybe it was a one-off. By the time the shift ended I had usually talked myself out of it entirely, and I walked to my car feeling relieved and quietly ashamed, because I knew I had chosen my own comfort over the agent's growth.

Learning to have these conversations well, without dread and without cruelty, is one of the things that separates a person who holds a title from a person who actually leads a floor. I did not arrive good at it. Across night audit, where the quiet hid small lapses, and busy front desks in Waikiki and later rooms operations in San Francisco with teams of sixty to ninety and up, I built the skill the slow way, one uncomfortable conversation at a time. This is what I have learned, said as plainly as I can.

Why do these conversations feel so hard?

The difficulty is almost never a lack of clarity about the problem. I can usually see the issue perfectly well. The difficulty is that naming it out loud puts the relationship briefly at risk, and a front desk runs on relationships. These are people I stand shoulder to shoulder with through long, strange nights. Telling one of them that their work has slipped feels like it might cost me the warmth we have built, and that warmth is not just pleasant, it is operational. A team that trusts each other covers for each other when a shift goes sideways.

So the fear is rational. What is not rational is the conclusion I used to draw from it, which was to stay silent and call the silence kindness. It was not kindness. It was self-protection dressed up as consideration. The agent I was protecting from a hard truth was quietly drifting toward a worse outcome, a formal writeup, a lost promotion, a reputation on the team, all of which I could have helped them avoid with one clean conversation early. Avoidance always feels generous in the moment and turns out to be the most expensive thing you can do.

This sits at the center of frontline hospitality leadership, where developing a person and protecting a standard turn out to be the same act. You cannot do either if you will not tell someone the truth to their face. The whole craft rests on a foundation of small, honest conversations most people would rather skip.

Be specific, private, and prompt

If I had to compress everything I know about this into three words, those would be the three. Specific, private, prompt. Each one is a discipline, and each one is the opposite of what fear tells me to do.

Specific means I describe the actual behavior, not a vague sense of dissatisfaction and not a judgment about the person. There is an enormous difference between "the last two arrivals skipped the ID check" and "you're getting sloppy." The first is a fact we can both look at, standing side by side, and solve together. The second is a verdict about who they are, and it invites a defense of their character instead of a change in their behavior. The moment a conversation becomes about identity rather than action, it stops being useful. I keep it on the specific, observable thing, because that is the only thing either of us can actually do something about.

Private means exactly what it says. Nobody gets corrected in front of a guest or a coworker. A public correction, even a mild one, humiliates, and a humiliated person does not absorb feedback, they defend themselves and quietly resent you. I take the person a few steps away, to the end of the desk or into the back office, somewhere the conversation belongs only to the two of us. This is non-negotiable for me even when the mistake happened in front of everyone, especially then.

A hard conversation held cleanly is not punishment. It is the respect of telling someone the truth.

Prompt means close to when it happened, at the first calm gap rather than the first convenient one, because convenient never actually arrives. The longer I wait, the bigger the thing grows in my head and the more freighted the eventual conversation becomes. A lapse I could have flagged in thirty seconds the same night turns into a whole sitdown a month later, and the agent is blindsided, wondering what else I have been silently holding against them. Naming it plainly is inseparable from naming it early, which is why I have written separately about the discipline of naming performance problems before they calcify. Timeliness is not just efficiency. It is fairness to a person who deserves to hear it while it is still fresh enough to feel like feedback.

How do you actually open your mouth?

Knowing the principles is not the same as knowing what to say when your heart is going a little fast. So here is roughly how I run one of these, mid-shift, without letting it swell into an event.

1. Open small and low-keySomething like "hey, can I flag one thing real quick" signals that this is a minor course correction, not a summit. The casual frame keeps the person from bracing for a fight before I have said a word.
2. State what you sawJust the observable facts, in one or two sentences, without the story I built about why. My theory of their motive is usually wrong, and leading with it guarantees defensiveness.
3. Say why it mattersA correction with no reason attached feels like an arbitrary rule. When I connect it to the guest who was affected, or the teammate who inherits the mess, the standard stops being my preference and becomes something we both care about.
4. Then stop and listenThis is the step people skip and the most important one. After I name the thing, I go quiet and let them respond. Half the time there is context I did not have: a system that failed, a guest who was abusive off the record, a personal weight they are carrying.
5. Close with what right looks likeI do not leave it at the problem. I say clearly what I need to see instead, so the person walks away with a target, not just a wound.

The whole thing, done well, takes under two minutes. The dread is always larger than the event.

What it sounds like: weak versus clean

The gap between a correction that lands and one that wounds is almost always in the wording. Here is the same feedback said two ways, so you can hear the difference.

Each row holds the same content. The left column invites a defense of character, the right invites a fix.

A worked version, start to finish, from a real kind of night: an agent had been short with a guest checking in late. At the next lull I stepped beside them and said, "Can I flag one thing. The late arrival in 812, you sounded pretty clipped with them. Everything alright?" That opened it as concern, not accusation. It turned out the guest had been rude first, off the record, after a delayed flight. So the conversation flipped: I acknowledged the provocation, thanked them for not escalating, and we agreed on a line they could use next time to stay warm without absorbing abuse. Two minutes. The standard held, the person felt seen, and nobody lost face. That is the whole craft in miniature.

When it needs to be more than a flag

Not every conversation is a thirty-second course correction. Sometimes the issue is a pattern, or the stakes are real, and it needs a fuller sitdown away from the floor. The principles do not change, but the preparation does. For those, I get clear in advance on exactly what I have observed, over what period, and what specifically has to change and by when. I write it down for myself first, not to build a case, but so I stay on the facts under the pressure of the room. Vagueness in a serious conversation is a kind of cowardice. If I am going to ask someone to change something that matters, I owe them precision about what and why.

The hardest version of this is the one that follows a real service failure, when an agent has let a guest down and both the guest and the agent need something from me in the same hour. That is its own craft, protecting the guest and the person at the same time, and I have written about leading through a service failure as a separate discipline. But even there, the corrective conversation with the agent follows the same rules: specific, private, prompt, and rooted in the belief that they can do better.

What defensiveness is really telling you

People get defensive. Expect it, and do not take it as failure. Defensiveness is usually a sign that the person cares about being seen as good at their job, which is exactly the quality you want in them. The mistake is to meet their defensiveness with more force, to pile on evidence until they concede. That wins the argument and loses the person.

Instead I stay level and come back to the observable thing. "I hear you, and I might be missing context, so tell me what happened from your side." Nine times out of ten, that single move dissolves the defensiveness, because the person realizes I am not trying to convict them, I am trying to understand and fix a thing. On a busy floor, my composure is contagious. If I stay calm and specific while they are heated, they come down to meet me. If I match their heat, we both climb. I learned that my own steadiness is a tool in these moments, not just a nicety.

And sometimes, when I listen, I discover I was wrong. The ID step was skipped because the system had frozen. The short tone with the guest followed twenty minutes of abuse I never saw. In those moments the conversation flips from correction to support, and I am always glad I opened with curiosity instead of a verdict. That is the quiet argument for listening: it protects you from confidently correcting a person who did nothing wrong, which is the fastest way to lose a good agent's trust.

The part after the conversation

A hard conversation is not finished when it ends. If I name a thing and then never mention it again, I have taught the person that my words have a short shelf life, which is almost worse than never speaking. So when something matters, I close the loop. Not with surveillance, but with attention. I notice out loud when it gets better, because catching someone doing it right is at least as powerful as catching them doing it wrong. And I come back to it, plainly, if it does not improve.

That followup is what turns a single awkward moment into actual accountability, and it is also what makes the next conversation easier. A team learns quickly whether their manager's corrections are real or theater. When they see that what I name I mean, and that I remember I said it, they start to trust the process itself. They know a flag from me is honest, proportionate, and never delivered to shame them. That trust is the whole point, because it is what lets me keep telling the truth without the relationship fraying.

I want to be honest that I still feel the weight before a hard conversation. It never became comfortable, and I have made my peace with that. What changed is that I stopped waiting for comfort to arrive before I acted. The dread is not a signal to stay silent. It is just the cost of caring about the person enough to tell them the truth. So I have the conversation, early and privately and plainly, and almost every time the person meets me better than I feared, and the thing I dreaded turns out to be the moment we both needed. Say the true thing while it is small, and trust that clarity, delivered with respect, is a gift and not a wound.