The Future of
Enterprise Architecture
- Towards the Coherent Enterprise
John Gøtze
In the Beginning ...
Imagine an enterprise that had not heard of EA.
 It is operational (sort of)
 It produces and uses information (there are artefacts)
 No enterprise wide coherence (at best accidental coherence)
Business
EA Not applied
IT
Existing
Enterprise
Information Indecision

Too much information
Too much complexity
Too many challenges
Too little time

Business Intelligence vs. Intelligent Business



Conditions
• The Constancy of Change
– Lewis Caroll’s Red Queen: "in this place it takes all the
running you can do, to keep in the same place.”
• Neurath's Boat
– ”We are like sailors who on the open sea must reconstruct
their ship but are never able to start afresh from the
bottom.”
Disruption
Alignment
= 0
”Remember Your Vector Math!”
Agility
Assurance
EA = ?

Everything Aligned

Enabled Agility

Embedded Assurance

...
10
Occam's Razor
"All other things being equal,
the simplest solution is the
best."
Ross, Weill & Robertson:
“Enterprise Architecture as Strategy”
Five elements

Strategic Initiatives

Operating Model

Enterprise Architecture

Engagement Model

Foundation for execution

The IT infrastructure and digitized
business processes automating a
company’s core capabilities.
Operating Model
Operating Model

Single point of
contact

Begins with
customers

Economies of
scale

Begins with
shared
services

Synergy and
Responsiveness

Begins with
processes,
customers and
shared
services

Scalability

Begins with
processes
N=1 & R=G
Geoffrey Moore's Cycle of Innovation
Core
Context
Mission Critical
Deploy
II
III
I
IV
Manage
Non-Mission-Critical
Invent
Offload
Fund next innovation
Strategy
Technology
Business
25
Foundation Architecture
EA 1.0
Use of EA to ensure Alignment of Business & IT
 Capture Understanding of Business
 Target: Systems Architecture and Design
 Valuable and the most practiced form of EA
Understand
the Business
Business
Captured and Designed
Captured
Not applied
IT
Existing
Enterprise
EA
Addition
Design
Systems
”Complete” EA Approach

A “complete” EA approach must have all of these elements, which are
specifically designed to work together in the context of the (IT)
governance process.
EA
Methodology
EA
Best Practices
EA
Framework
EA Tools &
Repository
Carnegie Mellon University
(IT)
Governance
EA
Artifacts
Technology – Business – Strategy
Security / Standards / Workforce
Scott Bernard's EA3 Cube
Lines of Business
Network
Infrastructure
Network
Infrastructure
Goals &
Network
Initiatives
Infrastructure
Network
Infrastructure
Products &
Network
Services
Infrastructure
Network
Infrastructure
Data &
Network
Information
Infrastructure
Network
Infrastructure
Systems &
Network
Applications
Infrastructure
Network
Infrastructure
Networks &
Infrastructure
C
O
M
P
O
N
E
N
T
S
Scott Bernard's EA3 Cube
–
–
–
•
Strategic Plan
Future Operating Scenarios
Balanced Scorecard ™ Goals and Measures
Business Level
–
–
–
–
–
•
Business Plan (E - Commerce Plan / E - Government Plan)
Business Requirements Use Cases
Business Case – Investment Portfolio
Business Process Management Applications
Business Process Reengineering / Improvement
EA
Methodology
Technology Level
–
–
–
–
–
–
Service Oriented Architecture
Object - Oriented Data Modeling/Application Development
Network - Centric Systems Engineering
Enterprise Resource Planning Systems
Network Management Applications
Security Architecture
EA
Best Practices
EA Management Plan
Future
Future EA
EA Views
Views
EA Standards
EA Program
EA Tutorial
Site Map
Networks &
Infrastructure
Security
Solutions
Technology – Business - Strategy
S
+
B
+
T
Strategic Level
Security, Standards, Workforce
•
Lines of Business
Network
Infrastructure
Network
Infrastructure
Goals &
Network
Initiatives
Infrastructure
Network
Infrastructure
Products &
Network
Services
Infrastructure
Network
Infrastructure
Data &
Network
Information
Infrastructure
Network
Infrastructure
Systems &
Network
Applications
Infrastructure
Network
Infrastructure
Networks &
Infrastructure
Enterprise Architecture Repository
Goals
& Initiatives
Products
& Services
Data &
Information
Systems &
Applications
High
Level
View
Strategic
Plan
Business
Plan
Knowledge
Warehouse
Business
Systems
Wide Area
Network
Security
Program
Mid
Level
View
Goals &
Initiatives
Business
Processes
Information
Flows
Support
Support
Systems
Local Area
Network
System
Certifications
Detailed
View
Performance
Measures
Investment
Portfolio
Data
Dictionary
Application
Inventory
Buildings
& Equipment
Data
Privacy
Current EA
Views
EA Tools &
Repository
C
O
M
P
O
N
E
N
T
S
EA
Artifacts
Foundation Architecture
- Provides Excellent Value
- Some implementations are simply IT
Architecture at the Enterprise Level
- In some cases this is all you need for a
particular investment.
Saint- Exupéry
FEA Practice Guide, OMB 2006.
http://www.whitehouse.gov/omb/egov/documents/FEA_Practice_Guidance.pdf
EA Transition Planning
LinesNetwork
of Business
Infrastructure
Network
Infrastructure
Goals &
Network
Initiatives
Infrastructure
Network
Infrastructure
Products &
Network
Services
Infrastructure
Network
Infrastructure
Data &
Network
Information
Infrastructure
Network
Infrastructure
Systems &
Network
Applications
Infrastructure
Network
Infrastructure
Networks &
Infrastructure
Current Architecture
LinesNetwork
of Business
C
O
M
P
O
N
E
N
T
S
EA
Management
Plan
Security, Standards, Workforce

