Every business has someone who knows how things really work. They know which vendor answers after hours, why one customer receives a different invoice, where the spare key is kept, and which step in the official procedure should never be followed literally. That person is valuable. The dependence built around that person is not.
Leaders often mistake institutional knowledge for employee excellence. The employee is praised for being indispensable, while the organization avoids asking why ordinary work cannot continue without private memory, personal relationships, and improvised judgment. The risk remains invisible until the person takes vacation, accepts another job, becomes ill, or is promoted away from the work. Then a reliable process suddenly becomes a series of unanswered questions.
Documentation alone does not solve the problem. A thick procedure manual can be as useless as no manual if it describes the ideal process rather than the real one. Useful process knowledge includes triggers, decisions, exceptions, handoffs, evidence, and escalation. It explains not only what happens, but what changes when the normal path fails. The people doing the work should be able to recognize themselves in it.
Start with a dependency interview, not a request to write everything down. Ask the key employee what people contact them about, which decisions wait for them, what they check before trusting the system, and which failures they prevent without reporting. Those answers reveal the real control points. Observe the work as it happens, because experienced employees often perform important checks so automatically that they no longer describe them as steps.
Next, decide what should be standardized and what still requires judgment. A password location, approval threshold, vendor contact, or closing checklist should not depend on memory. A complicated customer recovery or unusual safety decision may still require expertise. The goal is not to reduce capable people to scripts. It is to reserve their experience for situations that deserve it.
Then test the process without the expert in the room. Give a trained colleague a realistic scenario and watch where the work stops. Missing information, ambiguous ownership, inaccessible files, and undocumented exceptions will appear quickly. Correct those gaps and repeat the test. A process is not transferred when a document exists. It is transferred when another qualified person can produce a reliable result.
An indispensable employee should be indispensable because of the value they create next, not because the business cannot reproduce what they already know. Capturing operating knowledge protects continuity, improves training, and gives experienced people room to solve larger problems. If one person knows how everything works, celebrate the person. Then fix the failure point.
Sources
• Ready.gov, “Business Continuity Planning Suite”: https://www.ready.gov/business-continuity-planning-suite
• National Institute of Standards and Technology, “Contingency Planning Guide for Federal Information Systems,” May 2010: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf
• Project Management Institute, “Process Groups: A Practice Guide,” November 2022: https://www.pmi.org/es-es/standards/process-groups
Add comment
Comments