An introduction to the new language for enterprise transformations.

Are you stuck in the circle of insanity?

Did you know that three-quarters of large-scale transformations have failed to deliver for more than three decades, a rate that hasn't budged despite new technologies and methodologies. One is now happening at massive scale as AI investment surges with little return. The Transformation Insanity Curve argues the cause that it isn't poor execution but misdiagnosis: leaders treat an architectural problem — realigning how a business creates value, how technology enables it, and how people learn — as a behavioral one. Drawing on 70+ enterprise engagements, the model charts six stages from the self-defeating "Circle of Insanity" to a genuine "Breakout Path."

This article argues that the real reason AI “doesn’t pay back” is that most enterprises deploy it into legacy architectures never designed for AI‑enabled ways of working. It contrasts the typical AI portfolio that has dozens of disconnected pilots in a Circle of Insanity with a three‑architecture model in which Business Architecture defines value flows, Technical Architecture follows the work rather than leading it, and Learning Architecture ensures people can actually operate in the new system. The piece walks through illustrative scenarios (e.g., failed shared‑services automation, stalled customer‑360 programs) and shows how an architectural reset changes the economics of AI. It closes with 5 questions boards and a CEO can ask their organization to see whether their AI investments are building a Breakout Path or just another spin in the Circle of Insanity.

Learning Architecture is the third leg of enterprise transformation, alongside Business and Technical Architecture, and the one most often left to chance. In this fourth installment of ENKI LLC's Enterprise Transformation Series, CIO Lawrence Dillon, Chief Client Officer Stephanie Qualls, and Education Practice Leader Dr. Synthia Taylor draw on adult learning science, decades of research on why 88 percent of transformations fail, and two real-world client turnarounds to show why training plans are not learning architecture, why traditional change management falls short, and what boards and CEOs should be asking before they approve the next transformation investment.

Artificial intelligence has become the newest test of enterprise leadership, but the real question boards face is no longer whether to adopt it. It's whether the organization can pursue AI aggressively enough to compete while governing it well enough to remain trustworthy. This article, the fifth in ENKI LLC's Enterprise Transformation Series, examines why AI ROI keeps eroding after deployment, how AI reshapes cyber risk beyond traditional perimeters, and why boards that cannot inventory their AI estate are guessing rather than governing. Drawing on research from Deloitte, IBM, NIST, and the World Economic Forum alongside ENKI's work across more than 70 enterprise transformations, the authors argue that durable AI value depends on redesigning Business, Technical, and Learning Architecture together, not on adding another policy or officer.

Here you unpack Business Archeology as the “investigative science” that precedes responsible strategy and architecture design. The article contrasts two approaches: arriving with a preferred framework and staffing the engagement to confirm it, versus starting with structured observation, interviews, and process tracing that reveal the gap between documented process and lived process. It shows how Business Archeology surfaces the informal systems, shadow organizations, and cultural workarounds that make-or-break AI, ERP, and shared‑services programs. A short-anonymized case vignette illustrates how 1,200 projects collapsed into fewer than a dozen coherent initiatives once the true architecture emerged. The call to action: stop approving nine‑figure programs without first commissioning a Business Archeology‑style diagnostic.

This article argues that AI is now a capability in the same category as cloud, ERP, and the commercial internet — too consequential to ignore and too dangerous to deploy casually— but most organizations still treat it as a collection of pilots and tools. Building on board‑level AI cyber risk guidance, it explains why strategy and architecture consistently lag AI experimentation, how that gap erodes ROI and increases risk, and what boards and C‑suites must require from management to treat AI as a strategic capability rather than opportunistic automation.

Aimed at boards and C‑suite leaders, this article offers a simple mental model for thinking strategically about AI: where to play, how to win, and how to protect. It connects AI directly to business strategy, value streams, and operating models, guiding executives to ask the right questions about AI’s role before approving investment. It leverages ENKI’s Business Information Model, IT Strategy process, and Business Archeology™ to ground AI in real work rather than slides.

