There is a research paper that has been making rounds in enterprise AI circles and deserves more attention than the single line most people have taken from it.
The Stanford Digital Economy Lab published its Enterprise AI Playbook in April 2026. It is drawn from 51 live, production-grade deployments across 41 organisations, seven countries, and more than one million employees. And what it found cuts against almost every assumption the technology industry has built its messaging around.
In every deployment that succeeded, and in every deployment that failed, the determining factor was not the model. It was not the vendor, the feature set, the benchmark performance, or the integration timeline. In every case, the variable that decided outcome was the organisation: executive sponsorship, governance architecture, and the quality of workforce change management. Seventy-seven per cent of the implementation challenges in the study traced to non-technical factors: change management, data quality, and process redesign.
One Finding in 51 Deployments
The research does not say technology does not matter. It says it matters significantly less than most programmes treat it as mattering, and that the organisations which led with governance and change management consistently outperformed those that led with model selection.
One adjacent data point makes this more concrete. Sixty-one per cent of the successful deployments in the study followed at least one prior failed attempt. Those organisations had not found a better model on the second attempt. They had changed what they were actually doing. And in almost every case, that meant addressing the organisational variables they had underestimated the first time: governance structure, change management approach, and clarity of executive ownership.
The technology was not the lesson. The organisation was.
How Most Programmes Are Actually Structured
I have sat in enough enterprise AI programme kick-offs to recognise the pattern before the second slide.
The programme begins with a vendor selection process. A proof of concept is scoped, model performance is evaluated, pricing tiers are compared, latency is benchmarked. The technology conversation consumes the first two to six months of the programme. By the time it concludes, the organisation has committed significant capital and credibility to a specific platform before the questions the Stanford data confirms are the real determinants of success have been seriously engaged.
Those questions are not complicated. Who is the executive sponsor, and what does their sponsorship mean in terms of decision-making authority and resource commitment, not just endorsement? What is the governance architecture for the AI programme, not for the AI system, but for the programme? How does the organisation plan to manage the workforce transition that a serious deployment requires, and what does it know about the change-readiness of the teams it is deploying into?
These are not questions that get answered in a vendor evaluation. They are not questions that appear on most programme charters. They are the questions that decide whether the programme succeeds.
What Leading With Governance Actually Means
Leading with governance does not mean delaying deployment while a committee produces documentation nobody will read. It means defining, before the technology is in the ground, who owns the programme’s outcomes, how the workforce transition will be handled, and what the decision-making structure looks like when the deployment hits the friction that every serious AI implementation hits at scale.
Because the friction will come. It always does. And how an organisation responds to it reveals which frame it used at the start.
Programmes built on a technology frame diagnose the friction as a technology problem. The model is adjusted. The integration is patched. The interface is redesigned. The organisational dynamics actually driving the resistance go unexamined, because the programme was never looking at them. Programmes built on a change management frame diagnose the same friction differently. The conversation shifts to whether the right people were involved in design, whether transition support was adequate, whether the governance gave teams the clarity they needed to work confidently with the new system. Those questions lead somewhere. The technology-first version usually leads to another vendor call.
The Argument That Is Now Evidence
This is not a new insight for experienced transformation leaders. I have been making a version of this argument for years, and so has almost everyone else who has led a serious enterprise change programme. The frustration, and the genuine value of Stanford’s work, is that it can now be asserted with data.
For transformation leaders making the case for governance investment in leadership conversations where the pressure is almost always to accelerate on technology, the Stanford Playbook is the data point that turns an argument from opinion into evidence. It does not require arguing against the technology. It requires arguing about sequence and proportion, and it gives you the empirical foundation to do it.
The organisations still leading with model selection are systematically delaying the decisions that actually determine whether a deployment succeeds.
Fifty-one real deployments confirm it. That should be enough.