When this work is a fit
This work fits teams where training depends on shadowing one person, routine tasks vary by employee, or a key absence exposes undocumented knowledge. Begin with a process that repeats often enough to test.
Deliverables to define in the scope
- A prioritized process inventory with a named owner and review cycle.
- Procedures containing scope, prerequisites, actions, decision rules, and completion evidence.
- A controlled home for current versions and a retirement rule for outdated instructions.
- A practical walkthrough in which a second person attempts the task and records missing information.
How implementation progresses
- Observe a real execution and capture the judgment calls as well as the normal steps.
- Draft a short procedure around the task, then have an experienced operator check accuracy.
- Test with an appropriate backup, resolve gaps, and assign ownership for future updates.
What to bring to a scoping conversation
Bring existing checklists, training notes, approved policies, access requirements, and examples of errors. Choose a subject-matter expert who has time to validate the document; writing alone cannot establish that the steps are safe or correct.
Acceptance and handover
A procedure is ready when its intended user can complete a representative task, identify when to stop, and find the exception contact. Record the version and test date so successful training is attached to the instructions actually used.
Scope boundaries
SOPs should reflect approved operating practices. Documentation work does not replace technical, safety, clinical, financial, or legal approval required for the underlying activity.
Related implementation resources
Discuss the operating problem
Elixir consulting starts at $5,000 per month, with final pricing based on scope. Bring a recent example, the current workflow, and the person who owns the result to define the appropriate implementation scope.