Data Management

Laying the groundwork (DAMA)

💡Data as an Asset: The organisation recognizes data as a critical asset for insights, innovation, and achieving strategic goals.

💡Intentional Management: Extracting value from data requires planning, coordination, leadership, and management.

What is Data Management?

The development, execution, and supervision of plans, policies, and practices to deliver, control, protect, and enhance data value throughout its lifecycle [1].

Data Management

Who is a Data Professional?

• Roles range from technical (e.g., database administrators) to strategic (e.g., Chief Data Officers).
• Require both technical and business skills.
• Must collaborate across IT and business functions to ensure high-quality data meets organizational needs.

Here, we will discuss the principles of Data Management. Why data management matters in an organization.

Business Drivers — Why we manage data.

Business drivers are the core reasons or forces pushing an organization to invest in and improve data management. Think of them as the engine behind the effort.

Key Business Drivers include:

• The need for better decisions based on reliable data.
• Competitive advantage through insights about customers, products, and services.
• Avoiding waste, risk, and inefficiency caused by poor data.
• Meeting regulatory and compliance requirements.
• Supporting innovation and strategic goals through quality information.

📌 Example: “We need clean customer data to personalize marketing and increase sales.”

Goals — What we want to achieve

Goals are the desired outcomes of data management. They define what successful data management looks like.

Typical Goals include:

• Understanding and supporting the information needs of stakeholders.
• Ensuring data quality, privacy, and security.
• Preventing unauthorized access or misuse of data.
• Ensure data is usable, accessible, and adds value to the enterprise.

What is Data?

In its most basic sense, data is a representation of facts about the world — a way to capture reality so it can be stored, analyzed, and acted upon.

“Data is an interpretation of the objects it represents and an object that must be interpreted.”[2]

Data is Not the Same as Truth

We often think of data as truth, but it’s a representation — not the thing itself, but a version of it.

Example: Imagine a map. The map shows roads, borders, and rivers — but it’s not the territory.

• The map = data
• The territory = real world

Similarly, a sales number (like “42 units sold”) represents many real-life activities (calls made, orders placed, items shipped) but doesn’t capture the entire story.

………………………………………………………

Types of Data

Structured data — Data stored in organized formats like rows and columns.

• Example: A spreadsheet with customer names, emails, and purchase dates.

Unstructured data — Rich, often textual or multimedia content.

• Example: Audio recordings from customer service calls.
• Example: Product photos posted by customers.

………………………………………………………

Data Can Be Anything Now

Technological advances have expanded what we call “data”:

• Your heart rate from a smartwatch.
• Your Netflix watch history.
• The noise levels are captured in a smart city.
• The clicks you make on a website.

Even your Saturday dinner menu can be stored, shared, analyzed — and used by a food app to recommend a new recipe. That’s data.

………………………………………………………

Context Makes It Useful

Data alone isn’t valuable unless we know what it means.

Example: The Date Problem

• “03/04/2025” — Is that March 4th or April 3rd?
• It depends on context — which country you’re in and which system you use.
• Without context (called Metadata), the meaning is unclear.

………………………………………………………

Data is Shape-Shifting

Different departments or systems might represent the same idea in different ways:

“Customer”:

• In Sales: someone who bought something.
• In Support: someone who submitted a ticket.
• In Billing: someone with an invoice.

So, “customer” data may look different across departments, confusing unless standardized.

………………………………………………………

Why Managing Data is Hard

• It’s intangible — You can’t touch data like you touch a car or a chair.
• It’s easily copied — Unlike physical objects, one piece of data can be in 100 places at once.
• It’s easy to misuse — Just a small error in data can cause big consequences.

………………………………………………………

Quick Metaphor: Data is Like DNA

• It’s coded information.
• It defines how things function.
• It’s passed down, copied, and mutated.
• Without understanding it, you can’t build or repair anything complex.

………………………………………………………

Data and Information — What’s the Difference?

These two terms are often used interchangeably, but understanding the distinction (and the relationship) is key in data management.

Data is unprocessed, unorganized, and context-less. When data is organized and interpreted, it becomes information.

Data vs Information

Data = Raw Facts

Think of it like individual puzzle pieces. Example:

• “82”
• “London”
• “2025–04–11”

On their own, they don’t mean much.

Information = Data in Context

Putting the pieces of the puzzle together will make sense. Example:

• “82 people registered for the Data Summit in London on 2025–04–11.”

