Data Governance Frameworks: 13 Models Compared and Ranked by Industry (2026 Guide)

There is no best data governance framework. There is only the best fit for your industry, your data maturity and your exposure to AI.
Most organisations lose months debating DAMA against DCAM, or COBIT against NIST, as if one framework will settle every question. It will not. Each was built to solve a different problem: some describe the whole discipline of data management, some define who makes decisions, and some exist to satisfy auditors. Choosing the wrong one does not create an immediate failure. It creates a slow one, as governance drifts away from what the business needs.

This guide compares 13 data governance frameworks on a single scorecard, ranks them by fit for each industry, and adds the layer most comparisons miss: governance for AI.

‍

TL;DR: A data governance framework is the model of roles, policies, processes and standards an organisation uses to manage its data. There is no single best framework: financial services should start with DCAM, healthcare with DAMA-DMBOK and the NIST Privacy Framework, universities with DGI, and engineering-led SaaS firms with federated, data mesh governance. Add an AI governance layer, such as NIST AI RMF or ISO/IEC 42001, before AI touches governed data, and start with one domain rather than the whole enterprise.

‍

Key takeaways
  • A data governance framework is the structured model of policies, roles, processes and standards that determines how an organisation manages its data.
  • No single framework is complete. Strong programmes combine a core framework, an operating-model edge and an AI governance layer.
  • Financial services should start with DCAM, healthcare with DAMA-DMBOK plus the NIST Privacy Framework, and engineering-led SaaS firms with federated, data mesh governance.
  • Classic data governance frameworks were not designed for models that act on data. NIST AI RMF and ISO/IEC 42001 fill that gap.
  • Start with one domain and one measurable business problem. Tools come after people and process.
What is a data governance framework?

A data governance framework is a structured model that defines how an organisation manages its data: who owns it, who may use it, which rules apply, and how compliance is proven. It turns governance from a set of good intentions into decisions, roles and controls that operate every day.

Three terms are often confused:

  • Framework: the reference model, such as DAMA-DMBOK or DCAM, that describes what good looks like.
  • Programme: the organisation’s own implementation of that model, with named people, budgets and milestones.
  • Policy: a single enforceable rule inside the programme, such as a data retention or classification policy.

‍

What are the components?

The components of a data governance framework are broadly consistent across models, even when the names differ:

  • People and roles: a governance council, data owners accountable for domains, and data stewards who maintain quality day to day.
  • Policies and standards: rules for definition, classification, access, retention and quality.
  • Processes: how issues are raised, decisions made, exceptions approved and changes communicated.
  • Technology: catalogues, lineage, quality monitoring and access controls that make the rules enforceable.
  • Metrics: measures that show whether governance improves outcomes, not just whether policies exist.

Informatica frames the same idea as readiness pillars of people, processes, contributors and technology. The labels matter less than the principle: governance fails when any one of these is missing.

‍

Data governance frameworks: breadth vs. effort

Hover or tap a framework for details. Choose an industry to see the recommended core and complement.

Quadrant chart of 13 data governance frameworks, plotted by maturity and effort needed (horizontal) and breadth of coverage (vertical). A table version follows the chart.

Select a framework on the chart to see its summary.

Positions are Forte Group’s assessment based on each framework’s scorecard, October 2026. Breadth reflects how much of data management a framework covers; effort reflects the maturity and investment needed to adopt it.

View as table
FrameworkQuadrantMaturity neededAI coverageBest for
DAMA-DMBOKComprehensive, heavy liftMediumPartialA comprehensive core standard and shared vocabulary
DCAMComprehensive, heavy liftHighPartialAssessable, regulator-ready data management capability
COBIT 2019Comprehensive, heavy liftHighPartialLinking data to IT risk, controls and audit
Federated / data meshComprehensive, heavy liftHighStrongDomain ownership with automated, policy-as-code guardrails
PwC frameworkComprehensive, heavy liftMediumNoneLinking governance to enterprise risk and external audit
Eckerson GroupBroad, lighter liftLowPartialLean, modular governance
DGI FrameworkBroad, lighter liftLow to mediumNoneDesigning decision rights and accountability
BCG modelBroad, lighter liftMediumNoneGovernance inside a digital transformation programme
DGPO Best PracticesFocused, lighter liftLow to mediumNonePractical, vendor-neutral guidance and templates
SAS frameworkFocused, lighter liftMediumNoneAligning governance with corporate goals and analytics programmes
ISO/IEC 38505-1Focused, lighter liftMediumNoneBoard-level oversight of data
NIST Privacy FrameworkSpecialist, heavy liftMediumPartialManaging privacy risk in a structured way
CDMCSpecialist, heavy liftMedium to highPartialGoverning sensitive data in cloud environments

