How to Figure Out What's Actually Driving a Problem

The Wrong Fight

There's a debate that surfaces in almost every operations meeting I've ever sat in. Something breaks, or performance dips, or a number moves in the wrong direction, and within five minutes the room splits into two camps. One side wants to pull reports. The other side already knows what the problem is and wants to fix it.

Both camps are usually half right, and that's what makes it so frustrating.

The data people spend three weeks building a dashboard that confirms what the gut people already suspected. The gut people make a change that fixes one symptom while the real cause keeps running. Everyone goes home feeling like they did good work. The problem comes back in a different form six months later.

This happens because most people treat data and intuition as opposing philosophies instead of complementary tools. The actual skill, the one that separates good problem-solvers from great ones, is knowing when to use each, and how to get them to inform each other.

What Data Is Actually Good For

Data is a record of what already happened. That sounds obvious, but people constantly treat it like a crystal ball, or worse, like a verdict.

What data does well: it tells you the shape of a problem. Scale, frequency, timing, distribution. If your call handle time spiked last Tuesday, the data can tell you by how much, which team it affected, what time of day it peaked, and whether it correlated with anything else. That's genuinely useful. Without the data, you're guessing at all of those dimensions.

What data does badly: it almost never tells you why. You can stare at a dashboard for a long time and still have no idea what caused the thing you're looking at. The data shows you the crater. It doesn't tell you what hit.

I spent several years building and running contact center operations, and we had a lot of data. Call volume by hour, handle time by agent, CSAT scores by queue, first contact resolution rates broken down six different ways. If you wanted a report, we could build it. And we did, constantly. But I watched teams fall into a trap where they treated data hygiene as problem-solving. They'd tune the reporting, reconcile discrepancies, debate metric definitions, and then look up and realize the underlying issue hadn't moved.

More data is not the same as more clarity. And confusing the two is expensive.

What Gut Is Actually Good For

Your gut is your pattern library. It's everything you've seen before, compressed into a fast signal. When a seasoned manager walks into a team meeting and something feels off before anyone has said anything specific, that's not magic. That's their brain running a rapid comparison against thousands of prior situations and flagging an anomaly.

The problem is that most people can't articulate what their gut is actually responding to. It's a feeling, not a sentence. And when you can't explain it, you can't verify it, and you can't act on it with confidence.

There's also a darker side to gut-driven problem-solving. Your gut is built from your own experience, which means it inherits all your blind spots. If every team you've ever managed had a certain dynamic, your gut will pattern-match toward that dynamic even when the current situation is different. Confirmation bias runs on intuition, not data.

I've made gut calls that were exactly right, made in under a minute, based on a conversation I had in the hallway. I've also made gut calls that were confidently wrong because I was solving last year's problem in this year's situation. The difference usually came down to whether I stopped to ask myself: what is my gut actually responding to here? Can I name it?

The Part Nobody Talks About: Using Them Together

Here's how it actually works when you get it right.

Gut goes first. Not to solve the problem, but to generate a hypothesis. Something feels off with your top-of-funnel conversion. Your instinct says the lead quality changed, not the sales motion. Good. Write that down. That's your starting point.

Then you use data to pressure-test the hypothesis. You're not fishing for anything interesting. You're looking for evidence that either supports the hypothesis or breaks it. If lead quality dropped, you should see it in lead source data, in time-to-close by cohort, in early pipeline drop-off rates. If you don't see it there, your gut was pointing in the wrong direction, and that's useful information. Go back to square one.

If the data supports the hypothesis, now you have something. You have a narrative that accounts for what you're seeing, and you have data that's consistent with it. That's still not proof, but it's enough to act on with low-cost interventions while you gather more signal.

The flip side also works. Sometimes data finds something your gut never would have flagged. A correlation you weren't looking for. A segment that's behaving differently from the rest. When that happens, resist the urge to explain it immediately. Sit with it. Talk to people who are close to the work. Let your gut catch up to what the data found. Experienced operators are good at this, they see an anomaly in a report and immediately start mentally scanning their recent conversations and observations for something that connects.

Point being, the loop runs both directions. Gut generates hypotheses that data tests. Data surfaces anomalies that gut interprets. Neither one finishes the job alone.

The Practical Version

When you're looking at a problem and you're not sure how to start, run this sequence.

Write down your gut read first, before you pull any data. Not because your gut is right, but because it will bias your data interpretation if you don't surface it explicitly. You want to examine your hypothesis, not accidentally prove it.

Then ask: what would the data look like if my hypothesis were true? List the specific signals you'd expect to see. Now go look for those signals. If they're there, you have traction. If they're not, you have a new question.

Then ask: is there anything in the data that I didn't expect to see? Don't just look for confirmation. Look for surprises. Surprises are usually where the real problem lives.

Finally, talk to someone close to the work. Data and gut both operate at a distance from the actual human experience of doing the job. The person running the process, handling the customer, executing the task, often knows exactly what's wrong. They just haven't been asked, or they don't think anyone wants to hear it.

Most of the best diagnoses I've been part of ended with someone saying, "Yeah, we've known about that for a while." The data confirmed it. The gut suspected it. But the person doing the work could have told you in thirty seconds.

Bottom Line

Data tells you what happened. Your gut tells you where to look. Neither one solves the problem alone, and treating them as opponents is how you end up with expensive investigations that land on conclusions everyone already knew, or fast confident decisions that fix the wrong thing.

The managers who are actually good at this use both, deliberately, in sequence, and they stay curious enough to let each one challenge the other. When your gut and your data point to the same thing, you move fast. When they disagree, you've found something worth understanding.

That tension is not a problem. It's the work.