Become a Chief Data Officer: The Full Training Path

It covers the four sides of the CDO job: data governance, architecture, analytics strategy, and the internal politics of getting teams to use data. The lessons are grouped into blocks that run from building a data catalog to running a data quality program to presenting a data strategy to a board. It was written for the CDO role rather than adapted from a data analyst curriculum.

It's built for people heading toward the role: data managers, BI leads, analytics or data engineering heads who will soon own governance and strategy rather than delivery. A sitting CDO can also use it selectively, since the blocks work as standalone units. The level assessment tells you which ones matter for your situation.

No. There is no diploma, no state-recognized certification and no affiliation with a school or university. Reading is free and open; creating an account only saves your progress across sessions.

Start with the level assessment. It maps what you already know and points you to the blocks worth prioritizing, so you skip content you'd only be re-reading. From there, governance and the data catalog are the usual entry points because most other work depends on them.

A data strategy says what the business will get out of its data and in what order: which use cases, which investments, which arbitrages. Governance is the operating machinery that makes it possible: ownership, definitions, quality rules, access. Both are covered in the CDO path, and the second is what makes the first credible when you present it to a board.

Three things: interactive tools to model your own data roadmap, an action playbook with templates you can apply the same week, and a glossary covering the vocabulary that circulates in meetings, from data mesh to MDM. They exist so the reading turns into something you can put in front of colleagues.