Make change workable
Understand the difficulty. Make room for the work. Learn together.
Reluctance is information—not a diagnosis. Familiar habits and assumptions can hold change back, but people may also see risks, extra work, conflicting priorities or losses the proposal has overlooked. Find out which before choosing a response.
1. Understand what makes it difficult
Involve the people doing the work and those affected—not just enthusiastic volunteers. Ask:
- What would this change make better—and harder?
- What happened with previous improvement attempts?
- What would you have to stop doing to make this possible?
- What might you lose: time, autonomy, expertise, status or security?
- What would need to be true for you to try it?
Listen without dismissing doubt as a bad attitude. Check the concerns against the work: they may reveal a design problem, a genuine trade-off or an assumption that needs testing.
2. Make room to improve
Improvement is work. If it is a priority, leadership must make room for it—not add it to an already full workload and interpret non-delivery as resistance.
Agree what will stop, be deferred, simplified or covered. Protect time for learning and testing, adjust delivery expectations and provide the authority and support needed. Include the temporary workload of changing over, not just the hoped-for future saving.
If urgent work repeatedly consumes the agreed time, investigate that pattern with the team. Rework, interruptions and competing priorities may be crowding out the work needed to change those conditions.
Do not promise the same spare time twice. Capacity for operational surprises and protected capacity for improvement serve different purposes. Both need planning. See variation, capacity and slack.
Match the help to the difficulty
- “We have no time.” Decide what will stop or be covered; protect improvement time and adjust expectations.
- “This creates more work.” Examine the whole workload, remove duplicate steps and consider temporary support during the transition.
- “We tried this before.” Review what happened, explain what is different this time and test that explanation.
- “This could make things less safe or reliable.” Investigate the concern and agree safeguards and stopping conditions before proceeding.
- “I don’t know how to work this way.” Provide practice, tools, coaching and clear responsibilities—not just an announcement.
- “Something important to us is being lost.” Be honest about the trade-off. Involve those affected in decisions and available support; do not promise that nobody will lose anything.
3. Make the first step manageable
Co-design a small, bounded test where appropriate. Agree what changes, who is responsible, the time and resources available, what should improve and what might worsen. Decide when to review, adapt or stop.
A small test is not a reason to bypass safety requirements. Some decisions have lasting consequences even at a small scale; consider those before committing.
4. Close the feedback loop
Show what happened to people’s concerns: what changed in the proposal, what did not, and why. Check whether the new arrangement is usable in everyday work—not simply whether people attended training or agreed to it.
Review implementation, results, workload and possible harm. Adapt the arrangement with the people affected. Agreement today is not a guarantee that it will remain workable as circumstances change.
What’s your next useful question?
What makes this change difficult—and what will we change to make it workable?
Return to Right problem? →Return to Right intervention? →