5 Stakeholder Communication

Understand stakeholders and their needs

Stakeholder communication is more than sending updates. It helps people understand decisions, contribute relevant knowledge, raise concerns, and respond to change. Its plan should reflect stakeholder needs and be reviewed as the project and its stakeholders change.

Begin by identifying who needs to know or contribute, and why. Prioritize engagement according to the project’s impact on each stakeholder and that stakeholder’s ability to affect outcomes.

Build a working communication plan

Stakeholder analysis considers each person or group’s role, interests, influence, likely concerns, current attitude, information needs, preferred channels, accessibility or language needs, and the decisions or actions expected of them. Do not assume that a job title alone reveals who influences a decision; ask stakeholders who else should be involved.

A communication plan should specify:

• Audience: who needs the communication.

• Purpose: what it should achieve.

• Message: what information, decision, or request the audience needs.

• Channel and format: how the communication will be shared.

• Timing and frequency: when it will be shared, including important decision points.

• Owner: who prepares, delivers, and follows up.

• Response route: how stakeholders can ask questions or give input.

• Measure: how you will know whether the communication worked.

Use the plan as a working document, not a one-time task. Revisit it when stakeholder roles, project risks, milestones, or information needs change.

Tailor messages, channels, and timing

Adapt the content to the audience’s concerns and the level of detail they need. A sponsor may need options, impacts, and a recommendation; affected staff may need practical steps, training dates, and support contacts. Keep language clear, explain unfamiliar terms, and distinguish confirmed facts from estimates or unresolved questions. Audience research and preferences can help identify which message and channel will be relevant and useful.

Choose a channel that suits both the message and the response needed. Written updates are useful when information must be precise, searchable, or shared consistently. Meetings or calls allow questions, clarification, and discussion of complex or sensitive issues. A dashboard can make routine status visible, while a private conversation may better suit individual concerns. Consider access, confidentiality, time zones, language, and the risk of misunderstanding. Important announcements may need more than one channel, while keeping the core message consistent.

Time communications so people can act on them. Share information before decisions, training, or changes that affect stakeholders—not only after they occur. Set a dependable rhythm for routine updates, and communicate promptly when a significant issue or decision arises. Avoid unnecessary messages because frequent, low-value updates can make important information easier to miss.

For example, before introducing a new scheduling system, a project manager could give the sponsor a short options paper before the funding decision, brief supervisors before training begins, and send affected staff a practical guide before the system goes live. The messages differ in detail, but each explains what is changing, when it happens, and how to ask questions.

Invite and respond to feedback

Build response opportunities into the plan. These might include discussion time at briefings, interviews, workshops, office hours, surveys, or a named contact. Ask specific, open questions, such as, “What could prevent your team from using this process?” Listen without interrupting, check your understanding, and make clear how and when you will respond.

Record significant feedback with its source, issue, owner, next step, and due date. Acknowledge receipt, assess the concern, and explain what will happen, even if the requested change cannot be made. Where appropriate, share a brief “you said / we did” update. Monitor whether stakeholders understand and engage, and adjust the plan if messages are not reaching them or the response route is not working.

Handle difficult conversations constructively

When feedback is critical, separate the concern from your first reaction. Listen for the underlying impact or need, ask clarifying questions, summarize what you heard, and check that the summary is accurate. Avoid becoming defensive or making promises before you understand the issue. Then explain what can be done, who will act, and when the stakeholder will hear back.

Prepare for a difficult conversation by identifying its purpose, the relevant facts, and the desired outcome. Speak privately when appropriate. Describe the specific issue and its project impact without assigning blame, invite the other person’s perspective, and agree on a practical next step.

For example: “The updated requirements arrived after the design was approved. That may affect the delivery date. Can we review which requirements are essential and agree how to handle the change?” If the conversation becomes unproductive or the issue needs authority beyond your role, pause and use the project’s agreed escalation route.

• Two-way communication