My Thoughts
What Chefs Know About Creative Problem Solving That Most Managers Don't
Related Reading:
The best business lesson I ever learnt happened at 2 AM in a Brisbane kitchen when the head chef threw a tea towel at my head.
I was doing some consulting work for a restaurant group back in 2019, trying to help them streamline their operations. Classic business consultant stuff - process maps, efficiency metrics, the whole nine yards. But their Saturday night service was falling apart faster than a cheap umbrella in a Cyclone Tracy remake.
That's when Chef Marco (not his real name, but close enough) grabbed me by the sleeve and said, "Forget your bloody flowcharts, mate. Come watch how we actually solve problems."
What happened next completely changed how I think about creative problem solving in business environments.
The Kitchen Is The Ultimate Problem-Solving Laboratory
Most managers think problem solving is about following steps. Seven steps, six steps, five whys - doesn't matter. They want a process they can laminate and stick on the wall.
Chefs don't have that luxury.
When the oven breaks during dinner service, they don't convene a meeting. When the salmon delivery doesn't show up, there's no time for root cause analysis. When three waiters call in sick on Mother's Day, you don't get to postpone the customers.
You adapt. Fast.
The difference between kitchen problem solving and boardroom problem solving is like the difference between jazz improvisation and reading sheet music. Both have their place, but when the building's on fire, you want the jazz musician.
Why Most Business Problem Solving Falls Flat
Here's what I've noticed after fifteen years of watching companies struggle with basic challenges: they're addicted to perfect information.
I once worked with a mining company that spent eight months analysing why their productivity dropped 12% in Q3. Eight months! By the time they figured out it was a training issue, they'd lost two more quarters of performance. A decent chef would've spotted that problem in week one and had three different solutions running by week two.
The corporate world has this bizarre idea that problems should be solved once, permanently, with a documented procedure that prevents them from ever happening again.
Chefs know better. They know that every service brings new problems, and the goal isn't to eliminate problems - it's to get so good at solving them that your customers never notice they existed.
The Three Kitchen Principles Every Manager Should Steal
1. Test Solutions In Real Time
When a chef thinks the sauce needs more acid, they don't commission a study. They add a splash of lemon juice and taste it. If it works, brilliant. If it doesn't, they try something else in thirty seconds.
Most businesses treat every solution like it's carved in stone. They implement new processes with the solemnity of a constitutional amendment. Then wonder why nobody follows them.
I watched one team spend six weeks designing the "perfect" customer complaint process. Meanwhile, their chef mate down the road was already on version 12 of his table management system, iterating based on what actually worked during real service.
2. Embrace Controlled Chaos
This might upset some of you process lovers, but here's the truth: the best problem solvers I know are comfortable with a bit of mess.
A good kitchen during service looks like organised chaos to an outsider. Orders flying, pans clattering, everyone shouting - but underneath it all is a rhythm. Everyone knows their role, but they're also ready to jump in wherever they're needed.
Compare that to most offices, where crossing departmental boundaries requires three forms and a manager's approval.
I remember working with a logistics company where drivers weren't allowed to suggest route improvements because "that's the planning department's job." Meanwhile, these drivers were out there every day, seeing traffic patterns the planners never witnessed. Absolute madness.
3. Accept That Some Problems Don't Stay Solved
This is the big one. The one that makes finance directors break out in hives.
Equipment breaks. Staff get sick. Suppliers let you down. Customers change their minds. These aren't problems to be solved once and forgotten - they're ongoing realities to be managed.
The best chefs I know have backup plans for their backup plans. Not because they're pessimists, but because they're realists who want to keep serving great food regardless of what goes wrong.
Yet I still see companies treating recurring issues like moral failures. "Why is this happening again? Didn't we fix this last year?"
The Australian Advantage (And Why We're Wasting It)
Australians are naturally good at this kind of problem solving. We've got that whole "she'll be right" mentality that can be brilliant when channeled properly.
Look at how we handled the 2000 Olympics. Half the infrastructure wasn't finished six months before the games. Did we panic? Did we form a committee? No, we rolled up our sleeves and made it work. And it was bloody magnificent.
But somewhere along the way, we got seduced by overseas management consultants telling us we needed more "rigorous processes" and "systematic approaches." Don't get me wrong - some structure is good. But we've gone too far the other way.
I worked with a Perth mining outfit last year where they had seventeen different approval stages for equipment repairs. Seventeen! Meanwhile, their maintenance team was dying to just fix the bloody machines and get back to work.
What This Looks Like In Practice
Let me give you a real example. I was working with a Melbourne-based training company (not unlike the professional development workshops you see around town) when they hit a major delivery problem.
Their main trainer got food poisoning two hours before a major corporate session. Classic crisis.
The old approach would've been: call the client, apologise profusely, reschedule, maybe offer a discount. Damage control.
Instead, they went full chef mode. Within fifteen minutes, they had two junior trainers splitting the content, the sick trainer dialling in for the technical sections he could manage, and they'd restructured the whole day around smaller group activities that needed less facilitation.
The client loved it. Said it was more engaging than their usual sessions. They booked three more workshops on the spot.
That's kitchen thinking applied to business problems.
The Uncomfortable Truth About Innovation
Here's something that might ruffle some feathers: most corporate innovation programs are complete rubbish.
You know the ones - suggestion boxes that nobody checks, innovation days where everyone sits around talking about disruption, those awful brainstorming sessions where someone inevitably suggests "gamification."
Real innovation happens when you're under pressure and need to solve an actual problem. Not when you're in a comfortable conference room with unlimited coffee and motivational posters.
Chefs innovate constantly, not because they're trying to be creative, but because they're trying to survive service with dignity intact. They combine techniques from different cuisines, repurpose equipment in unexpected ways, and create new dishes because they ran out of ingredients for the planned ones.
That's how you get genuine breakthroughs - not from scheduled innovation time, but from intelligent responses to real constraints.
Why This Matters More Now Than Ever
The business environment is getting more unpredictable, not less. Supply chains that worked for decades are breaking down. Customer expectations are changing monthly. The skills that got us here won't get us there.
We need to learn from people who've always worked in unpredictable environments. People who've built careers around solving problems they've never seen before, with resources they don't have, in timeframes that seem impossible.
People like chefs.
Making The Switch
If you want to bring more kitchen thinking into your business, start small. Pick one recurring problem - something that comes up monthly and always seems to surprise everyone.
Instead of trying to prevent it from happening again, assume it will happen again and prepare accordingly. Build flexibility into your response. Train your team to improvise intelligently.
Most importantly, measure results, not processes. Chefs don't get points for following recipes perfectly - they get judged on whether the food tastes good and arrives on time.
The same should be true for your problem-solving efforts.
Stop trying to eliminate all uncertainty from your business. Start getting better at dancing with it instead.
Looking for more insights on practical problem-solving approaches? Check out these resources on creative problem solving training and strategic thinking development.