Menus Food

Building Menus That Actually Work in a Real Kitchen

You would be surprised how many restaurants run on menus that were built by someone who has never stood on a line during a Friday night rush. I spent seven years working in kitchens before I ever stepped into a management role, and the first thing I learned is that a menu is not a marketing document. It is a set of operational constraints. Treat it like one and you save yourself months of head-scratching later. Start with your equipment and your labor, not with inspiration. I had a client once who wanted to serve a tasting menu with twelve courses in a 40-seat space using three cooks. The menu looked beautiful on paper. It failed in two weeks because the kitchen couldn't get the hot plates out fast enough and the expeditor was essentially calling out orders by hand at the pass. The workaround was brutal but simple: we cut it down to a four-course rotating seasonal menu and added a dedicated prep cook whose only job was station mise en place. Food cost stayed the same. Ticket times dropped from eighteen minutes to nine. Revenue went up because we turned tables faster instead of trying to charge more for a show. When you are designing menus food, here is what actually matters in practice:

Map every dish back to a piece of equipment and a person. If a dish requires a salamander and you only have one, that dish becomes a bottleneck the moment two customers order it at the same time. I learned this the hard way when a new grill station was installed in a space that already had a flat top, a charbroiler, and a plancha. We added five grilled items to the menu assuming the new equipment solved our speed problem. It did not, because the plancha was the size of a yoga mat and two pans covered most of it. We ended up holding tickets for eight minutes waiting for grill space. The fix was removing three of those items and making the remaining two truly special so guests did not expect them every visit.

Structuring Your Menu for Profit and Sanity

Menu layout is psychology, but it is also math. People do not read menus linearly. They scan. Eye-tracking studies and actual restaurant observations both show that the top right and the center of a multi-page menu are the high-visibility zones. Put your highest-margin items there. Not necessarily the most profitable dishes in the sense of absolute dollars, but the ones where the margin percentage is strongest relative to labor cost. I used to work at a place where the chef kept putting the seafood tower in the center of the menu because it looked impressive. It was also the lowest margin item on the board and required three different stations to assemble. We moved it to the bottom of the appetizer section, kept the photo but reduced the description from three sentences to one, and watched seafood revenue stabilize while our overall food cost dropped by about four points over two months. The dish did not disappear. Guests still ordered it. We just stopped treating it like a centerpiece. Here is a practical framework I use now:

• List your top five margin items by contribution margin after labor and waste.
• Group dishes by station rather than by course. A menu that follows kitchen workflow reduces cross-call confusion and speeds up the pass.
• Avoid having more than three proteins per category. Decision paralysis is real and it slows ordering down.
• Use plain language in descriptions. Words like "deconstructed" and "artisanal" do not help the kitchen or the guest.

Common Pitfalls That Kill New Menus

The biggest mistake I see is menu inflation without operational change. Someone adds ten new dishes, assumes the kitchen can handle it, and then wonders why ticket times stretch and quality drops. Another mistake is sharing ingredients across too many dishes without tracking it. I worked at a restaurant where seven different appetizers used the same hazelnut-crusted goat cheese log. When we ran out of that ingredient, we could not make half the menu. The solution was to audit every dish weekly, track ingredient overlap, and deliberately diversify or consolidate. We usually consolidate now. Three proteins, two starches, four vegetables that rotate seasonally. It is not glamorous. It works. A second pitfall is pricing without factoring in portability and plating time. A dish that looks simple but requires twelve individual components plated by hand will destroy your covers per hour. I once removed a duck confit dish that had a great margin on paper but took nine minutes to plate because it required microgreens, a gastrique dot, a crisp, a sliced element, and a garnish that wilted if it sat for more than sixty seconds. We replaced it with a whole roasted bird that was cheaper to prep, cooked in bulk, and plated in thirty seconds. Margins improved and the kitchen stopped losing its mind at 7:30 PM.

How to Test and Iterate Without Wasting Money

Do not launch a full menu rewrite all at once. I run a limited test every time. Pick three candidates, run them as specials for two weeks, track sales velocity, waste percentage, and expediter complaints. If a dish sells well but generates repeated complaint tickets, fix the recipe or remove it. Do not keep a dish just because the food cost looks good in theory. The numbers you pull from the POS after two weeks tell you everything you need to know. I also keep a simple spreadsheet that tracks each menu item across four columns: average ticket time, food cost percentage, Gross Profit per unit, and number of comps or modifications per week. Over a month that data becomes obvious. You will see which items are liars. They look fine on paper and they perform poorly in reality. The menu is a living thing. It changes when your suppliers change, when your staff changes, and when the season changes. Stop pretending it does not. If you want a free tool to organize this, most POS systems have built-in menu engineering reports now. If yours does not, a basic Google Sheet with the four columns above does the job. Do not buy expensive software before you have the data flowing from your current setup.