July flash sale
Resistance is information about identity, incentives, trust, status, workload, prior experience, and perceived risk. This workshop helps change leaders map those conditions before selecting an intervention. It supports Kanban's evolutionary approach by replacing a generic communication plan with evidence, participation, and bounded experiments.
Official reference: Kanban University Change Leadership Masterclass. Course names, prerequisites, credentials, platform features, and award rules can change; confirm them on the official page for the class or credential you are considering.
Frame a concrete change
Describe the current behavior, the proposed policy or practice, the customer or worker problem it addresses, and the evidence available. Avoid labels such as 'people resist Kanban.' A team may accept visualization but oppose a public metric because it has previously been used for performance ranking. Specificity changes the intervention.
Map affected groups and losses
For each group, record what they may gain, lose, misunderstand, or fear. Consider decision authority, professional identity, predictability, workload, autonomy, reputation, and access to information. Include informal influencers and people who must operate the new policy, not only executives named on an organization chart.
Test assumptions through listening
Use short interviews and observation. Ask what problem people see, what they believe will happen, which prior changes shape their view, and what evidence would increase confidence. Do not use listening sessions to sell a finished plan. Update the map when the evidence challenges the sponsor's story.
Choose a proportionate intervention
Options include co-designing the policy, changing language, protecting data from misuse, training, piloting with volunteers, making displacement visible, securing leader behavior, or reducing simultaneous change. Start with the smallest intervention that can test the causal assumption while preserving safety.
Service walkthrough: Kanban Change Leadership
A leader wants public aging charts, but the team expects them to become individual performance measures. The change leader documents that risk, agrees a data-use policy, displays work-level rather than person-level information, and pilots the review for one work type. Trust improves because the intervention addresses the real concern instead of repeating that transparency is mandatory.
Review adoption and system outcomes
Track use, policy exceptions, decision quality, workload, customer outcomes, and narrative feedback. Compliance during a launch week does not prove adoption. Ask whether the change survives pressure and whether people can explain its purpose. Adapt or stop when harm or unsupported assumptions appear.
Use this Kanban Change Leadership worksheet
| Group | Perceived loss | Evidence needed | Possible intervention |
|---|---|---|---|
| Team members | Autonomy or safety | How metrics will be used | Data-use policy and co-design |
| Managers | Decision authority | New role in the system | Cadence and policy ownership |
| Customers | Access or responsiveness | Service expectation | Pilot and feedback |
| Shared service | Unplanned workload | Demand and capacity evidence | Entry policy and allocation |
How a team can apply Kanban Change Leadership
- Describe one observable change.
- Map formal and informal stakeholders.
- Name possible losses without judging them.
- Interview people before selecting the response.
- Pilot a reversible intervention.
- Review behavior and outcomes under normal pressure.
A month of deliberate practice with Kanban Change Leadership
During the first week, use Kanban Change Leadership: Resistance-Mapping Workshop to establish a shared boundary and baseline. Begin with this action: Describe one observable change. Invite the people who request, perform, manage, and receive the work; their different views will reveal assumptions that a board or dashboard cannot settle alone. Record definitions, missing data, known exceptions, and current customer consequences. Do not change several policies during the baseline week, because the service needs a credible comparison for the experiment that follows.
During weeks two and three, complete these actions: Map formal and informal stakeholders. Name possible losses without judging them. Interview people before selecting the response. Select one policy experiment that is within the group's authority, state why it should influence the observed behavior, and name a safety boundary for quality, workload, compliance, or customer harm. Keep unrelated changes visible. Use the working table above during the relevant cadence so the resource becomes part of a decision rather than a document that people read once.
During week four, complete the remaining actions: Pilot a reversible intervention. Review behavior and outcomes under normal pressure. Compare the new evidence with the baseline, ask affected customers and service participants what changed, and look for displaced delay outside the original boundary. Decide explicitly to keep, adapt, stop, or extend the experiment. Store the decision beside the policy and link back to the Kanban University Change Leadership Masterclass, noting the access date, so future reviewers can distinguish official guidance from the local interpretation used in this service.
Build formal capability around Kanban Change Leadership
Develop the relevant foundations through Kanban System Design training, Kanban Systems Improvement training. Continue with coaching questions for WIP resistance, improvement experiment canvas. Choose the path that matches your service responsibility and apply the learning with the people who operate and use the service.
Questions that keep Kanban Change Leadership evidence-based
- Which customer or service decision should this Kanban change leadership workshop help us make?
- What evidence do we have, and where are the measurement boundaries unclear?
- Which policy or behavior is within our authority to change?
- What unintended consequence should we watch during the experiment?
- When will we review the outcome and decide to keep, adapt, or stop?
