The management question is no longer whether a CDO can produce trusted data; it is whether the organisation has assigned the right decision rights for data use. For senior leaders, that means the CDO role only works when business owners, risk leaders, and product owners share accountability for where data is created, who can change it, and which decisions it is allowed to influence. If those boundaries are unclear, the CDO becomes a catch-all function for problems that are actually structural.
That creates an important trade-off. Centralising standards, definitions, and governance can reduce duplication and improve comparability, but it can also slow teams if every exception requires escalation. Decentralising analytics and data products can improve speed and relevance, but only if there is a clear control model for quality, lineage, privacy, and approved use. Leaders should ask where standardisation is essential, and where local autonomy is a better investment.
What “good” should now mean is measurable operating change, not just technical delivery. Useful questions include: are fewer decisions delayed by disputed numbers; are critical metrics owned by named business leaders; are data issues resolved at the point of use; and are data investments tied to process outcomes rather than platform activity? If the metrics stop at catalog completion or dashboard counts, the organisation may be funding visibility without accountability.
The practical implication for CIOs and boards is to treat the CDO as part of a broader governance system. That means defining sponsorship, escalation paths, and funding for stewardship, not assuming the role can compensate for weak business ownership. It also means testing whether data and AI programmes have explicit adoption targets, control points, and risk thresholds before scale. The next question is not “Is the CDO strong?” but “Is the operating model built to let the CDO succeed?”
The CDO Role Has Changed: Why Data Leaders Must Drive Decisions, Trust, And Change
For years, we’ve described the chief data officer (CDO) as the executive responsible for data, analytics, and insights. That definition was useful — and, for a time, accurate. It’s no longer sufficient. Our newly updated Chief Data Officer Role Profile reflects a quiet but consequential shift underway in leading organizations: today’s CDO isn’t just responsible for producing cohesive, trusted data, they’re accountable for assuring the data actually changes decisions, behaviors, and outcomes. And not just that – they have to do it while navigating an ever-shifting wave of communications processes/channels, and volatile technology change. That’s a very different job.From Data Delivery to Governance & Decision Enablement
In earlier versions of the role, the CDO was often framed as a kind of chief insights officer — building analytics teams, delivering dashboards, and promoting data literacy. In others, the CDO was basically the head of data engineering. Many CDOs still do that work, and it still matters. But organizations have learned (sometimes painfully) that insights, pipelines, and schemas alone don’t move the needle. What does?- Clear ownership
- Trusted data
- Confident decision-making
- Fewer meetings spent debating whose numbers are “right”
Why Change Management Is Now Core to the CDO Role
One of the most important updates in the new role profile is explicit: change management, stakeholder engagement, and value storytelling are now core CDO competencies. This isn’t a soft-skills upgrade. It’s a response to reality. Most data failures today aren’t technical. They’re human:- Leaders hesitate to act on data they don’t trust
- Teams stall when metrics conflict
- Employees avoid questions when data exposes risk or uncertainty
The Rise of Internal Data Experience
Another subtle but important shift: the role now emphasizes internal data experience, not just data literacy or digital fluency. Data experience asks different questions:- LOCATE: Can people find what they need?
- LEVERAGE: Do they know how to use it?
- TRUST: Do they trust it enough to act without hedging?
AI Raised the Stakes
AI has accelerated this evolution. As organizations embed AI into decision-making, the cost of poor data, weak governance, and cultural fear compounds quickly. Models don’t just scale insights — they scale uncertainty, bias, and mistrust when those conditions exist. That’s why the updated role integrates risk management, harm reduction, and human‑in‑the‑loop decision systems into the CDO’s remit. Someone must be accountable for ensuring that data — and the decisions it fuels — are not just sophisticated, but responsible and trusted. That “someone” is increasingly the CDO.What This Means for Executives and Boards
If you’re hiring, evaluating, or supporting a CDO today, the questions to ask have changed:- Can this leader drive adoption, not just delivery?
- Can they influence executives and change behaviors?
- Can they turn data into confidence — not just insight?
Now What?
If your expectations of the CDO haven’t changed, but the organization’s data, AI, and risk landscape has — it’s time to recalibrate. Our updated Chief Data Officer Role Profile outlines what modern CDOs are actually accountable for today: from decision enablement and change leadership to trust, adoption, and AI readiness. Check out the role profile below and reach out via an inquiry with me today [email protected] to learn more about how these leaders can help organizations locate, leverage, and trust information within your organization.The CDO Role Has Changed — And So Has What “Good” Looks Like
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.

