Applied Data · Module 8
Data as a product (making datasets usable, not just available)
A mature organisation treats important datasets like products.
Previously
Modelling basics (regression, classification, and evaluation)
Modelling is not magic.
This module
Data as a product (making datasets usable, not just available)
A mature organisation treats important datasets like products.
Next
Risk, ethics and strategic value
Data risk is broader than security.
Progress
Mark this module complete when you can explain it without rereading every paragraph.
Why this matters
If every request becomes a one-off extract, you are not serving data.
What you will be able to do
- 1 Explain data as a product (making datasets usable, not just available) in your own words and apply it to a realistic scenario.
- 2 Data is a product when it has an owner, an interface, and support expectations.
- 3 Check the assumption "Ownership is stable" and explain what changes if it is false.
- 4 Check the assumption "Interfaces are versioned" and explain what changes if it is false.
Before you begin
- Foundations-level vocabulary and concepts
- Confidence with basic diagrams and section terminology
Common ways people get this wrong
- Unowned datasets. Unowned datasets become stale and unsafe. Nobody fixes issues.
- Support as hero work. If support is ad hoc, the product becomes unreliable.
A mature organisation treats important datasets like products. They have owners, documentation, quality expectations, and support. This is how you reduce “shadow spreadsheets” and make reuse normal.
Worked example. The “can you send me the extract” culture
Worked example. The “can you send me the extract” culture
If every request becomes a one-off extract, you are not serving data. You are doing bespoke reporting at scale. A data product replaces that with a stable interface, clear meaning, and quality guarantees.
Verification. Write a data product page in five lines
Data product one-page template
This is the minimum viable contract for reusable datasets.
-
Name
State what the product is and what it is not.
-
Owner
Name accountable owner and support route.
-
Refresh
State update frequency and freshness target.
-
Quality
List mandatory checks and failure handling behaviour.
-
Access
Define who can use it and under what conditions.
Mental model
Data as a product
Data is a product when it has an owner, an interface, and support expectations.
-
1
Owner
-
2
Interface
-
3
Quality guarantees
-
4
Users
Assumptions to keep in mind
- Ownership is stable. If ownership changes without handover, data products decay.
- Interfaces are versioned. Versioning is how you change safely without breaking users.
Failure modes to notice
- Unowned datasets. Unowned datasets become stale and unsafe. Nobody fixes issues.
- Support as hero work. If support is ad hoc, the product becomes unreliable.
Check yourself
Quick check. Data as a product
0 of 5 opened
What does it mean to treat data as a product
Important datasets have owners, documentation, quality expectations, and support, like a service.
Why does 'send me the extract' culture hurt
It creates one off work, inconsistent definitions, and fragile decision making.
Name two things a data product page should include
Owner, refresh cadence, definition, quality checks, and access rules.
What is one benefit of stable interfaces for data
Teams can reuse data without repeated bespoke work and without silently changing meaning.
What is one risk if ownership is unclear
Problems do not get fixed, and trust in the dataset collapses.
Artefact and reflection
Artefact
A one-page decision note with assumption, evidence, and chosen action
Reflection
Where in your work would explain data as a product (making datasets usable, not just available) 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
Work through one scenario and justify the decision with evidence