How to reduce your restaurant’s dependence on key managers

What key-person dependence looks like

It rarely looks like a problem day to day. It looks like a GM who knows which vendor to call when the walk-in fails, a chef who knows the real prep quantities for Fridays, or an owner who is the only one who can answer how the patio close actually works.

The operation runs well — as long as those people are there and have time. When they leave, the team discovers how much of the company lived in one person’s head.

Why it gets worse as you grow

At one or two locations, the owner can be the system. Each new restaurant adds people asking the same few leaders the same questions. Those leaders become bottlenecks, and the questions they answer never become part of anything the company owns.

Start with the questions people keep asking

The fastest way to find undocumented knowledge is to track repeat questions. If managers or cooks keep texting the same person about the same thing, that answer belongs in the operation, not in a message thread. Write down what gets asked most often for a few weeks; that list is your capture plan.

Capture it from the people, in the restaurant

Key-person knowledge usually isn’t written anywhere, so it can’t be collected by asking for documents. It has to be captured through conversations and by watching the work. Short sessions with the people who hold it — focused on specific procedures, exceptions and judgment calls — capture far more than asking them to write it up.

Separate the standard from the person

Once captured, the knowledge needs an owner who isn’t the person who held it. Leadership should approve it as the company standard, so it survives that person’s schedule, promotion or departure.

Put it where the team already looks

Captured knowledge only reduces dependence if people use it instead of calling. It has to be easier to find the answer than to text the manager. That means organizing it by role and location, and making it quick to reach mid-shift.

Keep it current after you capture it

Captured knowledge goes stale like any other material. If nobody keeps it current, people learn it can’t be trusted and go back to asking the same key people. The dependence returns quietly.

Read how to standardize operations across locations, or see how Trensli captures and maintains operating knowledge.