‍

Data governance frameworks at a glance

The 13 frameworks below fall into five types. Use this table to shortlist, then read the detailed scorecards that follow.

Data governance frameworks at a glance: publisher, type, best use, maturity needed and AI coverage for 13 frameworks
Framework Publisher Type Best for Maturity needed AI coverage
DAMA-DMBOK DAMA International Comprehensive A shared standard and vocabulary across the whole data discipline Medium Partial
DCAM EDM Council Comprehensive Assessable, evidenced capability for regulated finance High Partial
CDMC EDM Council Comprehensive (cloud) Controlling sensitive data in cloud environments Medium to high Partial
DGI Framework Data Governance Institute Governance-specific Decision rights and accountability Low to medium None
DGPO Best Practices DGPO Governance-specific Practitioner guidance from a vendor-neutral association Low to medium None
ISO/IEC 38505-1 ISO/IEC Governance-specific Board-level oversight of data Medium None
COBIT 2019 ISACA IT, risk and audit Linking data to IT controls and audit High Partial
NIST Privacy Framework NIST Privacy risk Managing privacy risk, especially in the US Medium Partial
BCG model Boston Consulting Group Consultancy model Governance within digital transformation Medium None
PwC framework PwC Consultancy model Linking governance to enterprise risk and audit Medium None
SAS framework SAS Vendor model Tying governance to corporate goals Medium None
Eckerson Group Eckerson Group (now Datalere) Modular model Lean governance for smaller teams Low Partial
Federated / data mesh Operating model Operating model Domain ownership with automated guardrails High Strong

‍

The 13 data governance frameworks, compared

Each framework below follows the same structure: what it is, a scorecard, and where it falls short. Scores reflect Forte Group’s assessment against each publisher’s documentation as of October 2026.

Comprehensive data management frameworks describe the whole discipline, with governance at the centre. They make the strongest core.

1. DAMA-DMBOK

DAMA-DMBOK is DAMA International’s Data Management Body of Knowledge, the most widely used reference for data management practice. It treats governance as the hub connecting every other discipline, from data quality and metadata to architecture and security. The current edition is DMBOK2, revised in 2024 with expanded data ethics coverage. A third edition, DMBOK 3.0, is in development and will add AI, cloud and modern data platforms.

Its greatest strength is a common vocabulary. When business and technical teams use DMBOK terms, arguments about definitions give way to decisions. It also underpins the Certified Data Management Professional (CDMP) credential, which makes it the default language of data management hiring.

Scorecard: DAMA-DMBOK
PublisherDAMA International (DMBOK)
Best forA comprehensive core standard and shared vocabulary
IndustriesAll; strongest in healthcare, retail, manufacturing
Maturity neededMedium
Effort to adoptMedium
Regulatory fitGeneral; maps to GDPR, HIPAA and CCPA requirements through its policies
AI coveragePartial (ethics today; AI in DMBOK 3.0)
Pairs well withDGI for decision rights; NIST AI RMF for AI

Where it falls short: DAMA-DMBOK is a body of knowledge, not an implementation plan. Teams must decide sequencing and scope themselves.

2. DCAM (Data Management Capability Assessment Model)

DCAM is the EDM Council’s capability assessment model for data management, built by and for financial institutions. The EDM Council now operates as the EDM Association. Version 3 organises data management into 8 components, 34 capabilities and 101 sub-capabilities, each of which can be scored.

That scoring is the point. DCAM lets an organisation measure its maturity, benchmark against peers and show regulators structured evidence of progress. The EDM Council positions it as support for meeting requirements such as BCBS 239, the Basel Committee’s principles for risk data aggregation, and GDPR.

Scorecard: DCAM
PublisherEDM Council (DCAM)
Best forAssessable, regulator-ready data management capability
IndustriesBanking, insurance, asset and wealth management
Maturity neededHigh
Effort to adoptHigh
Regulatory fitBCBS 239, GDPR, SOX
AI coveragePartial
Pairs well withCOBIT for IT controls; CDMC for cloud

Where it falls short: the full model is available to member firms, and its depth is excessive for smaller or non-financial organisations.

3. CDMC (Cloud Data Management Capabilities)

