What a Menu Tells Me Before I Taste Anything

Before I walk a kitchen, I ask for the menu. Not to see what they cook. To see how they think. A menu is the most honest document a restaurant produces. The marketing flatters, the Instagram flatters, the mission statement most of all. The menu can’t, because it’s the one artefact where every decision has a cost attached, and costs don’t flatter anyone.

Give me two minutes with it and I’ll have a working theory of the operation before anything hits my table.

Length is a confession

Start with the count. A menu with sixty dishes usually isn’t generous. It’s nervous.

Somewhere along the way, someone couldn’t decide, or couldn’t say no to a partner, or lost a few weeks of sales and thought the answer was more choice. So they added. Nobody ever takes a dish off. Removing a dish feels like admitting failure. So menus grow like scar tissue. And every additional dish is another set of ingredients to hold, another prep to build, another SKU to waste, another thing a cook has to remember at 9pm on a Saturday when four tables land at once.

A sixty-item menu tells me the walk-in is full of slow-moving stock, the prep list is unmanageable, food cost is quietly bleeding, and consistency is impossible because no station can be good at that many things. A tight menu, say, twenty-five to thirty-five across the whole card, tells me someone made decisions and lived with them. That person is usually running a healthier kitchen, because the discipline that trims a menu is the same discipline that runs a clean line.

Look at what repeats

Now I read the ingredients across dishes, not down them. This is where the real intelligence is.

A well-built menu shares components deliberately. The same confit, the same base sauce, the same pickle, the same dough, showing up across several plates in different clothes. That’s a kitchen that understands sub-recipes and cross-utilisation — one prep feeding six dishes, one delivery of an ingredient turning over fast enough to stay fresh and cheap. When I see that pattern I relax a little, because it means someone costed this thing and built it to be produced, not just to photograph.

The opposite is the menu where every dish is an island. Thirty plates, and barely an ingredient appears twice. It reads impressive and it cooks like a nightmare. That kitchen is holding a vast, fragmented inventory, most of it moving too slowly, and the food cost will be brutal no matter how well they buy. A menu of orphans is a purchasing problem wearing a chef’s hat.

The tells of fear and vanity

Menus leak the psychology of the people who wrote them.

When I see a truffle special hand-written on a clip, a market-fish-of-the-day, a rotating pasta: good signs. That’s a kitchen confident enough to flex, using the card to move product and keep cooks engaged. When I see everything laminated, frozen in place, unchanged for two years, I read a kitchen that’s either coasting or afraid to touch anything in case the whole fragile system falls over.

Descriptions tell me things too. Over-written prose — six adjectives, three provenances, a story about the farmer for a dish that’s fundamentally a chicken — usually means the food itself isn’t carrying the weight, so the copy is compensating. The best menus tend to under-describe. “Turbot, brown butter, capers.” They trust the plate. A kitchen that trusts its plates usually has plates worth trusting.

And I always look at where the money dish sits. If the highest-margin item is buried mid-list in the same weight and typeface as everything else, nobody’s engineering this menu; they wrote it and walked away. If it’s positioned where the eye lands, boxed or given a little air, someone is actually managing the mix. That single detail tells me whether the menu is being actively managed, or was written once and left to fend for itself.

Price architecture

The spread of prices is a map of the concept’s confidence. A card where everything clusters within a few dirhams, every starter the same, every main the same, is a kitchen that hasn’t thought about anchors, trade-ups, or how a guest actually builds a bill. A menu with a deliberate high anchor, a cluster of workhorse mid-price dishes doing the volume, and a couple of accessible entries at the bottom is a menu built by someone who understands that the point isn’t the price of any one dish, it’s the average check and how you steer it.

I also watch for the gap between what’s priced high and what’s priced to sell. The chef’s-ego dish, the expensive, complex, low-selling showpiece, is fine to have, as long as the operator knows it’s a marketing cost, not a margin driver, and the real money is being made by the dishes nobody writes home about. When the ego dish is also expected to carry the P&L, the numbers never work, and no amount of covers fixes it.

Why this matters before the tasting

None of this replaces eating the food. Of course I taste. But by the time I do, I already know where to look, because the menu has told me where the operation is likely soft: the stations that are overloaded, the ingredients that are probably sitting too long, the dish the kitchen is quietly ashamed of, the mix nobody’s managing.

A menu is a plan, a cost sheet, a training document, and a piece of psychology, all at once, printed on one page and handed to strangers. Most operators treat it as decoration: the last thing designed, outsourced to whoever does the graphics, changed reluctantly. That’s a mistake. It’s the single densest piece of evidence about how a place is run.

So the next time you want to understand a restaurant, don’t ask about the concept. Ask for the menu, and read it like the confession it is.