How the EOS Issues Solving Track Helps You Solve Problems for Good

Certified EOS Implementer, Entrepreneurial Operating System, EOS, Expert EOS Implementer, Professional EOS Implementer
business action

Most leadership teams don’t have an issue-solving problem – they have a talking problem.

They spend hours in meetings discussing the same challenges again & again, never really fixing them. The same issues reappear next week, just with different names.

That’s why EOS gives you a simple framework that cuts through the noise – the Issues Solving Track, often known as IDS™: Identify, Discuss, Solve.

It’s one of the simplest tools in EOS, but also one of the most powerful. When used properly, it changes the way teams think, communicate & make progress.

Let’s unpack what it is, how to use it, & how to make it stick in your business.

What Is the EOS Issues Solving Track (IDS)?

The Issues Solving Track is EOS’s practical process for resolving business challenges once & for all.

It’s built on three steps:

  1. Identify – Get to the root cause of the issue.
  2. Discuss – Have an open, honest conversation about it.
  3. Solve – Agree on the next step & assign clear ownership.

That’s it – simple, but game-changing when done right.

In practice, teams use IDS every week during their Level 10 Meeting, where they dedicate time to solving their biggest issues, not just talking about them.

Why Most Teams Don’t Actually Solve Issues

Most meetings fail because people:

  • Jump straight into discussing before they’ve identified the real issue.
  • Avoid the tough conversations.
  • Confuse symptoms with root causes.
  • Leave meetings without clear actions or ownership.

The result? Frustration. Repetition. Stalled progress.

EOS fixes that by creating a rhythm of open, accountable problem-solving that sticks.

Step 1: Identify

This is where most teams go wrong.

They jump straight into solutions without truly understanding what the real issue is.

In EOS, Identify means going beneath the surface. The first problem you see is rarely the real one.

Ask “Why?” several times until you get to the root cause.

Example:

  1. Issue: “We’re missing delivery deadlines.”
  2. Why? “Because production is overloaded.”
  3. Why? “Because sales promised unrealistic lead times.”
  4. Why? “Because there’s no process for reviewing capacity before quoting.”

The real issue isn’t “late deliveries” – it’s lack of process between sales & production.

Once you’ve identified that, the solution becomes clear.

Step 2: Discuss

Once you’ve identified the true issue, then & only then – you discuss it.

This isn’t about blame. It’s about finding the best answer.

The key to this step is open, honest conversation. Everyone has to feel safe to speak up, share facts, & challenge assumptions.

EOS calls this “entering the danger.” It means being brave enough to say what everyone else is thinking, even if it’s uncomfortable.

The most effective teams discuss issues from a place of curiosity, not ego.

Ask:

  • What’s really happening?
  • What’s in the way?
  • What can we change?

Stay focused – if the conversation drifts, bring it back to the core issue.

Step 3: Solve

Once you’ve discussed it fully, agree on a clear solution & move forward.

A “solve” in EOS means identifying the next action that moves the issue closer to resolution.

Sometimes that’s a new process.

Sometimes it’s a tough decision.

Sometimes it’s simply agreeing who owns what.

The point is to walk out with a clear To-Do – not another conversation.

If an issue can’t be solved immediately, park it & come back next week with fresh data.

IDS in Action

When done properly, IDS can transform how your team works.

Here’s what it looks like:

  • You spend 10 minutes identifying the true issue.
  • 20 minutes discussing openly, without politics.
  • 5 minutes agreeing on one clear next step.

It’s practical, focused, & consistent & that rhythm builds momentum week after week.

Real-World Example

I worked with a leadership team who spent months arguing about poor customer service scores.

Sales blamed operations. Operations blamed admin. Admin blamed systems.

Once we applied IDS, the truth came out.

There was no standard process for handling customer complaints. Everyone assumed someone else was doing it.

Within one week, they documented the process, assigned ownership, & the issue disappeared – permanently.

That’s what happens when you solve the root cause, not the symptom.

Common Mistakes with IDS

  • Skipping Identify. You can’t fix what you don’t truly understand.
  • Avoiding tough discussions. Without honesty, you’ll never get to real solutions.
  • Solving too soon. If the solution feels easy, you probably haven’t gone deep enough.
  • No follow-up. Every solve needs a To-Do, and every To-Do needs accountability next week.
  • Treating IDS like a debate. It’s not about being right – it’s about fixing the problem.

6 FAQs About the EOS Issues Solving Track

1. What is the EOS Issues Solving Track?

It’s a three-step framework – Identify, Discuss, Solve – that helps teams fix problems permanently instead of talking about them endlessly.

2. Where do we use IDS?

It’s part of the weekly Level 10 Meeting agenda, but can also be used any time an issue arises.

3. Why is “Identify” the most important step?

Because the first issue is rarely the real one. If you don’t find the root cause, you’ll keep solving symptoms.

4. How long should the IDS process take?

As long as it takes to solve the issue properly – but focus on one issue at a time.

5. What’s the biggest mistake teams make?

Jumping straight into discussion or solutions without clear understanding of the issue.

6. What’s the result of using IDS consistently?

Fewer repeated issues, better accountability, & a more unified team.

Final Thought

IDS isn’t complicated – but it’s powerful.

It takes discipline, honesty & consistency to make it work, but once you do, your business stops getting stuck in the same problems.

You move faster. You waste less time. You finally start solving issues for good.

Want to learn how to use IDS effectively in your business?

Email me at debra@businessaction.com.au or book a free clarity call.


Written by Debra Chantry-Taylor, FBA Accredited Family Business Advisor, Certified EOS Implementer & Founder of Business Action.

Business Action is focused on helping Entrepreneurs lead better lives, through creating a better business. We have a small team of accredited family business advisors, EOS Implementers & Leadership coaches, as well as access to a huge range of advisors through our Trusted Partners Network.

Share This