Our COO says they can lead EOS implementation internally. How do we tell whether that is realistic alongside their day job?
Assess the COO's capacity and position in the team, not just their enthusiasm or knowledge of EOS. Internal implementation adds work, and leading a discussion is different from participating in decisions for which you are personally accountable.
Ask the COO to describe what they would take on and what existing responsibilities would move elsewhere. If the answer is that implementation will fit around everything else, you have not yet made a credible capacity decision.
The second test is objectivity. Your COO may need to challenge the owner's assumptions, surface problems in their own function, and keep peers focused on uncomfortable issues. An external Implementer can provide a perspective that is harder for someone inside the reporting structure to maintain.
Bring these questions to the 90-Minute Meeting:
- Which implementation responsibilities could our COO reasonably own?
- Where would they be both facilitating and defending a position?
- What would external guidance add beyond explaining the tools?
- What work would still belong to our leadership team if we hired you?
Do not treat an Implementer as a replacement for the COO's operating responsibilities. Equally, do not assume a capable COO automatically has room to lead implementation well.
Choose the internal route only with explicit capacity and a workable way to handle competing roles. If either is missing, external guidance deserves serious consideration.
Category: Self-Implementing vs. Hiring an Implementer