EOS IDS Process: Why Identify, Discuss, Solve Fails Without Follow-Through

Most leadership teams talk about the same issues week after week without ever really solving them. The Entrepreneurial Operating System™ (EOS™) was designed to stop that cycle. The core of EOS is a simple, yet powerful, three-step process: Identify™, Discuss™, and Solve™. The concept is simple: state the actual issue, discuss it openly, and arrive at a specific solution before anyone walks out the door.

Teams are good at spotting issues and having focused conversations. The problem begins when the meeting is over. There's a gap between agreeing on a solution in the boardroom and actually seeing it happen on the ground. One person walks away from the meeting believing the issue is resolved. In the meantime, the people who have to implement the solution don't know what they are supposed to do, or when, or why it matters. The decision quietly dies somewhere between the whiteboard and real life. IDSTM process isn't just about reaching a decision, but about making sure that decisions actually turn into action.

The IDS Process — and the Missing 4th Step

How the EOS IDS Process Works Inside an L10 Meeting

Real progress is made in the IDS part of your weekly Level 10 meeting. You have 60 minutes, the longest part of the entire meeting, to work through your Issues List™. But you don't just attack the top of the list. You rank them first. You and your team pick the three issues that are doing the most damage right now. Whether you're running a busy clinic in Dallas or a growing tech company in Austin, time costs money. Spending it on small problems while bigger ones quietly drain your resources is a losing game.

What surprises people is the simplicity of the method itself. First, you Identify the actual issue, not the symptom. Say your leads are dropping. Don't fault the marketing team. First, ask if your front desk is actually converting calls that are coming in. Dig until you find the true source. Then you Discuss it. No wandering around, no letting the conversation go astray. Everyone is heard, but the focus is on clarity, not venting. Lastly, you Solve it. In EOS, a real solution is when the team leaves with a clear, specific action that resolves the issue for good.

If you don't have a clear next step at the end of the meeting, you haven't solved anything. You just spent an hour discussing a problem that will be on the list next week.

The 3 Steps of the EOS IDS Process

Step	What it actually demands
IDENTIFY	The actual issue, not the symptom. Dig until you find the true source.
DISCUSS	No wandering around, no letting the conversation go astray. Focus is on clarity, not venting.
SOLVE	A real solution is when the team leaves with a clear, specific action that resolves the issue for good.

If you don't have a clear next step at the end of the meeting, you haven't solved anything.

Why the EOS IDS Process Is the Most Powerful Part of EOS When Done Right

You've been there, you know that feeling when you arrive at Tuesday's meeting and the same old problems are on the agenda again from last Tuesday. IDS is designed to solve that problem. When teams use it well, they stop venting about problems and start actually solving them. Consider this: the average professional wastes over 31 hours each month in unproductive meetings. That's a total of more than 1,200 hours of wasted time in a company of 40 people.

The cost of bad meetings

The average professional wastes over 31 hours each month in unproductive meetings. That's a total of more than 1,200 hours of wasted time in a company of 40 people.

The power of IDS is that it goes beyond the surface. It doesn't simply say "what is wrong? It asks "why is this wrong? Picture how a good doctor works. They don't simply take your temperature and send you home. They find out what is causing it in the first place. IDS is similar it challenges your leadership team to be honest about what is really broken in the business, rather than what is uncomfortable to discuss.

The true value is in that honesty. When people feel safe enough to name the real problem in the room, trust grows. You no longer avoid the uncomfortable topics and begin to address them directly and clearly. That transition from avoidance to action is what EOS refers to as "Traction™. It is not magic. It's just what happens when a team finally decides to take a stand.

The Follow-Through Problem: What Happens After You "Solve" an Issue

Most teams get this wrong: marking an issue as "Solved" during an L10 meeting does not actually fix anything. It is really just a note on a paper. Everyone in the room takes a good, deep breath when that item is placed in the solved column. This peaceful feeling of relief is as if the problem just packed its bags and left on its own. That feeling, however, is a trap. Though you have made a decision, you haven't created a result. These are two completely different things.

Imagine going to the doctor. The doctor sits with you, listens to you, diagnoses the problem, and then prescribes a medication for you. But, if you get home and never take the medication, you won't be healed even though you met with a doctor.

The Doctor's Visit Decision vs Result

Your own business works along these same lines. The part we call "Solve" is basically your treatment plan. But it only has value if someone actually takes it up and does something about it after the meeting is over. If it doesn't turn into a concrete, named, high-priority To-DoTM with a real person responsible, then you haven't solved anything. What has happened is that you simply talked about how to solve it, but didn't actually solve it.

