Three tools, three different jobs
Teams often use SOP, process map, and workflow interchangeably. They are related, but they answer different questions. Choosing the right format can make documentation much easier to maintain.
What is a process map?
A process map visually shows the sequence of activities, decisions, and handoffs from start to finish. Use one when you need to understand the whole system, uncover bottlenecks, or align teams on how work flows.
What is a standard operating procedure?
An SOP explains how to perform a repeatable task consistently. It typically includes purpose, scope, roles, prerequisites, step-by-step instructions, exceptions, and a review owner. Use an SOP when accuracy and repeatability matter.
What is a workflow?
A workflow is the operational sequence that moves work between people, systems, and states. It may be manual, automated, or hybrid. A workflow definition can include triggers, assignment rules, status changes, and notifications.
A practical example
For employee onboarding, a process map shows the journey from accepted offer to completed onboarding. SOPs explain tasks such as account provisioning or document verification. The workflow defines who receives each task and what triggers the next action.
How to decide what to create first
If nobody agrees on the sequence, start with a process map. If people know the sequence but execute tasks inconsistently, write SOPs. If work gets stuck between steps, design the workflow and its handoffs.
Keep documentation connected
Link each SOP to the relevant process step and keep ownership and revision dates visible. Documentation should be a usable system, not a folder of disconnected files.
Need help improving a workflow?
We help growing teams map, redesign, and organize business processes with practical, usable deliverables.
Discuss your project →