Leadership
By: Caroline Carruthers, Co-founder and Chief Executive of Carruthers and Jackson
As Told To: Pritam Bordoloi, Senior Reporter, CDO Magazine
Updated 11:45 AM EDT, July 17, 2026

For years, organizations have debated what makes a successful Chief Data Officer (CDO). Is it deep governance expertise? A strong analytics background? Business acumen? Technology leadership? Or increasingly, AI experience?
The answer is both simpler and more complicated than most people expect. When I co-authored The Chief Data Officer’s Playbook in 2017, we identified four common routes into the role: technology, governance, analytics, and data science.
At the time, AI was not yet a boardroom obsession, so it was not considered a distinct pathway. Nearly a decade later, the landscape has evolved significantly, and AI leaders have emerged as a new and highly visible category of data executive.
After working with hundreds of aspiring and practicing CDOs through CDO Summer School and across industry, government, and academia, I have learned that career paths into the role are far more varied than most frameworks suggest.
The five archetypes outlined below are useful because they help explain where many CDOs come from, but they do not tell the whole story.
The most effective data leaders are rarely defined by their original discipline. They are defined by their ability to solve problems, bridge worlds, and lead change.
The governance-first CDO is perhaps the most traditional archetype. These leaders often begin their careers in data management, data quality, compliance, records management, or governance functions.
Their expertise lies in creating structure, accountability, and trust around data assets.
Organizations typically bring in these leaders when data has become a risk. Perhaps regulatory requirements are increasing, or ownership is unclear, or critical data is inconsistent across systems. In these situations, governance becomes the priority.
The governance-first CDO understands that before organizations can generate value from data, they need confidence in it.
What makes these leaders successful is their ability to establish clarity around questions such as:
The challenge for governance-oriented leaders is that few executives become excited about governance itself. Boards rarely celebrate metadata standards or applaud stewardship models. They care about business outcomes.
Governance professionals can become so focused on policies and controls that they forget governance is not the end goal. So it has to be linked to business value.
That means governance-first CDOs must learn how to connect foundational work to tangible business value. The best among them understand that governance is not the destination. It is the enabler.
The second archetype emerges from analytics, business intelligence, and data science.
These leaders often began their careers building reports, conducting analysis, developing models, or extracting insights from data. Their instinct is to focus on outcomes, opportunities, and value creation.
They tend to be naturally curious and highly analytical. They are comfortable asking questions, challenging assumptions, and uncovering patterns that others miss.
Organizations often hire these CDOs when they want to accelerate decision-making, improve customer experiences, drive operational efficiency, or unlock new revenue streams.
Their strength lies in demonstrating what data can achieve.
However, analytics-first leaders sometimes encounter an unexpected challenge. In their enthusiasm to create value, they may underestimate the importance of foundations. They can become excited by insights and innovation while overlooking the importance of things like data quality, ownership, and organizational change.
A sophisticated model built on poor-quality data remains a poor solution.
The most successful analytics-oriented CDOs eventually learn that insight and governance are not competing priorities but complementary capabilities. Sustainable value requires both.
Technology-first CDOs often come from architecture, engineering, CIO organizations, or broader technology leadership roles.
These leaders understand platforms, systems, integration, and infrastructure. They know how information moves through an organization and where technical bottlenecks exist.
Many organizations naturally assume that data challenges are technology challenges. Sometimes they are, but often they are not.
One of the most important lessons I learned during my career came when I moved from technology leadership into a dedicated data role.
Technology leaders sometimes assume better platforms will solve data problems. I realized that better technology alone did not automatically solve the underlying problem.
You could deploy a new CRM system, replace an ERP platform, create faster dashboards, or build sophisticated reporting environments. But if nobody understands who owns the data, how it is governed, whether it is trustworthy, or how it will be used, the organization has simply created a shinier version of the same problem.
Technology alone doesn’t create trust, accountability, or business value. Technology-first CDOs succeed when they complement their technical expertise with strong business partnerships.
Technology enables capability, but data leadership creates value. The strongest technology-first CDOs bridge both worlds, translating technical excellence into measurable business outcomes.
This is one of the most fascinating archetypes because it rarely follows a traditional path. These leaders come from operational functions, marketing, customer experience, finance, supply chain, healthcare, public services, or other business disciplines.
They are often what I call “accidental data leaders” who did not start their careers intending to become CDOs. Instead, they encountered recurring business problems and became frustrated by their inability to solve them.
Eventually they realized that data sat at the root of many of those challenges, and that realization changes everything.
The business leader who repeatedly encounters inconsistent reporting starts asking questions about data quality. The operations executive struggling with inefficiencies begins investigating underlying data issues. Similarly, the marketing leader seeking better customer outcomes starts exploring analytics and insight generation.
In many cases, their journey into data leadership begins with a simple desire to solve problems more effectively. What makes these leaders particularly powerful is their ability to speak the language of the business.
They understand operational realities, stakeholder concerns, and what success looks like outside the data function.
As a result, they often excel at gaining executive buy-in and translating technical concepts into business outcomes.
However, business and operations leaders tend to understand the organization well, but can underestimate the complexity of leading an enterprise-wide data agenda across multiple functions.
When they combine their business perspective with strong data leadership disciplines, they become some of the most effective CDOs an organization can have.
The newest archetype is the AI-first CDO. These leaders often emerge from machine learning, AI engineering, advanced analytics, or innovation functions.
As AI becomes a strategic priority, organizations increasingly seek leaders who understand how to harness these capabilities responsibly and effectively.
Yet there is a danger in viewing AI as something fundamentally separate from data leadership. AI is extraordinarily powerful, but it remains a tool.
AI leaders often face the same temptation as technology leaders. There is a risk they become captivated by the technology rather than starting with the business problem.
The best AI leaders ask what they’re trying to solve before deciding whether AI is the right answer.
Many begin with the question, “How can we use AI?” A far better question is, “What problem are we trying to solve?”
The best AI-first CDOs start there.
Their success comes not from chasing the latest trend, but from understanding the business deeply enough to know where AI can make a meaningful difference.
These archetypes explain how people arrive in the role. They do not explain why some succeed while others struggle. The biggest distinction is not governance versus analytics or technology versus business. It is leadership.
Many aspiring CDOs spend years developing deep expertise in a particular discipline. That expertise matters. However, the transition into senior leadership requires a fundamental shift.
You stop being the expert who personally solves every problem. You become the leader who brings together the right expertise to solve problems collectively.
As a matter of fact, a governance specialist does not need to become the world’s best data scientist. Similarly, an analytics leader does not need to become the organization’s strongest architect, nor does a technology executive need to master every governance framework.
Instead, they need enough understanding across disciplines to build effective teams, make informed decisions, and create alignment.
The leaders who struggle are often those who remain attached to being the smartest specialist in the room. The ones that thrive are those who understand enough across every discipline to ask the right questions, build strong teams, and align people around business outcomes.
That’s the biggest shift from functional expertise to leadership, and in my experience, it’s what defines a successful Chief Data Officer.