Professional Documents
Culture Documents
RESEARCH BRIEFING
Volume V Number 2B July 2005 (revised Feb. 2006)
OF ENTERPRISE ARCHITECTURE
Cleaning up IT infrastructure, shared data and
enterprise applications provides a more manageable IT
Jeanne W. Ross, Principle Research Scientist environment. Manageability contributes to at least four
Peter Weill, Director risk-related benefits:
MIT Center for Information Systems Research Reduced business risk: the extent to which systems
are consistently and reliably up and running as
An enterprise architecture provides the organizing needed to support the business.
logic for business processes and information tech- Improved regulatory compliance: accessibility of
nology. Enterprise architecture defines a firm’s desired accurate data to respond to government require-
levels of integration and standardization. As firms ments.
build out their enterprise architecture, they should Increased disaster tolerance: the ease and speed
realize a number of technology and business related with which backup and recovery services are ren-
benefits. Based on a survey of 100 firms, this briefing dered to minimize business losses.
describes enterprise architecture benefits and how
firms attained those benefits incrementally as they Reduced security breaches: avoidance of computer
matured their business process and IT capabilities. viruses and inappropriate access (both internal and
external) to private or confidential data.
Technology-Related Enterprise
Architecture Benefits Business-Related Enterprise Architecture Benefits
Enterprise architecture forces discipline and stan- Partly as a result of the technology-related benefits and
dardization in the management and use of technology. partly as a result of more disciplined and standardized
Discipline and standardization, in turn, lead to three business processes, firms also generate business
types of technology-related benefits: benefits as a result of their enterprise architecture
efforts. These benefits are as follows:
IT Costs
Shared Business Platforms
As management eliminates non-value-adding varia-
tions in technologies and relies on a set of relatively Data and process standardization when combined with
stable technical competencies, a firm can reduce two integrating technologies generate two valuable out-
kinds of IT costs: comes:
IT operations unit costs: the actual cost of services greater data sharing: accessibility of data to internal
such as laptop provision and support, help desk, and external persons who do not capture data
application support, access to enterprise data, initially but have a need to know.
network capacity and email. Use of these services integrated process standards: reliability and predict-
grows over time, but the unit costs should decrease. ability of IT-enabled business processes across
Applications maintenance costs: the time and total locations and business units.
cost for making changes to existing applications to Managerial Satisfaction
reflect business and technology changes. Satisfaction is a subjective measure, but it is important
IT Responsiveness for generating enterprise-wide commitment to
In a standardized environment, IT and business leaders architectural improvements and the organizational
have fewer technology choices and thus spend less time changes those improvements enable. Satisfaction
making technology decisions or addressing unexpected captures the confidence of non-IT executives in the
technical problems. The result is reduced development ability of the IT unit to deliver business value:
time, including both the elapsed time and total Senior management satisfaction with IT reflects
development hours required to implement a new system. reactions of corporate leaders.
© 2005 MIT Sloan CISR, Ross & Weill. CISR Research Briefings are published three times per year to update CISR patrons,
sponsors & other supporters on current CISR research projects.
CISR Research Briefing, Vol. V, No. 2B Page 2 July 2005
Business unit leader satisfaction with IT reflects time. Managerial satisfaction also takes a steep climb,
attitudes of managers to the impact of IT on local testimony to the lower cost, improved business plat-
business results (e.g., costs, business value, service forms, and related business impacts. But while busi-
levels, reliability). ness and IT outcomes are higher in the second stage
than the first, they are still generally low (under 3 on a
Strategic Business Impacts
scale of 0–5). These low ratings are an indication that,
The enterprise architecture targets business needs, for most companies, Stage 2 is an important but early
which vary by company, but enable four important step on the journey toward a foundation for execution.
strategic outcomes.1
Operational excellence: low cost provider, empha- Benefits from Stage 3 (Optimized Core)
sizing efficient, reliable and predictable operations. Managers’ ratings of architecture benefits in the third
Customer intimacy: extraordinary customer service, stage are all higher than in Stage 2. The biggest
responsiveness, and relationships, based on deep differences between Stages 2 and 3 are the ratings on
customer knowledge. standard business platform and managerial satisfaction.
These results are not surprising, since the third stage
Product leadership: first to market with innovative
emphasizes development of shared process and data
products and services, usually dependent on rapid R&D
platforms. The large increase in IT executives’ ratings
to commercialization processes (e.g., market leader).
on data sharing and process standardization indicate
Strategic agility: the ability to respond rapidly to that the objectives of Stage 3 are generally realized.
competitor initiatives and new market opportunities. The improved satisfaction ratings are a result of having
At most companies, concerns about IT costs drive the a standardized business platform with lower costs and
initial interest in enterprise architecture, but we found more consistent quality. Both senior management and
that as companies mature their enterprise architectures, business unit management satisfaction ratings
they are remarkably successful in generating all six increased over 25% from Stage 2 to Stage 3.
benefits described above. In earlier research we
The increase in ratings on risk management, IT
described four stages of architecture maturity: business
development time and strategic business impacts are
silos, standardized technology, optimized core, and
relatively small, probably because enterprise archi-
business modularity (see Table 1 for definitions).2
tecture initiatives in Stage 3 demand large-scale busi-
Figure 1 shows the technical and business related
ness changes and those changes can be slow—and
benefits at each maturity stage.
risky—to implement. Stage 3 involves major new
enterprise-wide systems implementations and trans-
Growing Benefits Through Architecture Maturity
formational change. Thus the average rating on risk
IT executives give low ratings on all six benefits for management is still under 3 (on a 0–5 scale). Develop-
Stage 1 (business silo) architectures (typically lower ment time has a rating of 2.7—most likely because
than 2 on a scale of 0–5, i.e., not achieved to fully enterprise projects in this stage are large and both IT
achieved), a clear reflection of the impacts from and business expertise on the systems are limited.
ignoring enterprise needs when creating solutions to Strategic impacts received a similar rating, perhaps
local business needs. Over time the accumulation of because strategic benefits do not accrue until late in
local solutions becomes expensive and hinders new Stage 3, when new capabilities are in place and
business initiatives, particularly those that cross silos. management has learned how to leverage them. While
But, as the graphs show, firms achieve increasing the challenges to moving to Stage 3 are compelling,
benefits as they mature their architectures. our findings suggest that companies are securing
expected benefits. Managers at companies like Dow
Benefits from Stage 2 (Standardized Technology) Corning and MeadWestvaco, for example, have noted
Managers’ ratings increased by at least 25% from that major enterprise systems cause significant
Stage 1 to Stage 2 on all the metrics. The biggest discomfort before they start delivering measurable
increase in executives’ ratings is on IT development business and IT benefits.
1
The first three strategic impacts refer to the disciplines Stage 4 (Business Modularity) Benefits
described by M. Treacy and F. Wiersema in The Discipline of
Market Leaders, Perseus Press, 1995. We have added strategic
The cost improvements in IT level out by Stage 4,
agility because of its growing importance to companies. possibly because few firms have reached this stage,
2
See Ross, J.W., Creating a Strategic IT Architecture Compe-
and implementing process modules with standard
tency: Learning in Stages, MIT Sloan CISR Working Paper No. interfaces may introduce some initial learning costs.
335, April 2003 or Ross, J.W., Maturity Matters: How Firms The payback is much more evident in the strategic
Generate Value from Enterprise Architecture, MIT Sloan CISR impact of enterprise architecture initiatives. Overall,
Research Briefing, Vol. IV, No. 2B, July 2004. executives rated strategic business impacts (operational
CISR Research Briefing, Vol. V, No. 2B Page 3 July 2005
excellence, customer intimacy, product leadership and is that companies can be very selective about what they
strategic agility) 40% higher in Stage 4 than Stage 3. standardize when they have adopted business
These benefits come from having a set of well modularity. Stage 3 can force some uncomfortable
engineered business modules providing a platform for uniformity (e.g., an ERP forces process standards
execution and agility at a more granular level than that globally that, in some cases, may not represent a good
for Stage 3. For example, Citibank Asia created a fit). A benefit of Stage 4 is that it allows selective
credit card processing module that reduced processing standardization by module instead of larger-scale
costs by more than 50% and then reused this module to business processes. On the downside, carelessness in
quickly enter new markets in Asia and Eastern Europe. Stage 4 can lead to a loss of discipline—some things
that ought to be globally standardized won’t be.
Improvements in strategic business outcomes are
generated, in part, by faster IT development time
Building a Case for Enterprise Architecture
(average rating up 37% over Stage 3). Whereas the
third stage involved large-scale projects, Stage 4 Enterprise architecture initiatives can involve dis-
involves reusing or customizing smaller modules. mantling legacy systems or redesigning business
Faster development time should be a key benefit of processes. The benefits of such efforts can be elusive.
achieving Stage 4 architecture maturity based on Our research suggests that firms should establish
reusable modules. baseline measures for each of six benefit categories so
they can monitor the value of their enterprise
Risk management and managerial satisfaction ratings architecture initiatives. Our findings show that an
increase slightly from Stage 3 to Stage 4. However, the effective enterprise architecture typically leads to lower
standard platform rating drops significantly. The lower IT costs, more senior management satisfaction and
standard platform rating reflects both a potential ultimately improved business performance.
benefit and a potential risk of Stage 4. The good news
4.5 4.5
4 4
3.5 3.5
CIO Rating
CIO Rating
3 3
2.5 2.5
2 2
1.5 1.5
Cost Impacts (1) Shared Business Platforms (1)
1 1
IT Responsiveness (2) Managerial Satisfaction (2)
0 0
Business Silos Standardized Optimized Business Business Silos Standarized Optimized Business
Technology Core Modularity Technology Core Modularity
Architecture Stage Architecture Stage
(1) Unit operating costs and application maintenance cost. (1) Data and process standardization.
(2) Development time. (2) Senior management and business unit management satisfaction.
(3) Business risk, security breaches and disaster tolerance. (3) Operational excellence, customer intimacy,
product leadership and strategic agility.
About the MIT Sloan Center for Information Systems Research