Skip to main content

How to Engage Stakeholders and Build Commitment to Sustain Change

Engage impacted stakeholders in structured discussions to shape change, surface concerns, co-design support, and secure commitments. Use early, before launch, and after go-live to remove barriers, clarify decisions, and build ownership for adoption.

Introduction: why this action matters for adoption

Adoption is not created by announcing a change. It is created when the people who must work differently understand the case for change, can influence how the change will work in practice, and see their concerns converted into decisions, support, or clear trade-offs. Prosci frames change management as preparing, equipping, and supporting individuals so they can adopt and sustain a change, while CIPD emphasizes that genuine employee voice requires managers to listen and act on feedback [Prosci, 2024; CIPD, 2026]. (prosci.com)

This action is a stakeholder engagement and commitment intervention. Its purpose is to move impacted groups from passive awareness to active ownership. The evidence is directionally consistent: participation in strategic change has been associated with stronger goal achievement and organizational commitment and lower resistance, although the effect depends on fit with culture and personal goals [Lines, 2004]. (tandfonline.com)

What this action is and when to use it

This action actively involves impacted employees, managers, sponsors, change champions, or other stakeholders in structured conversations, workshops, design reviews, alignment sessions, and issue-resolution discussions. It is not a communications event. The output is a practical commitment: what will change, who will own which adoption risks, what support is needed, and what decisions or barriers must be escalated.

Use it when the change affects daily work, decision rights, roles, customer interactions, performance expectations, systems, or handoffs. Use it early enough to shape the design, again before implementation to confirm readiness, and after go-live to remove adoption barriers. PMI recommends stakeholder mapping as a living process, not a one-time activity, and LGA guidance stresses identifying impacted stakeholders, understanding motivations and influence, monitoring sentiment and buy-in, and involving stakeholders in design and delivery [PMI, 2015; LGA]. (pmi.org)

Do not use it as fake consultation. If the decision is already made, say so. Ask for input on implementation, risks, local adaptation, training, sequencing, or sustainment—not on choices that are closed.

Preparation: inputs, stakeholders, materials, timing, and decisions needed

Before facilitating, define the adoption outcome in behavioral terms. For example, “sales managers use the new forecasting workflow in every Monday pipeline review” is clearer than “users adopt the CRM.” Prosci’s process starts by defining success, impact, and approach, then tracking performance and adapting actions [Prosci, 2024]. (prosci.com)

Prepare five inputs: the change impact assessment, stakeholder map, readiness or sentiment data, known resistance themes, and a decision log showing what is open, constrained, or already decided. PMI’s influence/commitment matrix is useful because highly influential but low-commitment stakeholders often need focused involvement in planning so they have input and can build ownership [PMI, 2015]. (pmi.org)

Select participants deliberately. Gallup advises matching involvement to the type of change and the organization’s power dynamics: transformational changes need broader involvement across levels, while narrower transactional changes may require only those directly affected or able to remove barriers [Gallup, 2020]. (gallup.com)

Materials should include a simple future-state workflow, “what changes for me” impacts, adoption measures, issue categories, decision boundaries, and an action tracker. Timing should align with project phases: design input before build, readiness alignment before launch, barrier removal during rollout, and ownership transfer during sustainment.

Step-by-step facilitation guide

  1. Open with purpose and boundaries. Explain what the group can influence, what is fixed, and what decisions will be made after the session. This protects trust and avoids “engagement theater.”

  2. Connect the change to work outcomes. Ask participants where the change will help or hinder customer, employee, compliance, productivity, or quality outcomes. McKinsey notes that ownership and energy are needed to keep change plans on track and adapt them as reality changes [McKinsey, 2020]. (mckinsey.com)

  3. Validate impacts. Walk through the future-state process and ask, “Where will work be easier, harder, slower, unclear, or riskier?” Capture impacts by role, not by department alone.

  4. Surface concerns without labeling people as resistant. PMI warns against disrespectful stakeholder labels because they can harden resistance and narrow thinking [PMI, 2015]. (pmi.org) Ask instead, “What would make this difficult to adopt?” and “What would have to be true for this to work here?”

  5. Co-design support and barrier removal. Convert concerns into actions: training, job aids, manager talking points, policy clarification, process redesign, technology fixes, workload relief, or sponsor decisions.

  6. Secure visible commitments. Ask each owner to state what they will do, by when, and what support they need. Managers should leave with team-level follow-up actions because Gallup emphasizes that managers handle questions, negative emotions, feedback loops, and escalation during change [Gallup, 2020]. (gallup.com)

  7. Close the loop. Within a short, stated timeframe, publish what was heard, what will change, what will not change, and why. CIPD stresses that two-way communication requires listening and acting on feedback [CIPD, 2026]. (cipd.org)

  8. Track and adapt. Review the action tracker, adoption data, sentiment, and unresolved barriers weekly during rollout and less frequently during sustainment. McKinsey recommends monitoring progress and adjusting dynamically using relevant metrics and milestones [McKinsey, 2020]. (mckinsey.com)

