The Enterprise. Simplified.

Posted On August 25, 2026

Why AI Needs Enterprise Representation

This is the final part, Part 5 of The Enterprise. Simplified. In Part 4, I covered how business capabilities operationalize the enterprise.

One of the questions that have been asked most often over the past year is surprisingly simple.

“Why does AI struggle so much inside large enterprises?”

The answers are usually technical. Models need better prompts. Retrieval needs improvement. Context windows need to become larger. Semantic layers need to be richer. Knowledge graphs need to be expanded. Governance needs to mature. Agent frameworks need additional capabilities.

I don’t disagree with any of those observations.  They’re all important.  I’ve just come to believe they’re addressing symptoms rather than the underlying architectural problem.

Throughout this series, I’ve argued that enterprise architecture has gradually become centered on implementations. Projects deliver applications. Applications create representations of the business. New projects begin by interpreting those representations and producing new ones. Data warehouses, lakehouses, semantic layers, APIs, and AI platforms all improve how information is consumed, but they typically begin with the same implementation-centric view of the enterprise.

AI Focuses the Issue

Perhaps AI simply exposes that problem more clearly than previous technologies.  Think about how people work.

When a new employee joins an organization, they don’t begin by reading database schemas or studying API specifications. They learn what a customer is, how an order flows through the business, who is responsible for approving credit, how products are organized, and what information is important to each business function. In other words, they first develop a mental model of the enterprise before learning how individual applications support it.

We rarely give AI that same advantage.

Instead, we ask it to interpret thousands of tables, APIs, reports, documents, and application-specific representations, hoping it can reconstruct the business from its implementations. We continue adding retrieval systems, governance artifacts, and increasingly sophisticated reasoning capabilities to compensate for the fact that the enterprise itself has never presented a coherent representation of what it is.

That’s an extraordinarily difficult problem. Not because AI lacks intelligence. Because we’ve asked it to infer the enterprise rather than present the enterprise.

Throughout this series, I’ve suggested a different perspective.

The enterprise should present a stable, business-oriented representation of itself: its core information, the relationships among it, the behaviors that govern it, and the capabilities through which work gets done.  Business capabilities should expose the actions that create, modify, approve, and fulfill those entities through stable business abstractions. These elements create the enterprise representation I’ve been describing throughout this series.

If that foundation exists, something interesting happens.

An AI agent asked to create an order doesn’t begin by discovering which ERP system manages orders or which APIs belong to which application. It begins with the enterprise action Create Order. That business action exposes the information required to perform the work while allowing the underlying implementation to evolve independently.

The same principle applies to understanding customers, evaluating suppliers, approving invoices, analyzing inventory, or reconciling financial information. AI no longer needs to reconstruct the business from thousands of implementation artifacts because the enterprise has already described itself through stable information and business actions.

Enterprise Architecture. Simplified.

Notice that this isn’t really an AI architecture. It’s enterprise architecture. People benefit from the same representation. Developers benefit from it. Integration platforms benefit from it. Analytics platforms benefit from it. Partners benefit from it.

AI simply becomes another participant interacting with the enterprise through the same abstractions.  That’s why I don’t think the long-term challenge is making AI increasingly capable of understanding enterprise implementations.

I think the longer-term opportunity is making enterprises easier to understand.

We’ve spent decades improving how information is stored, integrated, governed, secured, analyzed, and distributed. Those investments have created significant value. But as enterprises have grown more complex, our understanding of them has become increasingly tied not only to systems and data structures, but to the many projects and solutions that have created their own representations of enterprise information, relationships, behaviors, and capabilities over time.

The next step is ensuring that we can represent the enterprise more consistently across those implementations, making its business meaning, relationships, behaviors, and capabilities explicit while abstracting unnecessary implementation complexity.

For many organizations, that will mean introducing technology capable of creating and operationalizing this simplified enterprise representation across existing systems, data, and applications without requiring the underlying implementations to be replaced. It may also mean changing how existing technologies are used and how projects are approached, so that consistent enterprise representations can be reused across initiatives and extended as the business evolves. That reuse can accelerate implementation, improve consistency, reduce risk, and provide a stronger foundation for governance and security instead of requiring these concerns to be rebuilt around each new solution.

If we can separate our understanding of the enterprise from the technologies and individual projects that implement it, we create a more adaptable foundation for AI and whatever comes next. As the business changes, its representation can evolve with it. But that evolution should be driven by changes in the enterprise, not by every change in the technology used to implement it.

The technologies will continue to change. The enterprise shouldn’t have to.