Enterprise Architecture Communication Plan

Would you communicate to your CEO the importance of adding the prefix “C_” to constants in your programming? Probably not. Nor would you explain to programmers the importance of tracing the business mission down through tactical initiatives in the organization.

Developing a communication plan is important not only for projects, but for Enterprise Architecture (EA) initiatives as well. Strong EA communication plans provide specialized messages for each stake holder group.

EA Communication Plan Importance

The EA communication plan is a key deliverable of your EA program implementation. This plan will sell stakeholder groups on EA and your program. The EA communication plan is important for several reasons. First, you may only have one chance to sell your message. Second, stakeholders will lose interest quickly if the message doesn’t pertain to them. Finally, a communication plan will provide a systematic method for delivering the EA message.

Specialized Messages for each Stakeholder Group

The EA communication plan should have distinct and specialized messages for each stakeholder group in the organization. For example, the Zachman Framework is based around six basic questions: what, how, where, who, when, and why; with six model types which relate to stakeholder groups: visionary, owner, designer, builder, implementer, and worker.

Stakeholder groups vary from organization to organization, but are on average similar across the board. Different EA Frameworks will use varied terminology to describe the stakeholders, but in the end they’re all the same.

Ultimately, a strong communication plan is critical to EA program success. The communication plan is ongoing and will never end.

Pragmatic Advice

• Put your plan on paper.

• Shop your plan to several knowledgeable people in your organization for advice.

• Don’t forget you may only have one chance to sell your stakeholders.