This blog is a running argument about enterprise technology for large, regulated enterprises — the kind that run on software they bought, not code they wrote. It’s written by a practitioners who lead enterprise architecture and AI in exactly those environments.
Across everything here, the writing keeps returning to a few ideas:
- Enterprise architecture should be judged by business outcomes. Its artifacts — diagrams, standards, governance — matter as far as they move the business, and not much further.
- The gains usually come from collapsing the relay, not scaling it. The layers and teams between the business and its systems tend to add more delay than capability.
- The “AI platform” is usually fewer real components than the diagrams suggest — and which ones you actually need depends on the use case.
The work falls into three bodies. You can read them as a progression, or jump to whichever fits what you’re working on.
Enterprise Architecture — Function by Function
The foundation. Each piece takes a function of enterprise architecture and argues how it should be reshaped to deliver value.
- Unlocking Real Business Value from Enterprise Architecture
- Designing an Operating Model for Enterprise Architecture
- Rethinking Architecture Governance in Large Enterprises
- Let’s Rethink Reference Architecture Diagrams
- Optimizing Technology Spend Through Platform Teams
Worked case studies, where the reasoning is shown end to end:
- Intersecting Business and Technology · Example 1 — EA enabling admissions growth
- Intersecting Business and Technology · Example 2 — build-vs-buy, worked through
Enterprise AI — What AI Actually Changes
From the economics of building software to the myth of the “AI platform.”
- The New Economics of Software Engineering
- Enterprise AI Architecture: What’s New and What Isn’t
- The Enterprise AI Platform: What’s Left When You Unpack It
- Your AI Problem Is Not a Technology Problem
- Governance Is a Form, Not a Platform
Beyond EA — The Future Enterprise
A forward view of the enterprise after the middle collapses. This is a point of view drawn from experience — where the enterprise is heading, not a report on something already built.
Read in order:
- The Agentic Enterprise Needs a Spine, Not a Mesh — the overview
- The Enterprise Without a Bridge — the shape of the organization
- Where the Lines Should Be Drawn — the system boundaries
- The Contract Is the Crossing — how domains connect
Supporting read: The Mesh Keeps Coming Back. The Reason For It Doesn’t. — why the “agentic mesh” is the latest in a long lineage, and why its cost case has expired.
If You Read Only Four
- Beyond Buy vs. Build: The Rise of GenAI-Accelerated Transformation — the accelerator model
- The New Economics of Software Engineering — why the cost of building changed
- The Enterprise AI Platform: What’s Left When You Unpack It — the platform, deflated
- The Agentic Enterprise Needs a Spine, Not a Mesh — the future enterprise, in one argument