Diagnose Change Resistance After a Process Rollout

When teams work around a new process, pressure often turns toward training, reminders, or a stronger mandate. Those responses feel direct. They risk missing why people changed behavior. A workaround often reveals a missing local decision, an awkward handoff, unclear ownership, a system gap, or a workload constraint during one part of a day. A delivery director should begin with work people perform rather than an assumption about effort or attitude.

Name observed behavior in concrete terms. “Adoption is weak” gives nobody a place to start. “Night shift supervisors record incoming work in a local spreadsheet before entering a new process next morning” describes behavior leaders should inspect. Ask where this happens, when staff began doing so, how often, and what follows. Ask who performs each step, who receives output, and what staff are trying to protect or complete.

Do not treat a workaround as proof of wrongdoing. Someone often made a reasonable choice inside a difficult situation. A local spreadsheet helps a supervisor retain urgent details while waiting for access. A private chat compensates for a slow or unclear handoff. A paper note supports staff whose work starts away from a desk. A director need not approve every workaround. The director needs enough detail to understand why people believe a path serves work.

Start with observed examples rather than a survey question. Ask a manager to select two shifts or cases where staff used another method. Map every action in order: trigger, person, record used, decision made, handoff, and result. Keep language descriptive. “Supervisor copies urgent details into a spreadsheet at 7:10 p.m.” is stronger than “Supervisor refuses a process.” Description leaves room for evidence. Labels invite defensiveness before anyone reviews facts.

Ask what changed between an earlier workflow and a new one. A new step sometimes requires data staff do not have. A sequence sometimes delays a decision until another team starts work. A familiar record sometimes fails to reach a person who relied on an earlier record. A local manager sometimes loses authority to resolve an ordinary exception. Compare old and new paths around one real situation. Do not map an ideal future state before understanding present work.

In a fictional recovery conversation, regional operations leader Mara says, “Please make teams follow this process. Why did nobody ask regions?” Director Eli replies, “This workaround gives us a specific event to examine. Where does staff leave a new process, and what does a current shift handoff require?” Mara explains late shift managers receive urgent requests after a central support desk closes. The new process requires a central reference number before a handoff record reaches completion. Managers started using a local log so morning staff would see urgent requests.

Eli asks Mara for two recent examples, not a general account of regional frustration. One request arrived at 6:45 p.m. and needed a morning decision. Another arrived after 8 p.m. with missing information. For each case, he asks who received a request, what information existed, when a central reference number became available, and what work a morning team performed. He also asks whether staff received clear instructions for urgent work outside support desk hours. Those questions turn a complaint into a traceable sequence.

Invite people who see relevant parts of work. Include a process owner who understands an intended workflow, a change lead who knows rollout activity, local managers who see daily work, and a person able to explain relevant system behavior. Keep attendance small enough for plain speech. A room full of observers produces polished statements and few useful details. Send a short purpose note beforehand: review observed work, identify friction, and prepare decision options for responsible leaders.

During a workshop, place one situation on a wall or shared document. Begin with a trigger. Ask each person what they did, what record they used, and why a next action mattered. Mark unknowns as unknowns. If people disagree, write both accounts and identify a record or observation needed to resolve a difference. Resist a quick vote about whose description sounds persuasive. Staff gain confidence when leaders test assumptions instead of defending an early view.

Separate issues by type. One problem might involve process design, such as a required sequence unsuitable for evening work. Another might involve information, such as missing instructions for urgent cases. A local management issue might arise from uncertainty over ordinary exceptions. Rollout support might be missing where supervisors never practiced a new handoff. Categories do not settle responsibility. They help leaders choose a response suited to observed friction.

In Mara's fictional region, a group sees three separate causes. A central reference requirement delays a complete handoff after desk hours. Local managers received no agreed rule for urgent cases. Several supervisors attended training before a revised screen appeared, then continued using memory and old notes. The team avoids one large remedy. A process owner takes a proposed evening exception path for review. Mara asks two managers to test urgent case wording. A change lead schedules a short practice session using fictional practice cases.

Set a narrow observation period after a change. One week provides time to watch several shifts without claiming final answers. Ask managers to record date, time, work type, step where staff used another path, reason given, and whether a revised path supported a handoff. Keep a log brief. A complicated form creates another barrier. Review entries beside workflow records where available, then ask what people did rather than relying only on later recollection.

Use careful language with local teams. “We found a defect” risks creating an expectation before a responsible owner reaches a decision. “We heard your concern” sounds polite yet leaves no work behind. A stronger statement says, “We observed two evening handoffs where a reference number arrived after staff needed to record a request. We are reviewing an evening path and will return Tuesday with an owner and next action.” People hear what leaders saw, what happens next, and when a response should arrive.

Mara might want a broad message telling every region to stop using local logs. Eli should pause before supporting such a message. First ask whether every region faces a similar sequence and whether a workable alternative exists. Ending a workaround before an acceptable path exists often hides behavior rather than resolving friction. A targeted message for an observed group, with a contact route for similar cases, produces better information than a sweeping instruction.

Close each recovery meeting with an observation log, a workflow owner, local manager actions, and a review date. Give every action a visible verb. “Eli owns adoption” is vague. “Eli brings evening exception options to a process owner by Tuesday” gives people a checkable commitment. “Mara supports managers” stays abstract. “Mara selects two managers for evening observation and confirms their time by Friday” creates a next move.

At 7:00 p.m. next Wednesday in this fictional example, manager June receives an urgent request after a support desk has closed. She follows an approved temporary evening path, records a request in a new process with available details, and adds a case to an observation log. On Thursday morning, Mara and Eli review June's entry beside a handoff record, then decide whether wording or workflow needs another change.