Chapter 15 ended with an adoption dashboard whose numbers someone has to act on. This chapter gives them a home by extending Management as Code to the AI portfolio. Architecture as Code (Chapter 19) argued that management intent, governance routines, and decision frameworks should be expressed as executable, version-controlled artefacts, and Chapter 23 of that volume showed how codified management interacts with culture and leadership (66, Nordqvist, 2025). AI programmes test that argument hard, because the value of an AI use case is uncertain until measured, the risk changes whenever the model or the data changes, and the organisation must report on both to boards and supervisory authorities. The chapter therefore shows how to run the portfolio as a register, track value, fund platforms and use cases, and steer and report on evidence produced by pipelines rather than on slides.
A conventional IT portfolio tracks projects with budgets, milestones, and status colours. An AI portfolio tracks hypotheses about where a probabilistic capability will create value, each of which may be disproved by evaluation, undermined by drift, or invalidated by a change in regulatory classification. Three properties follow. The portfolio changes faster than quarterly reviews can follow. Its state depends on technical evidence, such as evaluation scores, override rates, and cost per transaction, as much as on budget consumed. And it is itself a regulated artefact, because the inventory of AI systems that Chapter 9 described is the same list the steering committee funds and the same list from which high-risk systems must be registered under the AI Act.
Management as Code answers all three: a register in a repository changes as often as the use cases do, pipelines write evidence next to budget figures, and a schema lets one register serve governance, funding, and regulatory reporting.
Primary topics explored
- Why AI portfolios need Management as Code
- The use-case portfolio as a version-controlled register
- Managing the portfolio across the usage modes
- Value hypotheses and benefit tracking
- Objectives and key results for AI
- Funding models: platform versus use case
About AI Governance
AI Governance is Book 2 of The Transformed Architecture. It shows how large European enterprises and public authorities decide what artificial intelligence is used for, classify and manage its risks, meet the obligations of the EU AI Act and its neighbours, choose and contract their suppliers, organise the forums that take decisions, and produce the evidence that shows it is all true.
It builds on the conclusions of Architecture as Code.
Chief risk and compliance officers, AI governance boards, CIOs and chief architects, and senior officials in public authorities.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 16: Management as Code for AI Programmes in AI Governance gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Organisation and Leadership” and is one of 32 drawn from the manuscript.