TL;DR

A Communication Plan makes architecture communication intentional. It defines who needs what information, how it will be shared, and when it will be shared, so stakeholders stay aligned during the ADM cycle.

Why this matters

Enterprise architecture contains complex, interconnected information.

When communication is ad hoc, stakeholders miss context, decisions slow down, and alignment breaks.

A Communication Plan prevents that by ensuring:

  • the right information reaches the right stakeholders
  • at the right time
  • through the right channel

Where it fits in ADM

In practice, this is prepared in Phase A when stakeholders and concerns are identified.

It’s then used through later phases (commonly B–F) as architecture work gets more detailed.

Starting point: stakeholder map

The stakeholder map from Phase A Step 2 is the foundation.

From that map, define:

  • stakeholder groups
  • communication requirements per group
  • priority and frequency of engagement

Typical contents

A practical Communication Plan usually includes:

  • stakeholder groups and communication needs
  • key messages per stakeholder group
  • communication mechanisms/channels
  • communication timetable

Common mechanisms:

  • working sessions and governance meetings
  • updates/newsletters
  • repository or workspace access for architecture artifacts

Timetable and cadence

The timetable should state:

  • what communication happens
  • with which stakeholder group
  • when it happens
  • where/how it happens

Makes communication repeatable and reviewable, rather than personality-driven.

Common mistakes

  • sending the same message to every audience
  • no defined cadence (only reactive communication)
  • sharing details without business context
  • no single source of truth for artifacts and updates

Practical tip

Keep the first version simple.

Start with high-impact stakeholder groups and critical decision forums, then refine cadence and channels as the engagement evolves.

Exam note

  • Communication planning is part of effective Phase A stakeholder handling.
  • It supports the Architecture Vision by making intent and decisions visible across stakeholder groups.
  • It is created in Phase A and used through later phases.

Sources