Odenia Programmes · Programme direction
What does an interim AI programme director do, and when should you hire one?
Why most AI programmes stall
95% of organisations report no measurable P&L impact from their generative AI investment; 5% of integrated pilots extract value.
(MIT NANDA, The GenAI Divide: State of AI in Business 2025, preliminary report, 52 interviews and 153 survey responses, July 2025)
In the same study, pilots run with an external partner reached deployment about 67% of the time, against about 33% for tools built internally.
(same source)
For task-specific generative AI tools: six organisations in ten investigated one, two in ten piloted one, one in twenty put it into production.
(same source)
The report's own diagnosis: the barrier is not infrastructure, regulation or talent. It is that most systems do not retain feedback, adapt to context, or improve over time.
(same source)
A programme director's job is to make your pilot the exception to those numbers: one owner, a scope that fits on a page, a vendor held to a date, and a P&L line the board can read.
Sources: https://cloudelligent.com/wp-content/uploads/2026/02/v0.1_State_of_AI_in_Business_2025_Report.pdf (public copy of the MIT NANDA v0.1 report)
What the role covers
- 1
Scope and business case. What the programme delivers, for whom, measured how, by when. Written before the first vendor meeting.
- 2
Governance. A steering committee that decides, a delivery cadence that reports, one place where risks are logged and owned.
- 3
Vendors and build partners. Selection, contracts, delivery dates, acceptance. The programme director sits on the client's side of the table.
- 4
Delivery. The roadmap executed milestone by milestone, with the internal team learning as it goes.
- 5
Obligations. EU AI Act classification, Article 50 disclosure, documentation and data protection built into the roadmap, not bolted on.
- 6
Handover. The operating model, the runbooks and the people who own the system after the mandate ends.
The signals that you need one
A pilot has been running for more than six months and nobody can say what it has changed.
The roadmap is written by the vendor.
The board has asked for the P&L case and the answer is a slide of use cases.
A merger, a carve-out or a platform migration has landed on the team that runs the business.
The person who should own the programme already has a full-time job.
When you do not need one
The question is where AI pays in your processes: that is an audit and roadmap, two to six weeks, fixed price once scoped.
The programme will run for years: recruit. An interim director holds the role while you do, and hands over to the hire.
The scope is one tool for one team: a delivery engagement, staffed to scope, is enough.
How it is priced, and who runs it
Programme direction is a day rate, three to five days a week, on a written scope: deliverables, cadence, governance and price. Start within two to four weeks. Every engagement is run by a director with ten or more years of experience on international IT and digital transformation programmes. The founder can step in on complex programmes that need particular attention.
your questions
Questions we get on the call
A consultant advises and leaves you the delivery. An interim programme director takes the delivery: the steering committee, the vendors, the dates, the decisions in between. You get a person accountable for the outcome, for a defined period.
Six to twelve months is typical, three to five days a week. Shorter for a carve-out or a migration with a fixed cutover date. The end date is in the scope.
Remote across the EU, on site for the moments that matter: kick-off, steering committees, cutovers.
Yes. The audit covers an existing AI layer: conversation logs, the funnel from first message to booking, the CRM handoff. Same format, same price logic.
The programme is handed over: operating model, runbooks, owners. If you have recruited during the mandate, the handover is to your hire.