We have an operations manager whose tribal knowledge keeps fulfillment running, but they resist documenting their methods. How do we eliminate this key-person risk without alienating them?

Question

Tyler Smith · Accepted Answer

Key-person risk in operations directly erodes enterprise value. When critical knowledge lives exclusively in one employee's head, buyers see a catastrophic single point of failure and will protect themselves by withholding cash, demanding hefty earnouts, or discounting their initial valuation.

To resolve this without creating friction, change the narrative around documentation. When an owner asks an operations leader to document everything they do, the employee often fears they are being made redundant or prepared for termination. Instead, frame process capture as an investment in expanding their personal capacity and supporting company scale.

Begin by evaluating their seat on the Accountability Chart using the EOS People Component. Clarify their primary roles, emphasizing that developing repeatable systems and mentoring subordinates are explicit expectations of their seat. Explain that documenting their workflows allows them to delegate low-value tactical tasks so they can focus on high-impact initiatives they actually enjoy.

Pair this leader with a technical writer or an operations associate tasked with recording their daily routines, capturing screen recordings of complex software tasks, and converting those inputs into simplified standard operating procedures. Integrate AI transcription and process-mapping tools to minimize the administrative burden on the manager.

Once documented, test whether other team members can execute the workflow without asking questions. By embedding this into your core process documentation, you institutionalize proprietary operational knowledge, protect fulfillment, and eliminate an existential deal risk.