Business operations
Turn observed work into a process checklist
Watch the task as it is actually done, write down what you saw, then draft the checklist from those notes. Standardizing from memory or from how the task should work produces steps nobody follows. Mark every step you saw and every step you inferred.
Task observed: [ ] Who performed it: [ ] Date(s) and number of times watched: [ ] Trigger that starts the task: [ ] Inputs needed: [ ] Action observed: [ ] Seen directly or inferred: [ ] Tool or document used: [ ] Workaround noticed: [ ] Exception seen: [ ] How it was handled: [ ] How often it appeared: [ ] Evidence the task is complete: [ ] Open questions to answer: [ ] Confirmed with: [ ] Checklist owner: [ ]
Observation versus assumption
The main risk is a tidy checklist that includes steps nobody was seen doing. Compare each step against your notes and mark any with no basis. Check whether the observed person skipped a step, added one or used a workaround that the checklist should not erase without discussion. An exception seen once may be rare or common, so record how often if you know. A step like "check it looks right" needs a visible standard before it belongs on a list.
Compare this process checklist against my observation notes. List every step, input or exception that has no support in the notes, and every workaround in the notes that the checklist left out. Label each gap as assumed or omitted and quote the line involved. Do not fill gaps yourself.
Check the draft with the people who do the work
Show the draft to the person you observed and ask what it gets wrong. Answer the open questions by watching the task again or asking, and watch a second person if possible, since habits differ. Decide who owns the finished checklist and when it will be reviewed. Keep your original notes so later changes can be traced to what was observed.