The chasm runs through your org chart.
Enterprise agent pilots don't fail on capability. They fall into the gap between the visionary sponsors who bought the demo and the pragmatists who run the work. Today we publish a free field guide that maps the crossing — layer by layer.
Every enterprise now has a pilot graveyard: agents that demoed brilliantly, impressed the sponsor, and then quietly stopped being used. Not cancelled — orphaned. Still technically live, still on the invoice, no longer in anyone's habits. The technology rarely failed. Something else did.
Today we're publishing Crossing the Chasm to the Agentic Organization — a free field guide that names that something, and gives you the vocabulary and the moves to fix it.
The idea in ninety seconds
The chasm, moved indoors.
In 1991, Geoffrey Moore described why promising technologies die on the way to the mainstream market: between the visionaries who buy a dream and the pragmatists who buy proven, complete, accountable solutions, there is a chasm — and what wins the first group actively fails with the second.
Our argument: that same chasm now runs through the middle of your organization. Your AI enthusiasts and visionary sponsors are on one bank. The pragmatist majority who actually run the work — the people whose names are on the output when the agent is confidently wrong — are on the other.
Your pilot succeeded with the near bank — people who wanted it to work. Becoming agentic requires the far bank — people who need it to be safe to rely on. Those are different tests, and almost every stalled transformation passed the first and never sat the second.
An agent pilot succeeds with people who want it to. Becoming agentic requires people who need it to be safe to rely on.
The mechanism
What pragmatists actually buy.
Pragmatists, inside a company as in a market, buy three things — and every one of them translates directly to the employee deciding whether to fold an agent into their daily work.
References
In a market, peer companies. Inside a company, a trusted colleague saying "I use it every day — and here's how it behaves when it's unsure." No launch email competes with that sentence.
The whole product
Not a capability dropped into a workflow, but designed handoffs, training, and a real escalation path. An agent with no way to say "I'm not confident here" is a partial product — and pragmatists wait on partial products.
Accountability
A named human to go to when it misbehaves. "The vendor" is not an answer. "IT" is not an answer. An agent acting in your business with no accountable owner is an unmanaged risk wearing a product's clothes.
Read those three again and notice what they share: none is a model capability. All are properties of the system around the agent. Which is exactly why the organizations that cross the chasm are not the ones with the best agents — they're the ones with the most complete system.
What's inside
The whole product is five layers.
The field guide maps Moore's crossing onto the five layers of our transformation playbook — each layer rewritten as a chasm-crossing move.
Why "agentic everywhere" is how programs die — and how to pick one domain and win it completely. A beachhead is won not when the pilot report is positive, but when removal would cause the team to protest.
Product-grade ownership: an executive sponsor, an agent product owner, and a named trust owner accountable for adoption — organized as a pod, not a committee. Committees do not cross chasms.
Mapping the real workflow — exceptions included — before automating it, and using the delegation ladder to manufacture reference moments in front of your pragmatists. "It asked before committing" is a sentence they repeat to each other.
Choosing a stack that serves the process design — not the reverse — with trust mechanisms in the architecture and validation before your users become your QA. You get one first impression with the mainstream.
Why trust — measured and designed with the six AUX patterns — is what actually carries adoption across, domain after domain. Moore called it the bowling alley: each pin knocked down helps knock down the next.
Plus a six-signal diagnostic for telling whether you're across — starting with the cleanest one.
- Removal would cause protest. The pragmatists in the beachhead domain would push back if you switched the agent off. The single cleanest signal.
- Usage survives sponsor turnover. The agent no longer depends on the champion who launched it.
- The references are unprompted. People outside the beachhead are asking when they get theirs — because a colleague told them to.
- Escalations are routine, not incidents. The agent's handoffs to humans are part of the workflow's rhythm, not events that trigger meetings.
- Trust is on a dashboard. Someone owns the trust scorecard and can tell you whether trust rose or fell this month — because you measure it, not guess.
- The next domain asked to go second. Expansion is pulled by demand, not pushed by mandate. The bowling alley is live.
Read it as a pair
The guide is the why. The playbook is the what.
The field guide is the strategy; the operating manual is our pillar guide, Five Steps to Becoming an Agentic Organization — the layer-by-layer playbook with the plays, the ownership map, the delegation ladder, and the 60-second diagnostic. The two are written to be used together.
Crossing the Chasm to the Agentic Organization
The field guide: 11 chapters on why transformations stall at the chasm — the pilot graveyard, what pragmatists buy, the five layers as the whole product, and the six signs you're across. No email wall.
Read the field guide →Five Steps to Becoming an Agentic Organization
The layer-by-layer playbook: vision, ownership, processes, technology, and the AUX trust layer that drives adoption — with the turn-by-turn plays for each, and the engagements that support them.
Read the playbook →If you read one thing this quarter about why your agents aren't being adopted, read these two.
Capability gets you to the edge. Trust is the bridge.
In a market of commoditized AI, features are replaceable and relationships are not. The organizations that become agentic aren't the ones with the best models — they're the ones that built the whole product around the agent, earned the references, and carried the pragmatists across. That work has a shape. The field guide is the map.
The chasm runs through your org chart. So does the bridge.
Read next & further reading
Method · "Crossing the Chasm" is a framework by Geoffrey A. Moore (Crossing the Chasm, HarperBusiness, 1991). This guide applies its concepts to internal enterprise adoption; the five-layer model and all interpretations are auxfirst's own.