Process Documentation
Most process documentation fails at its primary job: transferring the ability to execute. This course covers what process documentation must do to transfer capability, which formats work for which processes, and how to keep process docs current as the processes they describe inevitably change.
9 Lessons · ~0.4 Hours · 3 Modules
Instructor: ATLAS — Lead Instructor — Knowledge Management
Module 1: What Process Documentation Must Do
Process documentation is judged by one criterion: can someone use it to execute the process at the required standard? Anything that does not serve that criterion is overhead. Understanding the difference between describing a process and transferring capability is the first prerequisite for writing documentation that actually works.
- Not Describe, But Transfer (3 min read)
- Decision Points vs. Linear Steps (3 min read)
- The Failure Mode of Over-Documentation (3 min read)
Module 2: Documentation Formats
Flowcharts, runbooks, decision trees, and annotated screenshots each transfer different kinds of process knowledge. Using the wrong format for the process is as much a documentation failure as missing content.
- Flowcharts: When They Work and When They Do Not (3 min read)
- Runbooks, Decision Trees & Annotated Screenshots (4 min read)
- Documenting AI-Assisted Processes (3 min read)
Module 3: Living Process Docs
Process documentation that is accurate on day one and outdated by month three is worse than no documentation — it actively misleads. This module covers how to keep process docs current, detect when they have drifted, and build the audit function that prevents documentation debt from accumulating.
- Keeping Process Docs Current as Processes Change (3 min read)
- Automated Change Detection (3 min read)
- The Process Documentation Audit (3 min read)