Editing Change Managment

= Change Management =
<!-- One-sentence neutral definition of the topic -->
Change management is a structured approach for preparing, supporting, and helping individuals, teams, and organizations move from a current state to a desired future state to achieve strategic or operational goals.

== Remembering (Knowledge / Recall) ==
🧠 Foundational concepts, terminology, and factual knowledge an expert should be able to recall.

=== Core terminology & definitions ===
* '''[https://en.wikipedia.org/wiki/Change_management Change Management]''' – Discipline focused on guiding organizational transitions.
* '''[https://en.wikipedia.org/wiki/Organizational_change Organizational Change]''' – Adjustment of organizational structure, culture, or processes.
* '''[https://en.wikipedia.org/wiki/Kotter%27s_8-Step_Process_for_Leading_Change Kotter’s 8-Step Model]''' – Influential framework for driving successful change.
* '''[https://en.wikipedia.org/wiki/Kurt_Lewin Kurt Lewin]''' – Social psychologist who introduced the 3-step change model.
* '''Lewin’s 3-Step Model''' – Unfreeze → Change → Refreeze.
* '''ADKAR Model''' – Awareness, Desire, Knowledge, Ability, Reinforcement.
* '''Stakeholder''' – Individuals/groups affected by or influencing change.
* '''Resistance to Change''' – Human or organizational pushback against transitions.

=== Key components / actors / parts ===
* Employees (internal change recipients)  
* Leaders and executives (sponsors, drivers)  
* Change agents / consultants  
* Project managers and PMOs  
* HR, Communications, Training teams  

=== Canonical models & frameworks ===
* '''[https://en.wikipedia.org/wiki/Kotter%27s_8-Step_Process_for_Leading_Change Kotter’s 8-Step Model]'''  
* '''[https://en.wikipedia.org/wiki/Change_management#ADKAR ADKAR Model]'''  
* '''[https://en.wikipedia.org/wiki/Lewin%27s_change_management_model Lewin’s Change Model]'''  
* Bridges’ Transition Model  
* McKinsey 7-S Framework  
* Burke–Litwin Causal Model  

=== Where this topic commonly appears ===
* MBA programs, leadership courses, organizational development  
* Mergers & acquisitions  
* Digital transformation projects  
* Healthcare, education, government, corporate restructuring  
* Process improvement (Lean, Six Sigma)  

=== Typical recall-level facts ===
* Early foundation: 1940s–1950s (Lewin)  
* Modern popularization: 1990s–2000s (Kotter, Prosci ADKAR)  
* Change failure rates often estimated at 60–70% without structured methods  

----

== Understanding (Comprehension) ==
📖 Explain underlying concepts, relationships, and theoretical frameworks.

=== Conceptual relationships & contrasts ===
* '''Change Management vs. Change Leadership''' – CM manages execution; CL inspires and directs vision.  
* '''Organizational Development vs. Change Management''' – OD is long-term cultural/behavioral shaping; CM focuses on discrete initiatives.  
* '''Technical Change vs. Adaptive Change''' (Heifetz) – Technical = known solutions; Adaptive = requires mindset/behavior shifts.

=== Core principles & paradigms ===
* People-centered transitions  
* Importance of communication and narrative framing  
* Psychological contract and employee trust  
* Motivation theory (Maslow, Herzberg) applied to change readiness  
* Urgency vs. panic (Kotter)  
* Psychological safety during transitions  

=== How it works (high-level) ===
* '''Inputs:''' Organizational strategy, problem statements, stakeholder analysis.  
* '''Processes:''' Build urgency → design change → communicate vision → remove obstacles → reinforce behaviors.  
* '''Outputs:''' Adoption, system/process changes, cultural shifts, improved KPIs.  

=== Roles & perspectives ===
* '''Executives''' – Provide sponsorship and resource alignment.  
* '''Managers''' – Translate change locally to teams.  
* '''Employees''' – Adopt new behaviors or processes.  
* '''Change Agents''' – Facilitate communication, training, and diagnostics.  

----

== Applying (Use / Application) ==
🛠️ Practical use of change management principles.

=== "Hello, World" example ===
Example of a minimal CM plan for rolling out a new software tool:
* Clarify purpose (why the change)  
* Identify stakeholder groups  
* Communicate timeline and expectations  
* Provide training sessions  
* Monitor adoption and collect feedback  

=== Core task loops ===
* Diagnose → Plan → Communicate → Enable → Reinforce  
* Stakeholder analysis and mapping  
* Risk and resistance assessment  
* Training and capability development  
* Feedback loops and continuous improvement  

