Why do so many restaurants close even with great food?

If you've worked in restaurants, you already know how the story ends. A place opens with good food, good atmosphere and guests who recommend it. Two years later it's closed. And when you ask what happened, nobody says the food was bad.

The numbers are hard: most restaurants never make it to five years. What almost nobody mentions is that cooking rarely shows up on the list of reasons.

Guests don't remember the dish. They remember the wait

Think about the last time you had a bad time at a restaurant. It probably wasn't because the food was cold. It was because nobody came to your table, because you asked for the check three times, or because you sat for twenty minutes staring at an empty plate.

Food is what you sell. Service is what gets remembered. And service falls apart in the details: who greets you, how long it takes to order, how fast you can leave when you're ready to go.

The food can be excellent, but if service falls apart, the guest remembers the wait.

The real problem: you don't know who stopped coming

The average restaurant knows exactly how much it sold yesterday. Almost none know who they sold to. That difference is expensive.

When you only see sales, a bad month looks like a bad month. When you see guests, you notice that the family who came every Friday hasn't shown up in six weeks, that new guests aren't returning, that you lost an entire group after one specific night.

• You can't tell whether that table was new or a regular.
• Nobody notices when someone stops coming.
• A bad experience disappears among the day's checks.
• By the time it shows in the monthly close, six weeks have passed.

And here's the part that matters: you can't win back someone you never identified.

Staff turnover takes the operation with it

Turnover in restaurants is high and it isn't going away. The problem isn't that a server leaves. The problem is that the way of operating leaves with them: how orders get entered, how payment is taken, how a big table is handled.

When everyone runs it their own way, service depends on who happens to be working that shift. Guests feel that, even if they can't explain it.

When something fails, response time defines the shift

Friday at 8:30 p.m., the kitchen stops printing tickets. At that moment it doesn't matter how many features your system has. What matters is how long it takes to fix.

If the answer is a case number and an automated email promising 48 hours, the shift is already gone. And with it, the tables that were waiting at the door.

So what can you actually do?

There isn't one answer, but there is a pattern among restaurants that last: they don't depend on a single person, a single register or a single way of operating.

• Guests can move forward even when the server is busy.
• You can take payment even when the card reader is at another table.
• The operation doesn't stop if a device breaks.
• Someone answers when something fails, at any hour.
• You know who comes, who returns and who stopped coming.

None of that changes your recipe. All of it changes whether the guest comes back.