Point of View
Strategy·15 August 2026·6 min readDesigning the AI Op Model
Before an organisation can delegate work to machines, it has to understand what it is delegating.
First published on LOWEMGMT ↗
Nobody should own AI, but somebody must own the decisions it makes. Most organisations are applying AI to their existing processes rather than redesigning the work around it, the same mistake early digital transformation made. This piece sets out the decisions, in order, that avoid repeating it.
Who owns AI here?
The Chief Data Officer thinks they do, and so does the CTO. The CFO owns the funding and general managers are busy using that to demonstrate their ability to integrate AI into their business functions. Ironically, the organisation chart doesn't define it; it only includes humans.
Nobody should own AI. But somebody must own the decisions it makes.
What's at stake
Only one in eight CEOs report that AI has influenced both revenue and costs positively (PwC), and about seven out of eight organisational leaders report that their organisations are not very well prepared to adopt AI in day-to-day operations (McKinsey). Those numbers point to something more interesting than an adoption problem. If this were simply a matter of buying better technology, the problem might have been solved by now.
Early digital programs often digitised existing processes before organisations learned to redesign the customer journey around what digital made possible. AI appears to be following a similar pattern. We are making existing tasks faster before asking the more consequential question: if intelligence becomes cheap, scalable and increasingly autonomous, how should the process work in the first place?
The lesson from past digital transformations is that applying technology to the same organisational design and processes only captures part of the value. Organisations that took a holistic approach and redesigned the experience rather than just applying technology to existing processes captured more of the opportunity. Yet despite the opportunity to redesign work, most leaders still expect AI to function primarily as a support tool over the next two years.
Where to start
Before an organisation can delegate work to machines, it has to understand what it is delegating.
This is where things get harder. Most organisations are far less explicit about how they actually operate than they think they are. Policies describe the normal case, but exceptions live in people's heads. Decision rights are often implicit. Process logic is embedded in systems, and experienced employees have learned how to navigate the gaps.
Humans can work around that ambiguity. Reliable autonomous agents need much more of it made explicit. This isn't necessarily a model problem. It is increasingly an organisational knowledge problem, and it should be treated and funded like infrastructure.
“Nobody should own AI. But somebody must own the decisions it makes.”
How to start, in order:
- Where will AI create disproportionate value? Which customer journeys, operational domains or decision systems matter enough that redesigning them could materially affect revenue, margin, risk or experience. Including past opportunities discarded as too hard.
- Who owns the outcome, the capability and the risk? For every priority domain, name the owner of the outcome, the process, the data, the enabling capability and the risk. They may not be the same person.
- How should the work be redesigned? Break the workflow into decisions and activities: which stay human-led, which become AI-assisted, AI-led with supervision, or eventually autonomous.
- Fund it as a P&L-owned capability on a shared platform, measured on outcomes. Funded as projects it dies as pilots, funded as a platform it loses business accountability.
- Design roles around what AI elevates: judgement, domain expertise, exception handling, relationship management and accountability, typically producing smaller, leaner teams.
Founder, LoweLabs
With more than 25 years’ experience across consulting, technology and industry, he has built and scaled multiple Data & AI practices, led complex transformation programs, and worked with some of Australia and Asia’s largest organisations. An INSEAD Global Executive MBA graduate, he combines commercial leadership, deep technical expertise and a practical understanding of how emerging technology can be turned into measurable business value.
First published on LOWEMGMT ↗
What separates a pilot from a product
The gap between a working demo and something people rely on.
Point of ViewEvaluating agents like you evaluate people
Why AgentOps borrows more from performance management than from software testing.
Field NoteSynthetic data, real judgement
Where synthetic profiles help, and where they quietly mislead.
Point of ViewWritten at the Wrong Altitude
Why your AI strategy keeps expiring, and why the next rewrite will not fix it.
Point of ViewThe Answer Is in the Portfolio
Eight figures on AI pilots, nothing on the P&L. Why "double down, redirect, or stop" is the wrong question.
Point of ViewNobody Should Own AI
The turf war between your CDO/CIO, CTO and CFO isn't a governance failure. It's a category error.
Next steps
Redesigning work around AI rather than bolting it on?
We help executive teams make the ownership, redesign and funding decisions that turn AI ambition into an operating model. Let's talk.