The Menu Nobody Printed

Imagine a small restaurant on a busy Friday evening. This is a hypothetical scene, although few restaurant owners will need much help imagining it. The printed menu has twelve main courses. The kitchen, however, is making something closer to thirty.

One guest would like the sauce from another dish. Another remembers a special from last month. A regular has always been allowed to order a smaller portion. Someone was told on the telephone that the lunch offer could probably be arranged in the evening. Each request seems modest. Each yes sounds hospitable. Nobody believes they have redesigned the restaurant.

Yet a second menu has appeared. It has no prices, no preparation notes and no agreed limits. Its dishes are called “They did it last time”, “It should only take a minute” and “I've already said we can”. Unlike the printed menu, this one can expand indefinitely.

This is not an argument against kindness. It is an argument for noticing where kindness sends the bill. A favour agreed at one table may be paid for in the waiting time of another, the concentration of a cook or the patience of the person trying to coordinate both.

A small change is not always a small job

To the guest, exchanging a side dish may look like moving one thing off a plate and putting another thing on it. Sometimes that is exactly what it is. A sensible operation should not turn a trivial adjustment into a constitutional dispute.

But other requests interrupt a sequence. Someone must clarify what was promised, check whether it is possible, communicate the change, remember it while preparing other orders and make sure the correct plate reaches the correct guest. The ingredient difference may be negligible. The coordination is not necessarily negligible at all.

Consider two imaginary substitutions. The first uses a side already prepared at the same station. The second requires a different station to start an item separately while the remaining dishes wait. They might carry the same surcharge—or no surcharge—but they are not the same operational product. Counting ingredients alone hides the difference.

That distinction matters because a restaurant sells more than plates. It sells a meal arriving in a workable sequence, with enough attention left for guests to feel looked after. A profitable-looking dish can become less attractive if its particular variation repeatedly disrupts that promise. The relevant question is not simply “What does this extra ingredient cost?” but “What else must happen because we agreed?”

The bill goes to the wrong table

Suppose, purely for illustration, that an unusual request needs four minutes of a supervisor's attention during the busiest part of service. Those four minutes are not necessarily four minutes added to every customer's wait. Nor should they be multiplied by every seat to manufacture an impressive loss. Their effect depends on what the supervisor would otherwise have been doing.

Perhaps nothing urgent was waiting. The favour was easy and worthwhile. Or perhaps two completed orders needed checking, a new colleague needed help and a guest was trying to pay. The same request can have a different cost at half past five and half past eight because the restaurant has a different amount of spare capacity.

This is the uncomfortable part: the person who receives the flexibility is not always the person who experiences its consequences. One table sees a generous restaurant. Another sees a distracted one. The staff member who said yes receives the immediate gratitude; colleagues inherit the work required to make the yes true.

No malice is needed. An organisation can create this pattern simply by praising individual helpfulness while leaving shared capacity out of the conversation. Everyone tries to do the right thing locally. The evening becomes harder collectively.

“Last time” is an unofficial contract

A one-off exception rarely arrives with an expiry date. If a guest receives a particular adjustment twice, it is understandable that they start to treat it as part of the offer. The restaurant remembers a favour; the guest remembers a service.

On the next visit, a different waiter says it cannot be done. From the restaurant's perspective, the rule has finally been applied. From the guest's perspective, the service has deteriorated. What looked like generosity has created an expectation that nobody formally accepted responsibility for maintaining.

The solution is not to lecture guests about precedent. It is to make the scope clear when the favour is offered. “We can arrange that this evening because the kitchen has capacity” is different from an unqualified “Of course”. Better still, frequently requested, feasible adjustments can become a small set of recognised options that everyone understands.

A restaurant should not require customers to discover its real offer through persistence or personal connections. When regulars know the unofficial system and newcomers do not, flexibility starts to resemble a loyalty programme with no published terms. That may charm a handful of people while making everybody else uncertain about what can actually be ordered.

Design flexibility instead of abolishing it

