The question people actually want to ask
Whenever I sit on a panel or catch up with someone in the hallway after a session, one question comes up more than any other: how do you keep a hotel running well when you can’t be everywhere at once?
People usually phrase it differently. Sometimes it’s about labor costs. Sometimes it’s about a bad review that stung. Sometimes it’s phrased as a question about technology. But underneath, it’s always the same worry: the hotel is bigger than any one person’s attention, and something is always about to slip.
I get why it’s the question people lead with. It’s the real problem. Everything else, budgets, training, guest scores, sits downstream of it.
Why the usual answer falls short
The standard answer is delegation. Hire well, trust your team, step back. That’s not wrong, but it’s incomplete enough to be almost useless on its own. Delegation without a structure underneath it just moves the anxiety from the manager to whoever they delegated to.
What actually closes the gap is having a small number of things you check personally, on a rhythm, regardless of how the day is going. Not a checklist that grows every time something goes wrong. A short list, held constant.
For me that means walking the property at set points in the day, not just when something’s already wrong. It means reading guest feedback myself rather than only seeing the summary a department head passes up. It means sitting in on part of a shift change now and then, not to catch anyone out, but because you hear things in that room you never hear in a report.
None of that replaces trusting the team. It’s what makes trusting the team sustainable, because you’re not trusting blind.
What I actually check, and what I let go
The things I check personally are the ones where a small miss compounds fast: how the front desk is handling a full house, whether housekeeping and maintenance are actually talking to each other, whether the numbers on occupancy and revenue match what I’m hearing about the mood on the floor. Those four things tell me almost everything about the health of a property on a given day.
What I don’t check personally, on purpose, is the fine detail of how each department head runs their team day to day. If I’m reviewing every schedule change or sitting in on every training session, I’ve built a bottleneck, not a system. The point of strong department heads is that they own that layer completely.
The discipline is in drawing that line clearly and keeping it there. It’s tempting, especially when you started in front-line roles yourself, to keep reaching back down into the operational detail because you know how to do it and you can do it fast. I’ve had to catch myself doing exactly that. It doesn’t help the manager who’s supposed to own it, and it doesn’t actually make the hotel run better. It just makes you feel busy.
The part that’s easy to skip
There’s a piece of this that gets skipped because it doesn’t look like management work: telling your team, plainly, what you’re going to check and why. If a front office supervisor thinks you’re walking the floor to catch mistakes, they’ll manage around you. If they know you’re walking the floor because that’s how you stay close to what guests are actually experiencing, they’ll usually start pointing things out to you before you find them.
That shift, from being watched to being informed, is most of what makes a hands-on style work instead of feel like surveillance. It costs nothing to explain, and most managers never bother.
What I’d say if I only had one line
If someone stops me with the short version of the question, my honest answer is this: you can’t be everywhere, so decide in advance which few things you’ll always check, and let everything else be someone else’s job to own completely. The mistake isn’t picking the wrong few things. It’s never picking at all, and ending up reacting to whatever’s loudest that day instead.