Where should we start with automation?

Most businesses don't stall on automation because the tools are missing. They stall because no one knows which task to automate first. The problem isn't capability. It's prioritization. And without a way to rank what actually needs to move, every automation candidate looks equally valid — and equally deferrable.

Why does automation always end up on next month's list?

We all have a version of this. A task that doesn't feel urgent enough to fix but too time-consuming to ignore. It sits in the schedule like furniture. We walk around it. We stop seeing it.

The reason it keeps moving to next month is that it doesn't feel like a crisis. It just feels like work. Ninety minutes a week compiling a report from three platforms. Done every week for a year. Familiar, manageable, invisible.

Seventy-eight hours. That's what ninety minutes a week becomes over twelve months. Nearly two working weeks spent on a task that creates no value — only visibility.

So the task isn't urgent. But the cost is real and compounding.

What makes a task worth automating?

Not every repetitive task deserves automation. That's the part we skip when we make our lists.

Automation has a setup cost. Time to build, time to test, time to maintain. A task that takes ten minutes a month might not clear that bar. A task that takes ninety minutes a week almost certainly does.

The useful filter is leverage: how much recurring time does this task consume, and is that time being spent at the point of highest business value? If the answer is no — if the task creates visibility but not decisions, movement but not progress — that's where automation earns its cost.

Not the most impressive thing to automate. The thing that's eating time at the point where the business needs attention most.

Why a list of improvements isn't a strategy

Most teams approach automation the way they approach a product backlog. Everything goes in. Then priorities fight each other. Then nothing moves.

A list of improvements isn't a strategy. Without knowing which item is the actual bottleneck, effort gets distributed evenly across things of wildly unequal leverage.

The company with the most automations doesn't win. The company that freed up the right capacity wins. Those are different problems.

This is why "we should automate more things" is such a hard question to act on. It sounds like a direction. It isn't. It's a category. Direction requires knowing which specific task, at which point in the workflow, is currently constraining what you're trying to do.

How do you find the actual bottleneck?

Start with time, not ideas. Track where the manual hours actually go for two weeks. Not from memory. From logs, calendars, or a simple tally. Memory optimizes for what feels important. Logs show what's actually happening.

Then look for the cluster. Usually one type of task — reporting, data collection, scheduling, outreach follow-up — accounts for a disproportionate share of manual time. That cluster is almost always the better starting point than the clever automation idea someone had in a meeting.

Do you know where your manual hours actually go this week? Most people don't, and that's exactly why automation planning stalls at the list stage.

What this comes down to

Automation stalls when prioritization is missing. The tools exist. The intention exists. What's missing is a way to rank which task is actually worth automating first. That ranking comes from time data, not intuition. The task worth automating is the one consuming the most recurring time at the point of lowest business leverage — not the flashiest candidate on the list. Understanding where time actually goes is the first move. Everything else follows from that.

The uncomfortable truth is that most automation lists are a form of avoidance. Collecting candidates feels like progress. Knowing which one to start with requires a harder look at how the business actually runs.

PS: If you've been "about to automate" the same task for more than three months, that's the one. Start there.

---

Frequently asked questions

How do I know which business tasks are worth automating? Start by tracking where manual hours actually go for two weeks. The task worth automating is the one consuming disproportionate recurring time at the point of lowest business value — not the most impressive candidate on the list.

Why does automation planning keep getting pushed to next month? Because repetitive tasks feel manageable rather than urgent. They don't trigger a crisis response. The cost is real but invisible until you add it up across a year. Ninety minutes a week becomes seventy-eight hours annually.

Is automating content or outreach a good place to start? It depends on whether those are actually your highest-cost manual tasks. Content and outreach automation get a lot of attention, but they may not be where your business is losing the most time. Follow the data, not the trend.

What's the difference between automating something and just eliminating it? Automation preserves the outcome while removing the manual effort. Elimination removes both. Before automating, it's worth asking whether the task produces real value or just visibility — sometimes elimination is faster and more effective.

How long does it take to see a return on a business automation? It depends on setup complexity and task frequency. A task that takes ninety minutes a week can pay back a full day of setup time in under a month. The higher the frequency and the lower the task complexity, the faster the return.

What if we don't have a developer to build automations? No-code and low-code tools — Make, Zapier, n8n — cover a wide range of repetitive business workflows without requiring engineering resources. The barrier today is prioritization, not technical skill.