Menu Writing: Good Dish vs Workable Kitchen

Kitchen FundamentalsTools, Systems & Process

A menu that works on paper but falls apart in service is one of the most common and quietly devastating mistakes a kitchen can make. Getting the balance right between what excites a chef and what a kitchen can actually deliver, consistently, night after night, is the whole job.

I once worked under a chef who redesigned the menu every fortnight. Not because the seasons demanded it, not because the suppliers had something extraordinary in, but because he got bored. The food was technically brilliant on day one. By day four, with two chefs off sick and a full house booked, it was a disaster. Beautiful ideas reduced to sweating line cooks and cold plates. The guests never knew why things felt slightly off. We did.

A Good Dish and a Workable Kitchen Are Not the Same Thing

This is the tension at the heart of every menu. A dish can be genuinely delicious, technically interesting, and completely wrong for your kitchen. Maybe it requires a last-minute reduction that ties up your only sauce pan during the rush. Maybe it needs a garnish that wilts in four minutes, which is fine during a quiet Tuesday but carnage on a Saturday. Maybe it simply takes thirty seconds longer than everything else on the pass, and thirty seconds, compounded across eighty covers, is the difference between a good service and a grim one.

Writing a menu is not a creative exercise in isolation. It is a logistical document dressed up in appetising language. The best menus I have eaten from, and the best ones I have written, are the ones where you cannot see the engineering underneath. Everything arrives at the right temperature; nothing is rushed, and the kitchen is not audibly suffering. That takes planning, not talent alone.

Start With What You Can Actually Do

Before you write a single dish, take an honest look at your kitchen. How many covers are you doing? How many competent hands do you have on a busy night? What equipment do you have, and what is its realistic capacity? A single oven at 200 degrees cannot simultaneously roast a rack of lamb to order, hold a confit at serving temperature, and finish a soufflé. Something will suffer. Usually the lamb.

This is not about ambition. Ambition is good. This is about honesty. The most satisfying menus I have written came out of tight constraints: three courses, a short kitchen brigade, proper British produce, and the discipline to do fewer things very well. That is not a limitation. That is a philosophy.

Map Your Kitchen’s Choke Points

Every kitchen has a bottleneck. It might be the grill, the pass, the single fryer, or the fact that your best cook has to run both meat and fish sections simultaneously. Before finalising any menu, walk through a hypothetical service in your head, or better still, do a dry run. Where does everything stack up? Where do orders collide? The answers will tell you more about your menu than any tasting session.

How to Write a Menu That Holds Together

Build around your larder, not your imagination. Start with what is genuinely in season and genuinely available from your suppliers. A menu built around proper asparagus in May is more exciting than one promising asparagus in October. The ingredient does the work when it is right. Your job is not to fight it.
Design for the brigade you have, not the one you wish you had. Each dish should be executable by the cooks actually standing in your kitchen. Be realistic about skill levels. A technically demanding garnish that requires a senior chef to finish every plate is a liability when that chef calls in ill.
Vary the cooking methods across the menu. If three of your main courses require the grill, you have written yourself into a corner. Spread the load: something braised, something roasted, something served at room temperature. This is not about variety for the guest (though that helps); it is about giving your kitchen a fighting chance.
Think in components, not just finished dishes. A good restaurant kitchen is built on intelligent prep. If your lamb dish uses a rosemary jus that also appears in the beef dish, that is smart. If every dish needs its own entirely separate sauce made from scratch to order, you have written a menu for a brigade twice the size of the one you employ.
Price for reality, not aspiration. A dish that requires three hours of prep per portion and a specialist ingredient with a thirty per cent wastage rate needs to be priced accordingly or cut. Sentiment is expensive. Run the food cost numbers before the menu goes on the board, not after the first week of trading.
Test it under pressure. Write the menu, taste it, and adjust it. Then imagine it during the busiest service you have ever had, with two people off and a large party on a special dietary requirement. Would it hold? If the answer is no, something needs to change before the guests find out.

The Language of the Menu Matters Too

A menu description is a promise. “Pan-roasted sea bream with a saffron and mussel velouté” sets an expectation. If the bream arrives steamed and the velouté is thin, you have broken that promise regardless of how it tastes. Write what you are actually serving, not the glossiest version of it. Guests are not fooled, and experienced ones will feel patronised.

Keep the language clean. A dish described in three lines is usually trying to hide something: either the dish is too complicated, or the writer does not trust the ingredients to speak for themselves. A properly sourced piece of hake with spring vegetables does not need a paragraph of justification. It needs to be cooked well and served hot.

Seasonality Is Not a Trend; It Is the Point

I get mildly irritated (which, for me, is quite a strong feeling) when menus treat seasonality as a marketing angle. Proper seasonal cooking is not about branding. It is about the fact that a tomato in August tastes completely different from one flown in during January, and no amount of olive oil will fix that. Build your menu around what is genuinely ready, not what is available in a theoretical supermarket sense.

Talk to your suppliers. Not just to order, but to ask what is coming through in good condition, what was caught well, and what the farm has too much of this week. Some of the best dishes I have ever written started with a supplier ringing to say he had surplus forced rhubarb and what did I want to do with it? That kind of relationship produces better food than any amount of trend-watching.

Frequently Asked Questions

How often should a restaurant menu change?

Often enough to reflect the seasons, not so often that your kitchen never gets the chance to execute a dish properly. A quarterly framework with weekly specials built around what is fresh that week is a sensible structure for most kitchens. Change for the sake of change is exhausting and rarely improves the food.

How many dishes should be on a menu?

Fewer than you think. A shorter menu is almost always a sign of a kitchen in control of what it is doing. Three or four starters, five or six mains, and three desserts are plenty for most restaurants. Every dish you add is another set of components to prep, another potential point of failure during service. Edit ruthlessly.

Can these principles apply to home cooks planning a dinner party menu?

Absolutely, and the logic is identical. Do not attempt a soufflé when you need to be at the table with your guests. Do not plan three dishes that all need your oven at different temperatures simultaneously. Choose one dish that requires your full attention, and build the rest of the meal around things that largely look after themselves. Cooking for guests should be a pleasure, not a hostage situation.

What is the single biggest mistake in menu writing?

Writing for the plate rather than the kitchen. A dish that photographs beautifully but creates chaos during a busy service will eventually show in the food. The guest may not be able to name what is wrong, but they will feel it: the slightly rushed garnish, the sauce that is a degree too cold, and the protein that is a touch overdone because the section was overwhelmed. Consistency is craft, and a good menu protects it.

The real test of a menu is not how it reads on the board or how it photographs on the pass. It is whether your kitchen can cook it properly on a wet Wednesday in February when the reservations are full, one of your cooks has gone home with a bad back, and the supplier delivered the wrong cut of beef. If it holds then, you have written something worth serving.