Digital Strategy and Enterprise Scale · Module 2
Data sharing, models, and standards
At scale, digitalisation depends on shared meaning.
Previously
Strategy and target state architecture
A target state keeps strategy concrete.
This module
Data sharing, models, and standards
At scale, digitalisation depends on shared meaning.
Next
Platforms, ecosystems, and governance
A platform only works when governance is clear.
Progress
Mark this module complete when you can explain it without rereading every paragraph.
Why this matters
A common failure mode in ecosystems is “we agreed the model”, then nobody funds stewardship.
What you will be able to do
- 1 Explain data sharing, models, and standards in your own words and apply it to a realistic scenario.
- 2 Sharing is safe when meaning is shared and controls are enforced at boundaries.
- 3 Check the assumption "Standards are enforced" and explain what changes if it is false.
- 4 Check the assumption "Auditability exists" and explain what changes if it is false.
Before you begin
- Comfort with earlier modules in this track
- Ability to explain trade-offs and risks without jargon
Common ways people get this wrong
- Semantic fragmentation. If meaning fragments, sharing becomes unreliable and expensive.
- Untracked access. If access is not tracked, misuse becomes invisible.
Main idea at a glance
Shared data model
Many systems, one shared meaning.
Stage 1
Utility source systems
Metering, billing, network management, customer records, and field operations systems. Each produces data that other parties in the ecosystem need. The challenge is making it trustworthy enough for others to build services on.
Trust is built through enforced identifiers, version control, and stewardship. Remove any one and the chain breaks.
At scale, digitalisation depends on shared meaning. A canonical model reduces translation work. A data sharing agreement keeps trust intact.
Interoperability is not just a technical issue. It is legal, operational, and cultural. You need incentives for everyone to keep the model accurate over time.
Worked example. Shared data without shared incentives
Worked example. Shared data without shared incentives
A common failure mode in ecosystems is “we agreed the model”, then nobody funds stewardship. Publishers ship changes when it suits them, consumers build workarounds, and the canonical model becomes fiction. Interoperability dies slowly, then all at once.
Common mistakes in standards at scale
Standards-at-scale anti-patterns
Standards fail when governance and incentives are neglected.
-
Assuming technical agreement is sufficient
Incentives and stewardship sustain standards over time.
-
Missing version governance
Uncoordinated releases create downstream breakage and distrust.
-
Treating agreements as paperwork only
Data-sharing agreements must be operationally enforced.
-
Underestimating identity and authorisation
Trust collapses without strong access controls and accountability.
Verification. “Can we share data safely” checklist
Safe data sharing checklist
Run these checks before scaling any shared dataset.
-
Purpose and lawful basis
Define clear purpose, lawful basis, and retention policy.
-
Named stewardship and change control
Assign stewards and formalise controlled model changes.
-
Access control and audit trails
Capture who accessed what data, when, and for what reason.
-
Misuse monitoring
Detect abnormal volume, access patterns, and policy violations.
Reflection prompt
Which is harder in your world, agreeing a standard, or keeping it healthy for five years. What would you put in place to make it survive leadership changes.
Mental model
Sharing boundary
Sharing is safe when meaning is shared and controls are enforced at boundaries.
-
1
Organisation A
-
2
Standard
-
3
Organisation B
-
4
Audit
Assumptions to keep in mind
- Standards are enforced. A standard helps only if systems follow it consistently.
- Auditability exists. Auditability is what makes sharing defensible under scrutiny.
Failure modes to notice
- Semantic fragmentation. If meaning fragments, sharing becomes unreliable and expensive.
- Untracked access. If access is not tracked, misuse becomes invisible.
Key terms
- canonical model
- A common structure that keeps core data definitions consistent.
- data sharing agreement
- A documented agreement that covers access, usage, and accountability.
Check yourself
Quick check. Data sharing and standards
0 of 6 opened
Why use a canonical model
It keeps core definitions consistent and reduces translation work.
What makes interoperability hard
It spans technical, legal, and operational choices, not just formats.
Why are data sharing agreements important
They set access rules, usage constraints, and accountability.
What is the risk of unmanaged model changes
Downstream systems drift, incidents rise, and trust erodes.
Why do shared IDs matter
They prevent mismatches across systems and reduce reconciliation work.
Who should own a shared field
A named steward with authority and a clear change control path.
Artefact and reflection
Artefact
A concise design or governance brief that can be reviewed by a team
Reflection
Where in your work would explain data sharing, models, and standards 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 a source schema into a canonical model and check coverage.