Skip to content
Stories & Systems
Back to insights

What should I automate first?

Updated
AutomationOperationsOwner Dependency

Automate first the work that is frequent, rules-based, painful when delayed, and safe when a machine does it. Leave high-judgment, relationship-sensitive, or still-unstable work human on purpose. If you only remember one line: standardize the path, then automate the path, then expand.

Who this is for

Owner-led teams that feel buried in busywork and are tempted to "automate everything." You do not need a bigger stack yet. You need a clear first win that buys back hours without creating faster chaos.

Choose a task your team can already explain

Before comparing tools, ask the person who does the work to walk through the last three examples. What started each one? What information did they need? What did they do when something was missing? How did they know it was finished?

If the answers change with every example, clarify the process first. A reliable automation needs a recognizable trigger, usable information, an agreed next step, and someone responsible when it stops.

Compare candidates on five separate factors:

  1. Frequency: how often does the task happen?
  2. Time cost: how much active work does one instance require?
  3. Judgment: can the next step follow a clear rule?
  4. Delay: what happens when the task waits?
  5. Recovery: how difficult would a wrong action be to correct?

Favor frequent, time-consuming tasks with clear rules and recoverable mistakes. Treat judgment and recovery as conditions to satisfy before proceeding. Adding everything into one score can hide a serious problem behind an attractive time estimate.

Good first targets

These usually score well in owner-led organizations:

  • Lead follow-up sequences after a form fill
  • Appointment reminders and no-show recovery
  • Status notifications when a record changes
  • Document or folder creation from a template
  • Routing requests to the right inbox or owner
  • Recurring internal reports that are already defined

If you are unsure whether the process is stable enough, read Is your process ready to automate? before you build.

What not to automate first

  • Exceptions the owner still decides case by case
  • Pastoral, HR, or sensitive conversations
  • Processes that change every other week
  • Anything where a wrong automated action is hard to undo

Those belong in a later phase — or may stay human permanently.

An example: routing a new service request

This is an illustrative example, not a reported client result.

Suppose your office receives service requests through a website form. A coordinator copies each request into a shared system, assigns the appropriate person, and acknowledges receipt. The work happens repeatedly and follows a stable path.

A useful first automation might create the record, assign it by service type, and notify the coordinator. Start with a draft acknowledgment if messages need checking. Keep unusual requests in a visible review queue instead of guessing how to handle them.

Before building, agree on the boundaries:

  • Required information must be present before assigning the request.
  • A duplicate submission should not create a second job.
  • The acknowledgment must not promise a price, appointment, or response time the team has not approved.
  • Failed transfers need a visible alert and a named person to resolve them.
  • The team needs a manual way to continue working during an outage.

The purpose is to reduce copying and chasing while keeping responsibility clear. Automating a reply alone would leave the underlying handoff unresolved.

Measure the work before and after

Observe a representative period before changing the process. Record task volume, active handling time, errors, exceptions, and who gets interrupted. Use the same definitions after the automation is working.

For illustration, 30 requests at four minutes each represent two hours of weekly handling. That is an estimate of the existing work, not a savings claim. Review time, exceptions, maintenance, and new tasks all count against any time returned.

Check whether the change also reduces missed handoffs. A faster process that creates duplicate records or harder-to-find errors may leave the team worse off.

A one-week way to choose

  1. Ask the team which recurring task creates the most copying, waiting, or chasing.
  2. Observe several real examples and write down the normal path.
  3. Check judgment, permissions, and recovery before choosing a tool.
  4. Assign a person to own the process and its exceptions.
  5. Establish a baseline and automate one narrow step.
  6. Review what happened before extending the automation.

Ask your right-hand person to help choose and review the first task. They need to understand what the system does, what it does not decide, and how to recover when it fails. Otherwise you may remove one manual task while becoming the only person who can maintain its replacement.

The best first automation is boring: same trigger, same steps, same outcome, every time.

How this connects to owner dependency

If the "automation opportunity" is actually a decision only you can make, you do not have an automation problem yet — you have Decision Debt or an Absence Audit finding. Clear the decision rights, then automate the leftover busywork.

Next step

Want a structured read on where friction concentrates in your operation? Take the Friction Assessment or browse how we help San Antonio owner-led organizations.