The safest first automation is rarely the biggest workflow in the company. It is the handoff that already has a clear owner, a clear failure mode, and a clear definition of done.
Start by looking for work that crosses a system boundary. A refund that needs a finance review, a support ticket that needs enrichment, or a CSV drop that needs validation usually has enough shape to automate without weeks of discovery.
What makes a good first workflow
- It happens often enough that manual work is visible.
- The input and output are already known.
- The failure path is acceptable if the workflow pauses for review.
- The team can compare automated output against a manual baseline.
Once that workflow runs cleanly, the next automation becomes easier to justify. You have logs, ownership, and a pattern the team can reuse.
What to avoid
Avoid starting with the most political workflow, the most brittle legacy process, or anything that requires every team to agree before value is visible. A narrow workflow that ships is more useful than a perfect platform plan that never reaches production.