The AI Succeeded. That Was the Problem.

In the space of three months, three different teams inside the same enterprise each launched an AI agent. Each earned a celebration in the internal newsletter as proof that the company was delivering on its board-approved “AI-first” mandate.

The first automated a segment of the market research workflow. The second handled document classification for a major client vertical. The third sat atop a proprietary dataset and answered natural-language queries on historical project performance.

Each tool performed well within its boundary. Weekly adoption metrics climbed. From a distance, the dashboard looked like textbook transformation success.

Then a fourth business unit approached procurement. They needed an agent trained on a commercial dataset none of the existing three covered. Procurement asked the obvious question: why not use one of the three agents the company already funded?

Weeks of friction followed. Eventually, the fourth team was forced to pilot one of the existing agents with the enthusiasm of someone ordered to wear a colleague’s shoes.

That pilot was never going to work. Everyone involved knew it, and everyone involved could later point to the adoption dashboard as proof they had complied.

The Orchestration Orphan

Think about the most effective advisor or executive you have worked with. Their value comes from cross-contextual synthesis: walking into a board review or a commercial deep-dive and connecting signals across siloed functions in real time.

The three agents were the exact opposite: three capable specialists that could not hold a conversation with one another. The research agent had zero visibility into project performance data. The classifier knew nothing about the vertical intelligence sitting one floor away.

Every enterprise architect knows the technical solution is an orchestration layer. The strategic question is who funds and owns it. In this company, no single executive had the incentive. An orchestrator’s value is cross-functional, which means it cannot be credited to any single department’s quarterly scorecard. Cross-functional capabilities die inside incentive structures that reward leaders solely for local tool adoption.

Three Behavioural Metrics of Priority Signal Divergence

What got built was a faithful mirror of the company’s unreconciled incentives. This is Priority Signal Divergence, and boards can measure it directly across three behavioural ratios without running a single employee survey:

• Calendar Attention Ratio: Rank the CEO’s stated strategic priorities presented to the board, then categorise leadership calendars over four months by which priority each meeting actually serves. In this enterprise, “AI-first” sat at number one on the strategy slide and number three in actual leadership meeting time.
• Budget Velocity Ratio: Measure the median days between a discretionary funding request and final sign-off for each stated priority. The three departmental agents won approval in days; the cross-functional orchestration layer could not even secure a budget owner. Allocation is what the board approves; velocity reveals what the operating model treats as urgent.
• Response Latency Ratio: Track median executive response times to internal escalations tagged to each strategic initiative. Messages tied to departmental scorecards drew replies in hours; cross-functional coordination requests sat for days.

Research by Bandiera, Prat, Hansen, and Sadun in the Journal of Political Economy tracking 1,114 CEOs across six countries confirmed this exact split: in high-performing firms, executive time allocation tightly matches stated priorities; in underperforming firms, the correlation collapses.

The AI did not fail. It succeeded so completely that it made the divergence between stated strategy and actual incentives visible to anyone willing to look.