Enterprise Architecture as Strategy
Jeanne W. Ross, Peter Weill & David C. Robertson
ISBN-13: 978-1-59139-839-4 & ISBN-10: 1-59139-839-8
“Enterprise Architecture as Strategy” is subtitled “Creating a Foundation for Business Execution.” Sadly, this is not what the authors deliver. This book, from the Harvard Business School Press, starts with much promise but quickly disappoints after the first two chapters. Opening statements in chapter two set the stage for concern. The authors state that “IT executives work to align IT and IT-enabled business processes with stated business strategy.” This wrong-headed approach to IT planning has become the foundation for failed projects and an increasingly dysfunctional relationship between business and IT.
IT cannot align to business strategy. Business strategies are too abstract to serve as IT alignment targets and this approach creates a knowledge gap that IT creatively fills with the vivid imaginations of an army of business analysts. The correct approach is for the business to align business architecture to the business strategy and then have IT align the IT architecture to the target business architecture. While this concept is becoming increasingly accepted as a means of achieving business / IT alignment, the authors make no mention of business architecture. As a result, they have left a knowledge gap for executives attempting to use this book as a guide to architecture based strategic planning and deployment.
The most insightful and useful portions of the book come when the authors lay out four business operating models: Coordination, Diversification, Unification and Replication. I have had the opportunity to apply these concepts at client sites and have found that it opens up the eyes of executives when they consider their own enterprise in light of these basic operating models. In short, it helps executives understand that their organization is structured in a certain way and they must structure their planning accordingly.
A second useful aspect of the book comes when the authors share one-page diagrams that encapsulate portions of the business and IT architecture in a way that can be quickly explained to an executive. Sadly, the authors provide little insight into the process involved in creating these pictures, discuss little of the underlying metadata required to support creation of these views and muddle the concepts of business and IT architecture as a result.
Consider for example, Figure 3-5 on page 59 showing the MetLife core diagram. While helpful for viewing the customer / screen / application / data relationships, it is essentially an IT-centric view of the enterprise and sidesteps a more business centric schematic that should include capability, value chain and process based views of the business. The risk in such a diagram is that it creates a perception that IT is the only aspect of the business that requires analysis and alignment.
In addition, the authors entirely omitted MetLife’s leading edge work in business architecture. MetLife shared its experiences and successes in business architecture and enterprise architecture on Nov. 2008 in New York. The MetLife presentation provided a clear view of the importance of business architecture within the context of enterprise architecture.
In stark contrast to MetLife’s views on business and enterprise architecture (and those of numerous other leading organizations), the authors define enterprise architecture (page 47) as “the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the company’s operating model.”
In this definition, the authors omitted the concept of business architecture and filled the void with business processes. The danger here is that it communicates a view that the only business aspect to enterprise architecture is the business process, which the OMG Business Architecture Working Group, Business Architecture Institute and even Wikipedia refute. Business executives reading this book will be led to believe that IT-enabled business processes and IT architecture are all that are required to deploy a successful business strategy. Industry best practices, including work being done by MetLife – a company cited by the authors, show this position to be patently wrong.
As far as the rest of the book is concerned, it quickly moves beyond the business realm into a discussion of IT architecture. The emphasis on IT is highlighted most dramatically beginning on page 92 where the authors list the first benefit of enterprise architecture as “reduced IT costs”. First, IT spending is a small percentage of overall spending and therefore not the ideal source of funding cuts. In addition, if IT funds are being spent to retain or attract customers, streamline the ability of a business to bring a new products or services to market, or control operational business costs, then reducing IT spending could have a negative effect on the business.
The focus on reducing IT costs as the number one benefit of enterprise architecture casts suspicion on the validity of this book as a guide to “creating a foundation for business execution” as the authors have labeled this publication. Given that the authors cast the CIO as the key driver of enterprise architecture (which presumably includes business architecture) it should not come as a shock that they focus their benefits discussion on IT value and not on business value.
Executives reading this book should use it sparingly and judiciously. While the four operating models can be useful as input to enterprise planning, do not assume that you can jump from business strategy to IT deployment. The track record of failure of this approach is all too clear. In addition, consider crafting simple views of the integrated business / IT architecture for executive planning purposes, but be sure to create the supporting business architecture / IT architecture metadata and related mappings needed to validate these views and to drill down to subsequent levels of detail.
Finally, this book as with most books should not be considered a business or IT planning bible, but rather just another book where executives can pluck one or two good ideas out to be added to their arsenal of useful concepts. In this case, pluck out the operating model concepts presented early in the book and then move on.
One From Many: Visa and the Rise of the Chaordic Organization
[Updated Review - August 2009]
Since my initial review of Dee Hock’s excellent book, I have had to opportunity to further test his ideas within the context of numerous business engagements. The organizing principles Dee Hock put forth in his book have served to create a foundation for establishing parallel organizational structures that can function within an enterprise. For example, TELUS Communications created a Quick Win team function that uses “Chaordic” principles to function within the context of the corporate hierarchy. Other organizations are applying Dee’s concepts as well to align with business partners to deliver a common set of products and services.
In addition, Dee’s work has taken on significant value in the practice of business architecture. The organizational representations that map to business capabilities, processes, customers, products, initiatives and other aspects of the business are best represented in the social networking diagrams. In addition, the focus on purpose and principles have provided a strong foundation for establishing collaborative teams within and across enterprises and this includes business architecture centers of excellence.
Dee’s work continues to resonate within the business community. While originally envisioned as a vehicle for aligning disparate organizations to organize around a common purpose to address major industry and social challenges, Dee’s work has been successfully adapted to provide real value within major enterprises. Any executive seeking collaborative solutions to major challenges would be well advised to read this book.
Dee Hock, Founder and CEO Emeritus of Visa, not only recalls the intriguing events that led to the creation of Visa, but shares the roots of his personal journey that took him to that place and time. This book chronicles Hock's exploration of the nature of organizations that go well beyond anything that had been done to that point in time. As a byproduct, he helped save a credit card industry that was bleeding money across a sea of large and small financial institutions. The reviews inside the book and on the cover, along with a Forward by Peter Senge, ring praises upon Hock for sharing this riveting story.
ISBN 0 14 00.9250 1
Chaos is a basic theme in nature, science and in organizations. Chaos, where order can be found in what appears to be random behavior, has tremendous implications on how we create and leverage organizations. If you want some excellent background reading on where Dee Hock is coming from in the Birth of the Chaordic Age, check out this book. Or if you just want to get a better understanding of the world in which we live, understanding chaos is a great start.
Adaptive Software Development: A Collaborative Approach to Managing Complex Systems
James A. Highsmith III
Highsmith applies Chaordic organizational disciplines to large-scale projects. He breaks away from the notion that a project can be neatly broken into little pieces, organized like a puzzle and laid out in a neat and predictable manner. Rather than the traditional task-driven thinking that has permeated project management for too long, Highsmith focuses on results-driven concepts. The book discusses collaboration and adaptability as overriding factors in managing complex projects. If you are deploying an e-business strategy across your enterprise, or tackling any other type of large, complex project challenge, this book is strongly recommended reading.
M. Mitchell Waldrop
ISBN 0 671 87234 6
Self-organizing systems are all around us. Whether you are talking about a hurricane, a pot of soup, the economy or an organizational infrastructure. Lessons from Complexity can be applied broadly, particularly when brought back into the realm of organizational structures. One important aspect of this is that self-organizing systems are more adaptive. Ever wonder why corporate hierarchies segregate people rather than encourage collaboration, or why they hinder rather than enable communication, or why they break before they adapt? Self-organization and other fascinating insights into a variety of disciplines provides the reader with, as Waldrop puts it, a "vision of the whole".
A visual ride through the world of fractals . Briggs brings together nature, math, science and art to show us what chaos looks like from many perspectives. My interest here continues along the lines of how organizations really look like fractals if you expose their true nature and do not try to pretend that they are really hierarchies. You will enjoy this one and can even put it out on your coffee table.
Barbara Benedict Bunker, Billie T. Alban
This book provides good insights into managing organizational change. Any executive team that thinks they can lock themselves up, build a new organizational hierarchy and then implement it from the top down should read this book. Of course those executives that do the most damage are likely to be the least likely to think they need advice on this topic. Bunker and Alban explore many ideas regarding topics such as participative design: a key element in building new organizations.
Doc Childre & Bruce Cryer
Most our reviews address the challenges of dealing with the complexities of moving enterprises further into the information age. From Chaos to Coherence addresses the human side of the equation. Childre and Cryer are from the Heartmath Institute and offer proven techniques for organizations undergoing radical changes in chaotic times. They offer tools to deal with real-time changes in companies and across industries. They also offer scientific underpinnings for their work something the Heartmath people have been doing for a long time.