Common Data Models and Organisational Meaning

Why Shared Meaning Matters

Modern organisations depend upon shared meaning.

Between people,
within teams,
about systems,
about processes,
for using AI tools,
to develop and understand reports,
to support governance mechanisms,
and other operational practices.

All of these depend upon language and concepts that are understood consistently across the organisation and communicated coherently with external stakeholders.

When meaning fragments:

coordination weakens,
learning slows,
trust declines,
integration becomes difficult,
and organisations increasingly struggle to act coherently under pressure.

The result is not merely “poor data quality.” The result is organisational fragmentation and fragile communication.

Different parts of the organisation begin operating with:

different assumptions,
different definitions,
different classifications,
and different interpretations of reality.

Over time, this reinforces siloed thinking, in which business units, functions, systems, and teams increasingly optimise for local meaning rather than a shared organisational understanding.

The result is not merely communication difficulty.

It creates hidden structural fragility that is often difficult to detect until operational stress, transformation, regulatory pressure, or organisational disruption exposes it.

👉 Fragmented meaning produces fragile, fragmented organisations.

Common Data Models Are Not Just Technical Artefacts

A Common Data Model (CDM) is often misunderstood as:

a database structure,
an integration tool,
or a technical architecture exercise only of interested to IT people.

In practice, a CDM performs a much deeper organisational role.

It provides:

shared organisational language,
consistent definitions,
semantic boundaries,
relationship clarity,
and organisational memory.

A well-designed CDM becomes part of the organisation’s shared understanding of itself.

A well-developed Common Data Model provides stable organisational meaning across:

business units,
with external stakeholders,
technology platforms,
governance processes,
analytics,
AI systems,
and operational practice.

Once the CDM is developed collaboratively, aligned with the BCM, and validated operationally through Gemba, the core semantic structures often become remarkably stable over time.

Systems may change.
Applications may be replaced.
Processes may evolve.
Organisational structures may shift.

However, the underlying organisational meaning frequently remains comparatively stable.

This stability is one of the reasons BCMs and CDMs form a critical part of the organisational Knowledge Base.

They provide enduring reference structures for:

shared language,
organisational memory,
governance,
learning,
integration,
proactive data and information quality management,
and adaptive coordination.

The goal is therefore not merely technical integration.

The goal is coherent organisational understanding sustained over time.

Shared Language and Organisational Glossaries

Every organisation already possesses a language.

The problem is that the language is often:

inconsistent,
implicit,
fragmented,
or locally interpreted.

Different teams may use the same term differently:

customer,
asset,
agreement,
incident,
risk,
service,
project,
or capability.

At the same time, different terms may describe the same underlying concept.

Over time this creates:

confusion,
data redundancy,
reporting inconsistency,
integration failure,
and disagreement about operational reality.

A Common Data Model helps establish:

common language,
shared definitions,
controlled vocabularies,
and organisational glossaries.

This does not eliminate complexity.

It creates stable reference points that allow complexity to be navigated more coherently.

👉 Shared language strengthens shared understanding.

Shared Meaning Before Technology

Technology changes constantly, but the meaning of the data used persists longer because:

Systems are replaced.
Platforms evolve.
Applications are upgraded.
AI tools emerge rapidly.

.However, organisations still need a stable understanding of:

what things are,
how they relate,
who owns them,
and why they matter.

The CDM therefore becomes:

a bridge between organisational meaning and operational structure,
a foundation for organisational memory,
and a stabilising mechanism for organisational learning.

📖 In Adapt, Survive and Flourish, this enduring organisational understanding is presented as part of the Knowledge Base.

The Knowledge Base is not merely a repository of documents, models, or technical artefacts. It encompasses the shared structures, language, relationships, definitions, patterns, and operational understanding developed collectively across the organisation over time.

The BCM and CDM take that foundational role because together they capture and stabilise:

organisational meaning,
capability ownership,
semantic relationships,
governance understanding,
and shared mental models.

This stability allows organisations to maintain coherence even as:

people change,
systems evolve,
technologies are replaced,
and organisational structures shift.

Without this stable foundation, organisations increasingly rely on fragmented interpretations, isolated knowledge, and informal reconciliation efforts to sustain coordination.

👉 The Knowledge Base helps organisations preserve coherent meaning while continuously adapting operationally.

One-to-One Correspondence and Semantic Integrity

