The Vanishing Middle of the Menu

Why Removing Dishes Takes More Courage Than Adding Them

Menus are getting smaller. Not because restaurants have less to say, but because they can no longer support saying everything at once.

Across dining rooms at every level, the middle of the menu is thinning. The second risotto. The third fish. The pasta that sells occasionally but requires its own mise en place. These dishes were never the signature or the staple. They were insurance. And insurance, as any operator eventually learns, is expensive in ways that don’t always show up on a single invoice.

What remains on many menus today is not minimalism for its own sake. It is correction. And understanding why that correction is so difficult to make — why operators who know exactly what the numbers are saying still hesitate to act on them — reveals something important about how hospitality businesses actually work, and where they most reliably fail.

How Menus Get Bloated

When I opened Formaggio Grill, transitioning from a wine bar concept to a full restaurant, I had a chef who had a hard time saying no. His instinct was generosity. His answer to every idea, every addition, every request to put one more thing on the menu was: yes, we can do it.

He was not wrong about the kitchen’s capability. He was wrong about the cumulative cost of saying yes to everything. Each new dish brought its own prep requirements, its own storage demands, its own training burden, its own failure points during service. The menu grew because nobody in the room had the discipline — or the authority, or perhaps the willingness to disappoint — to say: not this one. Not alongside everything else we are already doing.

This is how most menus get bloated. Not through a single bad decision, but through a succession of yeses from someone whose enthusiasm and skill made every addition feel manageable in the moment. The problem is never visible in any single dish. It is visible in the aggregate — in prep lists that run too long, in ticket times that stretch during peak hours, in the quiet exhaustion of a kitchen trying to execute too many things at once.

A menu with 28 items instead of 18 might increase perceived generosity by 30 percent. It can increase prep time and waste exposure by far more. The cost of the middle is rarely visible on a single invoice. It appears in labor creep, food spoilage, and ticket times that stretch precisely when they cannot afford to.

The chef who cannot say no is one of the most common figures in professional kitchens. He is talented, committed, and constitutionally unable to push back against the excitement of a new concept or a new dish. The menu grows because his generosity is real, and because the people around him mistake that generosity for operational confidence. By the time the problem is visible in the numbers, the menu has already become something the kitchen was never actually designed to support.

The Menu as Labor Model

Restaurants often treat labor as a scheduling variable. In practice, labor is embedded in the menu long before the schedule is written.

Every dish dictates station capacity, skill requirements, and margin for error. Add one specialty item that requires separate sauce work and its own garnish, and you may increase station time by fifteen minutes per shift. Multiply that across five days and you have added hours of paid labor without adjusting revenue by a single dollar. The dish might sell twelve covers a week. The labor cost of supporting it is invisible in the menu mix report but very visible in the payroll.

Broader menus also increase training complexity in ways that compound quickly. New cooks must master more components. Inexperienced staff rely more heavily on senior supervision. Error rates rise. In a tight labor market, that fragility shows immediately. A bloated menu collapses when one cook calls out. A focused menu absorbs the absence.

High-performing kitchens increasingly design menus around cross-utilization — shared sauces, shared garnishes, modular components that serve multiple dishes without multiplying prep requirements. Fewer unique ingredients. Tighter pars. Higher inventory turns. The system learns faster when noise is removed, and the noise on most menus is concentrated in exactly the dishes that sell least and cost most to support.

The Courage the Industry Doesn’t Reward

I was recently in a conversation with senior leadership at a well-known hospitality group. The menu numbers were clear. Several items were underperforming by every measurable standard — velocity, contribution margin, table frequency. The marketplace had moved past them. The data said so plainly.

The response was equally plain: those items have been on the menu for years. A few regulars order them. We don’t want to alienate them.

This is the conversation that happens in every hospitality business that has held a dish past its useful life. It is not a conversation about data. The data is not in dispute. It is a conversation about the emotional and professional cost of saying no — to a tradition, to a regular’s loyalty, to the implicit promise that what has always been there will continue to be there. Removing the dish feels like admitting something. It feels like retreat. And the industry does not train people to retreat gracefully, even when retreat is the correct tactical decision.

