Most organizations have data governance policies. Far fewer have data governance that actually works when it meets day-to-day operations. In this episode, Kenza and Pascal move beyond the theory and into the uncomfortable reality: why governance frameworks fail, why data quality is a leadership responsibility that nobody owns, and why the difference between having data and trusting data is exactly where most AI projects quietly fall apart.

The episode closes with a line worth writing down: a dashboard can be technically correct and still be organizationally untrustworthy. And another: trust should be earned by the system, not requested by the project team.

Key Takeaways

• Data governance only works when it protects value and speeds decisions — not when it is purely a compliance exercise people route around.

• The business owns the meaning of data. Technology owns the enablement. Governance connects the two.

• AI did not repeal garbage-in, garbage-out. It just made the garbage more eloquent. LLMs can mask data quality problems — which makes them more dangerous, not less.

• Trust in data must be built progressively: low-stakes decisions first, visible provenance, measurable error rates, and explicit human override.

• The opposite risk is equally dangerous: executives who trust the data too much. Confidence is not evidence. Mature organizations institutionalize questioning.

Hosted on Acast. See acast.com/privacy for more information.

"Data is the new oil." It's one of the most repeated phrases in every AI conversation - and one of the most misleading. Data is not valuable in itself. It is dead storage space until it is connected, trusted, contextualized, and governed in a way that actually improves decisions.

In this episode, Kenza and Pascal move from technology foundations into the data layer and make the case that most data problems are not technical problems at all. They are cultural, political, and leadership problems. And often, they are the result of organizations not knowing what they actually want to know.

Key topics:

• the DIKW pyramid (Data, Information, Knowledge, Wisdom) as a framework for understanding where companies get stuck,
• why data silos are political artifacts rather than technical accidents,
• how to move from raw data to decisions that actually change something.

Data silos are rarely technical accidents. They are political artifacts, fiefdoms inside organizations that protect data as a source of power.

Hosted on Acast. See acast.com/privacy for more information.

Legacy systems are not just old technology. They are the accumulated result of past decisions — many of them made for good reasons at the time — that now constrain everything a company wants to do with AI. In this episode, Kenza and Pascal go one layer deeper than IT image and strategy, into the structural reality of architecture, integration, infrastructure, and cybersecurity. They explore why legacy modernization is a leadership decision, not an IT backlog item, and what executives need to understand about the infrastructure gap between a successful AI pilot and production at scale.

Key topics:

- architecture choices that enable or constrain AI at scale,

- why disconnected systems create AI blind spots,

- the infrastructure investment needed for production-grade AI

- why cybersecurity is now an expanded executive responsibility.

Pascal's provocation: Legacy architecture is frozen decision history. The question for every board is which decisions are you still living with, and are they still the right ones?

Hosted on Acast. See acast.com/privacy for more information.