CDMC is the EDM Council’s framework for managing and protecting sensitive data in the cloud. Launched in September 2021, it defines 14 Key Controls covering areas such as data ownership, cataloguing, classification, entitlements, lineage and retention. Cloud providers and technology vendors helped shape it, so the controls translate directly into platform configuration.

CDMC answers a question DCAM and DAMA leave open: how governance should work when data lives across multiple cloud services and is copied faster than any manual process can track.

Scorecard: CDMC
PublisherEDM Council (CDMC)
Best forGoverning sensitive data in cloud environments
IndustriesRegulated firms migrating to or operating in the cloud
Maturity neededMedium to high
Effort to adoptMedium
Regulatory fitPrivacy and data residency regulations; supports DCAM evidence
AI coveragePartial
Pairs well withDCAM or DAMA-DMBOK as the core

Where it falls short: CDMC is scoped to cloud. It is a control layer, not a complete governance operating model.

Governance-specific and organisational frameworks focus on who decides, who is accountable and how authority flows. They are lighter than the comprehensive models and often sit alongside them.

4. DGI Data Governance Framework

The DGI Data Governance Framework, from the Data Governance Institute, is a governance-specific model built around decision rights and accountability. It has 10 components: mission and value, beneficiaries, data products, controls, accountabilities, decision rights, policy and rules, processes and tools, a data work programme, and participants.

Its value is clarity. Most governance programmes stall not because the rules are wrong, but because nobody knows who has the authority to approve, reject or escalate. DGI answers that question before any technology is purchased.

Scorecard: DGI Data Governance Framework
PublisherData Governance Institute (DGI framework)
Best forDesigning decision rights and accountability
IndustriesMid-to-large enterprise, higher education, public sector
Maturity neededLow to medium
Effort to adoptLow to medium
Regulatory fitGeneral
AI coverageNone
Pairs well withDAMA-DMBOK for technical depth

Where it falls short: DGI is light on technical controls such as lineage, quality monitoring and access enforcement.

5. DGPO Data Governance Best Practices Framework

The DGPO framework is a set of practitioner best practices from the Data Governance Professionals Organization, a non-profit, vendor-neutral association. It organises guidance into six categories: fundamentals, organisation, process, metrics, communication and stewardship.

DGPO is useful for teams that want proven practices rather than a theoretical model. Its emphasis on communication and metrics addresses two areas where many programmes quietly fail.

Scorecard: DGPO Best Practices Framework
PublisherData Governance Professionals Organization (DGPO)
Best forPractical, vendor-neutral guidance and templates
IndustriesCross-industry
Maturity neededLow to medium
Effort to adoptLow
Regulatory fitGeneral
AI coverageNone
Pairs well withDGI or DAMA-DMBOK

Where it falls short: detailed materials are largely members-only, and regulators recognise it less than DCAM or COBIT.

6. ISO/IEC 38505-1

ISO/IEC 38505-1 is the international standard for governance of data at board level. It applies the principles of ISO/IEC 38500, the standard for governance of IT, to how governing bodies oversee the use of data. ISO published a second edition, ISO/IEC 38505-1:2026, in August 2026, replacing the 2017 version.

This is the framework for directors, not data teams. It defines what a board should evaluate, direct and monitor, which makes it valuable where accountability must be demonstrated at the top of the organisation.

Scorecard: ISO/IEC 38505-1
PublisherISO/IEC (ISO/IEC 38505-1:2026)
Best forBoard-level oversight of data
IndustriesPublic sector, large and listed enterprises
Maturity neededMedium
Effort to adoptLow to medium
Regulatory fitSupports governance and accountability obligations generally
AI coverageNone
Pairs well withDGI for operating detail; ISO/IEC 42001 for AI

Where it falls short: it sets principles, not operating procedures. A board can adopt it without changing how data is managed day to day.

IT, risk and privacy frameworks approach data governance through controls, audit and risk management. They are rarely enough on their own but are often mandatory in regulated industries.

7. COBIT 2019

COBIT, from ISACA, is a framework for the governance and management of enterprise information and technology. COBIT 2019 remains the current version. It is not a data governance framework in the narrow sense, but its control objectives, performance measures and audit orientation make it the common language between IT, risk and internal audit.

Organisations that already use COBIT for IT governance can extend it to data rather than introduce a second, competing control model.

Scorecard: COBIT 2019
PublisherISACA (COBIT)
Best forLinking data to IT risk, controls and audit
IndustriesFinancial services, regulated enterprise
Maturity neededHigh
Effort to adoptHigh
Regulatory fitSOX, internal audit, IT general controls
AI coveragePartial
Pairs well withDCAM or DAMA-DMBOK for data-specific depth