A key principle in strong modelling practice is semantic clarity.

Where possible:

one concept,
one meaning,
one definition.

All validated in Gemba by the people who use them operationally.

This creates clearer relationships between:

language,
models,
data,
governance,
business units,
and operational practice.

When multiple meanings are attached to the same concept, or when different concepts are ambiguously merged, organisational confusion increases rapidly.

This principle of one-to-one correspondence helps reduce:

semantic drift,
duplicate meaning,
hidden assumptions,
and structural incoherence.

It strengthens:

trust,
traceability,
governance,
and learning consistency.

The goal is not bureaucratic perfection. The goal is reducing ambiguity where ambiguity creates operational risk.

The Relationship Between BCM and CDM

Business Capability Models (BCMs) and Common Data Models (CDMs) complement each other. The BCM outlines the organisation’s necessary capabilities, ‘what the business does’, while the CDM specifies ‘what the business deals with’, that is, the meaning and context of the data needed to perform these functions consistently. Together, they form a key part of the organisation’s knowledge infrastructure.

The BCM provides:

structural coordination,
capability boundaries,
ownership,
and organisational context.

The CDM provides:

semantic coherence,
shared language,
relationship meaning,
and information integrity.

When aligned together organisations improve their ability to:

coordinate activity,
share understanding,
integrate systems,
support governance,
and learn adaptively over time.

📖 Adapt, Survive and Flourish explores this stability through a comparison between a bank operating in 1910 and one operating in 2025.

Although technologies, channels, regulations, and operating environments have changed dramatically, many of the core organisational data concepts remain recognisable across both eras:

customers,
accounts,
agreements,
transactions,
applications,
transaction risk.
customer risk.

The example highlights an important insight:

While operational implementation evolves continuously, the underlying organisational meaning often remains comparatively stable over long periods. This is why the BCM and CDM are foundational.

This is why the models are not merely technical artefacts. They become part of the organisation’s holistic shared mental model.

Socialisation and Shared Understanding

Strong models are rarely produced in isolation.

The most effective modelling emerges through:

dialogue,
workshops,
storytelling,
challenge,
reflection,
and operational validation.

This aligns closely with:

SECI,
shared mental models,
stakeholder engagement,
and organisational learning.

The modelling process itself becomes a mechanism for:

building social capital,
developing shared language,
surfacing hidden assumptions,
and strengthening adaptive capacity.

In this sense, the value is not merely the finished diagram.

The value is the shared understanding developed through creating it together.

👉 The model is not the outcome. Shared understanding is.

Why Vendor Data Models Are Not Enough

One of the most common arguments against developing a Common Data Model is:

“We already have SAP, Oracle, Salesforce, or another enterprise platform — the data model already exists.”

At a technical level, this is partially true.

Enterprise platforms contain highly sophisticated internal data structures designed to support broad operational capability across many organisations and industries.

However, vendor data models are not the same thing as organisational meaning.

Vendor models are designed primarily to support:

software functionality,
transactional consistency,
platform integration,
and generic industry requirements.

They cannot fully represent:

local organisational meaning,
stakeholder language,
operational nuance,
governance interpretation,
organisational boundaries,
or the tacit understanding developed within a specific organisation.

Without organisational modelling, the organisation often adapts itself to the language and assumptions of the software platform.

Over time, this can create:

semantic drift,
siloed interpretation,
hidden workarounds,
fragmented ownership,
and loss of organisational learning.

The result is that the platform effectively becomes the organisation’s de facto meaning system.

This is one of the reasons many organisations struggle to distinguish between:

enterprise understanding,
application structure,
process configuration,
and operational reality.

A Common Data Model helps organisations retain ownership of their own meaning.

It provides a stable semantic layer that allows enterprise platforms, analytics tools, AI systems, governance processes, and operational practice to align around shared organisational understanding rather than software-driven interpretation.

👉 Applications support operations. The Knowledge Base preserves organisational meaning.

They cannot fully represent:

local organisational meaning,
stakeholder language,
operational nuance,
governance interpretation,
organisational boundaries,
or the tacit understanding developed within a specific organisation.

Without organisational modelling, the organisation often adapts itself to the language and assumptions of the software platform.

This creates an important organisational learning challenge.

Vendor models are developed from the accumulated experience, assumptions, patterns, and mental models of external designers, consultants, industries, and implementation teams.

