Key Steps for Effective Enterprise Architecture Programs

In the post Defining Enterprise Architecture: From Strategy to Engineered Systems, we defined Enterprise Architecture as the discipline of aligning business strategy with the design and implementation of computer systems. We’ll call this Alignment and Focus.

We’ve also established that there are three things we need to do: 

1. Translate Strategy into Technology Execution
2. Drive Architectural Alignment
3. Design Solutions

We’ll call that Things We Need to Do.

Alignment and Focus for Enterprise Architecture

In the post Creating the Structural Foundation for Enterprise Architecture we established Asset Management as the organizing structure and forcing function for effectuating Enterprise Architecture.

However, we did not take into consideration the different types of assets and their needs from an architectural oversight and governance standpoint. 

The Five Core Domains of Enterprise Architecture

There are typically five architectural domains that are important for Enterprise Architecture in large organizations:

• System
• Application
• Data
• Infrastructure
• Security

We’ll define and address each domain in future posts. The important thing to remember is that while the domains share commonalities, each also has unique concerns.

If you’re familiar with methods like TOGAF, you’ve probably noticed a few things missing from that list. I’ll address those in time.

But as we covered in the post Defining Enterprise Architecture Starts with Defining Architecture, keep in mind that our focus is on making computers do something, and effectiveness is ultimately determined at runtime.

How Enterprise Architecture Methods Are Structured

For each domain, we develop architecture methods. Those methods will break out across a hierarchical approach that follows a fairly conventional structure for Enterprise Architecture:

• Policies and Principles
• Rules
• Measures

Within that structure, we’ll address processes and methods, and show how standards and what I call “architecture blueprints” fit into the picture. The architecture blueprint series begins with the article Why Enterprise Architecture Requires a Baseline Blueprint.

The Three Core Functions of Enterprise Architecture

But, let’s go back to the three things we need to do…

You might assume that Translate Strategy into Technology Execution (the first task) should be the starting point. Usually it’s not—unless the organization is at such an early stage that upcoming changes will be tectonic, such as a major transformation initiative.

Or, as I covered in the post Creating the Structural Foundation for Enterprise Architecture, we may want to jump into the Design Solutions part (i.e., the third thing we listed). Please, no. Don’t do that. 

Architectural Alignment Comes First

Drive Architectural Alignment is where we want to be, and it will prove to be both impactful and powerful because it begins with policy integration.

We’ll cover that in the next post, Unstoppable Enterprise Architecture. 

Notes:
1. Headline image generated with Jetpack AI. Specific model unknown.