The food service industry has a problem it keeps refusing to name. Operators with food stand/truck and commissary experience are opening brick and mortar restaurants, hiring experienced restaurant cooks, and then watching everything fall apart - and blaming the cooks. The cooks, meanwhile, are questioning competence they've spent years earning. Nobody in this equation is connecting the right dots. This isn't a staffing problem or a training problem. It's a comprehension problem. And it starts with a fundamental misunderstanding of what a cook actually is.
It's been made worse by a growing industry of consultants who can sell restaurant success without understanding how kitchens actually work. Their credentials are real. Their portfolios are polished. Their operational knowledge is borrowed at best. Not too long ago, brick and mortar operators facing rising overhead costs started conflating skillsets - convinced that a five-year veteran of a high-volume sushi kitchen and the sous chef of a Mediterranean restaurant were interchangeable because both, technically, were cooks. It was the same category error we're seeing now, just a generation earlier. The details change. The assumption doesn't.
Each environment produces a distinct internal system. Commissary cooks are methodologists - they think in scale and sequence, mapping out which equipment gets used first, staggering production so nothing bottlenecks. Food stand cooks are built for volume and velocity; presentation is irrelevant when everything's going in a bag, so they crank the heat and hammer product out. Restaurant line cooks are something else entirely - they're running parallel processes, juggling multiple tickets simultaneously, timing five different components to land on the pass hot and together. A kitchen manager once put it plainly: commissary cooks are the intellectuals, food stand cooks are the ADHD kids, and line cooks are symphony conductors.
Skill doesn't transfer the way operators assume it does. Every environment builds its own muscle memory - not just technique, but movement, rhythm, instinct. A prep cook operates on the same logic as a commissary cook, just smaller scale; methodical, sequential, one thing at a time. Drop them on a line and they don't just struggle with the pace - they have to dismantle everything their body already knows and rebuild it under fire. The reverse is equally brutal. A line cook put on prep tries to run multiple things simultaneously because that's what their nervous system is trained to do. They reach for things that aren't where they expect them. They move in patterns that don't apply. What looks like incompetence from the outside is actually a skilled cook being asked to factory-reset muscle memory they spent years building. They're not failing. They're being failed.
Most operators who make this mistake aren't reckless - they're extrapolating from genuine experience. They built a food stand. They rented commercial kitchen space to do their prep, batch cooking one day and selling the next. It worked. What they don't account for is that their experience was always sequential - prep one day, service the next, in a kitchen that existed solely for production. A restaurant collapses that sequence into a single simultaneous operation, in a kitchen that has to serve both purposes at once, and that changes everything. When it starts falling apart, they default to the only frame of reference they have: "I did this for a year, why can't someone with actual restaurant experience handle it?" The question feels reasonable to them. It isn't. They're not asking a restaurant cook to work hard - they're asking them to perform a different job entirely, in a different environment, with a different internal clock, while calling it the same thing. The operator isn't malicious. They're just drawing conclusions from incomplete data, and the cooks are paying the price.
For the cook, the experience is jarring in a way that's hard to articulate. These aren't mediocre cooks who got exposed - they're often the best in the room. They know their craft, they understand systems, they can feel when a kitchen is running right. But when the environment is structurally broken - when prep for a farmers market takes priority while the dining room is open, when the line is set for service but keeps getting pulled away, when tickets start backing up through no fault of their own - something insidious happens. They start questioning themselves. A cook who has built careers, trained teams, and turned kitchens around suddenly wonders if they're losing it. And that self-doubt doesn't just sting - it breaks the very internal system that made them good in the first place. The operator is confused about why their experienced hire is struggling. The cook is confused about why they're struggling. Nobody has the language for what's actually happening. And in an industry that's already mentally and emotionally brutal, that confusion doesn't stay quiet for long.
The consequences compound quietly until they don't. Every time a cook leaves - bitter, burned out, or drowning in self-doubt they can't explain - they take something with them that never shows up on an exit interview. They take the knowledge of that specific kitchen. How the line breathes during a rush. The unspoken rhythm between stations. The thousand small adjustments that turn a chaotic service into a smooth one. No two kitchens are the same, no matter how hard operators try to standardize them, and that institutional knowledge is built slowly and lost instantly. When the next round of cooks comes in and makes the same mistakes, operators rarely connect the dots. Instead they double down - "an experienced cook should be able to handle this from day one" - not realizing they're asking the same wrong question they asked last time. The cooks who left get blamed. The cooks who stayed get ground down. And the operator wonders why nothing sticks. It's not a staffing problem. It's a comprehension problem. And until operators understand the difference between the kitchen they think they're running and the one that actually exists, the cycle doesn't break.