Data Governance Capability Map

The capability stack that turns a data catalogue into governed data products — enterprise data governance, lineage as a discipline, quality and trust signals, and the data-product operating model.

ForCDO · Head of Data

Compass

Businesspersona, use case, outcome
Capabilitywhat the org needs to do
Technologythe technology choices

Guided journey · Step 1 of 4

Enterprise Data Governance

Stand up the catalogue and classification capability via Purview Data Governance. The federation layer across Fabric, Databricks, Snowflake.

~ 12 weeks

Search any SKU, capability, risk, or source on this map.

Filter by type

All maps

Narrative intro

Data governance as a capability has four layers — catalogue, lineage, quality, products — and each takes about two quarters to land. This map names them and the SKUs that anchor each. Purview Data Governance is the cross-platform federation; the capability is the discipline that turns the platform into a governed estate.

Key takeaways

Governance capability has four layers — catalogue, lineage, quality, products
Purview Data Governance is the cross-platform federation across Fabric, Databricks, Snowflake
Column-level lineage is the audit-defensibility lever — nothing replaces it
Data products with named owners is the maturity threshold

Programme shape

Estimated duration: 24–48 weeks
Estimated FTE: 1 FTE governance lead + part-time domain owners and quality SMEs
Spend tier: significant
Risk level: elevated

Governance maturity is a multi-year journey. The capability is built in layers — catalogue first, lineage next, quality discipline third, data products last — and each layer takes ~2 quarters to land.

Back to all maps