We would rather self-implement EOS than share sensitive financial and personnel information with an outsider. Is that a good reason?
Treat confidentiality as a requirement to resolve, not an automatic reason to reject outside guidance. Self-implementation avoids introducing another party to sensitive information, but it does not remove internal bias or make difficult leadership conversations easier.
Use the 90-Minute Meeting to ask what information the presenter would need during a potential engagement and why. You can discuss your concerns using general descriptions rather than disclosing names, compensation details, or sensitive records during the introduction.
Before sharing confidential material, clarify:
- What confidentiality terms would apply to the engagement?
- What information would be retained, where, and who could access it?
- Would sessions be recorded or processed through third-party tools?
- Are there relationships with competitors or other parties that require discussion?
- Which details are necessary for the work, and which can remain private?
Do not assume every Implementer uses identical agreements or information-handling practices. Review the actual arrangements, with legal or security advice where appropriate.
My recommendation is to evaluate confidentiality and implementation capability as separate questions. If an Implementer can meet your requirements, privacy alone need not rule out professional guidance. If they cannot, choose another provider or self-implement with clear internal ownership.
Whichever route you choose, leadership needs enough shared information to identify the real issues. Keeping unnecessary personal details private is sensible. Withholding facts essential to a decision can prevent both internal and external facilitators from helping.
Category: Self-Implementing vs. Hiring an Implementer