I was sitting in a quarterly session with a construction company a while back. The leadership team was sharp, engaged, and genuinely working through the EOS model. Their Scorecard was solid. Their Rocks were on track. By any measure, they were executing.
And yet, somewhere out on the job sites, the crews were frustrated. The same problems kept showing up: scheduling gaps, wrong information, breakdowns between the field and the office. The leadership team was aware of these things. They had Issues on the list. They were IDSing. They were moving,
So why did it feel, to the people doing the work, like nothing ever changed?
I didn’t have a quick fix for them. What I did have was a clearer picture of the problem, and it’s one I see in a lot of companies running EOS.
The Gap Between Solving and Empowering
Here’s what I’ve come to understand: the goal isn’t to solve your employees’ problems for them. It’s to give them the tools and support to solve their problems themselves.
When employees raise an issue, formally or informally, and nothing visibly changes, they draw a conclusion: my input doesn’t matter here. Over time, that conclusion hardens. They stop raising issues. They disengage. And eventually, the talented ones leave. When they do, exit interviews often surface a version of the same phrase: “I just felt like nothing ever changed.”
The cruel irony is that plenty may have been changing. But it wasn’t where they were looking, or they couldn’t see the connection between what they raised and what got resolved.
This is a structural problem, not a cultural one. And EOS gives us a structural answer, though it takes time and intentional work to get there.
Give Your People the Ability to IDS
The Level 10 Meeting is built around a powerful idea: the people closest to a problem are often best positioned to solve it. IDS (Identify, Discuss, Solve) isn’t just a leadership tool. It’s a framework for giving anyone in your organization the agency to own an issue rather than just complain about it.
Most companies running EOS do IDS at the leadership level. Fewer extend it to their teams. That’s the gap.
When you teach IDS to your teams and build cascading meetings into your operating system, you’re doing a few things at once:
You’re creating a channel. Instead of issues dying in someone’s inbox or evaporating after a one-on-one, there’s a predictable, recurring forum where problems surface and get solved.
You’re assigning ownership. In EOS, issues don’t belong to whoever is most frustrated. They belong to whoever is accountable to solve them. Cascading meetings make it clear where an issue should live and who should drive it.
You’re building visibility. Employees can see their issues move. They know when something is escalated. They know when it is resolved. They don’t have to wonder if anyone heard them.
None of this happens overnight. Building a healthy cascading meeting structure takes quarters, not weeks. But the direction matters, and so does the signal you send by starting.
The Real Fix Is Structural
If your employees are saying “nothing ever changes around here,” resist the urge to respond with messaging or surveys. That’s not the fix. The root cause is almost always structural: there’s no reliable system for issues to surface, get owned, and get resolved in a way that’s visible to the people who raised them.
The answer isn’t to talk more. The answer is to build the right meeting structure. Cascade your L10s. Teach IDS across the organization. Give your people the framework to bring issues forward and watch them move.
It won’t happen fast. But when employees start to see their fingerprints on solved problems, “nothing ever changes” slowly becomes “we actually fix things here.”
I help leadership teams get what they want from their businesses. If your team is stuck in the same issues meeting after meeting, let’s talk.