We want to try self-implementing EOS after the 90-Minute Meeting. What should we put in place before we start?
Treat self-implementation as a leadership commitment with a review point, not as an informal experiment with a few management tools. Before starting, agree who will coordinate implementation, what time leaders will protect, and how you will judge whether your operating habits are improving.
The main risk is not that your team cannot understand EOS. It is that internal pressures and biases make consistent implementation harder. Someone must keep the work moving while also participating in the business decisions the system brings forward.
During the 90-Minute Meeting, ask the Implementer to explain the work your team would need to own without external guidance. Use that discussion to establish:
- An internal implementation lead with explicit responsibility and available time.
- A shared commitment to use the system consistently rather than selectively.
- A way to raise difficult issues, including issues involving the owner.
- A scheduled review of progress, obstacles, and the need for outside help.
Judge progress by behavior, not by completed templates. Are commitments clearer? Are issues being resolved rather than repeatedly discussed? Can leaders challenge assumptions without waiting for the owner to invite them?
Self-implementation can be a deliberate choice. It becomes a weak choice when nobody owns the implementation work or when the team has no agreed trigger for seeking help. Understand the Implementer's role now so that asking for support later is a practical decision, not an admission of defeat.
Category: Self-Implementing vs. Hiring an Implementer