Introduction: why this action matters for adoption
Team meetings are not just a communication channel; in change management, they are a live engagement intervention that helps people move from “I have heard something is changing” to “I understand why it matters, what it means for me, and what I need to do next.” Prosci’s ADKAR model identifies Awareness as the first individual outcome needed for successful change, before Desire, Knowledge, Ability, and Reinforcement [Prosci]. PMI also emphasizes that projects must plan for adoption and implementation outcomes if intended benefits are to be realized [PMI, 2013]. (prosci.com)
What this action is and when to use it
This action is a structured, facilitated meeting or event with impacted employees, managers, sponsors, or adoption leads. It is best used when the change has a meaningful impact on roles, processes, tools, decision rights, customer interactions, or performance expectations. The goal is not to “announce and leave”; it is to create a two-way setting where employees can hear the case for change, ask questions, test understanding, surface concerns, practise where appropriate, and align on next steps.
Use this action early to build awareness, during design to collect practical feedback, before go-live to build readiness, and after go-live to troubleshoot adoption barriers. CIPD describes employee voice as people expressing views, concerns, and suggestions that can influence decisions, including through informal channels such as team meetings [CIPD, 2026]. SHRM similarly frames serious change management as requiring communication, sponsor support, training, and resistance planning [SHRM, 2024]. (cipd.org)
Preparation: inputs, stakeholders, materials, timing, and decisions needed
Before scheduling the meeting, clarify the change outcome, impacted groups, expected behavior changes, known risks, and decisions that are still open. A meeting that asks for feedback on decisions already finalized will damage trust; a meeting that explains what is fixed, what is flexible, and what input is genuinely needed will feel more credible.
Prepare a short message pack covering the reason for change, the impact on the team, what will happen next, what support is available, and how questions will be handled. Prepare managers separately, because employees often interpret change through the person who leads their day-to-day work. Gallup’s engagement research emphasizes the manager’s role in creating shared ownership and involvement [Gallup, 2024]. (gallup.com)
Also prepare the environment. Edmondson’s research shows that people weigh interpersonal risks before asking questions, seeking feedback, or raising mistakes; psychological safety affects whether people speak up [Edmondson, 2002]. If the meeting includes practice, make it relevant to real work, because workplace learning transfers better when the environment and managers support use of new skills [National Academies, 2018]. (hbs.edu)
Step-by-step facilitation guide
Open with purpose and boundaries. Explain why the meeting is happening, what outcome is expected, what is known, what is not yet known, and how employee input will be used.
Tell the change story in plain language. Connect the change to customer, operational, risk, strategic, or employee reasons. Keep the message specific to the group’s work, not a generic enterprise narrative.
Translate the change into local impact. Describe what will start, stop, continue, or change for this team. Awareness increases when people can see the practical difference between current and future work [Prosci].
Invite questions before defending the plan. Use prompts such as, “What is unclear?”, “What might make this hard in your workflow?”, and “What do we need to solve before go-live?” This supports employee voice and reduces silent resistance [CIPD, 2026].
Practise or scenario-test if the change affects behavior. For a new system, walk through a realistic task. For a policy or operating model change, discuss scenarios and decision points. Adult workplace learning is stronger when learning is relevant, structured, and supported on the job [National Academies, 2018].
Capture issues visibly. Separate questions into “answered today,” “needs follow-up,” “risk or dependency,” and “decision required.” Assign owners and dates.
Close with commitments. Restate what employees should do next, what support is coming, and when the team will hear back. Follow-through is part of the intervention, not administration.
Example: how this could be applied in a real change initiative
A customer service team is moving to a new case management platform. The change manager runs a 60-minute team session two weeks before pilot. The sponsor explains why the old process causes delays, the people manager explains what will change in daily case handling, and a super user demonstrates two common customer scenarios. Employees then practise triaging a case and log blockers on a shared issue board. Three concerns emerge: unclear escalation rules, missing customer templates, and anxiety about productivity targets during transition. The change lead assigns owners, updates the FAQ, and schedules a follow-up practice session. The meeting builds awareness, but also strengthens readiness and adoption.
Roles and responsibilities
Role | Responsibility |
Change manager | Designs the session, prepares messages, briefs facilitators, captures issues, and tracks follow-up. |
Sponsor | Explains the business reason, shows visible commitment, and makes or escalates decisions. |
People manager | Localizes the message, encourages questions, reinforces expectations, and supports employees after the meeting. |
Facilitator | Manages time, participation, tone, questions, and psychological safety. |
Subject matter expert or super user | Demonstrates new processes, answers practical questions, and supports practice. |
Employees | Ask questions, test understanding, raise risks, and commit to agreed next steps. |
Common mistakes to avoid
The most common mistake is treating the meeting as a broadcast. If leaders talk for 50 minutes and leave five minutes for questions, the session may create compliance but not awareness or commitment. Another mistake is inviting feedback without a mechanism to act on it. CIPD stresses that genuine two-way communication requires managers to listen and act on feedback [CIPD, 2026]. (cipd.org)
A third mistake is skipping managers. If managers are surprised in the same meeting as employees, they cannot confidently interpret the change. A fourth mistake is overloading the session with slides instead of helping people understand what will change in their own work. Finally, do not label every concern as resistance. Concerns may reveal real design, capability, workload, or sequencing issues.
Measures of success or adoption indicators
Measure the meeting at three levels. First, check awareness: pulse responses to “I understand why this change is happening” and “I understand what it means for my work.” Second, check engagement and readiness: attendance, participation, number and quality of questions, unresolved risks, and confidence ratings. Third, check adoption movement: completion of practice, manager follow-ups, reduction in repeated questions, system usage, process compliance, error rates, customer outcomes, or other benefits tied to the change. This aligns with ADKAR-style individual outcomes, PMI’s focus on adoption and benefits, and learning transfer principles [Prosci; PMI, 2013; National Academies, 2018]. (prosci.com)
Checklist for the change manager
Define the meeting outcome: awareness, feedback, readiness, practice, alignment, or issue resolution.
Confirm the impacted audience and tailor examples to their work.
Brief the sponsor, people managers, facilitator, and subject matter experts.
Prepare the core message, FAQ, impact summary, and support information.
Decide what is fixed, flexible, and unknown.
Build in time for questions, discussion, and practice.
Create a visible issue and action log.
Agree how and when follow-up will be communicated.
Measure awareness, readiness, and adoption after the session.
Optional reusable agenda and message outline
Time | Segment | Purpose |
5 min | Welcome and purpose | Explain why the team is meeting and what outcome is expected. |
10 min | Why the change is happening | Build awareness of the business, customer, risk, or employee reason. |
10 min | What changes for this team | Translate the change into local workflow, role, tool, or behavior impacts. |
15 min | Questions and concerns | Surface misunderstanding, resistance, risks, and support needs. |
15 min | Practice or scenario discussion | Help employees apply the change to realistic work situations. |
5 min | Actions and close | Confirm next steps, owners, support channels, and follow-up date. |
Opening script: “Today’s goal is to make sure everyone understands why this change is happening, what it means for our team, and what we need to resolve before we move forward. Some decisions are already made, some details are still being shaped, and your questions will help us identify risks and support needs.”
References
Prosci. “The Prosci ADKAR® Model.” No publication date shown. https://www.prosci.com/methodology/adkar
Project Management Institute. “Managing Change in Organizations.” Based on Managing Change in Organizations: A Practice Guide, 2013. https://www.pmi.org/learning/library/managing-change-organizations-5872
SHRM. “Managing Organizational Change.” June 18, 2024. https://www.shrm.org/topics-tools/tools/toolkits/managing-organizational-change
CIPD. “Employee Voice.” April 6, 2026. https://www.cipd.org/en/knowledge/factsheets/voice-factsheet/
National Academies of Sciences, Engineering, and Medicine. “How People Learn II: Learners, Contexts, and Cultures.” 2018. https://nap.nationalacademies.org/read/24783/chapter/11
Edmondson, Amy C. “Managing the Risk of Learning: Psychological Safety in Work Teams.” Harvard Business School, March 15, 2002. https://www.hbs.edu/faculty/Publication%20Files/02-062_0b5726a8-443d-4629-9e75-736679b870fc.pdf
Gallup. “How to Create Shared Ownership of Team Engagement.” September 11, 2018; updated November 19, 2024. https://www.gallup.com/workplace/242054/teams-own-engagement.aspx