Kitchen bottlenecks: finding the station that stalls

Every kitchen has a station that holds the rest back on a busy night. Ask the team which one, and most will give an answer at once: the grill is always behind, or the pastry section is too slow, or the fryer cannot keep up. Often they are wrong. The station everyone blames is the one where waiting is most visible, not always the one that causes it.

Kitchen bottlenecks are the points where work piles up faster than it can be done, so every ticket that passes through them waits. Finding the real one matters, because time and money spent speeding up any other station changes nothing: the tickets still wait at the bottleneck.

This guide covers what a kitchen bottleneck is, why the obvious answer is often wrong, how to read ticket times by station to find the real constraint, and what to do once you have found it. Every venue and figure in it is an example.

A kitchen bottleneck is the station, the piece of equipment or the step that limits how fast the whole kitchen can turn out plates. If the grill can cook forty steaks an hour and the restaurant sells sixty at its busiest hour, the grill is the bottleneck: tickets pile up there, and every table with a steak waits.

The idea comes from the theory of constraints, which says that any system's output is limited by its single tightest constraint. Improving anything else does not raise the output; improving the constraint does, until another step becomes the new constraint.

In a kitchen, that means the first job is not to speed everything up. It is to find the one place where work waits longest, and start there.

Kitchens blame the station where waiting is most visible. A grill with ten tickets on its rail looks like the bottleneck, but the tickets may be waiting there because the sides from the fryer are not ready, or because the pass cannot plate fast enough and the grill is holding finished steaks.

Kitchens also blame the station with the loudest cook, the newest cook or the one that had a bad night last week. Memory is selective: one terrible evening at the pastry section is remembered for months, while a grill that is slightly behind every night goes unnoticed.

Evidence beats memory. Ticket times by station, measured over several busy services, show where work actually waits, and they often point somewhere the kitchen did not expect.

Ticket times measure how long each ticket takes from arriving in the kitchen to being completed. Measured for each station, they show which station takes longest on its part of each order, and how that changes through the evening.

A station whose ticket times rise sharply at the busiest hour, while others stay steady, is a strong candidate for the bottleneck. A station whose times are long all evening may simply have long cook times, which is a different problem.

Look at the middle of the range and the slow end, not only the average. A station whose median ticket is fine but whose slowest tickets take three times as long has a problem with surges, not with everyday speed. Our guide to ticket times: the only kitchen metric that moves covers how to measure them.

A ticket's time in the kitchen has three parts: the time it waits before anyone starts it, the time it takes to cook, and the time it waits at the pass for plating and collection. Splitting ticket times into those parts shows what kind of bottleneck you have.

Long queue times mean the station has more work than it can start: a capacity bottleneck. Long cook times mean the dishes themselves take long: a menu or method question. Long pass times mean the plates are ready but not leaving: a bottleneck at the pass, not at the station.

A grill with short queue and cook times but long pass times is not the bottleneck at all. Its steaks are ready and waiting for something else.

Another useful view compares how many tickets are waiting with how long tickets take. When a station is coping, more tickets mean only slightly longer times. When it reaches its limit, each extra ticket adds much more time, because the queue grows faster than the station can clear it.

The point where ticket times start to climb steeply is the station's practical capacity. Knowing it tells you how many tickets each station can handle at once before tables start to wait, which is the real kitchen capacity at that station.

That number is more useful than any rule of thumb, because it comes from your kitchen, your menu and your team.

Many kitchen bottlenecks come from how work is divided between prep stations. A station that cooks the restaurant's three best-selling mains will always be busier than one that cooks two rarely ordered starters. Dividing the kitchen by tradition, or by who likes which section, can leave one station overloaded and another idle.

Look at how many tickets each station receives at the busiest hour, and how much of the kitchen's work each one does. A station doing half the work with one cook is a bottleneck waiting to happen.

Sometimes the fix is to move a dish from one station to another, or to move a cook. Our guide to kitchen screen layout for four stations covers how dividing the work shows up on the screens.

Some bottlenecks are not about the station but about one dish. A dish that takes twenty-five minutes to cook ties up its station and delays every ticket it sits on, because the table's other plates wait for it.

