Development of an Enterprise Architecture Communication Plan

Communication significantly impacts how IT is perceived by the organization, and therefore it plays a crucial role

Jul. 17, 2009 09:30 AM

As a strategic activity for IT, communication is important for the effective management of both internal and external relationships. The IT function in many organizations operates with highly diverse stakeholders from different parts of the world. The situation has evolved rapidly over the last years through (standardization, globalization, and optimization…).

Communication significantly impacts how IT is perceived by the organization, and therefore it plays a crucial role in the successful positioning of IT as an internal partner. Moreover, given the competitive market pressure the position of IT within the company is the same that of an external IT provider. Hence the same level of professionalism in terms of quality and efficiency are demanded.

Communication concerns all business and IT employees whether they are managers, staff assigned to communication roles, or IT employees with technical tasks. Internally, multinational companies and global departments demand excellent communication and intercultural skills from employees and managers. This philosophy holds true for the field of IT. Smooth working processes and good performance are dependent on effective communications, especially in periods of change.

Effective communication is part of the overall plan for management of an Enterprise Architecture Program. An Enterprise Architecture communication document has to identify stakeholders of the organization’s Enterprise Architecture Program, the information needs of those stakeholders, and the communication strategy to be followed by the program in meeting those needs.

The goals of the Architecture Board, as established by (usually) the organization’s Management Committee’s mission and charter, requires a successful communication strategy. The Enterprise Architecture and the operations of the program charged with evolving that architecture are important topics that must be communicated by the program if the Enterprise Architecture initiative is to succeed.

The plan consists of sections devoted to an identified stakeholder group (you may reuse the stakeholders management defined in TOGAF). Within each section, the plan would identify:

The members of the stakeholder group
The TOGAF Enterprise Architecture Framework role(s) to which the stakeholder group maps
The information needs of the stakeholder group defined in the Architecture Vision The communication strategy to be followed by the program in meeting the information needs of the stakeholder group

This plan should be a living document, and as such should be updated on a regular basis to reflect new stakeholder groups, new information needs, and new communication strategies. It is important that the Enterprise Architecture Program be held accountable for implementation of this plan, and that the Architecture Board regularly reviews progress with the Program Director.

Stakeholder General Communication

Stakeholders are people who have key roles in, or concerns about, the system. Different stakeholders with different roles in the system will have different concerns. Stakeholders can be individuals, teams, or organizations (or classes thereof).

The list of stakeholders can be also based on the existing Business and IT organization and structure. It also takes into consideration recommendation from HR department addressing the various ways of communicating to various groups of people.

The various stakeholders may include (examples):

- Executive Management Board
- C-levels
- Business Users Advisory Board
- Business Units
- Procurement
- Architecture Board
- IT Units
- Enterprise Architecture team
- Customers
- Developers

The communication plan should take into consideration all groups (use best practices from EA frameworks such as TOGAF), the IT organization and the HR recommendations.

These groups will have to be clearly defined as probably some of the communication tools and techniques will have to be tailored for each community.

General Information Needs

The following information needs to be applied to all stakeholders.

Understand what Enterprise Architecture is (at least at a high level)
Understand the value, benefits, and importance of Enterprise Architecture to the business.

Understand how the Architecture Board and Enterprise Architecture Program are contributing to the pursuit of the organization’s business objectives.

Read the original blog entry...

Published Jul. 17, 2009— Reads 5,727
Copyright © 2009 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.

Latest Cloud Developer Stories

Data Center Fabric for Cloud Computing at Cloud Expo New York

By Pat Romanski

Enterprise IT organizations want to deploy a virtualized data center fabric that will provide the foundation for agile private cloud computing. Getting there does not have to be difficult, but it does require a new approach to data center infrastructure design – an approach that ...

Mule ION iPaaS Connects Cloud to On-Premise Apps

By Dana Gardner

New tools and services for swift software-as-a-service integration in the cloud lowers the barrier to SaaS adoption for SaaS providers and developers. MuleSoft this week launched Mule iON SaaS Edition, providing a broad set of new tools and services for swift software-as-a-Servi...

Cloud Expo New York Speaker Profile: Paul Lipton – CA Technologies

By Jeremy Geelan

With Cloud Expo 2012 New York (10th Cloud Expo) now under four weeks away, what better time to introduce you in greater detail to the distinguished individuals in our incredible Speaker Faculty for the technical and strategy sessions at the conference...

Cloud Expo New York: Using APIs to Extend Your Business Reach

By Pat Romanski

How can businesses harness the power of APIs to reach new customers and markets? In his session at the 10th International Cloud Expo, Alistair Farquharson, CTO at SOA Software, will walk the audience through the growth and evolution of the API, why effective API management is i...