From the house

When something goes wrong

A stack of white plates against a pale ground

Something goes wrong every evening. A plate arrives late, a dish has run out, somebody gets the wrong thing. A house is not measured by whether that happens but by what occurs in the following two minutes.

Why this is craft rather than chance is in our guide to service.

It happens every evening

Not as an exception but as the normal case, and a house claiming otherwise has either few guests or little honesty.

The order is always the same

Fix it first, explain afterwards. A guest sending back a cold dish does not want an analysis of the cause, they want a hot one. The explanation can follow, briefly, and without blaming anyone in the house.

Then comes a gesture, and it is smaller than people expect. A glass of wine, a pudding, the disputed dish off the bill. What does not help is an extended apology — it prolongs exactly the conversation the guest did not want to have.

The three commonest cases

Something has run out. That belongs said before the menu is read, not after. A house with a short menu following the shopping has this more often than one with forty dishes from a freezer — the connection is in what belongs on one menu and what does not.

It is taking too long. The right response is to raise it before the guest does. Ten minutes late, announced, is information; ten minutes late, unmentioned, is carelessness. How an evening is built in time is in timing at the table.

The dish is wrong. It goes back and is made again, without discussion. A schnitzel that stood a long time at the pass is no longer good, and the coating does not forgive it — what actually matters in a Wiener Schnitzel explains why.

What a guest can do

Say it early. The only genuinely unhappy sequence is the one where somebody eats half a plate, says nothing, and mentions at the till that it was not good. At that point nothing can be done except take money off — and that is the worst outcome for both sides.

And say what is wrong rather than only that something is. "The meat is tough" is usable. "It's not nice" is not.

What a house should not do

Argue about whether the guest is right. In most cases that cannot be established and does not matter either: a returned dish costs the price of its ingredients, an annoyed table costs more.

And visibly shift the blame. "The kitchen has…" is of no interest to a guest — they are sitting in a house, not in a department.

The difference between a fault and a preference

Not every piece of feedback is a fault. A dish can be technically correct and still not suit somebody, and that is no reason to remake it — though every reason to stay friendly about it.

The line falls where something is objectively wrong: cold, raw, overcooked, brought to the wrong person. That goes back without discussion. A dish that tastes different from what somebody expected is a conversation — and sometimes a sign that the menu description could be better.

A house that does not draw the distinction either takes everything back and loses money, or takes nothing back and loses guests.

What happens afterwards

A mistake solved only at the table happens again. So at the end of the evening there is a short conversation about what went wrong — not to find somebody, but to see whether the process caused it.

If the same dish comes back three times in a week, that is not chance but the menu or the flow. What that flow looks like is in how an order travels through a house.

Why it happens at all

Because most of this is handwork performed under time pressure. An evening with sixty guests means several hundred individual actions, and there is no such thing as a zero error rate in that.

What there is, is a process that makes mistakes visible early — at the pass, before the plate reaches the room. What that looks like is in how an order travels through a house.

Book a table — and say so if something is not right.

Share this post
Book a table(opens in a new tab)