Data ownership, stewardship and accountability across the org
"Everyone is responsible for data qualitydata qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.View full definition →" is one of the most destructive phrases in data management. When everyone is responsible, no one is.
Effective data governancedata governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.View full definition → requires clear, named accountability at three distinct levels, and most organizations confuse them, combine them, or skip them entirely.
The three data roles
Data Owner
The data owner is an executive or senior manager with business accountability for a data domain. They have budget authority, business accountability, and the organizational standing to enforce standards in their domain.
Key responsibilities:
- Approve data quality standards for their domain
- Resolve data conflicts that data stewards can't resolve
- Ensure domain data is fit for purpose for business use cases
- Sign off on data sharing agreements involving their domain data
The data owner is NOT a technical role. They are the business executive who stakes their reputation on data quality in their area. The VPVPA clear statement of the benefits your product delivers, the problems it solves and why customers should choose you over alternatives.View full definition → of Sales owns customer data. The CFO owns financial data. The CHRO owns people data.
Data StewardData StewardA business-side owner responsible for the quality, consistency and appropriate use of data in their domain.View full definition →
The data steward is the CDO's frontline agent in each business domain. They are typically a senior individual contributor with deep knowledge of both the business processes and the data that supports them.
Key responsibilities:
- Implement data quality standards set by data owners and the governance council
- Monitor data quality metrics daily or weekly
- Resolve data issues within their domain
- Document data definitions, lineage, and business rules
- Represent their domain in the Data Steward network
The data steward is the person in the business who actually knows where the data comes from, what it means, and why it sometimes looks wrong. They are invaluable. Losing a data steward is a significant organizational risk, their knowledge rarely exists in documentation.
Data Custodian
The data custodian is typically an IT or engineering role. They manage the technical infrastructure that stores and processes data, databases, pipelines, storage systems. They implement the access controls defined by governance but don't set the policies.
Data Governance Basics: DAMA-DMBOK, Ownership & Stewardship
Knowledge check
1. Why does the lesson call 'Everyone is responsible for data quality' one of the most destructive phrases in data management?
2. What best distinguishes a Data Owner from a Data Custodian?
3. Why is losing a Data Steward described as a significant organizational risk?
4. Select ALL statements that correctly describe the Data Steward role.
Select all the correct answers.
5. Select ALL responsibilities that correctly belong to the Data Owner.
Select all the correct answers.
Building a data ownership model in practice
Most organizations assign data ownership wrong. They either:
- Assign it to IT (wrong: IT owns infrastructure, not business data)
- Assign it to the CDO (wrong: the CDO can't own all data, they set governance standards)
- Leave it unassigned ("we'll figure it out later"), the most common mistake
The right approach: assign ownership at the domain level, mapped to the organizational structure.
Identify your domains: What are the fundamental data categories that mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → to your business model? For a retailer: Customer, Product, Transaction, Supplier, Inventory, Pricing. For a bank: Customer, Account, Transaction, Risk, Counterparty.
Map domains to business owners: Each domain maps to the executive who has business accountability for it. There should be no ambiguity. If two executives claim ownership of the same domain, that's an escalation to the CDO and ultimately the CEO.
Define ownership accountability metrics: Data ownership isn't honorary. Owners are accountable for Data quality scores in their domain, which feed into their performance metrics. In organizations that do this well, data quality is a KPIKPIKey Performance Indicator, a measurable value that shows how effectively you're achieving a specific objective, tracked over time against a target.View full definition → on the executive scorecard.
The data steward network as organizational infrastructure
The most effective CDOs build a Data Steward network before they build any technology. Here's why: technology can be replaced. Institutional data knowledge embedded in human relationships cannot.
A well-functioning Data Steward network:
- Has named stewards for every data domain
- Meets regularly (weekly async, monthly in person)
- Has a shared forum for resolving ambiguous data definitions
- Is recognized and rewarded, stewardship should be a visible part of the steward's role, not an invisible add-on to their day job
Organizations that skip the Data Steward network and go straight to technology consistently fail at data governance. The tools are empty without the human network that populates and maintains them.
What to do, from this lesson
These actions are compiled in the role's Playbook.
- Map data domains to accountable owners with quality KPIs on scorecards
- Build and reward a named Data Steward network before buying technology
Related articles
Recent articles from the blog that build on this lesson.
- DataHow JPMorgan Chase built data contracts across 50+ domainsJPMorgan Chase spent years grappling with fragmented data ownership across hundreds of business lines before systematically formalizing who owns what and on what terms. Their approach to data contracts offers a working model for CDOs who need accountability without organizational paralysis.
- DataHow Salesforce learned to make master data stickSalesforce spent years selling data quality to its customers while quietly struggling with fragmented customer and product records across its own acquisitions. The way the company addressed that internal contradiction holds practical lessons for any CDO trying to move MDM from a slide deck into operating reality.
- DataHub-and-spoke data teams: the model that sounds right and works badlyHub-and-spoke has become the default answer when CDOs are asked how to balance central governance with business-unit agility. The reality in most organisations is slower decisions, diluted accountability, and data professionals caught between two bosses with conflicting priorities.