Essay · 2026 · 6 min read
Where AI Doesn't Belong Is the More Strategic Question
On mandates, exclusion zones, and the research nobody asks for.
The instruction arrived as a verb. Agentify.
No problem statement attached. No user in the sentence. Just a directive that assumed the hard part was building and the easy part was deciding where to point it.
I've come to believe that assumption is backwards. The hard part of an AI mandate is not the build. It's determining where an agent earns its place — and, more consequentially, where it doesn't. That second question is the one almost nobody funds research to answer, and it is the one that determines whether the whole effort holds.
The mandate problem
Most organizations are not asking whether to add AI. That decision was made above the level of the people implementing it, usually in a room where the strategic value was self-evident and the user was an abstraction.
What arrives downstream is a directive without a diagnosis. And a directive without a diagnosis produces a predictable pattern: teams apply AI to whatever is technically easiest to reach, ship it, and then discover that ease of implementation and value to the user are almost entirely unrelated variables.
This is not a failure of engineering. It's a failure of sequencing. The research that should precede scoping gets skipped, because a mandate feels like it has already answered the question the research would ask.
It hasn't. It has only answered whether. It has said nothing about where.
A mandate answers whether. It says nothing about where.
What users actually tell you
When I ran foundational research on where AI could help an enterprise asset, I went in looking for opportunity. I expected to come out with a ranked list of tasks people wanted help with.
I did get that list. But the more valuable half of the findings was the inverse: the places where users actively did not want an agent involved, and were willing to say so directly.
The pattern was clean enough to be worth stating plainly. Where the task was about finding, navigating, or repeating, receptivity was high. People were glad to hand off the work of knowing where something lived, or of grinding through a process they already dreaded.
Where the task involved sensitive data, receptivity dropped sharply. In those areas, users didn't want agents acting upon them. They wanted certainty, a visible mechanism, and a person accountable for the outcome.
That distinction is not really about AI capability. The question users were answering was not can it be here, but should it be here. And their answer was a boundary.
Misplaced AI is not a local failure
Here is why exclusion zones matter more than the opportunity list.
If you put an agent somewhere users welcome it and it performs poorly, you have a quality problem. It's contained. You improve it or you pull it back, and the damage stays roughly where it happened.
If you put an agent somewhere users didn't want one — particularly somewhere consequential — the failure is not contained. It costs trust across the entire surface.
Trust is a shared resource across an experience. You spend it in one place and it's gone in all of them. Which means the cost of a misplaced agent can be every other agent you were planning to ship afterward.
Trust is a shared resource.
What the research actually has to look for
If you're going to map this properly, opportunity-hunting alone won't get you there. Four lenses did the work.
Pain points. Where the current experience breaks down, frustrates, or stalls the person outright.
Time-consuming tasks. The work that costs users the most time, which is the clearest candidate for compression.
Workarounds. What people built for themselves outside the system. Every workaround is a marker for an unmet need that somebody cared enough about to route around.
Sensitivity. Where users flagged that they'd rather stay in control — asked directly, not inferred from behavior.
The first three map opportunity. The fourth maps the boundary.
Telling an organization under an AI mandate that there are places AI shouldn't go is not a comfortable finding to carry into a room.
It reads, initially, as resistance. As the research function slowing things down. As someone who doesn't understand the strategic imperative.
But framed correctly, it is the opposite. Exclusion zones are what make the rest of the roadmap defensible. They convert an open-ended mandate into a bounded one, which is the only kind that can actually be executed with confidence.
What I'd ask before the next build
If you're operating under a mandate right now, three questions are worth answering before anything gets scoped.
Where have users already told us they want control rather than assistance?
What would it cost us if we placed an agent in a consequential moment and users rejected? Trust, financial, and otherwise.
Is our sequencing based on user effort and receptivity, or on what's easiest to build first?
The organizations that get AI right won't be the ones that deployed it in the most places. They'll be the ones that were deliberate about the places they left alone.