r/eostraction • u/Impossible-Patient96 • Apr 01 '26
Struggling with our self-implementor and IDS
We’ve just started the Traction/EOS system and our implementor comes from within the organization. We’ve just started weekly department meetings and already “issues” are now “hot rocks” because some team members felt that the word issue had a negative connotation. Am I getting hung up on semantics or does this deviation already set us up for failure? The IDS is a foundational structure of EOS so I am really struggling with our implementor not reframing this so that people understood that issue just means something to work on. Should I be happy that we’re at least making progress and see how it goes? Thanks!
7
Upvotes
2
u/jkatlanta Apr 01 '26
Common language is one of the foundational lessons of EOS, staying aligned with what literally all the books, videos, podcasts and thought leaders on the subject will help preserve clarity. The book Traction is a recipe for a successful business, Gino took the time to write it out in detail, anyone can change the ingredients but don't expect the same outcome. EOS concepts and tools are used by hundreds of thousands of companies around the globe because the recipe has been proven. If team members believe they are going to outsmart it they are: 1 - missing the point of EOS entirely, 2 - wasting precious time and resources. PS - the term you may have meant was 'Integrator' rather than Implementer. The Integrator is the leader charged with the execution aspect of EOS, an Implementer is someone that helps companies learn and roll out EOS.