Step one: write down what actually happens
Most documented processes describe intentions. Useful ones describe reality, including the workarounds people invented because the official path was too slow.
The fastest way to get this right is to follow one real job from first contact to final payment and write down every touch, including the ones that felt trivial.
Give every step an owner and a definition of done
Work stalls at ambiguity. If two people could plausibly be responsible for scheduling, it will sometimes be done twice and sometimes not at all.
"Done" needs to be observable. "Estimate sent" is observable. "Estimate handled" is not.
Remove before you optimize
- Delete steps that only exist to relay information.
- Merge approvals that always produce the same answer.
- Replace recurring decisions with defaults.
- Automate only what remains after the removals.
How do you know it worked?
Two signals: the same work now takes fewer touches, and someone who was not involved in designing the workflow can run it correctly on their first attempt.
If the process only works when the owner is watching, it is still a habit rather than a workflow.