Data Management

Definition

In business architecture, data management refers to the disciplines, policies, and organizational structures that govern how data is defined, created, stored, protected, shared, and retired across the enterprise. It spans everything from data quality and data governance to metadata management, master data management, and data security — treating data as a strategic asset rather than a byproduct of applications. Business architects typically engage with data management at the level of information concepts and data domains (e.g., Customer, Product, Contract), mapping them to the capabilities that create or consume them, rather than the technical schemas or database structures that data architects and engineers own. It's important to distinguish data management from data architecture and IT data operations. Data architecture defines the technical structures, models, and integration patterns that store and move data; data management is the broader governance and stewardship layer that decides what data means, who owns it, what quality standards apply, and how it should be used across business processes. A capability map might show "Customer Data Management" as a business capability; the underlying customer master data model, ETL pipelines, and database schemas are architecture and engineering concerns that implement that capability. Good data management also has clear boundaries: it does not include the business logic embedded in applications, nor does it substitute for information security architecture, though the two are tightly coupled. Instead, it functions as connective tissue — ensuring that as capabilities, value streams, and processes execute, they draw on data that is trustworthy, consistently defined, and appropriately governed regardless of which system or business unit touches it.

Origin & Context

The formalized discipline of data management is most closely associated with DAMA International's Data Management Body of Knowledge (DMBOK), which codified data governance, quality, and stewardship as enterprise-wide practices distinct from IT database administration. Business architecture practice, as reflected in the BIZBOK Guide from the Business Architecture Guild, incorporates data management by cross-mapping information concepts and data domains to capabilities and value streams, ensuring data accountability is tied to business ownership rather than left solely to IT.

Why It Matters

CIOs and Chief Data Officers care about data management because inconsistent or poorly governed data quietly drives up the cost of every downstream initiative — from regulatory reporting to AI adoption, since models and analytics are only as reliable as the data feeding them. Business architects use data management mapping to identify where the same data concept (like "customer") is defined differently across business units, a common root cause of failed system integrations and stalled M&A consolidations. Getting data ownership and quality standards right at the business capability level, rather than negotiating it system-by-system, materially reduces rework and accelerates any transformation that depends on trusted, shared data.

Common Misconceptions

Myth: Data management is an IT responsibility handled by database administrators and data engineers.

Reality: While IT implements the technical infrastructure, accountability for data definitions, quality standards, and stewardship decisions belongs to the business. Business architects help formalize this by assigning data domain ownership to specific capabilities and roles, not to the IT department by default.

Myth: Data management and data governance are the same thing.

Reality: Data governance is a subset of data management focused specifically on decision rights, policies, and accountability structures for data. Data management is the broader discipline that also includes data quality management, metadata management, master data management, and data lifecycle practices.

Myth: Once a master data management (MDM) tool is implemented, data management is solved.

Reality: MDM tooling addresses technical consolidation of records, but without business-defined data ownership, quality rules, and capability-level accountability, organizations often end up with a single technical source of truth that different business units still interpret and use inconsistently.

Practical Example

A regional bank's business architecture team was mapping capabilities for a digital lending initiative and discovered that "Customer" was defined and maintained differently across retail banking, wealth management, and commercial lending — each with its own onboarding process and data attributes. The lead business architect facilitated a cross-mapping exercise, linking the Customer Data Management capability to each affected value stream and identifying which business unit should own the authoritative customer record. Working with the Chief Data Officer, they established a single accountable data steward role for the Customer domain and defined shared quality standards for identity verification fields. This capability-level ownership model gave the digital lending program a trusted data foundation, avoiding the redundant reconciliation work that had plagued a prior cross-unit initiative and giving compliance teams a defensible answer to regulators about data lineage.

Industry Applications

Financial Services

Data management underpins regulatory reporting and KYC/AML compliance, where business architects map customer, account, and transaction data domains to capabilities to ensure consistent definitions across retail, commercial, and wealth divisions.

Healthcare

Patient and clinical data management is mapped to capabilities like Patient Records Management and Care Coordination, helping architects identify where inconsistent patient identifiers create safety and interoperability risks across care settings.

Manufacturing

Product and supplier master data management is tied to capabilities such as Product Lifecycle Management and Supply Chain Planning, reducing costly errors from inconsistent part numbers or specifications across plants and ERP instances.

Related Terms

• Business Capability: The structure business architects use to assign accountability for data domains
• Data Architecture: The technical modeling discipline that implements data management policies in systems