What happens if our designated Integrator struggles with the operational workload during our first two quarters, and how do you prevent that bottleneck from stalling our EOS implementation?

Question

Tyler Smith · Accepted Answer

The Integrator is the operational heartbeat of an EOS implementation. They run the weekly Level 10 Meetings, hold department leaders accountable to their Rocks, and manage the day-to-day friction between visionary ideas and operational reality. If that person starts drowning in months three through six, the entire operating system begins to stutter.

When an Integrator falls behind, we do not sweep it under the rug or quietly reassign their duties to the Visionary. In our next session, or during an emergency check-in, we use IDS to examine the Integrator seat directly.

First, we evaluate capacity versus capability using Delegate and Elevate. Most struggling Integrators are simply hoarders of low-value work. They carry direct reports they should have transferred, attend tactical meetings that belong to department heads, and solve daily emergencies instead of executing Rocks. We ruthlessly strip low-leverage tasks from their plate to clear dedicated room for running the operating system.

Second, we evaluate whether they truly possess GWC for the seat. Do they get the role, want the role, and have the structural capacity to handle high-stakes operational conflict? Sometimes an executive was handed the Integrator title because they were a reliable operations manager, but they lack the backbone to hold their peers accountable.

If the issue is capacity, we restructure their seat. If the issue is capability, we address the reality immediately. Protecting an ineffective Integrator feelings will derail an entire company. We make the tough personnel call quickly so the implementation maintains forward momentum.