Focused specifically on AI, this article argues that the limiting factor in AI‑first transformation is not GPU capacity or model choice but the organization’s ability to learn, adjust mental models, and make new kinds of decisions at scale. It shows how Learning Architecture uses metacognitive practices, reflection, and carefully sequenced learning journeys to help leaders, managers, and frontline employees change how they think about risk, judgment, and automation. The article draws a clear line between AI pilots that stay trapped in innovation labs and those that reshape how entire value streams operate. It ends with a suggested agenda that treats AI not as a technology demo but as a redesign of how the enterprise learns and decides.

Boards and C-suites that already use structured strategic choice frameworks, like Roger Martin's Playing to Win, know how to decide, where to compete, and how to win. What most haven't solved is why that choice keeps losing energy on its way to the front line. In this article we map how a well-structured strategic choice has to travel through Business, Technical, and Learning Architecture before it becomes anything more than a slide, and show, through a real warehouse example, how the right learning journey turns employees from blockers into owners.

This piece reframes governance from “committees and decks” to the concrete design of who decides what, using which information, under which constraints. It describes how decision‑rights frameworks and enterprise business information models (EBIM) act as the connective tissue between strategy, architecture, and execution. The article shows how unclear decision ownership and inconsistent definitions of core concepts (like “customer” or “product”) generate hidden drag on AI programs, M&A integration, and shared‑services transformations. Using simple illustrations (e.g., how a unified customer EBIM changes KYC, onboarding, and compliance initiatives), it argues that governance must be designed as part of Business Architecture, not bolted on afterward. The close: a set of three conversations boards should insist on before approving the next major technology or transformation spend.

This article positions Activity Modeling as the missing translation layer between business intent and modern technical patterns such as microservices, service oriented architecture, and AI agents. It explains how many enterprises draw technical boundaries based on systems or organizational structures rather than on reusable business activities and clear ownership. The piece shows how that leads to fragile microservice designs, brittle automation in shared services, and AI agents that automate edge cases while core work remains manual. A concrete example, restructuring customer‑facing processes around a coherent activity model, demonstrates how to simplify portfolios and reduce project sprawl. The article ends with three “acid tests” leaders can use to tell whether their AI or modernization program rests on solid activity logic or is simply repainting legacy complexity.

This article speaks directly to leaders whose AI, ERP, or “digital” programs are stuck, over budget, or politically toxic. It uses the Transformation Insanity Curve to help executives locate their current stage, whether they are in early denial, slogan‑heavy “change recognized,” or full “C‑suite Circle of Insanity.” It then lays out a practical roadmap to move from a stalled state into the Breakout Path: commissioning a Business Archeology‑style diagnostic, simplifying the portfolio around a few coherent value streams, rebuilding Business and Technical Architecture around those streams, and embedding Learning Architecture into the operating cadence. Short, anonymized case fragments illustrate how organizations have recovered from almost terminal fatigue. The article’s call to action is explicit: before you cancel or double down on a failing program, pause for a structured diagnostic conversation.

This article defines “Strategic AI” in ENKI terms: the integrated redesign of Business Architecture, Technical Architecture, and Learning Architecture to embed AI into the way an enterprise decides, learns, and governs risk. It distinguishes Strategic AI from ad hoc AI initiatives and tooling, shows why that distinction matters for boards and operating partners, and introduces core criteria that later pieces will elaborate.

This article paints a concrete picture of what “winning” in Strategic AI looks like for boards, investors, and operating partners. It synthesizes earlier pieces into a set of observable conditions: disciplined governance, aligned architecture, robust learning capability, resilient operations, and improving net ROI. It is written as a narrative description of the future state, with criteria executives can use to recognize whether their organization is on track or stuck in the Circle of Insanity™.

This article is targeted at C-suite leaders. It describes how to build an enterprise AI capability by redesigning Business Architecture, Technical Architecture, and Learning Architecture together. It shows why AI fails when any one of these architectures is weak, outlines concrete design questions per architecture, and introduces integrated practices for governance, delivery, and human capability.

This article bridges boards, C-suite, and architects by reframing AI ROI as net value after friction, control investments, remediation, legal exposure, downtime, and behavioral drag. It introduces a multi‑dimensional maturity model that assesses AI strategy across strategic alignment, architecture readiness, governance, risk and resilience, learning capability, ROI discipline, and third‑party control. The piece is concept‑level and sets up the more detailed instrument we plan to develop later.