If the objectives of the architecture aren’t clear for everyone or if people have differing objectives, there is a danger that expectations will not be met or will not have sufficient buy-in and acceptance to be able to work within an architecture. There are often (many) benefits of having the objectives clearly stated for everyone.

For instance the investments, in time and money, can be clearly and powerfully enunciated. Experience tells us that the justification questions arise time and time again. Consistency in the, enterprise wide, responses is crucial to building confidence in the architecture.

Formulating clear and concise objectives has the additional benefit of a well substantiated justification for the architecture: the objectives form the framework within which all important decisions and choices can validated. As it is impossible to achieve everything all at once, the objectives allow the focus to be laid on the appropriate aspects of the architecture.

Finally, the objectives can be used to monitor the user aspects of the architecture. Creating beautiful documentation does not necessarily guarantee that the objectives will be achieved. Additional effort will likely be required. The architecture should lead to the appropriate changes in the organization. The processes will also require monitoring.

Examples of objectives to strive for in an architecture are: management of a best-of-breed policy, supporting portfolio management, identifying and implementing possible synergies and removing barriers between departments.