Jeanne Ross 01 08 2007 EA
Jeanne Ross 01 08 2007 EA
Jeanne Ross 01 08 2007 EA
Jeanne W. Ross
Center for Information Systems Research (CISR)
MIT Sloan School of Management
Phone: (617) 253-2348, Fax: (617) 253-4424
jross@mit.edu http://mitsloan.mit.edu/cisr/
This research was made possible by the support of CISR sponsors and patrons. The research
team included Peter Weill, David Robertson (IMD), George Westerman, Nils Fonstad, Lenny
Zeltser, Charles Zedlewski, Niraj Kumar (MIT), and Mingdi Xin (New York University).
Data
Business Solution
Applications
Strategy Lag Design Lag
Infrastructure
New idea
So we started working on understanding the business strategy, and what we discovered in
that process is, they really didn't have a business strategy. What they had were a lot of
promises. We are going to grow. We are going to use branding. We are going to run our
plants more effectively. We are going to increase our volume, but they hadn't figured out
exactly how they were going to do it. And what I said was: it is very difficult for me to write an
IT strategy to support your business strategy when you don't have that defined.
—IT Architect, Global Manufacturing Firm
Center for Information Systems Research Source: Architecture as Strategy: Creating a Foundation for Business Execution,
J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
© 2006 MIT Sloan CISR – Ross
The Result of Traditional Approaches
to IT-Business Alignment
Corporate Data
Data
Applications
Technology
Platforms
Center for Information Systems Research Source: Architecture as Strategy: Creating a Foundation for Business Execution,
J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
© 2006 MIT Sloan CISR – Ross
Two Key Concepts
Strategic
Strategic Strategic Strategic
Initiative
Initiative Initiative Initiative
Defines
strategic limits
Operating Model Establishes
Defines priorities
Learning
and integration & Enterprise Architecture
exploitation standardization
requirements
Defines
core
capabilities
Defines
strategic limits
Industrial Engineering From
Model reliability to
Learning accessibility
High degree of
and
integration &
Enterprise Architecture to agility
exploitation
standardization
across businesses Defines
core
capabilities
Redundant operations Single package database
Global communications network Standard interfaces
Standard infrastructure Customer information database
Product development process Customer relationship process
Center for Information Systems Research Source: Architecture as Strategy: Creating a Foundation for Business Execution,
J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
© 2006 MIT Sloan CISR – Ross
Washington, D.C.’s Foundation for Execution
Defines
strategic limits Projects
Benign Service Model focused on
stabilizing
Ideas on
ways to use Process customer
infrastructure standardization Enterprise Architecture services and
across programs; enabling inter-
services
agency
Integration within
and among programs Defines sharing
core
capabilities
Sounds of silence operations IT development standards
Wide area and wireless networks Data warehouse
Procurement processes Web portal
Human resource processes Geographic information system
Center for Information Systems Research Source: Architecture as Strategy: Creating a Foundation for Business Execution,
J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
© 2006 MIT Sloan CISR – Ross
Four Operating Models
Coordination Unification
Unique business units with a need Single business with global process
to know each other’s transactions standards and global data access
Business Process Integration
Low High
Business Process Standardization
Center for Information Systems Research Source: Enterprise Architecture as Strategy: Creating a Foundation for Business Execution,
J. Ross, P. Weill, and D. Robertson, Harvard Business School Press, June 2006.
© 2006 MIT Sloan CISR – Ross
Focus of Standardization Differs
by Operating Model
Unification
Business Process Integration
Center for Information Systems Research Source: Enterprise Architecture as Strategy: Creating a Foundation for Business Execution,
J. Ross, P. Weill, and D. Robertson, Harvard Business School Press, June 2006.
© 2006 MIT Sloan CISR – Ross
Delta Air Lines’ Enterprise Architecture
Operational Pipeline
Prepare Flight Flight Clean/
Allocate Load Monitor Unload
for Flight Departure Arrival and Service
Resources Aircraft Flight Aircraft
Departure and Closeout Closeout Aircraft
E
V
Gate E
Pagers Kiosks Hand
Readers N
T Helds
Voice S
Delta Nervous System
Video Electronic Events
Customer Experience
Center for Information Systems Research
© 2006 MIT Sloan CISR – Ross
Source: Adapted from Delta Air Lines documents – used with permission.
Enterprise Architecture for
Carlson’s Diversification Operating Model
Customer Requirements
Business Initiatives
Travel Management Loyalty Hotel Distribution CRM
Enterprise Portal
Presentation
Business Process
IT Resilience
Application
Security
Data Trust
Common Infrastructure
Middleware
Data Object
Platform
Network
Portal –
Security & Licensing Rates & Suitability
Forms &
Presentation Entitlements Calcs
Requirements
Integration
Customer Screen Entry
& Validation
Sign-on Marketing
Operational Business
Producer ACORD JLife
Navigation Illustrations Data Store Rules
Underwriter Service
Underwriting
ML
Claims
AC
Call Center
Product Admin
Partner
Service
Portals Events Service Workflow
Provider
Recording
Channel Services
IVR/CTI Imaging E-mail Web Gateway
server server server server server
Center for Information Systems Research Source: Robertson, D. “ING DIRECT: The IT Challenge (B)”, 2003, IMD-3-1345.
© 2006 MIT Sloan CISR – Ross Used with permission.
Architecture Maturity Stages Yield Increasing
Value from IT
Business Standardized Optimized Business
Silos Technology Core Modularity
Strategic
Business
Value
Standard
interfaces
and business
componentization
Enterprise-wide Standardized
technology enterprise
standards processes/data
Locally optimal
business
solutions
% of
12% 48% 34% 6% Firms
Center for Information Systems Research Source: Enterprise Architecture as Strategy: Creating a Foundation for
© 2006 MIT Sloan CISR – Ross Business Execution, J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
Architecture Maturity Shifts Flexibility
Business Standardized Optimized Business
Silos Technology Core Modularity
Global
Flexibility
Local
Flexibility
Center for Information Systems Research Source: Enterprise Architecture as Strategy: Creating a Foundation for
© 2006 MIT Sloan CISR – Ross Business Execution, J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
Implications of Architecture Maturity Stages
Strategic Implications of IT
Local/Functional IT Operational Strategic
Optimization Efficiency Efficiency Agility
100% Local
25% 16% 15%
Applications
36%
Percentage of IT Investment
Shared
40% 35% 33% Infrastructure
35%
Architecture Maturity
IT Budget 100% 85% 75% 120%
IT budgets from 103 firms are corrected for industry differences with Business silos as the
baseline Only five firms in stage four reported their IT budgets so data is not reliable.
Center for Information Systems Research
Source: Architecture as Strategy: Creating a Foundation for Business Execution,
© 2006 MIT Sloan CISR – Ross J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
Enterprise Architecture Benefits by Stages
5
4.5
3.5
3 IT Responsiveness (1)
CIO Rating
1.5
0.5
0
Business Standardized Optimized Business
Silos Technology Core Modularity
Architecture Stage (1) Development time.
(2) Business risk, security breaches and disaster tolerance.
(3) Senior management and business unit management satisfaction.
(4) Operational excellence, customer intimacy, product leadership and
strategic agility.
Center for Information Systems Research Source: Architecture as Strategy: Creating a Foundation for Business Execution,
© 2006 MIT Sloan CISR – Ross J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
Learning Requirements of the Architecture Stages
Stage Business Standardized Optimized Business
Name Silos Technology Core Modularity
IT Capability Local IT Shared technical Enterprise-wide Plug & play
applications platforms hardwired processes business process
or databases modules
Business ROI of local Reduced IT costs Cost and quality of Speed to market;
Objectives business business operations Strategic agility
initiatives
Funding Individual Shared infrastructure Enterprise Reusable business
Priorities applications services applications and data process
stores components
Key Technology- Design and update of Core enterprise Management of
Management enabled change standards; funding process definition and reusable business
Capability management shared services measurement processes
Who Defines Local business IT & business unit Senior management IT, business and
Applications leaders leaders and process leaders industry leaders
Key IT Measure and Establish local/ Align project priorities Define, source &
Governance communicate regional/global with architecture fund business
Issues value responsibilities objectives modules
Center for Information Systems Research Source: Architecture as Strategy: Creating a Foundation for Business Execution,
© 2006 MIT Sloan CISR – Ross J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
Management/Governance Practices to Formalize Learning
Business Standardized Optimized Business
Silos Technology Core Modularity
Business cases
Project methodology
Architects on project teams
IT Steering Committee
Architecture exception
process*
Formal compliance process*
Infrastructure renewal
process*
Centralized funding of
enterprise applications*
Centralized standards team
Process owners*
Enterprise architecture
guiding principles*
Business leadership of
project teams*
Senior executive oversight*
IT Program Managers*
Enterprise architecture
graphic*
Post-implementation
assessment*
Technology research and
adoption process*
Full-time Enterprise
Architecture team
Architecture Maturity
* Reported value of asterisked items is statistically significantly related to
architecture maturity stage.
Center for Information Systems Research
Source: Enterprise Architecture as Strategy: Creating a Foundation for Business Execution,
© 2006 MIT Sloan CISR – Ross J. Ross, P. Weill, D. Robertson, HBS Press, June 2006.
Architecture Lessons
From Top Performing Companies
Low strategic High strategic
effectiveness effectiveness
Characteristic (n=78 firms) (n=25 firms)
Senior management involvement
Senior management explicitly defined 25% (of firms) 44% (of firms)
architecture requirements
Senior management oversees architecture 45% (of firms) 60% (of firms)
initiatives
Percentage of senior managers who can 19% (of mgrs) 39% (of mgrs)
describe high level architecture
Architecture built into project methodology
Percentage of project teams with architects 49% (of projects) 81% (of projects)
assigned
Percentage of projects subjected to 60% (of projects) 80% (of projects)
architecture compliance review
* Statistically significant difference between the responses of top 25% of firms on strategic effectiveness. Strategic effectiveness is
measured as strategic outcomes (operational excellence, customer intimacy, product innovation, and strategic agility) of architecture
initiatives weighted by their relative importance to each firm. The top 25% of firms on strategic effectiveness reported significantly higher
profitability which correlated with industry adjusted measures of firm-wide profitability.