A menu can get bigger one perfectly reasonable decision at a time.
A seasonal item stays. A franchisee wants a local favorite. A new sauce gets added to support a promotion. Nobody wants to disappoint the guests who still order the old version.
Eventually, the restaurant is carrying a collection of decisions made years apart, under different circumstances. Each item has a defender. The total workload rarely gets the same attention.
Picture a menu ranked from most ordered to least ordered. A handful of popular dishes form the head of the sales curve. The many items that each sell in smaller numbers stretch out behind them: the long tail. Together, those items can add meaningful sales, but each may also require ingredients, prep, storage and training. Low volume alone does not make an item a bad choice; the question is whether its value to guests and the business justifies the work it creates.
For a smaller brand, the cost shows up in prep lists, cooler space, waste, training and the lunch rush.
The fear of cutting is understandable. You can see the sales attached to an item. It is harder to see the sales you might be losing because the whole restaurant has become slower or less consistent.
My work at Panera, CoreLife, Noodles and Tatte has spanned both menu development and the operating realities behind it. Long-tail complexity develops at most restaurant concepts as menus evolve. When I look at a crowded menu, I want to know which choices guests truly value and what the restaurant must do to deliver them.
Start with the guest you could lose
Sorting the menu by sales is a useful first step. Automatically cutting the bottom twenty percent is a poor second step.
A lower-volume item may be the only satisfying option for a vegetarian in a family of four. A regional favorite may be essential in one market and irrelevant elsewhere. Something that looks marginal in the item report may help keep an entire occasion in your restaurant.
Ask who orders it, how often they return and what else they would choose. Look at transactions and guest behavior where the data allows it. Talk to operators and guests where it does not.
The practical question is how much business would leave, rather than move to another item. You will not know that perfectly in advance. You can learn enough to make a better decision than either keeping everything or cutting blindly.
Find the work attached to the item
Next, take the analysis into the restaurant.
Does this dish require an ingredient used nowhere else? A separate prep batch? A short shelf life? Another pan on an already crowded line? Does it interrupt the station handling your highest-volume products?
Consider two hypothetical slow sellers. One uses existing ingredients and takes a straightforward assembly step. The other needs its own sauce, garnish, prep routine and training. Similar sales can create very different burdens.
Look beyond food-cost percentage to contribution dollars, then identify waste and work you can actually remove. Do not book theoretical labor savings if the schedule will remain unchanged. Less preparation may create useful capacity without reducing payroll immediately.
And follow the ingredient through the menu. Removing one dish saves little if its special component remains in three others.
Sometimes you should simplify the production
At CoreLife, our beverage program was extensive, and making drinks from scratch created challenges with flavor and day-to-day consistency. We moved to Tractor beverages, which fit our ingredient standards and were easier for the operating teams to use. I discussed that decision publicly in 2021.1
That was a production decision. It illustrates why counting menu items alone can miss the opportunity. You may be able to preserve a guest choice while removing unnecessary work behind the counter.
Before deleting something guests value, ask whether a common ingredient, a better preparation method or an appropriate supplier solution could make it easier to deliver without compromising the reason people buy it.
Give each item a decision
During my time at Noodles, the menu transformation included testing additions and removals together. In August 2024, the company described removing three dishes in testing while assessing new dishes for guest response, operational feasibility and financial effects, including changes in menu mix.
At the same time, it planned to feature Spicy Korean Steak Noodles because awareness was low while satisfaction and appeal to younger consumers were strong. Low awareness was a reason to give that dish more attention.2
That distinction matters. An item may need better visibility, a stronger recipe, simpler production or a replacement. Others have had a fair chance and no longer justify their place.
Make the decision explicit. If an item earns an exception because it serves an important guest need, say so and define how you will evaluate it. Otherwise, an exception can become permanent simply because nobody revisits it.
Test the removal as carefully as the launch
Choose a manageable group of representative restaurants and a clear comparison. Avoid changing prices, promotions and half the menu simultaneously if you want to understand the result.
Give the team a good alternative to recommend. Make sure ordering screens and delivery menus match the test. Plan the inventory transition so the restaurant is not stuck with a case of an ingredient it can no longer use.
Agree beforehand on the review period and what would trigger a pause or reversal. Watch total transactions, repeat visits where measurable, contribution, waste, service times and guest feedback. Account for seasonality and differences between locations.
A few complaints deserve attention. They should not automatically outweigh the full result. Nor should a quieter kitchen excuse a meaningful loss of guests. Check both sides.
Keep the long tail from growing back
Put menu review on the calendar, with culinary, operations, finance and marketing looking at the same evidence. Assign someone to own the decisions and verify that the promised simplification actually happened.
Require every proposed addition to explain the guest need, expected contribution, operational demands and review date. Limited-time offers should have an end date and a deliberate decision about staying.
A rigid one-in, one-out rule can miss the point. Replacing a simple item with a complicated one may make the restaurant harder to run even though the menu count is unchanged.
The aim is a menu your guests have good reasons to choose and your teams can execute well every day. Trimming it becomes less frightening when you understand what you are protecting, what you are removing and how you will know whether the decision worked.
Sources
1. Tractor Beverage announcement, August 17, 2021. Includes Scott Davis’s explanation of CoreLife’s beverage production change.
2. Restaurant Dive, August 8, 2024. Reports Noodles’ test removals and its decision to feature Spicy Korean Steak Noodles.