Staff Meal: Reclaiming the 20 Minutes That Matter

Kitchen Culture

The staff meal is the most honest twenty minutes in any kitchen, and most of us have been squandering it for years.

I have eaten staff meals in Michelin-starred kitchens and in greasy transport caffs, in cramped basement prep rooms where you balance a bowl on your knees, and on loading bays with the bins for company. Some were extraordinary. Most were an afterthought. And that gap, between what a staff meal could be and what it usually is, tells you almost everything about the culture of a kitchen.

If you are not a professional cook, here is a brief explanation: The staff meal (sometimes called the “family meal” in American kitchens, though we will not be using that term here) is the communal meal eaten by the kitchen and front-of-house teams before service begins. It is, in theory, a moment of nourishment, cohesion, and calm before the chaos. In practice, it is often a bucket of overcooked pasta somebody knocked up in nine minutes while also doing three other things.

I want to argue that this is a terrible waste and that reclaiming those twenty minutes matters more than any new piece of kit or fashionable technique you might be chasing.

Why the Staff Meal Became an Afterthought

The decline of the staff meal is a story about priorities going wrong. When kitchens are understaffed and over-pressured, the meal that feeds your own team becomes the lowest item on the list. It gets handed to the most junior cook as a kind of punishment-by-responsibility. Nobody checks what they are making. Nobody tastes it. The result arrives on the table somewhere between grey and beige, and everybody eats it in silence while looking at their phones.

I once worked in a kitchen where the staff meal was, unfailingly, boiled rice and a curry made from whatever trim had been lurking in the walk-in longest. It was not terrible, precisely. But it was joyless. And joyless food eaten before a long service does not fuel anybody particularly well, physically or otherwise.

The problem is that the staff meal is treated as a chore rather than an opportunity. It is seen as a cost, a burden, a distraction. But this thinking is completely backwards.

What a Proper Staff Meal Actually Does

Feed your team well, and they work better. That is not sentiment; that is basic human physiology. A cook who has eaten a decent, balanced meal an hour before service has better concentration, better stamina, and frankly a better temperament than one running on a mouthful of bread and anxiety. The same applies to front-of-house staff, who are often forgotten entirely in this equation.

But the staff meal does something beyond mere calories. It sets the tone. When a chef patron bothers to cook properly for their own team, even quickly, even simply, it communicates something important: that you are valued and that standards apply here always, not just when the paying guests can see them. That message lands. People notice.

It also builds the kind of low-stakes confidence that formal training cannot. A young commis chef given responsibility for the staff meal, with proper guidance rather than abandonment, learns to plan, to season, and to manage a hot kitchen under a small but real deadline. It is the best teaching tool most kitchens never consciously use.

The Twenty Minutes: What They Should Look Like

Twenty minutes is not long. But twenty minutes of actually sitting down, eating together, and briefly not looking at a ticket machine is longer than it sounds when you are used to eating standing over a bin. Here is what that time can and should involve.

Everybody stops, sits if possible, and eats together. Phones face down on the table is a reasonable ask.
The food is tasted and commented on, briefly and constructively. Not a critique, just acknowledgement. This alone builds palate and awareness.
The head chef or senior cook acknowledges the effort made by whoever cooked it. One sentence will do.
Any pre-service notes are shared here, not shouted across a hot pass three minutes before the first cover arrives.
The meal ends with enough time for everyone to get back to their stations, composed and ready.

None of that is complicated. None of it costs money. Most kitchens simply do not do it.

What to Actually Cook

The best staff meals I have eaten were not elaborate. They were honest. A proper braise made from secondary cuts that had been slowly cooked since mid-morning. A big pot of dhal, properly seasoned, with good bread alongside. Fried rice with leftover vegetables and a decent amount of soy and sesame, done with actual heat and some care. The point is not complexity; it is intention.

There are a few principles worth following, whether you are running a professional kitchen or thinking about how this translates to cooking for a household of people before a busy evening.

Seasonality First

The staff meal should reflect the season, partly because seasonal produce is cheaper and better, and partly because it keeps the team connected to what is actually growing outside. In autumn, that means roots and squash and bitter leaves. In summer, it might be a quick tomato sauce with yesterday’s bread and whatever fresh herbs need using. Do not reach for the same ingredients every week out of habit. Habit is the enemy of a good cook’s palate.

Use Trim Intelligently

Every kitchen generates usable trim that, if handled properly, becomes something genuinely good. Leek tops make a fine broth. Parmesan rinds add extraordinary depth to any slow-cooked pulse. Carrot peelings, roasted, can go into a stock that embarrasses bought alternatives. Using trim well in the staff meal teaches economy and creativity simultaneously, which are two of the most valuable skills a cook can develop.

Season Properly and Taste Twice

I have eaten staff meals that were, at their core, quite good dishes ruined entirely by under-seasoning. If you are cooking for fifteen people and you are nervous about the salt, taste it, adjust it, and taste it again. Not everything needs to be heavily salted, but everything needs to be properly seasoned, and those are different things. This applies at home as much as it applies behind a pass.

The Home Kitchen Parallel

You may not run a restaurant. But the principle of the staff meal translates directly into domestic life, particularly for anyone who feeds a household of people and sometimes treats their own dinner as an obstacle rather than a pleasure. The habit of sitting down together before an evening, however briefly, and eating something made with actual care rather than resigned convenience, changes the atmosphere of a home in ways that are difficult to quantify but very easy to feel.

I am not suggesting you recreate a Michelin kitchen service at home (please do not; it sounds exhausting). But setting aside twenty minutes to actually cook something properly for the people you live with, and then to eat it without half your attention elsewhere, is one of the more underrated things you can do for yourself and for them.

Reclaiming It

If you are a chef reading this, I would ask you one honest question: when did you last cook the staff meal yourself? Not delegate it, not oversee it from a distance, but actually stand at the stove and make something for your team with the same attention you bring to the menu? If the answer is uncomfortable, that is useful information.

The staff meal is not a burden. It is a practice. It teaches economy, seasonality, speed, and care. It builds teams and resets atmospheres. It keeps even very senior cooks connected to the fundamentals of their craft, which is the only place good cooking ever actually comes from.

Twenty minutes, properly used, is not nothing. It might be the only twenty minutes in the day that genuinely belong to everyone in the kitchen at once. That is worth treating with a bit of respect.