Stakeholder engagement versus a communication plan, and how to tell them apart

Engagement changes decisions, communication carries information

A stakeholder communication plan is a document. It lists who needs to hear what, through which channel, how often, and who sends it. Stakeholder engagement is a practice: involving the people affected by your decisions in those decisions, so that what they say can change what you do.

A project can run its communication plan perfectly and still fail at engagement. The plan tells you the newsletter went out. It cannot tell you whether anyone's input changed anything, because distribution is not what it measures.

The test is the one I set out in stakeholder engagement versus stakeholder management: find the route by which stakeholder input changes a decision, and the named person who owns that route. A communication plan with a feedback route that feeds decisions is part of engagement. One without it is a distribution schedule.

A scenario

This is a composite of projects I have worked on, with the details changed.

An organisation rebuilds its website. The team writes a communication plan in month 1: monthly updates to all staff, a showcase event before launch, a feedback form on the intranet. Every item is delivered on schedule. The updates report progress in honest language, the event is well attended, and the feedback form comes back mostly positive.

The publishing workflow changes on the new site. The people who published every week will now do it differently, and that decision was taken in month 1 by the project team on the advice of the platform supplier. The consultation the updates referred to was a session in month 4 about page design. By then the workflow was built.

The communication plan worked. Everyone who could read the intranet knew the project existed, its timeline and its milestones. Engagement failed, because the people most affected by the one decision that shaped their working week had no route to change it, and a feedback form was never going to be that route. Their silence read, in the monthly reports, as contentment.

The lesson is not that the team should have consulted everyone about everything. The workflow decision was theirs to make. The failure was calling the month 4 session participation, and logging the form as engagement.

What a communication plan is actually for

None of this argues against writing the plan. Distribution is a real job: people cannot be involved in work they have never heard of. A plan earns its keep by naming, for each audience, the message, the channel, the frequency and the sender, and by committing to the one thing many plans omit: where the replies go, and which decisions they can affect. Write that route in and the plan becomes part of engagement. Leave it out and the plan will still execute perfectly, which is the problem.

The sender matters as much as the schedule. The plan needs a named owner. In the role set I use, that is the delivery lead, with escalation to the sponsor; the roles are set out in the guide to stakeholder engagement roles.

Which one is missing

Diagnose it by asking which failure you have.

If people know about the work but feel unheard, your communication is working and your engagement is missing. Add conversations before decisions, and a route for what they change.

If the people who would contribute do not know the work exists, your engagement design may be fine and your communication is missing. Write the plan. A transformation communication plan you can fill in is the template I use, with the phases crossed against audiences and the reply route built into the grid rather than added afterwards.

In a crisis the weights shift: communication carries most of the load while engagement narrows to the decisions still open. The playbook for that end of the spectrum is crisis communication for stakeholder management.

Who counts as a stakeholder for either document, and what they can decide or stop, is set out in internal versus external stakeholders. The full sequence, engagement strategy first, communication plan second, measurement third, is in what a stakeholder engagement framework is, with a worked digital-project example in creating a stakeholder engagement framework for a digital project.

Test your next update

Take the next update you plan to send stakeholders. Before you send it, write down one thing a reader could say back that would change a decision you have not yet made. If you cannot name one, the update is communication, and that may be exactly right. Send it, and do not log it as engagement. If you can name one, send the update, and make sure the reply reaches whoever makes that decision.