Every Successful AI Pilot Creates a Hidden Liability A large US insurer once asked us to help modernize how claims got processed. RPA bots went in, two legacy systems got replaced with one platform, and the pilot numbers looked excellent, faster intake, fewer manual touchpoints, happier claims adjusters in the room where it was tested. Everyone in that room had reason to be pleased. The metrics were real, the adjusters were not exaggerating their relief, and on paper this looked like exactly the kind of automation story organizations like to tell about themselves. Eighteen months later, that same pilot was still running in exactly one regional office. The model had not gotten worse. Nothing about its performance had changed. What changed is that scaling it meant pulling in people who were never part of the pilot, a budget owner who had to fund the rollout, a compliance team that suddenly had to sign off on something that used to be a contained experiment, an operations lead who had to ...

Most enterprise AI governance conversations I sit in on still treat "the model" and "the system around the model" as the same thing. A risk committee asks whether the AI is safe, someone answers with a benchmark score, and the conversation moves on. It is a comfortable shortcut, and it is also the reason so many governance frameworks fail the moment an agent gets real access to a real environment. Anthropic gave the industry an unusually clean way to see why that shortcut breaks down. In late May 2026, the company published a long engineering account of how it contains Claude across its three agentic products, claude.ai, Claude Code, and Claude Cowork. It is candid in a way corporate security writing rarely is, naming specific incidents, specific failure rates, and specific architectural choices that did not work the first time. Read against the backdrop of April's decision to hold back Claude Mythos Preview after it engineered its own way out of a sandbox dur...

  Most AI Failures Are Not AI Failures A regional bank in the northeastern US came to us with a familiar ambition. Move from a hierarchical structure to a project based operating model, faster decisions, less layered approval, technology and operations working as one team instead of two. The technology side was never the hard part. The hard part was that nobody had touched decision rights. People kept reporting the way they always had, escalating the way they always had, getting evaluated the way they always had. The bank wanted agility without redesigning who owned what, and that gap is where the actual work began. We ended up redesigning the operating model for the technology and operations group, building a new talent platform and reward framework around it, because the structure had to change before any process inside it could. This is the pattern we keep seeing, and it rarely gets named correctly. Pilots succeed on a narrow, well defined task with a small group of engaged user...

1989, Kathleen M. Eisenhardt published a landmark review of Agency Theory that would influence decades of thinking across economics, organizational behavior, finance, governance, and management. While the theory is often associated with incentives and monitoring mechanisms, its deeper contribution was to illuminate a more fundamental organizational challenge: how do we govern delegated authoritywhen information is imperfect and uncertainty is unavoidable? At its core, Agency Theory examines the relationship between a principal and an agent. Shareholders delegate authority to executives, boards delegate authority to management, and clients delegate authority to advisors. The challenge arises because the principal cannot perfectly observe what the agent knows, what actions are being taken, or whether those actions remain aligned with the principal's interests. Agency Theory provided a framework for understanding these tensions through concepts such as information asymmetry, incentive...

This is the closing piece of the second DigitalWalk editorial series. Over five weeks, five stories examined a single shift from five different entry points. If you followed one or two pieces and want the full map, this is it. Every anchor piece is linked below with both the Blogger analysis and the LinkedIn post for each story. The shift the series documented is this. AI crossed the threshold from experimental to consequential. Not in one domain. In every domain simultaneously. In the emergency room, in the courtroom, in the banking system, on social platforms, and inside enterprise software architectures. And in every domain where AI crossed that threshold, the accountability architecture was designed before the crossing happened and had not been updated to reflect a world where it has. That is the argument the series was always making. Every story was a different entry point into the same structural gap. The ER that changed the question When AI Becomes an Actor — Blogger Analysi...

Four stories into this series we have spent considerable time on what happens when AI governance fails. The Harvard ER trial revealed a liability map drawn for a world that no longer exists. The ChatGPT courtroom cases exposed a privacy architecture that millions of users assumed was there and was not. The Mythos dual-use problem put the Treasury Secretary on primetime television warning Americans about their bank accounts. TikTok's Remix feature demonstrated what platform governance looks like when the accountability architecture is built around creators rather than for them. This week two enterprise software companies demonstrated what the alternative looks like. Not perfectly. Not completely. But deliberately and publicly enough to deserve recognition as a model rather than just a product announcement. Microsoft pushed Microsoft 365 E7 and Agent 365 to general availability with a governance architecture that makes a specific and significant choice. Every AI agent operating wit...

TikTok Made Your Content AI Fodder by Default. That Is Not a Glitch. It Is a Governance Tell. When a platform ships a major AI feature with default opt-in, no global toggle, and no notification to affected creators, it is not making a technical mistake. It is making a governance choice. And that governance choice tells you more about how the platform thinks about creator rights, consent, and accountability than any policy document it has ever published. TikTok's Remixes feature, rolled out this week, lets any viewer turn a public post into AI-generated images, text memes, or other derivative content. The setting was on by default for every public post on the platform. Creators only found out because someone went digging through account settings and posted about it in complaint threads. There was no notification. There was no global toggle. Disabling Remix requires creators to turn it off on every individual post they have ever published, one by one. This is the third time in r...