They may be technically sophisticated and highly capable.

However, they are not automatically the organisation’s shared mental model.

Shared understanding only develops when meaning is actively socialised through:

discussion and dialogue,
workshops,
challenge and negotiation,
operational testing,
group reflection,
and Gemba-based learning.

This socialisation process is critical because it allows people across the organisation to:

question assumptions,
clarify meaning,
build shared language,
surface hidden conflicts,
and collectively internalise the model into operational practice.

Without this process, organisations often implement systems successfully yet fail to develop a coherent, shared understanding.

The result may be technically integrated systems operating within socially fragmented organisations.

👉 Technology can be deployed quickly. Shared meaning must be learned together.

AI, Modelling, and Organisational Meaning

AI can now generate:

candidate entities,
relationships,
structures,
patterns,
and models at extraordinary speed.

This creates significant opportunities for:

modelling acceleration,
pattern exploration,
human capability augmentation,
organisational learning,
and the strengthening of social and human capital.

However, AI does not inherently understand:

operational reality,
stakeholder consequence,
organisational politics,
boundary intent,
or lived organisational meaning.

AI is strongest at:

explicit knowledge discovery, analysis and delivery,
pattern generation,
structural exploration,
and relationship suggestion.

Humans remain responsible for:

meaning,
judgement,
context,
ethics,
and operational validation.

This is why Human–AI modelling should remain:

guided,
socialised,
iterative,
and consequence-aware.

Human–AI modelling is not simply a primitive ask/respond interaction.

The strongest outcomes emerge through iterative dialogue, where:

questions,
structures,
assumptions,
relationships,
definitions,
and perspectives

are progressively explored, challenged, refined, and socialised together.

In this sense, AI functions less as a passive query engine and more as a conversational modelling partner within a human-guided learning process.

The quality of the outcome depends not only on the technology itself but also on the organisation’s ability to:

engage critically,
reflect collectively,
validate operationally,
and build shared understanding through dialogue over time.

👉 AI accelerates modelling. Humans remain responsible for meaning and consequence.

Adaptive Capacity and Organisational Coherence

Shared meaning supports:

learning,
trust,
coordination,
governance,
adaptation,
and resilience.

Without coherent meaning structures, organisations increasingly rely upon:

informal workarounds,
tribal knowledge,
local interpretation,
and human reconciliation effort.

Over time this weakens:

organisational memory,
learning throughput,
cross-functional coordination,
and adaptive capacity.

A coherent BCM and CDM, therefore, provide more than structural design.

Together, they help form part of the organisation’s Knowledge Base:

the shared structures,
language,
relationships,
and understanding that allow organisations to learn and adapt coherently over time.

👉 Shared meaning strengthens adaptive capacity.

Data Quality Management (DQM) and Organisational Trust

Data Quality Management (DQM) is not simply a technical cleansing activity.

It is the organisational discipline of maintaining trusted meaning over time.

Poor data quality is often treated as:

missing values,
duplicate records,
inconsistent definitions,
conflicting reports,
incomplete context,
outdated information,
technical defects,
broken integrations,
or unreliable analytics.

However, many DQM problems originate much earlier:

unclear definitions,
fragmented ownership,
inconsistent interpretation,
weak governance,
or conflicting organisational assumptions.

This is why strong DQM depends upon:

common language,
shared mental models,
clear stewardship,
semantic consistency,
and operational accountability.

A Common Data Model provides the structural foundation for this work.

It establishes:

agreed definitions,
relationship integrity,
ownership boundaries,
reference structures,
and organisational meaning.

DQM then becomes the operational practice of maintaining that meaning under real organisational conditions.

This includes:

validation,
stewardship,
feedback loops,
exception handling,
lifecycle governance,
and continuous operational learning.

Without shared meaning, data quality deteriorates rapidly.

Without trusted data, organisational trust weakens.

Without trust, coordination and adaptive learning become increasingly fragile.

👉 Data quality is ultimately a question of organisational meaning, trust, and stewardship.

🤿 For a deep dive

Explore further

This article connects to the broader framework:

Ethical Domain — how constraints shape decisions
Sensemaking Domain — how organisations interpret reality
Relational Domain — how trust and coordination emerge
Learning Domain — how knowledge is created and tested
Action Domain — how intent becomes capability

To understand more on Purpose detailed Subject Areas, visit the Deep Dive section.

📖See the Books