Enterprise Architecture as a practice: A river journey through complexity

Enterprise Architecture: more than just blueprints

Traditional views often depict EA as a static set of blueprints, a rigid framework dictating the structure of an organisation’s IT landscape. However, a more nuanced understanding recognizes EA as a dynamic practice, a continuous process of sensemaking, decision-making, and adaptation. Remember the Sogeti DYnamic Architecture (DYA)? Just as the flow of a river is not only determined by its initial course but also by the terrain, the weather, and human interventions, EA is shaped by the ever-changing business environment, technological advancements, and organisational dynamics. This is the core of EA as a practice. It is not only about documents and blueprints, but rather about the continuous activity of doing architecture in an organisation. It is about guiding, planning, making and taking decisions about the future state of the enterprise, and how to get there.

Practice Theory: embracing the “doing” of architecture

Practice theory offers a valuable framework for understanding EA as a lived experience, not a thing. It emphasizes the importance of “doings” and “sayings” (Schatzki, 2001) – the actions, interactions, and shared understandings that constitute the practice of architecture. From a Dutch perspective, we can compare this to the practice of water management. It is not merely about having a plan for the dykes; it is about the ongoing activities of monitoring water levels, maintaining infrastructure, and coordinating responses to potential floods.

Similarly, EA practice involves many activities:

• Gathering knowledge about the current state and stakeholders’ views.
• Developing architectures: creating models, diagrams, and principles that represent the desired future state.
• Communicating and negotiating: engaging with stakeholders to build consensus and secure buy-in.
• Guiding implementation: aligning projects and initiatives with the architectural vision.
• Evaluating and adapting: assessing the effectiveness of the architecture and making adjustments as needed.

These activities are not linear; they are iterative and intertwined, much like the currents within a river. Each act of “doing” contributes to the flow of the EA practice, shaping its direction and outcomes.

Chaos Theory: navigating the unpredictable river

The business environment is inherently complex and unpredictable, like the turbulent waters of a fast-flowing river. Chaos theory, with its focus on nonlinear dynamics and sensitive dependence on initial conditions, provides insights into how small changes can have significant, often unforeseen, consequences (Lorenz, 1963).

In the context of EA, this means that even the most meticulously crafted architectural plans can be disrupted by unexpected events, such as:

• Emergence of new technologies: A disruptive innovation can make existing systems obsolete, necessitating a major shift in the architectural landscape.
• Changes in market conditions: A sudden economic downturn or the entry of a new competitor can force enterprises to re-evaluate their strategic priorities, impacting the architectural roadmap.
• Mergers and acquisitions: Integrating the IT systems of two different organisations can be a complex undertaking, requiring a careful assessment of compatibility and alignment.

The river metaphor: embracing flow and adaptation

The metaphor of a river helps us visualise the dynamic and adaptive nature of EA practice.

• The riverbed represents the existing organisational structure and IT landscape. It provides the foundation upon which the practice of EA unfolds.
• The flow of water symbolises the ongoing activities and processes within the organisation. EA practice aims to channel this flow in a direction that aligns with the organisation’s strategic goals.
• Obstacles represent challenges and opportunities. EA practitioners must navigate these obstacles, leveraging opportunities to steer the organisation toward its desired future state.
• The river delta represents the potential for multiple outcomes. EA does not guarantee a single, predetermined outcome. Instead, it offers a range of possibilities, each with its own set of trade-offs.

Just as a river’s course is constantly being shaped by its environment, EA practice must be adaptive and responsive to change. This requires a mindset of continuous learning, experimentation, and collaboration. It is not about imposing a rigid structure but about fostering a culture of innovation and resilience. It is about anticipating and designing for change and emergence.

A continuous journey of architectural practice

Enterprise Architecture, viewed as a practice, is not a destination but a continuous journey. It is about navigating the complex and often turbulent waters of the business environment, guided by a shared vision and a commitment to adaptation. By embracing the principles of practice theory and acknowledging the insights of chaos theory, we can develop a more nuanced and effective approach to EA, one that is as dynamic and resilient as the rivers that flow through our beautiful Dutch landscape.

References

Lorenz, E. N. (1963). Deterministic nonperiodic flow. *Journal of the Atmospheric Sciences, 20*(2), 130–141.
Schatzki, T. R. (2001). Introduction: Practice theory. In T. R. Schatzki, K. Knorr-Cetina, & E. von Savigny (Eds.), *The practice turn in contemporary theory* (pp. 1–14). Routledge.