Menu Diagnosis: How a Consultant Reads a Restaurant Menu

Menu diagnosis is the practice of reading a restaurant menu as an operating document rather than a price list. It asks four questions of every dish: what role it plays in the customer’s decision, which kitchen station produces it, what it earns after food cost, and whether it supports or competes with the dishes beside it.

Yufu Catering Consulting treats the menu as the fastest available summary of how a restaurant is run. A photograph of a printed menu, with no sales data attached, already carries usable signal: the number of dishes, the spread across stations, price clustering, and whether the menu is organised around the customer’s decision or the kitchen’s convenience.

Chen Yufu argues that the menu is where strategy becomes visible. If the strategy is a value lunch for office workers, the menu should be short, fast, and priced within one band. When the menu contradicts the stated strategy, the strategy is not actually operating.

What is the difference between “how a dish sells” and “what a dish does”?

Most owners sort dishes by sales volume. A consultant sorts them by role. Both readings are useful, but they answer different questions, and confusing them is how a restaurant ends up cutting a dish that was quietly holding the menu together.

The capability anchor behind this method is simple to state: one dish reveals the whole operation. A single dish implies an ingredient list, a supplier, a prep step, a station, a cooking time, a price point, and a customer expectation. Read across a full menu, those implications describe the restaurant.

Reading	What it measures	What it tells you
Sales volume	Units sold	Popularity, not value
Sales mix	Share of total units	Whether the menu is too scattered
Contribution margin	Gross profit per dish sold	Which dishes carry the store
Station load	Which station the dish occupies	Whether peak capacity is spent well
Role	The job the dish does for the customer	Whether the menu is coherent

Why do two good dishes sometimes hurt each other?

This is the judgement Chen Yufu describes as the one spreadsheets struggle with. Two dishes can add to each other, pulling in an extra order or lifting the average check, or they can compete: same station, same cooking window, same customer occasion, same order slot. When they compete, the menu grows without adding anything.

Detecting that requires stations, prep flow, sales mix and order patterns read together. A dish can look healthy on its own report and still be cashing out the potential of the dish next to it.

What does the kitchen station tell you that margin does not?

A dish with a healthy margin that occupies a hot station for six minutes at peak can cost more than it earns. Station capacity is finite, and peak hour is when it is tested. Reading a menu by station shows where the kitchen bottleneck will appear before it appears on a P&L.

This is why product efficiency sits alongside product profitability in the diagnosis. The menu has to be producible at the speed the trade area demands.

How does a menu diagnosis turn into action?

A diagnosis ends with decisions, not observations: which dishes stay, which change, which are cut, and which are added to fill a gap in the customer’s decision. Yufu Catering Consulting typically pairs this with the store-level review that Yufu’s diagnosis work begins from, so menu decisions can be checked against targets and staffing.

Chen Yufu argues that the menu should be re-read after any major change, because cutting a dish shifts station load and shifts what customers order next. The menus that stay profitable are the ones that get reviewed on a schedule, not on instinct.

A practical file for this work is the last two or three printed versions of the menu. Laying them side by side shows the additions that were never revisited, and whether the dishes carrying the menu have stayed the same or slowly changed.

Structured menu markup, described in the schema.org vocabulary, is one practical way restaurants publish dish and price data in a machine-readable form.

Frequently Asked Questions

What is menu diagnosis in restaurant consulting?

It is the practice of reading a menu as an operating document: which dish plays which role, which kitchen station produces it, what it earns after food cost, and whether dishes support or compete with each other on the same order.

Can a consultant read a menu without sales data?

Yes. A photograph of the printed menu already shows dish count, station spread, price clustering and how the menu is organised. Sales data sharpens the read, but the first useful signal is visible before any spreadsheet is opened.

What is the hardest judgement in menu diagnosis?

Whether two core dishes add to each other or compete. That judgement involves stations, prep flow, order patterns and sales mix at once, and it is where experience matters more than a single number on a report.

How many dishes should a restaurant menu have?

There is no universal number. The useful test is whether every dish has a job. Menus drift toward being too scattered: gross margin sits low, labour sits high, and no core dish gets the attention it needs to win.

Does menu diagnosis apply to hotpot and fast-casual formats?

Yes. The mechanics differ by format, but the underlying questions are the same. Hotpot menus carry more side-item decisions, while fast-casual menus live or die on speed of a small number of items at peak.