Welcome to another episode of the Data Debrief, the companion show to Driven by Data: The Podcast, where hosts Catherine Dowden-King and Kyle Winterbottom unpack Tuesday's episode, share what's been on their minds, and explore the realities of leadership, culture, and capability across the data and AI landscape.

This week, Catherine and Kyle reflect on the conversation with David Krauza, VP of Enterprise Data Strategy, Products & Governance at Comcast, diving deeper into the "arts and crafts" trap that derails data programmes, the discipline of building stakeholder trust before you need it, and what it really takes to drive the bus rather than ride it.

They cover:

Why David's mandated business school module ended up shaping his outlook on data leadership, and the recurring pattern of guests whose commercial thinking was forged outside a purely technical background
The "arts and crafts project" analogy David's boss used to describe technically impressive work that never moves the needle, and why naming the difference between process-enjoyment and outcome-focus matters as much in data as it does in any creative pursuit
Why so much of the data and AI ecosystem gravitates toward exciting new models, tools, and techniques without tying the work back to specific goals, decisions, and KPIs
David's framing that you have to help people before you need their help, and why the leaders who consistently land the biggest roles are the ones already putting into their networks and communities long before they need anything back
Catherine's take on why this same principle defines external brand building, and why leaders who wait until they're job hunting to invest in relationships are always playing catch-up against those who started years earlier
Kyle's view that building relationships with future stakeholders is not a side project for a data leader, it is the job, every bit as much as overseeing platform delivery, governance, and architecture
Why David reframed the trust gap many data leaders face as a sequencing problem rather than a communication problem, and what that distinction means for how and when leaders should be reaching out
The "bus riders and bus drivers" analogy at the heart of the episode title, and why organisations hire a data leader precisely because they don't already know the answer, making it the leader's job to shape direction rather than simply execute instructions
Why being a strong, detailed communicator changes the entire dynamic of a hiring conversation, and how that same skill plays out with stakeholders once someone is in the role
Catherine's practical tip for building interview and communication confidence using AI tools like ChatGPT or Claude as a low-stakes practice partner, and why consistent repetition beats waiting for natural talent to show up

Kyle's thought of the week: prompted by a message from a CDO at a crossroads in their career, Kyle reflects on why the CDO role isn't disappearing or resurging industry-wide so much as it's becoming entirely dependent on whether a business's leadership views data as a commercial value-creation function or a technology delivery capability. Where it's the latter, that responsibility increasingly sits with the CIO, and Kyle notes the early signs of broader transformation-style mandates emerging that fold CDO, CIO, and Chief AI Officer responsibilities into a single board-level role.

This episode explores what it actually takes to drive value rather than just deliver outputs, the discipline of investing in relationships long before you need them, and why naming the gap between busywork and real impact is often the first step to closing it.