Over the years I have walked into many kitchens where one person seemed to know everything. It was not always the chef or the manager. Sometimes it was a line cook, prep cook, purchasing clerk, or assistant manager who had quietly become the person everyone went to when something did not make sense. They remembered the order, knew the pars, understood the strange refrigerator, found the missing product, and somehow knew what Friday night would need before Friday night arrived. These were enormously valuable people, and management often did not realize just how much of the operation had begun to depend on them.

The problem usually revealed itself on the day that person was not there. Suddenly an operation that looked organized became uncertain. People asked questions nobody could answer. A familiar recipe changed. An order was missed. Prep was short. The closing routine that had worked for years turned out never to have been a routine at all; it had simply been one dependable person remembering to do everything. That is when a restaurant discovers the difference between having a strong employee and having a strong operating system.

Good people should make a restaurant better, but they should not have to hold it together. When the business depends on one person remembering, correcting, rescuing, and compensating for everybody else, that person becomes trapped by their own competence and the restaurant becomes vulnerable every time they leave the building. I call that person Tony, although I have known dozens of Tonys with different names in kitchens around the world. Tony is not the problem. The challenge is to take what Tony knows, turn it into something the organization knows, and build a restaurant that still performs when Tony finally gets a well-deserved day off.