What is the right way to roll out EOS tools to departmental teams without overwhelming middle managers who are already stretched thin?

Question

Tyler Smith · Accepted Answer

The most common rollout mistake is forcing company-wide adoption too quickly. Do not roll out EOS tools to departmental teams until the senior leadership team has run on the system for at least two full quarters. If your senior leaders cannot run a crisp Level 10 Meeting or hit an 80 percent Rock completion rate, they cannot teach it to their direct reports.

When you are ready to cascade, do not dump the entire system on department managers at once. Roll it out in three distinct phases.

Phase one is meeting cadence and accountability. Teach your department heads how to run their own weekly Level 10 Meeting with their teams. Let them build a simple departmental Issues List and run IDS on tactical operational problems for 30 to 60 days. This immediately improves departmental communication and eliminates unnecessary ad-hoc meetings.

Phase two is departmental Scorecards. Work with the manager to identify five to fifteen activity-based, weekly leading indicators that show whether their department is winning or losing. Do not burden frontline staff with complex financial metrics; give them clear numbers they directly control.

Phase three is departmental Rocks. Once their Level 10 Meeting and Scorecard are functioning smoothly, guide managers through setting their first round of departmental Rocks aligned with company priorities. Staging the rollout this way prevents tool fatigue and lets middle managers feel the operational relief of EOS before asking them to take on strategic execution.