Our head of operations has run our delivery department for ten years and keeps all of our execution processes in their head. How do we document these workflows on our exit runway without making them feel like we are trying to replace them?

Question

Tyler Smith · Accepted Answer

This is a common bottleneck. When a buyer sees a business where one key employee holds the entire operational playbook in their head, they see a massive risk. If that person leaves post-transaction, the business model breaks. You must de-risk this immediately, but you have to handle it delicately so your head of operations does not feel threatened.

To do this, use your EOS® Accountability Chart to clarify their role. Frame the documentation project not as a way to replace them, but as a path to elevate them. When a key manager is bogged down by holding every process in their head, they cannot scale. Explain that to grow their department and prepare the company for its next phase, we must document the core processes so they can delegate lower-level tasks and focus on higher-value leadership.

Have them document the 20 percent of activities that drive 80 percent of the results. Use the EOS® three-step process: Document, Simplify, and Package. Have them create simple, visual checklists or brief video walk-throughs of their daily routines.

By moving this knowledge from their head into a shared company asset, you turn a major key-person risk into an institutional asset. Buyers will pay a higher multiple because they see a repeatable system, and your head of operations gets a clearer path to promotion or a meaningful stay bonus when the transaction closes.