The consultant who recommends cutting twelve items from a menu is delivering news that feels like failure even when it is the opposite. The operator who accepts that recommendation is making a leadership decision that the dining room will benefit from immediately and never once think to credit.

Long menus often signal ambition. More often they signal hesitation — fear of losing a guest who wants something slightly different, fear of negative feedback about limited options, fear of committing to a narrower identity. Hedging spreads attention thin. Dishes that are rarely ordered still require prep. Proteins that sell twice a night still demand storage and monitoring. Those items tie up cash and cooler space while contributing minimally to contribution margin. Removing them is not retreat. It is clarity. And clarity, in a kitchen, is a form of leadership.

What Japan Understands

I returned recently from Japan, where the relationship between menu scope and execution quality is impossible to miss once you have spent enough time in dining rooms there.

Very few serious Japanese restaurants operate with large menus. The ramen shop serves ramen — perhaps three or four variations, each one refined to a degree that a broader menu could not support. The tempura counter serves tempura. The soba house serves soba. The focus is not a limitation. It is the entire point. The kitchen knows exactly what it is responsible for delivering, and that knowledge travels through the service without friction — from the cook to the server to the guest, in the form of food that arrives with the unmistakable quality of something that has been made the same way, correctly, thousands of times.

What a guest feels in those rooms is steadiness. A controlled confidence that is immediately distinguishable from the ambient tension of a kitchen trying to execute too many things at once. You feel it before you can name it — in the pace of service, in the way the server speaks about the menu without hesitation, in the consistency between what arrives and what was described. The dining room feels like a room where everyone knows what they are doing, because they do.

Focus in the kitchen produces confidence in the dining room. That confidence is what the guest registers as quality, often without understanding its source. They credit the food. The credit belongs to the decision about what not to cook.

The Cheesecake Factory exists as the deliberate opposite of this model, and it is instructive for exactly that reason. A menu that runs to over two hundred items is not a failure of discipline — it is a business model, built on industrial-scale kitchen infrastructure and centralized prep systems designed from the beginning to support that complexity. It works because the operation was engineered to support it. Most restaurants attempt a version of that complexity without any of the infrastructure, which is where the damage is done. The Cheesecake Factory is not a cautionary tale about menu length. It is a cautionary tale about attempting complexity without the systems to sustain it.

What Subtraction Actually Requires

Shrinking a menu requires more discipline than expanding one. This sounds obvious. It is rarely treated as such.

Expansion is easy to justify. Each addition carries its own rationale — a guest request, a seasonal opportunity, a chef’s enthusiasm, a competitor’s success with something similar. The yes that adds a dish to a menu is almost always defensible in the moment. The no that removes one requires the operator to absorb the discomfort of the decision without the immediate validation that comes from a new dish’s early orders.

These decisions are made in office chairs and prep meetings, often quietly, often reluctantly. They mean removing items that someone likes. They mean accepting that not every preference will be represented. They mean committing to depth instead of range and trusting that the guest will recognize the quality that focus produces even if they never consciously connect it to the shorter menu in their hands.

What remains after the middle disappears must justify itself daily. Each dish earns its place through velocity, margin, and execution. The kitchen develops genuine expertise in a smaller set of preparations rather than functional competence across a larger one. Consistency strengthens. And consistency, over time, builds the kind of trust that a broad menu — however appealing it appears on paper — cannot produce through range alone.

The dining room may not know what was removed. It will recognize what no longer feels strained. That recognition — felt but rarely articulated — is what brings guests back.

The End of Unnecessary Complexity

The vanishing middle of the menu is not a trend. It is a correction — slow, uneven, and still incomplete in most operations, but directionally correct for reasons that are simultaneously operational, financial, and experiential.

Operators who make the cuts honestly, who remove the dishes that are costing more than they contribute and resist the pressure to add them back under different names, are making a leadership decision that the industry does not celebrate and the guest never directly credits. The result shows up in kitchens that run cleaner, service that flows more confidently, and dining rooms that feel like rooms where someone is actually in charge.

That feeling is not accidental. It is the direct consequence of someone having the discipline to say no — to the chef whose answer is always yes, to the leadership team that won’t let go of a dish the numbers condemned two years ago, to the instinct that more is safer than less.

For many restaurants, that discipline is not aesthetic. It is the difference between whether the lights stay on.