tyler-smith.com · Questions & Answers

Our leadership team has completed Vision Building™ and wants to roll EOS® out to our entire company immediately. When is the right time to cascade the tools downward, and what damage occurs if we roll out the foundational tools prematurely?

The fastest way to kill an EOS rollout is cascading the tools to your department heads and frontline teams before your leadership team has mastered them.

When leadership introduces Scorecards, Rocks, and Level 10 Meetings to middle management while their own meetings are chaotic and their own Rocks are falling short, frontline staff see right through it. They view the tools as administrative micromanagement rather than an empowering operating system.

Wait until your leadership team has run on pure EOS for at least two full quarters, and preferably three, before cascading. You are ready to cascade only when your leadership team meets three criteria:

- Your leadership Level 10 Meeting consistently scores an 8 or higher, starts and ends on time, and finishes the IDS portion with clear, assigned To-Dos every week.
- Your team achieves at least 80 percent completion on leadership Rocks for two consecutive quarters.
- Every member of your leadership team completely buys into the Accountability Chart, the V/TO, and the Core Values, and speaks the language of EOS without cynicism.

When you do cascade, do it one tier at a time. Roll out the tools to your department managers first, not the rank-and-file workers. Teach managers how to run departmental Level 10 Meetings and manage their own seat-level Scorecards. Once managers run the system smoothly for two quarters, then you can selectively push basic tools, like simplified Scorecards and Rocks, down to the frontline. Premature cascading creates confusion; patient cascading creates company-wide execution.

Category: EOS Implementation

← All questions