Posts
Why Your Problem Solving Mindset is Probably All Wrong (And How I Learnt This the Hard Way)
Related Reading: Training Core Blog | My Thoughts | Further Resources | Professional Advice
So there I was, 3am on a Tuesday morning in 2019, staring at a whiteboard covered in what I thought was brilliant problem-solving methodology. Charts, flowcharts, decision trees – the whole catastrophe. My client's operations manager was supposed to arrive at 8am to review our "comprehensive solution framework." Instead, she took one look at my masterpiece and said, "This looks like you're trying to solve the wrong bloody problem."
She was right. And it only took me fifteen years in business consulting to realise I'd been thinking about problem-solving completely backwards.
Here's what nobody tells you about developing a proper problem-solving mindset: it's not about having more tools in your toolkit. It's about knowing when to throw the toolkit out the window entirely.
The Myth of Methodical Thinking
Every problem-solving course I'd ever attended – and trust me, I've been to plenty – started with the same premise. "Follow these seven steps." "Use this proven framework." "Apply this systematic approach." What absolute rubbish.
Real problems don't read business textbooks. They don't follow your neat little process maps or wait patiently while you work through phases one through seven. Most importantly, they don't care about your certification in Six Sigma or your collection of Post-it notes.
The problem-solving mindset that actually works is messier, more intuitive, and requires you to be comfortable with being completely wrong about your initial assumptions. Which, let's face it, you will be. About 73% of the time, in my experience.
What Plumbers Know About Business Problems
I learnt more about effective problem-solving from watching my mate Dave fix a blocked drain than from any management consultant. Dave doesn't start with a systematic analysis of the drainage system's hierarchical structure. He doesn't map out the customer journey of water through the pipes.
He sticks his head under the sink, has a listen, and makes an educated guess about where the blockage might be. If he's wrong, he tries something else. No ego, no commitment to the wrong solution just because it looked good on paper.
This is what I call the "plumber's mindset" – practical, adaptable, and refreshingly free of jargon. It's served me better in twenty years of business consulting than all the structured problem-solving methodologies combined.
Your problem-solving mindset needs to start with intellectual humility. Not the fake kind where you say "I could be wrong" while clearly believing you're not. The real kind where you genuinely expect to be wrong and you're ready to pivot faster than a tech startup running out of funding.
The Problem With Problems
Most business problems aren't actually problems – they're symptoms. And here's where that traditional problem-solving mindset fails spectacularly. It treats every issue like a mechanical fault that needs fixing, rather than a signal that something deeper is out of alignment.
I once spent three months helping a Melbourne retail chain "solve" their customer service complaints. We redesigned their complaint handling process, retrained staff, implemented new software, the works. Customer satisfaction scores improved for exactly six weeks before sliding right back to where they started.
The real problem? Their store managers were under such pressure to hit sales targets that they were actively discouraging staff from spending time with customers who weren't buying immediately. All our process improvements were just window dressing on a fundamentally flawed incentive structure.
This is why the most important question in problem-solving isn't "How do we fix this?" It's "What if this isn't actually broken?"
The Art of Productive Laziness
One of my most controversial opinions: the best problem solvers are strategically lazy. They look for the simplest possible solution first, not the most comprehensive one.
I call this "productive laziness," and it drives perfectionists absolutely mental. But it works because most business problems have embarrassingly simple solutions that everyone overlooks while they're busy being impressive.
Take inventory management issues. I've seen companies spend months implementing sophisticated forecasting systems when the real solution was having someone actually count what was on the shelves once a week. Revolutionary stuff.
The creative problem solving training I attended in Brisbane last year confirmed this – their most successful case studies involved solutions so simple that participants initially dismissed them as "too obvious."
Strategic laziness means asking: "What's the stupidest simple thing we could try first?" Nine times out of ten, it either solves the problem entirely or gives you much better information about what you're actually dealing with.
When Expertise Becomes the Enemy
This is going to annoy some people, but expertise can be the enemy of good problem-solving. Not always, but often enough that it's worth paying attention to.
Experts know too much about how things "should" work. They've invested years learning the right way to approach problems in their field. This makes them brilliant at solving familiar problems efficiently, but surprisingly poor at recognising when familiar problems are actually unfamiliar problems wearing a disguise.
I've watched brilliant engineers spend weeks debugging software issues that turned out to be caused by a loose cable. I've seen marketing experts design elaborate campaigns to address "brand awareness problems" when the real issue was that the product was genuinely inferior to competitors.
The problem-solving mindset that works brings together expertise with what I call "productive ignorance" – the willingness to ask stupid questions and consider obvious solutions that experts might dismiss too quickly.
Sometimes the most valuable person in your problem-solving process is the intern who doesn't know enough to know why your obvious solution "won't work."
The Power of Wrong Solutions
Here's something they don't teach you in business school: wrong solutions are often more valuable than right ones. Not because being wrong is good, obviously, but because wrong solutions fail fast and give you information you couldn't get any other way.
The traditional problem-solving mindset treats wrong solutions as failures to be avoided. The effective problem-solving mindset treats them as cheap experiments that eliminate possibilities quickly.
I learnt this working with a food manufacturer in regional Queensland who was losing money on every batch of a particular product. We tried six different "solutions" over three months. Five of them made things worse. But each failure taught us something specific about the underlying process that we couldn't have learnt through analysis alone.
The sixth solution – adjusting the temperature by two degrees at a specific point in the process – solved the problem completely. We'd never have found it without the five failures that came before.
This is why I'm suspicious of consultants who present you with the perfect solution straight up. Either they're solving a problem they've seen before (in which case, why are they charging consultant rates?), or they're guessing and pretending it's analysis.
Building Your Problem-Solving Instincts
The most underrated skill in problem-solving is pattern recognition, but not the kind you think. Not recognising patterns in data or processes – any decent analyst can do that. Recognising patterns in how problems hide from you.
Problems have personalities. Some problems are attention-seeking – they create drama and noise while the real issue quietly grows in the background. Other problems are shy – they only show up under specific conditions that you might not encounter during normal business hours.
My favourite problems are what I call "shape-shifters." These are the ones that change depending on who's looking at them. Ask the sales team about the problem and you'll get one story. Ask operations and you'll get a completely different story. Ask finance and you'll wonder if you're all working for the same company.
The shape-shifter problems require a different approach entirely. Instead of trying to pin down the "real" problem, you need to understand why different people are seeing different things. Often, that's where your actual solution lives.
The Melbourne Mindset vs. The Sydney Approach
I've noticed regional differences in problem-solving approaches that probably say more about business culture than anyone wants to admit. Melbourne businesses tend to overthink problems – lots of analysis, lots of process, lots of very impressive documentation that may or may not lead to action.
Sydney businesses tend to underthink problems – quick decisions, rapid implementation, fix it if it breaks later. Neither approach is inherently better, but both have predictable failure modes.
The Melbourne approach fails when the analysis becomes more important than the outcome. I've seen companies spend more on studying problems than it would have cost to try three different solutions.
The Sydney approach fails when the quick fix creates bigger problems down the line, or when the problem actually requires deeper understanding before you can address it effectively.
The problem-solving mindset that works borrows from both: Melbourne's thoroughness when you need it, Sydney's bias toward action when analysis won't help.
What Nobody Tells You About Team Problem-Solving
Most problem-solving happens in teams, but most problem-solving training focuses on individual techniques. This is backwards.
Team problem-solving isn't just individual problem-solving with more people. It's a completely different beast with its own dynamics, politics, and failure modes.
The biggest trap in team problem-solving is consensus-seeking. Everyone wants to find solutions that everyone can agree with. This sounds sensible until you realise that problems don't care about team harmony. Sometimes the right solution makes people uncomfortable, challenges existing power structures, or requires someone to admit they've been doing things wrong.
I've seen too many "collaborative problem-solving sessions" where the real solution was obvious to everyone in the room, but politically impossible to suggest. These sessions produce elaborate compromises that solve nothing while making everyone feel included in the process.
Effective team problem-solving requires what I call "constructive discomfort" – the willingness to propose solutions that might upset people if they work.
The Technology Trap
Since everyone's talking about AI and automation, let me share a controversial opinion: technology rarely solves business problems. It amplifies whatever processes you already have.
If your processes are good, technology makes them better. If your processes are rubbish, technology makes them efficiently rubbish at greater scale.
I've watched companies implement expensive software solutions to "solve" communication problems, only to discover that the problem wasn't the communication tools – it was that people didn't actually want to communicate with each other.
The problem-solving mindset that works treats technology as a potential amplifier, not a solution. Fix the underlying process first, then look for technology that helps you do more of what's already working.
This applies to AI tools too. Throwing AI at a problem you don't understand is just expensive guessing at scale.
When to Give Up (And Why That's Not Failure)
Here's the most controversial thing I'll say: sometimes the right solution is to stop trying to solve the problem.
Not every problem needs solving. Some problems solve themselves if you leave them alone long enough. Others are symptoms of necessary transitions that you can't shortcut. Some problems cost more to solve than they cost to live with.
The traditional problem-solving mindset treats giving up as failure. The mature problem-solving mindset recognises that knowing when not to solve problems is just as important as knowing how to solve them.
I spent six months trying to help a family business resolve conflicts between the founder and their adult children who worked in the company. Eventually, I realised that the "problem" wasn't actually a problem – it was a family working through a natural transition that couldn't be facilitated or process-mapped away.
The solution was to stop treating it as a business problem and recognise it as a family issue that would resolve in its own time.
Sometimes the most sophisticated problem-solving approach is to step back and let life happen.
The Real Secret (That Isn't Really Secret)
After twenty years of consulting, here's what I've learnt about the problem-solving mindset that actually works: it's not about having better techniques or more sophisticated frameworks.
It's about being genuinely curious about why things are the way they are, rather than being immediately focused on how to change them.
Most people approach problems with solutions already in mind. They're not really trying to understand the problem – they're trying to confirm that their preferred solution will work.
The problem-solving mindset that works starts with genuine curiosity and stays curious longer than feels comfortable. It asks questions like "What if this problem is actually serving a purpose we don't understand?" and "What would have to be true for this seemingly stupid situation to make perfect sense?"
This isn't about being philosophical or academic. It's practical. Problems that persist despite obvious solutions are usually persisting for non-obvious reasons. Understanding those reasons is how you find solutions that actually stick.
Looking for more unconventional business wisdom? Check out our posts for ideas that actually work in the real world.