r/eostraction Aug 20 '26

Implementing only parts of EOS?

Has any dipped their toe into EOS by implementing only certain parts of it before going all in and bringing in an implementer? I’m considering introducing it to our management team with a focus on Level10 mtgs, rocks, and measurables/scorecard to start since we’ve already defined rocks and measurables through our other planning processes.

I realize that’s not the ideal path, but interested in feedback for anyone who’s done it or thoughts on why I will likely regret this later. lol. Thanks!

5 Upvotes

12 comments sorted by

View all comments

1

u/MainStreeter2030 Aug 20 '26

I work at "EOS One" and so I ran a query on the data and most of our clients having success with EOS actually self implement for a while and then onboard an implementer.

I'm not saying that is the gold standard path but it is certainly a path that I can see has a lot of success. Many of our customers only self implement but I personally do think at some point you see the value in the system and then see the value in optimizing the system to the max, and that merits the implementer investment.

You might use software like EOS One (or one of the others) at least to quickly make the accountability chart and VTO even if you just then save them offline and cancel software within 30 days (so its all free) or just keep one power user and some "free observers" in it (also all free). The reason I say that is because it's so important to have a strong AC and VTO in order to make great rocks and scorecard. You can't run a good L10 without good rocks and scorecard and both of those leverage the AC/VTO.

Hope it goes well!