Introduction: why this action matters for adoption
Change fails in the gap between what the project team believes has been communicated and what impacted people can actually understand, try, question, and use in daily work. Short huddle sessions close that gap by creating a live, facilitated moment where people can hear what is changing, ask practical questions, practise a new behavior, and surface issues before they become adoption blockers. This matters because change management is fundamentally about adoption and usage, not only delivery of a technical solution [Prosci, 2026]. (prosci.com)
Huddles also support employee voice. CIPD recommends regular opportunities for employees to raise concerns and transparent follow-up so people can see how their input influences change [CIPD, n.d.]. (cipd.org)
What this action is and when to use it
A change huddle is a short, structured, facilitated live session, usually 10–20 minutes, focused on one change topic, one impacted group, and one clear outcome. IHI defines huddles as short stand-up meetings of 10 minutes or less used to review standard work, look back at performance, and look ahead to flag concerns [IHI, n.d.]. (ihi.org)
Use huddles when the change is close enough to people’s work that they need clarification, practice, or rapid escalation. They are especially useful during pilots, readiness checks, go-live, hypercare, resistance hotspots, and reinforcement. AHRQ’s TeamSTEPPS guidance says a huddle can be convened when a plan needs adjustment and that any team member observing relevant changes can call one [AHRQ, 2023]. (ahrq.gov)
Adapt the huddle by audience. For impacted employees, focus on “what changes in my work today?” For managers, focus on coaching, resistance, and escalation. For sponsors, use huddles to hear unresolved barriers and make decisions. For highly resistant groups, use smaller sessions, more listening time, and neutral facilitation.
Preparation: inputs, stakeholders, materials, timing, and decisions needed
Prepare the huddle from the change impact assessment, stakeholder map, readiness data, training plan, adoption metrics, and known resistance themes. PMI recommends identifying barriers and enablers, assessing stakeholder attitudes and skills, and continuing to detect feedback throughout the project lifecycle [PMI, 2012]. (pmi.org)
Before the session, decide the purpose, audience, facilitator, issue owner, escalation route, and what can be answered or decided in the room. Prepare a short message on the change, a one-page job-impact summary, a demo or practice prompt if relevant, and an issue log. Ask a people manager or local change champion to co-host where possible, because people managers are close to how the change affects day-to-day work [Prosci, 2026]. (prosci.com)
Step-by-step facilitation guide
Open with purpose and safety. State the topic, timebox, and desired outcome. Say: “This huddle is to identify what may stop us adopting the change and agree what we will do next.” Psychological safety and manager relationships influence whether people feel comfortable raising concerns [MIT Sloan, 2023]. (sloanreview.mit.edu)
Anchor the change in work impact. Briefly explain what is changing, why now, who is affected, and what is expected this week. Avoid a long presentation.
Ask a focused prompt. Use one practical question: “What is unclear?”, “What might stop us using this?”, “Where will this slow customers down?”, or “What do you need before go-live?”
Create equal participation. Use a quick round-robin, chat waterfall, or silent note capture before discussion. This prevents the loudest voices from becoming the only data.
Triage, don’t solve everything. Sort issues into answer now, assign action, escalate, park, or convert to training. PMI notes that resistance should be diagnosed because concerns may reflect motivation, competence, or both [PMI, 2012]. (pmi.org)
Confirm actions and owners. For each issue, agree owner, due date, escalation path, and how the group will hear back.
Close with reinforcement. Summarize what was learned, what will change, and the next expected behavior. Gallup’s research emphasizes timely, frequent, actionable feedback rather than delayed or vague feedback [Gallup, 2024]. (gallup.com)
Example: how this could be applied in a real change initiative
A company is introducing a new CRM process for sales and service teams. Two weeks before go-live, the change manager runs 15-minute huddles by region. The first huddle reveals that mobile access is unreliable, sales managers are unclear on approval rules, and service agents need a short practice scenario. The change manager assigns the mobile issue to IT, asks the process owner to clarify approval rules by Friday, and schedules a 10-minute practice demo for the next huddle. The huddle prevents “training is complete” from being mistaken for “people are ready.”
Roles and responsibilities
Role | Responsibility |
Change manager | Designs the huddle approach, prepares messages, facilitates or coaches facilitators, tracks issues, and reports adoption risks. |
People manager | Hosts local sessions, explains personal/team impact, encourages participation, and follows up with individuals. |
Sponsor | Opens key huddles when visibility is needed, reinforces why the change matters, and removes escalated barriers. |
Subject matter expert | Answers process or system questions and demonstrates the new way of working. |
Scribe/action owner | Captures issues, decisions, owners, and due dates. |
Participants | Raise practical concerns, test understanding, and commit to agreed next actions. |
McKinsey’s transformation research highlights the importance of frontline employees and line managers in successful transformations, while Prosci identifies sponsors and people managers as core change roles [McKinsey, 2017; Prosci, 2026]. (mckinsey.com)
Common mistakes to avoid
The most common mistake is turning the huddle into a broadcast. If people only listen, it is a briefing, not a huddle. The second mistake is collecting issues without visible follow-through; CIPD specifically recommends transparent follow-up so employees can see how voice influences change [CIPD, n.d.]. (cipd.org)
Other mistakes include inviting too broad an audience, allowing senior leaders to defend the solution instead of listening, mixing confidential HR issues into a group forum, and failing to distinguish training gaps from design, workload, or motivation concerns.
Measures of success or adoption indicators
Measure whether the huddle is improving adoption, not just whether it happened. Useful indicators include attendance from the intended impacted group, percentage of participants who contribute, number and type of issues raised, action closure rate, time to resolve blockers, confidence/readiness pulse scores, recurring resistance themes, training or practice completion, and adoption outcomes such as system usage, process compliance, support tickets, errors, rework, or customer impact.
Checklist for the change manager
Define the huddle purpose and audience.
Confirm facilitator, sponsor, SME, and scribe.
Prepare a short change-impact message.
Bring the current issue log and escalation route.
Use one focused question to surface challenges.
Capture every issue with an owner and date.
Communicate follow-up before the next huddle.
Adjust cadence as risk decreases or adoption stabilizes.
Optional reusable huddle template
Section | Suggested wording |
Opening | “We have 15 minutes to identify what may block adoption and agree next actions.” |
Change focus | “This week’s focus is: [specific process, behavior, system step, policy, or decision].” |
Prompt | “What is unclear, risky, difficult, or missing for you to use this change?” |
Triage | “Is this an answer-now, action, escalation, training need, or parked item?” |
Close | “Here is what we heard, what will happen next, who owns it, and when you will hear back.” |
References
Agency for Healthcare Research and Quality. “Monitoring and Modifying the Plan: Huddle.” May 2023.
https://www.ahrq.gov/teamstepps-program/curriculum/team/tools/huddle.html
Institute for Healthcare Improvement. “Huddles.” n.d.
https://www.ihi.org/library/tools/huddles
Prosci. “Core Roles in Change Management.” Published May 20, 2020; updated May 1, 2026.
https://www.prosci.com/blog/core-roles-in-change-management
Project Management Institute. “Managing the People Side of Change: A Systematic Approach.” October 23, 2012.
https://www.pmi.org/learning/library/managing-people-side-change-systematic-approach-5987
CIPD. “Employee Voice.” n.d.
https://www.cipd.org/en/views-and-insights/cipd-viewpoint/employee-voice/
MIT Sloan Management Review. “Proven Tactics for Improving Teams’ Psychological Safety.” March 27, 2023.
https://sloanreview.mit.edu/article/proven-tactics-for-improving-teams-psychological-safety/
McKinsey & Company. “The People Power of Transformations.” 2017.
https://www.mckinsey.com/~/media/mckinsey/business%20functions/people%20and%20organizational%20performance/our%20insights/the%20people%20power%20of%20transformations/the-people-power-of-transformations.pdf
Gallup. “How Effective Feedback Fuels Performance.” January 1, 2022; updated January 19, 2024.
https://www.gallup.com/workplace/357764/fast-feedback-fuels-performance.aspx