We've seen this movie before. AI is the automation craze, ten years later.
Every generation of business technology gets sold the same way: as the thing that finally fixes the process. It never does, on its own. Here's why AI won't be the exception — and what actually works instead.
The pitch always sounds the same
A decade ago, the pitch was automation. Robotic process automation, workflow software, "digital transformation" in the loosest sense of the term — the promise was that if you wired your existing process into a machine, the machine would run it faster, cheaper, and with fewer mistakes than the humans doing it by hand.
Today the pitch is AI. Different acronym, same promise: hand your process to something smarter than a human, and the process gets better. The tools changed. The pitch didn't.
What actually happened ten years ago is the part everyone conveniently forgets. Companies that automated a broken process didn't get a fixed process running faster. They got a broken process running faster — and running it at a scale and speed that made the underlying dysfunction much harder to catch, diagnose, and unwind, because now it was happening automatically instead of visibly, by hand, where at least someone noticed when it went wrong.
The mistake has a name, and it's older than either technology
This isn't a new observation. Business process reengineering, as a discipline, exists specifically because organizations kept making this mistake with every new wave of enterprise software going back to the 1990s. The core insight was never about the technology — it was about sequence. Fix the process, then apply the tool. Reverse that order, and the tool just becomes a faster way to do the wrong thing.
AI makes this failure mode worse, not better, for one specific reason: AI is genuinely more capable than the automation tools that came before it. A clunky RPA script that automates a bad process fails in ways that are usually obvious pretty quickly — it breaks, it errors out, someone notices. A capable AI system layered onto a bad process can paper over the dysfunction convincingly enough that nobody notices until the cost has already compounded. The better the tool, the more dangerous it is to point at the wrong problem.
That's not a line written for this article. It's the actual stated goal on a real client engagement, well before AI was part of anyone's vocabulary. The instinct to fix the process before touching the technology isn't new marketing positioning built around the AI moment — it's the same discipline applied to whatever the current hype cycle happens to be.
How to tell which problem you actually have
Most businesses considering an AI investment right now are really asking one of two very different questions, and conflating them is where the trouble starts:
- "Our process works, but it's slow or expensive — can AI speed it up?" This is a legitimate question, and often the answer is yes.
- "Our process is inconsistent, poorly owned, or nobody agrees on how it's supposed to work — can AI fix that?" This is the question that gets you in trouble, because the honest answer is no. AI applied here doesn't fix the inconsistency. It automates it, at scale, invisibly.
The uncomfortable part is that most organizations can't actually tell which question they're asking without looking closely — because a process that's been broken long enough starts to feel normal to the people running it. That's not a knock on anyone's judgment; it's just how organizational blind spots work. It usually takes someone outside the day-to-day to see the gap between "how we've always done it" and "how it actually needs to work."
- Could a new hire follow this process today from documentation alone, or does it live entirely in a few people's heads?
- If you asked three people on the team to describe how this process is supposed to work, would you get three different answers?
- When this process breaks, is it usually a tool problem — or a step someone skipped because ownership was unclear?
- Are you touching this process across more tools and spreadsheets than you could name off the top of your head?
If more than one of those gave you pause, that's not a reason to avoid AI forever — it's a reason to sequence the work correctly. Align on what the process should actually do, simplify it down to something consistent, and only then decide where AI or automation genuinely earns a place in it.
The businesses that get this right aren't slower to adopt AI. They're faster.
The instinct might be that all this diagnostic work up front is a delay — that the businesses racing straight to AI adoption are the ones getting ahead. In practice, it's usually the opposite. A business that fixes its process first ends up implementing AI faster and cheaper than one that's still discovering, mid-rollout, that the tool is just making an existing mess more efficient. The upfront discipline isn't the slow path. It's the one that doesn't require doing the work twice.
Which question are you actually asking?
Six questions, two minutes — find out whether your process is ready for AI, or needs work first.
Take the readiness check Talk to us