A demonstration is not a presentation with a live screen. In change management, it is a facilitated live engagement and learning intervention that helps people understand the change, see what will be different, ask questions, practise new behaviors, and agree what happens next. This matters because adoption happens through people changing how they work, not simply through a project team delivering a solution. Prosci’s ADKAR model describes successful individual change through Awareness, Desire, Knowledge, Ability, and Reinforcement [Prosci]. (prosci.com)

Demonstrations are especially useful when change feels abstract. They make the future state visible and allow managers, sponsors, and impacted employees to test whether the proposed change is understandable, workable, and credible. Gallup’s research on disruptive change also highlights the importance of trusted leadership communication and manager conversations that help employees answer, “What does this change mean for me?” [Gallup, 2024]. (gallup.com)

Run a demonstration when an impacted group needs to see, discuss, practise, or align around the change. It may be a system demo, process walkthrough, role-play, policy scenario, prototype review, manager briefing, sponsor alignment session, or post-go-live clinic.

Use it during design to validate the future workflow, before launch to build Knowledge and Ability, at go-live to reinforce expected behaviors, and after launch to remove adoption barriers. Avoid using a demonstration as a one-way announcement when the real need is consultation, decision-making, or conflict resolution. Employee voice requires people to express views and influence matters affecting their work; a demo should therefore include listening and action capture, not just broadcasting [CIPD, 2026]. (cipd.org)

Begin with the adoption outcome. Define what participants should know, believe, do, or decide by the end. For employees, the outcome might be “complete the new workflow without old workarounds.” For managers, it might be “explain the change, answer first-line questions, and escalate unresolved issues.” For sponsors, it might be “align on decisions, risks, and visible leadership actions.”

Prepare from the change impact assessment, stakeholder map, future-state process, training needs, readiness data, FAQs, known resistance points, and open decisions. PMI stresses that stakeholder engagement should go beyond listing senior people; it should identify affected stakeholders, viewpoints, influence, and actions that become part of the project plan [PMI, 2015]. (pmi.org)

Materials should include a short change story, role-based scenario, demo environment or artifacts, facilitator guide, issue log, decision log, practice exercise, feedback questions, and follow-up owner list. CDC training standards support interactive learning, Q&A, exercises, feedback, accessibility, and evaluation [CDC, 2025]. (cdc.gov)

Step 1 – Open with purpose and outcomes. State why the group is here, what will be demonstrated, what is still open, and what decisions or actions are expected. This reduces ambiguity and prevents the session from becoming a general complaint forum.

Step 2 – Connect to the reason for change. Keep the rationale short and relevant to the audience. McKinsey’s influence model highlights understanding and conviction, role modeling, skill-building, and reinforcement as important levers for changing mindsets and behavior [McKinsey, 2016]. (mckinsey.com.br)

Step 3 – Demonstrate the real work. Show the change through a realistic user, role, customer, or employee journey. GOV.UK guidance on service demos recommends setting context, showing users, walking through the action, and explaining what happens next; it also recommends rehearsing and cutting unnecessary detail [GOV.UK, 2020]. (services.blog.gov.uk)

Step 4 – Invite practice and questions. Ask participants to complete a short scenario, identify what they would do next, or compare the new workflow with the current one. Give feedback immediately. For remote groups, use breakout rooms, polls, chat prompts, or shared worksheets.

Step 5 – Surface resistance safely. Ask, “What would stop this working in your team?” and “Where will people be tempted to use the old way?” Psychological safety research emphasises that people need to feel able to speak up, ask for help, and share concerns without punishment [HBS Working Knowledge, 2023]. (library.hbs.edu)

Step 6 – Convert issues into actions. Separate questions, decisions, defects, training gaps, policy concerns, and resistance themes. Assign owners and dates. If a concern cannot be solved in the room, say how it will be reviewed.

Step 7 – Close with reinforcement. Recap the expected behavior, available support, manager actions, and next checkpoint. Reinforcement is essential because a good demo can build confidence, but adoption requires follow-through [Prosci].

A company is replacing a manual expense approval process with a new workflow tool. Before go-live, the change manager runs separate demonstrations for employees, people managers, and finance approvers. Employees practise submitting a claim, managers practise approving and rejecting with comments, and finance reviews exception handling. A sponsor opens each session by explaining why the process is changing. A scribe captures confusing policy points, system defects, and team-specific workarounds. After the session, the project team updates job aids, managers receive talking points, and unresolved policy questions go to the steering group.

Good indicators include attendance by impacted role, percentage of priority groups reached, number and quality of questions raised, confidence before and after the session, observed practice completion, unresolved issues by category, defects or process gaps identified, manager follow-up completed, usage of support materials, reduction in repeat questions, system or process adoption data, and post-go-live error or rework trends. CDC’s standards support evaluation, learner feedback, and follow-up after learners have had time to apply learning [CDC, 2025]. (cdc.gov)

Prosci. The Prosci ADKAR® Model. No publication date stated. https://www.prosci.com/methodology/adkar

Basford, T. and Schaninger, B. The four building blocks of change. McKinsey Quarterly. 11 April 2016. https://www.mckinsey.com.br/en/our-insights/the-four-building-blocks--of-change

CDC. Quality Training Standards. Centers for Disease Control and Prevention. 24 February 2025. https://www.cdc.gov/training-development/php/qts/index.html

Teinaki, V. Service demos: how to tell the story of your service. GOV.UK Services in government blog. 12 October 2020. https://services.blog.gov.uk/2020/10/12/service-demos-how-to-tell-the-story-of-your-service/

Miller, D. and Oliver, M. Engaging Stakeholders for Project Success. Project Management Institute. 1 January 2015. https://www.pmi.org/learning/library/engaging-stakeholders-project-success-11199

Barrett, H. and Kemp, A. Disruptive Change Is Hitting Leaders and Managers Hardest. Gallup. 23 May 2024. https://www.gallup.com/workplace/645152/disruptive-change-hitting-leaders-managers-hardest.aspx

CIPD. Employee voice. 6 April 2026. https://www.cipd.org/en/knowledge/factsheets/voice-factsheet/

Baskin, K. Four Steps to Building the Psychological Safety That High-Performing Teams Need. Harvard Business School Working Knowledge. 14 June 2023. https://www.library.hbs.edu/working-knowledge/four-steps-to-build-the-psychological-safety-that-high-performing-teams-need-today