Guide 03
Automate a Workflow
Most first automation projects are chosen on enthusiasm and judged on memory. This is the order that produces a number you can defend.
Independent guidance from Synergy. ISO/IEC 27001 and ISO 22301 are published by ISO/IEC, which has no affiliation with Synergy and has not reviewed this material. Always work from the published text of the standard.
This guide is deliberately not about tools. Which platform you use is a decision that comes after you know what the work costs, how often it happens, and what happens when it goes wrong. Choosing the tool first is the most reliable way to automate the wrong thing well.
It is also not about AI in particular. Several of these workflows are better served by an ordinary script or a form than by a model — and step 3 is where you find that out, before you have spent anything.
- Map the work — Before you can automate a task, you have to see it — and most of it is invisible because nobody wrote it down.
- Measure what it costs today — You cannot claim a saving you never measured. This step is boring and it is the one that makes the business case real.
- Choose the first workflow — The best first automation is not the biggest one. It is the one that can fail safely.
- Implement small — Ship the narrow version, on real inputs, with a human checking everything. Expand afterwards.
- Measure the gain and decide — Compare against the baseline honestly, including what the automation itself now costs.