Standards that stick: upholding service standards when no one is watching

Every hotel I have worked in wrote its standards down somewhere, and almost none of that writing, by itself, ever changed what happened at the desk. The binder is the aspiration. The real standard is something else entirely: it is what my team actually does at 2 a.m., when the lobby is empty, the manager has gone home, the shortcut is right there, and no one will ever know which way they went. That version, the one that holds with no one watching, is the only standard that is real. Everything else is a wish on a laminated card by the terminal.

I learned this most clearly on night audit at the Alohilani, where the whole shift is the quiet hour. There is no manager on the floor overnight. No one is checking whether you walked the late arrival to the elevator or just pointed, whether you logged the maintenance issue or told yourself the morning crew would catch it. The standard that survives those hours is the one that lives inside the person, not the one enforced from outside. That taught me what upholding service standards actually asks of a leader. The job is not to inspect harder. It is to build the kind of standard that no longer needs me standing there.

Why do standards collapse the moment you leave?

Because a standard enforced by supervision is not really a standard. It is compliance, and compliance has a fatal property: it is only as present as the supervisor. The agent doing it right because I am watching will do it wrong, or fast, or halfway, the moment I turn around. Not out of malice, but because the only reason for the standard was me, and I just left the room.

This is the trap of leading by inspection. You can raise your presence, walk the floor more, check more folios, hover more, and it works in a narrow way, exactly as far as your attention reaches and no further. You cannot be everywhere. When I ran rooms operations at Marriott Union Square, that meant teams of sixty, eighty, ninety people spread across shifts I was not even on. If the standard depends on my eyes, then most of the time, on most of the desk, there is no standard at all. Supervision does not scale. Ownership does.

A standard your team keeps only when you're watching is not a standard. It's a performance for the manager.

So the whole game shifts. Instead of asking "how do I catch more lapses," I started asking "how do I build a standard the team keeps because it is theirs." That is a completely different project, and it is slower, and it is the only thing that actually works. It is also the heart of what frontline hospitality leadership is really about, because you are not managing behavior, you are building the internal thing that produces the behavior when you are nowhere near.

Make the standard make sense

The first move is the one most managers skip: explain the why. A standard handed down as a bare rule invites exactly the response a bare rule deserves, which is to be followed as little as possible. A standard that makes sense, that connects to something the agent actually cares about, becomes a thing they own rather than a thing they endure.

When an agent understands why we verify the name on the card, not "because policy" but because it protects a real guest from a real charge they never made, the verification stops being a hoop and becomes something they would do anyway. When they understand why we walk a guest to the elevator instead of pointing, because a tired traveler at checkin feels the difference between being directed and being cared for, the walk stops being a rule I enforce and becomes a thing they want to do. The reason is the difference between a standard someone obeys and a standard someone owns. Rules require a watcher. Reasons travel with the person.

This takes patience and repetition, and me being willing to answer "why" honestly instead of retreating to "because I said so." Every time I connect a small task to a reason that matters, I am transferring the standard from my head into theirs. That transfer is the entire point, and it is worth naming precisely.

Written down, a standard is a line in a binder. Owned, it is a thing the person keeps because they understand why it matters, which is a different craft from writing it down.

A worked example: how to install a standard so it holds

Abstract advice about ownership is easy to nod at and hard to use, so here is how I actually install a single standard so it survives the quiet hours. Take one concrete behavior, the arrivals board kept current and clean, so any agent can read the house at a glance and no VIP or special request slips through. This is the order I move in, and why each step sits where it does.

1. Name the standard and the reason in one breath. Not "keep the board updated," but "we keep the arrivals board current so nobody's anniversary or accessibility request gets missed at handoff." The behavior and the stakes arrive together, so the standard has a purpose from the first day, not a rule looking for one later.
2. Model it at hour ten, not hour one. Anyone can hold a standard when they are fresh. The training that lands is what the team sees me do when I am tired at the end of a long shift and the board would be easy to leave for the next person. What I do at hour ten is the real standard, and they are watching for it.
3. Catch it done right, out loud. When an agent keeps the board immaculate through a rush, I say so, by name, where the team can hear it. Recognition of the standard done well is how pride gets planted, and pride is the fuel that runs when I am gone.
4. Name the first lapse fast and specific. The first time the board goes stale, I name it that day, quietly and precisely, before the lapse becomes the norm. Early and small keeps it a correction. Late and vague turns it into a confrontation.
5. Hand enforcement to the team. The standard has truly stuck the day a veteran agent, not me, reminds a new hire to update the board because it is now theirs to protect. That is the finish line. The standard no longer lives in my presence. It lives in the team.

Notice that only one of those five steps is about correction. The other four are about meaning, example, and pride. When managers ask me why their standards keep slipping, the answer is almost always that they collapsed the whole project down to the correction step and skipped the rest. Correction on its own is just supervision by another name, and supervision walks out the door when you do.

What you tolerate is the real standard

Here is the uncomfortable truth I had to accept about myself. I am not setting standards with my words. I am setting them with what I tolerate. The team is not really listening to my speeches about excellence. They are watching what happens when someone falls short, and calibrating to that.

If I walk past a sloppy checkin because the agent is busy, or well liked, or because I do not feel like the friction right now, I have not made an exception. I have written a new standard, and the whole team read it in real time. The next time, the corner gets cut a little more, because the last time it was fine. Standards rarely collapse in one dramatic failure. They erode one tolerated lapse at a time, each one small enough to excuse, until the accumulated drift is a desk that looks nothing like the one in the binder and nobody can point to the moment it changed.

Which is why upholding a standard is inseparable from being willing to name when it slips. You cannot protect a standard you will not talk about, and the talking has to be prompt and specific, before the lapse becomes the norm. That naming is its own skill, and I have written about it in naming performance problems, but the short version is this: the kindest thing I can do for a standard, and for the person, is to say plainly and early when something has slipped, so it stays a small correction instead of becoming the way things are done.

