The Enterprise Architect The primary responsibility of the Enterprise Architect is the management and implementation of the “Enterprise Architecture Plan.” In most company structures the Enterprise Architect reports to the CIO and has a staff of both technical and business knowledgeable members.
The primary responsibility of the Enterprise Architect is the management and implementation of the “Enterprise Architecture Plan.” In most company structures the Enterprise Architect reports to the CIO and has a staff of both technical and business knowledgeable members.
Since the Enterprise Architecture Plan (EAP) is a living methodology the Enterprise Architect is constantly monitoring and enhancing the EAP. The Enterprise Architect is the liaison between top management, stakeholders and end users of the “How’s,” “Why’s,” “What’s,” “Where’s,” and “When’s” of the EAP.
Since the EAP is not implemented as a pure technology or business methodology the Enterprise Architect must be able to communicate in an understandable language throughout the enterprise at any given moment. They must wear the hat of a technologist, business strategist, business analyst, project manager, product manager, and end user. They must be creative in thought, innovative in implementations, very organized, energetic, and most of all – a people person.
In today’s construct of businesses the Enterprise Architect serves a vital role in the continues success and growth of the enterprise. Statistics show that companies without an EAP lag behind those which do in performance and growth.
Are you building a track home – where the architect just moves rooms to provide a different look; or are you building a custom home – where the architect builds for growth and renovation?