Continuous improvement: test a small change and check what happened
Continuous improvement is a repeatable way to examine a problem, try a bounded change, study what happens and decide what to keep or investigate next.
Playbook
Support the ability and conditions to work differently.
New to this subject? Start here
Continuous improvement is a repeatable way to examine a problem, try a bounded change, study what happens and decide what to keep or investigate next.
Playbook
A team handoff is complete when the receiving team can understand the work, accept the relevant responsibility and take the next action.
Playbook
A process workshop should produce a shared account of current work, a defensible improvement question and an owned next test.
Playbook
Organization design connects the work an organization must accomplish with its roles, decisions, coordination, capabilities and incentives.
Playbook
Improve employee experience by investigating a specific part of working life, changing the service behind it and checking whether people can complete their work more easily.
Playbook
Connect training to specific tasks, supported practice, feedback and working conditions, then check application over time without treating 70/20/10 as a rule.
Playbook
Map new tasks to observable behaviour, assess evidence with clear limits and choose development or workplace fixes that address the actual gap.
Method
Plan a software rollout around real tasks, handoffs, permissions, practice and support, then use a bounded pilot to make the expansion decision.
Playbook
Build a candid change story around the reason, consequences, uncertainty and next actions, then check it with the people whose work will change.
Playbook
Use insights, options and experiments to change a working routine, with clear participation, decision rights, feedback and criteria for the next step.
Playbook
Use Kotter's eight steps as questions, not a recipe: build urgency from checkable evidence, involve people who know the work, and see where the model differs from ADKAR.
Framework
Treat pushback as information: sort objections into flaws, losses, workload, history and practical obstacles, check each one, and choose a fair response.
Playbook
See a new idea from the adopter's side with Rogers' diffusion theory: perceived attributes, the decision process, peer networks, adopter categories and when saying no is rational.
Framework
Use a practical workplace example to distinguish correcting an action from reconsidering the goals, rules and assumptions that guide it.
Comparison
Plan around the questions people need answered, connect messages to real work, and give feedback an owner instead of just another inbox.
Playbook
Plan a useful handover by identifying critical know-how, choosing appropriate transfer methods and checking that the next person can actually use it.
Playbook
A careful guide to Awareness, Desire, Knowledge, Ability and Reinforcement, including where the model needs support.
Framework
How to diagnose, support and sustain changes in everyday work without reducing adoption to communication.
Foundation guide
Try a different area, subtopic or format.
A person may understand a change and still be unable to act on it. Use these guides to separate questions about purpose, participation, learning, practical conditions and continued support. A model can organize the inquiry; it cannot substitute for listening and observation.