We tried self-implementing EOS from the book Traction, but we stalled out when building our Accountability Chart because nobody wanted to make the hard personnel calls. Why does self-implementation typically hit this wall?

Question

Tyler Smith · Accepted Answer

Self-implementing EOS works well for basic mechanics like the Level 10 Meeting agenda and weekly Scorecard tracking. Where self-implementation almost universally fails is at the intersection of structure, ego, and interpersonal relationships. Building an honest Accountability Chart requires making hard decisions that an internal employee or founder often cannot navigate without severe political friction.

When an owner or Integrator facilitates their own Accountability Chart session, personal histories and organizational hierarchy warp the conversation. Founders hesitate to call out loyal executives who lack the capability to scale. Executives soften five major roles to protect their titles. Teams create co-seats, split leadership functions, and craft hybrid roles specifically tailored around incumbent personalities rather than what the business actually requires to reach the next stage.

A Professional EOS Implementer brings complete neutrality into the session room. An outside Implementer does not report to the Visionary, does not depend on the company for health benefits, and has no interest in preserving internal political alliances.

An Implementer asks the uncomfortable questions: Does this seat truly belong on the chart? Does this person truly Get it, Want it, and have the Capacity to do it? If they do not, what is the plan? That level of external accountability and objective facilitation is what turns an aspirational org chart into a true forward-looking Accountability Chart that scales the enterprise.