×

Your Issues List Isn’t Supposed to Be a Storage Facility

There’s something strangely satisfying about adding a problem to an Issues List.

Someone raises a concern. You write it down. Everyone agrees it’s something that needs attention.

Great. It’s on the list.

Then next week comes around, & there it is again.

And the week after that.

Before long, you’ve got an Issues List full of problems that everyone knows about, but nobody seems to be doing anything about.

At some point, you have to ask yourself a question.

Are we actually solving issues, or are we just getting better at keeping track of them?

Because an Issues List isn’t supposed to be a storage facility for every problem your business has ever encountered.

It’s supposed to help you get things solved.

The Problem With Collecting Issues

Having spent years working as an Integrator with leadership teams running on EOS®, I’ve come to appreciate just how useful a well-managed Issues List can be.

But there’s a trap teams can fall into.

Every meeting generates another handful of issues. Something on the Scorecard is off track. A Rock is falling behind. Someone raises a concern about a process that isn’t working.

All legitimate things to capture.

The problem starts when adding something to the list becomes the end of the conversation rather than the beginning of solving it.

The list gets longer. The same issues keep appearing. And eventually, people stop believing anything will actually change.

That’s when the Issues List goes from being a useful tool to becoming another piece of administration.

And nobody needs more of that.

Stop Solving the Easy Stuff First

Here’s another thing that can happen.

The team has ten issues on the list, so they start at the top & work their way down.

Sounds logical enough.

Except the first issue might be something minor that takes five minutes to resolve, while the seventh issue is the uncomfortable conversation nobody particularly wants to have.

Guess which one gets discussed first?

It’s tempting to knock over the easy things because it feels productive.

You get to cross something off the list. Everyone feels like progress has been made.

But if the biggest issue is still sitting there untouched at the end of the meeting, have you really made the best use of everyone’s time?

One of the disciplines I like about the Issues Solving Track® is that you prioritise the most important issues rather than simply working through the list in order.

You identify the top priorities & tackle the biggest one first.

Not the easiest.

Not the most comfortable.

The one that matters most.

Are You Solving the Problem or Just the Symptom?

Of course, prioritising an issue is only half the battle.

You still have to work out what’s actually causing it.

This is where I think teams can lose a surprising amount of time.

Someone says sales are down, so the conversation immediately turns to finding more leads.

But what if the leads are fine & the real problem is conversion?

Or maybe customer complaints are increasing, so everyone starts talking about improving customer service.

But what if the real issue is that expectations aren’t being set properly before the work even begins?

If you jump straight into solutions, you can spend a lot of time fixing something that wasn’t actually broken.

That’s why the first step of IDS® matters so much.

Identify. Discuss. Solve.

The temptation is to rush through Identify because everyone wants to get to Solve.

But if you haven’t identified the real issue, you’re probably going to see it again.

Possibly with a slightly different name.

And it’ll end up straight back on the list.

A Decision Isn’t a Solution Until Something Changes

There’s one more trap worth watching.

The leadership team has a good discussion. Everyone agrees on what needs to happen. Someone writes down the decision.

Meeting finished. Problem solved.

Well, not quite.

If the solution requires action, someone needs to own it.

What exactly needs to happen? Who’s responsible? When will it be done?

Without those things, you’ve probably just had an interesting conversation.

EOS helps create that accountability through clear To-Dos, assigned to one person & reviewed at the next Level 10 Meeting®.

The aim isn’t to generate more administration.

It’s to make sure the decisions you make actually turn into action.

Because agreeing that something should change & making the change are two very different things.

The Goal Is a Shorter List, Not a Better One

A good Issues List isn’t necessarily an empty one.

Businesses will always have problems. New challenges come up, priorities change & things don’t always go to plan.

That’s normal.

The difference is what happens to those issues once they’re identified.

Do they get prioritised?

Does the team take the time to identify the real cause?

Are decisions made & followed through?

Or do the same problems keep getting carried forward because nobody’s quite sure what to do with them?

The purpose of the Issues List isn’t to prove how many problems your leadership team can identify.

It’s to help the team solve the issues that are holding the business back.

So next time you’re looking at your Issues List, pay attention to how many items you’ve been carrying around for weeks.

And ask yourself whether they’re still there because they’re genuinely difficult to solve, or because nobody’s tackled them properly.

Your Issues List should be a place where problems go to get solved.

Not somewhere they go to retire.