Pride holds what fear cannot

There is a wrong way to enforce standards that gets short-term results and rots the desk from underneath. That is standards by fear. You can absolutely get compliance through pressure and consequence, and it will look like it is working, right up until the fear is absent, at which point the standard vanishes, because fear was the whole structure. In the meantime you have made the desk a joyless place to work, and joyless desks bleed your best people out the door.

The standards that actually hold are the ones the team is a little proud of. When an agent takes visible pride in a spotless arrivals board, in a checkin that felt effortless to the guest, in a recovery they handled so well the guest left happier than if nothing had gone wrong, you are watching a standard that no longer needs you at all. Pride is self-enforcing in a way fear can never be, because pride keeps working after the manager goes home. It is the engine of the 2 a.m. standard.

Set the two engines side by side and the difference is stark. Both look identical while I am standing there; they diverge the instant I leave.

The only column that survives the unwatched hours is the right one, which is why I stopped trying to install fear and started trying to install pride. My job, then, is to connect the small task to the pride, over and over, until the connection belongs to them. Practically, that means:

• Catch people doing it right, loudly. At least as often as I catch them doing it wrong, and ideally more. Recognition of the standard done well is how pride gets planted.
• Name the standard as an identity, not a chore. "This is a desk that walks guests to the elevator" lands differently than "remember to walk guests to the elevator." One is who we are, the other is a task to resent.
• Let the team enforce it on each other. The strongest sign of a standard that stuck is when a veteran agent, not me, quietly corrects a new hire because the standard is now theirs to protect.
• Model it without exception. The fastest way to kill a standard is to hold the team to something I visibly skip when I am tired. What I do at hour ten is the real training.

All of this is really a form of developing people, because a standard someone owns is a small piece of growth. When I hand an agent the reason behind a standard and the pride of keeping it, I am not just protecting service, I am building the person, which is why so much of this overlaps with how I think about developing employees on the job. The standard and the person grow together, or neither one does.

The common mistakes that quietly lower the bar

Most of the ways I have watched standards die are not dramatic. They are quiet, reasonable, well-intentioned moves that lower the bar a notch at a time. A few I have made myself, early on, and now watch for:

• Treating every rule as equally sacred. When everything is a standard worth defending, the team cannot tell the load-bearing ones from the merely tidy ones, and the whole system flattens into a list nobody can hold in their head, let alone in their pride.
• Handing down the rule without the reason. A standard with no "why" attached is a standard the agent will follow only as far as my eyes reach. The reason is not a nicety. It is the thing that travels with the person to the shift I am not on.
• Trading the standard for peace in the moment. Walking past a lapse to avoid friction feels kind and costs almost nothing today. The bill arrives later, as a desk that drifted somewhere no single conversation could have caused.
• Holding the team to a standard I visibly skip when tired. Nothing kills a standard faster than an agent watching me cut the exact corner I told them not to. My exception becomes their permission.
• Leaning on fear instead of pride. Fear is faster to install and it produces a desk that performs for the manager and collapses the moment the manager is gone. Pride is slower to build and it is the only thing that runs at 2 a.m.

The thread through all five is the same. Each one feels reasonable in the moment and each one quietly rewrites the real standard downward. Upholding a standard is mostly the discipline of not making these small, comfortable trades.

Which standards actually matter?

That first mistake, caring about all standards equally, deserves its own answer, because it is the one that flattens a whole team. If everything is a standard worth defending, the team cannot tell the essential from the merely tidy, and they hold nothing with real conviction. Part of building standards that stick is choosing which few actually carry the guest experience and guarding those without exception, while holding the rest more lightly.

The ones I refuse to let slide are the moments a guest actually feels. A few I guard closely:

• The greeting. The first seconds a guest spends at the desk set their whole read of the property, and it is the easiest thing to let go flat at the end of a long shift. It is worth defending precisely because it is so quietly tempting to skip.
• The handoff. What one agent passes to the next, and what one shift owes the incoming one, is where service silently holds together or falls apart. A dropped handoff becomes a guest's problem hours later, on a shift that had no idea it was coming.
• The recovery. How the team treats a guest after something has gone wrong reveals more about the real culture than a hundred smooth checkins. A standard that survives a failure is a standard that has truly stuck.

When I concentrate my energy on the handful of standards that carry the most weight, the team can feel the difference between what is essential and what is merely preference, and they hold the essential ones far more reliably because they understand the stakes. Trying to enforce everything at once teaches the team that nothing in particular is sacred. Choosing a few and never bending on them teaches exactly where the floor is. On the front desk at the Waikiki Beach Marriott, where I once ran a checkin operation that averaged thirty to forty thousand dollars a month in room upsells, I learned that results follow the few standards you actually protect, not the many you merely list.

Build it for the quiet hours

In the end, everything about standards comes down to a single test I cannot personally administer, because I am not there when it matters. The test runs at 2 a.m., on the shift I am not on, at the far end of a desk I cannot see, when a tired agent faces the small choice between the right way and the faster way and no one will ever know which they picked. Everything I do about standards, the reasons I explain, the lapses I refuse to tolerate, the pride I try to plant, the example I set at hour ten, is aimed at that unwatched moment. I am trying to make the right choice the one they make when the choice is entirely their own.

That is a slower, humbler kind of leadership than walking the floor and catching people out. It does not give you the quick satisfaction of enforcement. But it is the only version that scales past your own eyes, past your own shifts, past your own presence, and it is the only version that lasts. Build the standard into the person, connected to a reason and carried by a little pride, and it will hold at 2 a.m. with no one watching. That, and nothing on the laminated card, is what upholding service standards actually means.