LEAD WITH DATA Podcast

The episode contains several valuable ideas about operationalizing governance through AI and policy-as-code, but substantial portions involve explanation of basic concepts (what is AI governance vs. data governance) and repetitive discussion of the same framework. The guest delivers genuine insights about moving from silos to integrated knowledge bases and treating agents as employees, but these are interspersed with considerable throat-clearing and general reflections that don't add density.

“The hardest part, I think, for data and AI governance is the embedment. You can have a great policy. Trying to embed that into an organization would take a rollout period, training period. You'd have to do, potentially assessments, checking of what's been done. And now you can have that all built into one.”

“So the gap between governance on paper and governance, that's really is where a lot of I think Programs tend to die from leaders that I talk to.”

The core concept of policy-as-code and embedding governance into workflows is relatively novel for traditional governance practitioners, and the framing of agents as employees with permissions/access models is interesting. However, the underlying ideas about risk-based approaches, cross-functional collaboration, and iterative learning are standard governance playbook material. The presentation feels incremental rather than fundamentally reconceptualizing the space.

“So we have a lot of promptathons, we have a lot of hackathons where we just say be creative and think outside of the box.”

“we need to treat them as if they are and employee. So we need to ensure that they have the right level of access to the right areas that we've assessed them to ensure that we're not breaching privacy concerns.”

Natalie Hogan is a credible operational practitioner with 15+ years in superannuation and regulated environments, currently executing governance transformation at scale in a complex, regulated industry. She is clearly embedded in actual implementation work, not a consultant or thought leader. However, her specific seniority level and organizational scope are never explicitly stated, limiting ability to assess true decision-making authority and scale of impact.

“Been working in superannuation or finance since I left school and my focus in superannuation has been for the last 15 years originally from financial planning and then moving into risk, uh, reporting and risk performance metrics and uh, moving into regulated reporting as well.”

“we did a, uh, check on all of that across the organization. We started to look at where our uh, gaps were and what we started to need to bring in.”

The episode contains few concrete examples, metrics, or timelines. While the guest mentions specific governance frameworks (DMBOK, APRA reporting, model governance, agent governance), her descriptions remain largely conceptual. No specific numbers on agent adoption, cost savings, timeline to implementation, or measurable governance improvements are provided. The superannuation regulatory context is relevant but underutilized for concrete examples.

“What do I need to do? I'm starting in an AI initiative. How do I go through this process? And it would ask questions reading its knowledge bank and then come back to you with a roadmap that says this is what you need to do to complete this and stay compliant”

“So if they've got a particular purpose that helps that particular team do a function and you have some that, you know, they might be doing assessments by checking recordings of the service center, for example, and ensuring that they meet certain regulation criteria.”

The host (Reena) asks solid clarifying questions and demonstrates genuine curiosity about operationalizing governance, with productive follow-ups on data foundations, agent roles, and team capabilities. However, she rarely pushes back on vague claims or asks for specific metrics. The conversation feels collaborative but lacks the edge of rigorous challenge - she accepts conceptual explanations without demanding concrete validation, and misses opportunities to pressure-test the sustainability of the approach or challenge optimistic framing.

“So when you went from driving data governance through Having agents and working in practice, uh, what did that mean for the people who were trying to use the data and what did it mean for the business?”

“Yeah, because I know there's been so many times where I've gone, I just want to know how much I've got in there, how, what's this payment for? And so good to be able to just quickly get that information”