A briefing during a change is not just a communication event. Done well, it is a facilitated live engagement or learning intervention that helps people understand the change, test what it means for their work, raise concerns, and agree next actions. This matters because adoption happens through individual behavior change, not simply through delivery of a project output. Prosci’s ADKAR model describes individual change as movement through Awareness, Desire, Knowledge, Ability, and Reinforcement [Prosci]. (prosci.com)

Briefings work best when they create a safe, practical space for sense-making. Gallup notes that employees’ questions shift through a change: early questions focus on the end goal and personal impact, while implementation-stage questions focus on steps, roles, and how to help [Gallup, 2020]. A good briefing therefore helps people move from “What is happening?” to “What do I need to do next?” (gallup.com)

A change briefing is a structured live session with a clear outcome, prepared messages, a facilitator, audience-specific content, time for questions, and a follow-up mechanism. It may be a small team meeting, manager cascade, sponsor-led forum, practice lab, operational readiness session, or go-live huddle.

Use a briefing when the impacted group needs more than an email: when personal impacts are material, resistance is visible, managers need alignment, people must practise a new process, or the project needs feedback before implementation. Prosci recommends two-way communication opportunities so people can share concerns, provide feedback, and ask questions in real time [Prosci, 2022/2025]. (prosci.com)

Adapt the purpose by phase. During discovery, use briefings to understand concerns and validate impacts. During design, use them to test workflow assumptions. Before go-live, use them to build confidence and rehearse new behaviors. After go-live, use them to surface issues, reinforce adoption, and agree corrections.

Start with the adoption outcome. Decide whether the session is meant to build awareness, create manager alignment, practise a task, reduce resistance, or confirm readiness. This keeps the briefing from becoming a generic town hall.

Prepare five inputs: the case for change, audience-specific impacts, decisions already made, decisions still open, and the action required from participants. Use the right sender. Prosci’s research-based guidance says senior leaders should deliver organizational messages such as why the change is happening, while immediate supervisors are preferred for personal impact messages [Prosci, 2022/2025]. Gallup similarly emphasizes matching the message to the right organizational level [Gallup, 2020]. (prosci.com)

Create materials that support adoption, not just information sharing: a short narrative, impact summary, “what changes for you” slide, demo or practice scenario, FAQ, issue log, and decision/action tracker. If the briefing includes learning, include realistic practice. CIPD’s evidence review finds training is more effective when people practise using real-world or learner-generated scenarios and when there is a safe learning climate [CIPD, 2023]. (cipd.org)

A company is introducing a new expense approval workflow. The impacted groups are employees who submit expenses, managers who approve them, and finance staff who audit exceptions.

Three weeks before go-live, the change manager runs separate briefings. The employee briefing explains why the process is changing, shows what will be different, and lets employees submit a sample claim. The manager briefing focuses on approval rules, escalation paths, and how to answer team questions. The finance briefing tests exception handling and captures policy gaps. Each briefing produces an issue log, updated FAQ, and confidence score. One unresolved issue—mobile receipt upload failures—is escalated before go-live, avoiding a predictable adoption barrier.

The change manager designs the briefing, defines outcomes, prepares materials, and ensures follow-through. The sponsor explains the business reason, demonstrates commitment, and removes barriers. The people manager translates personal impact, answers local questions, and coaches adoption. The SME or product owner demonstrates the new process and clarifies technical detail. The facilitator manages the conversation and psychological safety. The scribe or adoption analyst captures issues, decisions, sentiment, and readiness indicators. Participants are responsible for asking questions, practising honestly, and raising barriers early.

The first mistake is running a one-way presentation and calling it engagement. A briefing should include dialogue, feedback, or practice. The second is using the wrong sender: project teams can explain mechanics, but leaders and managers are more credible for business rationale and personal impacts [Prosci, 2022/2025]. The third is briefing before decisions are stable enough to discuss honestly, or so late that feedback cannot influence the plan. Other mistakes include mixing audiences with very different concerns, ignoring resistance, failing to capture actions, and measuring attendance instead of adoption.

Measure before, during, and after the briefing. PMI recommends change measurement before, during, and after implementation, including comprehension, behaviors, and post-deployment adoption [PMI, 2015]. (pmi.org)

Useful indicators include attendance by priority audience, quality and volume of questions, unresolved issue count, confidence ratings, comprehension checks, practice completion, manager feedback, sentiment themes, action closure rate, go-live readiness, system usage, process compliance, error rates, help-desk demand, and sustained behavior after go-live. A briefing is working when people can explain the change, perform the required behavior, raise issues early, and see that their input leads to visible follow-up.

60-minute change briefing agenda

Opening script

“Today’s briefing is designed to help you understand what is changing, what it means for your work, and what support you need to adopt it. Questions and concerns are useful data for the change team. We will capture what we cannot answer today and confirm follow-up actions after the session.”