After 25 years’ experience of running an enterprise architecture (EA) consultancy and software business, it is surprising how often we hear this question posed by senior managers. Even when questioners accept the case for EA in theory, they are sceptical regarding its practicality.
Scepticism and negativity
There can be several reasons for these negative reactions. These include:
- Poor understanding of what EA involves and what benefits it can bring. (Not helped by experts having different interpretations of the term ‘enterprise architecture’.)
- The difficulty of making a compelling business case for the initial investment required to establish a viable EA support team.
- The long time required to deliver tangible business benefits. (Many of the available EA tools need considerable time and effort simply to establish a useful baseline).
- Poor experiences of EA within their organisation. For example, when EA practitioners have spent months (or even years in some cases) developing data models or cross-functional business process diagrams that were out of date and unusable by the time they were published.
- The EA function being seen to act as a blocker rather than an enabler: enforcing architecture rules and standards that have impeded or delayed change projects.
- Organisational politics proving to be a constant hindrance, as the corporate interest represented by EA is pushed into second place behind the demands of projects with powerful business sponsors.
The Challenge of EA
We have addressed many of these points in previous blog posts, but here is our New Year’s top-level take on this perennial problem. Let’s start with the scale of the challenge:
- As the term literally implies, Enterprise Architecture is concerned with the structure of business. This comprises not only organisational assets, which include the business capabilities, services and processes, as well as the people involved, but also the IT applications, the data stores and the technologies that underpin all of these.
- Most organisations are inherently complex. A salient feature of this complexity is the intricate network of connections between the various organisational and IT assets.
- Individual organisations are unique. Even those in the same line of business will have different strategic priorities, different approaches to the market, different cultural norms, and different historical legacies reflected in their ways of doing business, as well as in their IT assets.
- Management’s failure to appreciate the true complexity of an organisation’s business structure – also known as the business operating model – is a prime cause of difficulties, not only with internal change projects but also with major strategic business initiatives such as mergers, acquisitions, divestments or business process outsourcing deals.
Approaches to EA
Unfortunately, a one-off EA project aimed at capturing a large organisation’s entire business operating model in all its detailed complexity would be ‘Mission Impossible’. We believe that attempting such an approach will not only be counterproductive, it should be unnecessary. It is far better to begin with a rapid sweep across the organisation to capture the assets and their critical linkages at a high level of abstraction. This will provide the context and framework for what comes next.
Any business at a given point in time is likely to have pressing problems affecting a particular part of the organisation. Or perhaps the business plans to launch a major change programme that is cross-functional or that involves external partners or an acquisition target. These are the areas on which to focus: to dive down and record the essential details needed to provide management with reliable information and insights that will inform their decision-making. By proactively addressing the operating model issues in these areas of potential high risk, the work of the enterprise architects is likely to be seen as relevant and helpful. Having established their credibility in this way, the architects should then find it much easier to expand the scope of their work to cover more aspects of the business at a detailed level.
All of this assumes, of course, that the enterprise architects are properly equipped and ready to meet the current business challenges. If it takes them too long to capture the necessary information and present their analyses to management, they will miss the window of opportunity that will really help the business. (This is one of the main frustrations we see with EA listed by the sceptics above.)
Succeeding in EA
A lot of successful EA teams accelerate these processes by engaging people in the enterprise to help with capture of the information they need. That frees the enterprise architects to focus on the more demanding aspects: ensuring the reliability of the input, establishing the critical linkages between the assets, ensuring the integrity of the business operating model, and validating the accuracy and relevance of the management reports.
The only way to convince the sceptics will be to deliver tangible value from EA at the times the business needs it.