There is an obvious objection. Restaurants are not factories, and the ability to recognise a person rather than process an order is part of hospitality. Some places earn their reputation precisely by adapting. A rigid “no substitutions” policy can protect a weak system at the expense of the guest.

That objection is right. The useful distinction is not between flexibility and discipline. It is between flexibility the business can deliver reliably and flexibility it can deliver only through improvisation, favours between colleagues or the heroic memory of one experienced employee.

An owner might agree a short list of straightforward variations, identify requests that need a kitchen check before a promise and clarify which changes the current service cannot support. Staff then have genuine discretion within a shared understanding, instead of either asking permission for everything or promising whatever sounds reasonable at the table.

Safety and accessibility must not be treated as discretionary conveniences in this exercise. Allergy requests require the restaurant's established safety procedures, not an improvised workaround or a calculation about whether a guest is profitable. The discussion here concerns optional commercial variations. Where a request cannot be met safely, politeness does not make an uncertain assurance acceptable.

The strongest boundary is often a useful alternative. “We cannot prepare that version tonight, but this dish gives you the combination you are looking for” keeps attention on the guest's purpose. It takes more judgment than reciting a rule, but less recovery work than accepting a promise the kitchen cannot honour.

Read the menu behind the menu

Before deleting dishes or issuing new rules, observe a few services. Keep a simple record of optional requests: what was asked, what was promised, who had to become involved and whether the same request returned. The point is to understand the system, not build a league table of difficult guests or unhelpful staff.

Separate requests that are genuinely easy from those that merely sound easy. Notice whether the difficulty comes from the food itself, unclear wording on the menu, a mismatch between lunch and dinner offers, or information that never reaches the kitchen. If several guests ask the same question, the printed offer may be doing too little explaining.

Then examine demand as well as disruption. A variation requested every evening may deserve to become a proper option. A complicated dish that attracts guests specifically to the restaurant may justify its demands. Removing everything awkward would also remove some of what makes a restaurant worth visiting.

The National Restaurant Association has discussed operational complexity in menu simplification.[1] That does not mean the ideal menu is always the shortest one. The useful principle is to assess what the team must deliver, not merely count lines on a page. Twelve dishes with endless negotiations can be harder to operate than eighteen dishes with well-understood preparation and variation.

Give the experiment an honest test

Try a limited change over comparable services: clarify two confusing descriptions, formalise one popular adjustment or require a kitchen check for one particularly disruptive request. Tell the team what is changing and why. Do not rewrite the entire operation and then attribute every improvement to a single rule.

Look at order completion times, remakes, complaints, the pattern of sales and the team's account of where work became easier or harder. A faster service that loses valued guests is not automatically a better business. Equally, keeping every possible request available is not proof of hospitality if ordinary orders become unreliable.

Compare similar levels of demand and staffing where possible. A quiet Tuesday is a poor witness for what a new process will achieve on a crowded Saturday. Treat an early improvement as a reason to keep testing, not as a guaranteed margin increase. The goal is a better-informed decision, not a flattering spreadsheet.

The generosity guests can rely on

Well-run hospitality leaves room for judgment. It also recognises that attention, like kitchen space, is finite during a service. Saying yes has consequences; saying no has consequences too. The skill is to understand both before the guest is given a promise.

A useful menu is therefore not just a description of food. It is an agreement between the dining room and the kitchen about what the restaurant intends to do well. The unofficial menu deserves the same care, even if most of it never needs to be shown to customers.

The ambition is not to become a restaurant that makes fewer efforts. It is to stop relying on invisible effort to keep visible promises. Guests should receive warmth because the business has made room for it, not because somebody backstage is rescuing another generous sentence.

There is nothing particularly hospitable about promising one table the world and asking the rest of the room to wait for it.

Source

[1] National Restaurant Association, “Supply shortages impact menu execution”, 28 June 2022. https://restaurant.org/education-and-resources/resource-library/supply-shortages-impact-menu-execution/ — historical industry context, not a claim about current market conditions. The scenarios and operating proposals above are the author's illustrations and analysis.