The Role of Dish Names in Guest Perception

A dish name is the first and sometimes only thing a guest reads before deciding whether to keep reading at all. In a long category, plenty of guests skim names and only stop to read a full description for the two or three that catch their attention. That means a name is not just a label. It is doing real selection work before the rest of the entry ever gets a chance.

Descriptive names versus evocative names

Research on menu naming, most famously a study out of Cornell involving labels like "Grandma's Zucchini Cookies" outselling plain "Zucchini Cookies" by a wide margin, points to a consistent pattern: names that evoke a specific story, place, or feeling outperform plain, purely descriptive ones, even when the underlying dish is identical. A guest ordering "Grandma's" anything is buying a feeling of comfort and nostalgia along with the food itself. A guest ordering "Zucchini Cookies" is just buying zucchini cookies.

This does not mean every dish needs an elaborate backstory bolted onto its name. It means the name should signal something beyond the literal ingredients whenever there is something honest to signal, a regional style, a family method, a specific technique that sets it apart from the generic version of the same dish.

• A name with a specific origin or story tends to outperform a purely literal ingredient list
• Overly long or overly clever names can confuse rather than intrigue if a guest can't tell what the dish actually is
• Familiar names lower the risk a guest feels in ordering, unfamiliar names raise curiosity but also raise hesitation
• Consistency matters: a menu mixing playful names with clinical ones reads as unfocused

Testing a rename before committing to it

If you suspect a dish's name is holding it back, a rename is a cheap thing to test, especially on a digital menu where changing text costs nothing. Try a more evocative or clearer version for a month and watch order count, keeping everything else about the dish, price, placement, description, exactly the same so you know the name is what actually changed. This is a case where small, isolated tests beat a wholesale rebrand of your entire menu's naming style all at once, since an isolated test tells you clearly whether the specific change helped.

It's worth involving staff in this too. Ask a server what guests actually call the dish when they order it, sometimes guests have already renamed it themselves in casual conversation, and that informal name might be a better fit than whatever's currently printed.

Naming conventions can also drift over time without anyone deciding they should. A menu that started with playful, story-driven names for every dish sometimes ends up half playful and half literal after a few years of piecemeal additions, and that inconsistency itself can make a menu feel less considered than it actually is, even when every individual name is fine on its own.

The risk of naming a dish into confusion

There is a real tension between intriguing and confusing. A dish named purely for creative flair, with no indication of what it actually contains, forces a guest to read the full description just to know if they'd even like it, which adds friction rather than removing it. The names that work best usually strike a balance: recognizable enough that a guest has a rough sense of what's coming, distinctive enough to stand out from three similar dishes nearby.

Regional or house-specific dishes carry extra risk here. A name that means something obvious to the kitchen staff can be completely opaque to a first-time guest, and if the description doesn't immediately clarify it, that dish quietly loses orders to something more legible sitting right next to it.

TasteGraph's AI dish explainer gives guests a safety net for exactly this situation: if a name is intriguing but unclear, a guest can just ask what it actually is in plain language and get an instant answer, rather than skipping past a dish because the name alone left them unsure.