Data Governance
Ownership, definitions, quality, lineage and access control: the practice that makes a data estate usable and defensible.
How data reaches a decision
What it is
Understanding Data Governance
Data governance is the operating model for data. Who owns each dataset, what each field means, what quality standard applies, where the data came from and who may see it. It is a practice supported by tooling rather than a tool, because a catalog with no accountable owners produces documentation nobody maintains.
Why it matters
It is the prerequisite for almost everything else. AI initiatives, regulatory reporting and self-service analytics all fail in the same place, which is data whose quality, meaning and access rules were never defined. Governance is what converts a data lake into a data asset.
Problems it addresses
- “Nobody owns the datasets our reporting depends on.”
- “We cannot trace where a number came from.”
- “We cannot answer a regulator asking how a figure was derived.”
- “Access to sensitive data is granted ad hoc and never reviewed.”
Capabilities
Ownership and stewardship model
A named accountable owner per domain, with stewards who actually maintain definitions.
Cataloguing and lineage
Discoverable datasets with traceable provenance from source to report.
Data quality management
Automated checks with alerting and a defined path to resolution, not periodic audit.
Master data management
Matching, merging and stewardship for the entities that appear everywhere: customer, product, supplier.
Access and classification
Sensitivity classification driving access policy, reviewed rather than assumed.
Policy and regulatory alignment
Retention, residency and subject-rights handling expressed as enforceable policy.
Use cases
AI readiness
Establishing the ownership, quality and access metadata that retrieval and model training depend on.
Regulatory reporting
Traceable lineage from source system to submitted figure.
Customer master data
One reconciled customer record across systems that each hold part of it.
Before you commit
Prerequisites, governance and risks
The questions that determine whether this will work in your environment, rather than in a demonstration.
What has to be true first
- Executive sponsorship, because governance without authority is documentation
- A catalog covering the estate before quality work begins
- Agreed domain boundaries
Governance
This is the governance capability. The practical test is whether the organization can answer, for any dataset in use: who owns it, what it means, how fresh it is, who can see it, and what happens when it is wrong.
Risks
- Governance theatre, meaning artefacts without accountability
- Process heavy enough that teams route around it
- Tooling bought before the operating model is agreed
Where Data Governance leads
Every connection below is recorded in the content itself, and each one says why it is here.
Capabilities
Technologies
Sectors
Reading
Explore solutions using Data Governance
Open the guided finder with this technology already selected, and see which capabilities apply to your goal, sector and environment — with the reasoning shown.
Start from a goal