A famous DIKW pyramid is a classic model in information science.

DAMA’s Critique of the Pyramid

“Data does not simply exist. It must be created.”[1]

1. Data isn’t found — it’s designed and recorded.

• Someone must decide what to capture and how.

2. It takes knowledge to create data.

• Ex: A camera roll doesn’t become information until someone categorizes or describes it.
• To record “customer churn,” we must know:
• — What counts as a “customer”
• — What defines “churn”

3. Data and information are not separate; they are intertwined.

• A dataset can be both raw and informative depending on who uses it and how.

Simple Analogy: Data is Juice’s Ingredients, Information is the Juice

• Data: Oranges, apples, sugar, water.
• Information: The mixed, processed juice you drink.
• Without knowing what the ingredients are (context), you don’t know what you’re drinking.

They Transform Each Other

• Data becomes information when structured for a purpose.
• Information can generate new data when analyzed.

Ex: Quarterly Sales Report

• Data: Raw transactions from POS systems.
• Information: Summary of total sales per region.
• New Data: Quarterly growth rate calculated from past data.

………………………………………………………

Data as an Organizational Asset

Data is not just support material — it’s a core asset that drives business success, just like:

• Financial capital
• Physical infrastructure
• Human resources

What is an “Asset”?

An asset is something that provides value, can be controlled, and has economic potential.

So… Why is Data an Asset?

1. It helps you make better decisions.
2. It can generate revenue (through analytics, targeting, etc.).
3. It has long-term value if maintained properly.
4. It is critical to daily operations (no transactions, no reports without it).

Examples:

Examples

Monetization is Growing

More companies are now:

• Valuing their customer data like intellectual property.
• Selling data to third parties (e.g. analytics or market research).
• Using data as a core product.

In the future, data may be listed on balance sheets, just like “goodwill” or patents.

………………………………………………………

Core Data Management Principles

There are a few defined principles designed to guide organizations in managing their data effectively, ensuring it supports operational needs and long-term strategic goals.

Part 1: The Foundation — Building the Asset

1. Data is an ASSET Treat data like a prized possession — it powers your organization like fuel.

2. An asset must be MEASURABLE If we can’t assess its worth, we can’t manage it. Like knowing the property value.

3. To be valuable, it must have QUALITY Garbage data = garbage decisions. Good data = power.

4. But how do we manage data quality? We need METADATA Metadata is like labels and instructions — it tells us what the data means.

Part 2: The Planning — Building the System

5. To create and manage metadata, we must PLAN Just like city planning — where will data live, how will it flow?

6. Every plan needs a LIFECYCLE From birth (creation) to retirement (archival or deletion).

7. But different data types have DIFFERENT NEEDS Not all roads are highways — some are alleys. Be flexible.

8. With variation comes RISK Misuse, loss, or breach — protect your digital city.

🏛️ Part 3: The Strategy — Governing the City

9. Different teams manage different data — that’s CROSS-FUNCTIONAL Like different city departments — police, transport, parks — all managing parts of the city.

10. Multiple teams bring MULTIPLE PERSPECTIVES The city must listen to its citizens — the users of data.

11. So we need an ENTERPRISE PERSPECTIVE The mayor (leadership) must see the full map.

12. Technology decisions must follow ORGANIZATION NEEDS Don’t build a shiny bridge to nowhere. Strategy first, tools second.

13. Above all, success depends on LEADERSHIP COMMITMENT The mayor must lead the data revolution. Without buy-in, nothing moves.

Data Management Principles

………………………………………………………

Data Management Challenges [1]

1️⃣ Value & Asset Awareness

Challenges where organizations fail to treat data as a real business asset.

• Data differs from other assets
• Valuing data is hard
• Lack of leadership commitment

📌 Theme: “We don’t truly see the value of our data.”

2️⃣ Quality & Trust Issues

Challenges that affect the reliability and usability of data.

• Poor data quality
• Lack of metadata
• Different data types need different handling

📌 Theme: “Even if we have data, we can’t trust or use it well.”

3️⃣ Planning & Architecture Gaps

Challenges stemming from the absence of foresight or structure.

• Lack of planning
• Ignoring the data lifecycle

📌 Theme: “We’re building without a blueprint.”

4️⃣ Governance & Coordination Problems

Challenges tied to organizational silos, misalignment, or disconnection.

• Siloed management/lack of coordination
• Enterprise-wide thinking is rare
• Multiple perspectives are overlooked

