Organizations often announce a change as if communication alone will make it happen. In practice, people need to understand the reason, know what is expected, have the tools to do the work and receive feedback about whether the change is succeeding. Change is easier to manage when the proposed benefits can be tested.
The core idea
Rather than assuming a framework mechanically predicts behavior, treat change models as checklists for planning and communication. The Plan–Do–Check–Act cycle is particularly useful for modest, reversible improvements, while larger transformations may need formal governance and extensive stakeholder engagement.
How to apply it
- State the problem and why remaining unchanged has a cost.
- Map who will be affected and which tasks, decisions or resources will change.
- Choose a small test group and define what success and failure would look like.
- Train participants, support the pilot and collect both measurable outcomes and qualitative feedback.
- Review evidence, adjust the approach and communicate the reasons before a wider rollout.
A workplace example
A firm introduces a new incident-reporting form. The project team pilots it with one site, tracks submission quality and completion time, and interviews frontline users. Their feedback shows that a required field is confusing. The form is corrected before wider deployment rather than asking every user to work around the problem.
What to watch out for
Some changes are legally mandatory or safety-critical and cannot be treated as optional experiments. Pilot only where it is safe and permitted. Avoid equating initial compliance with long-term adoption and maintain a route for users to raise issues.
Practice and reflect
For one upcoming change, write a one-sentence hypothesis and identify a safe pilot group.