The Menu Is a Business Plan You Can Eat
Hand a menu to the right person and they can tell you a great deal about the restaurant before a single plate arrives. Not the food. The restaurant.
Whether the kitchen has a point of view or is still auditioning for one. Whether the owner trusts the cooks or is still hedging with a dish for everyone who might wander in. Whether anyone has looked at this document in the last two years with fresh eyes, or whether it has simply been accumulating, one addition at a time, the way silt accumulates at the bottom of a river nobody's dredged.
A menu is not a list of what's for dinner.
It's closer to a confession, written in a font someone chose on purpose, about what this place actually believes it is.
What a Menu Is Actually Doing
Every dish on a menu is a small decision that got made once and then kept making itself, quietly, every single night.
It decided what ingredients have to be sourced and stored, which means it decided how much walk-in space gets used and how much of it might spoil before it sells. It decided how many prep tasks the kitchen has to complete before doors open, which is a labor decision wearing a food costume. It decided what a guest expects to pay, and therefore what kind of guest is likely to walk in expecting it.
A menu also shapes the reasons someone might return, whether to try something they missed or to order exactly the same thing they came for last time.
None of this shows up while you're reading a menu at a table, deciding between the branzino and the short rib. All of it was decided long before you sat down, by someone who may or may not have been thinking about it in these terms at the time.
Generous Is Not the Same as Big
There's a difference between a menu that feels abundant and a menu that has simply gotten too large, and the difference has almost nothing to do with the number of items on the page.
A diner can run forty dishes and still have a completely coherent identity, because most of those forty dishes are built from a shared, overlapping pantry, eggs, bread, potatoes, ground beef, arranged into different combinations rather than forty genuinely separate supply chains.
A neighborhood taco counter running six items can feel abundant precisely because those six are executed with total confidence, nothing hedged, nothing apologized for.
Meanwhile, a tightly edited eight-course tasting menu can still be conceptually confused if course four has nothing to do with the restaurant's actual point of view, borrowed from a trend or a trip the chef took, sitting in the lineup like a guest who wandered in from a different party.
So the useful question was never how many dishes are on this menu.
It's does this menu make sense for this restaurant, which is a completely different diagnostic and a much harder one to run from a spreadsheet.
It's worth being skeptical here of a piece of pop psychology that gets repeated constantly in restaurant circles: the idea, drawn from a widely cited jam-tasting experiment from 2000, that fewer options reliably sell more than many options because of "choice overload."
A 2010 meta-analysis of fifty separate studies on the phenomenon found the average effect across all of them was close to zero, with some studies replicating the original result and others finding the opposite.
The honest version of the finding is that choice overload happens under specific conditions, complexity, unclear differences between options, time pressure, and not as a universal law of how many dishes a menu should have.
A big menu executed with total clarity beats a small menu executed with none, every time.
Size was never really the variable that mattered.
Every dish added past what a kitchen can actually execute well does carry real cost, regardless of what any single psychology study says about the guest's experience of choosing.
Another ingredient to source. Another item competing for a shelf in a walk-in that was never built bigger. Another prep task layered onto a line that's already tight during a rush. Another station now depending on another cook remembering another technique under pressure. Another chance for something to sit unsold long enough to become waste instead of revenue.
That cost is operational, not psychological, and it accrues whether or not the guest ever notices the menu got longer.
The Menu as an Archaeological Site
Almost no restaurant sets out to build a confusing menu.
It usually arrives by accretion.
A special sells well for a few weekends and nobody has the heart to take it off. A regular asks for something off-menu often enough that it quietly becomes on-menu. A new chef arrives with different instincts and adds three dishes without removing the ones that no longer fit the story, because removing a predecessor's dish can feel like an unnecessary fight to pick.
A competitor down the block starts doing something well and it shows up, slightly altered, a few months later. A trend passes through, gets added to capture it, and stays long after the trend itself has moved on, because pulling it feels like admitting it was a mistake to add.
Five years of that produces a menu that isn't really a menu anymore.
It's an archive of every decision the restaurant was afraid to reverse, each one individually defensible, together adding up to something that no longer answers a simple question clearly:
What is this place actually for?
The Dish Nobody Wants to Cut
Here is where this gets genuinely difficult, and where a purely financial view of the menu runs out of usefulness.
Popularity and profitability are not the same thing, which most people in this industry already know.
What gets discussed less is that profitability and belonging aren't the same thing either.
A dish can be making real money and still not belong on the menu, quietly working against the identity the restaurant is trying to build. A dish can be losing money on every plate and still deserve to stay, because it's the reason someone's grandmother started coming in fifteen years ago, or because it's the dish a chef refuses to compromise even though the ingredient cost makes no sense, or because removing it would say something true and unwelcome about what this restaurant has become.
The mistake isn't keeping an inefficient dish.
Restaurants are commercial enterprises, but they are not only that, and pretending otherwise produces menus with excellent margins and no soul.
The mistake is keeping it without knowing why, without anyone in the building being able to say plainly what that dish is costing and what it's buying back in return.
A restaurant that keeps its unprofitable, beloved dish on purpose, eyes open, understanding the trade, is doing something coherent.
A restaurant that keeps it because nobody's ever asked the question is just accumulating, the same way it accumulates everything else it's afraid to touch.
What the Menu Says Before Anyone Tastes Anything
All of this is happening on the operational side of the kitchen door.
On the guest's side, a menu is doing an entirely different job: communicating what kind of night this is going to be, before a single plate arrives.
Language matters more than most menus admit.
A dish described in three careful words tells a different story than the same dish described in a full sentence of provenance and technique, and neither is automatically right, but the choice says something about how the restaurant wants to be read.
Category structure matters: a menu split into small plates, large plates, and sides is telling a guest to share and linger, while a menu organized into starters, entrées, and desserts is telling the same guest to expect a more traditional, sequential meal.
Where a price sits, how it's formatted, what it's positioned next to, all of it shapes a decision well before flavor enters the conversation, though it's worth being skeptical of the more confident claims floating around about menu psychology, the idea that removing dollar signs changes spending in a predictable, universal way, or that guests always read a menu in one specific pattern.
Some of that research is thinner than the confidence with which it gets repeated, and a restaurant's specific guest, room, and price point matter more than any general rule borrowed from an unrelated study.
What's absent from a menu says just as much as what's on it.
No description at all can read as confidence in a well-known cuisine, or as laziness, and the difference usually comes down to whether everything else in the room backs up which one it is.
A menu with no vegetarian option makes a specific, sometimes accidental statement about who this restaurant assumes is walking through the door. A one-page menu with no specials insert says something different than a one-page menu with three inserts stapled to the back, even if the food on all of them is excellent.
A guest reading a menu for the first time is doing, in miniature, the exact same diagnostic work outlined above, just without the vocabulary for it.
They can tell, often within a few seconds, whether the place in front of them knows exactly what it is.
That instinct is usually right, and it usually arrives before the first course does.
Does the Menu Know What Restaurant It Belongs To
A great menu isn't defined by its length, its restraint, its cleverness, or its price point.
It's defined by whether every item on it, and just as importantly, every item that isn't, seems to know which restaurant it belongs to.
That's a harder standard than it sounds, and most menus, examined honestly, would have trouble answering the question if the whole page had to speak for itself.