Data Governance Fails When IT Alone Leads
The Forbes Council article by a contributor identified as president and CTO of DataOps reports that organizations routinely stall on AI plans because core data governance was built inside IT without business participation. The author says experience across more than 200 engagements shows leadership teams often have budget and executive buy-in but still face messy, untrusted data. The piece cites a February 2024 forecast from Gartner Inc. that some efforts could fail by 2027 due to crisis-driven urgency. It also notes that MIT Sloan Management Review, citing a 2020 NewVantage Partners survey, found 90% of respondents pointed to people and process issues versus 9.1% pointing to technology. A 2021 Drexel University survey is cited as identifying cultural awareness and adoption as top obstacles. The article argues that governance requires cross-functional ownership and leaders who can bridge technical and business concerns.
What happened
The Forbes Council article, authored by a contributor who is president and CTO of DataOps, reports that many organizations with AI ambitions still fail to operationalize trustworthy data because governance programs were designed with only IT at the table. The author writes that this pattern appears across more than 200 client engagements.
Reported supporting evidence
The piece cites a February 2024 forecast from Gartner Inc. that some efforts could fail by 2027 due to crisis-driven urgency. It also references MIT Sloan Management Review, which in turn cites a 2020 NewVantage Partners survey where 90% of Fortune 1000 respondents identified people and process barriers and 9.1% identified technology as the principal obstacle. A 2021 Drexel University survey is cited as finding cultural awareness and adoption the top obstacles to data governance.
Technical details
The article frames IT responsibilities as infrastructure, access controls and pipelines, and reports that technical platforms alone do not produce organizational trust in data. The author emphasizes the need for governance definitions, accountability, and guardrails that map to the way different business teams work.
Editorial analysis
Industry context: Companies that confine governance ownership to IT commonly face adoption gaps because operational definitions and accountability live outside the technical domain. Change-management and role-specific guardrails are recurring themes in the literature cited by the article.
Context and significance
Editorial analysis: For organizations moving toward enterprise AI, the piece places emphasis on nontechnical barriers-people, process and culture-which industry surveys repeatedly surface as higher-friction than tooling. That framing aligns with established practitioner guidance that governance programs should combine data stewardship, business-domain definitions, and technical enforcement.
What to watch
For practitioners: track whether governance programs assign clear business-domain stewards, whether guardrails are tailored by function, and whether adoption metrics (usage, exception rates, trust surveys) are collected. Observers will also want to compare reported program outcomes against the benchmarks cited in the article, such as the NewVantage and Drexel survey findings.
Scoring Rationale
This topic is highly relevant to practitioners building production AI because governance and adoption deficits routinely block deployments. The piece consolidates survey-backed evidence and practitioner experience, making it a notable operational caution but not a frontier-technology breakthough.
Practice interview problems based on real data
1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problems
