Overview
The Eleven DMBOK Guiding Principles
The constitutional axioms — data is an asset, governance is non-negotiable, metadata is a product, etc.
Why it matters
The 11 principles compress the entire framework into one page of value statements. Citing them — verbatim — in a steering-committee paper short-circuits an hour of philosophical debate.
Going deeper
The eleven principles in one table, paraphrased from DMBOK² §1.3:
| # | Principle | What it forces |
|---|---|---|
| 1 | Data is an enterprise asset | Funded, owned, depreciated like any other asset |
| 2 | Value of data must be measured | Force a $$$ on the data, not just on the team |
| 3 | Data must be managed for quality | Quality is non-optional, not a P3 backlog item |
| 4 | Metadata must be managed | Catalog + lineage are first-class, not afterthought |
| 5 | Governance is required | Authority, not just opinions |
| 6 | All stakeholders need access (per role) | Access policy, not data hoarding |
| 7 | Data lifecycle must be managed | From provision to deprecation, intentionally |
| 8 | Cross-functional commitment is required | Not an IT-only programme |
| 9 | Multi-perspective viewpoint required | Business + technical views, joined |
| 10 | Architecture is foundational | Choices made early dominate; revisit deliberately |
| 11 | Different programmes need different DM | One-size-fits-all DM is the wrong size |
Treat these as constitutional — they are the ground every chapter sits on. If a proposal violates one, that's the discussion to have first, before debating tools or roadmap.