{"slug": "6-questions-every-enterprise-has-to-answer-about-ai", "title": "6 Questions Every Enterprise Has to Answer About AI", "summary": "At KPMG's annual Tech and Innovation Symposium, six foundational questions about enterprise AI emerged, signaling a shift from assisted to agentic AI. The consensus is that AI is no longer a technology problem but a transformation problem, requiring organizations to redesign processes, monitor costs, and plan for obsolescence. KPMG's Steve Chase warned that bolting AI onto existing systems is a recipe for trouble.", "body_md": "You've probably sat in this meeting.\n\nSomeone asks, \"so where are we with AI, actually?\" — and six people give six different answers.\n\nLast year, the questions were \"should we do this?\" and \"how do we prove ROI?\" This year, those questions have mostly disappeared.\n\nWhat replaced them are harder, more foundational questions. If nobody at your company is asking them yet, that's the thing to worry about.\n\nNLW came back from KPMG's annual Tech and Innovation Symposium with six questions that kept surfacing there. Almost none of them have answers right now. But they're the right questions.\n\nThe paradigm change already happened: from **assisted** AI (it helps me work) to **agentic** AI (it does the work).\n\nEnterprises spent three years anticipating this. Now that it's here, every question has been swapped out — they're all about how to solve the new problems this new way of working creates.\n\nNLW's read: 2026 is the year \"AI is not a technology problem, it's a transformation problem\" finally came home to roost.\n\nThe keyword is **redesigning**.\n\nThe strongest warning from KPMG's Steve Chase on the panel was this: bolting an AI strategy onto existing processes and systems is a recipe for trouble.\n\nIn the assisted-AI era, bolting on just meant you under-used the potential. In the agentic era, the cost gets much worse.\n\nWhen a new challenge arrived, the old corporate reflex was \"which vendor solves this best?\"\n\nThat's no longer sufficient.\n\nThinking in architectures means three concrete things:\n\nThe third question is about money: who spends what.\n\nUnderneath it sits another systems requirement — **monitoring and measuring AI usage**.\n\nNLW put it vividly: you haven't heard the word \"token\" this often at an event since the height of the crypto era.\n\nWithout visibility into AI cost and its relationship to output, you can't decide which individuals, teams, or projects should get which models, at what magnitude.\n\nThis is the one I related to most.\n\nThe consensus in the room: this will not be a set of nicely-produced corporate training videos.\n\nIt's real, messy work — pushing people to use new tools to do new things, then figuring out how to transmit knowledge from the parts of the org that have figured it out to the parts that haven't.\n\nThe pattern that kept recurring was **pairing**: putting AI-redesigned engineering teams and early adopters together with business units.\n\nNote what nobody was saying: that marketing will replace engineers. What they were discussing is how the 10–20% of skills — and more importantly the **mindsets** — that engineers and PMs carry become part of the essential toolkit for marketing, sales, and back-office people.\n\nEverything above is internal transformation. But there's an external dimension too.\n\nDirections discussed on site:\n\nMost organizations, though, treat themselves as \"patient zero\": shore up how they work internally first, then decide whether to radically change what they sell.\n\nThe hard part is that nobody gets to shut down for six months to figure it out. You do it in real time, while still servicing legacy customers on legacy products through legacy delivery.\n\nThe last question is the most counterintuitive.\n\nIf you're building new systems, how do you build **dynamism, planned obsolescence, and ephemerality** into them from the start?\n\nHarnesses will change. Interaction patterns will change. Customer expectations will change. Markets will change. Policy will change.\n\nSo anything you build today has to assume: a few months after it's ready, it will likely need rebuilding.\n\nAlmost none of these six questions have answers right now.\n\nBut that's exactly what should feel reassuring — people are finally asking the right ones. Last year the room was full of \"how do I convince others this is real?\" This year it's \"how do we redesign for a new era?\"\n\nIf I compress it to one line: **AI isn't a tool you buy and install. It's redesigning the organization around agentic work.**\n\nAnd that stack in questions 2 and 3 — multi-model tiering, routing, token-cost observability — is precisely why we're building Flatkey. Every enterprise is going to need that layer eventually.\n\n*Based on The AI Daily Brief (hosted by NLW), \"6 Questions Every Enterprise Has to Answer About AI,\" recorded around KPMG's annual Tech and Innovation Symposium. This is a structured secondary read; views and data per the original podcast.*", "url": "https://wpnews.pro/news/6-questions-every-enterprise-has-to-answer-about-ai", "canonical_source": "https://dev.to/hunter_g_50e2ec233acd07b5/6-questions-every-enterprise-has-to-answer-about-ai-2f9k", "published_at": "2026-08-02 07:42:30+00:00", "updated_at": "2026-08-02 08:12:54.611442+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-agents", "ai-policy", "ai-infrastructure", "ai-ethics"], "entities": ["KPMG", "Steve Chase", "NLW"], "alternates": {"html": "https://wpnews.pro/news/6-questions-every-enterprise-has-to-answer-about-ai", "markdown": "https://wpnews.pro/news/6-questions-every-enterprise-has-to-answer-about-ai.md", "text": "https://wpnews.pro/news/6-questions-every-enterprise-has-to-answer-about-ai.txt", "jsonld": "https://wpnews.pro/news/6-questions-every-enterprise-has-to-answer-about-ai.jsonld"}}