📌 Theme: “Everyone’s doing their own thing.”

5️⃣ Strategic Misalignments

Challenges that result when technology drives the strategy instead of serving it.

• Tech drives strategy instead of the other way around

📌 Theme: “We’re following the tools, not the needs.”

6️⃣ Risk & Ethics

Challenges involving security, compliance, and data misuse.

• Data brings risk

📌 Theme: “We’re exposed and unprepared.”

…………………………………………………………….

Data Lifecycle [1]

Let’s understand it with the help of our friend Aisha. She has a successful coffee shop — ‘Cafe Insights’. I asked her about the secrets of success in such a crowded market space.

She told me that she followed a series of simple steps,

Plan

Before serving her first cup of coffee, Aishaplanned everything. She asked herself,

• What kind of data will help me run Cafe Insights better?
• What should I track: customer preferences, sales, inventory, employee shifts?

Design & Enable

To bring her plan to life, she designed systems:

• A POS (Point of Sale) system for transactions,
• A feedback form for customer satisfaction,
• Inventory software to track beans and milk,
• Wi-Fi that logs customer traffic patterns.

Create/Obtain

Once opened, Cafe Insights began collecting data daily:

• Every order entered the POS.
• Every customer review landed in her feedback form.
• Suppliers emailed delivery records.

Store/Maintain

The data is automatically stored in a secure database.

• Cloud backups ensured nothing was lost.
• Old reviews were archived.
• Employee access was managed with passwords.

Use

Each week, Aisha reviewed dashboards and reports:

• Cappuccinos were top sellers on rainy days,
• Vegan pastries sold best on weekends,
• Coffee bean inventory always ran low on Thursdays.

She used data to optimize menus, optimize staff, and reduce waste.

Enhance

One day, she enhanced her customer's data with insights from a loyalty app. Now she could:

• Personalize offers (free soy latte on birthday!),
• Bundle slow-moving items with bestsellers,
• Refine her marketing campaigns.

Dispose of

Years passed, and some old suppliers' records were no longer needed. Aisha safely deleted outdated files, followed privacy guidelines, and reduced legal risks.

She ensured customer data was only kept as long as it was needed.

Data Lifecycle (inspired by [1])

………………………………………………………

Data Management Strategy

A data strategy outlines how an organization will use data to gain a competitive edge and achieve its business goals. It starts by understanding what data is needed, how to collect, manage, and trust it over time, and how to turn it into value.

This strategy must be supported by a Data Management program — a plan focused on ensuring data quality, integrity, accessibility, and security, while also addressing risks and ongoing data-related challenges.

There are various components for a data management strategy. Let’s organise them and understand them using a real-world example.

Imagine you’re working for a city transit authority launching a Smart Bus System. The goal is to improve route efficiency, monitor usage, and give citizens real-time updates.

1. Purpose & Direction (Why & Where)

Purpose & Direction

2. Scope & Framework (Who & What)

Scope & Framework

3. Design & Tools (How)

Design & Tools

4. Execution & Evolution (When & How Much)

Execution & Evolution

SMART Objectives

It makes the strategy actionable, trackable, and realistic. For our Smart Bus System,

• Specific: Track bus delay time with GPS.
• Measurable: Reduce average delay by 20%.
• Achievable: Within 12 months, using existing GPS tech.
• Relevant: Aligns with the city’s green & commuter happiness goals.
• Time-bound: The Pilot will be completed in 6 months, and the rollout will be in 12.

………………………………………………………

Data Management Framework

A structured model that organizes all the functions, roles, processes, and tools needed to manage the data effectively across an organization.

Think of it as a “blueprint” or “map” for your data landscape.

Because every organization is different, by industry, data scope, culture, and maturity, data management approaches will vary. That’s why frameworks are essential: they help visualize how data functions connect, align teams, clarify strategy, and guide decision-making.

Frameworks [1]

Business-IT Bridging Frameworks, *Help align business strategy with IT/Data Execution.

• *Strategic Alignment Model (SAM)
• Amsterdam Information Model (AIM)

Function Scope & Capability Models, *Clarity of roles, responsibilities, and functions across data domains.

• *DAMA-DMBOK Framework (The DAMA Wheel)
• DAMA Data Management Framework (Evolved)

Maturity & Growth Models, Visualize progression toward mature data practices. - DMBOK Pyramid (Peter Aiken’s Model)

Strategic Alignment Model

Originally developed by John C. Henderson & N. Venkatraman (1999)

