Lesson 1 — Purpose & Operating Spine
What a DMMA is really for
A Data Management Maturity Assessment (DMMA) is a disciplined way to determine how capable an organization currently is at managing data, compare that current state with the capability it needs, and turn the difference into a staged improvement program.
It changes an unhelpful question — “Are we mature?” — into better questions:
- What observable capability exists today?
- What evidence proves it?
- What capability does the business actually need?
- What is the gap?
- Which gap matters most to strategy, risk, compliance, or value?
- What should be improved first, and in what sequence?
- Is capability improving after the roadmap begins?
The chapter operating spine
BUSINESS DRIVER → OBJECTIVE/SCOPE → FRAMEWORK → EVIDENCE → RATING/CONSENSUS → INTERPRET GAP → TARGET → ROADMAP → RE-ASSESS
Think of this as a governed learning loop:
- Business driver explains why the assessment exists.
- Objective and scope decide what the assessment must represent.
- Framework supplies maturity structure and criteria.
- Evidence provides proof of practice.
- Rating and consensus establish a defensible current state.
- Interpretation translates capability gaps into business meaning.
- Target state defines needed capability, not maximum maturity by default.
- Roadmap sequences improvement.
- Reassessment tests whether capability actually changed.
Assessment is not the improvement program
This is one of the chapter's strongest boundaries.
Assessment = diagnose.
It characterizes current capability, strengths, gaps, and opportunity.
Improvement program = change.
It implements new processes, tools, roles, standards, governance, and other capabilities.
If a team starts rewriting standards while still interviewing participants and reconciling current-state evidence, it is changing the thing it is trying to measure. The result can become less consistent and less comparable.
Example
A stewardship assessment discovers that issue escalation depends on one senior steward.
- During the DMMA: document the evidence and rate the current capability.
- After interpretation: design repeatable roles and escalation procedures in the improvement roadmap.
Why organizations perform a DMMA
Chapter 15 gives several kinds of business drivers:
- regulation or oversight;
- Data Governance planning/compliance;
- readiness for process improvement such as MDM;
- merger or other organizational change;
- new technology adoption;
- persistent Data Quality or other Data Management problems.
The assessment can be broad or narrow: an entire Data Management function, one Knowledge Area, or one process. The result only represents what was actually in scope.
Cultural value beyond the score
A DMMA can also create a shared Data Management language. It can clarify roles, teach stakeholders how Data Management capabilities connect, make data-as-an-asset more concrete, and create a bridge between business and IT perspectives.
That shared frame is important because later improvement requires coordination across people, process, technology, governance, and culture.
Decision rules
- “What are we capable of today?” → assessment/current state.
- “What should we change?” → interpretation/roadmap.
- “Implement this new process now” → improvement program.
- “Did capability improve?” → reassessment.
Stop-and-check
Question: A team is still collecting evidence but begins redesigning workflows when it discovers weaknesses. What is wrong?
Answer: Assessment and remediation are being mixed. Finish the current-state assessment, interpret the result, then sequence improvements.
Source: pp. 503–505, 510–516.