I used to work for a chef named Adolph. You read that name right. Like many chefs, and unfortunately, befitting his name, Adolph had an outrageous ego. 

Picture this. The kitchen was open to the public until one day it wasn’t. An impatient customer asked repeatedly about her order, always saying “all I want is a hot dog.” Adolph finally took her at her word and threw a frozen hot dog at the lady. 

A week later, Adolph was shockingly still employed there. But the open kitchen was now a closed kitchen.

These stories are too common in restaurants. What interests me is how the operating system of restaurant kitchens is better built for high performance under pressure than many of the people working in them.

This raises a question I think about often: how should teams treat the problem of hierarchy? And how do great teams maintain order but stay flexible under stress? 

I studied how culinary teams operate, and discovered an imaginative approach to hierarchy: by letting the act of leadership move to whomever can best use it in the moment.

Kitchens and Battlefields

Do elite kitchens looks combat-like to you? You’re not hallucinating. 

Their operating model dates back to Franco-Prussian war veteran Georges Auguste Escoffier, veteran chef of Europe’s top kitchens. His wartime experience feeding French officers taught him an operating model he later refined at London’s Savoy Hotel, where it reached its classic form: the brigade de cuisine, a rigid set of specialized roles around singular functions. The saucier, poissonnier, rôtisseur, and others, each with its own subordinates, report ultimately to an executive chef, king of far-flung culinary domains. The culinary brigade was the battlefield brought to the kitchen.

150 years later, kitchen brigades still work, flying hot dogs aside. What fascinates me is how many later ways of working landed on similar answers to common problems: Who does what? How does work move? And how do we adapt when plans fail?

First, who does what? You can find later ways of working solving this the same way Escoffier did: naming roles, defining spaces, and subordinating the whole team to a single controlling outcome. From Ford’s assembly line to Scrum software teams, this pattern keeps recurring. Maybe it’s taken for granted in the 21st century but it was still bold and new in the 19th.

Second, how does the way of working perform at the edge? Start with the Andon cord from Lean Manufacturing, where one worker stops the line before defects pile up. Or look at how Scrum explicitly builds in inspection and re-planning to manage breakdown under pressure. The brigade’s rigid hierarchy seems different, but recent research finds an emerging strength in great brigades: during the rush, leadership swaps from top-down authority to collaborative, plural leadership, shifting the initiative to the scene of the most relevant knowledge.

Hard to imagine? Let’s spy on one team in action from the research.

A Chef Scrubbing Pans

At 8:15 p.m. in David’s kitchen, the rush is on. A frenzied dishwasher almost crashes with a cook hurrying a pan to the sink. Another cook throws his pan rather than risk collision.

The head chef sees it all. With no time for orders or reorganizing, he walks to the sink and scrubs pans until the dishes are caught up. This is humble and helpful, but it opens a risky workflow gap.

The metronome of David’s whole kitchen is his grill station, where open space and cook times limit everything else. The grill’s drumbeat choreographs the plating, prepping, and garnishing. So with the boss bailing out dish world, his station might have been the bottleneck. But then, without being told when or how, the team stepped in to run seamlessly without the boss. 

Does this seem far away from Adolph throwing hot dogs? Believe it or not, both Adolph’s and David’s kitchens have a clear through-line: The setup succeeds despite the boss’s flaws while still allowing his strengths to shine. You should have tasted Adolph’s chicken cordon bleu. 

When the Boss Isn’t the Answer

Most of us have to make the best of a mediocre leader. 

This is why the brigade’s flexibility matters: it emulates distributed leadership without losing the order and predictability of a hierarchy. It optimizes for a leader’s strengths, protects the team from the leader’s weaknesses, and makes space for brilliance in the ranks. 

Don’t try this at home. Your way of working still fits you better than imitating the brigade, but look what you owe to this model: defined roles, orderly flow, and flexibility under fire. Better still, the brigade offers a powerful answer to the problem of what to do when the leader doesn’t have great answers to the big questions. A great team finds the right answers anyway. 

To take away the best of the brigade, try this:

– Define the normal: Establish authority and clear roles in advance.

– Make expertise portable: Trust individual experts to excel outside their normal stations.

– Anticipate the breakdown: Expect your way of working to transform under pressure, and plan accordingly.

Legendary teams don’t need perfect leaders; they can succeed when their leaders can’t.

Think this could work for your event?

Tell me a little about your event, or grab a few minutes to talk it through.

Chris typically responds within one business day.


Leave a Reply

Your email address will not be published. Required fields are marked *