The SAM model helps organizations to align businesses and IT Strategies, ensuring that Data and Tech support the Business goals rather than operating in isolation. Think of it as a bridge between vision and execution.

There are four key domains in SAM,

Business Strategy

What the company wants to do to succeed. Things like what products to sell, who to sell to, and how to compete.

IT Strategy

How technology will support the business goals. What kind of tech to use, and how it helps the business do better.

Organizational Infrastructure & Processes

How the business is set up to run. Who does what, company rules, and daily work processes.

I/S Infrastructure & Processes

The tech setup and how it runs. Computers, software, networks, and IT teams that keep everything working.

And they are related as,

SAM — Henderson & Venkatraman [3]

Think of it like this,

What we want to do (business) must match How we are built to do it (organization) What tech do we use (IT) How tech is run (IT operations)

What is Strategic Integration? It refers to aligning an organisation’s strategic goals and its internal capabilities and structures, especially how business strategy and IT (or data) strategy work together to achieve long-term goals.

What is Functional Integration? It refers to the operational alignment between business processes and the IT infrastructure that supports them.

While Strategic integrations align long-term goals, functional integration ensures that daily operations, tools, workflows, and systems work together effectively.

Limitations: Why SAM Needs Supplements

Limitations of SAM

Amsterdam Information Model

Originally developed by Abcouwer, A.W.; Maes, R.E.; Truijens, J.H.J.M.

This is also called the 9-cell model. The authors extended the SAM model by adding a row and a column.

AIM introduces a specific focus on the real information and communication flows by explicitly incorporating organizational and IT structure as a critical dimension that interacts with strategy and execution.

SAM to AIM

A question that should pop into your head is, what value does an extra row or column add? This extra column emphasizes the management of information between Business and IT. It emphasizes that generating, acquiring, processing, storing, distributing and especially using information should take a central place in organizational thinking [6].

When represented in a 3×3 Matrix, each Cell represents a different management concern.

9-cell Grid

There are different aspects in which AIM differs from SAM.

Comparison with SAM

Example: Airline Use of AIM

Let’s take an airline scenario:

Airline Example

DAMA-DMBOK Framework (The DAMA Wheel)

This framework is the central model created by DAMA International to define and organize core data management functions across organizations.

Think of the “DAMA Wheel” [1] as the standard playbook for getting your data ducks in a row at work. It’s the go-to guide professionals and companies use to set up organized data management and keep things tidy.

It is a comprehensive, structured model that organizes 11 core data management knowledge areas [1], all centred around Data Governance.

Purpose

• Provide a common language and structure for managing data.
• Guide organisations in building mature, consistent data practices.
• Acts as a reference model for strategy, implementation, and training.

The eleven knowledge areas are,

*Data Governance

• *Decision rights, stewardships, policies.

*Data Architecture

• *Frameworks, models, and principles for organizing the data.

Data Modelling & Design - Entity relationships, logical & physical models.

Data Storage & Operations - Databases, backups, availability, performance.

*Data Security

• *Protection, access control, privacy.

*Data Integration & Interoperability

• *Moving, transforming, and linking data across systems.

Document & Content Management - Managing unstructured data, documents, and media.

*Reference & Master Data

• *“Single source of truth” for core business data.

*Data Warehousing & BI

• *Reporting, dashboards, analytics.

*Metadata Management

• *“Data about Data” — Lineage, definitions, ownerships.

*Data Quality Management

• *Accuracy, completeness, consistency.

At the Centre: Data Governance Data Governance is the heart of the framework. It supports and connects all the disciplines by:

• Setting policies
• Enabling stewardships
• Defining accountability

Data Wheel [1]

Visual Summary

• All areas are interconnected.
• None should be managed in isolation.
• Governance anchors and coordinates the others.

Multiple factors affect how data is managed in an organization. “Environmental Factors Hexagon” explains this. At the centre of this picture are goals and principles.

This means that the way people work with data and the tools they use should all be based on the organization's goals and data guidelines.

The hexagon also shows the connection between,

• People — Individuals who work with and manage the data.
• Process — Steps and procedures used to handle data.
• Technology — Tools and systems used for data management.

DAMA Environmental Factors Hexagon [1]

The Knowledge Area Context Diagram

This explains how each Data Management Knowledge Area (like Data Quality, Metadata, etc.) is structured internally in the DAMA-DMBOK Framework.

Each Knowledge Area is broken down into standard components to fully describe:

