Adapted from a book in progress on AI, crypto, and the machine-readable company.
The fastest way to waste money on AI is to automate a workflow you do not understand.
That sounds obvious. Companies do it every day.
They take a messy process with unclear ownership, inconsistent data, verbal decisions, hidden exception paths, and three unofficial workarounds. Then they layer AI on top and call it transformation.
What they get is not transformation.
What they get is a faster mess.
This is one of the oldest mistakes in management. A new technology arrives. Leadership sees leverage. The company skips the redesign and rushes to the tooling. It assumes the software will impose the discipline the organization never built for itself.
Sometimes that works for a quarter. Then reality sends the invoice.
AI does not fix bad operating design. It amplifies it.
That is why I keep coming back to the same line:
Do not automate the mess. Rewrite the mess.
If there is one idea worth carrying into every AI conversation, it is that one.
Automation multiplies whatever is already true
People talk about AI as though it injects intelligence into a company from the outside.
That is not quite right.
What AI usually does first is increase the speed, reach, and surface area of existing behavior. If the workflow is clear, AI can make it faster. If the workflow is ambiguous, AI can make the ambiguity travel farther. If the state is reliable, AI can help interpret it. If the state is fragmented, AI can turn fragmentation into polished output.
That is the danger.
A broken process used to be limited by human friction. It was slow. It was visible. It annoyed enough people that somebody eventually noticed.
AI reduces the friction.
Now the same broken process can route faster, summarize faster, answer faster, and scale faster. Which sounds useful until you realize the company has simply become more efficient at being wrong.
This is why so many AI deployments feel impressive in demos and disappointing in practice. The model looks smart. The company underneath it is still confused.
I saw this firsthand at Blockdaemon
I saw this clearly at Blockdaemon while rolling out konstant.cloud.
On the surface, the temptation was obvious. Build an AI interface, connect a powerful model, put a conversational layer on top of the company, and it looks like intelligence has arrived.
But that was never the hard part.
The hard part was making sure the system could ground itself in real operating state. If work lived in one place, decisions in another, customer context somewhere else, and important exceptions in side channels, then konstant.cloud would not become an operating advantage. It would become a very elegant way to generate confident summaries from incomplete reality.
That is the trap.
For konstant.cloud to be genuinely useful, it had to sit on top of something more disciplined: readable work, durable decisions, current source material, explicit ownership, and a tighter connection between what the company said was happening and what was actually happening.
In other words, the AI rollout immediately became an operating model project.
That is the part many leaders miss.
Once AI gets serious, it stops being mainly a tooling conversation. It becomes a truth conversation.
The fantasy behind bad AI strategy
A lot of enterprise AI strategy is built on a fantasy.
The fantasy is that intelligence can be added without redesign.
That leaders can keep the same fragmented systems, the same unclear handoffs, the same undocumented decisions, the same side-channel exceptions, and then somehow get a cleaner operating model by placing AI on top.
They cannot.
If the company has no shared reality, AI becomes a smoothing layer over disagreement.
If nobody knows who owns the outcome, AI becomes a polished narrator of organizational drift.
If the real process lives in folklore, AI can only automate the official fiction.
That last point matters more than most executives realize.
Most companies have two processes.
The first is the one in the documentation, the system, the executive review, and the training deck.
The second is the one people actually use to get things done.
The second one is usually the real company.
It lives in Slack messages, copied spreadsheets, hallway calls, escalation habits, personal notes, and unwritten rules. That is where customer commitments get rescued. That is where deadlines get saved or missed. That is where the company reveals what it actually trusts.
When leadership automates without redesigning, it usually automates the first process and ignores the second.
That is why the rollout looks clean while the business still feels chaotic.
Where this goes wrong in practice
The failure modes are not mysterious. They repeat.
1. AI automates ambiguity
A workflow says an item is “in progress.” One team means active work. Another means blocked pending review. A third means mostly done.
Then leadership asks AI what is at risk.
The model cannot resolve what the company never standardized. It can only interpret inconsistent signals and produce a sentence with good grammar.
That is not intelligence. That is ambiguity with formatting.
2. AI accelerates bad handoffs
A customer request enters the system. Sales frames it one way, product interprets it another way, engineering receives it stripped of commercial context, and operations inherits the consequences later.
Now add AI summaries and automated routing.
Did the handoff get fixed? No. It got faster. The distortion now moves with less resistance.
3. AI gives management false confidence
This one is especially dangerous.
When a human gives a messy status update, you can usually hear the uncertainty. When AI gives one, the uncertainty often arrives flattened into tidy prose. The result feels more authoritative than it is.
That is how leaders end up managing a description of reality instead of reality itself.
4. AI hardens the wrong workflow
Sometimes the most valuable people in a company are quietly compensating for a bad system. They know the hidden dependencies. They know which approvals can be ignored, which fields are stale, which spreadsheet matters, which issue needs a phone call instead of a ticket.
Then AI gets rolled out against the formal workflow.
Instead of fixing the design, the company hardens the bureaucracy around it. The machine now reinforces the weaker system because the stronger informal one was never made explicit.
5. AI widens operational blast radius
A bad manual process is annoying. A bad automated process is dangerous.
If AI is helping route incidents, summarize customer commitments, prioritize engineering work, prepare executive briefings, or interpret runtime events, then weak process design is no longer just inefficient. It is operational exposure.
That is when the bill comes due.
The lesson from the last reengineering era
This is one reason the current AI wave feels familiar to anyone who watched how business process reengineering got abused in the 1990s.
There was a valid insight at the center of that movement. Companies should redesign work around outcomes, not departments. They should reduce bad handoffs, simplify flows, and challenge internal bureaucracy.
Correct.
Then came the misuse.
Many leaders kept the language of redesign but skipped the discipline. Reengineering became a cover story for layoffs, centralization, and short-term optics. The company looked leaner on paper while the operating substance got weaker.
The current AI moment carries the same temptation.
Executives say they want productivity, speed, and leverage. Fine. Some of that is real. But too often the first question is still, “How many people can this replace?” instead of, “What is the actual flow of work, and why is it broken?”
That is the tell.
If AI starts as a labor-reduction story before it becomes a design story, the company is probably heading toward a more expensive version of the same old mistake.
The technology is better now. The management failure mode is not.
What rewriting the mess actually means
“Rewrite the mess” does not mean stop automating. It means earn the automation.
It means doing the harder operating work first so AI has something real to work with.
That usually starts in five moves.
1. Reframe around the value flow
Do not start with departments. Start with the end-to-end outcome.
How does customer demand become delivery?
Where does trust get won or lost?
Where do commercial promises meet technical reality?
Where does work wait?
Where does context degrade?
The org chart is not the unit of failure. The flow is.
2. Expose tacit work
Find the places where the company depends on oral tradition.
Which decisions disappear after meetings?
Which escalations happen off-system?
Which exceptions are handled informally?
Which teams keep shadow records because they do not trust the official ones?
That is the hidden company. If you do not surface it, you will automate around it and wonder why the results feel fake.
3. Choose canonical truth
Pick where truth lives for work, decisions, customer state, and runtime state.
Not in theory. In practice.
A company cannot become machine-readable if every important question requires interpretation across five systems and three memories.
4. Insert AI where judgment is expensive and state is strong
This is where AI actually shines.
Use it where first-draft economics matter, where summarization helps, where routing helps, where issue triage helps, where decision preparation helps, and where humans still own the final call.
Do not start where the underlying state is weakest. That is just industrialized guessing.
5. Harden the loop
Once AI enters the workflow, the workflow has to become more auditable, not less.
Who approved what?
What source grounded the recommendation?
What changed?
What failed?
Who owns the override?
If the answer is “it depends,” the system is not ready.
This is the real work
The most important AI projects in the next decade will not be the ones with the flashiest demos.
They will be the ones that force companies to become more legible to themselves.
That was the deeper lesson for me from rolling out konstant.cloud at Blockdaemon. The product side was interesting. The model side was interesting. But the real lesson was operational. Once you try to make AI genuinely useful inside a company, you immediately discover the quality of the company’s own state.
You find out what is explicit and what is folklore.
You find out where ownership is clear and where it is fuzzy.
You find out whether decisions survive the meeting in which they were made.
You find out whether the system reflects reality or merely describes a cleaner version of it.
That is not a side issue.
That is the project.
Do not automate the mess. Rewrite the mess.
Everything good comes after that.
This is the fourth post in a series on AI, crypto, and the machine-readable company.
The next step is turning this into a method: how leaders can redesign the company so AI becomes useful without making the business more brittle, more centralized, or more detached from reality
