Defining Enterprise Architecture: From Strategy to Engineered Systems

I recently reread a book on a popular Enterprise Architecture framework. I hadn’t finished it the first time because it read like watching a bad movie, in that you either leave or suffer through it, thinking it might get better.

But this time I was determined to read it, and I had chosen the worse option.

The Missing Link: Implementation and System Engineering

I’m always trying to figure out how things contribute to a computer doing something. That includes “things” called Enterprise Architecture. 

So why was this book about Enterprise Architecture so bad?

Well, in terms of practicality, the word “implementation” didn’t appear until nearly the end. It was then followed by a brief mention of “system engineering” on one of the very last pages.

I should also mention that this book was actually a study guide.

So, if a comprehensive study guide for the framework doesn’t say much about implementation and system engineering, then I guess that’s just not what the framework is about.

Enterprise Architecture Must Lead to Running Systems

In the post, Understanding Architecture: Key Definitions, I made a distinction when defining Architecture, saying that its “effectiveness will be determined at runtime,” which hopefully caught your attention. 

But in this example—a book about Enterprise Architecture—it’s as though building and running computer systems is just an inconvenient distraction; it’s certainly not a focal point of the architecture framework.

Defining the Value of Enterprise Architecture

Enterprise Architecture should be about adding value. Yet many approaches are abstract, conceptual, and disconnected from the overall design of computer systems.

The Four Areas of Enterprise Architecture

In my view, Enterprise Architecture encompasses four areas: strategy, architecture, design, and implementation (i.e., making a computer do something). (The id est is for all four.)

But all roads must ultimately lead to production systems and their management over time. That is, after all, what a technology function is there for in large organizations.

What Enterprise Architecture Actually Does

In Enterprise Architecture, we influence those four areas by developing a structured approach for doing three things:

1. Translating strategy into technology execution.
2. Integrating policies from across the organization.
3. Designing solutions.

A Clear and Practical Definition of Enterprise Architecture

So, let’s build from the definition of Architecture and define Enterprise Architecture with the same emphasis on simplicity and focus:

Enterprise Architecture is the discipline of aligning business strategy with the overall design and implementation of computer systems. 

From Definition to Measurable Results

Now we’ll work from that definition to define a methodology that positions us for actionable and measurable results with Enterprise Architecture.

And, yes, I did just say measurable results for Enterprise Architecture.

Notes:
1. Headline image generated by Google’s Gemini 2.5 Flash (also known as “Nano Banana”). That name either conveys coolness or stupidity. But after trying it out, I’m going with the latter.