Author Interview: Eric Jager
Book Title: Getting Started with Enterprise Architecture: A Practical and Pragmatic Approach to Learning the Basics of Enterprise Architecture
From the Editor: Welcome to the latest in our series of interviews with leading authors of books in Architecture and its related disciplines.
In this edition, we speak to Eric Jager about his December 2023 book, Getting Started with Enterprise Architecture. With a foreword by Whynde Kuehn, and positive reviews from all over the world, this book continues to provide enormous value to practitioners everywhere.
We are so happy to have been able to spend some time talking with Eric, and we hope you enjoy reading this interview.
EAPJ: Can you tell our readers a little bit about yourself, and your inspiration for writing this book?
Eric: Almost two decades ago, I found myself working in architecture without really realizing it. Pursuing a career in Enterprise Architecture wasn’t a conscious or well-considered choice. Rather, it was a natural process that unfolded. Due to my background in IT, I became interested in how things connected on a larger scale. Eventually, I found myself dealing with issues at the architectural level—specifically, IT architecture. Over the following years, I became interested in other areas, such as business operations and strategy. About twenty years ago, I realized that I was actually working in Enterprise Architecture. Since then, I have worked as an Enterprise Architect.
Having worked for various organizations over the years, I have seen up close how Enterprise Architecture (and sometimes the lack thereof) is applied in practice. The gap between theory and practice quickly became apparent. I began investigating the reason behind this discrepancy and concluded that many organizations lacked—and still lack—a clear understanding of how to begin working with architecture. Most organizations try to apply the theory described in frameworks such as the TOGAF Standard comprehensively and on as large a scale as possible. That is where many organizations go wrong.
Seeing this as the main reason architecture initiatives fail, I wrote a book presenting an approach organizations can use to start working with architecture. The book helps organizations focus on building a solid foundation first. Drawing from my years of practical experience, I created the Enterprise Architecture Implementation Wheel, a method for implementing Enterprise Architecture that can be used by novice and experienced architects alike.
EAPJ: Without giving too much away, how would you summarise the key points made in the book?
Eric: The book contains a wealth of information about the field of Enterprise Architecture. It begins with a brief history of architecture, a definition of the field, and an overview of its domains and roles. To provide a careful and coherent picture of Enterprise Architecture and its applications, the book describes a method for visualizing architecture and its position within an organization. Finally, the book describes and explains a simple way of working with architecture.
The method described in the book (the Enterprise Architecture Implementation Wheel) is based on the TOGAF Standard, which is arguably the most widely used architecture framework in the world. The main difference between my method and The Open Group’s is that my method establishes a fundamental Enterprise Architecture that can be expanded at any time. The book emphasizes creating a solid foundation rather than implementing a complete Enterprise Architecture immediately.
The Enterprise Architecture Implementation Wheel method consists of four stages, each divided into a number of steps. Each step consists of what I call key focus areas. These stages outline the primary components of implementing a basic Enterprise Architecture, addressing issues such as inventory, definition, implementation, and control stages. During each stage, the most important aspects of establishing a fundamental Enterprise Architecture are described. Using ready-made artifacts, the book proposes a kind of predefined framework that can be expanded and supplemented over time.
EAPJ: The book has been very well received by practitioners. What do you think has contributed to that popularity?
Eric: In my opinion, the book owes its success to three key factors. First, it is written in a narrative style. Unlike other books that describe the theory of an architectural framework, this book reads like a story rather than a reference work and avoids a static writing style. The chapters are a manageable size, with the exception of Chapter 8, which explains the theory behind the method. This contributes to a pleasant reading experience.
Second, the language used is accessible. Difficult words and excessive jargon are deliberately avoided, and terms and definitions are explained in recognizable language. Enterprise Architecture is a field with many definitions, so it’s important to use them carefully. However, they can also be explained in a more accessible way. That is what I have done in the book.
A third factor contributing to the book’s popularity is that the described method is easy to apply to any organization. The Enterprise Architecture Implementation Wheel (EA Wheel) is limited to the basics and does not have an excessive number of stages, steps, and key focus areas. This keeps it clear and straightforward. The components of the Implementation Wheel are recognizable and leave little room for interpretation. Organizations and architects who are just starting to work with architecture can begin using the method right away.
Overall, the book provides a practical and pragmatic approach to Enterprise Architecture. I think this also appeals to practitioners.
EAPJ: Who do you think would benefit most from the insight and advice the book provides?
Eric: As mentioned, the book is intended to help organizations and architects establish a fundamental Enterprise Architecture. The book will be most beneficial for organizations looking for an easy-to-implement method for setting up architecture or for reviewing their existing architecture to strengthen its foundations. The book can also be used by architects. Novice architects at the start of their careers and more experienced architects looking for a clear explanation of how to create a solid foundation for Enterprise Architecture will find it useful.
EAPJ: Should the book be read by people outside the Architecture profession?
Eric: Absolutely. Apart from the two most obvious groups I mentioned earlier (organizations and architects), the book is valuable for senior management and project leaders. These roles may not be directly involved in architecture but certainly have an indirect connection to it. Written without jargon or academic language, the book is ideally suited for roles with an indirect relationship to Enterprise Architecture. It enables readers to understand what Enterprise Architecture is, how it came about, where it can be used, and how it can help organizations implement and realize their strategies. This makes it particularly valuable for senior management.
EAPJ: Can you elaborate a little on the EA Wheel, which you describe in the book?
Eric: The EA Wheel method is a practical and pragmatic approach to developing a fundamental Enterprise Architecture. It is based on the TOGAF Standard. The method differs from the aforementioned framework in that it adapts TOGAF’s structure and flow by reorganizing its content into four main stages: Document, Define, Execute, and Control. Each stage is broken down into key focus areas and actionable artifacts, offering a streamlined entry point for organizations that are new to Enterprise Architecture.
The Enterprise Architecture Implementation Wheel
The straightforward description of the steps within the method ensures an accessible approach. The simplicity with which actions and outcomes are described and explained makes the method applicable to almost any situation and scenario.
Rather than aiming for exhaustive coverage, the Enterprise Architecture Implementation Wheel method provides a scalable foundation that organizations can build upon as they mature. It establishes a solid basis for effectively adopting and applying the core principles of the TOGAF Standard.
Designed primarily for early-career architects and organizations new to architecture, the method emphasizes clarity and usability. It includes a selection of tailored catalogs, diagrams, maps, and matrices. These essential deliverables make fundamental architecture easier to understand and implement. The Enterprise Architecture Implementation Wheel can be thought of as a simplified, tailored version of the TOGAF Standard, providing an approach that is easy to understand and apply to creating a fundamental Enterprise Architecture.
EAPJ: How does your book relate to existing approaches, frameworks and notations used in EA teams around the world?
Eric: The book provides an overview of the most well-known architectural frameworks. These include the TOGAF Standard, the Zachman Framework, and the BIZBOK Guide. The first two are compared, and their differences and similarities are identified. A key component of the TOGAF Standard is the Architecture Development Method (ADM). This approach to architecture is extensive. The TOGAF Standard describes all aspects of comprehensive Enterprise Architecture and uses the ADM to allow practitioners to apply it.
The Enterprise Architecture Implementation Wheel method described in my book selects the most important aspects for creating a fundamental architecture and further develops them with the help of ready-made artifacts. Since my method is based on the TOGAF Standard, the material is easily recognizable. This makes the method easy to apply and implement.
EAPJ: How do you describe the importance of Enterprise Architecture within organisations?
Eric: As we all know, structure, clarity, and coherence are essential to any organization. Unfortunately, these qualities are often lacking. In practice, we see that internal departments often operate independently of each other. This results in a disjointed whole. The consequences are often diverse. These range from business processes that do not fit together, to an organizational structure that does not match staffing requirements, to an application landscape with overlapping and duplicate functionality. Not to mention the supporting technology, which is often too firmly embedded, making systems difficult to replace and resulting in a lot of legacy technology.
Enterprise Architecture, when applied correctly, contributes to providing structure by offering insight and creating coherence between organizational structures, business processes, and the systems required to support them. Enterprise Architecture is a crucial factor in determining the impact of an organizational strategy and translating it into implementation. Ultimately, Enterprise Architecture contributes to achieving an organization’s objectives, making it an indispensable function for any organization, large or small.
EAPJ: What do you see for the profession as we move through our current period of rapidly accelerating technological innovation?
Eric: I believe the field of Enterprise Architecture would benefit from embracing technological development. However, experience, knowledge, and expertise in the field remain essential and cannot be replaced by emerging technologies. That said, contemporary techniques can support the field in its implementation. In my opinion, modern techniques can save a lot of time by making work easier, simpler, or faster. The field must remain open to these developments.
Additionally, I believe that we should not get ahead of ourselves. This is a trend that has been visible for years. With every new development, we shift our focus completely to the new trend, losing sight of the basics and the solid foundation. Over time, we conclude that the new technology is insufficiently aligned with the lagging, underdeveloped foundation. The result? We are unable to make as much use of the new developments as we had hoped. This is why I advocate for not losing sight of the importance of laying a solid foundation. This is particularly true in Enterprise Architecture. Lay a good foundation and build on it over time. Then, supplement that foundation with new technological developments.
EAPJ: Are you thinking of a second edition, or a follow up book that helps practitioners in other ways?
Eric: As luck would have it, I just finished putting the finishing touches on my second book, Mastering the TOGAF® Standard. As the title suggests, this book focuses on the well-known architecture framework, the TOGAF Standard. While the framework takes a theoretical approach, my book aims to provide an accessible explanation of the Enterprise Architecture framework. It delves into the most important and distinctive aspects of the TOGAF Standard, offering practical examples and clear visualizations. It contains concrete, step-by-step plans for all aspects of the TOGAF Standard. Users of the framework will particularly appreciate this last point, as it is something that is sorely lacking today. The book will be available in early 2026.
EAPJ: How can people engage with you if they want to find out more?
Eric: I am always open to a good conversation and can be found on LinkedIn regularly. I share a blog about the field every month and interact with colleagues almost daily. If you are interested in getting in touch, LinkedIn is one way to do so. My website also offers a way to contact me. It features a contact form that people can use to send me a message.
EAPJ: Where can people get a copy of your book?
Eric: The book is available from virtually all online bookstores. The most well-known are Amazon (including its localized websites) and Springer. More information can be found on my website.
About the author
With over 18 years of experience practicing Enterprise Architecture and extensive knowledge of its development and application, Eric is considered a thought leader in the field. He has worked for many organizations, ranging from government agencies to healthcare institutions.
Eric lectures on architecture at Eindhoven University of Technology and speaks at various conferences and seminars. He focuses on the practical and pragmatic application of Enterprise Architecture.
