Practical automation
When a workflow is ready for automation—and when it is not
Start with clear rules, reliable information, a named owner and a result you can verify. Keep a way to pause and recover.
October 3, 2026 · 3 min read
- Clear rule?
- Testable result?
- Safe recovery?
- Supervised pilot
If a step is missing, pause and verify before continuing.
Look for a small, repeatable task
Consider a pilot when the trigger, inputs and expected result are clear. An internal reminder to follow up on a sent quote is one possible example: it needs a current quote status, a due date and an owner. It should stop when a reply or decision makes it unnecessary. It is not permission to send an automatic message to the customer.
Stabilize the part you want to automate
If people disagree about a rule or the records conflict, resolve that issue before automating the affected step. A shared register and a clear review rule may be enough. A workflow can still contain judgement: automate only the repeatable part and route the exceptions to a person. Record current effort and errors over a stated period, including review time, so the pilot has a useful baseline.
Test both the normal and failed paths
With fictional records, try missing information, a repeated request, expired access and an unavailable service. Define how an exception is shown, who handles it and how to retry without repeating an action. During the pilot, require human approval before sending messages or changing customer records. Pause if the result cannot be confirmed; investigate before trying again.
Agree on access, recovery and a review date
Check the information each tool needs and its access, retention and sharing settings before using real records. Name someone who can pause the automation. Document the manual fallback and how to reconcile work done during an interruption. At the agreed review date, compare completed work, exceptions and total effort with the baseline. Keep, adjust or stop the pilot based on that evidence; do not treat estimated time saved as guaranteed cash savings.
Try this: name the task’s owner, expected result, exception route, stop procedure and review date. If one is missing, start there.
A practical checklist to adapt to your workflow. Examples are fictional.
General educational guidance; not a substitute for a project-specific privacy, security or legal review.