Where it falls short: COBIT is IT-centric. Business data owners often find it abstract and disconnected from their daily decisions.

8. NIST Privacy Framework

The NIST Privacy Framework is a voluntary tool from the US National Institute of Standards and Technology for managing privacy risk. Version 1.0, released in January 2020, remains the final version; a draft version 1.1 was published in April 2025. It is organised around five functions: Identify-P, Govern-P, Control-P, Communicate-P and Protect-P.

It is designed to work alongside the NIST Cybersecurity Framework, which makes it a natural choice for organisations already using NIST for security.

Scorecard: NIST Privacy Framework
PublisherNIST (Privacy Framework)
Best forManaging privacy risk in a structured way
IndustriesUS government and contractors, healthcare, regulated sectors
Maturity neededMedium
Effort to adoptMedium
Regulatory fitHIPAA, CCPA/CPRA, GDPR principles
AI coveragePartial
Pairs well withDAMA-DMBOK as the core; NIST AI RMF for AI

Where it falls short: it covers privacy, not data quality, metadata or architecture.

Consultancy and vendor models translate governance into strategy, operating models and business language. They are useful as an edge around a core framework, not as a replacement for one.

9. BCG Data Governance Model

The BCG data governance model, from Boston Consulting Group, treats governance as part of a wider digital transformation. It typically structures governance around data structures, policies, tools and a target operating model, with a data management office led by a Chief Data Officer coordinating owners and stewards.

Its strength is executive framing. It positions governance as a driver of business value rather than a compliance cost, which helps secure sponsorship.

Scorecard: BCG model
Best forGovernance inside a digital transformation programme
IndustriesLarge enterprise
Maturity neededMedium
AI coverageNone
Pairs well withDAMA-DMBOK for operational detail

Where it falls short: it is strategic and high level, with limited guidance on day-to-day controls.

10. PwC Enterprise Data Governance Framework

The PwC framework connects data governance to enterprise risk management and audit readiness. It is commonly described in five parts: governance strategy, enterprise data management, data lifecycle management, data stewardship and governance enablers, starting from a maturity and gap assessment.

Scorecard: PwC framework
Best forLinking governance to enterprise risk and external audit
IndustriesRegulated, audit-heavy organisations
Maturity neededMedium
AI coverageNone
Pairs well withCOBIT or DCAM

Where it falls short: adoption tends to be consultancy-led, and public documentation is limited.

11. SAS Data Governance Framework

The SAS data governance framework links governance directly to corporate objectives to secure executive support. It covers governance strategy and decision rights, stewardship and data management, and the people, processes and technology that enforce policy.

Scorecard: SAS framework
Best forAligning governance with corporate goals and analytics programmes
IndustriesAnalytics-heavy organisations
Maturity neededMedium
AI coverageNone
Pairs well withDAMA-DMBOK

Where it falls short: it is associated with a technology vendor, which some organisations prefer to avoid when choosing a neutral standard.

12. Eckerson Group Modern Data Governance Framework

The Eckerson Group framework, described by Dave Wells in 2019, is a modular model with six layers: goals, methods, people, processes, technology and culture. Each layer breaks down into detailed components that organisations select and configure for their own context. Eckerson Group is now part of Datalere.

It is the most flexible framework in this guide. For lean teams, it provides structure without the overhead of a comprehensive model.

Scorecard: Eckerson Group framework
PublisherEckerson Group, now Datalere (framework article)
Best forLean, modular governance
IndustriesSMEs, agile teams, private equity portfolio companies
Maturity neededLow
AI coveragePartial
Pairs well withDAMA-DMBOK as a reference

Where it falls short: auditors and regulators know it less well than DCAM, COBIT or DAMA-DMBOK.

What about McKinsey and Gartner data governance frameworks?

McKinsey and Gartner are frequently searched in connection with data governance, but neither publishes a formal framework comparable to DAMA-DMBOK or DCAM. Both publish research and guidance. Gartner, for example, argues for adaptive governance that varies its approach by context rather than imposing one model everywhere. Treat their material as strategic input to a framework choice, not as the framework itself.

Operating-model approaches change where governance lives in the organisation rather than what it contains.

13. Federated (data mesh) governance

Federated governance is an operating model in which domain teams own their data while a central body sets shared standards that are enforced automatically. It comes from Zhamak Dehghani’s data mesh principles, the fourth of which is “federated computational governance”.

