Chapter 16 — Data Management Organization and Role Expectations
Quick Study Navigation
🏠 Study Home · 📖 Chapter Library · 📘 Learn · 🎯 Exam Map · 🧠 Visuals · ⚔️ Battle Cards · 🧩 Scenarios · 📝 Questions · 🔄 Recall · 📕 Source PDF · 🗂️ Formatted Originals
Source boundary: DAMA-DMBOK2 Revised, Chapter 16, printed pp. 521–540. This fresh GitHub build is based on the current Chapter 16 Mastery Lab artifacts in Google Drive, not superseded GitHub prose.
Chapter 16 is supporting/specialist context, but it answers a practical question that sits underneath every other DMBOK capability: who participates, who decides, who is accountable, and how should Data Management fit the enterprise that already exists?
Core mental model
UNDERSTAND CURRENT CULTURE / DECISIONS / PEOPLE → CHOOSE OPERATING MODEL → DEFINE ACCOUNTABILITY & COMMITTEES → ENGAGE STAKEHOLDERS → CONNECT DMO TO CDO / DG / DQ / EA → ASSIGN ORGANIZATIONAL & INDIVIDUAL ROLES → MEASURE ADOPTION → EVOLVE
The chapter rejects a universal organization chart. The best design is the one that fits the enterprise's actual culture, reporting structure, decision style, maturity, complexity, and need for local autonomy versus enterprise control.
The seven study layers
- Guided Learning — plain-language teaching from current state through role discrimination.
- Exam Map — 26 high-yield decision targets, changed-fact drills, and readiness checks.
- Visual Memory Atlas — 15 text-first redraw maps.
- Battle Cards — high-confusion comparisons.
- Scenario Lab — organizational decision practice.
- Question Bank — closed-book practice and diagnostics.
- Teach-Back — retrieval, reconstruction, classification, and repair.
Artifact 08 is not prebuilt. Only repeated real misses, slow decisions, or confidence mismatches should become future error-repair material.
What to know before leaving this chapter
You should be able to: - distinguish an operating model from an org chart; - classify decentralized, network, centralized, hybrid, and federated structures from clues rather than labels; - explain why fit beats formal elegance; - diagnose whether a people-side failure is sponsorship, leadership alignment, communication, training, engagement, guiding principles, or adoption measurement; - use influence and interest to prioritize stakeholders; - separate Data Governance guidance from Data Management execution; - place the CDO, DQ, and Enterprise Architecture interfaces correctly; - distinguish organizational services/functions from person-level roles; - choose the Chapter 16 role from the actual responsibility, not from title prestige.
Current source artifacts
- Guided Learning: https://docs.google.com/document/d/1FjYf0reAzEYklBzXWOKwEnsHZUVPf_8Kss6um9uhWTE
- Exam Map: https://docs.google.com/document/d/16dTsnBHmbhk8FLSKY_-f261qIMDDsh57ysE3_rEwedg
- Visual Memory Atlas: https://docs.google.com/document/d/1wV2gt8niSKzSh3GKNBEKUsTFH1s7iX7NcEQfy6zNGcY
- Battle Cards: https://docs.google.com/document/d/1RZX2L9yabZmEzOptRDStW0rRmIOPoJrOTtRe01Pzigw
- Scenario Lab: https://docs.google.com/document/d/1BupsbvZYhfBI2dc74Un2gv5M1qbcq5P8NPJU_uzn3hQ
- Question Bank: https://docs.google.com/spreadsheets/d/101P6FmHmo_mZXV6ntLSBjO9kGlt7styUuapeg8twcCc
- Teach-Back: https://docs.google.com/document/d/1mAoyLHpJlrYPOP6TitaQuu8qHZUtjaMwrosh0wJq6nk
- DMBOK Chapter 16 source PDF: https://drive.google.com/file/d/1aX8ze7aLSkVsVG5C4eYBJW88Le6MgyfM/view