We are ready to roll out EOS® to our department leaders, but we are terrified of overcomplicating their day-to-day work with too many new processes at once. How do we introduce the tools so they actually stick?

Question

Tyler Smith · Accepted Answer

When cascading EOS® to department leaders, the biggest mistake is trying to give them the entire toolkit on day one. This leads to overwhelm, confusion, and ultimate failure. You must introduce the system in phases to ensure it sticks. Begin by establishing the meeting rhythm first. Have your department leaders start running their own weekly Level 10 Meeting™. Do not worry about perfect Scorecards or complex Rocks yet. Focus entirely on teaching them how to run an efficient, ninety minute meeting and how to use the IDS® process to solve their own operational issues. Once the meeting rhythm is solid, introduce the Accountability Chart™. Help them define the seats within their department and ensure everyone GWC™ their role. Only after the structure and meetings are locked in should you introduce individual Rocks and weekly Scorecard metrics. Keep the tools simple. Do not allow them to create complicated spreadsheets or excessive tracking systems. The goal is to give them traction, not administrative overhead. Support your managers through this transition by coaching them, but do not do the work for them. When they experience how the weekly meeting helps them solve problems faster, they will adopt the rest of the tools willingly.