The trap

Though you have made a decision, you haven't created a result. These are two completely different things.

Why To-Dos From the EOS IDS Process Die Before the Next L10

Most of the time, your To-Dos don't fail because your team is unmotivated. They fail because real life gets in the way. You walk out of your meeting feeling focused and ready, but the moment you sit back down at your desk, the chaos starts a flood of emails, staff popping in with "just a quick one," and some unexpected problem in your office that needs your attention right now. That meeting momentum disappears fast.

How a To-Do Dies Between Two L10s

The number one mistake leaders make is writing To-Dos that are too fuzzy to act on. Something like "look into the billing issue" sounds like progress, but it isn't. There's no clear owner, no defined action, and no way to know when it's actually done. A To-Do only has a fighting chance if it's specific enough to finish within seven days. If you can't wrap it up in a week, you're not looking at a To-Do anymore you're looking at a project, and it needs to be treated differently.

The other piece people overlook is visibility. Even a well-written To-Do will get buried if you have no way of keeping it on your radar between meetings. Whatever is loudest in your day will always win your attention by default. That's just human nature. So the real question isn't just how you write your To-Dos it's how you build a simple habit or system that keeps them in front of you all week long, not just on meeting day.

Fuzzy To-Do vs Sharp To-Do

Fuzzy — will die this week	Sharp — has a fighting chance
"Look into the billing issue"	Specific enough to finish within seven days
No clear owner, no defined action, no way to know when it's done	Clear owner, defined action, knowable completion
If you can't wrap it up in a week, it's not a To-Do — it's a project	System keeps it in front of you all week long, not just on meeting day

Whatever is loudest in your day will always win your attention by default.

The IDS to Execution Gap: Decisions Made, Nothing Changes

The "Execution Gap" is simple it's the distance between what you promised to do and what you actually did. When this gap keeps showing up week after week, your team quietly loses faith in you. They start treating the IDS process like a formality, something to sit through rather than act on. That's the moment "Execution Enforcement" falls apart.

Think about it from a doctor's perspective the "Provider-Logic." A doctor writes a prescription, the patient ignores it, and things get worse. But here's the part we don't talk about enough: if that doctor sees the same patient a week later and never asks "did you take the medication?" the doctor shares some of the blame.

The same thing happens in your business. If your L10 meeting doesn't open with a hard, honest look at last week's To-Dos, you're quietly sending a message to your whole team. You're telling them that the decisions made in IDS don't really matter. That it's fine to say "yes" in the meeting room and do nothing afterward. That accountability is optional.

And once your team believes that, the entire system loses its teeth. People stop bringing real problems to IDS because they already know the outcome a decision gets made, everyone nods to it and everything goes on exactly as before.

Execution enforcement is very important if you want your team to actually sit at their desk and work. Start every meeting by checking what was supposed to have been done. Then, actually hold each person accountable.

Start every meeting here

Start every meeting by checking what was supposed to have been done. Then, actually hold each person accountable.

What Automated Follow-Through Would Look Like for IDS Action Items

Imagine a scenario where the "Solve" doesn't just sit in a static document. In an ideal world, the moment you agree on a solution, the system takes over. Automated follow-through would mean that the assigned owner receives a notification not just once, but at strategic intervals throughout the week.

Real-Time Syncing: Your To-Do would be linked directly to your scorecardTM. If the task isn't finished, the related metric stays red.

Predictive Alerts: If a task that usually takes four hours hasn't been started by Thursday afternoon, the system flags it for the leader.

Contextual Accountability: Instead of waiting until next Tuesday to find out a task wasn't done, you would know by Friday morning, allowing you to course-correct before the week is lost.

What Automated IDS Follow-Through Delivers

Capability	What it means in practice
Real-Time Syncing	Your To-Do is linked directly to your scorecard. If the task isn't finished, the related metric stays red.
Predictive Alerts	If a task that usually takes four hours hasn't been started by Thursday afternoon, the system flags it for the leader.
Contextual Accountability	Know by Friday morning, allowing you to course-correct before the week is lost.

This is the difference between "managing" and "monitoring." Automation removes the human error of forgetting and replaces it with the "enforced execution" required to actually grow a business. You don't need more meetings. What you need is for the meetings you've already had to actually result in change.

You don't need more meetings. What you need is for the meetings you've already had to actually result in change.