No account needed to try. Sign up to a FREE systemHUB trial for unlimited use.
Get a better result
- Name the process the way your team says it out loud. "Booking in a job" beats "Client Intake Procedure v2" and you will both know what it means.
- Say who actually does it, by role. A process with no owner is a wish, and the draft will hedge every step until you name one.
- Describe what done looks like before you describe the steps. It works backwards from there, and the steps come out in the right order.
- Do not try to cover the exceptions on the first pass. Get the normal path documented, then add the edge cases where they belong.
Now save it in systemHUB.
This gives you a first draft, which is the hardest part of any system to start. What it cannot do here is put it anywhere. In systemHUB the draft becomes a real system with an owner, a review date and a place your team already looks, which is the difference between a document you wrote and a process somebody follows.
Start free trial