Here’s how it started for me: Over 20 years ago, I joined a scrappy New Orleans software company as a self-taught programmer. Just the founder and me…grinding it out, trying to build something. As the company grew, so did my role. I went from writing code to wearing pretty much every hat imaginable – sales, operations, eventually a seat on the leadership team.
The founder and I developed this rhythm. He’d dream big and see possibilities everywhere. I’d figure out how to actually make those dreams happen and keep the trains running. We didn’t have words for it at the time, but we were living that Visionary/Integrator dynamic before we knew it was a thing.
Then we both read Traction®. And it was like someone had written down exactly what we’d been trying to figure out on our own. We got excited. We got the leadership team excited. And we decided: let’s do this. Let’s implement EOS ourselves.
And here’s the thing, it IS doable. EOS even offers training specifically for self-implementation because they know capable leadership teams can make it work. We made progress. We learned a lot. We got value from the process.
But that experience taught me things about what EOS really requires that I wouldn’t have understood any other way. Now I’m a professional EOS Implementer, and when companies are weighing their options, I find myself sharing these lessons, not as reasons to avoid self-implementation, but as factors to consider beyond just the initial cost difference.
Lesson One: Visionaries Can’t Be in Two Places at Once
When we decided to self-implement, the responsibility for learning all the tools, facilitating sessions, and keeping everyone accountable got split between the Visionary and other leadership team members. That meant our Visionary, the person who should have been thinking about where the company was headed, what new opportunities we should pursue, and what the competitive landscape looked like in six months, was down in the weeds trying to figure out if we were running Level 10 Meetings correctly and whether we’d filled out the Accountability Chart the right way.
Visionaries operate best at 30,000 feet. That’s not a cliche, it’s how their brains work. When they’re also implementing the operating system, they’re flying the plane and rebuilding the engine simultaneously. They can do it. But there’s a cost to what doesn’t get their attention while they’re focused on implementation.
The question isn’t whether self-implementation is possible. It’s whether the opportunity cost of your Visionary’s focus during that process is worth the initial savings. And for Integrators? We already have full plates. Adding “figure out how to properly implement an entire operating system/framework” is adding a major initiative to an already full workload.
Lesson Two: The Temptation to Make It “Your Way”
Self-implementation creates an interesting challenge. Some EOS tools feel natural and easy, so they get adopted quickly. Others feel uncomfortable or seem like they don’t quite fit, so they get adjusted. Or skipped. Or bumped to next quarter.
We definitely fell into this pattern. The tools that aligned with what we were already good at? We ran with those. The ones that pushed us out of our comfort zone or required difficult conversations? Those somehow kept getting postponed.
The thing is, EOS works as a system. Each piece supports the others. When teams cherry-pick, even unintentionally, they’re implementing a version that gets customized along the way. The power of a proven system that’s worked for thousands of companies gets diluted.
Companies often say “We tried EOS but it didn’t really work for us.” Then the real story emerges: they implemented about 60% of it, skipped the hard parts, and wondered why they didn’t get the full results. It’s like making gumbo but leaving out the roux because it seems time-consuming. Sure, there’s something warm in a bowl at the end, but it’s not gumbo!
When there’s an experienced implementer guiding the process, they help teams push through the uncomfortable parts and implement the full system. That’s harder to maintain when everyone’s figuring it out together.
Lesson Three: The Unbiased Voice in the Room
Here’s something subtle but significant that we experienced: when everyone facilitating and driving EOS is also part of the leadership team, there’s no truly neutral voice in the room. It’s not about trust…our team trusted each other. But when the people guiding the process are the same people working through the issues, it changes the dynamic.
Team members are less likely to speak up about certain issues when they know the person facilitating has their own stake in the outcome. The tough conversations that need to happen can get softer or avoided altogether. Not because anyone has bad intentions, but because everyone in the room has history, relationships, and their own perspectives on the business.
A neutral third party brings something fundamentally different to the table. They don’t have a dog in the fight. They’re not trying to prove their idea was right or protect their area or navigate internal politics. They’re simply there to help coach the leadership team in working better together to get the most out of EOS.
The level of team buy-in that comes with a neutral guide is qualitatively different. When people know the person guiding the process doesn’t have a hidden agenda or a vested interest in any particular outcome, they engage differently. They speak more openly. They push harder on the tough issues. And that openness is what makes EOS work at its full potential.
Lesson Four: Momentum Is Easy to Lose
The first few months of our self-implementation went great. Everyone was excited. Quarterly meetings were scheduled. We were tracking Rocks, running Level 10s.
Then someone had a family emergency and we rescheduled. Then Q3 got crazy busy and we postponed our planning session. Then we realized we’d been so focused on hitting our numbers that we hadn’t really addressed that underlying issue with the Accountability Chart. Six months went by and the momentum had shifted. We were still using some of the tools, but that disciplined cadence? That accountability? It had gotten looser.
This is where the consistency of having someone outside the business makes a real difference. When sessions are scheduled with a professional implementer, those dates hold different weight. They don’t get rescheduled because everyone’s busy. Teams are busy because they’re growing, which is exactly why those sessions matter. An implementer holds leadership accountable to the process in a way that’s nearly impossible to maintain internally when competing priorities arise.
What This Really Comes Down To
Self-implementation absolutely works for some companies. EOS supports it, trains for it, and plenty of teams make real progress with that approach.
But here’s what I wish someone had helped us think through before we made our decision: the real cost isn’t just the implementer fees. It’s what else could have happened with that time and focus. It’s the Traction we might have gained faster. It’s the full power of the system versus the partial version we ended up with.
We made our decision based primarily on cost. Looking back, that shouldn’t have been the primary factor. The questions that matter more: Where does leadership’s time create the most value? How important is maintaining momentum through the implementation process? Will the team benefit from a truly neutral voice? Does the organization have the discipline to implement the full system without someone pushing through the uncomfortable parts?
Many companies that now run on EOS started with self-implementation. Some made it work. Others realized after six months or a year that they weren’t getting the Traction they’d hoped for, and that’s when they brought in help. The most common reflection? They wish they’d weighed these factors more heavily in the initial decision.
Where This Leaves Things
The conversation about how to approach EOS implementation isn’t about one way being right and another being wrong. It’s about understanding what the process really requires and making an informed decision based on more than just the initial cost difference.
I’ve been on both sides of this experience. I’ve lived through integrating EOS from the inside, with all its challenges and wins. Now I work with companies who’ve chosen to bring in experienced guidance. Both paths taught me what really matters in making this work.
If your team is weighing these options, the decision deserves more consideration than just comparing price tags. Sometimes it helps to talk through these factors with someone who’s walked both paths.
About Me
As a Professional EOS® Implementer, I serve as a teacher, coach, and facilitator, helping business leaders transform their companies through the Entrepreneurial Operating System®.
Helping leadership teams gain clarity and Traction is not just something I do. It is the work I am built for. And it brings me immense joy to help entrepreneurial companies run a better business and live a better life.