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

TAKEAWAYS:

• Organizational structure defines who reports to whom, how work flows, and who makes decisions—critical for efficiency and adaptability.
• Contingency theory states there’s no "best" structure; it depends on size, environment, and strategy (e.g., startups vs. banks).
• Centralization vs. decentralization affects speed (decentralized = faster decisions) but risks coordination (centralized = control).
• Span of control (how many subordinates a manager oversees) impacts communication clarity and managerial workload—ideal span is 5–9.
• Matrix structures (used in tech firms like Google) combine functional and project teams but create conflict over dual reporting.
• Organizational design must align with goals, technology, and culture (e.g., NTC’s bureaucratic structure vs. Pathao’s agile teams).

1. What Is Organizational Structure?

Organizational structure is the framework that shows:

• Division of labor (who does what).
• Authority and responsibility (who decides what).
• Communication channels (how information flows).
• Coordination mechanisms (how departments work together).

Why Does Structure Matter?

• Efficiency: Clear roles reduce confusion (e.g., Nabil Bank’s structured loan approval process).
• Adaptability: Flat structures (like Daraz’s) allow faster innovation.
• Control: Tall hierarchies (e.g., NTC) ensure compliance but slow decisions.

2. Types of Organizational Structures

A. Functional Structure (U-Form)

• Definition: Groups employees by specialized functions (marketing, finance, HR).
• Example: Most Nepali banks (Nabil, Global IME) use this for expertise in each department.
• Pros:
  • Economies of scale (e.g., shared HR tools).
  • Clear career paths (e.g., from teller → branch manager).
• Cons:
  • Silos: Marketing and sales may not collaborate well.
  • Slow cross-department decisions.

mindmap
  root((Functional Structure))
    U-Form
      "Groups by function (e.g., Finance, Marketing)"
      "Pros: Expertise, efficiency"
      "Cons: Silos, slow innovation"
    Example
      "Nabil Bank: HR, Loans, Retail in separate departments"

B. Divisional Structure (M-Form)

• Definition: Divides by products, regions, or customers (e.g., Daraz’s e-commerce vs. logistics divisions).
• Example: Toyota (global regions) or Chaudhary Group (divisions like cement, FMCG).
• Pros:
  • Focused strategy per division.
  • Faster response to market changes (e.g., Daraz’s regional teams).
• Cons:
  • Duplicated resources (e.g., each division may have its own HR).
  • Conflict between divisions (e.g., Daraz’s sellers vs. buyers team).

mindmap
  root((Divisional Structure))
    M-Form
      "Groups by product/region/customer"
      "Pros: Flexibility, focus"
      "Cons: Overhead, duplication"
    Example
      "Daraz: E-commerce division vs. Logistics division"

C. Matrix Structure (H-Form)

• Definition: Dual reporting—employees report to both functional and project managers (e.g., a software engineer reports to IT and a product team).
• Example: Google (project-based teams) or Nepal’s IT firms for software exports.
• Pros:
  • Flexibility for complex projects (e.g., Ncell’s app development).
  • Cross-functional innovation.
• Cons:
  • Conflict: "Who’s my boss?" (e.g., a Daraz employee in marketing vs. a campaign team).
  • Complex coordination.

graph LR
  A["Employee"] -->|"Reports to"| B["Functional Manager (HR)"]
  A -->|"Reports to"| C["Project Manager (New App Launch)"]
  B -->|"Conflicts with"| C

D. Network Structure (Virtual/Modular)

• Definition: Outsourcing core functions to external partners (e.g., Pathao outsources driver management to gig workers).
• Example: Uber (no employees, just contractors) or Nepal’s freelance IT firms.
• Pros:
  • Cost savings (no fixed overhead).
  • Access to global talent (e.g., Daraz’s international suppliers).
• Cons:
  • Loss of control (e.g., Pathao’s driver quality issues).
  • Dependence on partners.