The word that matters is computational. Policies are written as code and run inside data pipelines: data contracts, automated quality checks and access rules that execute in CI/CD rather than in review meetings. Domain teams move quickly because the guardrails are built in, not bolted on.

This is the model Forte Group recommends for engineering-led organisations. Governance should be enablement, not control. When engineers trust the data and the rules enforce themselves, governance accelerates delivery instead of slowing it.

Scorecard: Federated / data mesh governance
OriginData mesh principles (Dehghani, 2020)
Best forDomain ownership with automated, policy-as-code guardrails
IndustriesSaaS and technology, multi-division enterprise, logistics
Maturity neededHigh
Effort to adoptHigh
Regulatory fitStrong where policies are encoded and auditable
AI coverageStrong
Pairs well withDAMA-DMBOK for shared definitions; ISO/IEC 42001 for AI

Where it falls short: it depends on mature platform engineering and disciplined domain teams. Without both, decentralisation creates fragmentation rather than speed.

‍

Which framework is best for your industry?

This depends on the industry’s regulatory pressure, its data shape and how its teams are organised. The matrix below names a core framework, a complement and an AI governance layer for each sector.

Best data governance framework by industry: core framework, complement, AI governance layer, key regulations and rationale for 11 industries
Industry Core framework Complement AI layer Key regulations Why
Banking and financial services DCAM COBIT; CDMC for cloud NIST AI RMF; EU AI Act BCBS 239, SOX, GLBA, FINRA rules Regulators expect assessable, evidenced capability
Wealth management DCAM DGI NIST AI RMF SEC and FINRA rules, GLBA Client data and advice-related AI need clear accountability
Insurance DCAM DAMA-DMBOK NIST AI RMF; EU AI Act Solvency II, state privacy laws Pricing and underwriting models face fairness scrutiny
Healthcare and life sciences DAMA-DMBOK NIST Privacy Framework ISO/IEC 42001 HIPAA, FDA 21 CFR Part 11, GDPR Privacy and record integrity dominate
Higher education DGI DAMA-DMBOK Four-in-One model (Gao and Li, 2026); ISO/IEC 42001 FERPA, GDPR Distributed authority; AI in assessment and admissions
SaaS and technology Federated / data mesh DAMA-DMBOK ISO/IEC 42001 SOC 2, ISO 27001, GDPR, CCPA/CPRA Engineering-led teams need governance as code
Retail and e-commerce DAMA-DMBOK Eckerson NIST AI RMF PCI DSS, CCPA/CPRA, GDPR Customer data and personalisation at speed
Manufacturing DAMA-DMBOK Eckerson NIST AI RMF EU Digital Product Passport, CSRD Product and supply-chain master data
Logistics and transportation DAMA-DMBOK Federated / data mesh NIST AI RMF Trade and customs data rules, GDPR Many partners and real-time data
Private equity portfolios Eckerson DCAM for financial assets NIST AI RMF Varies by portfolio company Lean, repeatable governance across many firms
Public sector ISO/IEC 38505-1 DGI NIST AI RMF; EU AI Act National law, public records rules Board-level accountability and transparency

‍

Best data governance framework for financial services

The best data governance framework for banks and financial services is DCAM, paired with COBIT. Financial regulators expect institutions to evidence their data capability, not merely describe it, and DCAM’s scored capabilities produce that evidence. COBIT connects data controls to the IT general controls that internal and external auditors already test. Firms moving workloads to the cloud should add CDMC’s 14 Key Controls. For AI, credit decisions fall within the EU AI Act’s high-risk category, so a structured AI layer such as NIST AI RMF is a requirement, not an option.

Best data governance framework for healthcare and life sciences

The best data governance framework for healthcare is DAMA-DMBOK, paired with the NIST Privacy Framework. Healthcare data is clinical, financial and operational at once, which calls for DAMA-DMBOK’s breadth across quality, metadata and master data. The NIST Privacy Framework then structures the privacy risk management that HIPAA demands. Life sciences firms must also govern electronic records under FDA 21 CFR Part 11, where data integrity and audit trails are explicit requirements. ISO/IEC 42001 provides a certifiable management system for clinical and diagnostic AI.

Best data governance framework for higher education

The best data governance framework for universities is DGI, paired with DAMA-DMBOK. Universities distribute authority across faculties, administration and research offices, so decision rights must be designed before anything else. AI raises the stakes: admissions, assessment and academic integrity decisions now involve algorithms. Gao and Li’s 2026 “Four-in-One” model, covered in the AI section below, was built specifically for this setting.

