A walk-around during a change is a structured visit to the place where the change is being experienced. Its purpose is to see how the change is affecting real work, hear what people understand or misunderstand, clarify roles, remove barriers, and escalate issues before they become adoption risks. This makes it different from a leadership tour, town hall, or generic communication cascade. It is a field observation, role clarification, and direct support intervention.

The practice is supported by related evidence from change management, lean, project delivery, and healthcare improvement. Prosci identifies people managers as critical to adoption because they are close to employees and perform communicator, liaison, advocate, resistance manager, and coach roles [Prosci, 2021]. (prosci.com) Lean practice similarly emphasizes going to where work happens, observing reality, asking questions, and showing respect before acting [Lean Enterprise Institute, 2023]. (lean.org)

A change walk-around is a planned, purposeful visit by a change manager, sponsor, people manager, or project/change lead to observe the changed process, system, role, or behavior in the working environment. Use it when adoption depends on people doing something differently, especially during pilots, readiness checks, go-live, stabilization, and reinforcement.

It is especially useful when survey data or status reports are too abstract, when resistance is increasing, when managers are unsure how to support their teams, or when the change introduces new roles, handoffs, digital workflows, compliance steps, or customer-facing behaviors. AHRQ’s observation guidance notes that direct observation gives evidence of how well people can use a new standard, creates a basis for coaching, identifies training needs, and reveals workflow and communication patterns [AHRQ, 2017]. (ahrq.gov)

For sponsors, walk-arounds create visible, active support. Prosci specifically lists walk-arounds as one way change managers can create opportunities for sponsors to be active and visible [Prosci, 2018/2025]. (prosci.com) For frontline managers, walk-arounds help them act as liaisons, coaches, and resistance managers rather than passive recipients of project updates [Prosci, 2021]. (prosci.com)

Start with the adoption question: “What must people understand, do, or sustain differently?” Then define the scope of the walk-around: team, site, shift, role, workflow, process step, or stakeholder group. PMI’s stakeholder guidance emphasizes mapping impacted groups and sustaining sponsors so change decisions and role-modeling are reinforced across levels [PMI, 2015]. (pmi.org)

Before the visit, prepare a short briefing for the visitors: the change purpose, the expected future-state behaviors, known concerns, escalation routes, and what not to do. Decide whether the visit will be announced. IHI notes that organizations should decide whether to announce time and place in advance and agree this with leaders, managers, and frontline staff [IHI]. (ihi.org) In low-trust or high-resistance settings, announced visits are usually better because they reduce the sense of inspection.

Materials should include a one-page observation sheet, role clarification notes, FAQs, escalation log, and a simple “you said / we did / still investigating” tracker. The tone matters: McKinsey’s research links psychological safety to supportive and consultative leadership behaviors, including soliciting input and showing concern for team members [McKinsey, 2021]. (mckinsey.com)

A regional service team is adopting a new case management system. Two weeks before go-live, the change manager and local supervisor conduct walk-arounds during three shifts. They observe that employees understand the new screens but are unclear about who owns cases that transfer between regions. During go-live week, the sponsor joins one visit to reinforce why the change matters and to hear barriers firsthand.

The walk-around reveals three adoption risks: duplicate data entry, inconsistent role interpretation, and a missing quick-reference guide. The change team updates the role matrix, adds examples to the FAQ, and asks supervisors to cover the handoff rule in daily huddles. One week later, the team revisits the same groups and checks whether the workaround has reduced. This follows the logic of observation, coaching, and feedback described in AHRQ’s implementation guidance [AHRQ, 2017]. (ahrq.gov)

Useful indicators include the number and severity of barriers surfaced, percentage of actions closed by due date, recurring themes by site or role, reduction in workarounds, fewer help desk or support tickets, improved role clarity, faster cycle time, manager confidence, and observed use of the new behavior. For higher-risk changes, combine observation data with adoption dashboards, readiness pulse results, training completion, and benefit measures.

AHRQ recommends using observation data to reveal patterns, support coaching, and inform standard work across leadership levels [AHRQ, 2017]. (ahrq.gov) PMI similarly distinguishes installed change from implemented change, where benefits depend on changed behaviors and habits [PMI, 2015]. (pmi.org)

Change:
​Team/site/shift visited:
​Date/time:
​Visitors:
​Purpose of visit:

Opening script:
“We are here to understand how the change is working in real conditions. This is not an audit of individuals. We want to see what is clear, what is difficult, and what support would help adoption.”

Observation prompts:
Expected behavior observed? Yes / No / Partly
Role clarity evident? Yes / No / Partly
Workarounds seen?
Questions or confusion heard?
Training or knowledge gap?
System, workflow, policy, or capacity barrier?
Immediate clarification provided?
Escalation required? Owner/date:

Close-out message:
“Thank you. We heard three main points: ____. We can answer ____ today. We will take away ____ and respond by ____.”