Data, standards, and interoperability

Why this matters

Imagine two teams both talk about “customer”, where one means “the bill payer” and another means “the person who contacted us”, both definitions can be valid, but the dashboard becomes dangerous.

What you will be able to do

1 Explain data, standards, and interoperability in your own words and apply it to a realistic scenario.
2 Digital systems improve when processes create reliable data and data changes decisions.
3 Check the assumption "Processes are observable" and explain what changes if it is false.
4 Check the assumption "Definitions are shared" and explain what changes if it is false.

Before you begin

No previous technical background required
Read the section explanation before using tools

Common ways people get this wrong

Spreadsheet islands. Local tracking breaks global visibility. The system becomes a collection of private truths.
Data without action. If data never changes decisions, it becomes noise.

Main idea at a glance

Standards and data flow

Shared models make data reusable.

Stage 1

Source systems

CRM, billing, metering, customer contact, field systems. Each has its own schema, its own definition of key entities, and its own update cadence. The challenge is not getting data out. It is getting consistent data out.

I have seen source systems where the same field means different things depending on which team last updated the documentation. That is not a technology problem. That is an ownership problem.

The common data model is the critical layer. Without it, every downstream service interprets data differently.

A dataset is only useful when people trust it. A schema tells everyone what the data means. A data model keeps systems aligned.

An API is the bridge. interoperability is the goal.

Worked example. When two systems disagree on a definition and nobody notices

Imagine two teams both talk about “customer”, where one means “the bill payer” and another means “the person who contacted us”, both definitions can be valid, but the dashboard becomes dangerous when it quietly mixes them and leaders act on the combined number.

This is why I’m strict about schemas and data models. The goal is not bureaucracy. The goal is that two systems can exchange data without silently changing meaning.

Common mistakes in standards and interoperability

Common mistake

Treating data as only a technical asset

Reality: Data is a shared organisational promise. If finance and operations define a term differently, dashboards will be wrong.

Common mistake

Using the same word for different concepts

Reality: When two teams both say "customer" but mean different things, you spend meetings arguing about numbers instead of fixing problems.

Common mistake

Changing schemas without versioning

Reality: Break downstream consumers once and trust erodes. Version your contracts and communicate changes.

Common mistake

Building point-to-point integrations everywhere

Reality: It is quicker today, but you end up with a fragile web that nobody can maintain or understand.

Verification. Can you prove meaning survived the journey

Meaning-survival verification

Use this flow to prove data meaning was not corrupted during exchange.

Choose one critical field

Select a field such as status, completion date, or meter read type.
Define semantics and authority

Write valid values, business meaning, and who can modify the field.
Compare across at least two systems

Check both format and semantic equivalence, not only field names.
Resolve mismatches with source-of-truth rule

Document the canonical source and why that decision is operationally defensible.

Reflection prompt

What is one term your organisation argues about because it is fuzzy. If you had to define it in a way a computer could enforce, what would you write.

Mental model

Process to data to decision

Digital systems improve when processes create reliable data and data changes decisions.

1

Process
2

Data
3

Insight
4

Decision

Assumptions to keep in mind

Processes are observable. If work is invisible, you cannot improve it. Visibility is the first upgrade.
Definitions are shared. If teams disagree on meaning, you cannot coordinate outcomes.

Failure modes to notice

Spreadsheet islands. Local tracking breaks global visibility. The system becomes a collection of private truths.
Data without action. If data never changes decisions, it becomes noise.

Key terms

dataset: structured collection of related data
schema: structure and meaning of fields
data model: shared representation of how data is organised
API: defined way for systems to request and exchange data
interoperability: the ability for different systems to exchange and use data consistently

Check yourself

Quick check. Data and standards

0 of 7 opened

Why does a schema matter

It defines what data means so systems interpret it consistently.

What does interoperability enable

Different systems can exchange and use data reliably.

What is a data model used for

To align how data is structured across systems.

Why are APIs important

They provide controlled access to data and services.

Scenario. Two systems both say “customer”, but mean different things. What is the fix

Write the definitions, split the concepts if needed, and enforce them through schemas and contracts. Shared words without shared meaning cause silent errors.

What happens without shared standards

Every integration becomes a custom translation.

Why does data trust matter

Untrusted data leads to poor decisions and wasted effort.

Artefact and reflection

Artefact

A short module note with one key definition and one practical example

Reflection

Where in your work would explain data, standards, and interoperability in your own words and apply it to a realistic scenario. change a decision, and what evidence would make you trust that change?

Optional practice

Map raw data into structured fields and see how meaning is preserved.

Components of a digitalised system