Data Management Process

Chapter 1 2% of exam

Overview

Data Management Process, as defined in DAMA-DMBOK2 Chapter 1, establishes the foundational framework for the entire discipline of data management. It introduces the DAMA Wheel (also known as the DAMA Data Management Framework), which places Data Governance at the center surrounded by ten knowledge areas: Data Architecture, Data Modeling and Design, Data Storage and Operations, Data Security, Data Integration and Interoperability, Document and Content Management, Reference and Master Data, Data Warehousing and Business Intelligence, Metadata Management, and Data Quality. The framework provides a common vocabulary and conceptual structure that enables organizations to plan, implement, and improve their data management capabilities in a systematic and coordinated way. Data management operates at three distinct levels: STRATEGIC (long-term planning, alignment with business goals, and establishing a data management vision), TACTICAL (medium-term program management, policy development, standards creation, and architecture design), and OPERATIONAL (day-to-day execution of data management processes such as data entry, quality monitoring, backup, and access provisioning). The DMBOK2 emphasizes that effective data management requires coordination across all three levels and across all knowledge areas. A data management strategy must articulate a vision, business case, guiding principles, goals, delivery roadmap, and a governance framework to ensure execution. The chapter also establishes foundational principles that underpin all of DMBOK2: data is an asset that has value and should be managed accordingly, data management requires both technical and business participation, data management is a cross-functional discipline that spans organizational boundaries, and managing data effectively requires an enterprise perspective even when implementing locally. Data management maturity assessment is introduced as a mechanism to evaluate current capabilities and plan improvements across a standardized maturity scale (typically five levels from Initial/Ad Hoc to Optimized). Importantly, DMBOK2 positions data management not merely as an IT function but as a business function enabled by technology, requiring leadership, organizational change management, and a strong value proposition to sustain investment and organizational commitment.

Key Concepts

DAMA Wheel (Data Management Framework)

The DAMA Wheel is the central visual organizing construct of DMBOK2. It depicts Data Governance at the hub, surrounded by ten knowledge areas arranged as spokes or segments: Data Architecture, Data Modeling and Design, Data Storage and Operations, Data Security, Data Integration and Interoperability, Document and Content Management, Reference and Master Data, Data Warehousing and Business Intelligence, Metadata Management, and Data Quality. The wheel communicates that governance connects to and guides every other knowledge area, and that no knowledge area operates in isolation. Each knowledge area has defined goals, activities, roles, inputs, outputs, deliverables, and metrics. The wheel also reinforces the idea that data management is a holistic discipline, not a collection of independent silos.

Environmental Factors (Context Diagram)

DMBOK2 describes each knowledge area using a standardized context diagram that identifies the goals, activities, inputs, outputs, suppliers, consumers, participants, tools, metrics, and deliverables of that area. Crucially, each context diagram also identifies ENVIRONMENTAL FACTORS that influence how data management is practiced. These factors include: organizational culture (risk-averse vs. innovative), industry regulations (GDPR, HIPAA, SOX), technology landscape (legacy systems, cloud adoption), data maturity level, stakeholder attitudes, budget constraints, and geographic distribution. Understanding environmental factors is essential because data management practices must be adapted to the organization's specific context rather than applied as a one-size-fits-all template.

Data Management Strategy Components

A data management strategy, as described in DMBOK2, consists of several essential components: (1) VISION — a clear statement of the desired future state for data management; (2) BUSINESS CASE — quantified justification showing the value of data management investment, including cost reduction, revenue enhancement, risk reduction, and compliance; (3) GUIDING PRINCIPLES — fundamental beliefs and rules that direct decision-making (e.g., 'data is a shared enterprise asset'); (4) GOALS AND OBJECTIVES — specific, measurable targets tied to business outcomes; (5) GOVERNANCE FRAMEWORK — the organizational structure, roles, policies, and processes that enable execution; (6) DELIVERY ROADMAP — a phased plan with milestones, dependencies, and resource requirements; (7) METRICS AND KPIs — measures to track progress and demonstrate value. The strategy must align with and support the organization's overall business strategy.

Data Lifecycle

The data lifecycle describes the phases data passes through from creation to disposal. DMBOK2 identifies the key stages as: (1) PLAN — define data requirements, models, and architectures; (2) SPECIFY/ENABLE — design databases, define standards, provision infrastructure; (3) CREATE/OBTAIN — generate new data or acquire data from external sources; (4) STORE/MAINTAIN — persist data in databases, files, or data lakes and perform ongoing maintenance; (5) USE — analyze, report, and make decisions based on data; (6) ENHANCE — improve data through cleansing, enrichment, and integration; (7) ARCHIVE — move infrequently accessed data to long-term storage while retaining accessibility; (8) DISPOSE/PURGE — securely delete data according to retention policies and regulatory requirements. Different data management knowledge areas are more active at different lifecycle stages, but governance applies across all stages.