Best data governance framework for SaaS and technology companies

The best data governance framework for SaaS and technology companies is federated, data mesh governance, with DAMA-DMBOK supplying shared definitions. Engineering teams resist governance that arrives as meetings and approval forms. They accept governance that arrives as data contracts, automated tests and policy-as-code in the deployment pipeline. SOC 2 and ISO 27001 audits then draw on evidence the pipeline already produces.

In practice: Sphera, a provider of integrated risk management software, wanted to turn 15 years of operational data into real-time analytics for its cloud platform. Each customer had captured that data in different formats, and European customers required GDPR compliance. Forte Group built a mapping layer that standardised every customer’s data into one format, and designed privacy into the pipeline: personal data is anonymised or pseudonymised for customers subject to GDPR, and data moves into the analytics platform only for customers who opt in. The solution was delivered in four months. Governance here was not a separate programme; it was a design constraint built into the product.

‍

AI governance: the layer data frameworks miss

Classic data governance frameworks were designed for reporting and compliance. They were not designed for models that read data, make decisions and act on them. AI needs a governance layer of its own, covering model risk, explainability, accountability and human oversight.

Three references now define that layer:

  • NIST AI Risk Management Framework (AI RMF 1.0). Released in January 2023, it organises AI risk management into four functions: Govern, Map, Measure and Manage. NIST added a Generative AI Profile (NIST AI 600-1) in July 2024, and the framework is currently being revised. It is the most practical default for most organisations. (NIST AI RMF)
  • ISO/IEC 42001:2023. The international standard for an AI management system, published in December 2023. Because it is a requirements standard, organisations can be certified against it, which matters when customers or regulators want independent assurance. (ISO/IEC 42001)
  • The EU AI Act. A regulation, not a framework. It classifies AI uses by risk, and Annex III lists high-risk areas including education and vocational training, employment and access to essential services such as credit. Following the Digital Omnibus amendment, Regulation (EU) 2026/1744, obligations for Annex III high-risk systems now apply from 2 December 2027. (European Commission)

‍

The four layers of AI risk

New peer-reviewed research adds a useful model for how AI risk behaves inside a data governance programme. In a study published on 12 October 2026, Gao and Li analysed 48 papers on AI in university data governance and classified AI risk into four layers, each with its own source and its own governance response.

The four layers of AI risk, adapted from Gao and Li (2026): where each risk originates, an example, and the governance response
Risk layer Where it originates Example Governance response
Foundational Data and models Training-data bias, black-box decisions, fragile systems Model audits, explainable AI, robustness testing
Normative Rules that lag the technology Unclear data ownership; no one accountable for automated decisions Data classification policy, algorithm audit committee, appeal route
Structural Organisation and power Data silos, dependence on platforms, erosion of professional judgement Cross-department governance committee, Chief Data Officer, human in the loop
Ethical Values Privacy erosion, unfair outcomes, loss of autonomy Ethics by design, clear rules for AI use, stakeholder dialogue

Source: adapted from Gao and Li (2026), Systems 14(10), 1288, licensed under CC BY 4.0.

The study makes three points that apply well beyond universities:

  • Value and risk arrive together. Every benefit AI brings creates its own risk. Integrating data across systems improves insight, and it also spreads bias and widens privacy exposure.
  • Risks escalate across layers. A technical flaw becomes a rules failure when no review exists, then an organisational problem, then an ethical crisis.
  • Overreaction is also a failure. Banning AI outright, or imposing rigid rules disconnected from practice, feeds the same cycle it intends to stop.

The authors propose a “Four-in-One” response that coordinates technological, institutional, organisational and ethical governance. They also name a “governance paradox”: the cost of oversight can cancel out the efficiency AI was meant to deliver. Their answer is to phase governance by maturity, from basic usage rules and human review of high-stakes decisions, to explainable AI and internal ethics review, to independent audits.

The model is theoretical, and its causal chain has not yet been tested empirically. It was developed for universities in a Chinese regulatory context. Its structure, however, maps cleanly onto any organisation deploying AI on governed data.

‍

How AI governance failures escalate

The study cites recent incidents that show the escalation pattern in practice:

  • Ghent University: the rector’s opening speech included fabricated quotations produced by generative AI. A technical flaw became a governance failure because no review norms existed for AI use in administration.
  • Australian Catholic University: students were accused of AI cheating on the basis of a detection tool the university had known for over a year to be unreliable.
  • University of St Andrews: a medical student was found to have used AI because his dissertation’s grammar was too polished. The finding was withdrawn on appeal after months of disruption.

