Data governance often fails not because organizations lack policies or tools, but because nobody is quite sure who is supposed to do what. A data quality issue surfaces, and three teams point at each other. A new data product needs an owner, and the request stalls in email threads. A security exception is requested, and no one knows who actually has the authority to approve it.

---

A RACI matrix, Responsible, Accountable, Consulted, Informed, solves this by making decision rights and work assignments explicit. It clarifies who does what across key data governance activities, helping teams align, avoid gaps, and drive accountability.

It is not a bureaucratic exercise; it’s a tool for removing ambiguity at the exact moments when ambiguity is most costly: during an audit, a data quality incident, or a request for a new access permission. When roles are clear, escalation paths are clear, decisions get made faster, and accountability doesn’t evaporate the moment something goes wrong.

Data governance is not just a function. It’s a competitive advantage, and it starts with everyone knowing their role.

The pattern is deliberate: only Data Custodian and Data Engineer/Platform sit in IT. Everything else, what the data means, who gets access, why it matters, is a business decision. IT’s role is to build and secure the technical environment that makes those decisions executable; it does not make the decisions itself.

Keep it simple
Start with what matters most. Don’t try to RACI every possible activity on day one. Review and adjust the matrix as your governance maturity grows. Don’t let the organisation become heavy-footed. Start small and stay nimble. Build with the granularity in the organisation that provides agility and value, not the granularity that merely looks complete on a slide.

Align roles, not just titles
Titles vary widely between organisations; a “Data Steward” in one company might do the job of a “Data Owner” in another. Focus on the underlying responsibilities and decision rights, not the label on the org chart.

The Key Roles in Modern Data Governance

Before assigning responsibilities, it helps to define who the players actually are — and, critically, which side of the organization they should sit on. One of the most common governance failures is putting a role in the wrong home: an “owner” who is actually an IT system administrator, or a steward who has no real ties to the business domain they’re supposed to represent. Getting this placement right matters as much as defining the activity itself.

Don’t let IT inherit business decisions by default. When a Data Owner role is left vacant, IT often ends up making de facto decisions about access, quality, and definitions, simply because it’s the team closest to the systems. This is a governance anti-pattern: it puts business judgment calls in the hands of people who weren’t meant to make them. If a business-side Owner isn’t named, the gap should be treated as an open risk, not quietly absorbed by IT.

CDAO / Head of Data, Business (Executive)

Defines strategy, vision, funding, and enterprise priorities. This is a senior business leadership role — even when the person has a technical background, the mandate is enterprise strategy and investment, not systems operations.

Data Governance Lead, Business (Governance Office)

Designs and operates the governance framework, drives adoption, and ensures alignment across business and technical teams. This role typically sits in a central data/governance office rather than inside IT, though it works in close partnership with IT to implement what it designs.

Data Owner, Business

Accountable for specific data domains. Sets direction, priorities, and quality targets, and approves the policies that apply to their domain. Ownership must be tied to the business, not to IT — a Data Owner is a domain expert (e.g., Head of Sales, Head of Finance) who understands what the data means and how it should be used, not a system administrator.

Data Steward, Business (embedded in domains)

Manages metadata, monitors data quality day to day, coordinates remediation actions, and promotes standards across teams. Stewards are usually business-side specialists embedded within a domain (finance, HR, sales, etc.), acting as the operational link between the Data Owner and the rest of the organization.

Data Custodian (IT), IT

Responsible for infrastructure, storage, security controls, and system reliability. This is squarely an IT role: custodians make sure the technical environment can actually support the policies that business-side owners and stewards define, but they do not set those policies themselves.

Data User, Business

Uses data to make decisions and provides feedback and insights back into the governance process. Every employee who touches a report, dashboard, or dataset plays this role, regardless of department.

Do read more

Related reading: Master Data Management – The Golden Hour