Hello restaurateur,
As much as I attract food, I attract incidents. It’s basically a package deal at this point.
So last week’s incident came with noodles, a server who was convinced I said something I didn’t, and a plate of aglio olio I never ordered.
I was at this bar and restaurant with a friend, scanning through the QR code menu, doing what I do best: ordering enough food for two people who were clearly planning to eat like four. Falafel pita pocket, ravioli, pad thai noodles, two mocktails (remember the order)
Except the mocktails needed backup.
The server asked us to show him the exact drink on our screens because apparently describing a mocktail out loud is a competitive sport now. So there we were, two grown adults pointing at our phones like we were identifying a suspect in a lineup. Fine. A little extra effort.
The falafel pita pocket arrived first and it was great.
Then the noodles came, except they were pan fried noodles, not the pad thai I had ordered. I called the server back and told him this wasn’t what I ordered. He disappeared, and a few minutes later, the original server who had taken our order came back with the pad thai I had actually asked for.
Just when I thought the drama was over, the ravioli arrived. Except it wasn’t ravioli. It was aglio olio!
I told the server I had ordered ravioli, and he repeated the order back to me with total confidence: aglio olio. I looked at my friend for backup because at that point I needed a witness. She confirmed it too. I had said ravioli.
That’s when it clicked.
The accent, the pace, the way certain words get compressed when a restaurant is busy and loud, all of it had turned “ravioli” into “aglio olio” somewhere between my mouth and his notepad. The server gave me a look that said please, ma’am, let’s just move on, and honestly, I let it go. We ate the aglio olio. It was fine. But it stayed with me.
The Kitchen Did Nothing Wrong
The food, once it arrived correctly, was genuinely good. The issue was further upstream, at the exact point where a guest’s words become an order ticket. That’s a translation step, and if the person doing the translating isn’t fluent, confident, and clear, everything downstream inherits the mistake.
A restaurant can have the best chef in the city and the most beautiful interior on Instagram, and none of it matters if the person taking your order mishears half of what you say. That first conversation at the table is the actual product.
Everything else is just execution of what got heard.
It Even Has a Name
This isn’t some vague soft skill nobody’s bothered to define. It already exists in hospitality training, and not just under one name.
Menu Training. Menu Knowledge Training. Product Knowledge Training. Menu Familiarisation. Service Training. Menu and Service Training.
Different labels, same core idea: staff learning the menu well enough to speak about it clearly and confidently.
The version that fits what happened to my ravioli is Menu Knowledge and Service Training, which is about pronunciation, ingredients, and how a dish gets described and recommended to a guest.
Chances are you already know these terms. Most restaurant owners do.
So the real gap was never the vocabulary. It’s whether this training actually happens regularly, not just once during onboarding and never again.
Why This Deserves a Real SOP
A new server not knowing every last detail about an obscure dish is understandable. Nobody expects day-one perfection. But when the gaps are wide enough that a guest has to correct an order twice in one sitting, that’s not a one-off mistake. That’s a training system that stopped after day one.
Pronunciation matters here too, more than restaurants tend to give it credit for.
A guest saying “ravioli” and a server hearing “aglio olio” isn’t just an accent quirk. It’s a sign that the dish name was never drilled enough for it to be unmistakable, even under noise, even at pace, even from a table that ordered four things back to back.
5 Ways to Actually Fix This
Run regular menu checks: A quiz, a walk-through, a quick verbal run of the full menu every few weeks keeps knowledge sharp instead of letting it quietly decay after the first month.
Drill pronunciation out loud: Reading a dish name and saying it clearly to a guest are two different skills. Practice the second one specifically.
Rotate staff through the full menu: Servers naturally gravitate toward the dishes they know well. Make sure training covers the items they’d otherwise avoid recommending.
Refresh training every time the menu changes: New dishes should trigger a mini round of familiarisation before they go live on the floor, not after the first few guests get confused.
Build in a feedback loop from mix-ups: If a dish keeps getting misheard or mixed up, that’s data. Use it to fix the specific gap instead of treating every mistake as a one-off.
Good food gets people through the door. Being understood is what gets them to come back and actually order what they wanted the first time.
Order Up
I let it go because I’m the kind of person who eats whatever ends up in front of me and complains about it later, over a newsletter, to thousands of people.
Not the healthiest coping mechanism, but here we are.
Your guests probably won’t be that forgiving. Most people don’t want a surprise plate, they want the exact thing they pointed at on the QR code menu. So the next time your team walks the floor, ask yourselves honestly: could every server on shift right now pronounce, describe, and recommend every single dish on your menu without flinching?
If the answer’s a hesitant maybe, that’s your cue!
Until next week!