Operations ·
Replace “ask the expert” with usable operating knowledge
A system should remain understandable when its usual expert is unavailable. Start with the tasks another person would need to perform safely.
By Norwind
Document the first decision someone must make
A long reference document is not always useful during a confusing incident. Start with how to identify the system, where to find its current state and who can make a decision. Record the approved way to obtain access without putting credentials in a general document. Distinguish a routine procedure from a change that needs review by someone with deeper context.
Explain why the steps exist
A sequence of commands can become misleading when the environment changes. Add the intended outcome, the conditions under which the procedure applies and the signs that someone should stop. Include the meaning of important business records. The goal is to transfer enough understanding for a person to recognize when the instructions no longer match the situation in front of them.
Test the handoff before it is urgent
Ask another team member to follow a routine, low-risk procedure in a suitable environment. Notice where they have to ask for missing context. Improve the document from those questions and keep a named owner for future updates. Documentation is not a substitute for engineering judgment or a support arrangement. It is a way to reduce avoidable dependence on an individual and make escalation more precise when help is needed.
A practical check
- Document access procedures without exposing secrets.
- Include expected results and stop conditions.
- Have another person try a safe routine task.