When Does a Change Update Need a Meeting?
You're in a two-hour change readiness meeting.
Thirty people are present. Five of them are talking. Twenty-five are checking email and wondering why they're there.
Someone asks a question that only affects two people in the room. The discussion continues for fifteen minutes while everyone else waits.
This meeting could have been seven targeted emails.
Why does a change update default to a meeting?
Organizations default to meetings for change communication because meetings feel substantial.
They signal that the change is important. They create opportunities for questions. They ensure everyone heard the same thing at the same time.
But most of that value evaporates when:
The information is one-directional (no real discussion happens)
Questions are specific to individual situations (irrelevant to most attendees)
People need time to process before responding (can't react meaningfully in the moment)
Why does one meeting for every audience fail?
Most change meetings try to serve multiple audiences simultaneously.
Executives need strategic context. Middle managers need implementation timelines. Frontline supervisors need talking points for their teams.
Trying to address all of that in one session means:
Executives get bored during operational detail
Supervisors get lost during strategic discussion
Middle managers spend the whole meeting translating for themselves
Everyone leaves frustrated.
When does a change update need a meeting?
Meetings work for change communication when they:
Require real-time discussion to resolve ambiguity
Benefit from multiple perspectives interacting
Need to establish shared understanding across groups that will coordinate
Address questions that are relevant to most attendees
They don't work when they're used to:
Broadcast information that could be read
Create the appearance of inclusion without enabling real input
Ensure "everyone heard it" when written documentation would suffice
When do I send an email instead of a meeting?
Effective change communication matches format to purpose:
Email for: Status updates, timeline changes, resource links, reference information
Targeted small group calls for: Role-specific questions, implementation planning, troubleshooting
Large meetings for: Decision-making that requires diverse input, cross-functional coordination, crisis response
Written Q&A for: Common questions with standard answers, policy clarification, process details
Most organizations invert this: they meet about things that should be written and write about things that need discussion.
How do I decide if a meeting is necessary?
Before scheduling your next change meeting, answer:
"What outcome requires these specific people in the same conversation at the same time?"
If the answer is "so they all hear the same information," cancel the meeting and write it down.
If the answer is "so they can discuss and resolve X together," keep the meeting but make the objective explicit.
If there's no clear answer, you're scheduling a meeting out of habit, not necessity.
What does an unnecessary meeting cost you?
Every unnecessary meeting signals that you value organizational ritual over people's time.
References & Related Reading:
1) Geimer, Leach, DeSimone, Rogelberg, Warr, "Meetings at work: Perceived effectiveness and recommended improvements" (Journal of Business Research, 2015): https://www.sciencedirect.com/science/article/abs/pii/S0148296315000879
2) ogelberg et al., "Thirty Years of Meeting Science" (Annual Review of Organizational Psychology and Organizational Behavior): https://www.annualreviews.org/content/journals/10.1146/annurev-orgpsych-031925-091223
If you're planning how to announce a change, The DANCE System gives you 29 tools for planning and communicating it in five phases, from defining the scope to keeping it in place after launch.
Related Blog Posts:
How do I brief my managers before a change announcement?
Why doesn't communicate more fix a struggling change?
