We want to roll out EOS to our managers and staff, but our leadership team is still shaky on some of the concepts. How do we determine the exact operational milestones we must achieve before cascading the tools to the rest of the company?

Question

Tyler Smith · Accepted Answer

Cascading EOS to the rest of your organization too quickly is a recipe for chaos. Before you introduce the tools to your middle managers and frontline employees, your leadership team must achieve a high level of operational consistency.

Do not start the rollout until your leadership team has met three specific milestones. First, you must have successfully run your weekly Level 10 Meetings for at least two full quarters. The meeting must start and end on time, and your team must be solving real issues using IDS, not just status reporting.

Second, your leadership team must achieve an eighty percent completion rate on their quarterly Rocks. If the leadership team cannot finish their own goals, they have no business asking their subordinates to do the same.

Third, you must have a completely agreed-upon Accountability Chart. If there is still lingering debate about who owns which seat at the leadership level, cascading the tools will only spread that confusion downward.

Once these milestones are met, introduce the tools to the next tier of management first. Let them run on the system for a quarter before cascading it further. This phased approach allows you to build a team of internal advocates who can support the rest of the organization during the transition.