Skip to content

Insight · 7 min read · 30 July 2026

Six operating-model gaps

Pilots prove that something works in principle. Production requires an operating model. Six gaps explain most of the distance between a promising demo and a capability the business actually runs on.

Placeholder content

Draft: awaiting a named author and editorial review before publication.

'Pilot purgatory' is not a technology problem. In most organizations we meet, the pilots worked: approximately, for the people who built them, on the data they were given. What is missing is the operating model that turns a working demonstration into a run-and-improved capability. Six gaps recur.

1. No production owner

The pilot had a project team; the product needs an owner: someone accountable for its quality, cost and value next quarter, with budget and authority to change it. When the delivery team disbands and no owner exists, the system decays until someone quietly turns it off.

2. Evaluation was a launch event, not an operation

Pilots are evaluated once, before the decision. Production systems drift: source documents change, usage shifts, models get updated. Without continuous evaluation (automated checks plus periodic human review against a defined standard), quality degrades invisibly and trust follows.

3. The workflow was never redesigned

Dropping an assistant next to an unchanged process produces optional AI, used by enthusiasts and ignored by everyone else. Adoption follows when the surrounding workflow is redesigned so the AI-supported path is the default path, with the human decision points made explicit.

4. Data foundations were borrowed, not built

Pilots run on extracts and workarounds. Production needs governed access, refresh, lineage and quality ownership for exactly the data products the use case consumes. Not a multi-year data program, just the specific foundations this capability requires.

5. Governance arrived at the end

When risk, security and legal review a finished pilot, the only available answers are 'no' or 'redo it'. Intake classification, control requirements and evaluation evidence designed in from the start make approval a checkpoint rather than a renegotiation.

6. Value was never measured against a baseline

If nobody recorded what the process cost before, nobody can defend what the system saves now, and the capability loses the budget argument to whatever is measured. A baseline taken before the pilot is the cheapest insurance an AI investment can buy.

None of these gaps is closed by better models. They are closed by treating AI capabilities as products inside an operating model: owned, measured, governed and improved. That is the work between the pilot and the advantage.

Related reading

Posts that share a subject with this one.

Facebook Ads Agent Case Study
10 min readCase Study

Facebook Ads Agent Case Study

This case study walks through the full lifecycle of a Facebook Ads Agent, from first idea to a fully operational agentic system running in production. The agent is made up of a small team of specialists, a defined set of inputs, a strict list of things it's allowed to touch inside Meta, and a governance layer that keeps its behaviour in check. But the thing that matters most is the data feeding the agent and what business context we give it. If we fail to define a proper business scope for the agent, it will optimise a metric that could hurt the business. For example, if we ask the agent to drive revenue, it might push a product that has a 40% return rate. So if it doesn't have the right scope, it will develop tunnel vision.

Scoring AI value, feasibility and risk
6 min readInsight

Scoring AI value, feasibility and risk

Most enterprises have a list of AI ideas. Far fewer have a portfolio: a scored, sequenced set of investments with owners and decision gates. The difference determines whether AI spending compounds or fragments.