How to become an Enterprise Architect
The title 'Enterprise Architect' is exquisite. It conveys a sense of grandeur spanning the world with a touch of creativity of Frank Lloyd Wright. Indeed, this title is only for those who have the proven ability to oversee an entire corporate network while weaving intricate new patterns into the tapestry of corporate technology.
Imagine a role where you may have thousands of clients spread out across the globe, all connected via a nebulous web that we call a network. Ponder the time and effort that was required to build it. Consider the complexity of the web that permits the diversity of proprietary systems coexist in our modern corporation.
The Enterprise Architect (EA) is the person responsible for maintaining the regulated anarchy that reigns throughout our corporate networks.
What exactly is an Enterprise Architect? Simply put, an Enterprise Architect is the person who is responsible for overseeing, designing, planning and in some cases building, the overall network for a company. The responsibilities of an EA may span the nation, or they may span the globe, but regardless of the total scope, the EA is there to ensure that a corporate network grows in a controlled manner that will not disrupt current corporate obligations, and that provides the most optimum possibilities for future growth.
An EA is directly or indirectly responsible for ensuring a stable computing environment for user bases that can range from several hundred to hundreds of thousands. Regardless of the number, the EA is responsible for ensuring a cost efficient and reliable solution to ensure network availability for the corporation.
With such a large responsibility, the EA normally reports directly to the Corporate Chief Information Officer (CIO), or in rare cases, directly to the CEO. One apt description of the EA, is the technical expert for the CIO.
So how do you become an Enterprise Architect?
The key to being an Enterprise Architect is a diverse knowledge base. An EA must in effect be at least proficient (if not expert) in nearly every aspect of Information Technology (IT). Whether dealing with the application development/QA team for the newest client server application, or planning the installation of a new Ethernet network for a branch office in South America, the EA can never have too much information or too many details.
One of the best ways to start your career path to becoming an EA, is with a Bachelor's Degree in Computer Science. The broad spectrum of technologies learned about while attaining this degree is an excellent base to begin with.
Once you have your degree, use it. The best area to start working in is IT Project Management. This area involves almost all aspects of technology, and provide many possibilities to be involved in a wide range of technology implementations. At the same time, you should continue your studies, with the goal of obtaining your Project Management certification (PMI).
One of the most important qualities that you should practice while doing Project Management, is be very attentive to details. Ask questions about everything. If you have any questions, do not hesitate to ask. Your goal should be to know as much about the final deliverables as the people building the project. Additionally, do not be afraid of asking people Why?" they made a decision. This may aggravate the person you are asking, but if you answer honestly that you are simply wanting to understand the technology rather than questioning their decision, the aggravation will be very short-lived.
As you continue working in Project Management, as long as you keep questioning, your knowledge will grow. And eventually, you will start providing the answers to other peoples questions.
When this happens, you are almost ready to be an Enterprise Architect. The rest is up to luck and politics.