=== Frequently used actions ===
* Drafting a change vision statement  
* Conducting readiness assessments  
* Creating communication plans and roadmaps  
* Tracking adoption metrics  
* Running workshops and coaching managers  

=== Real-world use cases ===
* ERP system implementation  
* Organizational restructuring  
* Remote work transition  
* Customer service process redesign  
* Healthcare policy adoption  
* Quality and compliance improvements  

----

== Analyzing (Break Down / Analysis) ==
🔬 Demonstrate deeper structural understanding, diagnosis, and evaluation of complex change scenarios.

=== Comparative analysis of major frameworks ===
* '''Kotter vs. ADKAR''' – Kotter emphasizes leadership and momentum; ADKAR emphasizes individual-level behavioral adoption.  
* '''Lewin vs. modern agile models''' – Lewin is linear; modern change requires iterative cycles.  
* '''McKinsey 7-S vs. Burke–Litwin''' – 7-S focuses on internal alignment; Burke–Litwin maps causal environmental and internal drivers.

=== Failure modes & root causes ===
* Lack of sponsorship or visible leadership  
* Poor communication or inconsistent messaging  
* Underestimating cultural barriers  
* Insufficient training or resources  
* Change fatigue from multiple simultaneous initiatives  
* Lack of measurable reinforcement or incentives  

=== Troubleshooting & observability techniques ===
* Monitor adoption KPIs (usage, quality, error rates)  
* Conduct pulse surveys or sentiment analysis  
* Use stakeholder heatmaps to identify resistance pockets  
* Run retrospective workshops to adjust the plan  
* Analyze gaps in skills or motivation  

=== Structural insights ===
* Change impacts strategy, structure, processes, rewards, people, and culture.  
* Horizontal alignment (cross-department) is as critical as vertical alignment (leadership → employees).  
* Informal networks often determine success more than formal hierarchy.  

----

== Creating (Synthesis / Create) ==
🏗️ Designing and constructing organizational change strategies.

=== Design patterns & best practices ===
* Build urgency with clarity, not fear.  
* Communicate early, often, and consistently.  
* Use multi-channel communication (written, spoken, modeling).  
* Engage middle managers—key leverage point.  
* Pilot first, scale second.  
* Design reinforcement systems (recognition, metrics, incentives).  

=== Security, governance, or ethical considerations ===
* Ethical transparency about impacts (job changes, role elimination).  
* Avoid manipulation or coercion in communication.  
* Ensure changes are accessible and inclusive.  
* Address psychological safety during transitions.  

=== Lifecycle management strategies ===
* Initiation → Planning → Execution → Reinforcement → Sustainment  
* Build feedback loops and embed habits in culture  
* Conduct post-change reviews (lessons learned)  
* Institutionalize behaviors through policies and incentives  

=== Scalability & optimization patterns ===
* Use agile change cycles (short experiments, tight feedback)  
* Standardize CM playbooks across departments  
* Leverage change networks—distributed champions  

----

== Evaluating (Judgment / Evaluation) ==
⚖️ Determine appropriateness, trade-offs, success factors, and long-term organizational value.

=== Evaluation frameworks & tools ===
* ROI of change initiatives  
* Balanced scorecard impacts  
* Adoption and utilization metrics  
* Cultural alignment measures  
* Employee engagement scores  

=== Maturity & adoption models ===
* Reactive → Managed → Defined → Integrated → Optimized  
* Organizational readiness models and benchmarking  
* Prosci CM maturity model  

=== Key performance indicators ===
* Adoption rate and speed  
* Reduction in errors or rework  
* Productivity improvements  
* Customer satisfaction changes  
* Talent retention during transformation  

=== Strategic decision criteria ===
'''Change management is essential when:'''
* Changes affect large groups or mission-critical processes  
* Behavior changes are required (not just technical changes)  
* Risk of resistance is high  
* Cultural alignment is a priority  

'''May be less necessary when:'''
* Changes are minor or reversible  
* Impacts are limited to a small, specialized team  
* Technical adjustments require minimal behavioral shifts  

=== Holistic impact analysis ===
* Successful change improves efficiency, morale, and alignment.  
* Poorly implemented change creates confusion, resistance, and turnover.  
* CM establishes trust in leadership and organizational resilience.  
* The long-term benefit: capability to adapt continuously.

----

'''Linking Guidelines'''
* Replace placeholder links with Wikipedia links where available.  
* Use: '''[https://wikipedia.org/wiki/Page_Name Descriptive link text]'''  
* Internal wiki pages: '''[[Article Name]]'''

[[Category:Management]]
[[Category:Organizational Studies]]
[[Category:MBA Concepts]]