Workers on scaffolding against a clear sky
Field note6 min read
All posts

AI transformation frameworks compared: which one is for what

The EU AI Act, ISO/IEC 42001, the NIST AI RMF and maturity models answer different questions. What each is for, what is mandatory, the AI Act dates after the 2026 Omnibus, and how I combine them in a programme.

Photo: Tuaans / Unsplash

On this page

    Early in almost every AI transformation programme someone asks which framework we are following. The candidates arrive in a pile: the EU AI Act, ISO/IEC 42001, the NIST AI Risk Management Framework, a maturity model from a consultancy, the cloud provider's adoption framework. Teams then spend weeks comparing them as if they had to pick one.

    They do not. These documents answer different questions, and most organisations need two or three of them, each for its own job. This post sets out what each one is for, what is mandatory and what is not, and how I combine them.

    The short answer: the EU AI Act tells you what you must do, by law, depending on the risk of each system and your role. ISO/IEC 42001 tells you how to run AI governance as a management system that an auditor can certify. The NIST AI RMF gives you a method for finding, measuring and managing the risks of a particular system. Maturity and adoption models help you decide what to do next. None of them tells you whether a given AI investment pays off; that needs its own evidence.

    The frameworks at a glance

    Which framework answers which question

    EU AI ActWhat must we do, by law, for each AI system?Yes, for AI placed on the market or used in the EUNo; conformity assessment for some high-risk systemsIn force since August 2024; amended by the AI Omnibus in July 2026
    ISO/IEC 42001How do we run AI governance so it can be audited?NoYes, by accredited certification bodiesPublished December 2023
    NIST AI RMF 1.0How do we find, measure and manage the risks of a system?NoNoPublished January 2023; Generative AI Profile July 2024; revision in progress
    Maturity and adoption models (Microsoft, Google, Gartner)Where are we, and what should we do next?NoNoVendor documents, tied to their products or paid research
    OECD AI PrinciplesWhich values should guide AI use?NoNoAdopted 2019, updated May 2024

    Most organisations operating in Europe need the first three in some form, and one roadmap model.

    Source: European Commission; ISO; NIST; Microsoft; Google; Gartner; OECD (all accessed October 2026)

    Download the data (CSV)

    They also depend on each other, which is easier to see as a map:

    How the frameworks fit together

    setsgives presumption of conformity for Article 17designed to layer ondefinessets rules for certifyingguidesprofiles for generative AIfeedsevidencesEU AI ActLegal obligationsEN 18286ISO/IEC 42001Management systemISO/IEC 42006NIST AI RMFRisk assessmentNIST AI 600-1

    Hover an entity to see what it connects to. The harmonised standard EN 18286 is the formal bridge between ISO-style management systems and the AI Act. Maturity models sit outside this map: they plan the roadmap rather than define obligations or controls.

    Source: European Commission (October 2026); ISO; NIST

    Download the data (CSV)

    Show the data
    SourceRelationTarget
    EU AI ActsetsLegal obligations
    EN 18286gives presumption of conformity for Article 17EU AI Act
    EN 18286designed to layer onISO/IEC 42001
    ISO/IEC 42001definesManagement system
    ISO/IEC 42006sets rules for certifyingISO/IEC 42001
    NIST AI RMFguidesRisk assessment
    NIST AI 600-1profiles for generative AINIST AI RMF
    Risk assessmentfeedsManagement system
    Management systemevidencesLegal obligations

    EU AI Act: obligations by risk and role

    The AI Act is law, and it applies to providers, deployers, importers and distributors, including companies outside the EU whose AI is used inside it (European Commission). Obligations depend on the risk tier of each system and on your role. In July 2026 the AI Omnibus amended it, most visibly by moving the high-risk deadlines (legislative record). The dates as they stand now, also kept up to date in EU AI Act dates and guidance, tracked:

    EU AI Act: what applies when

    1 August 2024The Act enters into force
    2 February 2025Prohibited practices and the AI literacy duty
    2 August 2025Obligations for general-purpose AI models, and governance
    2 August 2026General application: transparency rules (Article 50) and enforcement
    2 December 2026New ban on systems that generate non-consensual intimate images or child sexual abuse material; marking deadline for generative systems already on the market
    2 December 2027High-risk systems in Annex III, such as employment, education, biometrics and critical infrastructure (originally 2 August 2026)
    2 August 2028High-risk AI in regulated products under Annex I, such as medical devices and machinery (originally 2 August 2027)

    As amended by the AI Omnibus, Regulation (EU) 2026/1744, in force since 27 July 2026.

    Source: European Commission, AI Act Service Desk: Timeline for the implementation of the EU AI Act

    Download the data (CSV)

    Two details matter for planning. The AI literacy duty survived the Omnibus in a softer form: providers and deployers must take measures to support their staff's AI literacy, without having to guarantee any particular level (Article 4). And the fines are large enough to put the Act on a board agenda: up to EUR 35 million or 7% of worldwide turnover for prohibited practices, and up to EUR 15 million or 3% for most other obligations, with lower caps for small companies (Article 99).

    What the Act does not give you is a way of working. It says what must be true, for example a quality management system for high-risk providers, not how to organise the people and processes that make it true. That is where the next two come in.

    ISO/IEC 42001: governance you can audit

    ISO/IEC 42001, published in December 2023, is a management system standard for AI, built the same way as ISO 27001 for information security: policies, objectives, roles, risk treatment, internal audit and continual improvement (ISO). It is not mandatory: the AI Act does not require it, and certification is voluntary and done by independent certification bodies, not by ISO itself (ISO), and a companion standard, ISO/IEC 42006 from July 2025, sets the rules for those bodies (ISO/IEC 42006).

    Its value is that it turns good intentions into a repeatable, evidenced process, which is what customers and procurement teams increasingly ask for. AWS, Google Cloud, Microsoft and Anthropic have all announced certifications for their AI services. In October 2026 the first harmonised standard under the AI Act, EN 18286 for quality management, was published in the Official Journal; the Commission describes it as designed to be layered on top of standards such as ISO/IEC 42001 (European Commission). A 42001 certificate on its own does not give the legal presumption of conformity that the harmonised standard does, but it is a natural starting point.

    NIST AI RMF: a method for risk

    The NIST AI Risk Management Framework is voluntary, not tied to any sector or use case, and not certifiable (NIST). It organises risk work into four functions: Govern sets the culture, policies and accountability and runs through everything else; Map establishes the context of a system and its risks; Measure analyses, tests and monitors them; Manage allocates resources to the risks found and responds to incidents. Its Generative AI Profile (NIST AI 600-1, July 2024) lists twelve risks that generative AI creates or makes worse, from confabulation and data privacy to information security and value chain integrity, each with suggested actions.

    I use it as the working method for assessing individual systems, because it is free, practical and maps cleanly onto both ISO and the AI Act. ISO/IEC 42001 against the NIST AI RMF, in one line: 42001 is the management system an auditor certifies, the RMF is the method for assessing each system inside it. One caveat: following the US AI Action Plan of July 2025, NIST is revising the framework, and as of October 2026 it says a revised version is in progress without having published one (NIST). The four functions are unlikely to change, but check for the new version before you build templates around specific subcategories.

    Maturity and adoption models: where to go next

    The roadmap layer comes mostly from vendors and analysts, and each names its stages differently:

    Three maturity and adoption models

    Microsoft Cloud Adoption Framework for AIPlan, Ready, Govern, Secure, ManagePractical and current (updated October 2026), but built around Azure
    Google Cloud AI Adoption FrameworkTactical, Strategic, Transformational, across six themes: Learn, Lead, Access, Scale, Automate, SecureUseful structure, but from 2020, before generative AI
    Gartner AI Maturity ModelFoundational, Emerging, Operational, Scaled, Transformational, across seven pillarsFull model is for paying clients

    Source: Microsoft Learn; Google Cloud whitepaper (2020); Gartner AI maturity model toolkit

    Download the data (CSV)

    Gartner reports that 45% of organisations with high AI maturity keep AI projects in production for at least three years, against 20% of those with low maturity (Gartner, June 2025). That is a correlation from a survey of 432 organisations, not proof that climbing the model causes success, but it fits what I see: mature organisations are better at stopping weak projects early and keeping good ones running.

    How I combine them

    A practical combination

    Inventory and classify every AI systemEU AI Act risk tiers and rolesA register with tier, role and owner per system
    Set up accountability and policiesISO/IEC 42001, or NIST Govern if certification is not neededAI policy, roles, approval and audit process
    Assess each system before launchNIST Map and Measure, with the Generative AI ProfileRisk assessment and test results per system
    Design technical controlsNIST Manage, informed by the architectureIdentity, logging, approvals and rollback built in
    Plan the roadmapOne maturity model, used as a checklistNext two quarters of capability work
    Decide which investments to fundNone of the aboveA business case with evidence and a pilot threshold

    The last row is the gap: no governance framework tells you whether an AI investment pays off.

    Download the data (CSV)

    The technical controls row is where governance meets architecture: delegated identity, drafts by default, tested rollback and measured reliability, as described in Agentic AI from demo to production. The funding row needs evidence of effect, which is thinner than most plans assume; see Does AI make developers faster? What the controlled studies say, what the MIT NANDA report's 95% actually measured, and Klarna's AI customer service; for the decision itself, A GraphRAG business case, done the evidence-based way, whose structure works for any AI investment.

    How much weight this evidence deserves

    Appraising the evidence

    EU AI Act and Commission guidanceAuthoritative: it is the lawGuidance and standards are still arriving; dates have already moved once
    ISO/IEC 42001 and NIST AI RMFBroad expert consensus on good practiceLittle rigorous evidence that adopting them improves AI outcomes
    Vendor and analyst maturity modelsUseful structureCommercial interests; survey correlations, not causation
    My programme workDirect experienceOne practitioner

    Download the data (CSV)

    Sources

    How to cite

    Ivan Bardak. "AI transformation frameworks compared: which one is for what". bardak.ai, October 29, 2026. https://bardak.ai/posts/ai-transformation-frameworks-compared

    Data behind the charts (JSON)

    Discussion