Solving Wicked Problems in the Wild

Operations isn’t a clean spreadsheet. It’s messy, pressured, and full of moving parts — systems break, comms get lost, and teams burn out. I’ve made it my job to dive headfirst into that chaos and fix what matters. In this post, I’m breaking down how I approach complex, high-friction problems — the kind that don’t show up neatly in a dashboard — and what it takes to solve them in the real world.

What’s a Wicked Problem?

A “wicked problem” doesn’t mean unsolvable — it means there’s no neat, single solution. It’s embedded in human behaviour, shifting systems, competing priorities, or all of the above. In the real world, it looks like:

• An optimisation system that technically works, but operators don’t trust it

• A production bottleneck that moves depending on the shift

• A training process that ticks the box but doesn’t build actual skill

• A “downtime cause: unknown” that’s used 400 times a month

You can’t solve these problems by throwing another spreadsheet at them. They require context, trust, and usually a bit of humble fieldwork.

My 5-Step Field Approach

1. Go to the noise

If the data doesn’t make sense, go to where it’s happening. I don’t mean another meeting — I mean the actual site, the actual shift, the actual system. I walk the floor. I ask “What’s the hardest part of your shift?” and I shut up. I look for workarounds. I watch where things slow down, where people pause, and where conversations stop.

2. Separate the symptom from the system

You’ll hear a lot of noise: “The scanner’s useless,” “It always does this,” “That’s just how we do it.” But usually, the visible pain isn’t the real root. My job is to dig. Is it a lack of training? Misaligned logic? A broken feedback loop? Often the problem isn’t what the team is doing — it’s why they think they have to.

3. Loop in the real experts — the people doing the work

You cannot fix wicked problems alone. I treat operators, team leaders, and even the most cynical shift veterans as design partners. I ask, “What would make this easier?” and build changes with them, not for them. When people are part of the process, they protect it.

4. Pilot in the wild, not the whiteboard

I don’t wait for perfect. If we think a change will help — a new visual tracker, a modified workflow, a logic tweak — we pilot it small and fast. I let the shift trial it, stress-test it, even break it. That’s where the gold is: you learn more in 48 hours of real-world feedback than in 3 weeks of planning.

5. Close the loop — visibly

The last step is always the same: make the change real and visible. I show what we heard, what we tried, and what we’re keeping. Whether it’s a poster, a dashboard update, or a shoutout in the team brief, I make sure the people closest to the problem see that they weren’t just heard — they were followed through.

The Result? Progress That Sticks

Solving wicked problems isn’t about brilliance — it’s about momentum. It’s about creating clarity where there was fog. It’s about reducing friction so that people can do their best work without fighting broken systems.

It’s not always sexy. But when a process flows better, when a shift runs smoother, when rework drops and people actually trust the logic — that’s the kind of win that matters.

Want to Tackle Your Own Wicked Problem?

If you’re dealing with something messy, layered, or just stuck — send it my way. I’m always up for a challenge. Let’s fix what’s broken, simplify what’s unclear, and build on what’s already working.