Data Management Principles (DAMA Principles)

DMBOK2 articulates a set of foundational principles that guide all data management activity: (1) Data is an asset with unique properties — it does not deplete when used and its value increases when shared; (2) The value of data can and should be expressed in economic terms; (3) Managing data means managing the quality of data; (4) It takes metadata to manage data — without metadata, data cannot be understood, discovered, or trusted; (5) Data management requires planning — it is not something that happens accidentally; (6) Data management is cross-functional and requires enterprise perspective; (7) Data management requires a range of skills and expertise from both business and IT; (8) Data management requires an enterprise perspective; (9) Data management must account for a range of perspectives; (10) Data management is lifecycle management. These principles appear throughout DMBOK2 and provide the rationale behind specific recommendations in each knowledge area.

Data Management Maturity Assessment

A maturity assessment evaluates an organization's data management capabilities using a standardized scale, typically five levels modeled after CMMI: Level 1 — INITIAL/AD HOC (no formal processes, dependent on individual heroics, unpredictable outcomes); Level 2 — REPEATABLE (some processes exist but are department-specific, limited documentation and consistency); Level 3 — DEFINED (enterprise-wide processes documented and standardized, roles and responsibilities assigned, training provided); Level 4 — MANAGED (processes measured with quantitative metrics, performance monitored and controlled, proactive improvement); Level 5 — OPTIMIZED (continuous improvement culture, processes self-correcting, data treated as a strategic differentiator with measurable business value). Assessment should cover all knowledge areas across dimensions of people, process, technology, and data. Results identify gaps and guide prioritization of improvement initiatives.

Knowledge Areas and Their Interrelationships

The eleven DMBOK2 knowledge areas are deeply interconnected. Data Governance sits at the center, providing oversight and coordination for all others. Data Architecture provides the blueprints that Data Modeling and Design translates into detailed logical and physical models. Data Storage and Operations implements those models in actual database systems. Data Quality depends on Metadata Management (you cannot measure quality without understanding data definitions). Data Integration and Interoperability moves data between the systems managed by Storage and Operations. Data Warehousing and BI consumes the integrated data for analytics. Data Security protects data across all areas. Reference and Master Data provides the shared entities used across systems. Document and Content Management handles unstructured data. Understanding these relationships is essential because improvements in one area often require changes in others, and neglecting one area creates weaknesses in the entire framework.

Data Management as a Profession

DMBOK2 positions data management as a distinct professional discipline, analogous to financial management or human resource management. It requires specialized knowledge, skills, and competencies. Key roles include: Chief Data Officer (CDO), data architects, data modelers, database administrators, data analysts, data engineers, data stewards, data quality analysts, metadata managers, and data scientists. Professional development paths include certifications such as CDMP (Certified Data Management Professional), DGSP (Data Governance and Stewardship Professional), and various vendor-specific certifications. The DAMA community provides networking, education, and standards development. DMBOK2 emphasizes that organizations must invest in building data management competencies through hiring, training, career path development, and communities of practice.

Organizational Change Management for Data Management

Implementing data management practices requires significant organizational change, and DMBOK2 explicitly addresses the human side of data management. Key change management elements include: (1) EXECUTIVE SPONSORSHIP — active, visible support from senior leadership is the single most critical success factor; (2) STAKEHOLDER ENGAGEMENT — identifying and involving key stakeholders early to gain buy-in; (3) COMMUNICATION PLAN — clearly articulating the why, what, and how of data management to different audiences; (4) TRAINING AND EDUCATION — building data literacy and specific data management skills across the organization; (5) RESISTANCE MANAGEMENT — proactively addressing concerns about bureaucracy, loss of autonomy, and additional workload; (6) QUICK WINS — delivering visible, measurable improvements early to build credibility and momentum; (7) CULTURE SHIFT — moving from data as a departmental byproduct to data as a shared strategic asset. Without deliberate change management, even technically sound data management programs fail.

Strategic vs Tactical vs Operational Data Management

DMBOK2 distinguishes three levels of data management activity: STRATEGIC — long-range planning activities including developing the data management vision, creating the enterprise data strategy, defining guiding principles, building the business case for data management investment, and aligning data management with business strategy. Strategic activities are typically led by the CDO and Data Governance Council. TACTICAL — medium-term activities including designing data architecture, developing policies and standards, selecting technologies, building data management teams, creating data models, and planning implementation projects. Tactical activities bridge strategy and execution. OPERATIONAL — day-to-day activities including data entry and validation, database administration, backup and recovery, access provisioning, data quality monitoring, metadata updates, ETL execution, report generation, and incident resolution. All three levels must be coordinated; operational improvements without strategic direction waste resources, and strategy without operational capability remains theoretical.

Data Management Value Proposition

