How to Train Staff to Describe Dishes So Guests Actually Order Them

The painful part is it's not the server's fault. Nobody taught them how to talk about food. We hand them a menu, run them through a shadow shift, maybe quiz them on the ingredients, and assume the rest is personality. It isn't. Describing food so that a guest actually wants to eat it is a skill. It's learnable. And most restaurants never teach it.

Here's what I've learned about what actually works.

The problem with "it's really good" is that it's about you, not the guest. It tells them your opinion. Guests don't come to a restaurant to validate your taste. They come because they're hungry and they want to feel something. Your job is to put them in the dish before it arrives.

The fix isn't training servers to memorize a paragraph about every menu item. That's how you get recitation that sounds like a brochure. Nobody wants to hear someone read the menu back to them in a slightly different order. What you want is one or two physical details that land in the body. Not the brain. The body.

Taste, texture, temperature, technique. Pick one or two. Say them out loud. Stop.

At Fat Tommy's, we added a walnut sauce to a pasta dish a few years back. It's earthy, it's got this slight bitterness that cuts through the richness, and the texture is almost silky without being heavy. For a while, servers just said "it's a walnut pasta, it's really good." Sales were okay. Then we started training them to say three words: "silky, earthy, rich." Just those three. And then one follow-up line: "It coats the pasta like a cream sauce but it's not heavy at all." Check average on that dish went up. The dish didn't change. The sentence did.

That's the thing I want you to take from this. Guests order based on a mental picture. If your server gives them nothing to picture, they default to safety. They order the thing they know. They order the burger. Nothing wrong with the burger, but they came in curious and left with ordinary. That's a miss.

The three-word hook works because it's repeatable and it doesn't require your servers to be food poets. They don't have to describe the entire dish. They just need to drop three accurate, sensory words and one short sentence that does the real work.

The other thing that matters is technique, and this one is underused. Guests are more curious about cooking than they used to be. Years of cooking shows and food media have trained them to find technique interesting, not intimidating. If something is wood-fired, tell them. If it's braised for six hours, say six hours. At Black Barrel Tavern, we have a smoked brisket that goes low-and-slow for hours before service. When a server says "it's smoked low and slow and it pulls apart with a fork," that sentence sells the dish. It creates anticipation. The guest starts imagining it before it hits the table.

The goal is to get the guest to start eating with their imagination before the food ever arrives. That's it. That's the whole thing.

Now let me tell you where most training programs fail at this. They either skip it entirely, or they dump a tasting note paragraph into a training manual and expect it to stick. Neither works. The skip is obvious. The paragraph fails because it's too much to memorize and too formal to say out loud naturally. Nobody talks like a wine review.

What works is what we do in pre-shift. You pull up the dish. You ask each server to give you their three-word hook. You correct it, you refine it, you run it back again. You make it feel like a drill, not a lecture. Three words. Then one sentence. Then stop.

The repetition is the point. When a server has said "silky, earthy, rich" fifteen times in pre-shift, it comes out naturally at the table. It doesn't sound rehearsed. It sounds like someone who knows the food.

Allergen accuracy has to be part of this too. Knowing a dish is "nutty and rich" is great, but your server also needs to know that "nutty" might literally mean tree nuts that can kill someone. At ShiftTrained, the platform I built, we bake allergen flags into the quiz questions so servers learn the flavor profile and the allergen profile together. They're not two separate things. A server who knows how to describe a dish should also know exactly what's in it.

The deeper point is that menu knowledge isn't really about the menu. It's about confidence. A server who can describe food well talks to tables differently. They're engaged. They make eye contact. They sell without feeling like they're selling. Guests feel it and they respond to it. Check averages go up. Tips go up. And the guest walks out having had a better experience than they would have had if they just ordered the safe thing.

That's why I keep saying description is a trainable skill. It's not talent. It's not charm. It's repetition and the right three words.

Figure out the three-word hook for every dish on your current menu. Get your team saying them out loud in pre-shift. Give it two weeks. You'll see it in your numbers.

Have a great day! — Terry Psaltakis
Your AI Restaurant Guy