In this article
A change management strategy connects the reason for a change with the people, capabilities, decisions, and working conditions needed to make it happen. It should explain more than the launch date of a new system or the structure of a project plan.
Five stages provide a useful practical framework: establish the reason, clarify the direction, enable people to act, build progress through learning, and embed the new way of working. The stages can overlap and may need revisiting. They are not a guarantee of success or a substitute for understanding the specific change.
This framework is also not a relabeling of a particular branded methodology. Established approaches, such as Kotter’s eight-step framework, offer additional ways to consider leadership, participation, obstacles, and sustained adoption. Choose a method that helps the work rather than forcing every situation into the same sequence.
1. Establish the reason for change
Begin with evidence. What problem, opportunity, or obligation requires a response? What happens if the organization does nothing? Which assumptions remain uncertain?
An honest case for change does not manufacture a crisis or promise that everyone will benefit equally. Acknowledge trade-offs. A new process may improve customer service while requiring employees to learn unfamiliar tasks or change established routines.
Use examples people can recognize. In an illustrative manufacturing business, repeated gaps between planning and production might cause rework and unreliable delivery dates. Show those patterns and invite the people involved to explain the conditions behind them before announcing a complete solution.
Include the emotional and practical experience of change without pretending to know how everyone feels. People may be concerned about competence, workload, job security, or the loss of a valued way of working. A communication campaign alone cannot resolve all of those concerns.
Evidence to look for: People can describe the reason in their own words, including what is known and uncertain. Questions are visible and receive a response. Repeating the official slogan is not enough.
2. Clarify the direction and decision process
Describe what should be different when the change works. Connect the desired outcome to everyday work, customers, and the organization’s purpose.
For example, “implement a new platform” describes an activity. “Give customer-facing teams a dependable view of order status” describes an intended result. The second statement helps people judge whether the implementation is actually useful.
Explain the broad path without pretending every detail is settled. Identify milestones, dependencies, decision owners, and how employees can influence the design. Separate decisions already made from those still open. Asking for participation in a closed decision damages credibility.
Make information accessible across locations, shifts, and work arrangements. US organizations operating across time zones should not rely on one live meeting to reach everyone. Use a concise written record of decisions and a dependable place for updates and questions.
Evidence to look for: Employees understand the intended outcome, their role, and how to obtain an answer when the plan is unclear. They know which decisions they can influence.
3. Enable people to work differently
Awareness and agreement do not create capability. Identify the skills, information, equipment, permissions, and capacity the new work requires.
Training should be close enough to application that people can use what they learn. Provide practice, examples, and support for common difficulties. Different roles may need different levels of preparation; one generic presentation rarely covers everything.
Examine the operating system around the change. Are targets, approval rules, incentives, and staffing compatible with the new approach? A team asked to collaborate across functions may still be rewarded only for its own departmental result.
Decide what work will stop or slow down during the transition. Temporary dual processes can create significant extra effort. If employees must maintain the old system while learning the new one, that load needs to be acknowledged and managed.
Managers also need support. Our guide to leadership development in everyday work explains how to connect learning with real decisions and organizational conditions.
Evidence to look for: People can perform the new tasks with appropriate support, and recurring obstacles have owners. Training attendance alone does not demonstrate readiness.
4. Build progress through testing and feedback
Early improvements can show whether the approach is useful and help the organization learn. Choose a bounded pilot with a meaningful outcome, a baseline, and a way to identify unintended effects.
For the order-status example, a pilot might examine one handoff between sales and delivery. Track whether the information is accurate and available when needed, whether staff must duplicate work, and what customers experience. Do not declare success simply because the software is in use.
Share what worked and what did not. A quick win should be a real improvement, not a favorable metric selected while important problems are ignored. Before expanding, check whether the pilot depended on exceptional support that cannot be sustained everywhere.
Treat objections as information to investigate. A concern may reveal a design flaw, an unresolved trade-off, a capability gap, or a different view of priorities. Listen without assuming that every disagreement is resistance or that every suggestion must be adopted.
Evidence to look for: Feedback changes the plan where appropriate. Problems are surfaced early, decisions are explained, and progress is supported by more than enthusiasm at the launch.
5. Embed the change in ordinary work
Adoption becomes more durable when the new behavior is supported by roles, routines, incentives, onboarding, and leadership decisions. Otherwise, the organization may return to the familiar approach once project attention moves elsewhere.
Assign ownership after the project closes. Update relevant process documentation and learning materials. Retire obsolete procedures deliberately so people are not left choosing between conflicting instructions.
Review what managers recognize and reward. If the organization says collaboration matters but promotes only individual output, the old pattern remains attractive. Values-based leadership helps connect stated commitments with daily choices.
Embedding does not mean freezing the new process forever. Establish a way to learn from experience and revise it when conditions change. The goal is a workable, maintained practice, not permanent loyalty to the original project plan.
Evidence to look for: New employees learn the current approach, responsibility is clear, and the organization can maintain and improve the process without the original project team driving every action.
Measure the change at several levels
Distinguish activity, adoption, experience, and outcomes. A completed training session is an activity. Correct use of a new workflow is adoption. Employees’ understanding and workload describe experience. Fewer errors or better service may be outcomes.
Use both numbers and conversations. A brief targeted check can reveal a specific difficulty; an interview can explain why it occurs. Select a frequency the organization can respond to rather than collecting feedback continuously without capacity to act.
OQM can contribute a baseline and later view of organizational conditions through eight factors. It is not a project-management system or proof that a particular initiative caused an improvement. Combine its findings with evidence specific to the change. The employee survey tool guide helps clarify those different purposes.
Lead change as an organizational responsibility
The organic perspective emphasizes conditions, relationships, and learning rather than assuming a plan can simply be imposed. This does not remove the need for deadlines, technical expertise, risk management, or difficult decisions.
Choose the stage where your current change is weakest. Is the reason unclear? Is the intended result vague? Are people unable to act? Is feedback ignored? Is ownership missing after launch?
Use that diagnosis to select the next action. Explore how OQM works or talk with us about your change process to examine the wider organizational conditions that support or obstruct it.