2015 is an anniversary year for Enterprise Architecture. It is 40 years since Richard Saul Wurman coined the phrase “Information Architecture” — in 1975. Information Architecture became Information Systems Architecture, and then Enterprise Architecture. I predict that enterprise architects will use this anniversary to reflect on the history of our discipline and its position within the organization structure.
For a long time, EA was firmly part of the IT department. More recently the EA team has been found as a stand-alone unit, independent of IT or business. 40 years on, EA will increasingly establish its role as a key member of strategic decision making, capability evolution and organizational change management.
To a certain extent, Enterprise Architects have operated in a silo, independent from other areas of the organization. Those other areas could both benefit from architectural insight and contribute to architectural understanding. In addition, EA teams have failed to reuse the analysis and outputs from other teams, such as business and process analysts, or ideas from organizational, business and operating models. I see that 2015 will bring the EA team into closer contact and greater collaboration with people from business analysis, strategy planning, business operations, and business value teams.
[Editor’s Note: This post is part of the annual “Cutter Predicts …” series.]