All Day
metaphor folk
Source: Food and Cooking → Organizational Behavior
Categories: systems-thinkingsoftware-engineering
Transfers
In professional kitchen communication, “all day” is the running total of a particular item across all active orders. When the expeditor calls “six salmon all day,” they are telling the fish station that six portions of salmon are needed across all current tickets — not six on one order, but six total. The call strips away per-ticket detail to surface the aggregate demand on a station.
Key structural parallels:
-
Aggregate versus per-ticket thinking — the core structural move of “all day” is abstraction upward. A cook receiving individual tickets sees a sequence of isolated orders: two salmon here, one there, three on that six-top. The “all day” call forces a shift to system-level thinking: how many total salmon must I produce in the next fifteen minutes? This maps directly onto the difference between task-level and capacity-level planning. A developer working through a sprint backlog ticket by ticket may not realize that seven of the twelve tickets require database migrations until someone calls the “all day” count for that resource.
-
Real-time demand visibility — the call is shouted across the kitchen and updated continuously as new tickets arrive and dishes leave the pass. The information is ambient, shared, and current. This contrasts with systems where demand data is trapped in individual queues, dashboards that nobody watches, or status reports compiled after the fact. The “all day” model says: make total demand visible, audible, and updated in real time, not aggregated after the service is over.
-
Enabling batching and sequencing — knowing the all-day count allows the cook to make production decisions that per-ticket thinking cannot support. If six salmon are needed in the next ten minutes, it may be more efficient to fire all six together than to cook them in three batches of two as each ticket arrives. The aggregate view reveals batching opportunities that the sequential view hides. In software operations, this maps to batching deployments, combining database migrations, or scheduling related infrastructure changes together rather than executing them as isolated tasks.
-
Abstracting away identity — the “all day” count deliberately discards information about which ticket each item belongs to. This is a feature, not a bug: the fish cook does not need to know that two salmon are for table 12 and four are for table 7. They need to know the total. The abstraction maps onto any system where individual request identity is less important than aggregate resource demand — load balancers, capacity planners, and scheduling algorithms all benefit from thinking in totals rather than individual transactions.
Limits
-
Homogeneity assumption — “all day” works because the items being counted are identical. Six salmon all day means six of the same preparation. In most organizational contexts, work items are not homogeneous. “Twelve tickets all day” is uninformative if the tickets vary wildly in complexity, required skills, and resource consumption. The metaphor imports a false equivalence between units that the kitchen enforces (through standardized recipes) but that other domains do not.
-
Small-team, co-located constraint — the call works because a professional kitchen is a small team in a shared physical space with real-time verbal communication. The expeditor can shout and every station hears immediately. This mechanism does not survive distribution: remote teams, asynchronous communication, or organizations with hundreds of contributors. The “all day” model is a broadcast protocol for small groups, not a scalable information architecture.
-
Snapshot fragility — the all-day count is accurate at the moment it is called and begins degrading immediately as new tickets arrive and completed dishes leave. In the kitchen, this works because the cycle time is minutes and the next call is seconds away. In domains with longer cycle times (sprints, quarters, fiscal years), the all-day equivalent becomes stale before it can be acted upon, and the effort of continuously updating it may exceed its informational value.
-
Aggregation hides priority — by collapsing individual orders into a total, “all day” erases the temporal and priority information attached to each order. The cook knows six salmon are needed but not which ones are urgent (the ticket that has been waiting) and which have just arrived. In contexts where priority differentiation matters more than total count — triage, incident response, customer escalations — the aggregation actively degrades decision quality.
Expressions
- “How many all day?” — requesting the total count of a resource or work item across all active work streams
- “Six deploys all day” — applying kitchen terminology to release management, counting total deployments planned across teams
- “What’s our all-day count on bugs?” — aggregating defect load across a team or sprint
- “I need an all-day number before I can plan” — requesting aggregate demand data before making resource allocation decisions
- “Heard, six all day” — the acknowledgment protocol, confirming receipt of the aggregate count
Origin Story
“All day” is standard kitchen brigade terminology, transmitted through professional culinary training and the apprenticeship tradition. It appears in culinary school curricula (Culinary Institute of America, Le Cordon Bleu) and in popular accounts of professional kitchen life, most notably Anthony Bourdain’s Kitchen Confidential (2000), which introduced a wide audience to the communication protocols of the professional line.
The term’s migration into technology and operations language is informal and recent, driven by the broader adoption of kitchen metaphors into agile and lean discourse. Dan Charnas’s Work Clean (2016) explicitly treats kitchen communication protocols as models for knowledge work coordination. The “all day” concept also appears implicitly in capacity planning literature: the practice of summing demand across work streams before allocating resources is the same cognitive operation the expeditor performs when calling the all-day count.
References
- Bourdain, A. Kitchen Confidential: Adventures in the Culinary Underbelly (2000) — popularized kitchen communication protocols
- Charnas, D. Work Clean: The Life-Changing Power of Mise-en-Place (2016) — explicit bridge between kitchen systems and knowledge work
- Culinary Institute of America, The Professional Chef, current edition — standard reference for kitchen terminology
- Ruhlman, M. The Soul of a Chef (2001) — kitchen culture and communication under pressure
Related Entries
Structural Neighbors
Entries from different domains that share structural shape. Computed from embodied patterns and relation types, not text similarity.
- Honeybee Is Ideal Scientist (animal-behavior/archetype)
- Data Stream (fluid-dynamics/metaphor)
- Process Thread (manufacturing/metaphor)
- The Chain of Responsibility Pattern (military-command/archetype)
- The Rule of Six (film-editing/mental-model)
- Value Stream (fluid-dynamics/metaphor)
- Flagship (seafaring/metaphor)
- Ideas Are Resources (economics/metaphor)
Structural Tags
Patterns: part-wholescaleflow
Relations: accumulatecoordinateselect
Structure: pipeline Level: specific
Contributors: agent:metaphorex-miner