How to Prioritize Operational Problems When Everything Feels Critical

I was on a call last month with a manufacturing leader who rattled off six problems in under two minutes. Late shipments. Quality issues that keep resurfacing. A scheduling system nobody trusts. Two key employees carrying tribal knowledge that hasn’t been documented. A CRM that sales won’t use. And a growing backlog of customer complaints that nobody has time to investigate because everyone’s too busy firefighting the last one.

Prefer listening? Watch this week’s Solo Session where I expand on the topic.

When I asked which one he wanted to tackle first, he said something I hear constantly: “All of them. They’re all mission critical.”

They aren’t all critical. But I understood why it felt that way, and if you’ve ever been in a similar position, you probably do too.

When you’re running a growing operation and problems are stacking up faster than your team can address them, everything starts to feel equally urgent. Late shipments feel urgent because customers are calling. Quality issues feel urgent because they’re driving the late shipments. Tribal knowledge feels urgent because you just lost a key person last quarter and barely survived it. The CRM feels urgent because leadership keeps asking for pipeline data that doesn’t exist.

So you try to fix everything at once. Or you fix whatever screamed loudest today. Or you launch three improvement initiatives simultaneously and none of them get the attention they need to actually stick.

Six months later, you’re in the same spot. Different fires, same cycle.

Why Everything Feels Critical

This is worth unpacking because the feeling itself is the first thing to address.

When a leader tells me everything is critical, what they’re really telling me is that they don’t have clarity on what matters most right now. Not what matters in general, everything on that list matters, but what matters most given where the business is today, where it’s trying to go, and what’s actually within reach to change in the next 90 days.

That lack of clarity isn’t a personal failure. It’s an organizational one.

When there’s no shared understanding of the single most important operational priority, every problem competes for attention equally. And when everything competes equally, the loudest one wins. Not the most important one. The loudest one.

This is how you end up with an entire leadership team in reactive mode. Not because they’re incapable of being strategic, but because without clarity on what to prioritize, reactive is all that’s left.

The Three Traps

I see three predictable patterns when leaders try to prioritize without a clear method. Most leaders fall into at least one. Many cycle through all three.

1. Chasing the loudest fire

Whatever problem is creating the most noise today gets all the attention. A customer calls about a late order, and suddenly the entire leadership team is pulled into expediting.

The quality issue that’s been quietly driving those late orders? It doesn’t make noise the same way. So it sits. The loudest problem gets resources. The most important problem waits.

2. Trying to fix everything at once

Leadership identifies six priorities for the quarter and assigns resources to all of them. On paper it looks productive. In practice, nothing gets enough focus to produce a meaningful result. Teams are stretched. Progress is incremental at best.

When nothing meaningfully improves, leadership starts to question whether the team can execute, when the real issue is that the team was set up to fail by being pointed in six directions at once.

3. Solving symptoms instead of root causes

A company is missing delivery dates. So they add overtime. Or they hire more people. Or they yell louder at the production team to move faster. Delivery improves for a few weeks, then slides back.

Because the actual problem was never capacity. It was a scheduling process that doesn’t reflect reality, fed by an ERP with unreliable data, maintained by three people who all enter information differently. The overtime was treating the symptom. The scheduling process was the disease.

These three traps feed each other.

When you’re chasing the loudest fire, you’re almost always solving symptoms. When you’re trying to fix everything, you don’t have the bandwidth to investigate root causes. And when you’re solving symptoms, the same problems keep coming back, which makes everything feel critical again.

It’s a cycle, and the only way out is to stop and get clear on what actually matters most.

Start With What You Can Measure

Here’s where leaders expect me to hand them a prioritization matrix. I’m not going to do that.

Not because matrices are useless, but because they require inputs that most overwhelmed leaders don’t have yet. You can’t score and rank problems you haven’t actually diagnosed.

Instead, I start with a simpler question: what are you already measuring?

Every business has something. Maybe it’s on-time delivery. Maybe it’s defect rates. Maybe it’s revenue per employee. Maybe it’s quote turnaround time. Maybe it’s just how many customer complaints landed in your inbox this month.

It doesn’t need to be sophisticated. It needs to be real.

Whatever you’re measuring, that’s your starting point. Not because those metrics are perfect, but because they give you something concrete to anchor the conversation. When everything feels critical, the first job is to move from feelings to facts.

Here’s an example. A leader tells me shipments are late, quality is slipping, and the team is burning out. All three feel equally urgent.

But when I ask for the numbers, we find that on-time delivery is at 89%. That means 11% of shipments are late. When we look at why those shipments are late, 70% of them trace back to the same three production processes. When we look at those processes, two of them have documented quality issues that have been flagged in customer complaints for over a year.

Now we have something.

The late shipments, the quality issues, and the team burnout aren’t three separate problems. They’re one problem expressing itself three ways. The quality issues in those specific processes are driving the late shipments, and the firefighting required to manage both is burning out the team.

One root issue. Three symptoms. That changes the prioritization conversation completely.

