Most CDOs have heard of DAMA-DMBOKDAMA-DMBOKData Management Body of Knowledge, référentiel de l'association DAMA définissant les 11 domaines de gestion des données (gouvernance, qualité, architecture, sécurité, etc.).. Far fewer have actually read it. And almost none implement more than a fraction of it, which is exactly the right call.
DAMA-DMBOKDAMA-DMBOKData Management Body of Knowledge, référentiel de l'association DAMA définissant les 11 domaines de gestion des données (gouvernance, qualité, architecture, sécurité, etc.). is a reference framework, not an implementation plan. Treating it like a to-do list is the first mistake. Understanding what it actually says, and which parts matter for your organization right now, is the CDO's job.
DAMA-DMBOK (Data Management Body of Knowledge) defines 11 knowledge areas, visualized as a wheel with at the center:
1. Data governanceData governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.Voir la définition complète →, The hub. Sets policies, standards, and accountability for all other areas.
2. Data architecture, The structural blueprint for how data flows across systems.
3. Data modeling & design, The schemas, ontologies, and conceptual models.
4. Data storage & operations, Physical storage, databases, archival.
5. Data security, Access controls, encryption, threat management.
6. Data integration & interoperability, How data moves between systems (ETLETLETL (Extract, Transform, Load) is a data integration process that pulls data from sources, reshapes it into a consistent format, and writes it into a target system.Voir la définition complète →, ELTELTELT (Extract, Load, Transform) is a data integration pattern where raw data is loaded into a target system first, then transformed inside it using the platform's compute power.Voir la définition complète →, APIs).
7. Document & content management, Unstructured data: documents, emails, media.
8. Reference & master data, Canonical codes, hierarchies, golden records.
9. Data warehousing & Business Intelligence, Analytical infrastructure and reporting.
10. MetadataMetadataDonnées sur les données, informations décrivant le contexte, la structure, la provenance et les caractéristiques d'un asset de données (auteur, date, format, source, définition)., Data about data: definitions, lineage, quality scores.
11. Data qualityData qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.Voir la définition complète →, Fitness for purpose across all dimensions.
The wheel metaphor is deliberate: remove any spoke and the wheel wobbles. But in practice, no organization invests equally across all 11 areas, and they shouldn't.
The DAMA-DMBOKDAMA-DMBOKData Management Body of Knowledge, référentiel de l'association DAMA définissant les 11 domaines de gestion des données (gouvernance, qualité, architecture, sécurité, etc.). is written for data practitioners at all levels. As a CDO, your highest-leverage areas are:
Must master: Data governanceData governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.Voir la définition complète →, Data qualityData qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.Voir la définition complète →, MetadataMetadataDonnées sur les données, informations décrivant le contexte, la structure, la provenance et les caractéristiques d'un asset de données (auteur, date, format, source, définition)., Master Data ManagementMaster Data ManagementMaster Data Management (MDM) is the discipline of creating and maintaining a single, consistent, trusted version of an organization's core business entities like customers, products, and suppliers.Voir la définition complète → (areas 1, 11, 10, 8). These are where CDO decisions directly create or destroy organizational value.
Must understand: Data architecture, Data security, Data integration (areas 2, 5, 6). You don't build these systems, but you make strategic decisions about them.
Delegate with oversight: Data storage, Data modeling, Document management (areas 4, 3, 7). These are engineering and IT decisions that need governance guardrails, not CDO micromanagement.
Vérification des acquis
1. According to the lesson, how many knowledge areas does the DAMA-DMBOK wheel define?
2. What is at the center (hub) of the DAMA Wheel?
3. The lesson describes DAMA-DMBOK as a 'reference framework, not an implementation plan.' What practical implication does this have for a CDO?
4. Select ALL knowledge areas that the lesson classifies as 'Must master' for a CDO.
Sélectionnez toutes les réponses correctes.
5. Select ALL knowledge areas the lesson categorizes as 'Delegate with oversight' for a CDO.
Sélectionnez toutes les réponses correctes.
Misunderstanding 1: "DAMA-DMBOK tells you how to implement data management."
It doesn't. It tells you *what* data management is. How to implement it, sequencing, tools, org design, change management, is left entirely to you. This is why organizations that follow DAMA-DMBOKDAMA-DMBOKData Management Body of Knowledge, référentiel de l'association DAMA définissant les 11 domaines de gestion des données (gouvernance, qualité, architecture, sécurité, etc.). to the letter still fail at data transformation: the framework is a taxonomy, not a playbook.
Misunderstanding 2: "We need to achieve DAMA maturity across all 11 areas before we get value."
Completely wrong. A Level 3 in Data qualityData qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.Voir la définition complète → and Data governanceData governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.Voir la définition complète → with Level 1 everywhere else will deliver more business value than a Level 2 evenly distributed across all 11 areas. Sequence matters. Foundation areas first, advanced areas later.
Misunderstanding 3: "DAMA-DMBOK is the same as data governance."
Data governanceData governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.Voir la définition complète → is one of the 11 areas, the central one, but still just one. The confusion causes organizations to build elaborate governance structures without touching Data qualityData qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.Voir la définition complète →, MetadataMetadataDonnées sur les données, informations décrivant le contexte, la structure, la provenance et les caractéristiques d'un asset de données (auteur, date, format, source, définition). management, or , then wonder why nothing improves.
DAMA-DMBOKDAMA-DMBOKData Management Body of Knowledge, référentiel de l'association DAMA définissant les 11 domaines de gestion des données (gouvernance, qualité, architecture, sécurité, etc.). is genuinely useful as a common language. When you tell your team to build a "data catalogdata catalogA centralized inventory of an organization's data assets, enriched with metadata, that helps people find, understand, and trust the data they need.Voir la définition complète →," everyone might have a different idea of what that means. When you say "we're implementing DAMA-DMBOKDAMA-DMBOKData Management Body of Knowledge, référentiel de l'association DAMA définissant les 11 domaines de gestion des données (gouvernance, qualité, architecture, sécurité, etc.). area 10 (Metadata management)," it's precise.
Use it for vocabulary, assessment, and certification (the CDMP certification is respected and increasingly expected). Don't use it as a project plan. Your organization's specific context, industry, size, regulatory environment, data maturitydata maturityNiveau de sophistication d'une organisation dans la gestion et la valorisation de ses données, mesuré sur une échelle de 1 (initial/réactif) à 5 (optimisé/transformationnel)., determines your implementation sequence far more than any framework.