Can we self-implement EOS and pay an Implementer only when we get stuck?
Ask about that arrangement directly, but do not assume every EOS Implementer offers occasional troubleshooting or that it provides the same support as a structured engagement. Availability, scope, and working expectations need to be confirmed with the individual provider.
Understanding the role of an external Implementer is valuable even if you intend to lead implementation internally. It helps you recognize when the team needs perspective or guidance that it cannot readily provide for itself.
The difficulty with a help-only-when-stuck approach is deciding when you are stuck. Internal teams may normalize recurring problems or ask for help with a tool when the deeper issue is accountability, leadership alignment, or inconsistent use of the system.
During the 90-Minute Meeting, explain that you are considering an internally led approach. Ask:
- Do you offer support for self-implementing teams?
- What assessment would you need before advising us?
- What would be included and excluded?
- When would you recommend a more structured engagement instead?
Keep responsibility clear. If your team leads implementation, someone internally must maintain the work and identify when outside help is needed.
A limited-support arrangement may be worth exploring where it is actually offered. Do not use it as a way to avoid committing leadership time, or assume occasional advice can compensate for persistent internal resistance to the system.
Category: Self-Implementing vs. Hiring an Implementer