A team meeting during change is not just a communication event. Used well, it is a facilitated live engagement and learning intervention that helps people make sense of the change, connect it to their work, raise concerns, and commit to the next behavior required for adoption. PMI emphasizes that change should be managed toward adoption, use, transition, and benefits realization, not simply delivery of project outputs [PMI, 2013]. (pmi.org)

This action is especially relevant to the “Desire” stage of Prosci’s ADKAR model, where employees move from understanding the need for change to making a personal decision to support and participate [Prosci, 2018/2025]. (prosci.com) A meeting cannot force desire. It can, however, create the conditions that make desire more likely: meaning, psychological safety, confidence, visible support, and a credible path to action [Albrecht et al., 2023]. (frontiersin.org)

Run this action when an impacted group needs more than an email, slide deck, or announcement. It is most useful when employees are asking, “Why are we doing this?”, “What does it mean for my job?”, “Will I be supported?”, or “Is leadership serious?” Those questions map closely to readiness beliefs such as appropriateness, management support, personal benefit, and capability [Holt et al., 2007]. (journals.sagepub.com)

Use the meeting early to surface concerns and build meaning; during design or testing to gather workflow feedback; before go-live to practise new behaviors; and after go-live to remove friction and reinforce adoption. For high-resistance audiences, use smaller manager-led sessions rather than large broadcasts. For sponsors or senior leaders, focus the session on visible commitment, decision clarity, and role modeling. For frontline employees, focus on practical impacts, what is changing in the work, and what support will be available.

Before scheduling the meeting, define the adoption outcome. For example, “customer service agents will log all cases in the new CRM from go-live,” not “employees will understand the CRM project.” PMI notes that value is realized only when outputs are adopted and used [PMI, 2013]. (pmi.org)

Prepare five inputs: the case for change, the audience impact summary, the decisions already made, the decisions still open to influence, and the support plan. The facilitator should know what can be changed, what cannot, and what questions need escalation. This matters because employee voice is only credible when managers listen and act on feedback, not when participation is symbolic [CIPD, 2026]. (cipd.org)

Materials should include a short message outline, impact map, FAQ, practice scenario, issue log, and commitment prompt. If the meeting includes a skill or system practice, design it for transfer to the job and plan follow-up evaluation, because training effectiveness depends on whether people can apply learning at work [CDC, 2024]. (cdc.gov)

A company is introducing a new CRM for customer support. Two weeks before pilot go-live, the change manager and team manager run a 75-minute meeting with support agents. The manager opens by explaining why the CRM matters for case visibility and customer handoffs. The adoption lead shows three work changes: creating a case, updating status, and escalating an issue. Employees then practise one customer scenario and identify likely friction points, such as duplicate fields and unclear ownership. The facilitator records issues into an action log and separates “answer today,” “escalate to design,” and “support after go-live.” This format supports employee voice, readiness, and learning transfer rather than treating the meeting as a one-way announcement [CIPD, 2026; Holt et al., 2007; CDC, 2024]. (cipd.org)

The first mistake is using the meeting to repeat the announcement rather than build desire. More awareness does not automatically create desire [Prosci, 2018/2025]. (prosci.com) The second is inviting feedback when no one is prepared to act on it; CIPD warns that genuine two-way communication requires managers to listen and act [CIPD, 2026]. (cipd.org) The third is allowing managers to facilitate before they are aligned themselves. If managers are passive or resistant, employees often read that signal more strongly than official messaging [Prosci, 2021/2025]. (prosci.com) The fourth is measuring attendance only. Attendance shows reach, not adoption.

Use a mix of leading and lagging indicators. Leading indicators include attendance, participation quality, number of concerns captured, percentage of questions answered, confidence to perform the new behavior, and pulse items on appropriateness, support, personal value, and capability [Holt et al., 2007]. (journals.sagepub.com) For learning sessions, measure whether employees can apply the new process after returning to work, not only whether they liked the meeting [CDC, 2024]. (cdc.gov) Adoption indicators include usage, process compliance, reduced workarounds, quality outcomes, support tickets, manager observations, and progress toward the intended business benefit [PMI, 2013]. (pmi.org)

60-minute agenda: 5 minutes for purpose and ground rules; 10 minutes for the change story; 10 minutes for “what this means for our team”; 15 minutes for questions and concerns; 10 minutes for practice or scenario discussion; 5 minutes for commitments; 5 minutes for next steps and follow-up.

Opening script: “Today is not just an update. The goal is to understand what is changing, discuss what it means for our work, identify what could get in the way, and agree what we will do next. I want to hear concerns early so we can address them rather than discover them after go-live.”

Commitment prompt: “Based on what we discussed, what is one action we can take this week to be more ready, and what support do we need from the project team or leadership?”