Blog

The Chef's Guide to Creative Problem Solving in Business

Related Resources:

The head chef at Rockpool screamed at me for twenty minutes straight because I'd served 180 covers with the wrong garnish on our signature dish. Standing there in that blazing hot kitchen, sweat dripping into my eyes, I had what business schools would probably call an "innovative breakthrough moment." But honestly? I just figured out how to think like a chef when solving any business problem.

Here's what they don't teach you in those expensive corporate training sessions: the best problem solvers aren't the ones with the fanciest frameworks or the most colourful Post-it notes. They're the ones who can work under pressure, adapt quickly, and—most importantly—taste their way to a solution.

Let me explain what I mean by that last bit.

The Mise en Place Mindset

Every decent chef knows you can't cook without proper mise en place—everything in its place. Before you even think about lighting the stove, you've organised your ingredients, sharpened your knives, and planned your timing. Most business people jump straight into "solving" before they've properly set up their workspace.

I've watched executives spend three hours in a meeting trying to solve a customer retention problem when they hadn't even looked at the actual customer feedback data. Meanwhile, any apprentice chef knows you taste the sauce before you adjust the seasoning.

The first thing I learned in that Rockpool kitchen was that good preparation isn't just helpful—it's the difference between a smooth service and absolute chaos. Same principle applies whether you're dealing with a supply chain crisis or trying to figure out why your team's productivity has dropped 30% since March.

Start with your ingredients. What information do you actually have? What's missing? What assumptions are you making that might be completely wrong?

I remember one client—a mid-sized manufacturing firm in Geelong—spent six months trying to "innovate" their way out of high staff turnover. They brought in consultants, redesigned their office space, even installed a fancy coffee machine. Turned out their main problem was that the factory floor got ridiculously hot in summer and they'd been too cheap to fix the air conditioning.

Sometimes the solution isn't creative at all. Sometimes it's just bloody obvious if you're willing to look.

The Pressure Test Philosophy

Here's where most business problem-solving goes wrong: people try to eliminate pressure instead of using it. Watch any episode of MasterChef and you'll see what I mean. The contestants who crack under pressure are usually the ones fighting against it. The winners? They channel that energy into focus.

I've been in boardrooms where executives spend half the meeting trying to make everyone "comfortable" before tackling the real issues. Mate, if your quarterly numbers are in the toilet, comfort isn't going to fix them. Sometimes you need that pressure to push through to genuinely creative problem solving training approaches.

The trick is learning to work with urgency without panicking. In a professional kitchen, you've got 200 customers waiting for their meals, orders coming in every thirty seconds, and if you mess up the timing on table twelve's mains, the whole section falls apart. But great chefs don't freeze up—they prioritise, delegate, and make split-second decisions.

The Flavour Balance Approach

This is where it gets interesting. Every good dish needs balance—sweet, sour, salty, bitter, umami. Too much of one element and the whole thing falls apart. Business problems are exactly the same, but most people approach them like they're trying to make soup with only salt.

Take customer complaints, for instance. I see businesses either completely ignore them (too much "sweet"—pretending everything's fine) or overreact and rebuild their entire service model based on three negative reviews (too much "bitter"—letting criticism dominate everything).

The best approach I've found is treating each problem like you're balancing a complex sauce. You need:

Sweet: What's working well that you want to preserve? Sour: What's the sharp criticism or challenge you can't ignore? Salty: What basic, fundamental thing needs to be solid? Bitter: What harsh reality do you need to accept? Umami: What's that deeper, underlying factor that ties everything together?

I used this approach with a retail client in Perth who was losing customers to online competitors. Instead of just cutting prices (too much "sour") or pretending their in-store experience was perfect (too much "sweet"), we looked at the whole flavour profile. Turned out their strength was personal service, but they were trying to compete on speed. Wrong game entirely.

The Brigade System for Team Problem Solving

Professional kitchens run on what's called the brigade system—everyone has a specific role, clear hierarchy, but also the authority to speak up if something's going wrong. It's not democratic, but it's not dictatorial either. It's functional.

Most corporate problem-solving sessions are either complete chaos (everyone talking at once) or complete silence (waiting for the boss to tell them what to think). Neither works.

Here's how I run problem-solving sessions now, borrowed straight from kitchen culture:

Head Chef (Project Leader): Sets the menu, makes final decisions, takes responsibility. Sous Chef (Deputy): Manages the process, keeps things moving, handles logistics. Section Chiefs (Subject Experts): Own their specific areas, have authority within their domain. Commis (Everyone Else): Execute tasks, provide information, raise concerns immediately.

The crucial bit is that last part. In a good kitchen, even the most junior commis can call out "behind you, hot!" and everyone moves. No ego, no hierarchy—just immediate response because the alternative is someone getting burned.

I've seen million-dollar projects fail because someone three levels down knew about a critical issue but didn't feel they could speak up. Meanwhile, in any decent restaurant kitchen, the dishwasher will tell the head chef if the plates are coming back with food still on them.

Tasting as You Go

Here's the biggest difference between amateur cooks and professionals: professionals taste constantly. They don't wait until the dish is finished to see if it's working. They adjust as they go.

Most business problem-solving happens like amateur cooking—you follow the recipe (framework), add all the ingredients (brainstorming sessions), then serve it up (implement the solution) and hope for the best. By the time you realise it's not working, you've wasted months and probably made things worse.

Better approach: test small, taste early, adjust quickly.

I worked with a software company that spent eight months building a "revolutionary" customer portal based on what they thought users wanted. Classic amateur mistake. Meanwhile, their main competitor was pushing out tiny improvements every two weeks, getting immediate feedback, and iterating.

Guess which approach worked better?

The Service Recovery Paradox

There's something in hospitality called the service recovery paradox—customers who experience a problem that gets fixed quickly and well often become more loyal than customers who never had a problem in the first place. It sounds counterintuitive, but it makes perfect sense when you think about it.

When something goes wrong and you handle it brilliantly, you've demonstrated your values under pressure. That's worth more than smooth sailing.

I see businesses trying to avoid problems instead of getting better at solving them. That's like a restaurant trying to never have a single order go out late instead of getting really, really good at handling it when timing goes wrong.

Both strategies matter, but if you can only pick one, pick problem-solving capability every time.

The Closing Rush

After seventeen years in business—starting in that chaotic Rockpool kitchen and working my way through consulting, training, and running my own show—I've learned that creative problem solving isn't about having the right techniques. It's about having the right attitude.

Chefs know that service will be messy, orders will come in wrong, equipment will break down at the worst possible moment. They don't try to eliminate these problems. They get really, really good at handling them quickly, calmly, and professionally.

That's the difference between businesses that thrive and businesses that just survive. The ones that thrive don't have fewer problems—they just solve them better.

And honestly? Once you start thinking like a chef, those expensive business problem solving tools start making a lot more sense. Because at the end of the day, whether you're trying to get 200 dinners out in two hours or figure out why your sales numbers are down 15%, it all comes down to the same thing: taste as you go, adjust quickly, and keep your head when everyone else is losing theirs.

Now, if you'll excuse me, I've got a client meeting in an hour and I need to practice what I preach—proper preparation prevents poor performance, as we used to say in the kitchen.