Restaurants Don't Have People Problems. They Have Systems Problems.

There is a moment I have watched in every restaurant I have ever worked in, and it lasts about four minutes. Something goes wrong. A table waits nineteen minutes for a first drink. An entree lands before the app is cleared. A party of eight is seated at a five top pushed against a two top and someone is eating with their back to a service station. In the first minute, nobody says anything, because everyone is busy. By the fourth minute, somebody has a name.

The name is usually the newest person, or the quietest one, or the one who was already having a bad week. Once the name exists, the night has an explanation, and an explanation is a very comfortable thing to have at 8:40 on a Friday. We finish the shift. We say the word coaching. Sometimes we schedule that person a little lighter next week, which everyone understands is a sentence.

And then the same thing happens again in eleven days, to somebody else.

A name is not a diagnosis. It is a place to put your frustration so you can get back to work.

The most expensive assumption in the industry

The assumption is that performance is a property of a person. That some people have it and some people do not, and management is mostly the sorting of one from the other. It is a flattering assumption for owners, because it means the room is fine and the hiring was unlucky. It is also, in my experience on the floor, almost never what is actually happening.

Watch the same server work two different sections and you will see two different employees. Watch a strong closer work a Tuesday with a full staff and then a Saturday where the busser called off, and you are not watching a change in character. You are watching the same person meet two different buildings.

W. Edwards Deming spent his career on a version of this argument in factories, and the line people quote is that a bad system will beat a good person every time. Restaurants are the most emotionally convincing counterexample and the least accurate one, because our systems are invisible. Nobody can point at the machine. The machine is a floor plan, a POS button order, a pre-shift that runs ninety seconds long, and an unwritten rule about who is allowed to comp a dessert.

What a systems problem actually looks like

In a room I worked in, drinks were late every Friday, and the bar took the blame every Friday. I stood at the well for one service with a notepad, which is not a sophisticated research method. Here is what was happening. The two busiest sections were the furthest from the terminal. Servers were batching their orders so they did not have to walk the room twice. The bar received four tickets at 7:52 and none at 7:44. The bar was not slow. The bar was being handed a rush that the dining room manufactured, and then being described in the manager log as slow.

Nobody was lazy. Nobody was careless. Two entirely reasonable people, both doing the sensible thing given where they were standing, produced a problem that neither of them could see. That is what a systems problem is. It is not the absence of effort. It is effort pointed at the wrong thing by the shape of the room.

Everyone was doing their job correctly and the guest still waited nineteen minutes. That is not a people problem. That is a design decision nobody remembers making.

Three questions that usually settle it

When something goes wrong, before anyone gets a name, I want to know three things. Has this happened to more than one person? Did it happen at a specific time or in a specific section? And would a new hire have known what to do, from something they were actually given?

If the answer to the first is yes, it is a system. If the answer to the second is yes, it is a system. If the answer to the third is no, it is a system, and you have been holding people accountable to a standard that exists only in the memory of whoever has worked there longest.

The honest test is uncomfortable. Take the person you blame most often and imagine they quit tomorrow. Does the problem leave with them? Most of the time the problem stays, learns the new person's name, and starts over.

Why we keep blaming people anyway

Because it is faster, and because it feels like management. Rewriting how tickets flow is a Tuesday of unglamorous work with no applause at the end. Having a difficult conversation with a server feels decisive tonight. One of those changes the restaurant and one of those changes the schedule.

There is also something more human going on. If the problem is a person, the owner is not implicated. If the problem is the system, the owner built it. That is a hard sentence to sit with at the end of a long week, and I say it gently, because the owners I work with are not careless people. They are people who have been inside their own shift for so long that they have the worst seat in the house for seeing it.

What changes when you make the switch

The turnover conversation changes first. Then the training conversation, because you stop teaching attitude and start teaching sequence. Then, and this is the part owners tell me they did not expect, the culture changes, because people stop working defensively. When a mistake produces a question about the process instead of a search for a name, the room gets quieter and faster at the same time.

I still work fine dining floors every week, and I have never once seen a restaurant fixed by finding the right person to blame. I have seen plenty fixed by someone standing in the room with a notepad on a Friday, watching where the work actually piles up, and being willing to believe that the people were fine the whole time.