None of these began as an ethical failure. Each began as a technical limitation that met an absence of rules, accountability and human judgement.

‍

What governed AI looks like in practice

The opposite pattern is AI deployed with human oversight designed in from the start. A national law firm asked Forte Group to automate client email responses without exposing the firm to legal or financial risk. Before the system went live, the firm’s knowledge base was cleaned and structured for accuracy. Responses then pass through a compliance layer, and any query the model is not confident about is routed to senior staff for review.

The result: 96% of inquiries are handled automatically, only 4% require escalation, and the firm saves an estimated 24,000 staff hours a year. In the terms of Gao and Li’s model, governance addressed the foundational layer through data quality and the structural layer by keeping a human in the loop for high-stakes decisions. Oversight did not cancel out the efficiency gain. It made the gain safe to keep.

‍

How to choose and implement a data governance framework

The most effective data governance programmes do not adopt a single framework wholesale. They combine three layers:

  1. A core framework that defines the discipline: DAMA-DMBOK, DCAM or DGI.
  2. An operating-model edge that fits how the organisation works: federated governance, Eckerson or BCG.
  3. An AI governance layer for models that act on data: NIST AI RMF or ISO/IEC 42001.

With that model in mind, implementation follows a consistent sequence.

  1. Assess current maturity. Inventory critical data domains, existing policies and data quality issues. Identify who owns each domain and who suffers when the data is wrong.
  2. Pick one business problem and one domain. Failed audits, slow reporting or untrusted customer data are good starting points. Avoid enterprise-wide launches.
  3. Choose the core framework, using the industry matrix above, and adapt its terminology to your organisation.
  4. Assign roles. Name a governance council, data owners and data stewards, and write those responsibilities into job descriptions.
  5. Automate policy where possible. Data contracts, quality checks and access rules should run in pipelines, not in spreadsheets.
  6. Measure outcomes. Track time to insight, data quality incidents, self-service adoption and issue resolution time, alongside leading indicators such as glossary coverage and lineage completeness.
  7. Scale by domain. Expand only after the pilot has met its success measures.

This mirrors the phased roadmap Gao and Li propose for AI governance: foundational controls first, systematic governance second, comprehensive governance only where resources and risk justify it. A focused pilot should show measurable results within 90 days.

‍

Do you need data governance tools first?

No. Tools do not create governance; people and processes do. Many organisations buy a catalogue or governance platform before agreeing who owns the data, and the platform sits unused. Start with roles, policies and one domain, then buy tools that serve the use cases you have proven. Forte Group’s rule of thumb is to defer major tool investment until the organisation reaches a defined, repeatable level of governance maturity.

‍

Constraints and challenges

Frameworks are reference models. Implementing them meets real constraints that no framework removes.

  • Effort and cost. DCAM and COBIT demand significant investment in assessment and evidence. The governance paradox applies to data as much as to AI: oversight that costs more than the value it protects will be abandoned.
  • Skills. Stewardship, policy design and policy-as-code require people who understand both the business and the data. Many organisations must build that capability while they implement.
  • Cultural resistance. Teams that see governance as bureaucracy will route around it. Governance must solve a problem they recognise, such as faster access to trusted data, or adoption will stall.
  • Moving targets. Standards and regulations change. ISO/IEC 38505-1 gained a new edition in August 2026, the EU AI Act timeline moved in July 2026, and both DAMA-DMBOK and NIST AI RMF are being revised. A framework choice needs an annual review.

‍

Frequently asked questions

What are the different types of data governance frameworks?

Data governance frameworks fall into five types: comprehensive data management frameworks (DAMA-DMBOK, DCAM, CDMC), governance-specific frameworks (DGI, DGPO, ISO/IEC 38505-1), IT, risk and privacy frameworks (COBIT, NIST Privacy Framework), consultancy and vendor models (BCG, PwC, SAS, Eckerson) and operating models such as federated, data mesh governance. Organisations can also be described by structure: top-down, bottom-up, centralised or hybrid.

What are the four pillars of data governance?

The four pillars of data governance are commonly described as people, processes, technology and policies. Some sources use variations, such as data quality, stewardship, protection and management, or Informatica’s people, processes, contributors and technology. Every version stresses that governance fails when any one pillar is missing.

What are the three main components of a data governance framework?

The three main components of a data governance framework are people (roles and accountability), processes (how decisions, issues and changes are handled) and technology (the tools that enforce and monitor policy). Policies and metrics sit across all three.

What is the best data governance framework?