An enterprise architecture is in continual transition as implementation and
upgrade projects are completed.
Needs coordination, prioritization, and oversight. ”We need a plan”.
Security, Standards, Workforce

Infrastructure
Network
Infrastructure
Goals &
Network
Initiatives
Infrastructure
Network
Infrastructure
Products &
Network
Services
Infrastructure
Network
Infrastructure
Data &
Network
Information
Infrastructure
Network
Infrastructure
Systems &
Network
Applications
Infrastructure
Network
Infrastructure
Networks &
Infrastructure
Future Architecture
C
O
M
P
O
N
E
N
T
S
Forward-Looking Architecture
One of the purposes of an EA program is to develop future
views of the architecture
Infrastructure
Network
Infrastructure
Goals &
Network
Initiatives
Infrastructure
Network
Infrastructure
Products &
Network
Services
Infrastructure
Network
Infrastructure
Data &
Network
Information
Infrastructure
Network
Infrastructure
Systems &
Network
Applications
Infrastructure
Network
Infrastructure
Networks &
Infrastructure
Current Architecture
LinesNetwork
of Business
C
O
M
P
O
N
E
N
T
S
EA
Management
Plan
Security, Standards, Workforce
LinesNetwork
of Business
Security, Standards, Workforce

Infrastructure
Network
Infrastructure
Goals &
Network
Initiatives
Infrastructure
Network
Infrastructure
Products &
Network
Services
Infrastructure
Network
Infrastructure
Data &
Network
Information
Infrastructure
Network
Infrastructure
Systems &
Network
Applications
Infrastructure
Network
Infrastructure
Networks &
Infrastructure
Future Architecture
C
O
M
P
O
N
E
N
T
S
EA is (like) Urban Planning




Many stakeholders
Many layers
Big projects
 Money
 Time
 Extent
A “discipline”
 Science
 Practice
Enterprise Architecture 2.0






Approaches can scale from local to global.
CEO wants to own and use the architecture.
Integrates Strategic, Business, and
Technology Planning.
Moving from Documentation to Analysis, to
Design -- supported by better tools/artifacts.
More standards on terms and methods from
international and national bodies.
More case studies of good and bad EA in the
public and private sector.
39
EA 2.0
Extended Architecture
Non-IT use of EA
 Support Coherence Generally (e.g. Policy Alignment)
 Enables ‘Enterprise Engineering’
 Less practiced form but arguably more valuable than foundation
Design
Business
Captured and Designed
Business
Captured
Not applied
IT
Existing
Enterprise
EA
Addition
Design
Systems
Extended Architecture
 Traditional Business Architecture:
 Capturing business requirements to build
systems
 Results in solutions aligned to business
 New Business Architecture:
 Design the business to achieve desired
business outcomes
 Results in business aligned to purpose
