Position Paper • AI Transformation

Safe Enough to Fail:
Why Most Enterprise AI Use Cases Never Deliver Real Value

21 May 2026

In this article

  • The safe use case

  • Changing the work

  • “We are not ready”

  • Choosing what changes

Want to talk through your AI deployment?

Most enterprise AI initiatives do not fail. They deliver something safer and less valuable: a slightly faster version of work the organisation was already doing.

Meanwhile, the use cases capable of changing how the business operates remain on the roadmap, waiting for better data, stronger governance or greater organisational readiness. The real cost is not the pilot that underperforms. It is the transformation that never begins.

The safe use case asks nothing of the organisation

Safe use cases win because they threaten no team, budget or decision-making structure. Bold ones often challenge all three. These are not primarily technological objections. They are organisational, and organisational objections usually win.

Bold does not mean large or expensive. A bold use case changes the workflow, not simply its speed. It removes a step, redistributes responsibility or changes how a decision is made. If it succeeds, the old process no longer makes sense.

A safe use case can be switched off tomorrow without anything else changing.

The boldness is not in the technology. It is in what the organisation must be willing to change.

Value comes from changing the work

McKinsey’s 2025 State of AI survey found that only 6% of respondents qualified as AI high performers, while just 21% of organisations using generative AI had fundamentally redesigned at least some workflows. Workflow redesign was the factor most strongly associated with bottom-line impact.

BCG reached a similar conclusion: only 5% of companies were generating substantial value from AI. The leaders were not merely automating existing work. They were reshaping core workflows and their operating models around AI.

Software engineering offers a useful illustration. Faros AI found that teams with high AI adoption merged 98% more pull requests, but review time increased by 91%. The study is observational, so it does not prove that AI caused the slowdown. It does show the risk clearly: when one part of a system accelerates and the surrounding workflow does not change, the bottleneck simply moves.

AI added to an old workflow will eventually be constrained by that workflow.

“We are not ready” is the deferral

The familiar reasons for postponing the bolder use case are legitimate: the data must improve, governance must mature and teams need more experience.

But these are rarely conditions that can be completed in advance. Organisations do not become ready and then redesign. They become ready by redesigning: learning where the data fails, which controls matter and how responsibilities must change.

Waiting creates a closed loop: the organisation postpones change until it feels ready, while the capabilities that would make it ready can only develop through the change itself.

The fast-follower strategy offers limited protection here. Technology can be observed and copied. Organisational learning cannot. A company can study another organisation’s tools, but it cannot inherit the experience of redesigning decisions, incentives and accountability around them.

That advantage is built by doing.

Choose the use case that changes something

The next prioritisation meeting should not begin with: “Which use case is easiest to deliver?”

It should begin with:

If this works, what will operate differently?

If the answer is “nothing, we will simply complete the same work faster,” the use case may still be useful. But it should not be mistaken for transformation.

The better use case is not necessarily the biggest. It is the one important enough to require a real change, and focused enough to test that change responsibly.

Bold AI use cases do not remain on the roadmap because the technology is not ready. They remain there because the organisation has not yet decided that preserving the current way of working is the greater risk.

Sources and further reading

  • McKinsey & Company The State of AI in 2025 QuantumBlack, McKinsey, 2025. Source of the 6% AI high-performer figure and the 21% workflow redesign figure. mckinsey.com


  • Boston Consulting Group The Widening AI Value Gap BCG, October 2025. Survey of 1,250 executives across sectors and geographies. Source of the 5% figure on companies generating substantial value from AI. bcg.com


  • Faros AI AI Productivity Paradox Report Faros AI, June 2025. Telemetry analysis of 10,000+ developers across 1,255 enterprise engineering teams. Source of the 98% pull request increase and 91% review time increase figures. faros.ai