Data culture & organization
Build data literacy, structure the data function, and drive data maturity
Data platforms do not fail because of technology. They fail because the organisation around them was never designed to use them. Bloc 7 fixes that. This is where you stop treating data as an IT project and start treating it as an operating capability that lives inside every team, every decision, every career path.
Module 7.1 puts you in front of the real question: how mature is your data organisation, and what comes next. You will run a proper maturity assessment and then sequence the moves that matter, because trying to do everything at once is how CDOs burn credibility in the first ninety days. Design comes before deployment. You will learn to shape an organisational model that matches your ambition instead of copying a diagram from a company that looks nothing like yours.
Module 7.2 is about scale. Data literacy is not a workshop you run once and forget. It is the capability that decides whether your analytics investment compounds or evaporates. You will learn to build that literacy across the entire organisation, not just the analytics bench. Then we get specific on structure: embedded analytics that sit close to the business, a Data Council that gives your function real governance and real authority, and a career ladder that keeps your best data people from walking out the door.
This block is written for leaders who own the outcome. By the end you will know how to read your organisation honestly, design the model it actually needs, and build the human capability that makes the whole thing move. Culture is not a soft topic here. It is the difference between a data strategy that gets quoted in board decks and one that gets used.
What you'll master
- Assess your data organisation's maturity with a framework that survives scrutiny
- Sequence organisational moves so early wins fund the harder changes
- Design a data operating model that fits your ambition instead of a generic template
- Build data literacy across the whole organisation, not just the analytics team
- Deploy embedded analytics that sit close to the business and its decisions
- Stand up a Data Council with real governance authority and clear mandate
- Create a career ladder that retains and grows your best data talent
Modules
Assess the organization's data maturity and sequence its organizational design
Build data culture and structure analytics teams at scale
Shows how to shift an organization toward data-driven decisions, embed data in key rituals, and overcome resistance and internal politics.
Shows how to map required skills, hire the right people, build career paths, and structure teams to keep talent from leaving.
Frequently asked questions
What does the Data culture & organization block cover?
It covers how to organise the human side of data: maturity assessment, operating model design, data literacy at scale, cultural change, and hiring and retaining data teams. It sits in the CDO Track and spans 4 modules and 12 lessons. The premise is that data platforms fail because the organisation around them was never designed to use them, not because of technology.
Who is this block for?
Leaders who own the outcome of a data function: CDOs, data directors, heads of analytics, and executives who have to make a data strategy work across teams they do not directly manage. It assumes you are deciding on structure, governance and headcount, not writing pipelines.
How is this different from a block on data architecture or platforms?
Data culture & organization deals with people, structure and decision rituals; architecture blocks deal with pipelines, storage and tooling. Here you design the operating model, the Data Council, the literacy program and the career ladder. The technology choice is treated as downstream of the organisational choice.
Which operating model should I choose: centralized, federated or hub-and-spoke?
There is no default answer, which is exactly why one lesson is dedicated to comparing centralized, federated and hub-and-spoke models. The choice depends on your maturity level, your ambition and how decisions already circulate in the company. The block teaches you to shape a model that matches your context instead of copying a diagram from a company that looks nothing like yours.
Where do I start if my data team exists but nobody uses its work?
Start with the maturity assessment in module 7.1, then look at decision rituals in module 7.3. An unused data team is usually a symptom of data being absent from the moments where decisions are actually made, and of literacy gaps outside the analytics bench. Sequencing matters: early wins fund the harder organisational changes.
What exactly does the block say about a Data Council and the career ladder?
Both are covered in module 7.2, in the lesson on embedded analytics, Data Council and data career ladder. The Data Council is presented as a governance body that needs a real mandate and real authority, not a monthly status meeting. The career ladder is treated as a retention tool: without visible progression, your best data people leave.