5 Stakeholder Communication and Continuous Improvement

Identify and understand stakeholders

Effective stakeholder communication is more than sending updates. It is a planned, two-way process: identify who needs to know or contribute, understand what matters to them, choose an appropriate message and channel, and check whether the communication achieved its purpose. Because stakeholders and project conditions can change, the approach needs to be reviewed and adapted throughout the work.

Begin by listing people and groups inside and outside the organization. Consider who makes decisions, does the work, uses the outcome, provides resources, sets requirements, or may experience unintended effects. Ask stakeholders who else should be involved, and revisit the list as the work progresses.

For each stakeholder or audience group, consider:

• Interest and impact: What do they care about, and how will the work affect them?

• Influence and involvement: What decisions or outcomes can they shape, and what input is needed from them?

• Position and concerns: Are they supportive, uncertain, or opposed, and what explains their view?

• Communication needs: What information, format, language, accessibility, and level of detail will help them?

• Preferred channels and timing: How and when can they realistically receive and respond to messages?

A Power–interest grid can help prioritize attention. Engage closely with people who have high influence and high interest, keep influential people appropriately informed and involved, and provide useful updates to affected groups with less formal influence. A group with limited decision-making power may still face major impacts or hold important knowledge, so the grid should not be used to ignore people.

Tailor messages to each audience

Keep core facts consistent while adapting emphasis, language, detail, and the action requested. A useful message answers five questions: What is happening? Why does it matter to this audience? What happens next? What do you need from them? How can they ask questions or give feedback?

The emphasis depends on the audience:

• Sponsor or leadership team: Focus on outcomes, risks, decisions, and exceptions. For example: “The schedule is at risk because testing is delayed. Please decide by Friday whether to add a test team.”

• Delivery team: Focus on tasks, dependencies, decisions, and near-term changes. For example: “Testing starts Monday. Please confirm your assigned cases in the tracker by Thursday.”

• People affected by a change: Explain what changes for them, when it happens, and where support is available. For example: “The new booking process begins May 6. Attend a demonstration or send questions to the project team.”

• Customers or community members: Explain practical effects accessibly and provide ways to respond. For example: “During the service update, appointments may take longer. Tell us about accessibility needs through the feedback form or phone line.”

Use plain language and explain unfamiliar terms. Choose formats that people can use: some audiences prefer concise data, while others benefit from a visual explanation, demonstration, or conversation. Consider language, disability access, time zones, digital access, and culture. A sensitive message may require a private or live discussion.

Choose channels and timing

Choose communication channels according to the purpose, audience preferences, urgency, sensitivity, and need for discussion or a record.

• Email or a written update: Useful for concise information, links, decisions, and records. Less effective when a difficult issue needs discussion.

• Meetings or one-to-one conversations: Useful for questions, decisions, disagreement, and relationship-building. Send an agenda and record actions afterward.

• Dashboards or project portals: Useful for recurring status information when users know where to find it and who maintains it.

• Demonstrations, briefings, or workshops: Useful when people need to see a proposed change, try a process, or contribute ideas.

• Surveys, interviews, or feedback forms: Useful for collecting input from more people. Include a clear question and explain what will happen with responses.

Set timing according to the decision or action required. Give people enough notice to prepare, share changes before they affect someone’s work, use a channel likely to be seen promptly for urgent alerts, and communicate at predictable intervals for routine updates. State deadlines and time zones where relevant. For important decisions, allow time for questions and follow-up rather than assuming one announcement is enough.

Build a communication plan

A communication plan turns the engagement approach into assigned, scheduled activities. It should specify the audience, purpose, message, channel, timing, owner, feedback route, and how effectiveness will be checked. Review it when audiences, risks, project progress, or stakeholder needs change.

A practical plan might include:

• Sponsor: Secure a decision on testing resources through a decision briefing and follow-up note. Set the timing by Friday, with earlier escalation if the schedule changes. The project lead owns the communication, and the success check is whether the decision is recorded by the deadline.

• Delivery team: Coordinate testing tasks through a weekly team meeting and task board. The test lead owns the communication. Check whether owners confirm tasks and dependencies.

• Affected staff: Explain a new process and collect concerns through a demonstration, accessible guide, and question form. A change lead owns the communication. Communicate two weeks before launch and send a reminder before launch; check attendance, whether questions are answered, and readiness.

Keep the plan practical. Too many messages can create fatigue; too few can leave people surprised or unable to act. Assign one owner for each communication so messages remain consistent and questions receive a response.

Close the feedback loop

Feedback is useful when people can see that it was received and considered. A feedback loop has five steps:

1. Invite input: Ask a focused question and explain how to respond.

2. Listen and record: Capture feedback consistently, including concerns and suggestions.

3. Assess and respond: Decide what can change, what cannot, and why.

4. Report back: Tell participants what was heard and what action followed.

5. Check again: Find out whether the response addressed the issue.

For example, staff may report that a new booking form is difficult to use on phones. The project team could test a revised form with users, publish the change, and explain which other suggestions are still being reviewed. If a suggestion cannot be adopted, explain the reason rather than leaving people uncertain. Closing the loop makes participation transparent and supports trust.

Evaluate and adapt communication

Assess communication by its results, not just by the number of messages sent. Useful indicators include whether people understood the change, took the requested action, made timely decisions, raised issues through the intended route, and felt able to participate. Review attendance, response patterns, repeated questions, missed deadlines, and feedback from different groups.

A low response rate may mean the channel, timing, wording, or access arrangements need adjustment; it does not necessarily mean stakeholders have no concerns.

After a communication activity, ask:

• Did the intended audience receive and understand the message?

• Was the information timely, clear, accessible, and relevant?

• Did stakeholders know what action was expected and by when?

• Did the chosen channel allow people to ask questions or contribute?

• What did feedback reveal about concerns, risks, or overlooked groups?

• What should change in the next message or engagement activity?

Record lessons and update the stakeholder list, communication plan, and messages. Repeat the review at important project stages and whenever circumstances change.

Apply the approach

Use these activities to apply the approach to a project, such as introducing a new staff scheduling system.

Map stakeholders

List at least six stakeholder groups, including people directly affected and groups that may be overlooked. For each group, note its interest, influence, likely concerns, information needs, and preferred way to give feedback. Identify one assumption that needs to be checked with stakeholders.

Write audience-specific messages

Write a short update for each of these audiences: a project sponsor who must decide whether to fund extra training; staff who will use the new system; and a support team that will answer questions after launch. Keep the facts consistent, but tailor emphasis, detail, channel, timing, and requested action. Check whether each audience would know what is changing and what to do next.

Plan communication and close the loop

Create a communication plan for one month of project activity. Include at least three stakeholder groups, an owner, timing, a channel, and a feedback route. Then consider a report from users that a key feature is confusing. Record how the team will acknowledge the feedback, assess it, decide on a response, and report back.

Review and improve

Evaluate the plan using the questions in the preceding section. Identify one group whose needs may not be met and one sign that communication is not working. Revise the plan and identify what evidence would show that the revision helped.

• Continuous improvement