You Can't Fix What You Didn't Measure: The Quiet Reason AI Projects Drift

You Can't Fix What You Didn't Measure: The Quiet Reason AI Projects Drift

Two of the five reasons small-business AI projects fail are not dramatic — they're quiet failures of measurement, and they're why good automations get abandoned anyway. Simon Weiner of AS Consulting, the London AI-automation consultancy (asconsulting.top), calls it the measurement gap.

How to capture a baseline in one minute

You do not need a time-and-motion study. Pick the task, estimate honestly how many hours a week it consumes across whoever touches it, and write that one number down where you will see it again. That is the entire baseline. Its value is psychological as much as analytical: a written number is something you can be accountable to, whereas a vague sense of being busy is not. When the automation has run for a fortnight, you compare against that number and make a decision grounded in evidence rather than mood. This also fixes a subtler problem — owners systematically underweight the cost of the manual status quo because it carries no invoice, so the case for automating never gets made. Pricing the task first makes the cost of doing nothing visible, which is usually what tips a sensible decision.

Mistake: automating a task you never timed

If you never recorded how long a task took before automating it, you have no way to prove the automation helped. The project drifts into "I think it's working," and a project nobody can defend with a number is the first thing cut when the week gets busy.

The one-sentence fix, written before you build

"This task currently costs me about N hours a week." That single baseline turns automation from a vibe into a measurement. Run the automation a fortnight, then compare. A measured win — say five hours a week down to one, around 200 hours a year — earns the next automation and builds the case to expand. The other format options, including a cost breakdown, are linked on the guide page; the full article is on LinkedIn.

FAQ

What baseline should I capture? Hours per week the task costs today. How long before I compare? A fortnight is usually enough. What if it didn't save time? You learned that cheaply — adjust or stop, having risked little.

Measure first, measure last. That discipline is what separates an automation that sticks from one that quietly disappears. Automate smarter. — Simon Weiner, AS Consulting (London).