6 Applying and Improving Stakeholder Practice

The stakeholder practice cycle

Stakeholder practice is a continuous cycle: identify who is affected by or can affect the work, analyze interests and influence, plan and carry out engagement and communication, then review results and update records and plans. The cycle should respond to changing stakeholder needs, project conditions, and relationships rather than treating engagement as a one-time task.

Stakeholders may be individuals or groups inside or outside an organization. Some people may be affected without formal representation or even knowing about the project, so the team should not define the stakeholder community only by its existing contacts or formal decision-makers.

Identify stakeholders broadly

Begin with project documents and contacts among staff and the community. Ask identified stakeholders, “Who else could be affected or have relevant knowledge?” Consider people who use, deliver, fund, regulate, or maintain a service, as well as people who may experience indirect effects. Treat the first list as a starting point and actively seek views from people who may be underrepresented in routine meetings or formal feedback channels.

For a library introducing self-service checkout kiosks to reduce queues and give staff more time to help visitors, the initial stakeholder group could include:

• Library visitors, including people with disabilities, older adults, and people who prefer or need support in languages other than English.

• Front-desk and accessibility-support staff.

• Library managers and the project sponsor.

• The kiosk supplier and the organization responsible for technical support.

• Community groups that help represent or serve library users.

Do not assume that faster checkout is the only measure of success. The change may affect people differently, including visitors who need assistance or cannot easily use a kiosk.

Analyze interests and impacts

Analyze what matters to different stakeholders, how they may be affected, and how they can be involved. Power–interest mapping can help prioritize attention, but it should not be the only test: someone with little formal influence may still be seriously affected. Record concerns and potential effects as well as influence.

For the library kiosk project, possible interests and engagement approaches include:

• Visitors who use the kiosks may care about ease of use, privacy, and reliable checkout. Short usability trials and an easy feedback route may suit them.

• Visitors who may need assistance may care about equal access, dignity, and the availability of human help. Accessible demonstrations and invitations through trusted community contacts may help gather their views.

• Front-desk staff may care about workload, training, and service quality. Workshops can identify practical concerns, while regular implementation updates keep staff informed.

• Library managers and the sponsor may care about cost, service outcomes, and schedule. Briefings can cover decisions, risks, and measures of success.

• The supplier and technical support organization may care about requirements, installation, and maintenance. Technical meetings can record actions and responsibilities.

A stakeholder register can record each stakeholder or group, relevant interests, known impacts, preferred contact method, engagement owner, latest contact, feedback, and next action. Record only information needed for the work, keep it secure, and distinguish confirmed information from assumptions.

Communicate and engage in both directions

A communication plan should specify who needs information, what they need to know, why and when they need it, how it will be shared, who is responsible, and how questions or feedback will be handled. Match the channel to the audience and purpose: a staff briefing, accessible demonstration, translated summary, or direct conversation may be more useful than sending everyone the same email. Include feedback routes and ways to assess whether communication is working.

Engagement is more than sending updates. Ask open questions, listen without promising outcomes that have not been approved, record concerns fairly, and explain what the team did with the input. Two-way engagement can reveal impacts or practical solutions the project team missed.

A kiosk trial, for example, might show that screen instructions are confusing and that some visitors want staff nearby during checkout. The team can log the feedback, test clearer instructions, and consider how assistance will be available. It should communicate both the changes made and suggestions it cannot adopt, with reasons.

Update records as conditions change

Treat the stakeholder register and engagement and communication plans as living records. Review them at milestones, after significant feedback, and when scope, schedule, or risks change. Update contact roles and preferences, new or changed concerns, engagement actions, owners, dates, and unresolved issues.

For example, a community group may explain that evening language classes use the library and that participants may need kiosk instructions in additional languages. The team should:

1. Add the affected group and its representative to the register, checking whether the representative can speak for the group or whether other views are needed.

2. Record the new concern, how it was raised, its potential effect, and any uncertainty that needs checking.

3. Review the communication plan, including timing, language, format, and a suitable way to gather feedback.

4. Assign an owner and due date to investigate kiosk language options and support needs.

5. Review accessibility, schedule, cost, and service risks, and escalate decisions through the agreed governance process.

6. Document the decision and communicate it back to the group, including next steps and limits.

A change or decision log can help the team trace what changed, why, who approved it, and which plans or records were updated. Do not overwrite earlier information in a way that hides the project’s reasoning or history.

Evaluate effectiveness and ethical practice

Review both outputs and outcomes. Outputs include meetings held, messages sent, and groups reached. Outcomes include whether people understood the change, had meaningful opportunities to contribute, received responses, and experienced an accessible service. Evidence may include feedback, unanswered questions, participation patterns, usability observations, complaints, and service results.

Low participation does not automatically mean low concern. Consider whether the invitation, timing, format, or setting created barriers. Use evidence about engagement to improve the current project and future practice, not merely to count activities.

A team review can ask:

• Did we identify people affected indirectly as well as people with formal authority?

• Were engagement opportunities accessible, respectful, and available in appropriate formats or languages?

• Did we explain the project honestly, including uncertainty and trade-offs?

• Did we protect personal information and avoid collecting more than was needed?

• Did different groups have a fair opportunity to influence decisions?

• Did we report back on what changed, what did not, and why?

• What evidence suggests the approach worked, and what should change next time?

Apply ethical principles throughout

Ethical stakeholder practice takes affected people seriously, is transparent about the purpose and limits of engagement, handles information responsibly, and avoids token participation. Consider affected groups and ethical concerns throughout the project lifecycle.

Effective practice is iterative: identify affected and influential parties; analyze interests, impacts, and needs; choose suitable two-way engagement and communication; record feedback and decisions; and update plans when circumstances change. Evaluate whether engagement was inclusive and useful, then use the findings to improve the project and future practice.