Deliverables from Enterprise Architecture
An EA process that delivers business value to the enterprise produces several things:
- An articulation of the strategic requirements of the enterprise
- Models of the future state, which illustrate what the enterprise should look like across all EA viewpoints in support of the business strategy
- A road map of the change initiatives required to reach that future state
- The requirements, principles, standards and guidelines that will steer the implementation of change initiatives
A successful EA program is not just about setting standards — it is about solving problems.
The Most Important Deliverable of EA Is Change
Enterprises undertake the process of enterprise architecture for a variety of reasons. Some want to reduce technology diversity. Others want to simplify a complex application landscape. Still others want to improve time to market for new products, or to take a more strategic approach to a transformation initiative. Whatever the reason for initiating an enterprise architecture program, there is one common objective: change.
The enterprise wants to perform better by doing things differently, and it expects the EA program to effect that change. It is critical to remember this when evaluating the outputs of an EA program. All the future-state models, principles and road maps will be for naught unless they are actually implemented.
It is not enough just to "clean up" the technical chaos that has grown up over the years; EA must help prevent the chaos from returning.
It is not enough to simplify an application portfolio this year; EA must help maintain simplicity in future years.
The more successful the EA process is year over year, the easier change should become — each future-state iteration becomes more evolvable than the last.