Category: Data Governance Frameworks
DAMA Wheel
Also known as: DAMA-DMBOK Wheel, DMBOK Wheel
Simply put
The DAMA Wheel is a visual diagram published by DAMA International as part of its Data Management Body of Knowledge (DMBOK). It places Data Governance at the center and arranges the other data management knowledge areas around it to show how the parts of data management connect as one system. It is primarily a conceptual map of functions rather than a step-by-step description of how data management work is actually carried out.
Formal definition
The DAMA Wheel is the reference diagram used in the DAMA-DMBOK to depict the scope and interrelationship of data management functions. It positions Data Governance as the central hub, with surrounding knowledge areas represented as spokes, to communicate that governance coordinates and integrates the other functional areas. Practitioners should note that the Wheel is a functional/structural model, not a process model; as one critique observes, it does not depict how data management is performed as a sequential process. It is a conceptual framework and does not by itself address regulatory obligations, lawful bases for processing, cross-border transfer mechanics, retention rules, or specific security controls, all of which fall outside its scope. Note also that source descriptions of the Wheel differ on the exact count and arrangement of surrounding knowledge areas, so implementers should verify against the current DAMA-DMBOK edition rather than relying on a single secondary summary.
Why it matters
The DAMA Wheel matters because it gives data management and governance teams a shared, recognizable picture of how the discipline fits together, with Data Governance placed at the center to signal that governance coordinates and integrates the surrounding functional areas rather than sitting alongside them as a peer. For organizations building or maturing a governance program, this framing helps communicate to stakeholders that governance is not a standalone project but the connective tissue across the broader set of data management functions. Its strength, as practitioners note, is clarity: it is one of the most recognized models in the field precisely because it presents the scope of data management as a single connected system in an accessible visual form.
Who it's relevant to
Data Governance Leads
Governance leads use the DAMA Wheel to explain why governance sits at the center of the data management operating model and how it coordinates the surrounding functional areas. It is useful for framing scope and stakeholder conversations, but it should be paired with process definitions, roles, and evidence of accountability, since the Wheel itself is a functional map and does not describe how the work is carried out.
Data Management and Data Quality Practitioners
Practitioners across the knowledge areas can use the Wheel to locate their function within the wider system and to see its relationship to governance. They should treat it as a structural reference rather than a workflow, and verify the specific knowledge-area set against the current DAMA-DMBOK edition rather than a secondary summary.
Privacy and Compliance Professionals
Privacy officers and compliance teams may encounter the Wheel when aligning data management functions with an organization's governance structure, but should note that it is conceptual and does not address regulatory obligations, lawful bases, retention, cross-border transfer mechanics, or security controls. Those requirements must be sourced from the applicable legal regime and standards, not inferred from the diagram.
Inside DAMA Wheel
Data Governance (central hub)
In the DAMA-DMBOK v2 Wheel, Data Governance sits at the center of the diagram, positioned as the coordinating function that interacts with all surrounding knowledge areas. It concerns the exercise of authority, decision rights, ownership, stewardship, and policy over data assets. This is a governance function and should not be conflated with information security controls, which address confidentiality, integrity, and availability.
Surrounding knowledge areas
The Wheel depicts Data Governance at the center encircled by ten surrounding knowledge-area spokes, giving eleven knowledge areas in total. These surrounding areas represent distinct disciplines of data management practice arranged around the central governance hub. The Wheel is a conceptual organizing framework rather than a compliance instrument or legal requirement.
Data management disciplines
The surrounding spokes cover recognized data management disciplines such as data architecture, data modeling and design, data storage and operations, data security, data integration and interoperability, document and content management, reference and master data, data warehousing and business intelligence, metadata, and data quality. These represent the operational domains that governance coordinates.
Framework purpose and scope
The DAMA Wheel is published by DAMA International as part of the DMBOK (Data Management Body of Knowledge) to provide a shared vocabulary and structure for the data management profession. It is a practitioner reference model. It does not itself impose legal obligations and is out of scope for prescribing statutory data protection requirements under any specific regime such as the EU GDPR, UK GDPR, CCPA/CPRA, or HIPAA.
Common questions
Answers to the questions practitioners most commonly ask about DAMA Wheel.
Does the DAMA Wheel place Data Governance as just one knowledge area among equals?
No. In the DAMA-DMBOK v2 depiction, Data Governance sits at the center of the wheel, with the surrounding knowledge areas arranged as spokes around it. This central placement is intentional: it signals that Data Governance provides the oversight, policy, and accountability structure that coordinates the other areas, rather than being one interchangeable slice among them. Treating governance as a peer discipline rather than the coordinating hub is a common misreading of the diagram.
Is the DAMA Wheel a data protection or privacy compliance framework?
No. The DAMA Wheel is a data management knowledge model covering areas such as governance, quality, architecture, and stewardship. It is not a regulatory instrument and should not be equated with the EU GDPR, UK GDPR, CCPA and CPRA, HIPAA, ISO/IEC 27701, or the NIST Privacy Framework. It can support privacy and security programs by organizing management disciplines, but it does not by itself establish lawful bases, transfer mechanisms, retention rules, or compliance obligations, which depend on the applicable jurisdiction and instrument.
How can an organization use the DAMA Wheel to structure its data management program?
Organizations typically use the wheel as a reference map to identify which management disciplines they need to address and how those disciplines relate to a central governance function. It is generally used to scope capabilities, assign ownership, and check for gaps across areas rather than as a step-by-step implementation plan. In practice, the model is adapted to the organization's size, sector, and maturity, and it does not prescribe specific tools, roles, or sequencing.
Where does the DAMA Wheel fit relative to information security controls?
The wheel frames data management disciplines that include governance, stewardship, quality, and lineage, and it treats security as one of the surrounding areas. This preserves the distinction between governance concerns, ownership, policy, data quality, and cataloging, and information security concerns focused on confidentiality, integrity, and availability. The two overlap where policy drives control requirements, but the wheel does not itself specify technical security controls; those are defined by separate security standards and implementations.
Does adopting the DAMA Wheel satisfy a records of processing activities or data inventory obligation?
No. The wheel is a conceptual model of management disciplines and does not fulfill any specific regulatory recordkeeping obligation. A records of processing activities requirement, where it applies, is a distinct legal duty and is not the same as maintaining a data inventory tool. The wheel may help an organization organize the functions that produce such records, but demonstrable evidence of processing activities must be maintained separately according to the applicable regime.
How should roles and accountability be assigned when applying the DAMA Wheel?
The model emphasizes a central governance function coordinating the surrounding disciplines, which typically implies assigning ownership and stewardship across those areas. Accountability under governance frameworks generally requires demonstrable evidence of decisions, controls, and oversight rather than stated intent alone. The wheel does not dictate specific job titles or map onto regulatory roles such as data controller, data processor, or data protection officer, so organizations must define those responsibilities separately and align them with the relevant legal instrument.
Common misconceptions
The DAMA Wheel shows eleven knowledge areas arranged as surrounding spokes.
In the DAMA-DMBOK v2 Wheel, Data Governance occupies the center and is surrounded by ten knowledge-area spokes, producing eleven knowledge areas in total rather than eleven surrounding spokes. Miscounting the segments is a common expert-level error when describing the diagram.
The DAMA Wheel is a compliance or regulatory framework that demonstrates adherence to data protection law.
The Wheel is a professional body-of-knowledge model for organizing data management disciplines. It does not, by itself, evidence compliance with any statutory regime, and treatment of data protection obligations differs across jurisdictions and instruments. Demonstrable accountability under governance and regulatory frameworks generally requires evidence beyond adopting a conceptual model.
The data security spoke on the Wheel means data governance and information security are the same discipline.
The Wheel deliberately positions Data Governance as a coordinating hub and treats data security as one surrounding knowledge area. Governance concerns ownership, stewardship, policy, quality, and lineage, while information security addresses confidentiality, integrity, and availability controls. The two overlap but should not be collapsed into a single function.
Best practices
When citing the DAMA Wheel, state the version (DMBOK v2) and describe Data Governance as the central hub surrounded by ten knowledge-area spokes for eleven total, to avoid miscounting the segments.
Use the Wheel as a vocabulary and structuring aid for data management programs, not as evidence of regulatory compliance; map its disciplines to the specific obligations of your applicable regime separately.
Keep governance activities (ownership, stewardship, policy, data quality, lineage, catalogs) distinct from the data security spoke, documenting where they overlap without merging the two functions.
Assign clear ownership and stewardship roles for each relevant knowledge area, and retain demonstrable evidence of governance decisions rather than relying on stated intent.
Adapt the Wheel selectively to organizational scope; not every knowledge area will be equally relevant, and the model does not prescribe which disciplines are mandatory in a given context.
Treat cross-border transfer mechanics, retention rules, and enforcement penalties as out of scope for the Wheel itself and address them through jurisdiction-specific analysis.