Where should an Enterprise Architecture Team sit within an Organisation?
Since the vast majority of enterprise architects report ultimately to their organisation’s Chief Information Officer (CIO) or to someone with an equivalent title, this may seem a rather odd question. But as enterprise architecture in its broadest sense is concerned with the operating model of a business, some people consider that its rightful organisational home should be at a higher level: providing direct support to the Chief Operating Officer (COO).
There are perfectly good reasons why the EA function typically sits within an organisation’s IT department. Modern enterprises rely on sophisticated information systems and internet-based external sources of information to an extent seen only in the realms of science fiction not so long ago. (The widespread adoption of artificial intelligence agents is the latest manifestation of this trend.) The challenges of marshalling these resources and of using them effectively require knowledge, skills and disciplines that naturally reside within the IT function. Also, an obvious precondition of the IT function’s success is having access to reliable information about the current IT estate: the applications, data and technologies that support the existing business.
Given this background it is hardly surprising that in most businesses EA investments tend to focus primarily on recording the IT landscape and producing reports on the IT assets for CIOs and their line managers. Our experience has indeed shown that rationalising the applications portfolio and simplifying the technology base are common priorities for an EA function. Unsurprisingly, these IT efficiency projects with their tangible benefits directly address the CIO’s personal objectives of managing the IT estate and budget. The downside, however, is that where resources are limited, EA initiatives aimed at serving the wider interests of the business can easily be squeezed out.
The EA Function needs to provide operational intelligence to serve the COO’s Agenda
Serving the wider business agenda is the area where the COO needs support from the EA function in terms of operational intelligence. Consider, for example, the handling of mergers, acquisitions and divestments, or of business process outsourcing contracts. Many of these megadeals fail to meet expectations in terms of budget, timescale and difficulty, and their failure is frequently down to poor appreciation of the operating model issues: in short, the applications architecture. The scale of costs, risks and benefits involved in these major business change programmes can make those worthy IT efficiency projects pale into insignificance.
Splitting the EA Function is not an easy Solution
A recent post on LinkedIn has described one organisation’s radical way of solving this problem. The company had split the EA function into two separate groups: one dealing with the IT agenda and the other focused on the business. The first group reported to the CIO, while the latter group, staffed primarily with business architects, reported to the COO. While this solution certainly addresses the prioritisation issue – ensuring that the wider business is not deprived of EA resources, it does have a fundamental flaw. A true enterprise architecture encompasses all the organisational assets from top-level business capabilities, through business services and processes, then their dependent IT applications and the related data, and finally down to the technologies that underpin all this. Dividing the EA responsibilities in the way described could lead to confusion at the points where the two groups’ activities need to intermesh. The obvious solution is to add another organisational layer to oversee and coordinate the work of the two parties. But apart from the additional administrative costs, who would want to take on this demanding and potentially stressful role, and to whom should the coordinator report: the CIO or the COO?
The best Home for EA may remain with the IT Function, but the CIO needs to step up to the Plate
On balance, we believe that the best outcome for most organisations will still be to have a unified EA function reporting to the CIO. But to ensure that the wider business can benefit from the smart use of EA to support strategic decision-making, particularly when major structural changes are planned, the CIO must ensure that adequate EA resources are allocated to the support of the wider business agenda. Failure to do so could result in significant missed opportunities and suboptimal outcomes for the business. For the CIO it would surely be a dereliction of duty.