The Real Reason Guests Ask "What's Good Here"

It is one of the most common lines a server hears, delivered with a friendly shrug: so, what's good here. Owners often treat it as harmless small talk, a chance for a server to build rapport and recommend the biryani. And sometimes that is all it is. But look closer and this question usually means something more specific: the guest looked at the menu and could not figure out on their own what stood out.

What the question is actually asking

A menu with twelve nearly identical curries and no indication of which one is the house specialty leaves a guest with no way to differentiate. Everything reads the same weight of importance. So rather than gamble on an unfamiliar dish, they outsource the decision to whoever is standing there, hoping the server's opinion will do the narrowing down the menu itself failed to do.

This is not a failure of the guest's attention or effort. Most people do not want to read fifteen dish descriptions closely before deciding what to eat on a Tuesday night. They want to be pointed toward something good quickly, and if the menu does not do that pointing, a person has to.

Why relying on staff to answer this is fragile

• Every staff member has a different personal favorite, so the answer varies table to table
• A busy server gives a rushed generic answer instead of a thoughtful one
• New staff often do not have a confident answer yet at all
• The most-recommended dish is not always the one the kitchen actually wants to sell more of

What a menu that answers this looks like

A menu that surfaces bestsellers, tags a chef's special clearly, or highlights what similar guests tend to enjoy answers the what's good here question before it needs to be asked out loud. This is not about hiding information from guests who want to explore on their own. It is about giving the ones who want quick guidance an obvious signal to follow, the same way a good host might steer a friend toward the right order without being asked.

Rohit Malhotra, who owns Spice Route, ran into a version of this problem directly. His Kadhai Paneer had the best like rate on the entire menu but sat buried on page two where almost nobody found it on their own. Once he tagged it as a chef's special, it moved up for every guest instead of depending on a server remembering to mention it. That one change did the work that used to fall on staff memory alone.

Letting the menu do the recommending

What happens when nobody is around to ask

Think about a guest ordering through a kiosk or a delivery app with no server present at all. They cannot ask what's good here, so they either default to something familiar or scroll aimlessly looking for a signal, a badge, a star, anything that tells them where to look first. The absence of a person to ask makes it obvious how much work that little question was actually doing.

This is a useful way to audit your own menu. Cover up the idea that a server will be there to help and ask whether a guest could still figure out what to order confidently on their own. If the honest answer is no, that is exactly the gap worth closing.

It is also worth noticing who tends to ask this question most. First-time guests ask it far more than regulars, which makes sense, regulars already have a favorite they return to. That means the what's good here moment is disproportionately happening during a guest's very first impression of your restaurant, which is exactly the visit you most want to get right without leaving it to chance or to whichever server happens to be free.

TasteGraph reorders each guest's menu based on what they are likely to enjoy and can surface bestsellers and dishes worth highlighting automatically, so the question of what's good here gets answered by the menu itself, consistently, for every table, rather than depending on whichever server happens to be walking by.