Most change initiatives fail for reasons that have nothing to do with the tools.
They fail because leadership gets excited about the solution before fully understanding the reality people are operating in every day.
I’ve lived this from the inside.
Years ago, when we decided to implement EOS internally, we did what a lot of capable leadership teams do. We read the books. We learned the tools. We got organized. We started talking about accountability, Rocks, Level 10 Meetings, scorecards.
To be clear, we didn’t skip the Vision work. We had a Vision. We talked about it often at the leadership level. What we underestimated was how much listening needed to happen alongside that work, especially outside the leadership room. We focused on defining where we were going, but we didn’t slow down enough to fully understand how people experienced where we already were.
That distinction matters. Listening isn’t separate from Vision. It’s part of it.
Not the surface-level listening where leadership assumes they already know the issues, but the kind that surfaces the workarounds people have normalized, the friction they’ve learned to live with, and the quiet assumptions about how decisions really get made.
Those things don’t disappear when you introduce a new operating system. If anything, they become more visible. Or, as we like to say in EOS, things start to get really transparent. And that’s a good thing.
As an organization gets stronger in Vision, People, and Data, the three components at the top of the EOS Model, the imperfections, impurities, obstacles, and challenges become crystal clear. But so do the opportunities. So do the ideas. So do the places where the business can grow faster and cleaner once the truth is on the table.
Frontline employees and team members outside the leadership room feel change first. Their buy-in has a lot to do with whether they understand where the organization is headed and why. When there’s a clear, shared vision and it’s actually communicated across the organization, people can see how their work connects to something bigger than their individual role. That’s where things really start to shift.
When employees understand the vision and the plan, they’re able to internalize it. They stop seeing measurables as arbitrary numbers and start seeing how what they’re accountable for drives upward to the common direction the organization is moving in. The work has context. Expectations make sense. People want to be part of it. This is where EOS, when implemented well, shines.
Vision isn’t just defined at the leadership level. It’s shared, reinforced, and lived throughout the organization so everyone is rowing in the same direction.
This isn’t about forced enthusiasm or motivational posters on the wall. It’s about alignment. To the extent that you can get everyone on the team sharing one vision and pulling together, things start to click in ways that are hard to explain. Planets align. Traction builds. Execution gets cleaner. Magic happens.
At its best, EOS isn’t just about tools. It creates a structured way to surface what’s really happening before accountability tightens and to connect people’s day-to-day work back to a shared direction.
When that step gets skipped, the tools still get rolled out. Meetings still happen. Rocks still get set. But execution feels heavier than it should. Accountability starts to feel imposed instead of shared. Momentum slows, and leadership wonders why something that looks good on paper isn’t sticking.
When people feel heard and understand where they’re headed, something changes. They engage differently. They take ownership instead of compliance.
That’s one of the biggest lessons I took away from self-implementation. The mechanics matter, but the human side matters first. Discipline without understanding creates friction. Discipline built on shared truth creates traction.
If you’re thinking about rolling out EOS or any major operating system, the most important work may not be learning the tools. It may be creating space for people to be heard and making sure everyone understands and buys into where the organization is going before you ask them to change how they work.
That step doesn’t slow change down. It speeds everything else up.
For those of you who’ve led or lived through a change initiative, what made the biggest difference in whether people truly bought in?