I like to think about transformation as the following 8 steps:
- Determine the Core Processes
- Document the AS IS Architecture
- Define Design Principles
- Determine the future business design through User Experiences
- Determine the TO BE Architecture
- Create the Transformation Roadmap
- Implementation
- Monitor and Improve
Within my previous 8 posts I describe how I think about and execute each of these 8 steps. A successful EA will gage the organization and adjust their techniques accordingly. The EA does not lead the full transformation, they actually play different roles throughout the transformation journey.
The transformation journey is made up of 3 key sections:
Imagine the possibilities…. Bring it to life…. Realize the benefits
Imagine the possibilities through design, reach for the stars and then scale it back accordingly.
The EA leads the work in this section, the goal is to translate the Strategic Goals into a Future Operating Model.
Bring it to life through projects.
The EA assists the work in this section, the goal of the EA is to monitor and ensure alignment across projects resulting in the strategic goals.
Realize the benefits through KPIs.
The EA builds tools used in this section but does not usually participate. The goals of the tools are to track the performance of the implementation and ensure the strategic goals are realized and continue to perform throughout the years to come. This brings up an interesting discussion. Do organizations need a full time EA position or Architecture office?
The EA position is a powerful and specialized role that is the key to a successful transformation and from my experience is not fully understood.