DMBOK2 emphasizes that data management programs must articulate a clear value proposition to justify investment and sustain organizational support. Value can be demonstrated through multiple dimensions: (1) RISK REDUCTION — fewer data breaches, improved regulatory compliance, reduced audit findings; (2) COST REDUCTION — eliminating redundant data stores, reducing manual data reconciliation, lowering error correction costs; (3) REVENUE ENHANCEMENT — better customer insights leading to improved marketing effectiveness, cross-selling, and product development; (4) OPERATIONAL EFFICIENCY — faster report generation, reduced time searching for data, streamlined data integration; (5) DECISION QUALITY — more accurate and timely data leading to better strategic and operational decisions; (6) COMPLIANCE — avoiding penalties from GDPR, HIPAA, SOX, and other regulations. The value proposition should use the language of business, not technology, and should be tailored to different stakeholder audiences.

Relationship to Information Governance and IT Governance

DMBOK2 carefully distinguishes Data Governance from related governance disciplines. INFORMATION GOVERNANCE is a broader superset that encompasses the governance of all forms of information including unstructured documents, records, email, and multimedia content, not just structured data. IT GOVERNANCE focuses on the governance of technology infrastructure, systems, and IT services (commonly addressed by frameworks like COBIT and ITIL). DATA GOVERNANCE specifically addresses the governance of data assets, including data quality, metadata, policies, standards, and data-related decision rights. These three disciplines overlap significantly: IT Governance provides the technology infrastructure that Data Governance relies on; Information Governance provides the broader organizational context within which Data Governance operates. For the exam, remember that DMBOK2 focuses specifically on data governance as the central hub of the data management framework.

Best Practices

✓ Use the DAMA Wheel as an organizing framework to ensure all knowledge areas receive appropriate attention and investment in your data management program
✓ Develop a comprehensive data management strategy with a documented vision, business case, guiding principles, goals, governance framework, and phased delivery roadmap
✓ Align data management strategy explicitly with business strategy — demonstrate how data management supports specific business objectives and initiatives
✓ Conduct a baseline maturity assessment across all knowledge areas before planning improvements to identify gaps and prioritize investments
✓ Ensure data management operates at all three levels (strategic, tactical, operational) with clear connections between long-term planning and day-to-day execution
✓ Invest in organizational change management from the start — executive sponsorship, stakeholder engagement, communication, and training are essential for adoption
✓ Articulate the data management value proposition in business terms (risk reduction, cost savings, revenue growth, compliance) rather than technical terms
✓ Define data management roles and career paths to attract, develop, and retain data management professionals within the organization
✓ Use the standardized context diagram approach (goals, activities, inputs, outputs, metrics) to plan and communicate each knowledge area's scope and responsibilities
✓ Treat data management as an ongoing program with continuous improvement, not as a one-time project with a fixed end date
✓ Establish foundational principles (data is an asset, metadata is essential, enterprise perspective is required) and communicate them widely as the basis for decision-making
✓ Build a data management community of practice within the organization to share knowledge, develop skills, and maintain engagement across business and IT participants

💡 Exam Tips

★ Data Management Process is 2% of the exam — expect approximately 2 questions, but the foundational concepts from this chapter appear throughout all other knowledge areas
★ The DAMA Wheel places Data Governance at the CENTER — this is a commonly tested fact. Know that governance is the hub connecting all ten surrounding knowledge areas
★ Know all eleven knowledge areas by name and be able to identify which chapter and topic each covers — the exam may test your ability to categorize activities to the correct knowledge area
★ Understand the three levels: Strategic (vision, strategy, business case), Tactical (architecture, policies, standards, models), Operational (day-to-day execution, DBA, ETL, monitoring)
★ Data management maturity levels follow the CMMI model: Initial, Repeatable, Defined, Managed, Optimized — know characteristics of each level and that most organizations start at Level 1-2
★ DMBOK2 emphasizes data management is a BUSINESS function enabled by technology, not purely an IT function — questions may test this distinction
★ The data lifecycle stages (Plan, Create/Obtain, Store/Maintain, Use, Enhance, Archive, Dispose) may be tested — know that governance applies across ALL stages
★ Executive sponsorship is consistently identified as the single most critical success factor for data management programs — this appears frequently across exam topics
★ Distinguish between Data Governance (data assets), IT Governance (technology/systems), and Information Governance (all information types) — know that Information Governance is the broadest of the three
★ The DAMA Principles establish that data is an asset, data does not deplete with use, data's value increases when shared, and it takes metadata to manage data — these fundamental principles may appear in exam questions
★ Know that a data management strategy requires: vision, business case, guiding principles, goals, governance framework, delivery roadmap, and metrics
★ Remember that organizational change management is a key theme in DMBOK2 — questions may ask about communication, training, quick wins, and resistance management as components of successful data management implementation