Automate the repeatable. Keep the human.

When a team is busy, “we should automate this” can sound like a complete brief. It is really the beginning of one. Before choosing software, understand the task well enough to explain what happens when everything goes right—and when it does not.

A sensible first automation is usually a repeated, bounded task with a clear owner. It should make the working day easier without making the process harder to understand.

Follow one item through the process

Choose a real example, such as an incoming project enquiry. Write down where it arrives, what information gets copied, who reviews it and how the next person knows they need to act.

Mark the steps that require judgement separately from the steps that follow a rule. Copying an agreed field into a tracker may be routine. Deciding whether the project is a good fit is a different kind of work.

This map often reveals a simpler fix: a clearer form, fewer duplicate fields or one agreed place to store the information. Do that work before connecting more tools.

Define the exceptions first

Imagine the same enquiry arriving twice. Imagine a missing email address, an unavailable destination or someone changing their mind. Decide what the process should do in each situation.

For a first version, a visible queue for human review can be more useful than trying to handle every exception automatically. A failed step should have an owner and an obvious next action. Otherwise the team exchanges visible manual work for invisible maintenance.

Use the simplest suitable method

If the decision can be expressed as a clear rule, begin there. An AI component may be worth exploring for an ambiguous task, but it also needs examples, review and a way to handle uncertain output. The label matters less than whether the process is dependable enough for its purpose.

For an enquiry workflow, start by organising the submitted information and preparing an internal draft. Review the draft before it reaches a customer. Expand the responsibility only after you understand the mistakes and the effort needed to correct them.

Make the pilot measurable

Record how long the task takes before the change, then track completed items, exceptions and correction time during the pilot. Include the time spent maintaining the automation. Avoid declaring success simply because fewer clicks are visible.

Assign an owner, document how to pause it and keep the original working process available while testing. A useful automation should leave the team with more clarity about the work, not less.

The first goal is modest: one repeated task handled well, with a person still able to explain what happened.