Triage in the first ten minutes

When everything lands at once, you do not need to be faster — you need a fixed order and a smaller pile.

The idea

Two cooks call out, the ice is gone, twelve people walk in on top of four reservations, and three departments want you. The instinct is to move faster. Speed is the weakest lever you own.

The first ten minutes are not for solving. They are for ordering and shrinking. Order means one fixed pass every time: safety, then anything with a clock you cannot move, then the thing that gets worse if left, then everything else. Shrinking means stopping the inflow — close a section, pause seating, pull an item — so the pile stops growing while you work.

Two sentences have to be said inside those ten minutes: one to your team naming who owns what, and one to a guest setting an expectation you can actually keep. And whatever you deliberately put down, you have to pick back up.

The floor board

Ten minutes, in thirty-second steps. Items land on a timer. Give each one an action, watch the three queues, and see what your choices cost. Press play, or step through one half-minute at a time.

minute 0:00 / 10:00 ready — press play or step

Filled dot above the line: a decision. Open dot with a slash: something held and never picked back up. Square below the line: one of the two sentences.

The board is quiet for about thirty more seconds. Press play — the first item lands at minute 0:30.

How it works

Name the rung, not the noise. Sort every incoming item into one of four rungs — safety, a clock you cannot move, gets worse if left, everything else — and always take the highest open rung first. Loudness is not a rung.
Shrink before you solve. Ask what stops more work arriving: pause seating, close a section, pull an item, cut the offering. This is almost always stronger than any speed you can add.
Say the two sentences. One to the team: "Marco has the pass, Dani has the door, I have the floor — come to me only for guests." One to a guest: "It's a thirty-minute wait for a table; the bar is open now." Both inside the ten minutes.
Defer out loud, with a time. "Not now" is a decision only when it has a clock on it and a place it is written down.
Run the recovery pass. When the queues stop growing, go back to the held pile item by item. A triage answer that never returns to what it put down is half an answer.

The arithmetic is why speed loses. A short line with a full book:

kitchen output   4 cooks on the line      = 16 tickets / 10 min
two call out     2 cooks on the line      =  8 tickets / 10 min
inflow           5 tables x 2.4 courses   = 12 tickets / 10 min

gap              8 - 12                   = -4 tickets / 10 min, compounding
                 after 30 minutes         = 12 tickets behind
                                          = roughly +25 min ticket times

lever A: work faster
  best case      +1 ticket / 10 min       -> gap -3   still losing, plus remakes

lever B: reduce the load  (close one section, pull two dishes)
  inflow         2.5 tables x 2.4         =  6 tickets / 10 min
  output         2 cooks, shorter menu    =  8 tickets / 10 min
  gap            8 - 6                    = +2 / 10 min   the backlog drains

Lever A moves the number by one and borrows from the next hour. Lever B flips the sign. That is the whole reason the first move is usually a subtraction.

When to use it

Situation	What it gives you, and the trade-off
Several problems land inside a couple of minutes	An order you can defend later. Trade-off: you will consciously let something get slightly worse.
Demand is outrunning capacity, not just badly organised	Reducing load is the only real fix. Trade-off: you turn revenue and goodwill away on purpose.
You are the single point everyone comes to	Naming owners buys back your attention. Trade-off: it costs thirty seconds up front, when you feel you have none.
A guest is waiting on information you do not have	An honest, keepable expectation. Trade-off: the honest number is worse than the one they hoped for.
One clear failure with a known fix, and slack elsewhere	Skip triage — just fix it. Triage is overhead when there is only one thing wrong.
Anything with a safety dimension	No triage decision at all. It goes first, every time, without a cost-benefit conversation.

Watch out for

Treating volume as a rung. The loudest item is usually a guest at the door or a manager on the phone; the highest item is usually a burner, a plate shortage, or a table with a curtain time. Sort by consequence, not by decibels.
Working faster as the plan. Speed borrows from the next hour and pays interest: remakes, a cut hand, a table you forget you promised. If your answer to "everything is happening" is "move quicker", you have not made a decision yet.
Delegating into fog. "Someone grab the door" is not delegation. Name the person, name the task, name when you want to hear back, and get it repeated to you. Unowned tasks come back to you at minute nine, larger.
Quoting a time to be liked. Three optimistic ten-minute quotes create three angry tables at minute twelve. One honest thirty-minute quote, with an option attached, creates a wait you can survive. Only promise what you'd still be right about if nothing improved.
Leaving the reduction in place. Pausing seating and closing sections are temporary trades, not resting states. When the pass catches up and you have not re-opened, you have converted a service problem into a revenue problem — and the waiting list into walkouts.
A held pile with no clock. Deferring is a real, skilled move — but "later" is not a time and your head is not a system. Say it out loud, put it on paper, and come back before you go home.

Worked example

"Tell me about a shift that went sideways." Here is the shape of a strong answer, told as ten minutes rather than as a story about being busy.

Friday, 7:10pm, 140 on the book. Two cooks call out; four minutes later a walk-in of twelve arrives with four reservations due at 7:25; the bar reports the ice machine is empty. First pass: nothing unsafe, so the clock item goes first — the twelve people standing at the door. I did not seat them. I paused seating for eight minutes, offered the bar, and quoted a thirty-minute wait, because the real constraint was two cooks, not twelve chairs. That is the subtraction: inflow from 12 tickets per ten minutes down to about 6, against an output of 8. The rail starts draining instead of growing.

Then the two sentences. To the team, at 7:14: "Marco owns the pass and gives me a ticket time every five minutes; Dani owns the door and the wait list; I'm on the floor. Ice: Sam takes the van next door, back by half past." To the room, at 7:16, table by table on the eight longest waits: "Your mains are about fifteen minutes out — that's a real number, and I'll come back either way." The ice I delegated; the GM's call I deferred out loud — "after service" — and wrote it on the board.

By 7:35 the rail was down from 21 to 12, so I re-opened the section and resumed seating on a twenty-minute quote. At 9:40 I ran the recovery pass: called the GM back, filed the ice repair, and comped the two tables that had waited longest. Two covers lost on the night. No walkouts, no incident, and nobody on the line was asked to go faster.

Notice what makes it interviewable: a stated order, a subtraction with numbers behind it, two named communications with timestamps, an explicit deferral, and a return to the pile.

Check yourself

Minute two. Two cooks are down, the ice machine is empty, and the fire panel in the back hall is beeping with an unattended pan on the flat top. What do you take first?

The kitchen is twenty minutes behind and the door keeps opening. Which move is stronger in the next sixty seconds?