3. Key Design Elements

A. Centralization vs. Decentralization

B. Span of Control

• Definition: Number of subordinates a manager oversees.
• Ideal Span: 5–9 (too few = micromanagement; too many = overload).
• Example:
  • Narrow span (tall hierarchy): NTC (1 manager : 3 subordinates).
  • Wide span (flat structure): Startups (1 manager : 10+ subordinates).

graph TD
  A["CEO"] --> B["VP Operations"]
  B --> C["Regional Manager 1"]
  B --> D["Regional Manager 2"]
  C --> E["5 Team Leads"]
  D --> F["7 Team Leads"]
  label="Narrow span (NTC-style)"

C. Formalization

• High formalization: Rules, procedures, and policies are strictly defined (e.g., NTC’s engineering manuals).
• Low formalization: Flexible guidelines (e.g., Google’s "20% time" for side projects).
• Trade-off:
  • High formalization → Consistency but slows innovation.
  • Low formalization → Creativity but risks errors.

4. Contingency Theory: No One-Size-Fits-All

Contingency theory states that the best structure depends on:

1. Environment: Stable (functional) vs. dynamic (matrix).
2. Strategy: Cost leadership (centralized) vs. innovation (decentralized).
3. Technology: Routine (tall hierarchy) vs. complex (flat teams).
4. Size: Small firms (flat) vs. large firms (divisional).

Real-World Examples

5. Organizational Design Process

1. Assess the environment: Is it stable (banking) or turbulent (tech startups)?
2. Define goals: Profit (centralized) vs. innovation (decentralized).
3. Choose structure: Match to goals (e.g., matrix for R&D).
4. Implement: Train employees, update policies.
5. Evaluate: Measure efficiency, adapt as needed.

Worked Example: Kathmandu Traffic Routes

• Problem: Traffic jams due to poor coordination between police, city planners, and drivers.
• Current Structure: Decentralized (multiple agencies with no unified command).
• Solution:
  • Matrix structure: Traffic police report to both city planning and emergency response teams.
  • Tech integration: Use centralized dashboards (like Singapore’s traffic management) to monitor real-time data.
• Outcome: Faster response to accidents, reduced congestion.

## In the Real World

1. Nabil Bank’s Functional Structure

   • Idea Used: Functional (U-form) structure with clear departments (Retail Banking, Corporate Banking, Treasury).
   • How It Works: Loan officers report only to the Loan Department Head, ensuring standardized processes. This reduces errors in approvals but can slow down personalized service.
   • Nepali Context: Banks like Nabil use this because regulatory compliance requires strict procedures.

2. Daraz’s Divisional + Matrix Hybrid

   • Idea Used: Divisional (M-form) for products (e-commerce, logistics) + matrix for cross-functional teams (e.g., a product manager works with marketing, tech, and supply chain).
   • How It Works: During Big Billion Days, a single product team (matrix) coordinates with inventory (divisional) and marketing (functional) to avoid stockouts.
   • Global Parallel: Amazon uses a similar model for its AWS (cloud services) division.

3. Pathao’s Network Structure

   • Idea Used: Virtual/modular structure—no full-time drivers, just gig workers.
   • How It Works: Pathao outsources driver management, vehicle maintenance, and customer support to third parties. This keeps costs low but requires strong IT systems to track performance.
   • Risk: If a partner (e.g., bike rental service) fails, Pathao’s operations suffer (as seen during COVID-19 lockdowns).

4. NTC’s Bureaucratic Structure

   • Idea Used: Highly centralized and formalized structure with narrow spans of control.
   • How It Works: A single board makes decisions for all engineering projects, and detailed SOPs govern every task (e.g., road repair timelines).
   • Why It Exists: Nepal’s political instability and funding constraints require strict control to avoid corruption.

6. Common Mistakes in Organizational Design

