How do you document a process?
Watch the work or ask the person who does it. Write each step in order, starting with a verb. Add who does the step and in which tool. Say what sets the process off and how you know it is done. Then have someone else follow the document and fix each place where they got stuck.
Document it in five steps
- Watch it or ask. Sit with the person who does the job, or have them talk you through the last time they did it.
- Write the steps in order. One action per step. Start each one with a verb: call, enter, send, check.
- Add the owner and the tool. Who does the step, and where.
- Say when it starts and when it's done. What sets the process off, and what a finished job looks like.
- Test it on someone new. Hand the document to a person who has never done the job. Fix each place where they stop to ask.
Two kinds of process documentation
A process map shows the whole process on one page. An SOP gives the instructions for one job in it. Most teams need both: the map so people can see how the work moves, and the SOPs so people can do each part.
Keeping it current
A process document goes out of date the day the work changes. Give each document one owner, keep every document in one place and change the document in the same week the work changes.