Write a Practical SOP with AI and a Real Walkthrough
A standard operating procedure should help another person complete a repeatable task. AI can organise rough notes, but the procedure needs a real walkthrough to expose missing steps. Start with the trigger, required access and expected result, then document what to do when the normal path fails.
Why it matters
Experts skip familiar details without noticing. A new person may need to know which account to use, what a valid input looks like and where to stop if a required condition is missing.
A practical workflow
- Perform the task and capture the actual sequence, including prerequisites, decisions and checks along the way.
- Ask AI to organise the notes into purpose, inputs, steps, exceptions and completion criteria without inventing missing details.
- Give the draft to someone unfamiliar with the process and observe where they need clarification.
- Revise the procedure, assign an owner and record when it should be reviewed after tools or rules change.
An example
For publishing an event page, include where approved details come from, who checks dates and links, and how to confirm the page is live. 'Upload the content' is not enough if the reader cannot identify the approved version or final verification step.
A mistake to avoid
Do not include passwords, recovery codes or other secrets in the procedure. Describe how authorised people obtain access through the proper system. Screenshots also need review when interfaces change.
Try it and check the result
Have another person complete the task using only the SOP in an appropriate test setting. Record each interruption and unexpected decision, then update the document until the important gaps are resolved.
Reference and further reading
Google's prompt design strategies.
The workflows and examples in this guide are illustrative. Product controls and availability can change; check the linked official guidance for your setup.
Continue with Turn Meeting Notes into Action Items People Can Trust or explore all blog topics.