Change management

In short

Change management is the systematic process of planning, implementing and stabilising a shift in an organisation's strategy, structure, technology, processes or culture, and of helping the people affected move from the old way of working to the new one. It matters because the technical part of a change (new ERP, new org chart, a merger) is usually easier than the human part, and most failed transformations fail on adoption, not on design. Indian universities examine it in Principles of Management, Organisational Change & Development and HRM papers; it is a standing question in UGC-NET/Management, MBA entrance interviews and company placement rounds. Employers test it directly in consulting (Deloitte, EY, KPMG, Accenture), IT transformation (TCS, Infosys, Wipro), HR/OD roles and operations, because GST, digitalisation, UPI, hybrid work and large bank and corporate mergers have made change a permanent condition of Indian business.

Explained

What change management is, why change happens, and its types

• Organisational change: any alteration in an organisation's people, structure, technology, processes or strategy. Change management: the discipline of making that alteration deliberately, with least disruption and highest adoption.
• External drivers (PESTEL): policy and law (GST 2017, Companies Act 2013, labour codes, IBC 2016), economy (demand shifts, interest rates), society (consumer preferences, gig work), technology (AI, cloud, UPI, e-commerce), environment (ESG, EV transition), competition (Jio's entry reshaping telecom).
• Internal drivers: new leadership, growth or decline in profitability, mergers, poor quality or productivity, employee attrition and engagement data, system obsolescence, promoter succession in family firms.
• Planned vs emergent change: planned change is intentional and goal-directed (an ERP rollout); emergent change arises continuously from operational decisions and local adaptation (Weick & Quinn's "continuous change").
• By magnitude: *incremental / first-order* (fine-tuning within existing logic, e.g. Kaizen) vs *radical / transformational / second-order* (changing the logic itself, e.g. a bank becoming digital-first).
• Ackerman's three types: developmental (improving what exists), transitional (replacing old with a known new state), transformational (the end state is not fully known at the start — emerges).
• By content: strategic, structural, technological, process, people/behavioural and cultural change (Leavitt's four interacting variables were task, structure, technology and people); they are interdependent — changing one without the others causes misalignment.
• Greiner's growth model: organisations grow through evolutionary phases punctuated by revolutions (crises of leadership, autonomy, control, red tape), each demanding a structural change — common in Indian start-ups scaling past the founder.
• Dunphy & Stace contingency view: the right change style depends on scale and urgency — *collaborative/consultative* for incremental change with time, *directive/coercive* for crisis turnarounds (as in an IBC resolution).

Classic models and step-by-step processes

• Lewin's three-step model (1947): Unfreeze (create dissatisfaction with status quo, communicate the case for change, reduce restraining forces) → Change/Move (new structures, processes, training, pilots) → Refreeze (institutionalise through SOPs, KRAs, incentives, systems, so behaviour does not revert).
• Lewin's force field analysis: at any moment behaviour is an equilibrium between driving forces and restraining forces. Change happens when the net force turns positive — and *weakening restraining forces* is usually cheaper and less conflictual than adding pressure.
• Kotter's eight-step model: 1 create urgency; 2 build a guiding coalition; 3 form a strategic vision and initiatives; 4 enlist a volunteer army (communicate widely); 5 enable action by removing barriers; 6 generate short-term wins; 7 sustain acceleration (do not declare victory early); 8 institute change in the culture.
• ADKAR (Prosci, Jeff Hiatt) — an individual-level model: Awareness of the need, Desire to participate, Knowledge of how, Ability to apply, Reinforcement to sustain. The first element that scores low is the barrier point; work there instead of running generic training.
• Action research model (planned change cycle): problem identification → consultation with a change agent → data gathering and diagnosis → feedback to the client group → joint action planning → action → re-measurement, and loop again.
• McKinsey 7-S framework: Strategy, Structure, Systems (hard Ss) and Shared values, Style, Staff, Skills (soft Ss) must stay mutually consistent; a change in one S that leaves others untouched fails. Useful as a diagnostic checklist in exams and case interviews.
• Bridges' transition model: manage the *psychological* transition in three phases — Ending/letting go, the Neutral zone (confusion, dip in performance), New beginning. Change is external and can be dated; transition is internal and takes longer.
• Kübler-Ross change curve (adapted): shock → denial → frustration/anger → depression → experiment → decision → integration; explains the predictable performance dip after go-live.
• Other diagnostic models worth naming: Nadler-Tushman congruence model (fit between task, people, formal and informal organisation), Burke-Litwin model (transformational vs transactional factors), Judson's and Galpin's phase models, Appreciative Inquiry (4-D: discover, dream, design, destiny) as a strengths-based alternative.

Resistance to change and how it is handled

• Individual sources: habit, economic insecurity and fear of job loss, fear of the unknown, selective perception, loss of status or control, low self-efficacy about new skills, mistrust of management from past broken promises.
• Organisational sources: structural inertia, group norms and sub-cultures, limited focus of change (changing one unit only), threat to established power relationships, threat to resource allocation and expertise, union opposition, sunk costs in existing systems.
• Kotter & Schlesinger's six approaches: (i) education and communication; (ii) participation and involvement; (iii) facilitation and support (training, counselling, time off); (iv) negotiation and agreement (settlements, protected pay); (v) manipulation and co-optation (co-opting a leader of resisters) — ethically risky; (vi) explicit and implicit coercion — fast but leaves lasting resentment. Choose on speed required, expected resistance and power position.
• Resistance is diagnostic, not only an obstacle: it signals real risks, poor design or genuine losses, and legitimises engaging dissent rather than suppressing it.
• Levers that reduce restraining forces: credible two-way communication, early and visible sponsorship, pilots and quick wins, reskilling guarantees, job-security assurances where honest, "change champions" from the shop floor, redesigning incentives and KRAs to reward the new behaviour.
• Readiness assessment before launch: sponsor strength, past change history, scale of impact by group, culture, capacity to absorb (number of concurrent changes) — scored into a readiness index.

Organisation development and improvement approaches

• Organisation Development (OD): a planned, system-wide, behavioural-science-based effort, managed from the top, to increase organisational effectiveness and health through planned interventions in processes. Values: humanistic, participative, data-based, long-term.
• OD interventions by level: *individual* — coaching, sensitivity/T-group training, career planning; *group* — team building, role analysis technique, inter-group problem solving, process consultation; *organisation-wide* — survey feedback, confrontation meeting, Grid OD, structural redesign, Total Quality Management, Quality of Work Life (QWL) programmes.
• Change agent roles: internal (HR/OD head, transformation office) or external (consultant); roles range from expert and trainer to process facilitator and advocate. Needs diagnostic skill, credibility and political sense, not just technique.
• Kaizen and TQM: continuous small improvements by employees, PDCA (Plan-Do-Check-Act) cycle, quality circles, 5S, suggestion schemes — widely used in Indian auto and auto-component plants (Maruti Suzuki, Bajaj, Sundaram Clayton).
• Business Process Re-engineering (Hammer & Champy): fundamental rethinking and radical redesign of processes for dramatic improvement in cost, quality, service and speed; clean-slate rather than incremental; high failure and high retrenchment risk, so it interacts with labour law.
• Six Sigma DMAIC (Define-Measure-Analyse-Improve-Control) and Lean (waste elimination, flow, pull) are structured change methods with measurement built in; "Control" and Lewin's "Refreeze" serve the same purpose.
• Learning organisation (Senge's five disciplines): personal mastery, mental models, shared vision, team learning, systems thinking — a capacity for continuous change rather than a one-off project.
• Culture change (Schein's three levels): artefacts (visible), espoused values (stated), basic underlying assumptions (taken for granted). Real change requires shifting the third level; levers are leader behaviour, what gets measured and rewarded, recruitment and socialisation, stories and symbols.
• Agile/iterative change: short sprints, minimum viable change, feedback loops — increasingly used instead of a single big-bang go-live in IT and digital programmes.

Running a change programme: roles, communication and measurement

• Governance: executive sponsor (accountable), steering committee, change management office/transformation office, process owners, change champion network, project manager. Distinguish *project management* (scope, schedule, cost of the technical solution) from *change management* (adoption by people) — both are needed.
• Stakeholder analysis: map each group on power × interest (manage closely / keep satisfied / keep informed / monitor) and plan engagement accordingly; RACI charts fix who is Responsible, Accountable, Consulted, Informed.
• Communication plan: answer "why, why now, what it means for me, what happens if we do nothing"; use the employee's preferred channel; repeat the message many times; preferred senders are the CEO for the business case and the immediate supervisor for personal impact.
• Training and capability: needs analysis by role, role-based training, job aids, super-users, hypercare support after go-live.
• Metrics: adoption/utilisation rate, proficiency and error rates, speed of adoption, training completion, help-desk ticket trend, employee pulse scores, attrition in affected groups, and business benefits realised against the case. Sustainment is checked 3-12 months later.
• Failure statistics: the widely quoted claim that about 70% of change programmes fail (Kotter, Hammer) is much debated and not a measured universal rate — quote it as a consulting estimate, not a fact.

Indian legal, regulatory and practice framework

• Industrial Disputes Act, 1947 — Section 9A: an employer must give 21 days' notice in the prescribed form to workmen before effecting any change in conditions of service specified in the Fourth Schedule (wages, hours, shifts, grades, classification, rationalisation or technological change reducing jobs, etc.). Changing shifts or introducing automation without this notice makes the change legally challengeable.
• Retrenchment and closure: Section 25F (conditions precedent — one month's notice or pay, 15 days' average pay per completed year of service, notice to government); Sections 25M/25N/25O (establishments with 100 or more workmen — Chapter V-B — need prior government permission for lay-off, retrenchment or closure); Sections 25FF/25FFF (compensation on transfer of undertaking or closure); Section 25G (last-in-first-out within a category).
• Industrial Relations Code, 2020 consolidates the ID Act, Trade Unions Act and Standing Orders Act: it retains the notice-of-change duty and raises the prior-permission threshold to 300 workmen (several states had already raised it by state amendment). The four labour codes, enacted in 2019-2020, were brought into force on 21 November 2025; central and state rules are still being framed and differ by state, so verify the current position before relying on a threshold.
• Standing orders / certified service rules govern shift timings, transfers and discipline; a change usually needs modification of the certified standing orders.
• Structural change: Companies Act 2013 Sections 230-232 (compromise, arrangement, merger/demerger approved by NCLT with creditor and member meetings), Section 233 (fast-track merger for small companies and for a holding company with its wholly owned subsidiary), Section 66 (capital reduction); Competition Act 2002 combination approval by CCI above notified asset/turnover thresholds; IBC 2016 resolution plans force restructuring under a time-bound process; SEBI LODR Regulation 30 requires prompt disclosure of material events to stock exchanges.
• Indian change episodes commonly cited: GST implementation (2017) forcing process and IT change across all firms; demonetisation (2016) and the push to digital payments/UPI; merger of SBI with its associate banks (2017) and the Bank of Baroda-Dena-Vijaya amalgamation (2019); Tata's acquisition of Air India (2022); HDFC-HDFC Bank merger (2023); VRS at BSNL/MTNL (2019); the Maruti Manesar unrest (2011-12) as a case of change and grievance mishandling; the Covid-19 shift to remote and then hybrid work (2020 onwards).

Key points

• Change management - the structured process of moving an organisation and its people from a current state to a defined future state and making it stick.
• Lewin's model - unfreeze, change, refreeze; refreezing (systems, SOPs, KRAs) is what prevents relapse.
• Force field analysis - change occurs when driving forces exceed restraining forces; reducing restraints beats adding pressure.
• Kotter's 8 steps - urgency, coalition, vision, communication, remove barriers, short-term wins, sustain, anchor in culture.
• ADKAR - awareness, desire, knowledge, ability, reinforcement; the first element scoring 3 or below is the barrier point to fix first.
• 7-S framework - strategy, structure, systems, shared values, style, staff, skills must stay aligned through the change.
• Planned vs emergent change - deliberate project-based change vs continuous adaptation from day-to-day decisions.
• Incremental vs transformational - fine-tuning within the existing logic vs changing the logic itself (first- vs second-order).
• Bridges' transition - ending, neutral zone, new beginning; the psychological transition lags the organisational change.
• Resistance - arises from habit, insecurity, loss of power, mistrust and structural inertia; it is also useful diagnostic information.
• Kotter & Schlesinger tactics - education, participation, facilitation, negotiation, co-optation, coercion; choose by urgency and power.
• OD - planned, system-wide, behavioural-science-based effort to improve effectiveness; interventions at individual, group and organisation level.
• Change agent - internal or external facilitator who diagnoses, designs and shepherds the change; not merely a trainer.
• BPR vs Kaizen - radical clean-slate process redesign vs continuous small employee-driven improvement.
• Section 9A, ID Act 1947 - 21 days' notice to workmen for Fourth Schedule changes in conditions of service, including technological change.
• Chapter V-B - prior government permission for lay-off, retrenchment or closure at 100+ workmen under the ID Act (300 under the IR Code 2020, in force since 21 November 2025, and under earlier state amendments; rules still being framed).
• Mergers - NCLT route under Sections 230-232 of the Companies Act 2013, CCI clearance for large combinations, SEBI LODR disclosure.
• Measurement - adoption rate, proficiency, benefit realisation and sustainment checks, not just project completion.

Formulas and examples

Example 1 - Force field analysis for an ERP rollout (auto-component firm, Pune, 480 employees).

• Step 1: Net force = 16 − 17 = −1 → at launch the change will stall.
• Step 2: Act on restraints — a written no-retrenchment assurance with redeployment (5 → 3) and 40 hours of role-based training with super-users (4 → 2).
• Step 3: New restraining total = 3 + 2 + 3 + 3 + 2 = 13; net force = 16 − 13 = +3 → the change becomes feasible without adding managerial pressure.

Example 2 - Change equation on a 1-5 scale (hybrid-work policy in an IT services unit).

• Assessment: D = 4 (staff unhappy with the full return-to-office mandate), V = 4 (clear hybrid vision published), F = 2 (no concrete first steps announced).
• Change potential P = D × V × F = 4 × 4 × 2 = 32 (maximum 5 × 5 × 5 = 125).
• Resistance R = 4 on the same 1-5 scale; put on a comparable scale, R′ = 4 × 25 = 100. Since 32 < 100, the change fails.
• Intervention: a 90-day pilot in two delivery units with booking tools and team charters raises F from 2 to 5 → P = 4 × 4 × 5 = 80; pilot results and manager involvement cut R from 4 to 3 → R′ = 3 × 25 = 75.
• Now P (80) > R′ (75) → the change moves. Note how F, the cheapest variable, carried the decision.

Example 3 - ROI and payback of a GST-driven ERP change (distribution company, 120 users).

• One-time costs: licences ₹18 lakh + implementation consultant ₹12 lakh + training (120 × ₹2,500 = ₹3 lakh) + productivity dip ₹7 lakh = ₹40 lakh.
• Recurring cost: AMC and support ₹4 lakh per year.
• Annual benefits: inventory carrying cost saving ₹14 lakh + invoice error and GST penalty saving ₹6 lakh + redeployment of 4 clerical roles ₹12 lakh = ₹32 lakh per year.
• Three-year totals: benefits = 32 × 3 = ₹96 lakh; costs = 40 + (4 × 3) = ₹52 lakh.
• ROI = (96 − 52) ÷ 52 × 100 = 84.6% over three years.
• Payback: annual net operating benefit = 32 − 4 = ₹28 lakh. Year 1 leaves 40 − 28 = ₹12 lakh unrecovered; 12 ÷ 28 = 0.43 year → payback ≈ 1.43 years (about 17 months).
• Year-1 ROI alone = (32 − 44) ÷ 44 × 100 = −27.3%, which is why change business cases must be read over the full horizon.

Example 4 - ADKAR diagnosis and adoption rate (new CRM, 1,200 field staff).

• Pulse survey averages (1-5): Awareness 4.2, Desire 3.9, Knowledge 2.6, Ability 2.1, Reinforcement 3.0.
• Composite = (4.2 + 3.9 + 2.6 + 2.1 + 3.0) ÷ 5 = 15.8 ÷ 5 = 3.16.
• Barrier point = the first element at or below 3, i.e. Knowledge (2.6), followed by Ability (2.1) — so more communication (Awareness already 4.2) would be wasted spend; hands-on training, job aids and coaching are the correct interventions.
• Adoption at month 3: 846 of 1,200 staff logging daily activity = 846 ÷ 1,200 × 100 = 70.5%; target 90% by month 6 means converting about 234 more users.

Where it is used

• Consulting and transformation practices: Deloitte, EY, KPMG, PwC, Accenture and Capgemini hire "change management" and "people and organisation" consultants for ERP/SAP, S/4HANA, cloud and shared-services rollouts.
• IT services and GCCs: TCS, Infosys, Wipro, HCLTech and captive centres run large-scale reskilling, agile transformation and hybrid-work change programmes; organisational change management (OCM) is a billable stream in every ERP project.
• Banking and financial services: public-sector bank amalgamations, core banking migrations, digital onboarding, and RBI-driven compliance changes; branch-level change champions are a standard structure.
• Manufacturing and auto: Kaizen, 5S, TPM and lean cells in Maruti Suzuki's supplier base, Tata Motors, Bajaj and Ashok Leyland; shift-pattern or automation changes trigger Section 9A notices and union negotiation.
• HR and OD roles: change manager, OD specialist, HR business partner, L&D head, internal communications — responsible for readiness assessment, stakeholder plans, training and adoption metrics.
• Public sector and government programmes: GST rollout, DBT and Aadhaar-linked services, Digital India and smart-city projects, where thousands of staff change processes simultaneously.

Interview questions

• Q: What is change management and how is it different from project management? A: Project management delivers the technical solution on scope, time and cost; change management ensures the people affected adopt and sustain it. A project can finish on time and still fail if adoption is low.
• Q: Explain Lewin's three-step model with an example. A: Unfreeze — show staff why the manual billing system is costing orders; Change — implement the new system with training and pilots; Refreeze — write it into SOPs, KRAs and incentives so no one reverts to spreadsheets.
• Q: Why is force field analysis useful if you already know the change is necessary? A: It separates drivers from restraints and shows that weakening restraints — fear, skill gaps, data issues — usually moves the equilibrium more cheaply and with less conflict than increasing pressure.
• Q: What are the main sources of resistance to change? A: Individually, habit, economic insecurity, fear of the unknown and loss of status; organisationally, structural inertia, group norms, threats to existing power and resource allocation, and mistrust from past change failures.
• Q: Is resistance always bad? A: No. It often flags genuine design flaws, real losses or missing information, so engaging it improves the change; suppressing it drives resistance underground into passive non-adoption.
• Q: How would you choose between a participative and a directive change approach? A: By urgency, scale and power position (Dunphy & Stace): participative when there is time and the change is incremental, directive or coercive in a survival crisis such as an IBC resolution — accepting the cost in trust.
• Q: What is the barrier point in ADKAR and why does it matter? A: The first of the five elements scoring low; it is where adoption actually breaks, so spending on communication when the real gap is Ability wastes budget and delays the change.
• Q: Which legal requirement applies in India when you change shift timings or introduce automation that cuts jobs? A: Section 9A of the Industrial Disputes Act, 1947 requires 21 days' notice to workmen for Fourth Schedule changes; retrenchment adds Section 25F conditions, and 100+ workmen establishments need prior government permission under Chapter V-B (300 under the IR Code, 2020, in force since 21 November 2025).
• Q: Why do performance figures usually dip right after go-live? A: Employees are in Bridges' neutral zone — learning new steps while the old habits no longer apply; the dip is predictable and is managed with hypercare support, super-users and realistic targets, not by reversing the change.
• Q: How would you measure whether a change programme succeeded? A: Adoption and utilisation rates, proficiency and error rates, benefit realisation against the business case in rupees, employee pulse scores and attrition in affected groups, re-checked 6-12 months later for sustainment.
• Q: A change was declared a success at go-live but people reverted in six months. What went wrong? A: Reinforcement failed — Kotter's steps 7-8 and Lewin's refreeze were skipped: incentives, KRAs, reporting and supervisory routines still rewarded the old behaviour.
• Q: How does BPR differ from Kaizen, and when is each appropriate? A: BPR is a radical clean-slate redesign for dramatic gains, suited to a broken, uncompetitive process; Kaizen is continuous employee-driven improvement, suited to a sound process needing steady cost and quality gains at low risk.

Common mistakes

• Treating Lewin's refreeze or Kotter's step 8 as optional, and describing change as complete at go-live.
• Writing Kotter's eight steps in the wrong order or merging steps — examiners mark the sequence, especially urgency first and anchoring in culture last.
• Confusing ADKAR (individual adoption) with Kotter (organisation-level sequence), or citing one when the question asks for a diagnostic model.
• Treating the change equation C = D × V × F > R as additive; because it is multiplicative, a zero in any term kills the change.
• Discussing retrenchment or automation-driven change in Indian answers without the Section 9A notice and Chapter V-B permission requirements, or quoting the 100/300-workmen threshold as settled when state amendments and the still-evolving labour-code rules make it vary.
• Quoting "70% of change efforts fail" as an established statistic rather than a consulting estimate.
• Listing OD interventions without saying at which level (individual, group, organisation) each works, and confusing sensitivity training with team building.
• In interviews, answering only with frameworks and no stakeholder, communication or measurement plan — employers want the operating detail.

Related topics

Organisational behaviour · Leadership and team management · Organisational structure and design · Principles of management · Business environment in India · Cross-cultural management