Our leadership team is highly capable and we have read the books, so we are considering self-implementing EOS®. What are the critical risks of self-implementation that we might not see from reading the material?

Question

Tyler Smith · Accepted Answer

Self-implementing EOS® comes with several critical risks, primarily stemming from the lack of objective facilitation and the inability to maintain a pure system.

Risks of Internal Facilitation

When a leadership team attempts to self-implement, someone from within the team must take on the role of facilitator. Typically, this falls to the Visionary or the Integrator. This internal facilitation creates two significant problems:

• Lost Strategic Brainpower: The person facilitating cannot fully participate in the strategic discussions. They are preoccupied with managing the clock, keeping discussions on track, and enforcing the agenda. This means you lose their valuable input and strategic brainpower in critical conversations. The role of an Integrator is demanding enough without adding meeting facilitation to the mix, as discussed in [should Integrator facilitate Level 10 Meetings](/qa/should-integrator-facilitate-level-10-meetings).
• Lack of Neutrality and Bias: An internal facilitator inherently lacks neutrality. They come with their own biases, historical context, and established political relationships within the team. This makes it incredibly difficult for them to:
• Call out team dysfunction or unproductive behaviors without it feeling like a personal attack.
• Address tough issues or conflicts head-on, as they are part of the internal dynamic.
• Push back effectively when the team avoids uncomfortable truths or personal accountability. This can be particularly challenging if team members are protective of their departments, as highlighted in [leadership team trust and healthy conflict](/qa/leadership-team-trust-healthy-conflict).

Compromising the System

A professional EOS Implementer® brings essential external authority and zero bias to the process. An outside guide can:

• Address Structural Gaps: They can push hard on structural deficiencies in your Accountability Chart, ensuring that roles are clearly defined and accountability is unambiguous. Issues such as [resolving Accountability Chart seat overlaps](/qa/resolving-accountability-chart-seat-overlaps) are much easier to tackle with an impartial arbiter.
• Insist on Robust Metrics: An Implementer will prevent you from settling for soft or subjective metrics on your Scorecard, ensuring that your team tracks quantifiable, impactful numbers. They can help you move from [lagging results to weekly leading indicators](/qa/leading-vs-lagging-scorecard-metrics).
• Force Root Cause Analysis: During IDS® (Identify, Discuss, Solve), an Implementer will ensure you address the actual root causes of issues, rather than just superficial symptoms.
• Maintain System Purity: Self-implementers often "customize" the tools to fit their comfort levels, leading to a diluted version of EOS. An Implementer ensures you run the pure system as intended. This prevents the team from abandoning the process when it becomes uncomfortable, saving months of trial and error and ensuring the full benefits of the framework are realized.