Look at which dishes take the most kitchen time, and how often they are ordered at the busiest hour. A slow dish that sells well at peak is a bottleneck in itself. Options include preparing more of it in advance, changing the method, moving it to a quieter station or limiting how many are sold at peak.

Our guide to cook times: the myth of the average main covers how one dish drags every ticket it sits on.

Sometimes the constraint is a piece of equipment rather than a station. A kitchen with one fryer, one salamander or a small oven may be limited by how much that equipment can hold at once, whatever the cook does.

Equipment bottlenecks show up as long cook times at the station that uses the equipment, rising sharply at peak. The fix may be a second piece of equipment, a change to the menu so fewer dishes depend on it, or a change to the method so the equipment is used more efficiently.

Before buying new equipment, check the evidence. A second fryer will not help if the real bottleneck is the pass.

Some bottlenecks are created before service starts. A station that begins the evening with its mise en place unfinished spends the first hour cooking and prepping at once, and falls behind before the rush arrives. A sauce that runs out at eight o'clock and has to be made again stops a station for ten minutes at the worst time.

Look at whether the slow station started service ready. If it often did not, the fix is in the afternoon, not in service: a better prep list, more prep time or prep moved to a quieter station. Our guide to the prep list that ends the morning guesswork covers how to plan it.

A station can become the bottleneck simply because it is short of hands at the wrong time. A cook on a break at half past seven, a late start or a station staffed by a new cook on a busy night can all create a constraint that has nothing to do with the station's equipment or its dishes.

Compare ticket times with the rota. If a station's times rise when a particular cook is off or on a break, the fix may be a change to the breaks, a second cook at peak or training that lets another cook step in. Cross-training, so cooks can help a neighbouring station for half an hour, is one of the cheapest ways to ease a bottleneck that moves through the evening.

The pass is a bottleneck more often than kitchens admit. One person plating, checking and calling every dish for a full room can become the constraint on a busy night, even when every station is keeping up.

The signs are long pass times, plates waiting under the lights and stations holding finished food because the pass is not ready for it. Servers waiting at the pass for plates is another sign.

Fixes include a second person at the pass at peak, runners who collect plates as soon as they are ready, simpler plating for the busiest dishes and a clearer view of which plates belong to which table.

Bottlenecks move. Fix the grill, and the fryer may become the new constraint; fix the fryer, and the pass may take its place. That is normal and expected: improving the tightest constraint raises the kitchen's output until the next one appears.

Bottlenecks also move through the evening. The cold section may be the constraint early, when starters dominate, and the grill later, when mains are fired. Look at ticket times by station and by hour to see the pattern.

Keep measuring after each change. A fix that moves the bottleneck has worked; it has simply revealed the next step to improve.

The kitchen's layout can create bottlenecks of its own. Cooks crossing each other's paths, a walk-in fridge at the far end of the kitchen, a single sink shared by three stations or a pass too small for a full table's plates all slow the work, however good the team.

Watch a busy service with layout in mind. Where do cooks wait for each other? Where do they walk furthest? Where do plates pile up? Small changes, such as moving a fridge drawer to the station that uses it most, adding a shelf at the pass or changing which station plates a dish, can remove minutes from every ticket without any new equipment.

Layout bottlenecks are hard to see in ticket times alone, because they slow every station a little rather than one station a lot. If ticket times are long everywhere but no single station stands out, look at how people and plates move through the room.

A kitchen's bottleneck at lunch is often different from its bottleneck at dinner. Lunch may be dominated by quick dishes from one station and a rush in a short window; dinner by longer cooks, more courses and a slower, longer peak.

Look at each service separately. A fix that eases the dinner bottleneck may do nothing for lunch, and the reverse. Some kitchens change how work is divided between stations for each service, so the station carrying the lunch rush is not the same one carrying the dinner rush.

Some kitchen bottlenecks start on the floor. If four tables are seated together, they order together, and their tickets arrive together. A station that copes well with steady work can be overwhelmed by a wave.

Spreading arrivals and orders across the evening reduces the waves. Staggered booking times, a host who seats with the kitchen in mind and servers who do not take four orders at once all help. Our guide to pacing covers so the kitchen never drowns covers how.

Firing courses at the right moment matters too. Mains fired for every table at the same time create a wave of their own.

