Should the IS/IT tail be wagging the EA dog?
24 May 2010
Jeanne W. Ross recently proposed the following.
“Let me propose the following hypothesis: Although EA was initially a function within the IT organization, we will soon find IT to be a function within EA. This is actually not a wild theory; it’s a trend.”
- Jeanne W. Ross, Foreword, The SIM Guide to Enterprise Architecture, CRC Press, 2010, p. xli.
This is a great proposal.
Making the IS/IT function part of the Enterprise Architecture (EA) function makes much more sense than having the Enterprise Architecture function as part of IT.
Unfortunately the latter situation is far too common as organisations make the mistake that EA is somehow a more specialised version of Solution Architecture and Technical Architecture.
From the business perspective, the IS and IT functions are often seen as part of the problem and if the Enterprise Architecture (EA) function reports to IS/IT then by association it can also seen as part of the problem.
Since EA is very close to the business by definition (i.e. the ‘Enterprise’) this make life for an Enterprise Architect very difficult. Their natural and main business stakeholders will be wary of sharing their discussions on strategy and business ideas with EA.
The EA function should ideally report to the executive board and be a peer with the business functions.
Often the EA function reports to the CIO. If the CIO is the head of IS and IT functions, then this can be a problem.
Ideally the Chief Enterprise Architect (i.e. the CEA) should be a new ‘C’ level executive position and a peer of the CIO and not report to the CIO.
This would instantly give the Enterprise Architecture function the level of authority and position with the organisation hierarchy that it needs to do its job properly.
See also the discussion on this topics started by Birgitt Hartje