Skip to main content

Putting the Enterprise Back in Enterprise Architecture

Despite the fact that in many organizations the Enterprise Architect and the Enterprise Solutions Architect are often conflated, they are very distinct roles that require different skill sets and areas of expertise.

The Enterprise Solutions Architect is a role that focuses on designing solutions to problems that tend to be IT-centric, while an Enterprise Architect focuses more on designing or documenting the relationship between all the systems across the Enterprise and how they interact to deliver value.

In this episode of LeadingAgile’s SoundNotes, Ross Beurmann is back to bring some clarity to the difference between the two roles, the nature of the work, and the differences in the skill sets required for each role.

Zachman Framework

During the interview, Ross references the Zachman Framework, which was developed by John Zachman in the 1980’s. The framework “provides a formal and structured way of viewing and defining an enterprise” (see Wikipedia link below). If you’d like to read up on it, here are some places to get started:

Contacting Ross

Contacting Dave

We Need Reviews

If you like this podcast, we’d be very grateful for reviews or feedback in iTunes. It will help us create more visibility for this podcast so that we can reach more people. Click here to leave us a review or post feedback.


If you have comments on the podcast or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at

LeadingAgile CSM and CSPO Classes

For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to:

Use the discount code: LA_Podcast to receive a 15% discount on the class.


White Paper
Agile Transformation White Paper 75 Min View

Learn what a structured Agile Transformation is supposed to look like.

Transformation Explained 47 Min Watch

Learn how to achieve true business Agility.

White Paper
Clarity in the Backlog 20 Min View

Take a deep dive into how you should go about creating clarity in your backlog.