Once you know the bottleneck, ease it in the cheapest way first. Make sure it never stands idle: the bottleneck station should always have its next ticket ready and its mise en place done. Remove work it does not need to do, such as plating that could happen at the pass or prep that could happen earlier in the day.

Then look at the work itself. Can a slow dish be partly prepared in advance? Can the busiest dishes be spread across two stations? Can a second cook join at peak?

Only then consider bigger changes: new equipment, a different menu or a different kitchen layout. Each costs more, and each should be justified by the evidence.

Every change to ease a bottleneck should be measured. Before making it, note the station's ticket times at the busiest hour over a few comparable nights. After making it, measure the same nights and the same hours again.

Compare like with like: busy nights with busy nights, the same days of the week and similar numbers of covers. A change that seems to work on a quiet evening may make no difference on a full one. If the times fall, keep the change and look for the next constraint. If they do not, undo it or try something else, rather than leaving a change in place because it felt right.

Keep a short note of each change and its result. Over a few months, that note becomes a record of how the kitchen has improved, and a guide for whoever runs it next.

Evidence works best when the team sees it. Show the cooks the ticket times by station, explain what they mean and ask what they think is causing the waits. The people on the line often know exactly why a station falls behind, once they see that the question is about the work and not about them.

Share the results of each change too. A grill cook who sees their station's waits fall after a change to the fryer understands why the kitchen works as a system, and is more likely to suggest the next improvement.

The bottleneck sets the kitchen's real capacity: the number of covers it can serve well in an hour. If the grill can cook forty mains an hour and the menu sends most mains to the grill, the kitchen's capacity is about forty covers an hour, however many seats the room has.

That number should shape bookings and the menu. A kitchen whose capacity at peak is lower than the room's demand needs either fewer covers at peak, more capacity at the bottleneck, or a menu that spreads the work more evenly.

Knowing the number makes those decisions easier, because they rest on evidence rather than on hope.

An invented bistro believes its grill is the bottleneck: on busy nights, the grill always has the most tickets and the grill cook is always under pressure. The owner considers a second grill.

Before buying, the bistro looks at its ticket times by station over a month of busy nights, split into queue, cook and pass time. The grill's queue and cook times are steady; its pass times are long. The fryer's queue times climb steeply after eight o'clock. The grill is holding finished steaks while it waits for the fries.

The real bottleneck is the fryer, which also serves most of the starters. The bistro moves two fried starters to an oven, adds a second fryer basket routine at peak and puts a runner at the pass. Ticket times at the busiest hour fall by a third, and no second grill is needed.

In servearound, each dish belongs to the station that cooks it, and each station's board shows only its own work, with the stations page showing how many tickets each station has live. Every ticket shows its age as it counts, so a station falling behind is visible during service.

Kitchen analytics then show the evidence for any range of dates: tickets, share of the work, median queue time, median prep time, the slow end of total time and remakes for each station; where the minutes go between the queue, prep and the pass; ticket time by day and hour; queue depth against ticket time; which dishes cost the kitchen the most time; and the slowest tickets with their lines. See Analytics and Order Fulfillment.

The station, equipment or step that limits how fast the whole kitchen can turn out plates, where work piles up and waits.

Read ticket times by station over several busy services, split into queue, cook and pass time, and see where work waits longest.

The station where waiting is most visible may be waiting for another station, or for the pass.

The station has more work than it can start: a capacity problem at that station.

Yes. Long pass times and plates waiting under the lights are the signs.

Only after the evidence shows the equipment is the constraint, and cheaper fixes have been tried.

Fixing the tightest constraint raises output until the next one appears. That is a sign the fix worked.

It sets the number of covers the kitchen can serve well in an hour, which should shape bookings and the menu.

Kitchen bottlenecks are the points where work piles up faster than it can be done, and they limit the whole kitchen. The station everyone blames is often not the real one, so use evidence: ticket times by station, split into queue, cook and pass time, measured over several busy services, and compared with how many tickets each station is carrying.

Look for the station where queues grow fastest at peak, check whether slow dishes, equipment or the pass are the real constraint, and ease it in the cheapest way first. Keep measuring, because the bottleneck will move, and let the kitchen's real capacity shape your bookings and your menu.