Organizational Structure & Design: Types, Models & Real-World Impact

Core Concepts: What Is Organizational Structure?

Organizational structure defines how tasks, roles, and responsibilities are grouped and coordinated within a company. It answers:

• Who reports to whom?
• How are decisions made?
• How does work flow?

1. Definition & Purpose

• Definition: A framework that outlines roles, relationships, and reporting lines to achieve organizational goals.
• Purpose:
  • Clarifies who does what (avoids confusion).
  • Ensures efficient communication (reduces delays).
  • Helps adapt to change (e.g., mergers, tech shifts).
  • Aligns resources with strategy (e.g., Nabil Bank’s customer-centric branches).

Types of Organizational Structures

Each structure suits different business needs. Below is a comparison table of the four primary types (classic + modern):

2. Worked Example: Nabil Bank’s Structure

Nabil Bank uses a hybrid functional-divisional structure:

• Functional: HR, Finance, IT (centralized).
• Divisional: Regional branches (e.g., Kathmandu, Pokhara) with local managers for customer service.
• Why?
  • Efficiency: Centralized functions reduce costs.
  • Local adaptability: Branches tailor loans/products to regional needs (e.g., agriculture loans in Chitwan).

MERMAID DIAGRAM: Nabil Bank’s Hybrid Structure

Key Design Principles

1. Centralization vs. Decentralization

2. Span of Control

• Definition: Number of subordinates a manager directly oversees.
• Optimal Span:
  • Narrow (3–6 subordinates): Better supervision (e.g., military units).
  • Wide (7–10+ subordinates): Faster decisions but less control (e.g., Google’s flat structure).
• Example:
  • NTC: Narrow span (technical teams report to senior engineers).
  • WhatsApp: Wide span (product teams are large but autonomous).

MERMAID DIAGRAM: Span of Control

Contingency Factors: Choosing the Right Structure

No single structure fits all businesses. Three critical factors influence design:

1. Organization Size

   • Small firms (e.g., local tailors): Simple structure (owner-manager).
   • Large firms (e.g., Chaudhary Group): Complex structures (divisional + matrix).

2. Technology & Innovation

   • Routine tasks (e.g., NTC call centers): Functional structure (clear roles).
   • Innovative tasks (e.g., Himalayan Java’s new product lines): Matrix structure (cross-team collaboration).

3. Environment (Stable vs. Dynamic)

   • Stable (e.g., NEPSE stock exchange): Mechanistic (rigid rules).
   • Dynamic (e.g., Daraz during Diwali sales): Organic (flexible teams).

MERMAID MINDMAP: Contingency Factors

mindmap
  root((Organizational Structure Design))
    Size
      Small: Simple
      Large: Complex (Divisional/Matrix)
    Technology
      Routine: Functional
      Innovative: Matrix
    Environment
      Stable: Mechanistic
      Dynamic: Organic

In the Real World

1. Daraz (Nepal’s Amazon): Network Structure

• Idea Used: Network structure (outsourced logistics, third-party sellers).
• How?
  • Fulfillment: Orders handled by third-party warehouses (e.g., Delhivery).
  • Sellers: Independent merchants list products (no need for Daraz to stock inventory).
• Impact:
  • Cost savings: No capital expenditure on warehouses.
  • Scalability: Added 100+ new sellers during COVID-19.

2. Pathao (Ride-Hailing): Matrix Structure

• Idea Used: Matrix structure (functional + project-based).
• How?
  • Functional Teams: Engineering (app development), Marketing (promotions).
  • Project Teams: Temporary squads for new city launches (e.g., Pokhara expansion).
• Impact:
  • Speed: Launched in 50+ cities in 3 years.
  • Innovation: Cross-team collaboration led to Pathao Pay (digital wallet).

3. Nabil Bank: Hybrid Functional-Divisional

• Idea Used: Hybrid structure (centralized functions + decentralized branches).
• How?
  • Centralized: IT, Risk Management (headquartered in Kathmandu).
  • Decentralized: Branch managers approve local loans (e.g., SME financing in Biratnagar).
• Impact:
  • Customer trust: Local managers understand regional needs (e.g., agricultural loans in Terai).
  • Efficiency: Centralized IT reduces branch-level tech costs.

Exam Tip

How This Unit Is Tested (TU/PU/NEB Pattern)

1. Definitions & Differences (2–4 marks):

   • Expect questions like: "Distinguish between functional and divisional structures with examples from Nepali businesses."
   • Key: Use the comparison table above and cite real firms (e.g., NTC vs. Daraz).

2. Scenario-Based Questions (5–8 marks):

   • "A new e-commerce startup in Nepal has 50 employees. Recommend an organizational structure and justify your choice."
   • Approach:
     • Identify size (small), innovation focus → Functional or Simple structure.
     • If scaling fast → Matrix (like Pathao).
     • Use contingency factors (e.g., "dynamic environment → organic structure").

3. Diagram Interpretation (3–5 marks):

   • "Analyze the following organizational chart and identify the structure type."
   • Tip: Look for:
     • Single reporting line → Functional.
     • Dual reporting → Matrix.
     • Outsourced boxes → Network.

4. Case Study Application (8–10 marks):

   • "How does Nabil Bank’s structure help it serve rural customers?"
   • Structure:
     1. Identify structure type (hybrid functional-divisional).
     2. Link to contingency factors (decentralized branches for local needs).
     3. Real-world impact (e.g., higher loan approval rates in rural areas).

Common Mistakes to Avoid

• Vague examples: Don’t say "a bank"; say Nabil Bank’s branch model.
• Ignoring contingency factors: Always explain why a structure is chosen (e.g., "Daraz uses a network structure because it needs scalability").
• Overcomplicating diagrams: Stick to 3–4 levels in org charts for exams.

Quick Revision Checklist

Before the exam, ensure you can: ✅ Define centralization/decentralization and give a Nepali example. ✅ Draw functional vs. divisional structures and label 3–4 roles. ✅ Explain how Pathao’s matrix structure enables fast expansion. ✅ Link NTC’s structure to its stable environment. ✅ Calculate span of control in a given scenario (e.g., "A manager has 8 subordinates—is this narrow or wide?").

Final Note: Organizational structure is not static—companies like Daraz and Pathao evolve their structures as they grow. Always relate theory to real-world adaptability.