Enterprise architecture often involves discovering and understanding fragmented, inconsistent, and undocumented knowledge hidden throughout an organization. Similar to archaeologists, architects must carefully excavate layers of enterprise artifacts, systems, documents, and models to uncover the truth about how an enterprise functions and evolves. This approach, called enterprise archaeology, provides a strong metaphor and method for grasping the structural and operational realities that support business performance.
Why "Archaeology" Matters in EA
1. Map the Site: Structure Your Excavation
To begin an enterprise archaeological effort, architects should:
2. Think Stratigraphically: Understand Layers of Change
Adopt a stratigraphic view of the organization, akin to geological analysis:
EA Layer | Description | |||
Strategic Layer | Enterprise intent and long-range goals | |||
Capability Layer | Core capabilities and outcomes | |||
Process/ Function Layer | How work is performed | |||
Data Layer Application Layer | Information entities, definitions, flows, and structures that support processes Supporting systems and integrations | |||
Technology Layer | Infrastructure and runtime platforms | |||
Analyze how these layers interact and how a change in one layer propagates (or fails to) across others. Misalignment often reveals structural vulnerabilities or transformation friction. Note: the layers presented in this section represent a common stratification used to analyze enterprise architecture. However, they are not exhaustive. Depending on the organization's context, additional layers, such as security, compliance, and standards may be equally important. These layers should be considered as a part of a comprehensive analysis, especially when addressing cross-cutting concerns or regulatory requirements.
3. Adopt Hypothesis-Driven Modeling
Rather than assume legacy documentation is accurate, use hypothesis-based modeling:
This investigative approach builds a more trustworthy and transparent architecture baseline.
4. Embed Enterprise Archaeology into Governance
Make enterprise archaeology part of the ongoing architecture practice:
5. Structure Architectural Discovery Using the Six Interrogatives
A powerful technique in enterprise archaeology is to structure your investigation using the six fundamental interrogatives: What, How, Where, Who, When, and Why. These simple questions can serve as a lens through which to analyze artifacts, identify gaps, and guide discovery efforts.
Each interrogative addresses a distinct dimension of enterprise reality:
Using these questions as scaffolding helps ensure that discovery efforts are comprehensive. For example, when examining a legacy application, ask:
This line of inquiry supports both logical rigor and completeness. It also enables you to trace inconsistencies, reveal assumptions, and connect disconnected fragments. Gaps in one or more areas often indicate areas of risk, misalignment, or neglected governance.
When used across multiple systems, processes, or capabilities, the six interrogatives allow architects to compare and integrate insights systematically, helping to reconstruct a more coherent and actionable view of the enterprise landscape.
6. Promote a Culture of Discovery
Effective enterprise archaeology depends on culture, not just tools:
Why This Matters
The value of this approach extends far beyond documentation:
Getting Started: A Practical Path Forward
Conclusion
Enterprise archaeology is more than a metaphor—it's a systematic method for revealing organizational truth within fragmented and aging systems. Through disciplined discovery, interrogative analysis, and collaborative exploration, architects can clarify confusion and uncover value that often lies just beneath the surface. your text here ...
When you subscribe to the blog, we will send you an e-mail when there are new updates on the site so you wouldn't miss them.
15954 Jackson Creek Pkwy
Suite B463
Monument, CO 90132
dummyZACHMAN: (818) 244-3763
dummyFEAC: (703) 836-1002
dummy
Comments