jump to navigation

EA communications plan July 11, 2008

Posted by Chris Eaton in communications, EA, IT Architecture, methods, people.
Tags: , , , , , , ,
trackback

Communications planning I feel is an oft forgotten part of an EA, even a mature EA. Often, communications is an ad-hoc affair, but planning who you communicate to, what to tell them, when to tell them and then executing against that plan *should* be a substantial part of a good EA practitioner. After all, communications in one form or another is what you are going to be doing 90% of the time.

Communications can take different forms, it could be a regular monthly email, or regular calls to disseminate information, a one on one call, a group call focused on a particular decisions or a website for individuals to find the information themselves. The audience of a particular communication is very important, a is the timing of the communication.

Who, What, When – A communications plan says WHO you are going to communicate with,  WHAT you are going to tell then, and WHEN you are going to tell them.

WHO says that different roles and people need to hear and know about different information. Classic best practices say that executives for instance need to hear and know about different things from solution architects and again there are further role like project managers who should be aware of aspects of the EA like standards and will need to ensure compliance but don’t necessarily understand how the technology needs to work for that compliance

WHAT says what you are going to tell them based on their role, a CIO probably expects a monthly high level update in less than one hour, a solution architect, or group of solution architects may need a one hour meeting to discuss just one new standard which you have introduced, other roles like project managers who own project which need to comply to EA only an awareness.

WHEN says that communications need to arrive at different frequencies for different roles, monthly, weekly, yearly? When can also be triggered, for instance if a requirement changes, or a major event takes place which alters, or could alter, the EA such as a merger of your company or of a competitor, or a change in business strategy, or perhaps even a Black Swan.

In summary most communications should (must) be planned for a specific audiance, of course there are times when the unexpected happens and communications takes the form of hastily scheduled calls or meetings, but the vast majority in a mature EA should be planned.

Advertisements

Comments»

No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: