Skip to content
Software Architecture Guide

Enterprise Architecture Strategy

Explanation

Section titled “Explanation”

Business strategy does not stand still. Markets evolve, competitors act, and new technologies appear. An enterprise therefore cannot transform once and stop. It needs the ability to transform again and again.

An enterprise architecture strategy responds to this. It sets out how the organization approaches continuing change. Enterprise architecture (see “Enterprise Architecture”) done well works as a business transformation practice. The architect’s job is to connect things.

Starting point and direction

Practical guidance begins with mapping the current state. Next, the team defines what the architecture should look like in the future. The strategy covers the path between the two.

How architects steer

Architects guide the choices of others. They do not dictate them. They also measure change and communicate its value, so everyone understands why it matters.

Why it matters

Ross, Weill and Robertson argue that the enterprise architecture may matter far more for execution than the strategy itself. A strategy without a matching architecture is therefore a weak foundation. For related ideas, see “Enterprise Architecture (Ross/Weill/Robertson definition)” and “Foundation for Execution”.

Example

Section titled “Example”

A retailer sees customers moving to online ordering. The architects first map how ordering, stock and delivery work today. They then describe how these should work in the future. They share this picture with the teams that make the choices, and they track how each change affects the business. When the market shifts again, they update the picture and repeat.

Trade-offs

Section titled “Trade-offs”

The facts describe direction, not costs. One tension follows from them. Architects guide rather than dictate, so results depend on others understanding the value of each change. Measuring and communicating takes ongoing effort.

A continuing cycle of mapping, defining, guiding and measuring change.

Diagram source 
flowchart LR
  A[Map current state] --> B[Define desired future architecture]
  B --> C[Guide others' choices]
  C --> D[Measure change and communicate value]
  D -->|Markets or technology shift| A

Checks

Section titled “Checks”
  • The document records the current state of the architecture and the desired future architecture.
  • The document explains how change is measured and how its value is communicated to stakeholders.
  • The strategy treats transformation as ongoing, not as a one-off event.
Section titled “Related”

Sources

Section titled “Sources”