Diagnosis & Feedback in OD: Tools, Models & Real-World Use

TAKEAWAYS

• Diagnosis in OD is a structured analysis of organizational health (e.g., culture, performance gaps) using models like Lewin’s Force Field or Nadler-Tushman Congruence Model.
• Effective feedback must be specific, timely, two-way, and actionable—avoiding vagueness or blame to prevent resistance.
• Data sources for diagnosis include surveys, interviews, observations, and financial metrics (e.g., NTC’s employee turnover rates).
• Feedback loops (e.g., PDCA cycle) turn diagnostic insights into change actions, but require trust and transparency to work.
• Ethical traps in feedback include bias, confidentiality breaches, or misdiagnosis (e.g., assuming low productivity = "lazy employees").
• Real-world tools: 360-degree feedback (used by Himalayan Java for leadership development) or SWOT analysis (Daraz’s market entry strategy).

1. What Is Organizational Diagnosis?

Organizational diagnosis is the systematic collection and analysis of data to identify gaps between an organization’s current state and its desired state. It answers:

• Why is performance declining? (e.g., Ncell’s customer complaints spike)
• Where are misalignments? (e.g., Pathao’s rider-manager conflicts)
• How can we fix it? (e.g., eSewa’s IT system bottlenecks)

Key Steps in Diagnosis

flowchart TD
    A["1. Define Purpose"] --> B["2. Collect Data\n(Surveys, Interviews, Documents)"]
    B --> C["3. Analyze Data\n(Quantitative: Turnover rates\nQualitative: Employee focus groups)"]
    C --> D["4. Identify Gaps\n(Compare with benchmarks)"]
    D --> E["5. Prioritize Issues\n(Urgency vs. Impact)"]
    E --> F["6. Develop Action Plan\n(OD interventions)"]

2. Models for Diagnosis

A. Lewin’s Force Field Analysis

Kurt Lewin’s model views change as a balance of driving forces (helping change) vs. restraining forces (resisting change). Example: Nepal’s traffic congestion (NTC’s challenge)

• Driving forces: New metro rail projects, bike-sharing schemes.
• Restraining forces: Lack of public awareness, political delays.

mindmap
  root((Lewin’s Force Field))
    Driving Forces
      Government policies
      Tech solutions (e.g., Pathao’s route optimization)
    Restraining Forces
      Budget constraints
      Public resistance
    Outcome
      Net force = Change (or no change)

B. Nadler-Tushman Congruence Model

This model checks 6 organizational components for alignment:

1. Work environment (e.g., Daraz’s warehouse conditions)
2. Formal organization (e.g., NTC’s hierarchy)
3. Informal organization (e.g., employee networks)
4. Individuals (e.g., skills gaps in NEPSE traders)
5. Tasks (e.g., redundant processes in banks)
6. Goals (e.g., misaligned KPIs in Chaudhary Group).

3. Data Collection Methods

4. Feedback in OD: The Bridge Between Diagnosis and Action

Feedback is not criticism—it’s structured communication that:

• Clarifies the diagnosis (e.g., "Your team’s 30% error rate is due to X").
• Involves stakeholders (e.g., NTC workers in safety feedback sessions).
• Triggers action (e.g., Kathmandu’s traffic police using feedback to redesign routes).

Characteristics of Effective Feedback

mindmap
  root((Effective Feedback))
    Specific
      "Your report had 5 typos (not 'good effort')"
    Timely
      Given within 48 hours of the event
    Two-Way
      "What challenges did you face?"
    Actionable
      "Here’s how to improve: [training link]"
    Ethical
      Confidential, non-judgmental

Worked Example: Khalti’s Customer Complaint Feedback Loop

1. Diagnosis: 20% of transactions fail due to "server timeout" errors.
2. Feedback: Khalti’s tech team shares error logs with developers and customers via a FAQ update.
3. Action: Developers prioritize fixes; customers see transparency → trust improves.

5. Common Pitfalls in Diagnosis & Feedback

6. Ethical Considerations

• Confidentiality: Never share individual feedback without consent (e.g., NEPSE trader’s performance data).
• Bias: Avoid favoring certain departments (e.g., NTC’s IT team over field staff).
• Transparency: Explain why feedback is collected (e.g., "This helps redesign your workload").

Case Study: Himalayan Java’s Ethical Feedback Fiasco

• Problem: Managers used anonymous surveys to "out" underperforming baristas.
• Outcome: Morale crashed; turnover rose 40%.
• Fix: Switched to team-based feedback with clear improvement plans.

7. Tools for Diagnosis & Feedback

In the Real World

1. eSewa’s Digital Transformation (2020–2023)

   • Diagnosis: Users complained about slow transaction times.
   • Tool: Root Cause Analysis (RCA) identified server overload in peak hours.
   • Feedback: eSewa’s tech team shared updates via WhatsApp broadcasts (two-way communication).
   • Outcome: 30% faster transactions after cloud migration.

2. Nabil Bank’s Loan Default Crisis

   • Diagnosis: 15% of loans defaulted due to poor risk assessment.
   • Tool: Nadler-Tushman Model revealed misalignment between loan officers’ goals (quotas) and customer needs (affordability).
   • Feedback: Bank introduced cross-departmental workshops (officers + economists).
   • Result: Defaults dropped to 8% in 2 years.

3. Pathao’s Rider-Manager Conflicts

   • Diagnosis: Observations showed managers yelling at riders for low ratings.
   • Feedback: Pathao rolled out anonymous rider surveys and manager training on de-escalation.
   • Impact: Rider retention improved by 25%.

Exam Tip

How to Score Full Marks on Diagnosis & Feedback Questions

1. Define clearly: Start with a one-sentence definition (e.g., "Organizational diagnosis is a systematic process to identify gaps between current and desired performance...").
2. Use models: Always name and explain at least one model (Lewin’s, Nadler-Tushman, or PDCA) with a Nepali example.
3. Structure feedback: For "characteristics of effective feedback," use a bullet list or table (like above).
4. Link to ethics: If asked about challenges, mention confidentiality, bias, or resistance and how to mitigate them.
5. Real-world tie: End with a short case study (e.g., "Like NTC’s traffic diagnosis, [organization] used [tool] to...").

Common Mistakes to Avoid:

• Describing diagnosis as "just surveys"—it’s analysis + action.
• Ignoring stakeholder involvement in feedback (examiners love this point!).
• Forgetting ethics—always mention at least one ethical consideration.