We have read Traction and are trying to decide between self-implementing EOS or hiring a Professional EOS Implementer. What actually breaks down when an owner tries to run the process in-house?

Question

Tyler Smith · Accepted Answer

When an owner or internal leader attempts to self-implement EOS, two structural breakdowns happen almost immediately. First, whoever holds the marker cannot fully participate. If the Visionary or Integrator is standing at the whiteboard trying to teach the tools, manage the clock, and direct the conversation, they cannot be challenged by the rest of the room. Second, self-implementing teams almost universally modify the system to avoid existing internal landmines. They skip uncomfortable conversations about people who do not GWC their seats, they soften Rock definitions to spare feelings, and they cherry-pick tools rather than executing pure EOS.

A Professional EOS Implementer brings complete neutrality and a commitment to the proven implementation sequence. There is consistent consensus across the EOS community that there is one way to run EOS the right way. An outside Implementer introduces tools at the exact right moment, spots self-deception, and forces the team to confront root causes during IDS instead of treating surface symptoms. The cost of a professional is not just buying session facilitation; it is buying an outside forcing function that stops the leadership team from bargaining with the model. If you self-implement, you risk running a halfway version of the system that produces compliance rather than real traction. Commit fully to the process or acknowledge that your DIY approach will preserve the very dysfunctions you are trying to cure.