Visual Maps 1–4
Map 1 — Oversight vs execution
Data Governance
authority • control • decision rights • policy • monitoring • enforcement
│ directs / oversees
▼
Data Management
operational execution across the Data Management functions
Rebuild rule: arrow means “governs/oversees,” not “does all work.”
Map 2 — Governance organization layers
Steering Committee
highest authority • funding • executive support
↓
Data Governance Council
initiatives • policy/metrics • issues/escalation
↓
Data Governance Office
ongoing definitions/standards/owner-steward coordination
↓
Stewardship Teams
subject-area/project collaboration
↓
optional Local Governance
Caution: Figure 16 is a generic operating model, not a mandatory reporting org chart.
Map 3 — Operating model types
CENTRALIZED
[one DG organization] → all subject areas
REPLICATED
[unit A: same model] [unit B: same model] [unit C: same model]
(no decisive central coordination clue)
FEDERATED
[enterprise DG coordination]
↙ ↓ ↘
[unit A] [unit B] [unit C]
local participation + shared consistency
Memory: One / Repeat / Coordinate.
Map 4 — Stewardship role family
Chief Data Steward → enterprise governance leadership / possible chair or virtual CDO
Executive Steward → senior manager on DGC
Enterprise Steward → domain oversight across business functions
Data Owner → final business-domain decision accountability
Business Steward → business SME; meaning/rules/subset control
Technical Steward → technical Knowledge Area expertise
Coordinating Steward→ leads/represents steward teams
Exam three-way: Owner decides; Business Steward defines/controls meaning; Technical Steward implements/supports.
Source anchors: pp. 74–79; Figures 15–17; Table 4.