How Do I Document a Process That Lives in One Person's Head?
When a critical process depends on one experienced employee, the business is carrying continuity risk even when that employee is excellent at the work.
Document the decisions and exceptions, not just the happy-path steps.
A useful SOP begins with observation and structured interviews. Ask the person who knows the work to demonstrate a real example, explain what changes from case to case, and identify the judgment calls that are invisible to everyone else.
The document should then be tested by someone who did not create it. If that person cannot follow the process or know when to escalate, the SOP is not finished.
Warning signs of undocumented knowledge
- Training consists mostly of shadowing one employee.
- Vacation, illness, or turnover creates immediate operating stress.
- Old procedures exist but no longer match daily work.
- Employees know the steps but disagree about exceptions or quality standards.
- Managers repeatedly answer the same process questions.
What a usable SOP includes
- Purpose, scope, trigger, and expected outcome.
- Required inputs, systems, records, and approvals.
- Steps written in the order the work is performed.
- Decision points, common exceptions, and escalation rules.
- Acceptance criteria, evidence to retain, and a named document owner.
How to keep documentation alive
- Assign one owner who can approve updates.
- Review the SOP after failures, major system changes, or role changes.
- Place checklists where the work occurs instead of burying them in a shared drive.
- Keep version and approval dates visible.
- Remove obsolete copies so employees are not choosing between conflicting instructions.
Where the two packages fit
This is a strong fit when the work already exists and the priority is to capture it accurately, reduce key-person dependency, and make training and execution more consistent.
Best when the work stays within one known workflow, function, or small stakeholder group.
Best when the workflow crosses teams, systems, handoffs, or meaningful quality risks.
Both are focused 30-day remote engagements. Final scope, assumptions, exclusions, timing, and acceptance criteria are documented before work begins.
Review package detailsWhy this is not generic advice
The engagement is grounded in real workflow examples, operating records, interviews, and the decisions employees make while doing the work. The output is specific to the selected process: current state, ownership, documentation, controls, measures, and a 90-day execution sequence.
Daniel Woodmansee's background includes more than four decades in manufacturing and operations, fourteen years in quality control management, and founder-level direction of the live PauseThePitch production system.
Related owner questions
Start with the workflow
A useful first message identifies the workflow, what keeps going wrong, who owns the decision, what has already been tried, and why the problem matters now.
Daniel Woodmansee · Panama City, Florida · Remote engagements across the United States