As an Implementer, I get this question from time to time. I get it. I really do. I'm naturally a Visionary and I'm always looking to improve things. I've also seen companies who just want to do it 'their way' or use their language.
Simply put, running EOS purely is in your best interest.
When you read that Gino and others have been testing, iterating, and turned every lever, it's absolutely true. There is immense value in the testing and iteration phase.
What we can do from those who came before us is to learn and not make the same mistake.
That said, I know there are always new theories and ways of doing things. But, that's not what EOS is all about. The problem isn't that you haven't found that magic pill yet, the problem is that most companies have too many systems, conflicting processes, and an extreme lack of clarity, accountability, and execution.
So, when a company asks if we should run EOS purely, my answer is yes. Don't make it harder than it needs to be. Don't confuse your people. Don't confuse yourself. It works. Thousands have come before you to prove that.
Once your foundation is rock solid and you want to test some new theories, hey, you've earned that right, if you want. But, if you aren't gaining consistent traction, if you don't have true accountability, if you have people issues, if you don't do anything with your metrics, and if you're not enjoying your work and your life... give yourself the gift of choosing one system and implementing it well.
Our culture today is always looking for the next thing. We have an app for everything. I don't mind that in certain cases. But, when it comes to your business, your people, and your life - it's too important to mess around and go after shiny objects. I say this from deep down experience in making those mistakes myself. Stick with EOS purely. Make that commitment. It's a gift that will keep on giving.
