2 Stakeholder Engagement and Adoption

Engagement as an ongoing cycle

Stakeholder engagement is more than sending updates. It involves listening to stakeholders and using their input to shape decisions and support. Because stakeholders and conditions can change as the work develops, engagement and analysis need to be revisited throughout the change.

Identify stakeholders broadly

Begin with the change’s objectives: identify what must happen, who needs to act, and who can help or hinder the outcome. Identify possible stakeholders broadly before deciding which groups need the most attention.

Stakeholders may include:

• People directly affected: employees, customers, service users, or partners whose work or experience will change.

• People who influence adoption: executives, sponsors, managers, respected peers, and informal opinion leaders.

• People who enable or constrain the change: project teams, support functions, suppliers, regulators, or other groups whose decisions or resources matter.

Use workshops, existing relationships, team knowledge, and referrals from stakeholders to find groups that might otherwise be missed. Identification is iterative: additional stakeholders may emerge as the change develops.

Analyze and prioritize needs

Stakeholder analysis records each group’s impact from the change, influence over its outcome, interest, and current perspective or readiness. Also record concerns, information needs, and barriers to adopting the new way of working. A stakeholder map can show which groups need close involvement, while a stakeholder register keeps the underlying details and responsibilities visible.

Prioritize according to adoption risk and the attention each group needs, not influence alone. A highly influential executive may need focused sponsor briefings, while a large frontline group facing high day-to-day impact may need practical demonstrations, manager conversations, and accessible support.

Treat the analysis as a working hypothesis rather than a fixed label. Check it through direct conversation and revise it when evidence changes.

Plan purposeful communication

Set a clear objective for each priority group: what should its members understand, contribute, decide, or do? Then choose the appropriate messenger, channel, timing, and opportunity for response.

Communication should explain what is changing, why the change is needed, what it means for the audience, when it will happen, and where people can get help. Tailor the detail and format to audience needs; a broadcast message rarely answers every group’s practical questions.

Sponsors can establish the purpose of the change and show visible commitment. Managers can connect it to everyday work and identify local support needs.

Listen and close the feedback loop

Engagement should be two-way. Listening sessions, demonstrations, workshops, surveys, manager check-ins, and pilots can reveal questions and operational problems early.

Close the feedback loop by explaining what was heard and what action followed. If a suggestion could not be adopted, explain why. This helps make stakeholder input part of the change process rather than leaving people uncertain about whether their feedback mattered.

Respond to concerns

Questions, hesitation, and disagreement provide information about people’s experience of the change; they are not proof that someone is simply obstructive. Ask what is behind a concern. Possible causes include unclear reasons for the change, competing priorities, a perceived loss, insufficient skills, limited resources, or a practical design problem.

Respond with an action suited to the concern, such as clearer explanation, involvement in decisions, training, coaching, or removing an obstacle. Follow up to learn whether the response helped.

Monitor engagement and adoption

Engagement continues during implementation and after launch. Track engagement, such as participation and feedback, as well as adoption, such as use of the new process, completion of required tasks, or observed work practices. Review these signals alongside stakeholder feedback, then adapt communications and support.

Attendance at a briefing or positive survey responses alone do not show that people have adopted the change. Measures of engagement and adoption provide different information and should not be treated as interchangeable.

Example: introducing an expense system

When a company introduces a new expense-reporting system, the stakeholder groups include employees who submit reports, managers who approve them, and finance staff who resolve errors.

Employees need hands-on practice and a clear route to support. Managers need guidance on changes to approvals. Finance staff need to test exception handling and report recurring problems. A pilot and regular feedback checks reveal that the receipt-upload step is confusing. The project team improves the instructions and interface, then checks system usage and error patterns after rollout.

In this example, engagement helps resolve a practical barrier to adoption rather than merely repeating the launch announcement.

The continuous engagement cycle

The process is continuous: identify stakeholders broadly, analyze impact and influence, prioritize according to adoption needs, communicate with purpose, listen and respond, then measure and adjust. Tailored, two-way engagement helps people understand a change, raise concerns, prepare for new behaviors, and sustain adoption.