How to Decide Whether a Process Should Be Automated
A practical test for separating the work that is worth automating from the work that only looks like it is.
Business Signals
Short field guides on AI, automation, operations, customer acquisition, web systems and making better technology decisions. Written for owners and operators, not for developers.
This is not a news feed. Every Signal here is written to stay true for years, so you can read one when the question comes up rather than when it is published.
Deciding what to automate, where AI earns its keep, and how to keep a person in the loop where it matters.
6 Signals
A practical test for separating the work that is worth automating from the work that only looks like it is.
The same tool can reduce effort or quietly multiply it. The difference is almost always in who checks the output and how hard checking is.
The realistic places AI earns its cost in a company of five to five hundred people, and the places it usually does not.
Full automation is not the goal. Knowing exactly where a person should press the button is what separates a durable system from a liability.
The unglamorous, high-frequency task nobody wants to talk about is almost always the right place to start, and there are good structural reasons why.
The expensive repetition in most companies is not on the shop floor. It is in inboxes, spreadsheets and the gaps between systems, and it is hard to see.
Handoffs, duplicate data entry, internal workflow, and the quiet costs of information living in too many places.
6 Signals
Scattered information rarely announces itself as a problem. It shows up as slow answers, arguments about numbers and quiet customer damage.
The points where work passes from one person to another are where time, information and accountability leak. They are also the easiest places to improve.
Six properties that distinguish a workflow people follow from a procedure document nobody has opened since it was written.
Duplicate data entry is rarely on anyone's list of problems because it is spread thinly across everyone's day. It is one of the largest recoverable costs.
Spreadsheets get an unfair reputation from the cases where they have been pushed too far. For a large class of problems they remain the correct answer.
The specific warning signs that a sheet has outgrown itself, and how to move off it without a nine-month project.
What happens to an enquiry after it arrives, how fast you answer, and where leads fall through the gap.
6 Signals
Most businesses have never traced their own enquiry path end to end. The exercise takes an hour and regularly finds leads going nowhere.
For most service businesses, how fast you reply is not customer service. It is a feature customers compare, often the only one they can compare early.
Reporting tells you what happened to your leads. Routing determines what happens to them. Most businesses invest in the first and neglect the second.
A brochure describes. A sales process moves someone from uncertainty to a decision. Most business websites are still built as the first thing.
The gap between the team that generates demand and the team that fulfils it is where most enquiries quietly disappear, and neither side can see it.
Automated follow-up works when it is specific, useful and honest about what it is. It fails when it pretends to be a person having a thought.
Metrics worth watching, a single source of truth, and the difference between having data and having a signal.
6 Signals
A useful metric changes a decision. Most of the numbers on a business dashboard fail that test, and the failure is usually structural rather than accidental.
A reporting layer built on unreliable inputs produces confident, attractive, wrong answers, and makes them harder to question.
Businesses are not short of data. They are short of the small number of things that should make someone stop and act.
Adding numbers to a report feels like progress and usually reduces the chance that anything gets acted upon.
The goal is not one system holding everything. It is one authoritative answer per question, which is a far smaller and more achievable project.
Analytics tools are excellent at showing you data and indifferent to whether it means anything. The questions worth asking are about your own business.
Speed, ownership, search visibility, and the difference between a page and a working web system.
4 Signals
Speed is not a technical vanity metric. It changes how many people reach your contact form, and the causes are usually mundane and fixable.
Beneath the tactics, search visibility comes down to a machine being able to determine what you do, who you do it for, and whether you are credible.
A surprising number of businesses do not control the assets their operations depend on, and only discover it during a dispute or a departure.
Both produce a website. Only one of them participates in how the business runs, and the choice between them is about what you need the site to do.
Build, buy, or leave it alone — including the projects that are better left unstarted.
2 Signals
The third option is missing from most technology decisions, and it is frequently the right one.
Projects consume attention, not just money, and attention is the scarcer resource. Declining well is a skill worth developing.
Applied technology for business
That is usually the moment worth a conversation. Alden Signal works with businesses across the United States and Canada on applied AI, automation, data and decision systems, and web systems.