As the Visionary founder, I am fully committed to EOS, but I am worried that my Integrator is treating the rollout as just another project on their to-do list rather than a fundamental shift in how we run the business. How do we define the Integrator's specific role in making the implementation stick?

Question

Tyler Smith · Accepted Answer

The Integrator is the ultimate owner of the operating system. While the Visionary champions the big picture, the Integrator must drive the daily and weekly adherence to the EOS tools. If the Integrator treats the rollout as a secondary project, the rest of the team will view it as a temporary fad. To make the implementation stick, the Integrator must run the weekly Level 10 Meeting with absolute discipline, ensuring it starts and ends on time. They must hold the leadership team accountable to their weekly Scorecard numbers and quarterly Rocks. When processes break down, the Integrator must point back to the Accountability Chart and the V/TO rather than stepping in to solve the problem directly. The Integrator must also ensure that the cascading of tools to the next levels of the organization happens at a sustainable pace. They must act as the primary filter, preventing operational noise from distracting the team from their Rocks. If your Integrator is struggling to own this space, you must address whether they truly GWC the seat. An EOS implementation cannot survive a passive Integrator.