Topic starter
24/06/2026 7:41 pm
TL;DR: AI governance breaks when organisations treat data selection as an afterthought, because low-quality, poorly contextualised, or noncompliant data drives confident but flawed model outputs according to Collibra. The real governance risk starts upstream, where data is chosen, classified, and understood before deployment hardens bad assumptions into automated decisions.
Editorial analysis by NHI Mgmt Group, based on content published by Collibra: “The AI connoisseur. Curating high-quality data for responsible innovation”.
Key questions
Q: How should teams decide whether a dataset is suitable for AI use?
A: Start with use case fit, then test quality, context, and permitted use.
Q: Why do AI projects fail when data review happens too late?
A: Because AI turns data assumptions into repeatable behaviour.
Q: What do organisations get wrong about data governance for AI?
A: Many organisations treat data governance as a reporting or analytics function instead of a control layer for delegated action.
Practitioner guidance
- Define data approval gates before model work begins Require use-case owners to prove that candidate datasets are relevant, current, and legally usable before any training or tuning starts.
- Attach ownership and business context to AI data assets Make provenance, intended use, and data steward responsibility visible in the same workflow that teams use to request or consume the data.
- Separate data quality checks from compliance checks Treat accuracy, completeness, and freshness as one review track, and permitted-use and sensitive-data constraints as another, so one pass does not mask failure in the other.
Bottom line: AI governance fails when data selection is treated as a secondary step instead of the control that shapes model behaviour.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 5:04 am
Data understanding is the real control boundary in AI governance: deployment controls cannot compensate for poor upstream data selection. Once a model is trained or tuned on unsuitable inputs, the error becomes repeatable, scalable, and harder to unwind. That shifts governance value from post hoc monitoring toward pre-use discernment. The implication is that AI programmes should be designed around data readiness, not just model approval.
A few things that frame the scale:
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How can organisations tell whether AI governance is actually working?
A: Organisations can tell AI governance is working when they can inventory every agent, explain its purpose, show who owns it, and prove that permissions are tightly scoped. If those four things are missing, the programme has policy language but not operational control. Auditors will notice the gap quickly.
👉 Read our full editorial: AI governance fails when data understanding comes second