There is no single best data governance framework. DAMA-DMBOK is the most widely used general standard, DCAM is the strongest for regulated finance, and federated governance suits engineering-led organisations. The best choice depends on industry, maturity and AI exposure.

Is DAMA-DMBOK a data governance framework?

DAMA-DMBOK is a body of knowledge for the whole of data management, with governance at its centre. Most organisations use it as their core reference and adapt it into an operating framework.

Do small businesses need a data governance framework?

Yes, but a lightweight one. A modular model such as Eckerson, a short list of owned data domains and basic quality and access policies are enough to start. The aim is trust in the data, not paperwork.

How is AI governance different from data governance?

Data governance controls the data. AI governance controls the models that use the data and the decisions they make, including explainability, bias, human oversight and accountability. AI governance depends on data governance, but data governance alone does not cover it.

How long does it take to implement a data governance framework?

A focused pilot in one domain can show results in 8 to 12 weeks. An enterprise-wide rollout typically takes 6 to 18 months, depending on the number of domains, regulatory requirements and organisational complexity.

What is the difference between data governance and data management?

Data governance decides how data should be handled: who owns it, which rules apply and who is accountable. Data management carries out that work day to day: integration, storage, quality checks and security. DAMA-DMBOK places governance at the centre of data management because every other discipline depends on its decisions.

What is the difference between DAMA-DMBOK and DCAM?

DAMA-DMBOK is a body of knowledge that describes what good data management looks like across every discipline. DCAM is a capability assessment model that scores how mature an organisation is, with 8 components, 34 capabilities and 101 sub-capabilities in version 3. Many financial institutions use DAMA-DMBOK for shared definitions and DCAM to measure progress and evidence it to regulators.

Is NIST a data governance framework?

NIST does not publish a general data governance framework. It publishes the NIST Privacy Framework for privacy risk, the Cybersecurity Framework for security risk and the AI Risk Management Framework for AI. Organisations combine these with a core framework such as DAMA-DMBOK to cover data quality, metadata and ownership.

What roles does a data governance framework define?

Most data governance frameworks define four core roles. A governance council sets strategy and resolves conflicts. Data owners are business leaders accountable for a data domain. Data stewards maintain quality and definitions day to day. Data custodians, usually in IT, operate the systems that store and protect the data. Many organisations also appoint a Chief Data Officer to lead the programme.

What is federated computational governance?

Federated computational governance is the fourth principle of data mesh, defined by Zhamak Dehghani. Domain teams own their data, a central group sets shared standards, and those standards are enforced automatically as code in data pipelines. It allows teams to move quickly without each one inventing its own rules.

Which framework should be used for AI governance?

NIST AI RMF is the most practical default for AI governance, organised around four functions: Govern, Map, Measure and Manage. ISO/IEC 42001 suits organisations that need certification for customers or regulators. Organisations operating in the EU must also comply with the EU AI Act, whose obligations for Annex III high-risk systems apply from 2 December 2027.

What should a data governance framework template include?

A data governance framework template should include the framework’s scope and objectives, a list of data domains with named owners and stewards, decision rights and escalation paths, core policies for classification, access, quality and retention, and the metrics used to measure success. The scorecard fields used in this guide make a useful starting structure for comparing frameworks.

How do you measure the success of a data governance framework?

Measure data governance by business outcomes and leading indicators. Outcome measures include time to insight, data quality incidents, compliance findings and self-service adoption. Leading indicators include business glossary coverage, lineage completeness, the share of critical data elements with named owners and the share of policies enforced automatically.

‍

A data governance framework is a means to an end.
The end is trusted data that people can use quickly and safely, and increasingly, AI that the organisation can explain and defend.
  • Choose a core framework by industry, not by popularity.
  • Add an operating model that fits how your teams already work.
  • Treat AI governance as a layer on top of data governance, not a separate project.
  • Start with one domain and one business problem, and prove value within a quarter.
  • Review the choice annually; the standards are moving.

‍

Forte Group designs and implements data governance programmes that enable teams rather than slow them down.

Engagements begin with a maturity assessment and a focused pilot, then scale across domains using federated governance, policy-as-code and AI governance for LLM, RAG and machine learning systems. Forte works across financial services, healthcare, higher education, SaaS and other regulated industries.

Book a free data governance consultation

About the author

Simon Wright
Digital & Content Marketing Manager at Forte Group

You may also like

Transform AI into a Scalable Delivery Capability

83% faster delivery. Under 10% rework. See exactly how Xceptor got there.