The need for the initial model

When an organization decides to start establishing an enterprise architecture, one of the initial questions they pose themselves is: “How do we do that?” Next they start Googleing – and find a lot of well-founded and proven frameworks like Zachman, TOGAF, DODAF, FEA, OIO etc. Soon they find that these frameworks are very comprehensive. They also find it difficult to decide which model suits their organization and where to start within each model. Apparently the established EA frameworks have steep learning curves.

Within our daily work we help companies overcoming this steep learning curve. In this article we will share our experiences in doing that and provide some hints and tricks on how to start out establishing enterprise architecture.

Requirements for the initial model

Often the customer has two simple questions:

1. Which framework should we choose?
2. Where do we begin?

And our answer is: “Do not choose a framework yet – but let us tell you where to begin.”

The reason for this is that you can start out in the same way and then later decide which EA framework you want to mature your organization towards. The same foundation is valid for most (perhaps all?) EA frameworks. This foundation is what we call “the initial model”.

Let us put out the requirements for the initial model. The model must:

• Gain support from the entire organization.
  The single greatest challenge any EA model faces is lack of support from the organization – and top management especially. Any model carries a death sentence from the beginning without support from the organization. Do not bother starting.
• Be accessible and easy to understand.
  The initial model must be easy to understand for everyone; IT people, managers, employees. The architects and program managers must be able to explain the model to anyone involved in IT projects.
• Provide a fast ROI.
  When following the initial model in the IT projects the organization must experience ROI fast. ROI is achieved primarily through reuse. Usually we seek to have reuse in the 2nd IT project using the initial model.
• Map to established EA frameworks.
  Any model must pay respect to the established EA frameworks. The reason for this is that these models are the results of the experience gained from thousands of projects throughout a great variety of organizations and scenarios. The initial model is not an alternative to the established frameworks. The initial model should be considered a first step stone.
• Adapt to the existing business, infrastructure and enterprise architecture.
  The initial model needs to “fit into” the existing environment. You cannot present a model that requires huge changes or challenges the existing way of doing business or the investments already made in the infrastructure. Also the model must respect “the existing enterprise architecture.”
But hey - we do not have any existing enterprise architecture!?! Yes you do. The point is that somehow the business always has been - and still is developing. Despite the fact that your organization does not have established enterprise architecture processes, these processes are still conducted. Although unawarely, silently and informally – enterprise architecture is still performed. Many organizations do have a way of describing their business processes and do have ways to conduct their IT projects. These activities might be minor components in the enterprise architecture – but central activities in IT projects.

One might find some of the above-mentioned criteria hard to achieve. But just imagine what happens, if you: on the basis of managerial support succeeds in providing an easy to understand model that provides fast ROI without jeopardizing the existing business? The answer is: enthusiasm!

You will see that the organization returns to the IT department wanting more. Then you will also see the IT department delivering more due to the extensive reuse of messages. You have a positive spiral. It is certainly worth striving for.

In our experience it is not that hard after all - hence the title of this website.

On to The initial model.