Organizational changeUnit 1011 min read
Case Studies & OD Applications: Real-World Change in Action
Unit 10 of Organizational Change explores how OD theories are applied through real-world case studies, analyzing successful (and failed) change initiatives in Nepali and global firms. Learn to diagnose organizational challenges, evaluate intervention strategies, and link academic models to practical outcomes—using exam
TAKEAWAYS:
- Case studies bridge theory and practice: Real-world examples (e.g., Nabil Bank’s ATM adoption) show how Lewin’s change model or Kotter’s 8-step framework are actually implemented—with messy human factors.
- OD interventions have measurable outcomes: Techniques like survey feedback (used by Himalayan Java) or team-building (applied at Chaudhary Group) can be quantified (e.g., 20% productivity gain post-intervention).
- Failure is a case study too: Pathao’s early rider protests (resistance to gig-work changes) teach more than successes—analyze why change backfired (e.g., lack of communication).
- Ethics and power shape change: NEPSE’s 2020 trading halt case reveals how regulatory power and cultural norms (e.g., "insider favoritism") derail even well-intended OD.
- Contemporary issues demand OD: Climate change (e.g., Daraz’s carbon-neutral delivery pilots) and AI adoption (e.g., Ncell’s chatbot rollout) are modern OD challenges.
- You’ll be tested on analysis: Exams ask how a case applies a model (e.g., "Explain Kotter’s steps in Daraz’s warehouse automation using evidence from the case").
1. Why Case Studies Matter in OD
OD isn’t just theory—it’s about solving real problems. Case studies help you:
- See models in action: Lewin’s Unfreeze-Change-Refreeze isn’t abstract when you trace how Nabil Bank unfroze teller-based services before rolling out mobile banking.
- Spot patterns: Resistance to change often follows the same scripts (e.g., employee fear of job loss at Himalayan Java during automation).
- Learn from mistakes: Kathmandu’s traffic congestion isn’t just a transport issue—it’s a failed OD intervention where stakeholder buy-in collapsed.
IMAGE: "Nabil Bank mobile banking app interface" | "Step 1: Unfreezing old teller-based services"
(Shows the app’s onboarding flow, highlighting how the bank’s OD team used customer surveys to identify pain points in branch visits.)
2. How to Analyze a Case Study
Use this 5-step framework to dissect any case (including exam questions):
flowchart TD
A["1. Identify the Problem"] --> B["2. Map the Change Model Used"]
B --> C["3. Diagnose Resistance Forces"]
C --> D["4. Evaluate Interventions"]
D --> E["5. Assess Outcomes & Ethics"]
E -->|"Loop back"| AWorked Example: Daraz’s Supplier Onboarding Crisis
Problem: Daraz’s rapid growth led to supplier complaints about delayed payments and unclear quality standards. Model Used: Kotter’s 8-Step Change Model (with gaps). Resistance:
- Structural: Suppliers lacked digital literacy for Daraz’s new ERP system.
- Cultural: Traditional wholesalers resisted "Daraz’s dictation" of packaging standards. Interventions:
- Short-term: Hired OD consultants to run cross-functional workshops (intervention: Team Building).
- Long-term: Partnered with local NGOs to train suppliers (intervention: Education & Communication). Outcome: 35% supplier retention rate post-intervention (vs. 15% industry average).
Exam Tip: Always ask:
- Which OD model fits best? (Lewin? Kotter? ADKAR?)
- What resistance was overlooked? (e.g., Daraz ignored supplier unions’ power).
- Were ethics considered? (e.g., Did Daraz’s training disproportionately help urban suppliers?)
3. Real-World OD in Nepali Companies
| Company | Change Initiative | OD Model/Intervention Used | Outcome | Lesson for Exams |
|---|---|---|---|---|
| Nabil Bank | Shift from branch banking to mobile | Lewin’s Unfreeze-Change-Refreeze + Survey Feedback | 40% reduction in branch visits | Key: Used data-driven diagnosis to identify pain points. |
| Himalayan Java | Factory automation (2018) | ADKAR Model (Awareness → Desire → Action) + Job Redesign | 25% cost savings, but 10% employee turnover | Key: Failed to address psychological safety during refreezing. |
| NTC | Smart meter rollout (2020) | Kotter’s Model + Stakeholder Analysis | 60% adoption in Kathmandu Valley | Key: Success came from pilot testing with consumer groups. |
| Pathao | Rider gig-work model (2017) | Force Field Analysis (Lewin) | Initial protests, now unionized riders | Key: Power imbalance (company vs. riders) led to resistance. |
IMAGE: "Daraz supplier portal dashboard" | "Intervention: Education & Communication to reduce resistance"
(Shows the portal’s training modules, highlighting how Daraz used gamified quizzes to improve supplier compliance.)
4. Global Cases: Lessons from Google & Toyota
Case 1: Google’s Project Aristotle (Culture Change)
- Problem: High turnover in engineering teams despite perks.
- OD Approach:
- Used Action Research (intervention: Survey Feedback).
- Found "psychological safety" was the #1 predictor of team success.
- Outcome: Redesigned onboarding to emphasize vulnerability-based trust.
- Exam Link: Connect to Schein’s Organizational Culture Model (artifacts → espoused values → basic assumptions).
Case 2: Toyota’s Lean Transformation (1990s)
- Problem: US plants had high defect rates vs. Japan.
- OD Approach:
- Diagnosis: Used Process Consultation to map workflows.
- Intervention: Quality Circles (employee-led problem-solving).
- Outcome: Defect rates dropped 50% in 2 years.
- Exam Link: Tie to Lewin’s Force Field Analysis (driving forces: quality demand; restraining: union resistance).
5. Contemporary OD Issues in Nepal
A. Digital Transformation (eSewa, Khalti)
- Challenge: Low financial literacy among users.
- OD Intervention: Education & Communication (e.g., Khalti’s "Digital Didi" campaign).
- Ethical Dilemma: Does gamification (e.g., cashback rewards) exploit behavioral biases?
B. Climate Change Adaptation (Nepal Tourism Board)
- Challenge: Trekking routes degraded by overuse.
- OD Approach:
- Diagnosis: Used SWOT Analysis to identify tourist vs. local guide conflicts.
- Intervention: Conflict Resolution (mediation workshops).
- Outcome: 20% reduction in illegal trekking routes.
C. AI in Customer Service (Ncell, NMB Bank)
- Challenge: Employees feared job loss from chatbots.
- OD Failure: Ncell’s 2021 bot rollout had no refreezing phase—led to union strikes.
- Lesson: Always use ADKAR to manage employee desire for change.
6. How to Answer Case Study Questions in Exams
Question Type: "Analyze how Kotter’s 8-Step Model applies to Nabil Bank’s mobile banking launch." Step-by-Step Answer Framework:
Step 1: Create a Sense of Urgency
- Evidence: Nabil Bank’s survey showed 60% of customers wanted 24/7 banking.
- OD Link: Kotter’s Step 1 = Diagnosis (using survey feedback).
Step 2: Build a Guiding Coalition
- Evidence: Cross-functional team (IT, marketing, operations) led the project.
- OD Link: Power & Politics (avoiding silos).
Step 3: Develop a Vision
- Evidence: "Banking Anytime, Anywhere" slogan.
- OD Link: Vision Statement as a change catalyst.
Step 4: Communicate the Vision
- Evidence: SMS blasts + branch posters.
- OD Link: Communication Intervention (but failed to address rural digital divide).
Step 5: Empower Broad-Based Action
- Evidence: Tellers trained as "mobile banking ambassadors."
- OD Link: Role Redefinition (intervention).
Step 6: Generate Short-Term Wins
- Evidence: First 3 months saw 50,000 new mobile users.
- OD Link: Reinforcement (positive feedback loop).
Step 7: Consolidate Gains
- Evidence: Phased rollout (Kathmandu → provinces).
- OD Link: Pilot Testing (Lewin’s Change phase).
Step 8: Anchor in Culture
- Evidence: Mobile banking now in Nabil’s core values.
- OD Link: Refreezing (Schein’s basic assumptions).
Common Mistakes:
- ❌ Describing the case without linking to models.
- ❌ Ignoring resistance (e.g., "employees resisted" is vague—specify why).
- ❌ Forgetting ethics (e.g., Did Nabil Bank’s SMS blasts exclude illiterate users?).
7. Case Study: Kathmandu’s Traffic Management Reform
Problem: 3-hour daily gridlock in 2018 (cost: $100M/year). OD Approach:
- Diagnosis: Used Stakeholder Analysis to map:
- Drivers (wanted faster routes).
- Rickshaw pullers (feared job loss from metro).
- Nepal Police (lacked resources).
- Intervention:
- Conflict Resolution: Mediated between rickshaw unions and metro planners.
- Education: "Traffic Awareness" campaigns in schools.
- Outcome: 25% reduction in congestion (but metro delays persist due to political resistance).
Exam Tip: Always ask:
- Who were the key stakeholders? (Power/Interest Matrix)
- What interventions were missing? (e.g., Lack of incentives for carpooling).
8. Exam Tip: How to Score Full Marks
- Structure: Use the 5-step analysis framework above.
- Models: Name at least one OD model per case (e.g., "This fits Lewin’s Change phase because...").
- Evidence: Quote specific numbers (e.g., "35% supplier retention").
- Critique: Discuss limitations (e.g., "The case ignores political resistance from unions").
- Ethics: End with a moral question (e.g., "Was it ethical to lay off 10% of Himalayan Java’s workforce?").
Sample Answer Starter:
"The case of Nabil Bank’s mobile banking launch exemplifies Kotter’s 8-Step Model, particularly in Steps 3–5. The bank’s vision of ‘Banking Anytime, Anywhere’ (Step 3) was communicated via SMS blasts (Step 4), but the lack of multilingual support in rural areas created a communication gap, a common pitfall in Education & Communication interventions (Schein, 2010). Resistance from tellers (Step 5) was managed through role redefinition, though this led to a 15% turnover in branch staff—highlighting the ethical dilemma of balancing efficiency with employee welfare."
In the Real World
- eSewa’s Digital Push: Used ADKAR to train merchants, but failed to address trust issues in rural areas (where eSewa agents were seen as "government spies").
- Daraz’s Warehouse Automation: Applied Lean Six Sigma to cut order processing time by 40%, but ignored union power, leading to strikes.
- Ncell’s Chatbot "Ncell Bot": Rolled out without refreezing, causing customer service reps to protest—showing how Kotter’s Step 8 is often skipped.
Worked Example Tie-In:
Imagine you’re advising Ncell on their chatbot rollout. Using Lewin’s Force Field Analysis, you’d identify:
- Driving Forces: Cost savings ($2M/year), 24/7 customer support.
- Restraining Forces:
- Employee fear (job loss).
- Technical limits (Nepali language nuances).
- Intervention: Run focus groups with call-center staff (intervention: Survey Feedback) to co-design the bot’s handoff protocol.
Final Checklist for Exam Prep
- Memorize 3–4 case studies (Nabil Bank, Daraz, NTC, Pathao).
- Master 2 models per case (e.g., Kotter + ADKAR for Nabil Bank).
- Practice critiques: For every success, ask, "What went wrong?"
- Ethics angle: Always end with a moral question (e.g., "Was the change fair?").
- Visuals: Sketch a force field diagram or stakeholder map for each case.
pie
title Stakeholder Analysis: Kathmandu Traffic Reform
"Manage Closely (High Power, Low Interest)" : 20
"Keep Satisfied (High Power, High Interest)" : 30
"Keep Informed (Low Power, High Interest)" : 30
"Monitor (Low Power, Low Interest)" : 20Based on the TU BBM syllabus for Organizational change (ELE224), unit 10.
Discussion
Loading…