Loading content
Data governance defines policies, roles, and processes to manage data quality, access, and compliance across an organization. It establishes clear ownership, classification, and controls across the data lifecycle. Implementation requires organizational alignment, role definitions, and technical enablers to ensure trustworthy and value-driven use of data.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Data governance is the organization-wide operating model for data quality, access, responsibilities, and compliance across the data lifecycle.
The discipline emerged from a practical problem: data existed in many systems, departments, and roles, but it was not governed consistently. As regulation increased and data estates became more fragmented, organizations needed formal principles, roles, and control points to manage quality, traceability, access, and protection across the data lifecycle.
Think of data governance as a control layer above the data landscape. Rules define what data may be used for. Roles such as owner and steward make and monitor decisions. Metadata makes assets visible, lineage shows where data came from and how it moved, quality rules test reliability, and access plus protection controls limit sensitive use. This turns stewardship into something auditable rather than informal.
A named role carries business accountability for data and decides on rules and exceptions.
Measures, checks, and improvement work ensure that data is fit for its intended use.
Descriptions of data objects, definitions, and responsibilities make assets discoverable and understandable.
The origin, transformations, and sharing of data remain traceable across systems and processes.
Permissions and approvals determine who may view, change, or share data.
Personal and sensitive data are protected through organizational, technical, and legal measures.
Data governance matters when many systems share the same data, when regulatory obligations must be met, or when business teams need trusted definitions and clear accountability. It reduces shadow copies, inconsistent metrics, and unclear approvals. The trade-off is extra coordination, maintenance, and control effort; overly rigid rules can slow teams down.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.