Unit V — Organizational Systems
35. Organizational Change
Organizational change management is the deliberate process of moving people and systems from a current state to a desired future state while managing the psychological and political resistance that naturally arises. Readiness for change depends on employees' perceived need, belief in their own capability (change efficacy), and trust in leadership's communication. Poorly managed change erodes trust for future initiatives even when the technical rollout succeeds.
- Change readiness assessment: diagnosing willingness and capability before launch
- Resistance management: addressing loss aversion, uncertainty, and self-interest
- Participation and involvement: engaging affected employees in design choices
- Communication strategy: sustained, two-way, and tailored by audience
- Change efficacy: collective belief that the group can execute the change
- Pulse-survey readiness score before go-live
- Number and nature of help-desk tickets citing confusion or refusal to use new system
- Attendance and engagement rate in change-training sessions
- Percentage of managers actively championing versus passively complying
- Post-rollout adoption rate of the new system after 90 days
Meridian Textiles, a Tirupur-based garment exporter with 2,300 employees across three plants, is implementing an integrated ERP with AI-based production scheduling to replace paper-based planning that has run for 18 years. Six weeks after go-live, only 35 percent of shop-floor supervisors are using the new system as designed; many continue parallel paper logs, citing distrust of the AI scheduler's recommendations and fear that the system will be used to judge their individual performance or eliminate their planning role. The plant heads report supervisors quietly telling operators to ignore system-generated priority sequences. The CEO, under pressure from the ERP vendor and board to show ROI, must decide how to accelerate adoption without triggering a larger walkout in a unionized workforce.
System adoption rate at week 6
35 percent of supervisors
Parallel paper logs still in use
2 of 3 plants
ERP implementation cost
Rs 6.5 crore
Union representation
68 percent of shop-floor workforce
Supervisor survey: fear of job elimination
61 percent agree
AMandate compliance with disciplinary consequences
Issue a directive that paper logs are prohibited and non-use of the ERP will be treated as a performance issue subject to warnings.
BLaunch a participative redesign of the rollout
Pause the full mandate, form a supervisor working group to co-design scheduling override rules and clarify that the AI recommends but supervisors retain final call, then relaunch with their input visible.
CIntensive communication and training campaign without structural changes
Keep the system and rules as designed, but run town halls, FAQs, and refresher training explaining benefits and job security assurances.
DPilot-and-scale with a champion plant
Concentrate effort on making one plant a visible success with volunteer supervisors and incentives, then use peer testimony to scale to the other two plants.
AMandate compliance with disciplinary consequences
Strengths
- Fast, unambiguous signal that adoption is non-negotiable
- May force short-term usage numbers up quickly
Risks
- High risk of triggering union grievance or work slowdown
- Compliance without buy-in often reverts once monitoring eases
BLaunch a participative redesign of the rollout
Strengths
- Directly addresses fear of role elimination and builds change efficacy
- Participation typically produces more durable commitment
Risks
- Slower path to full ROI and delays vendor and board expectations
- Requires skilled facilitation to avoid the group becoming a veto point
CIntensive communication and training campaign without structural changes
Strengths
- Lower cost and faster to execute than redesign
- Can correct genuine misinformation about the AI's purpose
Risks
- Does not address the real, not just perceived, threat some supervisors feel to their role
- Risk of being seen as one-way messaging rather than real listening
DPilot-and-scale with a champion plant
Strengths
- Creates credible peer proof rather than top-down claims
- Limits initial resistance to a contained, manageable group
Risks
- Slower overall timeline across all three plants
- Other plants may dismiss the pilot as not representative of their conditions
Which path should Meridian's CEO take to rebuild adoption momentum for the ERP and AI scheduler without provoking a larger labour dispute?
Issue a directive that paper logs are prohibited and non-use of the ERP will be treated as a performance issue subject to warnings.
Strengths: Fast, unambiguous signal that adoption is non-negotiable; May force short-term usage numbers up quickly. Risks: High risk of triggering union grievance or work slowdown; Compliance without buy-in often reverts once monitoring eases.
Pause the full mandate, form a supervisor working group to co-design scheduling override rules and clarify that the AI recommends but supervisors retain final call, then relaunch with their input visible.
Strengths: Directly addresses fear of role elimination and builds change efficacy; Participation typically produces more durable commitment. Risks: Slower path to full ROI and delays vendor and board expectations; Requires skilled facilitation to avoid the group becoming a veto point.
Keep the system and rules as designed, but run town halls, FAQs, and refresher training explaining benefits and job security assurances.
Strengths: Lower cost and faster to execute than redesign; Can correct genuine misinformation about the AI's purpose. Risks: Does not address the real, not just perceived, threat some supervisors feel to their role; Risk of being seen as one-way messaging rather than real listening.
Concentrate effort on making one plant a visible success with volunteer supervisors and incentives, then use peer testimony to scale to the other two plants.
Strengths: Creates credible peer proof rather than top-down claims; Limits initial resistance to a contained, manageable group. Risks: Slower overall timeline across all three plants; Other plants may dismiss the pilot as not representative of their conditions.
Set the weight of each criterion (1–5), then score every alternative (1–5). The matrix is a thinking aid, not a verdict.
| Criterion | Weight | A | B | C | D |
|---|---|---|---|---|---|
| Behavioural impact | |||||
| Employee acceptance | |||||
| Feasibility | |||||
| Cost (higher = more affordable) | |||||
| Risk containment | |||||
| Long-term sustainability |
With your current weights, alternative A scores highest. A matrix only reflects the weights you chose. Evidence, ethics, feasibility and the people affected still belong in your judgement — you decide.
Draw on Kotter's eight-step change model to assess whether a guiding coalition and short-term wins exist, Lewin's unfreeze-change-refreeze framework to judge whether the organization was adequately unfrozen, and change-efficacy and psychological-safety concepts to explain why participation reduces resistance rooted in fear rather than mere habit.
- Short term: a mandate approach (A) risks an immediate union grievance within days
- Short term: a participative pause (B) delays the board-promised ROI timeline by one to two quarters
- Long term: durable adoption requires supervisors to trust that the AI augments rather than replaces their judgment
- Long term: how this rollout is handled will shape resistance levels for every future digital initiative at Meridian
- Long term: unaddressed job-security fears can resurface as attrition of experienced supervisors even if the system is technically adopted
- What distinguishes resistance based on habit from resistance based on genuine threat to job security?
- How does participation change not just behaviour but underlying beliefs about the change?
- What would you look for in the first 30 days to know if a change effort is genuinely succeeding versus being outwardly complied with?
Change efficacy refers to:
Why are Meridian's supervisors reverting to paper logs despite the ERP mandate?
Given the risk of a union dispute and the underlying fear driving resistance, which response best balances adoption speed and sustainability?