vault backup: 2026-07-23 07:56:59
This commit is contained in:
@@ -0,0 +1,104 @@
|
||||
**MD file:** `Data Owner.md`
|
||||
**Estimated reading time:** 8–10 minutes
|
||||
|
||||
# Data Owner
|
||||
|
||||
## Definition
|
||||
|
||||
A **Data Owner** is the person or business role accountable for a data domain, dataset, or important business definition.
|
||||
|
||||
The Data Owner has authority over meaning, acceptable use, access, quality expectations, retention, and important business rules.
|
||||
|
||||
## Simple Mental Model
|
||||
|
||||
> **The Data Owner decides what the data means and what should happen with it.**
|
||||
|
||||
IT may host the system. Data Engineering may build the pipeline. An analyst may build the dashboard. None of them automatically owns the business meaning.
|
||||
|
||||
## How It Works
|
||||
|
||||
Example:
|
||||
|
||||
```text
|
||||
Employee Data
|
||||
Business owner: HR
|
||||
IT: operates systems
|
||||
Data team: pipelines and reporting
|
||||
```
|
||||
|
||||
Ownership is accountability, not technical administration.
|
||||
|
||||
## Example
|
||||
|
||||
Marketing and Product disagree on `Active User`.
|
||||
|
||||
The data team should not silently choose the definition because it owns Power BI.
|
||||
|
||||
A Data Owner should approve the business definition, which can then flow into [[Business Glossary]] and [[Semantic Layer]].
|
||||
|
||||
## How It Fits Into the Bigger Picture
|
||||
|
||||
```text
|
||||
[[Data Governance]]
|
||||
↓
|
||||
[[Data Owner]]
|
||||
Accountability / decision authority
|
||||
↓
|
||||
[[Data Steward]]
|
||||
Day-to-day quality and maintenance
|
||||
```
|
||||
|
||||
## My Company / Real-World Context
|
||||
|
||||
Potential ownership could look like:
|
||||
|
||||
- Advertising Revenue → Finance / Advertising business leader
|
||||
- Employee Data → HR
|
||||
- Content Metadata → Programming / Content
|
||||
- Streaming Audience KPI → agreed business owner
|
||||
|
||||
Your Data Governance team can facilitate and implement without owning every business concept.
|
||||
|
||||
## CTO Perspective
|
||||
|
||||
A common failure is confusing system ownership with data ownership.
|
||||
|
||||
A useful question is:
|
||||
|
||||
> **Who has the authority to make the final business decision about this data?**
|
||||
|
||||
If nobody can answer, ownership is unclear.
|
||||
|
||||
### Questions to Ask
|
||||
|
||||
- Who is accountable for this data?
|
||||
- Who approves its business definition?
|
||||
- Who approves access?
|
||||
- Who establishes acceptable quality?
|
||||
- Is the owner a business role or merely the person who built the system?
|
||||
- Is ownership documented?
|
||||
|
||||
## Meeting Scenario
|
||||
|
||||
**Situation:** Marketing and Product ask your data team to decide the definition of Active User.
|
||||
|
||||
**Possible response:**
|
||||
|
||||
> "Data can quantify the options and explain the consequences, but this is ultimately a business-definition decision. We need an accountable owner who can approve the definition, after which we'll implement it consistently."
|
||||
|
||||
## Key Takeaways
|
||||
|
||||
- A Data Owner is accountable for business meaning and appropriate management.
|
||||
- Ownership is not the same as building or hosting the system.
|
||||
- Business departments should normally own business meaning.
|
||||
- [[Data Governance]] should make ownership explicit.
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Data Steward]]
|
||||
- [[Data Governance]]
|
||||
- [[Business Glossary]]
|
||||
- [[Metadata]]
|
||||
- [[Data Catalog]]
|
||||
- [[Semantic Layer]]
|
||||
- [[KPI]]
|
||||
Reference in New Issue
Block a user