As the Visionary, I drove our decision to implement EOS, but my Integrator is hesitant to run the day-to-day discipline of the tools. How do we establish the right division of ownership?

Question

Tyler Smith · Accepted Answer

This dynamic is common. Visionaries are naturally drawn to the conceptual clarity and big-picture potential of EOS, so they initiate the process. However, if the Visionary continues to direct the Level 10 Meeting, chase Scorecard updates, and track weekly to-dos, the entire implementation will eventually break down.

By definition, the Integrator seat owns the execution, cadence, and operational management of the business. The Integrator is the glue holding the leadership team accountable to the operating system. If your Integrator is hesitant, you must first identify why. Often, the Integrator hesitates because the Visionary continues to cut in, change priorities mid-week, or run sidebar conversations that undermine the system.

To resolve this, schedule a Same Page meeting between the Visionary and Integrator. Establish clear lane boundaries. The Visionary must formally hand over the ownership of the EOS execution rhythm to the Integrator and step back into a participant role during Level 10 Meetings.

The Integrator must step up and own the pulse: enforcing meeting start times, driving IDS, demanding Scorecard updates, and managing quarterly Rock tracking. If the Integrator understands the system but refuses to enforce accountability with peers, evaluate whether they truly GWC the Integrator seat. An Integrator who will not hold the team accountable cannot successfully execute the operating system.