1 — Purpose, DMBOK Targets & Prerequisite Gate

Lab purpose

Make Chapter 1 visible as enterprise Data Management work: identify assets, connect them to business value and risk, trace lifecycle responsibilities, separate data requirements from technology choices, and create a small business-aligned direction for Meridian.

DMBOK concept targets

By completing this lab, you should be able to demonstrate—not merely define—that:

Data Management is broader than database or IT administration; it coordinates plans, policies, programs, and practices across the data lifecycle to protect and increase data value.
Data is an organizational asset with unusual properties, so value, inventory, protection, duplication, ownership, and replacement must be managed deliberately.
Data is representation and needs context; Metadata and Data Quality are foundational to understanding and using it.
Data Management is cross-functional and requires an enterprise perspective, multiple stakeholder perspectives, and leadership commitment.
Data Management is lifecycle management and includes risk management; different data types can require different lifecycle treatment.
Business-aligned data requirements should lead technology decisions rather than technology convenience defining the requirement.
Data strategy and Data Management program strategy connect business goals to prioritized management capabilities and initiatives.
The 11 Knowledge Areas are distinct but interdependent; Data Governance coordinates and provides direction without being identical to all Data Management.

DMBOK source anchors: Chapter 1, pp. 19–20 definition/business driver/goals; pp. 20–25 representation/assets/principles; pp. 25–34 management challenges; pp. 34–35 strategy; pp. 35–49 frameworks/Knowledge Areas.

Meridian situation

Meridian operates successfully, but its data estate grew faster than its management discipline. Systems support the business, yet shared data is inconsistently defined, governed, traced, protected, and measured.

Use these persistent conditions as Chapter 1 evidence:

Condition	Observation	Chapter 1 lens
MCG-001 / MCG-002	CRM, POS, and Service disagree about customer identity and “active customer.”	Representation, enterprise perspective, Metadata, quality, governance coordination
MCG-004	Revenue KPI cannot quickly be traced from dashboard to source/transformation.	Metadata/context, planning, lifecycle/lineage distinction, management value
MCG-005	Nulls, duplicates, invalid references, impossible quantities, stale addresses.	Fitness for purpose, value loss, risk, quality across lifecycle
MCG-006	Reporting account sees synthetic sensitive attributes it does not need.	Risk, appropriate use, protection across lifecycle
MCG-009	Columns lack descriptions, owners, classifications, or trustworthy source information.	It takes Metadata to manage data
MCG-010	Decision authority and escalation are inconsistent.	Enterprise coordination, leadership, governance relationship

Prerequisite gate

You are ready when you can:

explain Data Management, data-as-asset, lifecycle vs lineage, Metadata/Data Quality foundations, business-first technology decisions, and the 11 Knowledge Areas without merely rereading definitions;
recognize Meridian's main business processes, systems, data domains, and at least five messy-company conditions;
create/edit a document or spreadsheet and optionally a simple diagram; and
save reasoning and outputs rather than only screenshots.

STOP RULE: If you cannot explain the Chapter 1 concepts above, return to the Chapter 1 mastery material. Do not compensate by adding technology.

Required outputs

A. Meridian Data Asset Inventory
B. Value & Risk Assessment
C. Lifecycle Management Map
D. Business/Data Requirements Before Technology
E. Mini Data Management Charter, Scope & Roadmap
F. Knowledge Area Map & DMBOK Debrief
G. Acquisition Change-Fact Revision