AI Governance
By: Todd Henley | Board Member of AIFAlliance.org, Chirag Agrawal | Global Head of Data Science at Novelis, Tina Salvage | Senior Data & AI Consultant at OminiaDigital, Rehan Kausar | Chief AI Officer, AI Advantages, Mansi Agarwal | Global Head of Analytics and AI at Carrier, Shuchi Agrawal | Head of AI Execution, SMBC Group, Robin Gordon | Chief Data Officer, Hippo
As Told To: CDO Magazine
Updated 2:56 PM EDT, May 14, 2026

AI is being pushed into all areas of organizations at breakneck speed, often without full consideration of the impact. Yet CDOs and data leaders are expected to ensure everything remains controlled, explainable, and compliant.
That’s why strong AI governance is no longer a theoretical discussion. This complete system of checks and balances of autonomous systems, from conception to monitoring, is now an everyday operational challenge.
But AI adoption can feel like it’s moving faster than governance frameworks, strategies, and implementation models can mature.
To help data leaders thrive, we’ve drawn insight from our extensive community of executives who are navigating these realities firsthand.
This guide explains how to deal with the trade-offs, gaps, and decisions that emerge when AI systems move beyond pilots and into production. It brings together components data leaders will need to research, implement, and monitor AI governance, using deep insights gained from experienced executives.
Before beginning any implementation, data leaders need to set their AI governance strategy, which helps focus on and build in the right frameworks, goals and implementation. Setting this early means creating a safe, secure and ethical AI system.
But as these systems are increasingly embedded into workflows, retrieving information, interacting with applications, coordinating tasks, and triggering actions in real time, that evolution changes the nature of governance entirely.
Chirag Agrawal, who leads global data and AI initiatives in a major manufacturing organization, has experience of how to focus on this transition, from assistance to execution.
His vision allows data leaders to reflect on a broader enterprise reality: traditional governance models were designed to manage model risk, not autonomous behavior operating dynamically across systems.
When setting a strategy, Agrawal also emphasizes something many organizations still underestimate: AI governance cannot operate effectively as a static review process when systems are acting continuously.
To ensure AI governance scales safely and confidently, watch for key warning signs.
Many organizations begin by searching for an AI governance framework, a defined structure that can be easily deployed to keep new AI models in check.
Across enterprises, one pattern appears repeatedly: teams spend months aligning on governance structure while foundational issues such as data quality, ownership, collaboration, and change management remain unresolved.
Todd Henley, who has spent more than two decades building governance, risk, and compliance programs across regulated industries, argues that the industry has become far better at producing frameworks than explaining how to operationalize them.
Organizations don’t need to solve everything simultaneously. Frameworks are useful, but only when they support how the business actually operates.
Start by assessing organizational culture, change management maturity, and collaborative capacity to determine the best-fitting frameworks.
Plan to build strong cultural foundations and work hard on building space for collaboration. This will enable smoother integration and help foster buy-in across departments.
Existing structures are the data leader’s friend: build on them for scalability and minimal disruption. This saves budget and resources by not bringing in a new disruptive system.
Ultimately, best practices ensure AI governance frameworks are compliant, robust, and relevant, giving key business leaders confidence in their ability to adapt to future needs.
One of the simplest questions in AI governance often exposes the biggest weakness: who owns your organization’s most critical AI system?
Here’s a clue: it should never be a committee, nor simply a function of another system.
Rehan Kausar is a seasoned AI leader who advises regulated financial institutions on AI governance and examination readiness. He has seen the same structural issues surface repeatedly and is steadfast in his belief that clearly defined AI governance roles are essential, with one accountable owner assigned at each stage.
He also highlights that it’s not even a single person that is responsible for the entirety of the platform.
Ownership shifts across stages:
Each phase requires explicit accountability tied to named owners with authority to act. This is one of the clearest differences between AI governance that exists operationally, and that which exists primarily in documentation.
Most organizations already have AI governance policies. The larger issue is whether they’ve embedded enforceable controls throughout the AI lifecycle before regulators, auditors, or risk events find the gaps.
That’s where having rigorous AI governance compliance comes to the fore.
Especially in regulated industries, scrutiny is shifting away from policy documentation and towards operational evidence.
Based on his work in risk and compliance environments, Kausar points to a major change already underway. Regulators and examiners increasingly want proof that governance controls are functioning continuously inside production systems.
The same challenge extends into third-party AI governance and vendor risk management. Many organizations now operate AI indirectly through SaaS platforms, embedded AI features, foundation model providers, and external APIs.
Those systems still create AI governance obligations even when the organization did not build the underlying model itself. Policies can, of course, define intent, but only controls make that intent enforceable.
Getting the compliance right means the gap between known and documented systems is a measurable, regulatory cost, and one that’s increasingly enforced.
Some of the biggest AI governance failures are not technical at all. They are ethical failures, where the system does not uphold the enterprise’s needs or values. These often only become visible once AI systems begin operating at scale.
Tina Salvage, a senior data and AI leader working closely with enterprise teams, approaches things through the lens of ethical AI governance.
Her perspective reflects a growing enterprise reality: many AI risks emerge not because systems malfunction, but because underlying assumptions were never properly questioned.
In many cases, the system is technically working as designed. The ethical problem happens when the outcome is scaled.
This is why responsible AI governance increasingly requires organizations to evaluate not just whether systems work, but whether their decisions can be justified, explained, and defended under scrutiny.
If that’s not the case, then heading back to the discussion table about how these points can be addressed is an action that should be taken as a matter of urgency.
Many governance programs appear mature structurally but struggle to demonstrate whether governance is actually working. That’s where AI governance metrics and KPIs become critical..
Mansi Agarwal, Global Head of Analytics and AI at Carrier, approaches this problem from a systems and outcomes perspective.
Her view reflects a broader shift happening across enterprise AI: governance is increasingly being evaluated through system behavior over time, not simply through point-in-time validation.
Agarwal’s concept is treating every AI agent as a governed entity with identity, ownership and lifecycle tracking. It introduces a more actionable way of thinking about AI governance – and how success is measured.
While it might be enticing to think of implementation as the only important thing, defining the right AI governance metrics is arguably the most critical. Only then will data leaders be able to see if what they intended is functioning correctly.
Visibility alone does not solve the challenge of effective AI governance implementation. One of the hardest parts of operationalizing governance is translating visibility, policies, and oversight frameworks into consistent execution.
Establishing clear AI governance guidelines across systems, workflows, and teams is critical to turning governance from a theoretical framework into a scalable, working enterprise capability.
One of the most common gaps is the separation between governance and engineering workflows. AI systems are developed inside delivery pipelines, while governance is a parallel review process. Teams work around governance, rather than with it.
Shuchi Agrawal, an experienced AI and data executive across financial services, aviation, and healthcare, focuses heavily on closing this divide.
Her perspective reflects an important operational reality: AI governance scales far more effectively when it becomes infrastructure instead of oversight.
To successfully scale AI, enterprise leaders must embed AI governance into their operating model. But it must be owned as a transformation capability, not merely a compliance function.
Getting the right guardrails in place is crucial for CDOs looking to show their worth, and give the confidence to regulators, customers, employees, and boards that will allow them to scale their projects in the right way.
AI governance is often treated as a new layer of enterprise oversight, bringing all-new challenges, but actually many of its biggest limitations trace back to something much older: data governance.
Robin Gordon, Chief Data Officer at insurance company Hippo, notes that many organizations appear mature from a data governance perspective. But they can lack the operational foundations AI systems actually require.
Most enterprises already have governance structures, but the problem is that these structures were largely designed for humans navigating data environments, not AI systems consuming data at scale.
This is where many organizations encounter the illusion of readiness. AI governance programs may document data successfully without making it operationally usable for automated systems.
Without those foundations, organizations struggle to move beyond narrow AI use cases into broader enterprise interoperability and scalable automation.
Gordon’s perspective reframes governance as something embedded into pipelines and operational systems rather than maintained primarily through documentation and policy layers.
Closing the gap between data and AI governance requires treating governance as a core component of data architecture, no longer just documentation.
What’s becoming increasingly clear across enterprises is that the AI governance challenge is no longer hypothetical.
Organizations are now trying to operationalize AI while simultaneously managing fragmented data environments, evolving privacy expectations, unclear ownership models, and growing regulatory pressure.
This hub gives data leaders the steps, checks and discussions needed to properly implement AI governance into enterprise – but for any executives looking for deeper insight into the AI governance landscape, we’ve put together our AI and Data Governance in the Enterprise Trend Report.
This explores many of the tensions spoken about in this article directly through research and practitioner perspectives from senior data and AI leaders.
The report finds out where organizations currently stand on governance maturity and where the biggest operational gaps still exist. It also analyses the processes of enterprises that are successfully moving from AI experimentation toward enterprise-scale execution.
The report includes perspectives from enterprise leaders across multiple industries, including governance, privacy, AI implementation, and automation experts. It also offers practical resources designed to help organizations strengthen governance capabilities as AI adoption accelerates.
For many CDOs, the challenge is no longer whether governance matters. It is how quickly governance capabilities can mature alongside increasingly autonomous systems.