What Should You Automate First?

Signs a task may be worth automating

• It happens often, on a predictable schedule or trigger.
• The steps are the same every time.
• The decision rules can be written down clearly.
• It moves information between tools you already use.
• Forgetting it causes a visible problem, like a missed follow up.
• Someone is copying and pasting the same fields repeatedly.

The best first candidate is usually ordinary rather than impressive. It is a small, dependable action that happens often enough to matter, such as creating a standard task set after a form is submitted. A narrow automation is easier to test, monitor, and repair than a long chain touching every tool in the business.

Signs it should stay manual

• It requires reading context and deciding what matters.
• The outcome changes depending on tone, relationship, or nuance.
• It happens rarely, so maintaining the automation costs more than doing it.
• The process is still changing week to week.
• An error would be expensive and hard to notice.

Manual is not a failure. Some work is better done by a person who can catch what a rule cannot.

Repetitive work versus judgment based work

Repetitive work follows a rule. Judgment based work weighs options. Automation handles the first well and the second badly.

What can be automated around a human decision?

A task does not have to be fully automatic to become easier. Keep the decision with a person and automate the preparation or follow-up around it. For example, a system can collect a request, create a review task, attach the relevant information, and notify the owner. The owner still decides whether to approve it. The system then records and routes that decision.

This approach is useful for proposals, refunds, sensitive client messages, content approval, and anything else where context matters. It removes administration without pretending judgment can be reduced to a simple rule.

A useful test: can you write the task as a sentence that starts with when this happens, do exactly this? If the sentence needs several it depends clauses, the task is probably judgment based. You can still automate the surrounding steps and leave the decision to a person.

Simple examples to start with

• Reminders. Nudges before deadlines, renewals, or scheduled calls.
• Task creation. Standard tasks generated when a project or client starts.
• CRM updates. Contact details and stage changes recorded without manual entry.
• Lead routing. New inquiries sent to the right person with the right information attached.
• Recurring tasks. Weekly and monthly work that appears automatically instead of being rebuilt each cycle.
• Notifications. Alerts when something is approved, overdue, or waiting on someone.

Why automating a broken process makes things worse

Automation does not fix a process. It repeats it faster and more consistently. If steps are unclear, if ownership is vague, or if the current process only works because someone quietly corrects it, automation will spread those problems instead of solving them.

Make the process ready first

• Confirm the trigger that starts the process.
• Remove steps that no longer serve a purpose.
• Name an owner for exceptions and failed runs.
• Decide what a successful outcome looks like.
• Use consistent fields, statuses, and naming across the tools involved.

Before automating, write the process down as it actually happens today, not as you wish it happened. If you cannot describe it in order, it is not ready. Our guide on SOPs, checklists, and workflows is a good place to start.

A simple way to prioritize

Score each candidate task on three things and start with the highest total.

• Frequency. How often does it happen.
• Consistency. How identical is it each time.
• Cost of forgetting. What breaks when it gets missed.

High frequency with high consistency is the safest first automation. Low frequency with high complexity is usually the worst. Start with one task, run it for a few weeks, and confirm it actually holds up before adding the next.

You can also score effort and risk. A strong first choice has high frequency, high consistency, low implementation effort, and a mistake that is easy to spot and correct. If two tasks score similarly, choose the one that affects fewer systems.

Test before you depend on it

1. Run the automation with sample information, including missing or unusual fields.
2. Check what happens when the same trigger arrives twice.
3. Confirm the right person is notified when something fails.
4. Keep the manual process available during the first live runs.
5. Document the trigger, actions, owner, tools, and how to pause the automation.

Review early runs instead of assuming that a successful connection means a useful result. The goal is not to automate the most work. It is to make a clear process more reliable while keeping people involved where their judgment adds value.

Your first automation checklist

• The process is stable and can be explained in order.
• The trigger and expected outcome are unambiguous.
• The information needed is available in a consistent format.
• Someone owns monitoring and exceptions.
• A failed run will not create an unsafe or irreversible outcome.
• The result can be checked against the original manual process.