Overview
In this episode of The Dashboard Effect, Brick Thompson and Caleb Oaks work through the AWS report on the CDO Agenda for 2024, using it as a framework for discussing how data leaders can prepare their organizations for the impact of generative AI. The conversation draws out the themes that resonate most with their own experience working inside real data environments, and the result is a grounded synthesis of what the report recommends and what that advice looks like when it has to be applied to an organization that is still building its data foundation.
For data leaders and technology executives trying to separate the practical from the aspirational in the generative AI conversation, this episode offers a useful reference point. See how Blue Margin’s Managed Data Platform helps organizations build the consolidated, high-quality data infrastructure that CDOs need to demonstrate visible business value today while positioning for the AI capabilities that depend on it tomorrow.
What This Episode Covers
Creating Visible Value (1:00 – 2:04)
The top priority for Chief Data Officers according to the report is demonstrating business value, not technical accomplishment. The shift the hosts describe is from measuring success by what was built to measuring it by what changed in the business as a result. That reorientation matters for how data teams communicate their work internally and how they prioritize what to build next.
Data Quality Is Paramount (2:09 – 4:43)
Despite all the focus on generative AI, the biggest roadblock organizations face is data quality. The garbage in, garbage out principle applies as absolutely to AI as it does to any other analytics tool, and the hosts are consistent on this point: clean, reliable data is not a prerequisite that can be deferred while AI tooling is evaluated. It is the work that needs to happen first, and in most organizations it is the work that is furthest behind.
Incremental Approach (6:02 – 6:43)
The report recommends avoiding monolithic data projects in favor of a use-case-by-use-case approach that delivers consistent, incremental value. The hosts endorse this framing directly. Large, all-or-nothing data initiatives are difficult to sustain organizationally and rarely deliver the business alignment that smaller, focused efforts can achieve more quickly and more visibly.
Do Not Abandon Existing Investments (6:44 – 7:35)
The temptation to discard existing data and analytics investments in favor of generative AI is one the report explicitly cautions against, and the hosts agree. The better path is to integrate generative AI into existing infrastructure rather than treating it as a replacement for work that is already delivering value. Rebuilding from scratch to chase a new technology is expensive and rarely produces the improvements that motivated it.
Common Data Platform (7:58 – 9:16)
Consolidating data tools onto a single, common platform, whether Azure and Fabric, AWS, or another unified stack, reduces maintenance overhead, improves security posture, and simplifies data management across the organization. The hosts make the case for platform consolidation not just as an efficiency gain but as a prerequisite for the kind of consistent data governance that AI readiness requires.
The Current State of Generative AI in the Enterprise (9:20 – 11:25)
The hosts are realistic about where generative AI’s enterprise applications currently stand. The most mature use cases are in customer operations, personal productivity, and coding assistance. Analytical applications that operate reliably enough for business decision-making are still developing. The conclusion they draw is practical: the best strategy right now is to get the data foundation in order so the organization is ready when more powerful AI analytical tools arrive, rather than waiting for those tools to motivate the foundational work.
Who It’s For
This episode is worth your time if you are a Chief Data Officer or data leader trying to align your roadmap with where the industry is heading without losing focus on the foundational work that makes any of it possible, a technology executive evaluating how to position generative AI investments relative to existing data infrastructure initiatives, a data team trying to make the case internally for platform consolidation and data quality work in an environment where generative AI is capturing more organizational attention, or any organization that has started asking what AI readiness means and wants a practitioner’s perspective on how to answer that question honestly.
Why It’s Worth a Listen
The value of this episode is in how it translates a formal industry report into a conversation grounded in the practical realities of data work. The AWS report covers the right themes, and Brick and Caleb bring the context needed to make those themes actionable for organizations that are not operating at the scale of the enterprises the report primarily addresses.
The point about not abandoning existing investments is worth particular emphasis. Generative AI has a tendency to be positioned as a replacement for rather than an extension of existing analytics work, and organizations that follow that framing often end up with neither a working AI capability nor the reliable reporting foundation they walked away from. The integration mindset the hosts advocate is more durable and more practical.
And the conclusion that getting the data house in order is the best current strategy for AI readiness is one that holds up regardless of how quickly the technology matures. Organizations that do that work will be positioned to take advantage of AI capabilities as they develop. Organizations that defer it will find themselves doing the same work later, under more pressure, with less time to do it well.
