Part of our guide: AI implementation and operating model
There is a pattern that repeats itself across almost every AI programme that stalls: the technology works, the pilot was a success and the board is enthusiastic. And then nothing happens, because nobody has designed the operating model that would allow the capability to function at scale.
The pilot team built something impressive, and yet there is no clear owner for it in the day-to-day business and nobody has defined how it interacts with existing processes. The governance framework does not cover it and the people who need to use it were not involved in designing it. So it sits there, a working proof of concept with no pathway into the organisation.
This is an operating model problem, not a technology problem.
What we mean by operating model
An operating model is the bridge between strategy and execution, defining how an organisation delivers value: what capabilities it needs, how those capabilities are structured, who owns them and how they interact. When AI enters that picture, the operating model has to evolve, because AI does not just automate existing processes, changing what processes are needed in the first place.
Consider a mid-market insurer processing claims, where AI can accelerate triage and improve fraud detection while changing the role of the claims handler, the escalation pathways, the quality assurance model and the regulatory reporting chain. If you deploy the AI without redesigning those elements, you get friction, workarounds and, eventually, a capability that nobody trusts.
The three layers of AI operating model design
Across the organisations we have worked with, effective AI operating model design addresses three layers.
Capability architecture. Before selecting any AI tool, you need to understand your business capabilities, what you do, how well you do it and where AI creates real advantage. This is enterprise architecture applied to AI strategy, preventing the common trap of starting with technology and hoping it finds a problem to solve.
Process and role design. For every AI capability you introduce, the surrounding processes and roles need to be redesigned, settling who makes the decisions the AI used to support. The design also has to cover who oversees the AI's outputs and what happens when the AI gets it wrong. These are first-class design decisions rather than afterthoughts, and they determine whether the capability goes on to deliver value or to create risk.
Governance and accountability. Every AI capability needs clear ownership, defined performance metrics and a review cadence, and without those things capabilities drift and models degrade. Nobody notices until something goes wrong, so this layer is especially critical in regulated sectors, where accountability cannot be ambiguous.
Why this matters for mid-market businesses
Large enterprises can absorb operating model failures because they have enough resource and enough resilience to muddle through, and mid-market businesses cannot. A failed AI programme in a 500-person company means more than wasted investment, because it leaves lost momentum, eroded trust in technology-led change and a leadership team less likely to try again.
That is why we start with the operating model, not the technology. Getting the design right from the beginning means every AI capability you deploy has a home in the organisation, clear ownership and a pathway to value.
For the strategic framing that underpins this approach, see Why AI Strategy Must Lead Technology, and for an example of how operating model design works in practice within a compressed delivery model, see The 8-Day AI Sprint.
If your organisation is ready to design an AI operating model that actually works, Breathe is where we start, and Flow is where we build.