The quiet work of managing a star performer who is slipping

There is a particular quiet that settles over a desk when everyone can see the thing but no one will say it. The agent who used to set the pace has slowed down. Their checkins still work, guests still like them, but the edge is gone, the followups are landing late, and the rest of the team has started to trade glances. Nobody wants to be the one who names it, least of all the manager, because this is someone we respect.

I have managed a star performer slipping more than once, across a front desk in Waikiki and rooms operations in San Francisco, and it stays hard no matter how many times you do it. Letting a weak performer go is clean. Coaching a struggling new hire is expected work. But addressing a strong agent whose performance is declining asks you to act on a fade that is both real and quiet, before it becomes a number anyone can point to. Move too soon and you insult a good person. Wait too long and you lose the team's respect and, often, the agent along with it.

Why a star performer starts to slip

The first thing to understand is that a fade almost never means the person got worse at the job overnight. Skill does not evaporate. What changes is usually underneath the skill: motivation, focus, or the sense that the work still matters. A top performer is often someone who cares more than the average, and people who care are the ones who burn out, get bored, or quietly lose faith when something around them stops making sense.

I have seen a handful of common causes on the floor, and it helps to hold them in mind before you decide what you are looking at:

• They outgrew the role. No one gave them anything bigger to reach for, so the effort that used to go into the work now goes nowhere, and it drains away.
• Something at home is pulling on them. The shift is the only place it shows, because it is the one place they cannot hide it.
• They were passed over. They watched a weaker colleague get praised for less, or a supervisor spot went elsewhere, and a small resentment took root.
• They are simply tired. Not in a way that a performance plan fixes, but in a way a good week off would fix, if anyone had noticed they needed one.

Laid out plainly, each cause points somewhere the word laziness never would. The value of the table is that it stops me reaching for the response my frustration wants and points me at the one the situation actually needs.

None of those are laziness, and treating them like laziness is the fastest way to turn a recoverable slip into a resignation. The leader's job is not to assume the cause. It is to notice the change early, name it plainly, and open a door the person can walk through.

There is one more cause worth naming, because it is the one leaders least like to look at. Sometimes a strong agent fades because the leadership around them changed and the work stopped feeling fair. A schedule that always hands them the hardest section. A promise about growth that quietly evaporated. A manager who leans on their best person for everything and thanks them for none of it. When that is the cause, the fade is not a performance problem at all. It is feedback, delivered the only way the person feels safe delivering it, and the honest response is to fix what broke rather than to correct the symptom.

What are you actually seeing?

Before you say anything, get specific with yourself. A fade is easy to feel and hard to describe, and a vague sense of disappointment is not something you can act on fairly. So I make myself answer a plain question: what, exactly, is different now that was not different two months ago?

Usually the answer is a handful of small things that have started to repeat. The greeting that used to be warm is now efficient. The arrivals prep that used to be spotless now has gaps someone else catches. The followup call that used to happen does not. The upsell that used to close, back when a strong agent on my Waikiki front desk could move thirty to forty thousand dollars of upgrades a month, now goes unoffered. Alone, each one is nothing, a single tired shift. Together, in a pattern, they are the real signal. One off night is human. A run of them is information.

A single bad shift is human. A pattern is information.

I keep this honest by watching for facts, not moods. I am not looking for a bad attitude, which is a story I would be telling myself. I am looking for observable things I could describe to the person without arguing about their character. This matters, because the conversation that helps is built on what you saw, not on how you felt about it. My own test is simple: if I cannot name three concrete changes, out loud, that have each shown up more than once, I am not ready to have the conversation yet, and I watch one more week. Three specific facts is the difference between a fair conversation and an accusation the person can wave away.

How do you open the conversation?

The instinct most new leaders have is to soften the whole thing until it disappears, or to store it up until a review and then unload a season of small frustrations at once. Both are unfair. The person deserves to hear it early, clearly, and privately, while there is still plenty of room to recover. The skill here is the same one that runs through every hard conversation at the front desk: be specific, be prompt, and separate the behavior from the person.

I open with the track record, because it is true and because it sets the frame. Something like: you are one of the strongest people on this desk, which is exactly why I wanted to raise something I have noticed. Then the specifics, described flatly. The last few weeks, the greeting has been shorter, a couple of followups slipped, the prep had gaps that are not like you. Then, and this is the part that matters most, a real question instead of a verdict. Is everything okay? What am I not seeing?

Why the question does the work

That question is not a formality. Roughly half the time it surfaces something I had no way to know: a sick parent, a second job, a slow simmer of frustration about being passed over. When the agent tells you the real cause, the conversation stops being a correction and becomes a repair. You cannot fix what you refuse to hear, and a person who feels heard will give you far more than a person who feels managed.

The hard part is staying quiet long enough to let the real answer arrive. The first thing a person says is rarely the true thing. Fine, just tired, is the reflex. If I sit with it, do not rush to fill the pause, and let the silence do some of the work, the second answer is usually the one that matters. Learning to wait through that gap is a skill on its own, and it is where a lot of these conversations either open up or quietly close.

A few things I hold in mind when I open it:

