Our divisions want to self-implement EOS separately. Would one outside Implementer help us avoid creating different versions of it?
Agree on the intended operating structure before allowing each division to choose its own implementation approach. Separate efforts can create different expectations about priorities, accountability, and issue resolution, even when everyone uses the same EOS vocabulary.
Start by identifying which decisions belong to the overall leadership team and which belong within each division. Then identify where the divisions depend on one another. Those shared responsibilities are where inconsistent implementation can become particularly costly.
Use the 90-Minute Meeting to explain your structure and ask how the presenter would approach the scope. Do not assume a standard introduction will settle every question about a multi-division rollout. Ask what further discovery would be needed before recommending an implementation plan.
An external Implementer may be valuable because they can provide a common teaching approach and challenge local habits without representing one division's interests. That is an objectivity benefit, not a guarantee that one person is the right fit for every organizational structure.
My recommendation is to establish a shared leadership-level approach before authorizing separate rollouts. If you self-implement, assign clear responsibility for maintaining consistency and resolving cross-division disagreements. If you hire an Implementer, assess their relevant experience and clarify the engagement's scope.
The goal is not identical operations everywhere. It is enough consistency that leadership can make decisions, understand commitments, and address shared issues without translating between competing interpretations of EOS.
Category: Self-Implementing vs. Hiring an Implementer