Follow the Connections

This is the part most people skip.

Once you’ve identified what appears to have the highest impact based on what you can measure, the next step is to ask: what’s upstream of this?

Problems in operations rarely exist in isolation. They’re connected. A delivery problem is often a scheduling problem. A scheduling problem is often a data problem. A data problem is often a process problem; people entering information inconsistently because there’s no standard, or the standard exists but nobody follows it because it was written four years ago and doesn’t match how the work actually gets done.

When you follow those connections, you often find that the problem with the highest visible impact isn’t the one you need to fix first. The one you need to fix first is the one that’s feeding it.

This is where the real prioritization happens. Not in a scoring matrix, but in the discipline of tracing symptoms back to their source and being honest about what you find.

Sometimes the answer is uncomfortable. Sometimes the root issue is that leadership hasn’t provided clear expectations for how a process should work. Sometimes it’s that the process was never documented in the first place. Sometimes it’s that the team has been telling leadership about this problem for two years and nobody addressed it.

Whatever it is, that’s your priority. Not because it’s the loudest or the most visible, but because fixing it will relieve pressure across multiple symptoms simultaneously.

Pick One

I know how that sounds. You’ve got six problems and I’m telling you to pick one.

But here’s what I’ve learned after nearly 30 years of doing this work: companies that pick one priority and execute it well outperform companies that pick five and spread thin every single time.

Picking one doesn’t mean ignoring the others. It means being intentional about sequence. You’re deciding what to fix first, not what to fix ever. The other problems don’t disappear. They go on a list. And many of them will improve on their own once the root issue is addressed, because they were connected to it all along.

This is where crawl, walk, run actually matters. It’s not just an implementation philosophy for individual systems. It’s how you approach the entire operation. Master one thing. Stabilize it. Then move to the next.

The compounding effect of this approach over 6, 12, 18 months is dramatically more impactful than trying to improve everything incrementally at the same time.

The hard part isn’t the method. The hard part is the discipline to stay focused when the next fire starts screaming for attention. That’s a leadership challenge, not an operational one.

What This Actually Looks Like

Let me bring this together with a practical example.

A manufacturer is running at about $12 million in revenue and trying to grow. Leadership identifies their biggest problems: on-time delivery is inconsistent, quality complaints are increasing, they’re over-reliant on a handful of experienced employees, and their production scheduling is reactive instead of planned.

Step one: what are you measuring?

On-time delivery is at 87%. Quality complaints have doubled in the last six months. They don’t have a formal metric for tribal knowledge dependency, but they know that when one specific person is out, an entire production line slows down.

Step two: follow the connections

Why is delivery at 87%? Because production schedules change daily based on whatever’s most urgent. Why do schedules change daily? Because the information feeding the schedule is unreliable, orders aren’t entered consistently, and lead times in the system don’t match reality.

Why are quality complaints up? Because the experienced operators who catch issues before they leave the floor are the same people whose knowledge hasn’t been documented. When they’re stretched thin covering for the reactive scheduling, quality slips.

Step three: pick one

The production scheduling process is the root. It’s fed by inconsistent data entry (a process problem), it creates the daily chaos that stretches the experienced operators (which drives quality issues), and it directly causes the delivery misses.

Fix scheduling, and you relieve pressure on delivery, quality, and the team simultaneously.

That’s one priority. Not six. One that unlocks movement on three others.

Once scheduling is stabilized, you move to the next highest-impact problem, which is likely documenting the tribal knowledge that those experienced operators carry. Then you keep going. Crawl, walk, run.

When You Don’t Have Clean Data

I want to address this because it’s the objection I hear most often: “We don’t have good data to make this kind of decision.”

You have more than you think.

You have customer complaints, even if they’re in emails instead of a tracking system. You have on-time delivery numbers, even if they’re rough. You have a general sense of which processes break most often, because your team is firefighting them every week.

Start there. Imperfect data is better than no data, and it’s significantly better than gut feel disguised as strategy.

You don’t need a perfect picture. You need an honest one.

Talk to your team. Ask the people doing the work what breaks most often, what workarounds they’ve built, and what they’d fix first if they could only fix one thing. The front line almost always knows where the real problem is. They just haven’t been asked.

Final Thoughts

The reason everything feels critical is almost never because everything is actually critical. It’s because there’s no filter. No shared understanding of what matters most right now. No clarity.

And without that clarity, every problem competes for attention equally. The loudest one wins. Resources get spread across too many fronts. Symptoms get treated while root causes persist.

And six months later, the same leader is sitting in the same meeting listing the same problems.

The way out is straightforward but not easy: measure what you can, follow the connections, pick the one problem whose resolution will create the most relief across the operation, and give it the focus it deserves. Then do it again.

If you’re looking for a method to rank the specific improvement projects once you’ve identified where to focus, I’ve written about that separately: How to Prioritize Process Improvement Initiatives. That’s the tactical next step after this strategic decision is made.

That’s it for today.

See you all again next week!

Dave