Business Automation Strategy: What to Automate and What to Keep Human

A child touching the finger of a white robotic hand

Automation saves time when it is applied to the right work, and creates new problems when it is applied to the wrong work. A strategy is simply a way of deciding which is which before you build anything. This guide gives you criteria for choosing tasks, a clear view of what should stay with people, and a method for introducing automation without losing control of it.

What automation is, and is not

Automation means a system carries out defined steps when a defined event happens, without someone doing each step by hand. A form submission creates a record and sends a confirmation. An unpaid invoice triggers a reminder after seven days.

It is not a substitute for a process. If nobody can describe how a task should be done, automating it only produces the confusion faster. Workflow Automation Basics: Triggers, Actions and Checks explains the building blocks.

What makes a task a good candidate

A task is worth automating when most of these are true.

  • It repeats often. Daily or weekly, not twice a year.
  • It follows rules. The same input should always lead to the same action.
  • The inputs are structured. Form fields, spreadsheet rows, order data.
  • The steps are stable. The process is not changing every month.
  • Errors are cheap or easy to spot. A wrong internal notification matters less than a wrong invoice.
  • It involves copying between systems. Retyping data is slow and error-prone for people and trivial for software.

Typical examples: confirmations and reminders, creating records from forms, moving data between tools, scheduled reports, backups, routing enquiries to the right person, publishing at a set time.

What to keep human

Some work is better done by a person, even when it could technically be automated.

  • Judgement and exceptions. Decisions that depend on context, such as whether to make an exception to a policy.
  • Sensitive conversations. Complaints, bad news, negotiations.
  • Relationships. The messages that make a customer feel known.
  • High-impact decisions. Anything with significant legal, financial or safety consequences.
  • Final approval. Publishing, payments above a threshold, messages to a whole customer list.
  • Rare tasks. If it happens three times a year, a checklist is cheaper than a workflow.

The middle ground: automate the preparation

Many tasks are best split. The system gathers the information, prepares a draft and puts it in front of a person, who reviews and approves. A reply to a common question can be drafted automatically and sent by a human. An invoice can be generated automatically and checked before it goes out.

This approach is particularly appropriate when AI is involved, because AI output can be wrong in ways that look right. See How to Fact-Check AI-Generated Content Before Publishing.

How to prioritise

  1. List the recurring tasks in one area of the business for a week or two. Include how often each occurs and roughly how long it takes.
  2. Score each task on frequency, time per occurrence, how rule-based it is, and the cost of a mistake.
  3. Estimate the effort to build and maintain the automation, including subscriptions.
  4. Start with tasks that are frequent, rule-based and low-risk. They pay back fastest and teach you the most.

The Automation ROI Worksheet turns this into numbers.

Fix the process first

Before automating a task, write it down as a short procedure: the trigger, the steps, who is responsible, what counts as finished. The Standard Operating Procedure Template gives a format. Remove steps that serve no purpose. Then automate what remains.

Design for failure

Every automation fails eventually: a service changes, a field is renamed, an account expires. Plan for it.

  • Assign an owner to each automation, a person who knows it exists and is responsible for it.
  • Log what happened, so you can see which items were processed.
  • Send alerts on errors to someone who will act on them.
  • Add checks, such as stopping when required data is missing.
  • Keep a manual fallback. Know how the task is done by hand if the system is down.
  • Document it. What it does, which accounts it uses and how to switch it off.

Tools: choose after the process

Look first at what your existing tools can already do. Email services, form builders, online stores and accounting software often include automation features. Connector platforms link separate tools without programming, and custom code covers what they cannot. Prefer the simplest option that meets the need. Every additional tool is another account, another cost and another thing to maintain.

Security and privacy

  • Give each automation only the access it needs.
  • Store passwords and keys in the tool’s secure settings, not in spreadsheets or documents.
  • Know which services personal data passes through and make sure that matches your privacy policy.
  • Remove access when someone leaves or a tool is retired.

Measure and review

After a month, compare the result with what you expected.

  • Time actually saved
  • Errors caught and errors caused
  • Effect on customers: faster replies, fewer missed steps
  • Maintenance time and cost

Review each automation at least once a year. Retire the ones that no longer match how the business works. An automation nobody remembers is a risk.

Warning signs

  • Automating a process that nobody has written down.
  • Automated messages that customers cannot reply to.
  • Workflows only one person understands.
  • No alert when something fails silently.
  • So many connected tools that a small change breaks several things.

A first project

  1. Choose one frequent, low-risk task, such as handling contact form enquiries.
  2. Write the current steps.
  3. Simplify them.
  4. Build the automation with a human approval step where it matters.
  5. Test with normal and unusual cases.
  6. Run it for a month and review.

How to Plan and Test a Contact Form Automation and How to Build an Email Welcome Automation Step by Step are worked examples of exactly this.