What the Best Restaurant Managers Do Differently

Then there were the managers who made something click. Staff stayed longer. Servers upsold without being pushed. Tables got the story behind the dish, not just the description on the menu. Guests came back. Not because the manager had a better system, exactly. Because they had a different obsession.

Here's what I noticed, watching both kinds over three decades. The good ones obsessed over what their people *did*. The great ones obsessed over what their people knew.

That distinction sounds small. It isn't.

A manager who manages behavior is always chasing. Did you greet the table in 60 seconds? Did you suggestive sell the appetizer? Did you run the food while it was hot? They're checking boxes. Constantly. It's exhausting for everyone, and the second that manager isn't on the floor, the behavior degrades. Because the staff never internalized *why*. They just knew what to do when someone was watching.

A manager who manages knowledge builds something different. They ask questions. Before service, during a slow moment, the day after a new menu dropped. Not to call someone out. To find the gaps. Because they know that a server who understands the dish will sell it better than a server who memorized a script. A bartender who knows which cocktail has egg white in it doesn't have to look it up when a guest has an egg allergy at 8pm on a Saturday. The knowledge is already there. It shows up when it needs to.

I remember when we introduced a new walnut sauce at one of my concepts. Great dish. Rich, a little sweet, paired well with the pork. We put it on the menu, ran a pre-shift tasting, and moved on. Two weeks later, I watched a server describe it to a guest as "kind of like a pesto." That's it. That's all she had. The guest ordered something else. And I thought, whose fault is that really? Not hers. She never got the language. Nobody built it with her.

The great managers I've worked with and hired, they catch that gap before service, not two weeks later. They're the ones asking a server, in front of the rest of the team, "Tell me about the walnut sauce. Walk me through it like I've never had it." Not to embarrass anyone. To build the shared vocabulary. And when the server stumbles, the manager helps fill it in, and now the whole team just heard it again.

That's the move. Pre-shift questions directed at individuals, out loud, so everyone learns from the answer. It's the oldest teaching method there is and most restaurant managers have stopped doing it because they're too worried about running long or making someone uncomfortable.

The follow-up the next day is where the real separation happens, though. Average managers ask questions at the pre-shift. Great managers come back 24 hours later. "Hey, someone asked you about the walnut sauce last night. How'd it go?" That question does three things. It tells the server their knowledge matters enough to revisit. It creates a learning loop instead of a one-time download. And it signals that the manager is paying attention to what their people know, not just whether they showed up on time.

I've seen this play out at Black Barrel Tavern with our whiskey list. We've got a deep program. Staff can get lost in it. The managers who just hand out a cheat sheet and hope for the best, their servers deflect when guests ask about barrel age or mash bill. The managers who ask about it the next shift, the ones who quiz informally, their servers start to own it. You can hear the confidence in how they talk at the table.

Now here's the part that changed everything when I started building ShiftTrained. We added a leaderboard. Not to shame anyone. Just to make knowledge visible. Staff can see how they're doing on quizzes relative to their coworkers. And what happened surprised even me. People started retaking quizzes on their own phones. Not because we told them to. Because nobody wants to be at the bottom of a list when they're competitive people working in a competitive environment. Restaurant people are competitive by nature. You're either in the weeds or you're not. You either know the menu or you don't. A leaderboard just makes that visible.

I've seen a lot of management philosophies come and go. High-touch hospitality, servant leadership, open-book management. Some of it is useful. But the through-line in every high-performing restaurant team I've ever been part of is the same thing: someone in leadership cared what was in their people's heads. They didn't just watch what people did. They asked what people knew, repeatedly, specifically, and without making it a performance review.

The managers who do that don't burn out as fast either. Because their floor runs on knowledge, not surveillance. They're not chasing behavior all night. They're seeing the results of what they built in the kitchen before service started.

That's the job. Build the knowledge. Ask the questions. Come back the next day. Everything else follows.

Have a great day! — Terry
Your AI Restaurant Guy