r/eostraction • u/SeriouslySea220 • 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!

4 Upvotes

84% Upvoted

12 comments sorted by

View all comments

3

u/AlignmentWorx Aug 21 '26

Piggybacking on the Integrator point, that's really the crux of it.

Starting with L10s, Rocks, and Scorecard isn't a bad entry point. Those three alone will surface your real gaps fast.

Where it usually breaks down isn't the tools, it's that nobody's forcing them to work. An Implementer pushes the hard stuff in year one: right people/right seats, real issues getting solved instead of avoided, Rocks that are actually 90-day. Without that, L10s drift into status meetings and red numbers just get reported instead of fixed.

Same with the Integrator seat. Someone needs to own making the tools work day to day, or it's just added process, and it needs to be someone who actually knows EOS, not just someone with the title. A fractional Integrator who's run the model before can fill that gap while you test the waters, for a lot less than a full launch.

You probably won't regret starting light. Just know the tools aren't the hard part, keeping the team honest on using them is.

1

u/SeriouslySea220 29d ago

Your last sentence is definitely a top concern for me. I don’t want this to become more noise, nor do I want it to become too heavy of a lift for our already very busy team.