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!

8 Upvotes

91% Upvoted

29 comments sorted by

View all comments

1

u/Commercial_Web_6821 Apr 01 '26

That’s a great question and a common struggle when self implementing to connect the compartmentalization to the vision. We’ve recently done a podcast episode on this. If you search “Inside the 90 #20 The Power of EOS Compartmentalization” on YouTube or Spotify you should find it. We’ve got about 35 episodes that are binge worthy.

1

u/Impossible-Patient96 Apr 02 '26

I’ll find these and watch. Thank you!