Change Management turns an improvement from a technical solution into adopted work. It plans stakeholder engagement, communication, training, readiness, resistance response, reinforcement, and sustainment.
Definition
Change Management is the structured approach used to move people, teams, and organizations from a current state to a desired future state. It includes understanding impacts, engaging stakeholders, planning communication, building knowledge and ability, managing resistance, and reinforcing adoption.
In Lean Six Sigma, change management is what helps a new process, control, standard, metric, or system become the normal way of working. Without it, technically correct solutions often fail in practice.
History
Change Management developed from organizational development, project management, human behavior, quality deployment, and transformation work. As organizations implemented new systems and improvement methods, they learned that technical implementation and human adoption require different but connected plans.
Today change management is commonly paired with Lean, Six Sigma, digital transformation, ERP implementation, safety programs, organizational redesign, and culture change. Models such as ADKAR and Kotter provide common language, but the core work is practical: help people understand, adopt, and sustain the change.
When to Use
Use Change Management when a project changes how people work, make decisions, use systems, follow standards, measure performance, interact with customers, or coordinate across functions. It is especially important when the change affects many people, introduces new technology, changes roles, removes old habits, or faces likely resistance.
Small local improvements may need only simple communication and coaching. Larger changes need formal impact analysis, stakeholder planning, training, readiness checks, support channels, and sustainment metrics.
Step-by-Step
- Define current and future state. Clarify what is changing, why, who is affected, and what behavior is expected.
- Assess impact. Identify changes to roles, workload, skills, tools, metrics, routines, decision rights, and risks.
- Analyze stakeholders. Map affected groups, influence, support level, concerns, and engagement needs.
- Build sponsorship. Align leaders and managers on the case for change, priorities, and visible actions.
- Plan communication. Define messages, channels, timing, feedback loops, and who communicates to whom.
- Plan training and support. Provide job aids, practice, coaching, access, and help during transition.
- Manage resistance. Listen for barriers, address legitimate concerns, and respond to behavior that blocks adoption.
- Measure adoption. Track actual use, proficiency, process performance, and sustainment rather than only completion milestones.
- Reinforce and stabilize. Update standard work, audits, metrics, leader routines, and recognition so the new method holds.
Examples
- Control plan rollout: A plant updates inspection frequencies after a customer issue. Change management covers affected inspectors, training, system changes, supervisor checks, and audit follow-up.
- ERP process change: A team changes purchasing workflows. Stakeholders receive role-specific communication, practice sessions, floor support, and adoption metrics.
- Lean daily management: A site introduces tier meetings and visual boards. Managers are coached on meeting behavior, escalation, and problem-solving questions.
- Service process redesign: A call center changes case routing. The plan includes agent training, customer messaging, queue monitoring, and supervisor coaching.
Common Pitfalls
- Starting too late. Change planning should begin while the solution is being designed, not after launch.
- Equating communication with adoption. People may hear the message and still lack desire, knowledge, ability, or reinforcement.
- Ignoring managers. Local managers determine whether priorities and behaviors change in daily work.
- No impact assessment. Hidden workload, role, or metric changes can create resistance.
- Training without practice. Knowledge does not become ability without real support and feedback.
- No sustainment plan. Old habits return when reinforcement and ownership are weak.