Think business “Purpose”
not just business “Process”
EA 3.0
Embedded Architecture
The use of EA by non-IT and IT in normal
processes.
 Architecture is already there, so an enterprise’s architecture should NOT be
developed as a project. It should be leveraged.
 Find these key descriptive processes, apply EA structure to those artefacts
and enable alignment.
Align Those Doing
Business Design
Business
Captured and Designed
Captured
Structured
IT
Existing
Enterprise
EA
Addition
Align Those Doing IT
Design
Embedded Architecture
Implications
 EA becomes the task of the CxO Leaders
 Alignment Support is the Chief Architect’s Responsibility
 'Built-Out' effort gets reduced because we get to reuse 'Built-In' artefacts.
Example:
When starting transformation of a policy center because of new political direction
we would:
Previously – Begin the process of properly capturing the “As Is”.
Now – We simply get the “As Is” from the artefacts updated through regular
process (e.g. Annual Plans, Budgets…).
Motto: Find It, Structure It, and Align It
Balanced EA
• Ubiquitous, embedded architecture
– ”Way of Life”
• Living architecture, ever-green
• Solid foundation
• Strategic alignment
• Alignment, Agility AND Assurance
• Coherent enterprise
Gary Hamel
• Management innovation
• Our enterprises have '21stcentury, Internet-enabled
business processes, mid20th-century management
processes, all built atop
19th-century management
principles'
• Management 2.0
• New Management DNA
May 2008
Alignment of Business & IT
Foundation Architecture
Understand
the
Business
Business
Captured
IT
EA
Existing
Enterprise Addition
Design
Systems
Not applied
Captured and Designed
50
Extended Architecture
Non-IT use of EA
Design
Business
Captured and Designed
Business
Captured
Not applied
IT
EA
Existing
Enterprise Addition
Design
Systems
51
Embedded Architecture
The use of EA by non-IT and IT in normal processes
Align Those Doing
Business Design
Business
Captured and Designed
Captured
Structured
IT
Existing
Enterprise
EA
Addition
Align Those Doing
IT Design
52
Coherency Management
- Architecting the Enterprise for
Alignment, Agility, and Assurance
Doucet, Gøtze, Saha, Bernard (forthcoming)
www.coherencymanagement.org
Technology – Business – Strategy
Security / Standards / Workforce
Lines of Business
Network
Infrastructure
Network
Infrastructure
Goals &
Network
Initiatives
Infrastructure
Network
Infrastructure
Products &
Network
Services
Infrastructure
Network
Infrastructure
Data &
Network
Information
Infrastructure
Network
Infrastructure
Systems &
Network
Applications
Infrastructure
Network
Infrastructure
Networks &
Infrastructure
C
O
M
P
O
N
E
N
T
S
Design
Leadership & facilitation
EA
Assessment
Any investment or Whole enterprise
Observers – Stakeholders – Partners
Coherent View
Continuous Coherency Improvement
DESIGN
Leadership/Facilitation
Improve
Designs &
Descriptions
ENTERPRISE
ADVICE
New Rules
Methods, Models
Designs
DESIGNERSDESCRIBERS
Planners
Policy Writers
Operations:
HR, FM, TM, IM
•Structures
•Patterns
•Frameworks Improve
•Designs
Functioning
ARCHITECTUR
E
ASSESSMENT
Any Investment or Whole Enterprise
Enterprise Description
Designs (Business & Tech)
Plans (Project, Annual…)
Reports, Org Charts, Job
Descriptions, Précis,
Process Maps
etc
Enterprise
ADVICE
Gaps / Overlaps
From Strategy
to Operations
DECIDERS
Owners
Executives
Managers
Staff
Resources
People, Money, Information,
Technology, Property, Assets…
Operational Enterprise
The three aspects of coherency
Coherent Rules for Descriptions
 Coherent Descriptions
 Coherent Enterprise

Coherent Enterprise




When the enterprise experiences coherent operation and
execution.
Alignment is very mature because the rules allow
descriptions to be compared for alignment and adjusted
accordingly.
Agility is achieved because the designs are coherent,
which includes a developed understanding and practice
of loose coupling by design instead of tight coupling by
accident.
Assurance is gained through an ability to not only have
all the information but also, through coherency, have the
information provide real knowledge.
Contact
John Gøtze
http://gotze.eu
john@gotzespace.dk