Every new leader eventually meets the fear underneath this whole subject. You have a standard to hold, you know you should hold it, and you can already picture the face of the person you will have to hold it with. So you hesitate. You tell yourself you will let it slide just this once, that being firm will make you the villain, that the team will like you less. I have felt all of that. And what I have learned, across a front desk in Waikiki and rooms operations in San Francisco, is that the fear is aimed at the wrong target. Teams almost never resent a fair standard. What they resent is an unfair one, and the difference is entirely in how you hold it.
The villain a team turns against is not the leader who has high standards. It is the leader who enforces them unevenly, without explanation, or only when it suits them. Consistency, not leniency, is what keeps a team on your side. This piece is about how to hold a line firmly and stay someone people want to work for, because those two things are not in tension. Done right, they are the same act.
Teams resent unfairness, not standards
Start with the thing most new managers get exactly backward. They assume a team wants the lowest possible bar and will love whoever lets them clear it easily. In my experience the opposite is true. People take real pride in working somewhere with a standard, in being part of a desk that is genuinely good. A slack, sloppy operation is not a fun place to work. It is a demoralizing one, because the people who care watch the people who do not get away with it, and something in them deflates.
What a team actually wants is fairness. They want to know that the line is real, that it applies to everyone, and that meeting it means something. When you hold a standard evenly, you are not taking something from your team. You are protecting the thing they are proud of from the few who would erode it. The strong performers, the ones you most want to keep, are quietly begging you to hold the line, because every time you let it drop you are telling them their extra effort was optional all along.
Your best people are quietly begging you to hold the line. Every slip tells them their effort was optional.
So the reframe is this. Enforcing a standard is not an act against the team. It is an act on behalf of the team, and specifically on behalf of the ones carrying it well. Once I understood that, the fear lost most of its grip. I was not choosing between the standard and the team's goodwill. Holding the standard fairly was how I earned the goodwill of the people whose opinion I most wanted.
I have watched what happens to a desk where the line quietly disappears. It does not become relaxed and happy. It becomes tense in a different way, because the people still trying can feel the unfairness of doing more than the people coasting, and there is no relief valve for that resentment when the manager will not act. The hardest workers start to ration their effort down to the level that goes unpunished, not out of laziness but out of a basic sense of justice. A dropped standard does not make a team easier to lead. It makes a team quietly angrier, and the anger has nowhere to go but sideways, into the culture of the desk.
What makes enforcement feel fair?
Fairness is not a feeling you generate with a warm tone. It is built from a few concrete things, and when they are present, even a firm correction lands as fair. When they are missing, even a gentle one breeds resentment.
- Consistency. The same line, for everyone, every day. The moment a standard applies to one person and not another, it stops being a standard and becomes a mood, and a team can smell a mood instantly.
- A reason. A standard people understand is one they can own. When the team knows why the line exists, holding it feels like sense, not control. When they do not, it feels like a rule for its own sake.
- Predictability. People can meet a bar they can see. What they cannot meet is a bar that moves with your mood or your stress level. Steadiness is a form of respect.
- Self-application. The line has to apply to you first, most visibly of all. A leader who exempts themselves has already lost the argument, whatever they say.
That last one carries more weight than the rest combined. Nothing destroys a standard faster than a leader who holds others to a line they will not hold themselves. If I ask the desk to be spotless with followups and my own promises to the team go unkept, the standard is dead and I killed it. But when the team sees me hold my own line first, on the days it costs me something, the standard stops being mine imposed on them and becomes ours, held together. This is the same principle that runs through building service standards that stick. What you model outweighs what you mandate, every time.
Consistency is the whole game
If I had to reduce fair enforcement to a single word, it would be consistency, because almost every accusation of unfairness traces back to its absence. The team is not keeping a ledger of whether you are strict. They are keeping a ledger of whether you are the same. A leader who lets a standard slide on a slow Tuesday and then enforces it hard on a busy Friday has not been lenient and then firm. They have been unpredictable, which is worse than either, because now no one knows where the line actually is.
Inconsistency also creates the exact villain you were trying to avoid. When enforcement is uneven, the person corrected on Friday does not think, I was wrong. They think, why me, why now, when Tuesday was fine. The correction feels personal because the pattern is arbitrary, and a personal correction is the kind people carry as a grudge. The irony is sharp: the leader who bends the line to be liked ends up disliked, because bending it made every eventual enforcement feel like a targeting rather than a rule.
Consistency is also what lets you enforce a standard with a light touch. When the line is steady and known, you rarely need a heavy hand, because meeting it is simply the norm and a small reminder is enough. It is the leaders who let things drift and then overcorrect who end up in dramatic confrontations. Hold the line quietly and evenly every day, and you almost never have to hold it loudly.
The other thing consistency protects is the new person. When a standard is steady, a new hire learns exactly where the line is within a week, because they watch it hold for everyone and calibrate to it. When enforcement wobbles, the new person cannot find the line at all, and they end up guessing, which is stressful and unfair to them. Consistency is not rigidity. It is the kindness of a clear world. People relax inside predictable expectations and tense up inside unpredictable ones, and a relaxed, confident team gives better service than an anxious one guessing at what you want today.
When should a standard actually bend?
None of this means the line never moves. It means it moves for the right reason, in the open, and not under pressure in the moment. A standard should bend for context, never for the discomfort of the person enforcing it. Those are two completely different things, and the team can always tell which one is happening.
Bending for context looks like this: circumstances genuinely changed, so I name the change openly and adjust the expectation for everyone. The system is down, so tonight the checkin standard flexes and here is exactly how. That is not a broken standard. That is a leader reading reality and saying so out loud, and the team respects it because it is honest and it is shared. Knowing when a situation truly warrants an exception is part of judgment, the same judgment that decides when to name a performance problem and when to let a genuinely off day go.
Bending under pressure looks completely different. It is quietly letting the line drop because someone pushed back, or because it was late and you were tired, or because holding it meant a hard moment you did not want. That kind of bending is invisible in the moment and expensive later, because the team learns the real rule: the standard is negotiable if you push hard enough or catch the manager weary enough. Once they learn that, every standard you hold is up for negotiation, and you have traded one uncomfortable moment for a hundred.
A simple test keeps me honest here. Before I let something slide, I ask myself whether I would make the same call for a different person, on a busier day, with a manager watching. If the answer is yes, the exception is probably real context. If the answer is no, I am bending under pressure and dressing it up as flexibility. That one question has saved me from a lot of quiet erosion, because it forces the difference between a fair adjustment and a tired surrender out into the open where I can see it clearly.
Fair enforcement versus unfair, side by side
It helps to see the two next to each other, because in the moment they can feel identical from the inside. The difference is entirely in how the line is held, not how high it sits.
| What changes | Unfair | Fair |
|---|---|---|
| Timing | Enforced when you are stressed, ignored when you are not | The same line holds on a slow Tuesday and a packed Friday |
| Who it covers | The star gets a pass the struggler would never get | The star and the struggler meet the same bar |
| Reason | A correction with no reason, "because I said so" | A correction tied to the guest or teammate it affected |
| Yourself | You hold the desk to a line you visibly break | You meet your own line first, on the days it costs you |
Every row sits at the same height. What separates the columns is consistency, a reason, and whether the leader stands inside the line too.
A worked example of the honest version: one busy night the property management system went down mid checkin rush. The written standard of verifying every reservation against the system was suddenly impossible. The unfair move would have been to keep quietly holding agents to a bar reality had removed, then correct whoever fell short. What I did instead was name the change out loud to the whole desk: tonight we verify identity by ID and confirmation email, we log every room by hand, and we reconcile the second the system is back. That is a standard bending for context, in the open, for everyone at once. The team moved faster because they knew exactly where the temporary line was, and nobody felt singled out when we cleaned it up later. Contrast that with the tired surrender of simply letting checkins get sloppy because it was late and hoping nobody noticed. Same slower night, opposite effect on trust.
Trusted beats liked
The deepest shift a leader makes on this subject is giving up the wish to be liked in favor of the goal of being trusted. They are not the same, and chasing the first actively undermines the second. A leader who bends every standard to keep everyone happy is pleasant for about a month and then quietly stops being taken seriously, because a line that never holds is not a line at all.
Trust is different and it is durable. A team may not enjoy every standard I hold, but they trust that I am fair, that I am consistent, that I will hold the same line for the star and the struggler, and that I will hold it for myself first. That trust is worth infinitely more than being liked, because it is what a team leans on when a standard costs them something, when I have to ask them to do the harder right thing on a night they would rather not. Liked gets you cooperation on easy days. Trusted gets you the room on hard ones.
And here is the part that took me longest to believe: holding the line fairly is how you become liked in the way that matters. Not liked as in easy, but respected, relied on, the leader people are quietly glad is on tonight because they know the desk will be steady and fair. That is the affection worth having, and you cannot get it by lowering the bar. You get it by holding the bar in a way that is so evidently fair that even the person you corrected walks away knowing you were right. You do not have to choose between the standard and the team. Held with consistency, a reason, and yourself on the line first, the standard is the surest way to keep them.