Data ownership strategy
On this page 9 topics
Overview
Topics
- Federated ownership
- governance
- data contracts
Learn first
3.5 h of practice (estimate)
Learning outcomes
- Design federated data ownership with clear domain owners for operational and analytical data.
- Define data contracts (schema, semantics, quality, SLAs) between producing and consuming teams.
- Establish governance for sensitive data that does not centralize all decisions.
- Evaluate data mesh ideas against the organization's maturity.
Lessons
Lab and exercises
Lab
SRA-004-LAB1 · Ownership map
Outcomes: 1–4 · Time: ~2 h
- Inventory the major operational and analytical data sets in Commerce 2030 with current holders and consumers.
- Assign one owner per data set, mark authoritative sources and copies.
- Write data contracts for the five most consumed data sets: schema, semantics, quality rules, SLAs, versioning policy.
- Define a classification and governance model for sensitive data with decision rights.
- Assess data mesh readiness and choose which ideas to adopt now.
Acceptance: every data set has one owner; contracts include quality SLAs.
Exercises (case-based; six exercises)
| ID | Outcome | Task |
|---|---|---|
| SRA-004-EX01 | 1 | Given a map where five teams hold copies of product data, assign one owner and label authoritative source versus copies. |
| SRA-004-EX02 | 1 | Decide ownership for analytical data derived from orders: who owns the warehouse model, and who owns the revenue metric? |
| SRA-004-EX03 | 2 | Write a data contract for SellerPayoutIssued: schema, semantics, quality rule, freshness, versioning. |
| SRA-004-EX04 | 2 | A producer plans a breaking change. Write the notice process and automated checks that prevent surprise. |
| SRA-004-EX05 | 3 | Design a governance model for personal and payment data that does not route every request through one team. |
| SRA-004-EX06 | 4 | Score the organization's readiness for data mesh and recommend which ideas to adopt in year one. |
Show solutions
- EX01 The domain that creates and changes the data owns it (for example Catalog owns product data); others hold labeled copies refreshed from the source with a stated lag.
- EX02 The Orders team owns the source events; the analytics or Finance team owns the warehouse model; Finance owns the revenue metric definition, with a contract reconciling it with Orders.
- EX03 Include: payout id, seller id, gross, fees, net, currency, issued time; semantics of each amount; rule that net equals gross minus fees; freshness SLA (agree with consumers); additive changes minor, removals major with notice.
- EX04 Notice period, version both old and new for an overlap, compatibility check in the producer pipeline, consumer-driven tests, and a named contact for each consumer.
- EX05 Classify once, apply default controls by class, let owners approve within policy, automate masking and access logging, and escalate only exceptions. Measure time to access and incidents.
- EX06 Score domain team stability, platform maturity, catalog, and consumer demand. Typical year one: ownership, contracts, and catalog first; self-serve platform and wider mesh later.
Outcome 3 is also covered by the governance step in the lab; outcome 4 by the lab readiness assessment and quiz.
Workplace evidence: a data contract or ownership agreement you established between teams.
Quiz
Outcomes: O1 federated ownership · O2 data contracts · O3 federated governance · O4 data mesh evaluation.
A self-check for you: nothing is graded, saved or sent anywhere. Choose an answer, then check it. You can try again as often as you like.
Practical part
Six case exercises SRA-004-EX01 to EX06 plus the lab, reviewed as an ownership map and contract set. Pass: at least five of six exercises correct, quiz at least 8/10, and a map where every data set has one owner and every contract includes quality SLAs.
Common mistakes
A central data team owning everything; contracts without semantics.
Assessment
Contract and ownership review.
Workplace evidence
A data contract or ownership agreement you established between teams.
Career relevance
Data architecture and governance (ARC-023, ARC-030).