Example: applying the action in a CRM change

A company is replacing spreadsheets with a CRM forecasting process. Sales representatives worry that data entry will reduce selling time, managers worry that reports will expose pipeline quality, and leaders want better forecast accuracy.

The change manager runs two design-input workshops with sales reps, one manager alignment session, and a sponsor issue-resolution meeting. Employees identify duplicate fields, unclear opportunity stages, and a mobile usability problem. Managers agree to model the new workflow in weekly pipeline reviews rather than asking for spreadsheet backups. The sponsor approves removing three fields, funding short “practice clinics,” and changing the first-month metric from forecast accuracy to completion and quality of opportunity updates. The result is not simply better communication; it is shared ownership of the adoption conditions.

Roles and responsibilities

Role

Responsibility

Sponsor

Sets direction, confirms decision boundaries, removes escalated barriers, and visibly reinforces commitments.

Change manager

Designs the engagement, facilitates sessions, manages the action log, tracks adoption indicators, and escalates risks.

People managers

Translate the change for their teams, hold local conversations, coach behavior, and report barriers.

Impacted employees

Validate impacts, test practical solutions, identify risks, and commit to agreed new ways of working.

Project/product lead

Explains the solution, evaluates design feedback, and confirms what can change technically or operationally.

Change champions/adoption leads

Represent local realities, test materials, support peers, and feed back adoption issues.

Common mistakes to avoid

The most damaging mistake is inviting input when no input can influence anything. A close second is treating engagement as a single workshop rather than a commitment cycle. Other frequent errors are engaging only supporters, bypassing people managers, overusing champions as messengers without giving them influence, failing to document decisions, and measuring attendance instead of adoption. Broad involvement can also backfire when the change is narrow and the engagement creates confusion or expectations beyond the actual decision space [Gallup, 2020]. (gallup.com)

Measures of success or adoption indicators

Useful leading indicators include representative participation from impacted groups, quality and specificity of issues raised, percentage of actions closed by due date, manager follow-up completion, sentiment movement, readiness scores, and reduction in unresolved adoption barriers. Outcome indicators include actual usage, process compliance, proficiency, cycle time, error rates, customer or employee experience measures, benefit realization, and whether line managers have accepted ongoing ownership. McKinsey links successful change execution to clear governance, metrics, role accountability, and line ownership [McKinsey, 2020]. (mckinsey.com)

Checklist for the change manager

  • Have we defined the specific behavior or outcome that must be adopted and sustained?

  • Do we know which groups are impacted, influential, supportive, uncertain, or resistant?

  • Are we clear about what participants can influence?

  • Have sponsors and managers agreed to act on or explain feedback?

  • Are the right formal and informal influencers involved?

  • Is every concern converted into an action, decision, risk, or explicit “no”?

  • Do managers have a follow-up script and team-level commitments?

  • Are adoption indicators reviewed after the session?

  • Is ownership transferring from the project team to the business before closure?

Optional reusable template: 75-minute commitment session agenda

Time

Segment

Output

0–10 min

Purpose, decision boundaries, and desired adoption outcome

Shared understanding

10–20 min

Future-state walkthrough: what changes in daily work

Validated impacts

20–40 min

Barrier discussion: what could prevent adoption

Prioritized risks

40–55 min

Co-design support: what would make adoption workable

Support actions

55–65 min

Commitment round: owners, dates, escalation needs

Action log

65–75 min

Close: what happens next and when feedback will be answered

Trust and follow-through

Sample facilitator script: “We are not here to re-decide the business case. We are here to make sure the change can work in real operations. Please be specific about barriers, trade-offs, and support needs. If something is open, we will record the decision owner. If something is not open, we will say so and explain why.”

References

Prosci. “Change Management Process.” Published July 1, 2024; updated August 20, 2025.
https://www.prosci.com/blog/change-management-process

Prosci. “The Link Between Change Management and Employee Engagement.” Published July 3, 2025; updated October 30, 2025.
https://www.prosci.com/blog/change-management-employee-engagement

Project Management Institute. Miller, D. and Oliver, M. “Engaging Stakeholders for Project Success.” PMI White Paper. January 1, 2015.
https://www.pmi.org/learning/library/engaging-stakeholders-project-success-11199

CIPD. “Employee voice.” Factsheet. April 6, 2026.
https://www.cipd.org/en/knowledge/factsheets/voice-factsheet/

Gallup. Odilov, S. and Musser, C. “Proven Change Management Principles: How to Effectively Initiate It.” July 15, 2020.
https://www.gallup.com/workplace/315602/proven-change-management-principles-effectively-initiate.aspx

McKinsey & Company. Keller, S. and Schaninger, B. “How do we manage the change journey?” May 5, 2020.
https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/how-do-we-manage-the-change-journey

Lines, R. “Influence of participation in strategic change: resistance, organizational commitment and change goal achievement.” Journal of Change Management, 2004.
https://www.tandfonline.com/doi/abs/10.1080/1469701042000221696

Did this answer your question?