To document a process: name the trigger and the finished result, watch the work happen once, list every step in order, record the tools and decisions at each step, write it in plain instructions, have someone else run it cold, then assign an owner and a review date. A usable process document takes about 90 minutes, not a week.
The seven steps
- Define the trigger and the outcome. Start with what kicks the process off and what "done" looks like. Everything between those two points is the process.
- Watch it happen once. Do not interview from memory. People describe the version they intend to run, not the one they run.
- List the steps in order. One action per line, starting with a verb.
- Record tools, inputs and decision points. Note where the work branches and what determines each branch.
- Write it for a competent stranger. Assume the reader is capable but new. Avoid internal shorthand unless you define it.
- Test it cold. Someone who has never run the process follows it without help. Every question they ask is a gap to fix.
- Assign an owner and a review date. No owner means no maintenance, and an unmaintained document is worse than none.
The template structure
| Section | What goes in it |
|---|---|
| Purpose | One sentence on why this process exists |
| Trigger | The event that starts it |
| Owner | Named role, not a person name |
| Steps | Numbered actions with tools and links |
| Decisions | If X then Y branches |
| Definition of done | The observable result |
| Last reviewed | Date and reviewer |
What to document first
Start with the processes that are frequent, costly when wrong, or currently trapped in one person head. Client onboarding, monthly reporting, and handovers between teams almost always qualify.
Common mistakes
- Documenting the ideal process instead of the real one.
- Writing paragraphs where a checklist would do.
- Burying documents in a drive nobody opens during the work.
- Skipping the cold test, which is the only real proof of quality.
Frequently asked questions
How detailed should a process document be?
Detailed enough that a competent new team member can complete it without asking a question, and no more. If a step is obvious to anyone in the role, compress it.
What is the difference between a process document and an SOP?
A process document maps how work flows from trigger to outcome. An SOP is the standardised instruction set for performing one part of that flow. Map first, then write the SOPs for the steps that matter.
How long does it take to document one process?
About 90 minutes for a straightforward process: 30 minutes observing, 40 drafting, 20 testing. Complex processes with many branches take a half day.
Where should process documents live?
Wherever the work already happens. Documentation stored away from the tools people use daily gets abandoned within weeks.
Need this done across the business? Our Operations Management service builds and maintains the documentation, and free resources include the health check we run first. Or book a strategy call.