The 5-Minute Test: Is This Task Worth Automating?

Not everything should be automated. That might sound strange coming from an operations automation consultancy, but it's true. We've seen businesses spend weeks automating a task that happens twice a month and takes five minutes. The automation cost more to build, maintain, and debug than the manual work ever did.

The real skill is knowing what to automate. Here's a framework you can use in five minutes to evaluate any task. (And if you want to see the real cost of not automating, read The $120K Employee Who Copies and Pastes All Day.)

What Makes a Task Worth Automating?

A task is a strong automation candidate when it scores high on three dimensions: frequency, predictability, and cost. If a task is frequent, rule-based, and expensive in time or errors, it's almost always worth automating. If it's rare, judgment-heavy, or cheap, it's probably not.

Let's break each dimension down.

Dimension 1: How Often Does This Task Happen?

Frequency is the most important factor. A task that happens 50 times a day offers 50x the return on automation compared to a task that happens once a week.

Dimension 2: How Predictable Is the Task?

Automation works best on tasks that follow rules. "If X happens, do Y." The more predictable the task, the more reliably you can automate it. Tasks that require reading context, making subjective calls, or handling novel situations are harder and more expensive to automate.

Dimension 3: What Does This Task Cost?

Cost isn't just the time spent doing the task. It's also the cost of errors, delays, and the opportunity cost of the person doing it. A 10-minute task done by your $150/hr senior engineer costs more than a 30-minute task done by a $20/hr coordinator.

How Do You Score a Task?

Add the three scores together. The maximum is 15, the minimum is 3.

• 12-15: Automate this now. You're leaving money on the table every day you don't.
• 9-11: Strong candidate. Worth building a business case and scoping the automation.
• 6-8: Evaluate further. Might be worth simplifying the process before automating. Sometimes removing unnecessary steps is more valuable than automating the existing ones.
• 3-5: Probably not worth it. The ROI won't justify the build and maintenance cost. Consider documenting it instead.

How Does This Work in Practice?

Let's score three real tasks using this framework.

The Printable Checklist

Use the checklist below to evaluate any task in your business. Print it out, pin it to the wall, and run through it the next time someone says "we should automate this."

What Do More Worked Examples Look Like?

Let's run through a few more scenarios to show how the framework handles different types of tasks.

When Should You NOT Automate a Task?

The framework catches most cases, but there are situations where a task looks like a good candidate on paper but should still be left manual. Watch for these.

• The process is still changing. If you are still figuring out the best way to do something, do not automate it yet. Automating a process that changes every month means rebuilding the automation every month. Wait until the process stabilizes for at least 3 months before investing in automation.
• The exceptions are more common than the rule. Some tasks appear rule-based on the surface but have so many edge cases that the automation would need dozens of conditional branches to handle them all. If more than 30% of instances require human intervention anyway, the automation adds complexity without enough payoff.
• The task builds relationships. Some manual touchpoints are valuable specifically because they are manual. A handwritten thank-you note to a new client. A personal check-in call to a VIP customer. Automating these removes the thing that makes them effective.
• The automation would be more fragile than the manual process. If the task depends on systems that change frequently (third-party APIs with unstable endpoints, spreadsheets that get restructured regularly, platforms that update their interface often), the automation may break so often that maintaining it costs more than doing the task by hand.
• The volume does not justify the investment. A task that takes 5 minutes and happens twice a month costs about 2 hours per year. If the automation takes 8 hours to build and 2 hours per year to maintain, you will never break even. The math has to work.

What If a Task Scores Low but Still Feels Painful?

Trust the framework, but investigate the feeling. A task that scores low on automation value might still be a problem worth solving -- just not through automation.

Common alternatives:

• Simplify: Remove unnecessary steps. Challenge why the task exists in its current form. Often a process was designed for a situation that no longer applies.
• Template: Create a reusable template, checklist, or standard operating procedure. This doesn't eliminate the task but reduces the cognitive load and error rate.
• Delegate: Move the task to the right level. If a $100/hr manager is doing $20/hr work, the fix might be delegation, not automation.
• Eliminate: Sometimes the best automation is deleting the task entirely. Ask: "What would happen if we stopped doing this?" If the answer is "nothing," stop doing it.

What's the Biggest Automation Mistake Businesses Make?

Automating a broken process. If your current workflow has unnecessary steps, bottlenecks, or workarounds for problems that were never fixed, automating it just makes the dysfunction faster. Fix the process first, then automate the clean version.

The first rule of automation: don't automate a bad process. You'll just produce bad results faster.

The second most common mistake is automating one task in isolation without looking at the full workflow. Individual task automation creates islands. End-to-end workflow automation creates systems. The difference matters as you scale.

Ready to see where you stand? Take the Automation Readiness Checklist.