Organizations use enterprise architecture (EA), which describes an enterprise from an integrated business and IT perspective, to improve business and IT alignment. The literature describes many different methodologies to organize EA practice. However, organizations typically adapt these EA methodologies to their specific needs rather than use them directly “out of the box”. As a result, actual EA practices often differ substantially from the original EA methodologies. Unsurprisingly, establishing a successful EA practice remains troublesome even though multiple detailed methodologies exist. However, researchers have yet to investigate the adaptation of EA methodologies in organizations. In this paper, based on an in-depth qualitative case study, I explore the adaptation of the most popular EA methodology, TOGAF, to address this gap. In this paper, I holistically describe a TOGAF-based EA practice and analyze the adaptation of the TOGAF methodology in an organization. From my findings, I conclude that none of the TOGAF-specific recommendations proved useful in the studied EA practice. Supported by ample indirect evidence available in the existing EA literature, this study questions the value of TOGAF as a standard for EA practice. Moreover, the studied EA practice hardly resembles any established EA methodologies or theoretical conceptualizations. Therefore, the EA practice that this case study describes presents a new, largely unexplored empirical phenomenon. Although this study raises multiple “inconvenient” questions challenging the status quo in the EA discipline, it does not provide definite answers to most of these questions, which calls for further research on methodological aspects of EA practice.

Enterprise architecture is a description of an enterprise from an integrated business and IT perspective intended to bridge the communication gap between business and IT stakeholders and improve business and IT alignment. Enterprise architecture consists of multiple different artifacts providing certain views of an organization and the available enterprise architecture literature offers a number of comprehensive lists of artifacts that can be used as part of an enterprise architecture practice. However, these lists of enterprise architecture artifacts were never validated empirically and the practical usage of different artifacts still remains largely unexplored. Based on a comprehensive empirical analysis of enterprise architecture artifacts used in 27 diverse organizations, this study identifies the list of 24 common artifacts that proved useful in practice and describes in detail their usage and purpose. Although this study does not attempt to theorize on the findings, it makes a significant empirical contribution to the enterprise architecture discipline. In particular, this study (1) provides the first consistent list of enterprise architecture artifacts that actually proved useful in organizations, (2) offers the first available systematic description of their usage, (3) questions the common view of enterprise architecture as a set of business, information, applications and technology architectures and (4) questions the widely accepted conceptualization of enterprise architecture as a set of the current state, future state and transition roadmap. This study provides compelling empirical evidence in favor of reconceptualizing enterprise architecture and calls for further research in this direction.

Enterprise architecture is a collection of artifacts describing various aspects of an organization from an integrated business and IT perspective. Practicing enterprise architecture in organizations implies using these artifacts to facilitate information systems planning and improve business and IT alignment. Despite its long history, the enterprise architecture discipline still remains largely atheoretical and lacks a solid theoretical basis. Based on our previous empirical studies of the practical usage of enterprise architecture artifacts in multiple organizations and broad literature analysis, this conceptual article identifies and discusses in detail 10 theories that can be considered key for understanding how an enterprise architecture practice works: actor-network theory, boundary objects theory, cognitive fit theory, communities of practice theory, decision-making theories, information processing theory, knowledge management theory, management fashion theory, media richness theory, and uncertainty principle. Taken together, these theories offer a comprehensive theoretical view of an enterprise architecture practice explaining the role of enterprise architecture artifacts, their usability, and participation of stakeholders and, therefore, may constitute a theoretical basis of the entire enterprise architecture discipline. Although this article does not elaborate on any of these theories, it brings these theories to light, establishes their critical importance for comprehending an enterprise architecture practice, and positions them as central to the enterprise architecture discourse. Each of these theories can be leveraged by enterprise architecture scholars in their future studies for analyzing enterprise architecture practices through respective theoretical lenses. This article intends to provide fresh theoretical insights on enterprise architecture, spark new waves of theoretical enterprise architecture research, and contribute to the development of a sound theoretical foundation for the enterprise architecture discipline.

In recent years, the literature has emphasized theory building in the context of Enterprise Architecture (EA) research. Specifically, scholars tend to focus on EA-based capabilities that organize and deploy organization-specific resources to align strategic objectives with the technology’s particular use. Despite the growth in EA studies, substantial gaps remain in the literature. The most substantial gaps are that the conceptualization of EA-based capabilities still lacks a firm base in theory and that there is limited empirical evidence on how EA-based capabilities drive business transformation and deliver benefits to the firm. Therefore, this study focuses on EA-based capabilities, using the dynamic capabilities view as a theoretical foundation, and develops and tests a new research model that explains how dynamic enterprise architecture capabilities lead to organizational benefits. The research model’s hypotheses are tested using a dataset that contains responses from 299 CIO’s, IT managers, and lead architects. Based on this study’s outcomes, we contend that dynamic enterprise architecture capabilities positively enhance firms’ process innovation and business–IT alignment. These mediating forces are both positively associated with organizational benefits. The firms’ EA resources and specifically EA deployment practices are essential in cultivating dynamic enterprise architecture capabilities. This study advances our understanding of how to efficaciously de-lineate dynamic enterprise architecture capabilities in delivering benefits to the organization.