The procedure is documented, yet the team still asks the experienced colleague how to do the task. A useful standard operating procedure explains the trigger, required inputs, steps, decisions, exceptions and completion checks at the point of work. Write it for the person performing the task, not for a folder nobody opens.
Photo by Jakub Żerdzicki on Unsplash.
Observe the real task first
Ask someone to demonstrate a recent case using the actual tools. Note where they rely on memory, choose between versions or use a workaround. Settle unnecessary steps and unclear ownership before describing them as the approved method.
Use this compact SOP record
Purpose, scope and intended user.
Trigger and prerequisites.
Required records, templates and access.
Steps with visible completion checks.
Decision rules and exceptions.
Escalation and backup owner.
Maintenance owner and revision date.
Add screenshots where a visual instruction removes ambiguity, but avoid recording passwords or confidential client information. Link to the authoritative template instead of embedding another copy that can become stale.
Test with someone unfamiliar with the task
In an illustrative billing-preparation task, the instruction says “check the client details”. The test user cannot tell which record controls the billing address. Replace the phrase with the named record, required fields and route for conflicting details. Keep payment approval outside the procedure unless the relevant authority is explicitly defined.
Ask the test user to complete a normal case without prompts from the author. Then introduce a missing input. Note the exact step where they stop, guess or leave the instruction to ask someone else. Those observations tell you what to revise. A document can be accurate yet still omit the context a new user needs.
Maintain the instruction where work happens
Related guidance: practical process-mapping guide.
Give users a simple way to report an unclear step. Review the SOP after a process or system change, and remove obsolete versions from normal use. A current owner matters more than a long document history nobody maintains. Hili Consulting can help turn undocumented work into procedures the team can follow and improve.
