4 Stakeholder Engagement Planning and Practice

Plan around stakeholders and decisions

Effective stakeholder engagement is planned and two-way. It is not simply a way to gain approval: it can reveal risks, improve decisions, and make impacts and trade-offs clearer. Identify who is affected or influential, learn what they need, involve them in ways that fit the decision, and adapt as circumstances change.

Turn analysis into a plan

For each stakeholder or group, consider and record:

• Role and impact: What can they influence, and how might the work affect them?

• Interests and concerns: What outcomes matter to them? What questions or risks do they raise?

• Current relationship: Are they supportive, undecided, concerned, or opposed? What evidence supports that assessment?

• Engagement need: What do they need to understand, contribute, decide, or receive, and when?

• Practical access needs: Consider language, disability access, technology, time, location, confidentiality, and cultural context.

• Owner and follow-up: Who will engage them, by what date, and how will commitments and feedback be recorded?

A power-and-interest mapping can help prioritize attention, but it should not be the only filter. People with limited formal influence may still be significantly affected or under-represented, so use the map to guide rather than replace judgment and inclusion.

A practical engagement plan states the purpose, audience, method, timing, responsible person, and intended outcome for each activity. Be explicit about what participants can influence and what is already fixed. Engage early enough for input to matter, and match the effort to the decision’s impact, uncertainty, and sensitivity.

Choose methods that fit the need

Choose the least burdensome method that can produce the insight or involvement required. Often, a mix of methods works best:

• Share routine progress: Use a short email, accessible update, or dashboard; for example, a monthly delivery update for a broad audience.

• Clarify an individual concern: Use a one-to-one conversation or phone call; for example, discuss how a planned change affects a service team.

• Gather views across a group: Use a survey, interview, or focus group; for example, ask different user groups about an early design.

• Explore options or trade-offs: Use a facilitated workshop or roundtable; for example, compare rollout options with staff and service users.

• Collaborate on a solution: Use a co-design session, working group, or prototype testing; for example, test a new process with the people who will use it.

• Make or confirm a decision: Use a decision meeting, formal review, or written approval; for example, ask a sponsor to resolve a documented choice.

A broadcast message informs, but usually does not provide meaningful participation. When dialogue, questions, or shared design are needed, choose a method that allows them. Make participation accessible, use clear materials, and seek views beyond the most visible or vocal contacts.

Build trust and report back

Trust grows when engagement is respectful and predictable. Explain the purpose, constraints, decision process, and intended use of feedback. Listen without interrupting, check your understanding, and avoid promising outcomes you cannot control. Keep commitments and protect confidential information.

Close the feedback loop by reporting what was heard, what changed, what did not change, and why. If views cannot be acted on, explain the reason plainly.

For example, a project team planning a new appointment system might hold short interviews with patients who have different access needs, test a prototype with reception staff, and send progress updates to other service users. The team could then explain which suggestions were adopted and why some were not feasible. Each method has a defined purpose; together, they provide more than a single general survey.

Respond constructively to resistance

Resistance is information, not automatically obstruction. It may reflect a real impact, competing priorities, lack of trust, insufficient understanding, past experience, or a concern that has not been heard.

Ask open questions such as, “What is your main concern?” and “What would need to be true for this to work?” Separate the underlying issue from a proposed solution, acknowledge valid impacts, and agree on a specific next step.

Respond proportionately:

• Clarify misunderstandings with evidence.

• Adapt a proposal where feasible.

• Test an unresolved concern.

• Escalate a decision that is outside your authority.

• Explain why a constraint prevents a requested change.

Record the concern, owner, action, and response date. Consultation does not guarantee agreement, and not every suggestion will be adopted. Transparent reasons are more credible than silence.

Track and adapt engagement

Maintain a proportionate engagement log or register. For each stakeholder or activity, record the date, purpose, method, participation, main themes, concerns, decisions, commitments, owner, due date, and follow-up.

Track both activity—for example, whether a promised meeting happened—and usefulness—for example, whether feedback changed a design or uncovered a risk.

Review the plan at milestones and when there is a major change, a new stakeholder, a missed commitment, a repeated concern, or a shift in support. Ask whether important groups are missing, whether the method remains accessible, and whether follow-up is timely. Update the analysis and plan: engagement is iterative, not a one-time mapping exercise.

• stakeholder analysis