The Wall Street Journal reported that Anthropic says enterprise AI adoption remains in “early phases”, with the company’s September 2025 Economic Index describing adoption as uneven. For technology teams, the point is practical: the availability of models and tools does not mean that use has become consistent across a business.
Adoption remains uneven
Anthropic’s framing is a warning against treating enterprise AI as one standard rollout. Different teams may be at different points of assessment, use and control, even inside the same company.
That matters for architecture and governance. A platform decision can be made centrally, but actual use still depends on data access, process fit, approval routes and the way output is checked before it enters business work.
Planning implications
Architects and IT managers should separate model selection from operating controls. The model is only one part of the deployment; identity, data boundaries, logging, review and exception handling decide whether the use is manageable.
Uneven adoption also affects procurement. A contract or platform choice may cover more users than are ready to use the service in a controlled way, while some teams may already be testing use cases before common rules exist.
Why the early phase matters
At this stage, premature standardisation is a risk. Teams can commit too early to one approach, or they can leave each department to define its own controls without a common view of data and accountability.
The better planning question is narrower than “how do we adopt AI”. It is which work should be exposed to a model, which data is in scope, who approves access and how the organisation checks the result.
When a vendor describes enterprise AI adoption as early and uneven, the practical questions are which use cases are ready, which controls must come first and how responsible AI work is organised; ECS's Core AI topic deals with those questions alongside agentic AI, Azure AI Foundry, the EU AI Act and responsible AI. Sessions and workshops give attendees space to compare implementation choices with product group input and practitioner experience. Attend with concrete adoption and governance questions, especially where pilots are moving faster than internal policy.
This article was written by the ECS editorial team with the assistance of Amal Agent, run.events' AI assistant, which supported the research, drafting and proofreading.