She Almost Didn't Knock

There was a Beverage Server standing outside my open office door who looked like she was trying to decide whether to knock.

She knocked.

I could tell she was close to tears before she said a word. I told her to come in and sit down.

I already knew there was a challenge in her department. I knew because I had been meeting one-on-one with her director. I knew because I had done a skip review with her manager. I had context, background, and a general read on what was happening and why.

What I didn’t have was her perspective. What she had internalized. What the team believed was true about decisions that had been made above them. That part only surfaced because she trusted me enough to walk through the door.

She trusted me because she knew me.

Not from a company newsletter or an org chart that showed me as the property’s General Manager. She knew me because I spent time in the beverage wells. I showed up to team meetings. I was on the floor often enough that my presence wasn’t an event. It was just normal. When I stopped to talk, it wasn’t an inspection. It was a conversation.

That takes longer to build than most leaders budget for. And it cannot be replicated through a Team Member Engagement Survey.

I mentioned yesterday that our company is administering our annual survey. The engagement survey has a legitimate function. It captures data at scale. It surfaces patterns. It gives leadership a directional read on how the organization is feeling at a point in time. For large organizations, it is a reasonable starting point.

But it has a ceiling.

A survey captures what someone is willing to say anonymously, in the format you designed, at the cadence you scheduled. It cannot capture what someone is still working out. It cannot tell you how a decision landed on the floor three weeks after it was made. It cannot show you the gap between what leadership communicated and what the team actually understood.

That Server didn’t need a survey question to surface what was wrong. She needed to believe that telling me directly would matter.

The conversation moved in two directions.

She gave me something: a view of how the team had processed a series of decisions, what had filtered down to them, and what hadn’t. Critical context had not reached the floor. The reasoning behind certain choices had never been communicated clearly, and in the absence of explanation, the team had filled in the blanks themselves. What they filled in was a distortion of the truth.

I gave her something back: the fuller picture. Enough for her to leave with a broader frame than she arrived with.

She wasn’t just “less upset” when she left. She was informed. And she would carry that back to the people she worked alongside every day.

That’s a return a survey doesn’t produce.

The skip review, the one-on-one, the time spent walking the floor — none of it scales the way a digital survey does. It requires actual hours, actual presence, actual investment in relationships with people several layers removed from the leadership table.

And those investments compound.

They mean you’re not going in cold when someone surfaces a problem. They mean you’ve already built enough trust that coming to you feels like a real option. They mean that when a Server is standing outside your door deciding whether to knock, she already knows the answer will be, “Come in”.

If I hadn’t already been meeting with her director and her manager, the conversation would have been less productive in the moment. I would have had to go back, gather more context, and return to her with a fuller picture later. That’s not a failure of leadership. It’s just a slower path to the same place.

The time I had invested in being present on the floor meant we could get there together, in one conversation, the day she needed it.

Surveys measure sentiment at a distance. Presence builds the trust that makes the real conversations possible.

Who on your team right now might be standing outside a door, deciding whether it’s worth knocking?