![\"\"](\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/05\/iStock-2187999439.jpg\")
<\/p>\n<\/p>\n
Sutowo Wong<\/a> wants to tell you something uncomfortable. The managing director of AI & data at\u00a0Temus<\/a> \u2014 a Temasek Holdings digital transformation consultancy \u2014 stood before a room of data and digital officers at the\u00a09th CDDO Asia Summit<\/a> in Singapore and laid out a chart. A blue line, a gray line and a chasm between them.<\/p>\n The blue line is what AI should be delivering to your organization, given the pace of technological progress. The gray line is what it is actually delivering. The gap between them, Wong estimates, is roughly ten trillion dollars. Globally, unrealized, and sitting there like an unread email. \u201cThere\u2019s so much that AI can do,\u201d he told the audience, \u201cbut we are hardly scratching the surface.\u201d He\u2019s right. And if you\u2019re a CDO, this is squarely your problem.<\/p>\n The tempo problem<\/p>\n Here\u2019s the paradox that should keep every data officer awake. AI model breakthroughs now arrive every few months. GPT-4 to GPT-4o. Claude 3 to Claude 3.7. DeepSeek rattling cages out of nowhere. Meanwhile, the average enterprise AI deployment? Wong puts it bluntly: \u201cSometimes it can be five years.\u201d<\/p>\n In AI time, that\u2019s geological.<\/p>\n Wong calls it a \u201ctempo mismatch,\u201d and it\u2019s not a technology failure but a management one. The models are ready. The infrastructure is increasingly mature. What lags is everything else: operating models, workflow redesign, governance structures, and the all-too-human tendency to commission another pilot instead of shipping something real.<\/p>\n \u201cIt is not about the technology,\u201d Wong said, with the tone of someone who has said this too many times. \u201cIt is a problem of change management. It is a problem of integration \u2014 not just in a technical sense, but in the sense of how do you integrate that into your workflow?\u201d<\/p>\n The AI triangle: Value, speed, sovereignty<\/p>\n Wong\u2019s framework for closing the gap has three legs. He calls it the \u201cAI Triangle,\u201d and he emphasizes that you need all three to score.<\/p>\n Value. Achieve measurable, organization-wide outcomes. Not a science experiment in one division. Not a productivity stat no one can convert to revenue. Hard savings, or don\u2019t bother.Speed. Prototype in hours. Ship to production in weeks. Wong\u2019s team can build a working prototype in six hours. That same project? In production in under 12 weeks. \u201cGone are the days when you can spend years on the transformation program,\u201d he added.Sovereignty. AI contextualized to your organization \u2014 your data, your architecture, your existing investments. Not a generic model answering generic questions about your highly specific, very real business.<\/p>\n Wong spent additional time on sovereignty. Most enterprises \u2014 especially in regulated industries \u2014 cannot simply hand their data to a cloud-based LLM and call it a day. Your competitive edge lives in proprietary data. Your compliance obligations live there, too. It means a capable model is the starting point, not the solution.<\/p>\n The agent economy is already here<\/p>\n Wong\u2019s bigger argument isn\u2019t about LLMs but what comes after them. \u201cWe have entered the AI agent economy,\u201d he declared, tracing AI\u2019s evolution from computer vision (AI can see) to transformers (AI can understand) to diffusion models (AI can create) to agentic systems (AI can act).<\/p>\n The shift, as he frames it, is from conversation to execution. AI is no longer a search engine you type questions into. It\u2019s an autonomous actor that plans, maps tasks, executes them, and reports back. For a CDO, this goes beyond an incremental upgrade; it\u2019s a category change. The governance implications alone could occupy a full offsite.<\/p>\n Wong offered a telling governance example: imagine two AI agents in your organization \u2014 one in finance, one in HR. What happens when the finance agent queries the HR agent for compensation data? Should that be allowed? Who approved it? What\u2019s the fallback if it fails? These are not theoretical questions. They are the operational reality of deploying agents at scale, and most enterprises have answered exactly none of them.<\/p>\n He also drew a sharp line between probabilistic and deterministic AI \u2014 a distinction critical in financial services. \u201cYou want to execute a transaction \u2014 wire an amount from one account to another. You want it to be \u2018about right\u2019? A million dollars, plus or minus? No way.\u201d Determinism matters. Especially when the stakes are real.<\/p>\n Proof points that aren\u2019t vaporware<\/p>\n Wong is refreshingly numbers-oriented. He doesn\u2019t offer transformation in the abstract; he offers receipts.<\/p>\n At a genomics lab, his team cut processing time from over 60 hours to under 90 minutes. Compute costs dropped 85 percent. At a cybersecurity client, AI agents now handle the full vulnerability management loop \u2014 scanning, severity triage, remediation recommendations and stakeholder communications \u2014 autonomously, eliminating the budget line.<\/p>\n At an insurance firm, AI-powered training avatars doubled agent activation rates. The context matters: only three to five agents survive out of every hundred hired. Training them is expensive and mostly wasted. Using AI to simulate demanding (and sometimes unreasonable) customers, then scoring and coaching agents, makes the economics suddenly sensible.<\/p>\n The common thread? None of these are pilots. They\u2019re production deployments. \u201cExperiment once, deploy many times\u201d is Wong\u2019s mantra. If you\u2019re still running your fourth proof of concept on the same use case, you already know who you are.<\/p>\n The CDO imperative<\/p>\n Wong\u2019s prescription for CDOs is uncomfortable in the best way. Stop waiting for the data foundation to be perfect before you deploy AI. Start with your most valuable, most ready-to-use cases, then work backward to identify exactly which data you need, and prepare only that. Multi-year data transformation programs launched in anticipation of future AI projects are a form of organizational procrastination. \u201cDon\u2019t wait for two years. Don\u2019t wait for five years.\u201d<\/p>\n The operating model is equally non-negotiable. If every AI use case requires a bespoke negotiation with IT to extract and clean data, you will never move fast enough. Speed demands structure \u2014 clear decision rights, clear escalation paths, and clear ownership. Without that scaffolding, AI transformation becomes a series of heroic one-off sprints that don\u2019t compound into anything.<\/p>\n