Lesson 1 — Current State and Fit Come First
What the chapter is really saying
A Data Management Organization cannot be designed in a vacuum. Before drawing reporting lines, understand the enterprise that the DMO must live inside.
Six current-state lenses
- Role of data — Which processes are data-driven? How visible is data in strategy? How are requirements understood?
- Cultural norms — What behaviors or beliefs could support or resist governance and shared accountability?
- Existing DM/DG practices — Who already performs Data Management work or makes data decisions, even informally?
- Work organization — Is work project-based, operational, committee-driven, or some combination?
- Reporting relationships — Is the enterprise centralized or decentralized, hierarchical or flat?
- Skill levels — What Data Management knowledge already exists from staff through executives?
These questions do not merely describe the organization. They reveal what type of structure can realistically be sustained.
Describe current state, then test satisfaction
Knowing who does the work is not enough. Ask whether the current arrangement actually supports business outcomes. Chapter 16 uses business-facing questions such as: - Can leaders make timely decisions? - Are revenue reports trusted? - Can the company track meaningful KPIs? - Can it comply with data-related laws?
Poor answers identify the organizational need the DMO must address. They do not automatically prove that centralization is the answer.
Reuse before replacing
A recurring Chapter 16 principle is to start with what already exists: - people already doing stewardship, modeling, quality, metadata, or related work; - committees already making cross-functional decisions; - existing reporting and decision constructs that people understand.
Radically replacing these structures can turn a Data Management initiative into an HR/political reorganization before the organization understands its own capability.
Evolution, not automatic revolution
Most organizations sit somewhere in the middle of a maturity continuum. Therefore, the normal approach is to evolve the current organization and its participants. Market shocks or new regulation can justify faster change, but acceleration increases the people-side change load.
Exam decision rule
If the stem says leadership has already drawn a new DMO but has not studied current committees, decision norms, existing participants, or culture, the best next step is usually current-state assessment, not more detailed org-chart design.
Source anchor: Chapter 16, pp. 521–523.