Fire

Transfers

In a professional kitchen, “fire” is the command from the expeditor (or chef de cuisine) that tells the line to begin cooking a specific dish or course. It is not “start working” — mise en place, prep, and staging have already happened. It is “execute now.” The word “fire” borrows from the literal act of applying heat, but in kitchen usage it has become a pure synchronization signal: a one-word protocol that coordinates timing across multiple stations.

Key structural parallels:

• Separation of preparation from execution — “fire” only works because everything upstream is already done. The proteins are portioned, the garnishes are prepped, the sauces are ready. The command does not initiate work from scratch; it releases pre-staged work. This maps onto deployment pipelines (code is built, tested, and staged before the deploy command), military operations (troops are positioned before the order to advance), and project management (a “go/no-go” decision that presupposes completed preparation). The metaphor teaches that the trigger event is the least interesting part of the process — what matters is the preparation it depends on.
• Single-voice coordination of parallel work — a dinner service involves multiple cooks working simultaneously on different components of the same plate. The expeditor’s “fire” synchronizes them: grill station starts the steak, saute station starts the vegetables, pastry starts plating dessert for the previous course. Without the single coordinating voice, each station would work at its own pace and plates would arrive at different times. This is a human implementation of a barrier synchronization primitive — parallel workers proceed independently until a coordinator signals the next phase.
• The command is irrevocable — once a steak is on the grill, you cannot un-fire it. The cook is committed. This maps onto irreversible deployments, published communications, and any system where execution cannot be cheaply rolled back. The kitchen’s culture of confirming the fire command (“heard, fire table twelve”) exists precisely because the action is irreversible and costly to undo.
• Tempo control through sequencing — the expeditor controls the pace of the entire service by choosing when to fire each table. Fire too early and plates stack up under heat lamps. Fire too late and guests wait. This is flow control: the expeditor is a human rate-limiter, matching production to consumption. The metaphor maps onto any system where timing of execution matters more than speed of execution — release management, editorial calendars, supply chain scheduling.

Limits

• “Fire” has lost its fire — the word has been so thoroughly domesticated in kitchen usage that it carries none of the urgency, danger, or destructive connotation of literal fire. It is calm, routine, and low-drama. Importing the metaphor into other domains can misleadingly suggest that the execution trigger is dramatic or high-stakes, when in a well-run kitchen it is the most ordinary moment in the service.
• The cook has less autonomy than the metaphor implies — “fire” sounds like empowerment: the cook is trusted to execute. But in a professional kitchen, the response to “fire” is a rehearsed sequence with narrow tolerances. The cook does not decide how to cook the steak; they execute a specification. The metaphor can mislead when applied to creative or knowledge work, where the executor is expected to exercise judgment, not follow a recipe.
• It assumes completed preparation — the metaphor’s power depends on mise en place being done. In domains where preparation is never truly complete (most software projects, most organizational initiatives), the “fire” command can create a false sense of readiness. Calling “fire” on an unprepared kitchen produces chaos; calling “fire” on an unprepared project produces the same, but the incompleteness is harder to see.
• Single-point-of-failure in the coordinator — the system works because one person (the expeditor) holds the global state and sequences all commands. If the expeditor is overwhelmed, sick, or incompetent, the entire service collapses. The metaphor naturalizes centralized control, which may not scale or may introduce fragility in systems that need distributed coordination.

Expressions

• “Fire table twelve” — the canonical kitchen command, ordering all stations to begin cooking the entrees for that table
• “Don’t fire until I call it” — holding back execution until the coordinator is ready, common in both kitchen and military contexts
• “Fire when ready” — deployment and release management borrowing the kitchen’s trigger-on-readiness protocol, confirming that all preconditions are met before execution begins
• “Heard” — the acknowledgment protocol confirming the fire command was received, borrowed into business contexts as a model of clear communication
• “All day” — the companion command that states the total count (“three salmon, all day”), providing context for the fire command

Origin Story

The hierarchical kitchen brigade system was formalized by Auguste Escoffier in the late 19th century, adapting military organizational principles to professional cooking. The expeditor role (aboyeur) and the call-and-response protocol (“fire” / “heard”) emerged from the need to coordinate many cooks working in parallel under extreme time pressure. The word “fire” likely entered kitchen usage through its literal meaning — apply heat — but quickly became a pure synchronization signal with no semantic connection to combustion.

The metaphor crossed into software and business discourse through the broader adoption of kitchen vocabulary (mise en place, in the weeds, behind) by productivity writers, most notably via Dan Charnas’ Work Clean (2016), which explicitly mapped kitchen protocols onto knowledge work practices.

References

• Charnas, D. Work Clean: The Life-Changing Power of Mise-en-Place (2016)
• Escoffier, A. Le Guide Culinaire (1903) — foundational text for the kitchen brigade system
• Bourdain, A. Kitchen Confidential (2000) — popularized kitchen culture and vocabulary for a general audience