How to Identify Your Restaurant's Most Underrated Dish

Every kitchen has one. A dish the chef is quietly proud of, that gets ordered maybe twice a week, sitting on a menu next to items that move ten times as fast. Ask the staff and they will usually name it without hesitation. Ask the owner and they might not even remember it exists. That gap between staff instinct and owner awareness is exactly where an underrated dish hides.

Popularity alone will not find it

The obvious mistake is looking at your top sellers list and assuming everything not on it is simply less good. Sales volume tells you what got ordered, not what would have been loved if more people had tried it. A dish can sell rarely for reasons that have nothing to do with quality: it is buried at position seventeen in a long section, its name doesn't signal what it actually is, or its description undersells it compared to flashier neighbors.

The signal you actually want is the gap between order frequency and satisfaction among the guests who did order it. A dish ordered rarely but loved intensely by nearly everyone who tries it is a very different problem than a dish ordered rarely because it disappoints.

• Low order count paired with a high like rate among the guests who did order it
• Staff recommending it more than the sales data would suggest it deserves
• Guests who order it once tending to order it again on a later visit
• Positive comments in the rare feedback you do get, out of proportion to how often it sells

Why this is nearly impossible to see with paper

A printed menu and a POS report can tell you the order count. Neither can tell you whether the six people who ordered the dish this month loved it or merely tolerated it. Without that second number, low order count and low quality look identical from the spreadsheet, even though they call for completely opposite responses. One deserves better placement. The other deserves a recipe review or removal.

This is exactly the blind spot that traditional menu engineering, built entirely on sales data, never solved. It can tell you a dish is a puzzle, strong margin and weak sales, but it cannot tell you whether the fix is visibility or the dish itself.

A quick way to sanity-check a hunch

If you already have a dish in mind, staff usually do, a fast way to confirm it before rearranging anything is to simply ask your servers to mention it more often for a week or two when a guest seems undecided. If the dish gets ordered more and the reaction stays positive, you've confirmed the hunch cheaply, without touching the menu layout at all. If the reaction is lukewarm even with the extra push, the dish might not be as underrated as it felt, and the energy is better spent elsewhere.

This kind of informal test is useful precisely because it's low commitment. You're not reprinting anything or restructuring a category. You're just testing a theory about guest reaction before investing more effort into a permanent fix.

Turning the discovery into action

Once you find a genuinely underrated dish, the fix is usually simple: move it up in its category, sharpen the description so it doesn't read like an afterthought, and maybe put it in front of guests whose stated preferences suggest they would like it. What you should not do is leave it exactly where it is and hope word of mouth eventually catches up. Word of mouth about a dish nobody orders travels slowly, if at all.

TasteGraph's dashboard flags exactly this pattern under its Promote category: dishes with a high like rate but low order volume, the clearest sign of an underrated item worth surfacing more. Instead of relying on a chef's hunch or a server's aside, you get the actual number of guests who tried it and loved it, and a clear nudge on what to do next.