Why Personalised Menus Beat Generic "Chef's Picks" Sections

A chef's picks section is a genuinely good idea, and nothing about personalisation is meant to argue against having one. The point worth making clearly is that it solves a narrower problem than owners sometimes assume, and understanding the gap between the two clarifies what each is actually good for.

What a chef's picks section does well

It's an editorial statement, a chance for the kitchen to say here's what we're proud of, here's the dish that represents what we're trying to do. That has real value: it can highlight a signature dish, push a new item that deserves attention, or simply reflect the restaurant's own point of view about its food. Guests generally respond well to a clear, confident recommendation from the people who actually made the dish.

Where it runs into a hard limit

• It's the same list for every single guest, regardless of their own taste or dietary needs
• A guest with a spice aversion sees the same picks as a guest who loves heat
• It doesn't update based on what an individual guest has liked in the past
• A guest who's already tried and disliked a chef's pick keeps seeing it recommended anyway

None of these are flaws in the concept of a chef's picks list, they're just the natural limit of a single fixed recommendation trying to serve every guest at once. A restaurant with a genuinely diverse guest base, different ages, different spice tolerances, different dietary needs, is always going to have a chef's picks list that lands better with some guests than others, simply because it was never built with any individual guest in mind.

Running both at the same time

The strongest setup isn't picking one over the other, it's running a chef's picks section as a genuine editorial voice while personalising the rest of the menu's ordering underneath it. A guest still gets to see what the kitchen is proud of, and separately gets a menu that adjusts to their own taste for everything else they browse. The two serve different purposes and neither one replaces what the other is good at.

A concrete case where a fixed chef's pick backfires

Imagine a chef's picks section built around a rich, creamy pasta dish, chosen because it's the kitchen's proudest plate this season. A guest who's lactose intolerant sees it recommended anyway, every single time they open the menu, regardless of how many times they've already skipped past it. That's not a failure of the dish or the chef's judgement, it's just the natural limit of a single recommendation trying to serve a guest base with genuinely different needs. A personalised layer underneath would simply not surface that dish prominently to that particular guest, while still letting the chef's picks tag stand for everyone else it does suit.

How this affects new guests' first impression of your best food

There's an argument that a chef's picks section is most valuable precisely for new guests who have no other basis to decide what to try, and that's fair as far as it goes. But it still only works as well as the average guest it was built for. A new guest whose tastes diverge from that average gets a recommendation that's confidently wrong for them, and a confidently wrong suggestion can do more damage to trust than no suggestion at all, since it signals the menu wasn't really paying attention to who was actually looking at it. Pairing a fixed chef's pick with even a lightweight layer of personalisation avoids that risk without asking the kitchen to give up its own editorial voice, since the two run side by side rather than one having to compromise for the other.

TasteGraph supports keeping a chef's picks or bestseller tag visible as the restaurant's own editorial signal, while personalising the broader order of the menu around each guest's taste, so you get the confidence of a curated recommendation and the relevance of a per-guest experience at the same time.