Fable
The food runner and the person reading the menu
The banquet hall's kitchen line is divided into two processes. The first is the menu reader—after guests order, they must judge which dish can be made at which stove, which should be cooked first, and whether a substitute is needed. The second is the food runner—after the stove finishes cooking, the runner carries the dish to the guest's table.
The new foreman Xiao Kong noticed that customers had recently been complaining about slow service, so he focused directly on getting the food runner to improve. The runner's speed increased from two trips a minute to three, but complaints did not drop. Xiao Kong added another food runner, and the two ran together, but complaints still did not drop. Xiao Kong grew anxious and said the problem was in the food-running step.
Old Tu, the senior chef in the back kitchen, pulled Little Kong over to stand beside the menu reader for ten minutes. Old Tu said: watch what he is doing. When this person gets a menu, he does not sort it first; he reads straight down in the order on the slip. Braised pork takes forty minutes, while smashed cucumber takes only two. He called out the braised pork first, and the five cold dishes behind it all got stuck waiting. No matter how fast the runner is, there is no dish on the stove to run.
The small hole changed the process. The person reading the menu classified first: fast dishes were ordered first, slow dishes were marked with estimated times, and similar dishes could be cooked together. After classification, it was passed to the stove, and after the stove finished cooking, it went to the server. On the day of the change, average serving time dropped from twenty-eight minutes to fourteen. Complaints fell to zero.
Xiao Kong later reviewed this and drew a process card. What the menu reader does is called "dish scheduling"—choosing which stove, in what order, and whether there is a substitute. What the food runner does is called "dish delivery"—carrying the cooked dishes to the table. The two roles sit next to each other, but the bottleneck is in the first one. He spent two months optimizing the second, which only amplified the errors of the first.
Old Tu said: Slow food delivery may be the server's problem, or it may be that there is simply no food on the stove. Look at the stove first, then at the delivery—when there is no food on the stove, the server standing still is not because he is lazy, but because the earlier decision gave him nothing to deliver. Pairing a fast server with a confused menu reader is like giving an extremely responsive system the wrong tools.
The banquet hall later produced a training manual. The first page had a flowchart with four words written beside it: Dispatch comes first. During new employee onboarding, Old Tu would call them over and have them feel what it's like to be a food runner sprinting down the corridor empty-handed. After one lap, he'd ask: Do you think he ran fast enough? Everyone said yes. Then he'd ask: So why do you think he had no dishes in his hands?
The answer to the last question was written on page two of the manual: when serving is slow, do not first assume the food runner is not fast enough. First check the person reading the menu—whether he chose the right stove, whether he ordered the sequence correctly, and whether there is an alternative.