The Execution Signal
Architecture doesn't deploy itself.
Vol. 3 named the stack. Four layers. Each one available today. The IBM i MCP Server is live. Mapepire is in production. The architecture exists and is documented.
So why aren’t organizations running?
That is the question Vol. 4 answers. And the answer is not what most people expect. The barrier to execution is not the technology. It is not the platform. It is not even the budget, most of the time.
It is the distance between a named architecture and a deployed agent. That distance has a name now. It has a cost. And it turns out, the IBM i practitioner is the person best positioned to close it — for their own organization and for every IBM i organization around them.
---
## SIGNAL 13 · THE FAILURE SIGNAL
### The Stack Is Ready. The Organizations Aren’t.
*MIT / Fortune / BCG / ManpowerGroup, 2024–2026 — Three convergent data points measuring the same gap from different angles.*
The readiness statistics are not a surprise anymore. They have been consistent across multiple research organizations for two years running. But their consistency is precisely the point — this is not a temporary lag that resolves itself as organizations get more comfortable with AI. It is a structural gap that widens as AI capability advances faster than organizational readiness.
The numbers:
**95%** of generative AI pilots at major companies are failing. Not struggling — failing. MIT and Fortune put this number in the field in mid-2025. The headline got attention. The follow-on analysis got less attention: the root causes are almost entirely organizational. Lack of skills to govern AI deployments. Data complexity that was never addressed before the pilot started. Governance structures that cannot assure AI acts responsibly. Project scope that was too ambitious to prove anything.
**26%** of scaled AI experiments reach production. BCG’s research found that roughly three in four enterprise AI experiments that make it through internal approval and resource allocation still never make it to production. They stall in the translation layer between proof-of-concept and organizational deployment.
**77%** of organizations have no committed agentic AI strategy. ManpowerGroup’s 2026 research found that more than three quarters of organizations are either experimenting without a deployment framework or waiting for more clarity before committing. In a moment when capability is compounding monthly, that posture is not caution. It is exposure.
Three organizations. Three methodologies. One finding.
The technology arrived. The organizations did not follow.
> “The platform is not the problem. Deploying without posture is.”
*— Signal4i · Vol. 2 · March 2026*
Vol. 2 called this the posture problem. Vol. 4 is the proof that posture is still the constraint — even after the architecture is named and available. The execution gap is real, it is measurable, and it is organizational from top to bottom.
---
## SIGNAL 14 · THE FDE SIGNAL
### The Market Quantified the Gap. Then Priced It.
*Anthropic, 2025–2026 — Anthropic invents a new job category — the Forward Deployed Engineer — because they kept watching capable organizations fail to deploy capable models.*
When a company building the most capable AI systems on earth decides it needs to put humans inside its customers’ organizations just to make deployment work, that is not a product decision. That is a market signal.
Anthropic did not create the Forward Deployed Engineer role because it sounded strategic. They created it because of a pattern they kept observing: capable organizations acquiring capable models and then failing to deploy them at any meaningful scale. The gap between what the model could do and what the organization was ready to use was consistent, measurable, and not closing on its own.
The FDE is the answer to that gap. An embedded human who lives inside a customer organization and translates in both directions — between what AI can do and what the organization actually needs, and between what the organization knows and what needs to be encoded for the agent to act on.
The job title matters less than what it reveals. Every major AI company is now in the business of closing a gap that should not exist if technology adoption worked the way it is supposed to. The fact that Anthropic, with access to the most capable models available, still needed to invent a translation role tells you something important about where the constraint actually lives.
It does not live in the model. It lives in the organization.
> “You cannot hand an organization a model and expect transformation. You need a guide who knows the terrain — not a consultant who reads the map, but someone who has walked it.”
*— Signal4i · signal4i.ai*
The market is now paying a premium for people who can do what the FDE does: speak both the language of AI architecture and the language of the business, embedded inside the organization that needs to change. That premium is a price signal. It is the market telling you that the translation layer between architecture and execution is scarce, valuable, and not going away.
---
## SIGNAL 15 · THE SCALE SIGNAL
### $90 Billion. 500,000 Employees. Can’t Deploy Until 2027.
*WSJ / PYMNTS, March 13, 2026 — FedEx plans AI agents in more than 50% of its workflows by 2028 — but cannot begin deployment until 2027. The reason is not the AI. The reason is the organization.*
FedEx Chief Digital and Information Officer Vishal Talwar stated the ambition plainly in March 2026: every employee and every task across the globe will get adapted to AI and will improve with AI.
The ambition is real. The investment is committed. The intention is serious.
And they cannot deploy until 2027.
Not because the AI does not exist. Not because the vision is unclear. Because their data consolidation project is not finished — and hundreds of legacy systems still need to be replaced before agents can reach them. At $90 billion in annual revenue. With 500,000 employees. With a dedicated AI transformation budget that most IBM i organizations in any given industry sector will never approach.
The FedEx story is not a cautionary tale about a company that moved too slow. FedEx has been investing in digital transformation for years. The story is a proof case about the nature of the execution gap. It is not a technology problem. It is an organizational readiness problem — and it scales with the organization, not with the investment.
The IBM i organizations in every sector FedEx serves are running the same gap at a smaller scale. Same data silos. Same legacy dependencies. Same governance gaps that were never addressed because the business kept running and there was no urgent reason to address them until the reason arrived all at once.
> That is not a technology failure. That is a readiness failure. And it is happening at a company with more resources than every IBM i organization in this room combined.
The difference between FedEx and an IBM i organization with $50 million in revenue is not the nature of the gap. It is the scale. And smaller scale cuts both ways. The same organizational readiness problem that takes FedEx until 2027 to work through can be addressed by a focused IBM i organization in phases — if they start now, and if they have a guide who knows the terrain.
---
## SIGNAL 16 · THE PRACTITIONER SIGNAL
### The IBM i Practitioner Is the Natural FDE.
*Signal4i analysis, 2026 — The characteristics the market is paying premium for are characteristics the IBM i practitioner has been building for thirty years.*
What does a Forward Deployed Engineer actually need to do?
Understand the business deeply enough to know what the organization is actually trying to accomplish — not just what it says it wants. Know the technical architecture well enough to design what agents can realistically do within that environment. Translate between those two worlds without losing fidelity in either direction. Be embedded enough to earn the trust of the people whose knowledge needs to be encoded. And stay long enough to see the first use case through from proof to production.
Now read that description again and ask: who in the IBM i world already does this?
The IBM i practitioner has been doing exactly this for thirty years. They understand the business — deeply, specifically, across decades of edge cases and exceptions and rules that predate the documentation. They understand the platform — architecturally, operationally, at the level of what will hold up in production and what will not. They are already embedded inside the organization. They already have the trust of the people whose knowledge needs to be encoded. They have already been translating between business complexity and technical implementation their entire career.
The translation layer between AI architecture and organizational deployment — the thing Anthropic invented a new job category to fill — is the thing the IBM i practitioner has been living in for decades.
The market is now paying premium for that capability. The question is whether the IBM i practitioner recognizes it in themselves — and whether the IBM i organization recognizes it in them — before someone else arrives to name it.
> “The bottleneck was never intelligence — it was the translation layer between knowing and building. That layer is collapsing.”
>
> *— Andrej Karpathy · Former Director of AI, Tesla · OpenAI*
Karpathy is describing what happens to the translation layer between human knowledge and executable code. The IBM i practitioner has been on the knowing side of that layer their entire career. The layer is collapsing — which means they are now on both sides of it simultaneously. The domain expert and the system author are becoming the same person.
That is not a threat. That is the most important position in the execution gap.
---
## What This Means
Four signals. One thesis.
The execution gap is not a technology problem. It is an organizational readiness problem that the technology cannot solve on its own. The market has recognized this — first by quantifying the failure rate, then by inventing a new job category to close the distance. FedEx proved it at scale: $90 billion, 500,000 employees, still working through the same gap that IBM i organizations of every size are working through right now.
The IBM i practitioner is uniquely positioned to close this gap — for their own organization first, and for the organizations in their sector as they watch the window close.
Architecture doesn’t deploy itself. But the people who know both the platform and the business — who have been living in the translation layer for thirty years — can.
---
## Vol. 5 — The Tandem Signal
The execution gap is real. The practitioner is the answer. And the organization is the frame.
Because here is what the execution gap data reveals when you look at it closely: the organizations that close it fastest are not the ones with the best technology or the most capable practitioners. They are the ones that move technology transformation and organizational transformation simultaneously — not in sequence.
Every IBM i organization navigating this moment is running three transformations at once: the technology, the organization, and the human role within it. Moving them in sequence is how you end up in the 95% that fail. Moving them in tandem is how you end up in the 5% that compound.
Vol. 5 — The Tandem Signal — is about what tandem transformation actually looks like in practice, why sequence kills momentum, and what the IBM i community uniquely understands about running multiple complex changes in parallel.
---
*Signal4i tracks the AI signals that matter for IBM i organizations. Not predictions. Events that have happened, data that has landed, and what they mean for the organizations running the platform.*
*Published by Reggie Britt · Signal4i · signal4i.ai*