Author Interview: Jörg Ziemann
Book Title: Fundamentals of Enterprise Architecture Management
From the Editor: Welcome to the latest in our series of interviews with leading authors of books in Architecture and related disciplines.
In this edition, we speak to Jörg Ziemann about his book, Fundamentals of Enterprise Architecture Management. We are so happy to have been able to spend some time talking with Jörg, and we hope you enjoy reading this interview.
Origins and Purpose
EAPJ: What motivated you to write Fundamentals of Enterprise Architecture Management, and why did you feel this book was needed?
Jörg: The book is based on my 20+ years of enterprise architecture practice in large international enterprises, my previous research activities, and on my lecture “Enterprise Architecture Management and Enterprise Digitalization” at the University of Hannover.
For the university lecture, I missed having a textbook that would cover the topic of Enterprise Architecture Management (EAM) comprehensively, and that would be scientifically rigorous and practically relevant. Similarly, in my role as Senior Enterprise Architect inside large companies, I missed a comprehensive, precise description of EAM that plainly addresses questions like: How can you derive EAM and digitalization goals for your individual enterprise, aligned with its business model? What does the corresponding, optimal EAM implementation in the enterprise look like, e.g., the EAM capabilities, processes and tools? What is a realistic way to measure the success of your EAM activities?
This book aims at closing this gap, being a fundamental handbook for scholars, business managers, architects, CIOs, and other professionals engaged in enterprise digitalization and the enterprise-wide IT landscape, or, as I put in a recent presentation:
- There are many enterprise architecture books written by practitioners.
- There are many enterprise architecture books written by scientists.
- There is only one book based on a significant scientific and practical enterprise architecture management background.
EAPJ: Can you talk a little about your professional journey, and how it has shaped the perspective you bring to EAM in this book?
Jörg: My professional journey spans more than 20 years across industry, research, and academia, which strongly shapes the perspective taken in Fundamentals of Enterprise Architecture Management. I started in software engineering, data analytics, and business information systems, and early on worked at the German Research Center for Artificial Intelligence (DFKI) as an enterprise architect and project lead, grounding my thinking in solid scientific foundations. Over many years in large enterprises—most recently as Senior Enterprise Architect and Lead Architect for Data Analytics at Lufthansa Group—I experienced firsthand the realities, constraints, and trade-offs of enterprise-wide digitalization. In parallel, my academic work as a researcher and university lecturer helped me structure complex problems and connect theory with practice. Writing and speaking extensively on EAM allowed me to continuously reflect on recurring patterns and anti-patterns across organizations. This combination of hands-on responsibility to deliver results in the industry, scientific rigor, and teaching led to a pragmatic, yet method-oriented view of EAM.
EAPJ: The book is part of The Enterprise Engineering Series. Can you tell our readers a little bit about that series and how your book is positioned in it?
Jörg: The Enterprise Engineering Series by Springer focuses on a design-oriented approach to enterprises, integrating information systems and organization sciences, and addressing both theoretical foundations and practical applications. It is aimed at academic audiences as well as experienced practitioners. Fundamentals of Enterprise Architecture Management is positioned within this series by combining scientific rigor with extensive practical insight. It explicitly follows an enterprise engineering perspective by explaining how enterprise architecture capabilities can be deliberately designed to fit an organization’s industry, business model, and specific requirements.
Defining the Discipline
EAPJ: In your view, what distinguishes effective EAM from traditional IT architecture or governance approaches?
Jörg: Enterprise Architecture Management (EAM) is the planning, steering, and controlling of the enterprise architecture to ensure a coherent, sustainable, and business-aligned digital ecosystem. At its core, EAM connects business strategy with the key elements of the digital landscape. It can be applied at different scopes, ranging from all parts of an enterprise – including also non-IT parts – to focusing only on the digital ecosystem. Despite its broader name, EAM usually focuses only on the (enterprise-wide) digital ecosystem. Another frequent misconception is to reduce EAM to IT documentation or compliance-driven governance. Effective EAM differs from traditional IT architecture by being proactive, design-oriented, and strategically focused rather than reactive. It balances central coordination with local autonomy to avoid fragmented, redundant system landscapes. In this sense, EAM acts like a city planner, shaping the long-term structure and evolution of the enterprise rather than managing isolated IT solutions.
Core Concepts and Frameworks
EAPJ: Your book introduces a structured approach to EAM. Which foundational concepts do you believe every organisation must understand before attempting to mature their architecture practice?
Jörg: Before attempting to mature their architecture practice, organizations must first clarify their business model and operating model, including key strategic parameters such as the desired degree of centralization versus decentralization. EAM can only act as an effective “conveyor belt” if it translates these business fundamentals into the functional design of the digital landscape. Structure follows function: the structure of the digital ecosystem must reflect the business and operating model. The classic example is consciously defining the balance between central coordination and local autonomy to avoid both uncontrolled fragmentation and over-centralized governance. Only on this basis can EAM be meaningfully tailored to the organization’s culture and power structures and mature into a trusted, value-adding capability.
EAPJ: How does your framework relate to, complement, or challenge established standards such as TOGAF, ArchiMate, COBIT or ISO/IEC frameworks?
Jörg: The book comprehensively describes Enterprise Architecture Management: what it is, how to fit the EAM capability to a specific enterprise, how to implement EAM processes and roles, and how to evaluate EAM in an enterprise. The framework positions itself as a pragmatic integrator that complements established standards by bridging theoretical rigor and practical applicability. The other frameworks rather focus on enterprise architecture (as opposed to EA Management) or individual parts of EAM:
- TOGAF’s focus is the ADM, which describes how to develop the architecture of one complex system, while the book comprehensively describes the “plan-build-run” of an EAM capability in a specific enterprise.
- ArchiMate is a modelling language, while the book provides the organizational and decision-making context in which such models create value.
- COBIT and ISO/IEC standards focus on governance and quality, with EAM clearly positioned as a proactive design discipline that connects business strategy with operational execution. The book refers to the valuable content of these standards, e.g. in the chapter “evaluating EAM”.
Practical Application
EAPJ: Many organisations struggle to translate EA theory into actionable practice. What are the most common barriers you see, and how does your book help overcome them?
Jörg: Many organizations struggle to translate EA theory into practice due to overly complex frameworks, an “ivory tower” mindset, and a lack of mechanisms that connect strategic architecture visions to operational IT delivery. Common barriers include one-size-fits-all approaches, a disconnect between academic theory and practitioner needs, and a focus on static enterprise architecture instead of active Enterprise Architecture Management.
The book addresses these challenges by shifting the focus to a clear EAM lifecycle of planning, steering, and controlling of both the EAM capability itself, which – once tailored – can then manage the enterprise-wide digital ecosystem, covering these phases:
- Strategic and tactical design of the EAM capability: Figuring out the parameters that shape the EAM capability and the digital ecosystem, e.g. the balance of local autonomy with central coordination.
- Implementing EAM: The EAM cube is a practice proven reference model summarizing the EAM and EA capabilities relevant for large enterprises. It is accompanied by detailed descriptions of EAM processes, roles and artifacts.
- Evaluating EAM: Here, concrete metrics and dashboards to make EAM outcomes transparent and measurable, are described.
EAPJ: You discuss complexity in organisations, and the impact it can have on how they function. Could you elaborate a little on that topic, and how you see EAM helping?
Jörg: Organizational complexity emerges from the growing number of interlinked business and IT elements, intensified by scale, interdependencies, and rapid technological change. If left unmanaged, this complexity leads to a lack of transparency, reduced agility, higher costs, and increased operational and security risks. Decision-makers struggle to understand causal relationships and the impact of change in opaque, fragmented system landscapes. Enterprise Architecture Management addresses this by treating complexity management as a core objective and guiding the digital landscape through managed evolution. Through standardization, harmonization, and a shared architectural view, EAM reduces unnecessary variety while still balancing central coordination with local autonomy, enabling organizations to remain efficient, resilient, and adaptable.
Strategy, Governance, and Value
EAPJ: How should enterprise architects position themselves to influence strategic decision‑making rather than being confined to technical domains?
Jörg: To influence strategic decision-making, Enterprise Architects must lead an enterprise-wide target picture process that manages the full lifecycle of the digital ecosystem. This includes envisioning a business-driven target state, planning the transition through as-is/to-be models and strategic roadmaps, and embedding these roadmaps into investment and project portfolios to steer implementation. Continuous evaluation using metrics and heat maps ensures both the digital landscape and the architectural guidance remain aligned with business strategy. In this role, EAs act less as technical reviewers or “building inspectors” and more as urban master planners, shaping sustainable enterprise-wide structures rather than approving isolated IT projects.
EAPJ: What indicators or metrics do you believe best demonstrate the value of EAM to executives and business stakeholders?
Jörg: To demonstrate the value of Enterprise Architecture Management (EAM) to executives and business stakeholders, metrics should focus on linking the health of the digital ecosystem to strategic business outcomes, typically categorized into financial efficiency, agility, and technical transparency. Because EAM provides value indirectly by shaping the value-creating system and preventing future problems (the “prevention paradox”), these indicators must clearly show how a managed landscape performs better than an unmanaged one.
To put this into perspective, evaluating EAM is like monitoring a city’s health: you can count individual medical treatments (EAM visibility, quality of EAM processes, roles and artifacts), but the results of urban planning are displayed in broader metrics like reduced traffic congestion (lower technical complexity, homogenous, well-structured digital landscape), faster emergency response times (improved IT agility), and higher property values (increased business effectiveness through the digital landscape).
In practice, EAM measurement concentrates on a small set of outcome-oriented indicators: shifting spend from “run” to “change,” lowering total cost of ownership through platform reuse, and reducing technical complexity via standardization and application retirement. From a business perspective, improvements become visible through faster time-to-market, higher project success rates, and better functional fit of applications to business needs. Complementing these quantitative metrics, qualitative indicators—such as stakeholder trust and EAM’s role as a trusted advisor in strategic decisions—signal whether EAM is truly influencing enterprise-wide outcomes rather than operating as a technical support function.
The Human and Organisational Dimension
EAPJ: EAM is as much about people and culture as it is about models and processes. What organisational behaviours or mindsets are essential for EAM to thrive?
Jörg: For Enterprise Architecture Management (EAM) to thrive, organizational culture and soft factors are often more critical than technical models, as a mismatch between strategy and culture can lead to failure, aptly summarized by the proverb “culture eats strategy for breakfast“. For EAM to thrive, an organization must have an open culture that prioritizes enterprise-wide transparency and long-term sustainability over local, short-term autonomy. Stakeholders need to embrace “architectural thinking,” valuing proactive design as a way to prevent future complexity rather than just reacting to immediate crises. This requires moving away from an “Ivory Tower” perception toward viewing EAM as a trusted advisor that fosters collaborative problem-solving across the business. Ultimately, like citizens in a well-planned city, the organization must recognize that shared standards are not restrictions, but essential rules that enable everyone to move faster and more safely. Also, it must be understood that EAM is a highly collaborative game, played across all levels and domains of an enterprise.
EAPJ: How can architects foster collaboration across business, IT, and governance functions in environments that are traditionally siloed?
Jörg: Architects foster collaboration by acting as a “conveyor belt” that connects business strategy with IT execution through informal communities and modern collaborative tools. By participating in portfolio management and reporting to senior leadership, they gain the strategic mandate to align local project demands with the broader enterprise vision. Rather than acting as rigid gatekeepers, they should serve as “harbor pilots” or coaches, using business capability maps and “big pictures” to create a shared language across departments. This integrated approach ensures that while individual units remain creative, they all contribute to a common, sustainable infrastructure that serves the entire organization.
Emerging Trends and Future Directions
EAPJ: How do you see the role of enterprise architecture evolving in the next five to ten years, especially with the rise of AI, digital ecosystems, and adaptive operating models?
Jörg: The role of Enterprise Architecture Management (EAM) is set to change significantly over the next five to ten years to address the challenges of AI, digital ecosystems, and adaptive operating models. Key trends can be summarized as follows:
- In the last few years Enterprise Architecture Management reached a new level of maturity and acceptance. Fundamental questions about “what is enterprise architecture?” are part of the past; the tools, processes, and methods are now well-defined, operational, and can be further refined.
- AI will be increasingly used inside EAM, making the EAM process more rational, efficient and transparent. This will also improve the enterprise-internal data basis of EAM and will further strengthen the discipline itself.
- AI, GenAI, and AgenticAI will continue to dominate the development of the enterprise landscape in the next few years. Today it is widely accepted, that the main challenge of enterprise AI is in the overall architecture and the interplay of the various business and technical disciplines (e.g., data, access, AI). This will further increase the momentum of EAM.
Concrete examples include:
- Managing AI and Data-Centric Platforms – With the rise of AI, the focus shifts from managing isolated applications to building and governing enterprise-wide platforms for big data and AI. EAM ensures that AI solutions are integrated into the digital ecosystem rather than remaining in isolated “sandboxes”, with harmonized and accessible data products.
- Decentralization and Federated Architecture Communities – To cope with the complexity of new technologies and the many involved disciplines and domains, as well as the need for “bottom-up design”, decentralized, collaborative structures are the new normal. Architects are embedded in product-focused teams, while central EAM moderates architecture communities and provides guiding principles, acting as “harbor pilots” who guide through complex landscapes.
- Mastering Complexity in Digital Ecosystems – As enterprises connect with partners and customers, managing interoperability becomes critical. EAM balances local autonomy for innovation with central coordination for scale and transparency, avoiding chaotic “spaghetti-ball” landscapes of redundant systems.
In summary, the enterprise architect’s role is evolving from a “building inspector” enforcing rules to a “collaborative city planner of a megacity,” designing the enterprise-wide digital ecosystem for dynamic, AI-driven growth – always in collaboration with the enterprise-wide architecture and stakeholder community.
EAPJ: Are there emerging capabilities or competencies you believe future architects must develop to remain relevant?
Jörg: Depending on the role – enterprise architect, domain architect, or solution architect – different competencies are required. However, due to the stronger connection of disciplines (e.g. AI, data, access management) pushed by AI, a general need for more cross-cutting, interdisciplinary tech know-how can be anticipated. Complementary to this, on the soft-skill side, also an even stronger need for collaborative and communicative competencies can be expected. Of course, fundamental AI-competence and AI-based business digitalization will be required. Since AI will take over more and more EAM processes and functions, the competence will shift more to assess and green-light AI-based proposals, requiring a rather high seniority and experience regarding technical and business architecture.
Guidance for Practitioners
EAPJ: What advice would you give to early‑career architects who want to build strong foundations in EAM?
Jörg: To build a strong foundation in Enterprise Architecture Management (EAM), early-career architects should move beyond technical modeling and embrace a role that is strategically integrated and collaborative. Although it may seem in day-to-day work that deep technical expertise is not always required, a strong technical foundation is essential. The chief architect of a global brand based in San Francisco once told me that the best enterprise architects often have a background in integration architecture. Beyond this, the following pillars provide a robust framework for professional development:
- Commit to broad, continuous learning: Successful architects are avid learners who maintain a wide-angle view of business domains and the technical state of the art (such as cloud, AI, and IoT) without needing to be experts in every line of code.
- Master abstraction to see through complexity: A core goal of EAM is complexity management—keeping the digital landscape lean, simple, and transparent. Without active steering, IT landscapes naturally drift toward chaotic “spaghetti” structures that increase costs and reduce agility; standardization and harmonization are key to keeping this entropy in check.
- Focus on communication and collaboration: The value of EAM is often indirect, as it lies in preventing future problems and costs that are not yet visible. To build credibility and legitimacy, architects must actively communicate success stories showing how architectural guidance enabled faster delivery or avoided redundant spending. EAM thrives as a collaborative and decentralized discipline, supported by informal networks, wikis, and collaboration tools that engage stakeholders in shared knowledge creation.
EAPJ: For seasoned practitioners, what areas of practice do you believe deserve renewed attention or reinvention?
Jörg: The obvious answer is: everything related to AI.
Beyond that, all of the classic EAM tools and capabilities (as displayed e.g. in the EAM cube) are relevant, and should be further developed. In the next few years, many of these functions will at least partially be automated by AI.
Also: Use the method suggested in the book, to have a coherent strategy-to-execution chain for EAM itself. The complete EAM ecosystem should be stable, in an easy to tell story, that connects the enterprise operating model (strategic fit of EAM), EAM implementation (processes, tools, roles, artifacts) and EAM evaluation (metrics) into a lifecycle of continuous improvement.
Reflections on the Book
EAPJ: If readers take away only one core message from Fundamentals of Enterprise Architecture Management, what should it be?
Jörg: Today we have a well-established method for planning, implementing and evaluating enterprise architecture management that every large enterprise can use.
EAPJ: Looking back, is there anything you would expand on or explore differently in a future edition?
Jörg: I am thinking of a complementary book, that focuses more on the technical enterprise architecture and illustrates the processes via recent examples from the aviation industry, e.g. for introducing GenAI or planning the enterprise-data landscape.
Closing Thoughts
EAPJ: What conversations do you hope this book will spark within the EA community?
Jörg: I hope it will finally stop the tired discussion on “what is EA and what is EAM”, and instead focus on individual EAM capabilities, e.g. for tailoring the EAM capability to the requirements of a specific enterprise, or the practicalities of the “target picture process” for planning enterprise-wide landscapes.
EAPJ: Where can readers continue to follow your work or engage with your thinking on EAM?
Jörg: On LinkedIn (www.linkedin.com/in/drziemann) and my website eamfundamentals.com, where I frequently post use cases and complementary material to the book.