• Private, always. A fade addressed in front of the team is a humiliation, and it guarantees you lose them. This happens at the end of the desk, quietly, or off the floor entirely.
• Recent and specific. Point to this week and last week, not to a grievance from March. Old, saved-up examples read as an ambush.
• An out, not a trap. The goal is to give the person a way back, not to build a case. If it turns into evidence-gathering, they can feel it, and the door closes.
• Your own part. Ask yourself first whether you stopped giving them anything to grow toward. Sometimes the fade is a message about your leadership, not their effort.

A conversation, step by step

When I coach a new supervisor through their first one of these, I give them an order to move in, because the sequence itself does a lot of the protecting. Here is how it runs.

1. Set the frame with the track record. Open by naming what they are good at and that it is genuine. This is not flattery to soften a blow. It is the true context that everything else sits inside, and it tells them the conversation is about recovery, not removal.
2. Name three specific, recent facts. Describe what changed, flatly, using the observable things you wrote down. No adjectives about their character. Just the shorter greeting, the missed followup, the gap in the prep.
3. Ask an honest question and then stop talking. Is everything okay? What am I not seeing? Then let the silence sit. Do not rescue them from the pause. The real answer usually comes second, after the reflex answer.
4. Listen for the cause, not the excuse. If they hand you something real, a struggle at home, a resentment, a boredom, treat it as the actual problem to solve, not a hurdle to get past on the way to your point.
5. Agree on one concrete thing that changes, and a time to check in. Not a formal plan with a paper trail. A small, mutual next step and a date. A followup a week or two out signals that you meant it and that you are paying attention.

The whole thing takes ten minutes when it goes well. What makes it land is not a script, it is the frame: you are raising this because they are worth it.

Protecting the rest of the team

Here is the reason you cannot let this drift, even when the person is likeable and the decline is gentle. The rest of the desk is watching, and what they are really watching is whether the standard applies to everyone or only to the people with a reputation to protect. When your best agent coasts and nothing happens, every other agent updates their sense of what is required. The floor learns that effort is optional once you have earned enough credit. That lesson spreads faster than any policy.

I have felt this happen. A strong agent slips, I hesitate because I do not want to bruise them, and within a couple of weeks a newer person who used to hustle has quietly matched the lower bar, because why would they hold themselves to a standard the star no longer has to meet. The failure to name a fade in one person becomes a slow sag across the whole team. When I was running rooms operations with teams of sixty to ninety people, one unaddressed fade at the front never stayed one fade. It set the ceiling for everyone who could see it. This is why the work of holding a line and the work of developing people are not opposites. They protect each other. You cannot really develop people on the shift you have if they can see that the standard bends for whoever is popular enough.

None of this means you address a private struggle in public. It means you address it, period, and you do it soon enough that the rest of the team never has to wonder whether you will. When you handle it well and quietly, the effect on everyone else is calm, not fear. They do not see the conversation. They just see that the desk still holds, and that a good place to work is one where the standard is real for everybody.

It helps to remember what a fade costs the star themselves, not just the team. A person who was once the strongest on the desk knows, on some level, that they are coasting. That knowledge is corrosive. Pride is part of what made them good, and a slow slide erodes it quietly, shift after shift, until the version of themselves they were proud of feels far away. When you name the change with respect, you are not only protecting the team. You are handing the person back a mirror they had started to avoid, and most people, given that mirror early and kindly, would rather rise to it than keep sinking below the standard they used to set for everyone else.

Common mistakes managers make

Even leaders who mean well tend to get a star performer slipping wrong in the same few ways. I have made most of these myself, which is the only reason I can name them.

• Waiting for the numbers. The report always lags the floor. If you tell yourself you will raise it once a metric confirms it, you have chosen to act only after the fade has already cost you a month and possibly the team's trust.
• Leading with the problem instead of the person. Skip the track record and open with the criticism, and even a fair point reads as a verdict. The star hears that their whole history just got erased by two bad weeks, and they stop listening.
• Saving it up for the review. Bundling a season of small slips into one annual conversation feels efficient and lands as an ambush. Feedback that arrives months late cannot be acted on, only defended against.
• Assuming laziness. Deciding the cause before you ask closes the only door that leads to a repair. Nearly every fade has a reason, and the reason is rarely the one your frustration invents.
• Confusing kindness with silence. Letting a good person coast to spare their feelings is not generosity. It lets their pride erode and teaches the team that the bar is soft. The kind move is the early, honest one.

When it does not turn around

Sometimes you do all of it right and the fade continues. You named it early, you listened, you offered something to reach for or a lighter stretch to recover, and the person still drifts. At that point the conversation has to get clearer, and you have to say the harder version out loud: this is the standard, here is where you are, and here is what needs to change and by when. That is still respect. It is the respect of telling someone the truth about where they stand instead of letting them slide toward a formal problem they never saw coming.

A few of those conversations end with the person choosing to move on, and that is not always a failure. An agent who has outgrown a desk and cannot find room to grow on it is sometimes better served by an honest push than by a comfortable stall. What you owe them is clarity, early and kind, and a fair chance to recover with real support behind it. What you do not owe them, and cannot afford to give, is silence that protects your comfort at the cost of theirs and the team's.

The whole thing comes down to a single discipline, which is the same one that naming a performance problem always requires. See the fade while it is small. Describe it as a fact, not a flaw. Ask before you conclude. And act soon enough that the person gets a real chance to come back and the team never learns that your best people are exempt from the standard everyone else is held to. Do that, and most of the time you keep the agent, keep the standard, and keep the trust, all three at once, which is the only outcome worth playing for.