AI operating model options
Chooses how to structure AI ownership — centralised, federated, hub-and-spoke or embedded — against the organisation's size, maturity and portfolio, not against what looks impressive.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
Compares four structural options for owning and running AI capability as it moves from experiment to production, tested against the organisation's actual size, maturity and portfolio shape rather than against whichever model looks most sophisticated on paper.
- Centralised
- A single team owns AI capability and delivers it as a service to the rest of the organisation. Fastest to build genuine expertise; slowest to embed AI into the specific judgement each function needs.
- Federated
- Each function builds and owns its own AI capability independently. Fastest to embed in specific judgement; slowest to build deep expertise and likely to duplicate effort across functions.
- Hub-and-spoke
- A central team sets standards, tooling and governance while embedded specialists in each function do the applied work. The most common landing point for organisations past the earliest stage, and the most complex to run well.
- Fully embedded
- AI capability dissolved entirely into existing functional teams with no central coordination at all. Rare, and usually only right for organisations where AI has become simply part of how every function already works.
- The fit test
- Chosen against the organisation's actual size, maturity and how concentrated or spread the AI portfolio is — not against which model is currently fashionable.
- Revisit trigger
- A stated point — a maturity threshold, a portfolio size, a specific initiative — at which the model should be reconsidered, because the right model at experiment stage is rarely the right one at scale.
How you run it
- Map current AI activity and who runs itEvery initiative in flight or in production, and its current ownership — the honest starting point rather than the aspiration.
- Score the organisation's size and maturityAgainst each of the four models' actual requirements — a hub-and-spoke model needs a scale of AI activity a small federated effort does not yet have.
- Compare the four models against that specific fitNot against which model looks most sophisticated. The right model for a twenty-person organisation is frequently not the right model for a group with a dozen business units.
- Choose and name the model, stating the trade-off acceptedEvery model trades speed against depth, or coordination against duplication. State explicitly what was given up.
- Set a revisit triggerA maturity threshold or portfolio size at which the choice should be reconsidered — because the right model at experiment stage is rarely the right one at scale.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- The current AI initiatives in flight or in production, and who currently runs each
- The organisation's size and existing operating model conventions for other capabilities
- How the AI portfolio is expected to grow over the next twelve to eighteen months
You’ll end up with
- The operating model that fits the organisation as it is now, chosen and named
- The trade-offs of that choice stated explicitly, not glossed over
- A stated trigger for when the model should be revisited