Lesson 8 — DMO Interactions and Global Organizations
The DMO is one node in a wider enterprise system. Chapter 16 highlights four major interfaces.
Chief Data Officer (CDO)
The CDO is a senior bridge between business and technology and an enterprise data strategist/ambassador. Common Chapter 16 mandates include: - establishing organizational data strategy; - aligning data requirements with resources; - establishing governance standards, policies, and procedures; - advising data-dependent initiatives; - evangelizing sound information-management principles; - overseeing data use in analytics/BI.
In a decentralized structure, the CDO can own strategy while IT, operations, and LOB resources execute it.
Data Governance vs Data Management
Data Governance: strategy, policy, standards, decision framework, accountability guidance — shorthand: doing the right things.
Data Management Organization: implements and operates the practices — shorthand: doing things right.
They are synergistic, not substitutes. Reporting direction may vary; clear responsibilities do not.
Data Quality
DQ is often an entry point because quality problems make value visible. A successful local DQ practice may later expand into a unified/COE approach as shared data, MDM, reference data, or metadata needs grow. Its operating model should align with the overall DMO.
Enterprise Architecture and the ARB
Data Architects may sit in Enterprise Architecture or the DMO, often with a dotted-line relationship to the other.
An Architecture Review Board (ARB) reviews adherence to architecture standards and may approve/disapprove projects or systems.
If no Data Architects exist, DMO–EA coordination can occur through: 1. Data Governance; 2. an ARB; 3. periodic leader-to-leader meetings.
If ad-hoc coordination becomes difficult, the organization may need a more formal role or committee.
Global organizations
Global DMOs face country-specific laws plus distributed systems, staff, time zones, languages, and business priorities.
Chapter 16 emphasizes: - standards; - synchronized processes; - aligned accountability; - training/communication; - monitoring/measurement; - economies of scale; - reduction of duplicate effort.
Networked/federated patterns become attractive because they can preserve enterprise accountability while accommodating legitimate regional variation.
Source anchor: Chapter 16, pp. 533–537.