AI Platform and Security · Module 5 · Delivery and Operations

From Pilot to Production: Scaling AI Across the Organisation

The lesson explains why AI pilots stall and how to codify the path from idea to governed production service. Participants learn the pilot trap and its causes, the platform as a product with golden paths, the intake record and four prioritisation criteria, the production readiness review as a gate mapped to Article 26 of the AI Act, the go or no-go decision record with stop criteria, the closing of pilots that do not proceed, and measures of industrialisation.

Lesson 23 of 25Chapter 2390 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Platform and Security / Module 5 / Chapter 23

Learning objectives

After the lesson the participant can:

Key concepts

Pilot trap
The state in which an organisation can start AI initiatives but not finish them: proofs of concept with no owner, model code in a notebook on a laptop, and no funding. The chapter calls it a failure of architecture, not of talent.
Golden path
A documented, templated, supported way of building a particular kind of AI service with the controls already wired in. A team that leaves it must prove equivalence at the readiness review.
Intake record
A short structured file in the use-case portfolio repository with sponsor, value hypothesis, decision impact, data sources, likely AI Act role and prioritisation scores. It makes the decision to proceed reviewable and seeds the risk classification.
Production readiness review
The gate between a pilot and a service: a codified checklist whose items are verified by evidence in the repository, most of them automatically. An item passes, fails, or passes with a recorded exception that has an owner and an expiry.
Stop criteria
Conditions in the go-live decision record, measurable from the observability configuration verified at the gate, any one of which triggers rollback. A rollback then depends on a threshold and not on a meeting.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Match

Deployer obligations and their evidence

Match each obligation of Article 26 of the AI Act with the evidence in the repository that the chapter's checklist names.

Interactive exercise 2 · Scenario

A pilot that will not proceed

Apply the chapter's guidance on closing pilots to a decision in an organisation like yours.

Teaching plan

10 minThe teacher asks how many pilots participants' organisations have started and how many are in production, then names the symptoms of the pilot trap.
20 minRead Hansa Mutual's golden path manifest and intake record UC-2026-014; participants mark which fields do work later at the gate.
15 minWalk the readiness checklist against the Article 26 table and the result of Hansa Mutual's gate run with its two exceptions and one failure.
35 minExercise: groups run a readiness review on a real pilot and write the go or no-go record, including the option they rejected.
10 minClose with how to close a pilot that will not proceed and with the four measures of flow.

Discussion

  1. The single failure in Hansa Mutual's gate run belonged to the business owner: nobody had agreed the baseline that defines success. Who would fail that check for your current pilots?
  2. Reuse potential is the prioritisation criterion most organisations omit. Which of your proposed use cases would force the platform to add a capability the next five also need?
  3. What do your abandoned pilots still hold in the way of data extracts, credentials and indexes, and who is responsible for closing them?

Written exercise

Exercise · 35 minutes

Readiness review and go or no-go record

Take a pilot in your own organisation, or Nordvik Region's staff assistant before its scale-out. Write its intake record with value hypothesis, baseline and target, decision impact, data sources, likely AI Act role and the four prioritisation scores. Then run a readiness review with at least eight checks drawn from the chapter's table and checklist; for each give the evidence location, whether it is automated, and the result as pass, fail or pass with exception, naming an owner, an expiry and a compensating control for each exception. Finally write the decision record: at least two options, the decision, conditions, three measurable stop criteria and who accepts the residual risk.

Deliverable: An intake record, a readiness checklist with results and exceptions, and a go or no-go decision record with stop criteria and a named accountable owner.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. What is the deeper cause of stalled pilots, according to the chapter?

    Show the answer

    C. Most pilots are built beside the enterprise estate, so controls must be retrofitted at higher cost
    A pilot in a sandbox with its own identity model and logging has no path to production; the question is whether it was built on a path that can carry it there without being rebuilt.

  2. What happens at the readiness gate when an item's evidence is missing or older than the last model or prompt change?

    Show the answer

    A. The pipeline blocks deployment unless an exception is recorded with an owner and an expiry
    The review is a gate, not a meeting, and an expired exception fails the gate like a missing artefact.

  3. Which option did Hansa Mutual choose in the go-live decision AIDR-0034 for the claims triage assistant?

    Show the answer

    B. A conditional go: property claims only, 30 per cent of handlers, for six weeks
    The record keeps the rejected options, sets conditions such as closing the two exceptions before expansion, and lists stop criteria that trigger rollback to manual triage.