The CDO's Cloud Stack

What a Chief Data Officer actually owns — the data-product operating model, the governance plane, quality and trust signals, and the lineage discipline that makes data load-bearing for the wider business.

BusinessCapabilityTechnology
Compass
  • Businesspersona, use case, outcome
  • Capabilitywhat the org needs to do
  • Technologythe technology choices
Guided journey · Step 1 of 4

Data Products & Ownership

Establish the data-product operating model. Datasets without owners decay; products with owners compound.

~ 8 weeks

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

Filter by type

Narrative intro

The CDO's hard problem isn't platform choice. Fabric, Databricks, and Snowflake are all viable substrates for an enterprise data estate. The hard problem is getting domain ownership, quality discipline, and lineage rigor to outlast any one platform decision. This map names those four pillars and the SKUs that support them.

Key takeaways

  • Data products with named owners outlast platform decisions
  • Purview is the governance plane that spans Fabric, Databricks, Snowflake
  • Trust signals belong at consumption — dataset by dataset, not platform-wide
  • Column-level lineage is the difference between defensible reporting and theatre

Programme shape

Estimated duration
26–52 weeks
Estimated FTE
1 FTE data platform lead + part-time governance, domain, and quality SMEs
Spend tier
major
Risk level
elevated

The CDO's hard problem is not platform choice (Fabric vs Databricks vs Snowflake) — it's getting domain ownership and quality discipline to outlast any individual platform investment.

Back to all maps