The Best Ops Person I Ever Promoted Didn't Have a Black Belt
She'd spent four years waiting tables. And it showed — in the best possible way.
The leader pulled me aside after the plant walk.
"Phil, who stands out to you?"
I'd spent two days on the floor. Watched the morning startup. Sat in on shift handovers. Talked to the people nobody usually talks to. I gave him my answer: the woman running the scheduling board. No Six Sigma certification. No formal ops training. She'd never heard of Prosci ADKAR. But she moved through that floor in a way I recognized immediately — eyes up, talking to everyone, problems absorbed before they became fires.
He nodded slowly. "She doesn't have a black belt."
I said I knew that.
"She used to wait tables."
I told him that was actually the point.
He wasn't sure he believed me. He gave her the job anyway. Within a year, she was running the production floor. He never mentioned the black belt again.
Go sit at a restaurant bar sometime. Not to drink — to watch.
The kitchen behind that pass is producing somewhere between 20 and 50 completely different products, on completely different timelines, for completely different tables, with a team of people who weren't all trained together and who are probably not all having a good night. They're doing this in real time, under noise and heat, without the luxury of a rescheduled delivery date or a revised work order.
If that sounds familiar, it should. It's your plant floor.
The difference is that a restaurant doesn't pretend the complexity is manageable with a spreadsheet. It manages it with clear communication, defined hand-offs, relentless tempo awareness, and a team ethic where everyone understands that one person dropping the ball means the whole table walks unhappy. Every shift, they run what we would call a production meeting, a constraint review, and a team debrief. They just don't call it that. They call it a shift.
What four years of that does to someone's operational instincts, no classroom replicates.
I've told my wife more than once: if I had to do it over, I'd spend a year working in a restaurant while I was in school. You learn more about operations — about real operations, under real pressure — in a busy kitchen than in most MBA programs.
You're probably thinking: fine, but I can't put someone with no formal training into a role that has real technical requirements.
Fair. A restaurant background doesn't replace trade certification or engineering knowledge. I'm not suggesting you hand someone a role they're not technically qualified for.
But "technically qualified" and "operationally capable" are two different things, and industrial businesses routinely confuse them. They promote the person with the credentials who has no instinct for how a floor actually moves. They pass over the person with no credentials who could run the morning startup in their sleep.
The question isn't "does she have a black belt?" The question is: does she understand the goal, know the process, communicate when something's off, and hold the team together under pressure? If the answer to those four things is yes, the belt is a training course, not a prerequisite.
Here's what restaurant-trained operators understand that formal credentials often don't teach.
The goal is specific and visible. In a kitchen at 6 pm on a Saturday, the goal is every table fed correctly, in order, on time. Not "deliver excellent customer experiences." Not "drive continuous improvement." The goal. Specific, visible, shared. On your production floor, if the goal isn't that clear and that visible, that's the first thing to fix — before you worry about who's running the room.
The process is internalized, not just followed. A great line cook knows the recipe and knows when to deviate. They've internalized the standard so thoroughly they can recognize the exception. That's the target on a production floor too — not compliance to a procedure manual, but deep enough understanding of the process that the team can adapt in real time without asking permission.
Communication is constant, not periodic. In a restaurant kitchen, the call-and-response never stops. "Firing table seven." "Two minutes on the ribeye." "Corner." That's not noise. That's a system. Your equivalent is the shift handover, the constraint conversation, the end-of-day walk. If getting your team to communicate feels like pulling teeth, look at the system — not the people.
Everyone knows the team wins or loses together. A server who doesn't flag a dietary restriction doesn't just inconvenience one table. They blow the whole night for the kitchen. That interdependence is visceral in a restaurant. It can be built on a plant floor — but someone has to name it, model it, and hold the line when people revert to silos.
The person who comes to your floor already wired for all four of those things is worth ten times the person who can explain a fishbone diagram but has never had to make a real-time call with consequences.
Stop filtering on credentials. Start watching what people actually do.
One next step: Before your next internal promotion decision, write down four questions: Does this person know the goal? Can they explain the process to someone new? Do they communicate proactively when something's wrong? Do others trust them under pressure? Score each honestly — then compare that list to your shortlist. You may find the best candidate doesn't have the longest resume.
Further reading:
- First, Break All the Rules — Marcus Buckingham & Curt Coffman (Simon & Schuster, 1999). Buckingham's research on what the best managers do differently — including how great managers identify talent over credentials and build around what people can actually do.
- The Talent Code — Daniel Coyle (Bantam, 2009). On how deep practice in high-stakes, real-consequence environments builds the kind of skill that formal training rarely replicates.
- The Goal — Eliyahu M. Goldratt (North River Press, 1984). The foundational text on constraint thinking, and the argument that understanding the goal — clearly, specifically, operationally — is the first job of every person on the floor.