What is the exact division of responsibility between our internal Integrator and our Professional EOS Implementer during the first year of rollout?

Question

Tyler Smith · Accepted Answer

The Professional EOS Implementer and the internal Integrator play complementary but completely separate roles in running the operating system. Confusing these responsibilities slows down adoption and creates friction in the leadership room.

The Implementer is an outside teacher, facilitator, and coach. Their job is to teach the EOS tools cleanly, facilitate the off-site session days, challenge the leadership team on tough decisions, and hold the mirror up when artificial harmony or avoidance creeps in. The Implementer owns the process inside the session room, introduces tools at the proper cadence, and ensures the team does not drift from pure EOS.

The Integrator owns execution outside the session room. Between quarterly sessions, the Integrator runs the business day to day. They facilitate the weekly Level 10 Meeting, ensure the Scorecard is updated every week, drive accountability on quarterly Rocks, and manage the leadership team to their seats on the Accountability Chart.

The Implementer never manages your people, and the Integrator should never try to facilitate their own quarterly or annual planning sessions. When an Integrator attempts to act as the Implementer, they lose their ability to participate fully as an executive, and team members often view their facilitation as biased. Let the Implementer handle session mastery so the Integrator can focus entirely on operational traction.