A change forum is not simply a meeting with a better title. Used well, it is a change-management intervention that helps people make sense of the change, surface barriers, practise new ways of working and align on what must happen next. This matters because organizational change only becomes real when individuals and groups change what they do; Prosci’s ADKAR model frames this as movement through Awareness, Desire, Knowledge, Ability and Reinforcement [Prosci ADKAR Model]. (prosci.com)

Forums also build readiness. Weiner defines organizational readiness as shared commitment to implement a change and shared belief in the group’s capability to do so [Weiner, 2009]. (link.springer.com) A well-run forum gives the impacted group a live opportunity to test the “why,” understand personal impact, raise concerns and leave with clearer next steps.

A forum is a structured live engagement or learning session with a defined outcome, agenda, facilitator, prepared messages, issue-capture method and follow-up process. It sits between communication, consultation, training and adoption support. It is most useful when the change affects roles, workflows, systems, customer interactions, policies or decision rights.

Use forums early to validate impacts and hear concerns, before go-live to build understanding and practise, during implementation to manage resistance and solve adoption blockers, and after go-live to reinforce the new way of working. If the organization is genuinely consulting on a proposal, be clear about what is still open to influence; Acas notes that consultation includes considering employees’ thoughts, concerns and issues before decisions are finalized [Acas, 2026]. (acas.org.uk) If the decision is already made, do not call the session “consultation”; call it an implementation or adoption forum.

Start with the adoption objective: what should this audience understand, believe, practise or commit to by the end? Then gather the change story, impact assessment, stakeholder map, readiness data, training needs, known objections, open decisions and escalation routes. CIPD’s learning needs guidance emphasizes identifying capability gaps against current and future performance needs and involving subject matter experts, operational managers and impacted employees [CIPD Learning needs analysis, 2025]. (cipd.org)

Invite only the people needed for the outcome. Sponsors are useful when the “why” or trade-offs must be explained. People managers are essential when personal impact, coaching or reinforcement is required; Prosci’s CLARC roles describe managers as communicators, liaisons, advocates, resistance managers and coaches [Prosci CLARC, 2021/2025]. (prosci.com) Prepare a short core message, a realistic scenario, a Q&A log, an action log and a closing message that explains what will happen with the input.

A company is introducing a new CRM process for sales and customer service. Before go-live, the change manager runs separate forums for sales managers, frontline users and support teams. In the frontline forum, participants hear the reason for the change, compare the old and new workflow, practise logging a customer interaction and identify two adoption blockers: unclear ownership for duplicate accounts and missing mobile instructions. The action log assigns the data decision to the product owner and the mobile job aid to the training lead. One week later, managers receive a follow-up pack and reinforce the new workflow in team huddles. This turns the forum into an adoption loop: listen, practise, fix, reinforce.

The most common mistake is using a forum as a one-way broadcast. That undermines employee voice, which CIPD defines as people expressing views, concerns and suggestions that can influence decisions at work [CIPD Employee voice, 2026]. (cipd.org) Other mistakes include inviting too broad an audience, hiding bad news, letting senior leaders dominate, failing to distinguish fixed decisions from open questions, collecting issues with no owner, and running a single event with no reinforcement. Avoid “performative listening”: if you ask for input, show what happened to it.

Measure before, during and after. During the forum, track attendance by impacted group, participation, questions, sentiment, unresolved issues and comprehension checks. Immediately after, measure confidence, clarity and perceived readiness. After go-live, look for behavioral indicators: use of the new process or tool, reduction in workarounds, quality or cycle-time changes, support tickets, manager observations and repeat themes. PMI recommends measuring comprehension, desired behavior change and post-deployment adoption rather than relying only on communication reach [PMI, 2015]. (pmi.org)

60-minute agenda: purpose and ground rules, 5 minutes; sponsor or manager change story, 10 minutes; impact walkthrough, 10 minutes; questions and concerns, 15 minutes; practice or scenario discussion, 15 minutes; actions and close, 5 minutes.

Opening script: “Today’s session is about understanding the change, testing what it means in practice and identifying what could block adoption. Some decisions are already made; I will be clear about those. Where input can still shape implementation, we will capture it, assign an owner and report back by [date]. Questions and concerns are welcome because they help us make the change workable.”