1. Ignoring the Environment

   • Example: A Nepali textile firm using a matrix structure (like global brands) but failing because local suppliers are unreliable.
   • Fix: Start with a functional structure, then add flexibility.

2. Over-Centralization

   • Example: Ncell’s slow app updates because all decisions go through Kathmandu HQ.
   • Fix: Empower regional managers (decentralization).

3. Poor Span of Control

   • Example: A Daraz manager overseeing 15 subordinates, leading to miscommunication.
   • Fix: Limit to 6–8 subordinates per manager.

4. Resisting Change

   • Example: NTC clinging to paper-based records despite digital alternatives.
   • Fix: Pilot hybrid structures (e.g., digital tools for field teams).

## Exam Tip

How This Unit Is Tested

1. Definitions + Examples

   • Question Type: "Define functional structure and give a Nepali example."
   • How to Score:
     • Definition: 1 mark (e.g., "Groups employees by specialized functions").
     • Example: 1 mark (e.g., "Nabil Bank’s HR, Finance, and Loan departments").
     • Application: 1 mark (e.g., "This ensures expertise but creates silos between departments").

2. Comparisons (Tables)

   • Question Type: "Compare centralized and decentralized structures."
   • How to Score:
     • Use a Markdown table (as above).
     • Add Nepali examples (e.g., NTC vs. Himalayan Java).

3. Case Studies

   • Question Type: "How would you restructure Pathao to improve efficiency?"
   • How to Score:
     • Diagnose: "Currently uses a network structure but faces coordination issues."
     • Solution: "Introduce a hybrid matrix structure for driver management + keep outsourced logistics."
     • Justify: "Matrix allows faster response to demand spikes; outsourcing reduces costs."

4. Process Questions

   • Question Type: "Explain the steps to design an organizational structure."
   • How to Score:
     • Use a bullet list or flowchart (Mermaid).
     • Link each step to real-world examples (e.g., "Assess environment → Daraz’s dynamic e-commerce market").

5. SWOT of Structures

   • Question Type: "What are the advantages and disadvantages of a divisional structure?"
   • How to Score:
     • Advantages: Focus, flexibility (use Daraz’s regional teams).
     • Disadvantages: Duplication, conflict (e.g., Daraz’s e-commerce vs. logistics teams).

Model Answer Snippet (7+8 Marks)

Question: "Organizational effectiveness depends on proper organizational structure. Discuss the statement and explain the process of structuring an organization."

Answer: Organizational effectiveness refers to achieving goals efficiently while adapting to change. Proper structure ensures clear roles, communication, and coordination, directly impacting performance.

How Structure Affects Effectiveness:

1. Clear Roles: A functional structure (e.g., Nabil Bank) reduces confusion but may slow cross-department projects.
2. Decision Speed: Decentralized structures (e.g., Himalayan Java) allow faster innovation but risk inconsistent quality.
3. Resource Use: Divisional structures (e.g., Daraz) optimize resources per division but may duplicate costs (e.g., separate HR teams).

Process of Structuring an Organization:

flowchart TD
  A["Assess Environment"] --> B["Define Goals"]
  B --> C["Choose Structure"]
  C --> D["Implement"]
  D --> E["Evaluate & Adapt"]
  label="Step 1: Analyze stability (e.g., banking = functional; tech = matrix)"
  label="Step 2: Align with goals (e.g., NTC’s stability vs. Daraz’s growth)"

Example: Nepal’s NTC

• Current Structure: Bureaucratic (centralized, high formalization).
• Issue: Slow response to floods or landslides.
• Solution: Introduce a matrix structure for emergency teams, combining engineering (functional) and disaster response (project-based).

Conclusion: Effectiveness depends on matching structure to context. A one-size-fits-all approach fails (e.g., Pathao’s network structure works for gigs but not for corporate training).

Marking Scheme:

• Discussion: 5 marks (clear links between structure and effectiveness).
• Process: 3 marks (logical steps with examples).
• Example: 2 marks (real-world application).