Enterprise Architecture

You Should Always Apply an EA Framework

While you analyze and implement the organization’s to-be enterprise architecture you will have to apply a framework, or do you?

Role of the Framework

The enterprise architecture framework plays with interesting role when it comes to the empowerment of enterprise architects by providing: 

  • Providing examples on artefacts that can contain the relevant information.
  • An overview of information that has to be uncovered.
  • Identifying gaps in the collected data.
  • Identifying how information is to be collected and in what order.
  • Speeding up clarifications and implementation of identified changes.
  • Speeding up information collection and information processing.
  • Applying best practices to analyze impacts when the new initiatives (projects) are implemented.
  • Following up on enterprise investments.

Advantages of a Framework

Organizations applying an enterprise architecture framework can benefit from some advantages compared to organizations that do not:

  • Proven methods.
  • Knowledge is usually available.
  • Different templates support the use of the frameworks.
  • Communities of practice.
  • The advantages mentioned in the former chapter.

Disadvantages of a Framework

Though there are many advantages of using an enterprise architecture framework, then there some disadvantages by using a framework: 

  • You will have to follow a standard.
  • Frameworks rarely appear intuitive for stakeholders.
  • Time is consumed on a method and not on content creation.
  • No scope on cash flow.
  • Some frameworks require certification, which can add costs of operations for the organization.
  • Adaption of the framework for the individual organization. Does the framework suit the needs and requirements of the individual organization?


I have personally never worked in an organization that has adopted an enterprise architecture framework. The organizations have on the other hand been perfectly able to do fine without. However, the organizations could also do better. 

The EA teams in each of the organizations could have used more effort on choosing a few artefacts that could prove additional value for the stakeholders e.g., artefacts related to project initiation, principles for investments, standards and business processes or system landscapes.  Additionally, the individual EA teams could develop the requested artefacts iteratively through lean principles in order to get and process the relevant information that makes each of the artefacts usable. In other words, one step at a time, and just enough – just in time.


Most organizations can easily apply a few core artefacts and gain the relevant impact on their organizations. Consequently, you and your organization do not have to implement an EA framework for your to-be analysis, though the organization might be able to harvest some benefits by doing so, though it does also comes with a price.