How to choose your first workflow to automate

Most organisations have more automation ideas than time to build them. The first project matters more than its size suggests: it sets expectations, builds trust in the approach, and teaches your team how automated work should be monitored. Choosing well is mostly a matter of asking the right questions before any tool is opened.

Start with a list, not a tool

Ask the people who do the work which tasks they repeat every week. Write each one down as a short sentence that describes the trigger, the steps, and the result. For example: “When a new enquiry arrives by email, someone copies the details into the CRM and assigns it to a colleague.”

Describing tasks this way keeps the conversation about the process rather than about a specific product, and it often reveals that several “different” tasks are variations of the same flow.

Score each candidate on five questions

For every task on the list, answer these questions honestly:

1. How often does it happen? Daily or weekly tasks pay back effort faster than quarterly ones.
2. How consistent are the steps? Tasks that follow the same path most of the time are easier to automate reliably than tasks that need judgement at every step.
3. What happens if it goes wrong? A mistake in an internal summary is easy to correct. A mistake in an invoice or a message to a customer is not.
4. Is the input data available and tidy? Automation depends on information arriving in a predictable format.
5. Who owns the process? Someone needs to be responsible for the automated version and notice when it stops working.

A good first candidate is frequent, consistent, low-risk, and has a clear owner.

Prefer “assist” over “replace” at first

For a first project, it is usually wiser to automate the preparation of work than the final action. An automation that drafts a reply for a person to approve, or fills in a record for someone to check, can save much of the time with far less risk. Once the team trusts the output, you can decide whether to remove the review step.

Define what success looks like before building

Agree in advance how you will judge the result. Useful measures are simple: time spent on the task before and after, the number of items that needed correction, and whether the people involved find it helpful. Write these down before you start, so the evaluation is not shaped by the outcome.

Plan for the day it breaks

Every automation eventually meets an input it was not designed for. Before launch, decide:

• where failures will be reported, and who will see them
• how to pause the automation quickly
• how the task will be done manually in the meantime

A short runbook covering these points turns a broken automation from an emergency into a routine fix.

A simple starting point

If you are unsure where to begin, look for a task where information is copied from one system to another by hand. These tasks are common, easy to describe, and usually low-risk, which makes them a sensible place to learn how automation fits into your organisation.