Writing · February 1, 2026
When AI Fails, It’s Usually a Management Problem
An article by Kevin M. Miller, published February 1, 2026.
ai · leadership · strategy · engineering · decision-making
AI can write code.
That part isn’t controversial anymore.
I’ve watched models generate clean, consistent, testable code with very little effort. Complaints about “bad AI code” are almost always implementation failures, not hard limits.
So when AI initiatives fail inside companies, it’s worth asking a better question:
If execution isn’t the problem, what is?
The Temptation
AI is an irresistible idea for cost control.
Developers are expensive. Even in the Midwest, a senior engineer easily costs six figures. AI keeps getting better. It feels obvious to ask: Why not train a model and reduce headcount?
On spreadsheets, it looks disciplined. In reality, it’s often the start of a very expensive detour.
The Hidden Cost
I’ve seen teams assign multiple senior developers for a year to “build AI capability.”
Best case, they create a system that can replace part of a mid-level role. Worst case, they create something no one fully understands or trusts.
Either way, the company now owns:
- training pipelines
- prompt discipline
- governance
- review processes
- institutional knowledge maintenance
None of that is free. None of that is core to the business. And none of it creates differentiation customers will pay for.
What AI Can’t Absorb
A human developer doesn’t just write code.
They bring decades of accumulated context:
- past failures
- domain instincts
- political awareness
- unspoken constraints
- pattern recognition across companies and industries
This knowledge isn’t written down. It’s formed through experience and conversation. Often, it’s subconscious.
You can theoretically encode this into an AI system. In practice, no organization ever finishes—and no one maintains it when reality shifts.
So the AI executes instructions without understanding the environment those instructions live in.
And that’s where things quietly break.
Execution Was Never the Bottleneck
The uncomfortable truth is this:
AI fails when it’s used to replace judgment instead of compress it.
Most organizations don’t suffer from a lack of execution. They suffer from unclear priorities, incomplete understanding, and misaligned incentives.
AI doesn’t fix that. It amplifies it.
The Pattern Repeats
This is the same mistake companies make when:
- restaurants decide to bake their own bread
- teams roll their own authentication systems
- businesses build internal tools no customer will ever see
It’s control mistaken for competence.
Excellence is finite. When you spend it on non-core systems, it disappears from the work that actually matters.
Where AI Actually Belongs
AI works best when it:
- accelerates informed humans
- compresses decision cycles
- reduces friction around known judgment
It fails when it’s treated as a shortcut around understanding.
The companies that win with AI don’t try to replace expertise. They protect it—and multiply it.
That distinction matters more than any model choice ever will.
Related writing
On the same explicit topics
Related by shared tags and categories from article metadata.
-
R / 01
January 27, 2026
Why Personalization Is Failing — and What Actually Scales
Most products claiming personalization are just regressing to the mean. Real value doesn’t come from better recommendations — it comes from reducing failure.
Read -
R / 02
leadership
Once You Notice the Shift, It’s Hard to Unsee
A quiet moment where trust changes shape — and what happens on both sides of it.
Read -
R / 03
leadership
Hiring, Vendors, and the Cost of Cornering People
Related writing
Read
Continue reading