What to automate first: finding the workflow worth fixing

Signs a workflow is ready for automation

Not every manual process deserves a system. The ones worth attention usually show several of the same signs.

• The same request or task comes round again and again.
• Information is copied by hand between a spreadsheet, an inbox and another system.
• People spend time chasing approvals or asking where something has got to.
• The process lives in one person’s head and slows down when they are away.
• Nobody can easily say how many items are in progress or where they are stuck.

Map one real example from start to finish

Pick a recent, real case and walk through it with the people who handled it. Note what triggered it, who was involved, each step, which systems were touched and how long it waited between steps.

Pay particular attention to the exceptions: the request that arrived incomplete, the approver who was on leave, the case that did not fit the form. A map of the tidy version of a process is easy to draw and not much use. The awkward cases are where time is lost, and they decide whether a new tool survives real work.

Find where the work stalls

With the map in front of you, look for the places where work waits or information goes missing. They are often handoffs: one person finishes and the next does not know it is their turn, or receives only part of what they need.

Fixing a single handoff can do more than automating every step on either side of it.

Start with one path and one team

Resist the urge to automate the whole process at once. Choose the path that covers the most common case and build a lean tool around it: a form that collects the right information first time, an approval flow with clear owners, or a dashboard that shows where things stand.

Prove it with one team. A focused pilot shows whether the tool is useful before you invest in the harder parts, and it gives you people who can explain it to the next team.

Not every automation needs AI

A clear workflow, a structured form or a simple rule is often the better answer, and it is easier to maintain. AI is worth considering where a step involves reading documents, interpreting free text or sorting requests that follow no pattern.

Make that decision step by step, not for the workflow as a whole.

Plan for adoption as well as delivery

A tool nobody uses has automated nothing. Before building, agree who will own the process once it changes, who needs access, which existing systems it must work with and how the people doing the work will take part in testing it.

Review the first version with them and adjust it. Integrations and wider rollout are easier to scope once one workflow is running and the team has opinions about it.