• What is it?
• What it does;
• How it operates.
• Who is involved?
• What success looks like.

The 12 Components of Knowledge Area Context,

1. Definition: What the Knowledge Area is about.
2. Goals: Why it exists and what it aims to achieve.
3. Activities: Key tasks performed (Plan, Develop, Control, Operate)
4. Inputs: What is needed to start the activities?
5. Deliverables: Outputs or artefacts produced.
6. Roles and Responsibilities: Who does what?
7. Suppliers: Who provides inputs?
8. Consumers: Who benefits from outputs?
9. Participants: Those who perform, manage, or approve activities.
10. Tools: Software or technologies used.
11. Techniques: Methods and best practices followed.
12. Metrics: How performance and success are measured.

Why So Many Models? Because Data Is a Stage with Many Acts.

The DAMA Wheel gives us the cast of characters — the 11 Knowledge Areas. The Knowledge Area Hexagon reveals the scripts' goals, tools, roles, and deliverables. The Context Diagram zooms in to show the scenes — the who, what, how, and why behind each act.

But together, they build a full production — a structured, strategic, and human view of how we manage and master data.

While the DAMA Wheel, Hexagon, and Context Diagrams each illuminate parts of the data management world, none connect the dots between the Knowledge Areas. There was no map for how they depend on, strengthen, or enable each other.

To fill this gap, efforts were put into evolving these models, resulting in the following frameworks.

DMBOK Pyramid (Peter Aiken’s Model)

Aiken’s Model lays down a logical progression of the phases that an organization could follow to achieve a solid foundation for Data Management.

Aiken’s Four Stages

Phase 1: Application + Basic Infrastructure Setup

• The organization purchases an application with a database[1].
• Starts foundational work — Data Modelling & Design, Data Storage, Basic Data Security.
• Integration and interoperability efforts begin to connect the system to the environment and other data sources[1].

Phase 2: Confronting Data Quality Challenges

• As the system is used, data quality problems emerge.
• Achieving better data quality requires: — Reliable Metadata [1]. — Consistent Data Architecture[1]
• Without architecture and Metadata, different systems conflict.

Phase 3: Establishing Data Governance and Expanding Disciplines

• To sustain data quality and metadata management, Data Governance must be established.
• Governance provides structure and accountability.
• Enables the execution of broader disciplines: — Document and Content Management. — Reference Data Management. — Master Data Management. — Data Warehousing. — Business Intelligence.

Phase 4: Leveraging Well-Managed Data for Advanced Analytics

• With governance, high-quality. standardized data, the organization can: — Fully enable advanced analytics. — Drive predictive insights, machine learning, AI projects, and business strategy with confidence.

Phase 1 → Phase 2 → Phase 3 → Phase 4
(App + Storage) → (Fix Quality + Metadata) → (Governance + Discipline) → (Advanced Analytics)

Why This Model Matters

• It stops the ‘Skip to AI’ madness without foundation.
• It forces maturity step-by-step.
• It ensures real value is extracted safely and sustainably from data.

DAMA Data Management Framework (Evolved)

Sue Geuens’ model, found within the DAMA-DMBOK2 framework [1], presents a way to understand how different parts of data management work together, especially in Business Intelligence (BI) and Analytics.

Seu Geuen’s model

Think of it like building a house,

• BI and Analytics are like the residents of the house. They are the ones using the information to make decisions and gain insights.
• The house also needs essential utilities like Master Data (the key information about important things like customers or products) and a well-organized Data Warehouse (where lots of information is stored and prepared for analysis).
• These utilities, in turn, rely on feeding systems and applications [1]. These are like the pipes and wires bringing in water and electricity to the house.
• For the residents to live comfortably, the house needs strong foundations like reliable Data Quality, good Data Design, and practices that allow different data systems to work together.
• Finally, Data Governance acts like the homeowner’s association or the building codes. It sets the rules and guidelines for how all these parts of data management should be handled and how they should depend on each other.

In the end, this is just the beginning. As we step into the world of the Eleven Knowledge Areas and more, we will unlock the true depth and potential of the data management framework — a journey toward mastery, precision, and endless possibilities.

Sources:

1. DAMA DBOK, Second Edition.
2. Unknown
3. CIO — Wiki. Retrieved from here.
4. Summary of the SAM. Retrieved from here.
5. Contouren van een generiek model voor informatiemanagement. Retrieved from here.
6. Vision on information management. Retrieved from here.