Leadership
Written by: Chris Yates | SVP, Managing Director of Data and Architecture
Updated 10:00 AM EDT, August 26, 2026

For most of my career, data has been treated like plumbing. Everybody needs it, almost nobody wants to talk about it, and people only pay attention when something leaks. That mindset is dangerous now. Data is no longer the quiet utility behind the business. It is the language of the business. It is how we see customers, measure risk, understand performance, and decide which hill is worth taking next.
That shift changes the job of the Chief Data Officer (CDO). The CDO cannot be satisfied with being the person who owns the warehouse, the reporting stack, or the governance policy. Those things matter. They are the bones. But leadership is the muscle that makes the body move. If data does not shape decisions, if it does not create clarity, if it does not change behavior, then it is just another asset sitting on the shelf.
The hardest part of data leadership is not getting the data into a platform. The hardest part is getting the organization to believe the data, use the data, and act on the data together. That is where the work gets human. That is where titles matter less than trust.
Somewhere along the way, many organizations confused delivery with impact. We built dashboards, shipped reports, launched portals, and celebrated the artifact. Then we wondered why the same questions kept coming back in the next meeting. The lesson I have learned is that a dashboard by itself does not change behavior. It has to be connected to a decision, an owner, a rhythm, and a clear business outcome.
A dashboard can show what happened. Leadership can turn that into what matters, why it matters, and what we are going to do about it. That is the difference between reporting and data leadership. Reporting answers a question. Data leadership changes the quality of the conversation.
In practice, that means meeting business leaders where they are. When a team asks for another report, the better first question is not, “What columns do you want?” It is, “What decision are you trying to make, what risk are you trying to reduce, or what action are you trying to speed up?” That simple shift moves the work from fulfilling a report request to understanding what the business actually needs.
Trust does not arrive because a CDO says, “This is the source of truth.” Trust shows up after repeated moments where the numbers hold up under pressure. It shows up when lineage is clear, definitions are agreed upon, ownership is named, and the business can see the path from source to decision. Trust is not a slogan. It is a discipline.
That discipline requires a different approach to leadership. It is not glamorous work to define terms, retire duplicate reports, document pipelines, or put governance back into the daily operating model. I have seen how much friction can disappear when teams agree on a common definition before they argue about the trend. The executive conversation can change when leaders are no longer debating the math and can focus on the decision in front of them.
A practical move for CDOs is to identify the handful of metrics that create the most debate across the enterprise and start there. Name the business owner. Document the definition. Clarify the source. Establish the refresh rhythm. Then make that governance visible enough that leaders know where the number came from and who is accountable for maintaining its integrity.
Data leadership is not about having the most information in the room. It is about creating enough trust that the room can move.
Artificial intelligence has made the CDO role more visible, but it has also removed a few hiding places. Organizations want speed. They want automation. They want copilots, agents, predictive models, and faster answers. I understand the urgency. I feel it too. But AI does not forgive weak data leadership. It exposes it.
If definitions are unclear, AI can scale confusion. If access is messy, AI can magnify risk. If documentation is stale, AI can answer from yesterday while the business is trying to make tomorrow’s decision. AI readiness is not only a model selection exercise. It also requires determining which data is trusted enough, governed enough, and understood enough to be safely reused in higher-value workflows.
The CDO’s role as both builder and translator becomes especially important here. We have to understand architecture deeply. We also have to speak plainly enough that the business understands the tradeoffs. AI readiness is not a technical certification. It is an organizational maturity test, and the CDO can help the enterprise pass that test with clear standards, repeatable governance, and honest conversations about risk and value.
The next frontier of data leadership is not only about platforms, cloud strategy, or governance tooling. Those matter, but the real advantage is a cultural one: teams that ask better questions, leaders who do not use data as a weapon but as a flashlight, and an environment where it’s better to recognize a mistake and adjust than to remain committed to the wrong conclusion.
For CDOs, building this kind of culture also requires humility and a recognition that data teams do not hold all the context. In financial services, for example, the same number can mean different things to operations, risk, finance, technology, and the frontline. The work is not to force everyone into a technical conversation. The work is to create the shared language that lets those perspectives inform the decision instead of slowing it down.
I believe data is a team sport. We > Me is not just a leadership tagline. It is a data strategy. The analyst, engineer, steward, business owner, compliance partner, and executive sponsor all carry part of the mission. If one group tries to own the whole truth alone, the system can break down. If the work is shared with clarity and accountability, the system gets stronger.
My challenge to data leaders is this: stop measuring your value only by what your team produces. Start measuring it by what your organization can now decide, prevent, simplify, or accelerate because your team did the work.
Start with three questions:
The answers can help identify where data leadership has the greatest opportunity to create value.
From there, consider how that impact shows up across the organization:
The answers provide a clearer picture of whether a data organization is becoming a true enterprise partner.
Importance is not the same as impact. Impact is earned in the operating rhythm. It is earned in the hard conversations about ownership. It is earned when governance becomes a guardrail for speed instead of a symbol of friction. The leaders who make that shift can help their organizations move faster because they have done the slower work of building trust.
Data will continue to grow. Platforms will continue to evolve. AI will continue to change expectations across the enterprise. But one principle remains: organizations do not become data-driven because they have data. They become data-driven because leaders create the conditions for data to be trusted and used.
For data leaders, the charge is clear:
CDOs who embrace that approach can do more than modernize the data estate. They can help modernize how the organization thinks, decides, and moves. And in the AI era, that may be the most important data leadership opportunity of all.