Organizing & Departmentalization: Structures, Types & Real-World Cases

TAKEAWAYS:

• Organizing is the process of arranging resources (people, tasks, technology) to achieve goals efficiently, often visualized as a hierarchical structure (trees) or process flow (mermaid).
• Departmentalization groups jobs by function, product, customer, location, or process, each with distinct trade-offs (e.g., functional silos vs. cross-functional flexibility).
• Functional departmentalization (e.g., HR, Finance) is common in small firms but can create communication bottlenecks; product-based (e.g., Daraz’s electronics vs. groceries teams) improves focus but increases costs.
• Location-based (e.g., NTC’s regional offices) and customer-based (e.g., banks’ retail vs. corporate divisions) structures adapt to geographic or market needs but may duplicate resources.
• Process-based (e.g., Toyota’s assembly line) optimizes workflows but requires high standardization.
• Hybrid models (e.g., matrix structures in consultancies) combine multiple types but risk conflict and ambiguity.

1. What Is Organizing?

Organizing is the second function of management (after planning) that:

• Groups activities into departments or teams.
• Assigns authority/responsibility (who does what, who reports to whom).
• Coordinates resources (people, tech, finances) to achieve goals.
• Creates structure (e.g., flat vs. tall hierarchies).

Why Organize?

• Efficiency: Avoids duplication (e.g., one HR team for all employees).
• Accountability: Clear roles reduce confusion (e.g., who handles customer complaints?).
• Adaptability: Structures like matrix organizations allow flexibility (e.g., Daraz’s regional + product teams).
• Scalability: Helps grow from a startup (e.g., Pathao’s early flat structure) to a multinational (e.g., Nabil Bank’s layered hierarchy).

2. Approaches to Organizing

Organizations use three primary approaches, each with pros/cons:

MERMAID: Functional vs. Divisional Structure

3. Departmentalization: Types and Examples

Departmentalization groups jobs to improve coordination. The five main types are:

A. Functional Departmentalization

• Definition: Groups by specialized functions (e.g., HR, Marketing, IT).
• Example:
  • Nepal: NTC (Technical, Finance, HR departments).
  • Global: Google (Engineering, Sales, Legal teams).
• When to Use: Small/medium firms, stable environments.
• Pros:
  • Economies of scale (shared resources).
  • Clear career paths (e.g., IT specialist → IT manager).
• Cons:
  • Silos: Marketing and IT may not collaborate well.
  • Slow to adapt to change (e.g., a bank’s rigid functional structure struggles with fintech disruptions).

B. Product/Service Departmentalization

• Definition: Groups by products or services (e.g., smartphones vs. laptops).
• Example:
  • Nepal: Daraz (Electronics, Groceries, Fashion teams).
  • Global: Unilever (Detergents, Personal Care, Food divisions).
• When to Use: Diverse product lines, large firms.
• Pros:
  • Focused teams (e.g., Daraz’s electronics team knows consumer trends).
  • Faster decision-making (e.g., a new laptop launch).
• Cons:
  • Duplication: Each team may have its own HR/Finance.
  • Higher costs (e.g., separate marketing for each product).

MERMAID: Product-Based Structure (Daraz)

C. Customer Departmentalization

• Definition: Groups by customer type (e.g., retail vs. corporate).
• Example:
  • Nepal: Nabil Bank (Retail Banking, Corporate Banking, SME Banking).
  • Global: Starbucks (Retail, Foodservice, eCommerce teams).
• When to Use: Diverse customer needs (e.g., banks serve individuals vs. businesses).
• Pros:
  • Tailored services (e.g., corporate loans vs. personal loans).
  • Strong customer relationships.
• Cons:
  • Overlap: Retail and corporate banking may share branches.
  • Complex coordination.

D. Geographic/Location Departmentalization

• Definition: Groups by regions or locations (e.g., Kathmandu vs. Pokhara offices).
• Example:
  • Nepal: NTC (Central Office + 7 Regional Offices).
  • Global: Coca-Cola (Asia, Europe, Americas divisions).
• When to Use: Large geographic spread, local regulations (e.g., NTC’s regional offices handle local complaints).
• Pros:
  • Local responsiveness (e.g., NTC’s Pokhara office knows regional power issues).
  • Compliance with local laws.
• Cons:
  • Redundancy: Each region may have its own HR.
  • Higher management costs.

MERMAID: Geographic Structure (NTC)

E. Process Departmentalization

• Definition: Groups by workflow steps (e.g., manufacturing stages).
• Example:
  • Nepal: Himalayan Java (Coffee farming → roasting → packaging).
  • Global: Toyota (Assembly line: welding → painting → final assembly).
• When to Use: High-volume, standardized processes (e.g., factories, call centers).
• Pros:
  • Efficiency: Specialized steps (e.g., Toyota’s assembly line).
  • Easy to monitor quality.
• Cons:
  • Rigid: Hard to adapt to custom orders.
  • Worker boredom (repetitive tasks).

Toyota’s process-based departmentalization (Image: Archive of Fiat Historic Centre (Centro Storico Fiat), Public domain, via Wikimedia Commons)

4. Choosing the Right Departmentalization

Worked Example: Pathao’s Growth

• Early Stage (2015): Flat, functional structure (Operations, Tech, Customer Support).
• 2018 (Expansion): Added geographic departments (Kathmandu, Pokhara, Lalitpur teams).
• 2020 (Diversification): Product-based teams (Ride-hailing, Food Delivery, Logistics).
• Result: Faster adaptation but higher coordination costs.

Decision Framework:

## In the Real World

1. Nabil Bank’s Customer Departmentalization

   • How it works: Retail Banking (individuals), Corporate Banking (businesses), SME Banking (small firms).
   • Why? Tailored loan products (e.g., home loans vs. working capital loans).
   • Challenge: Coordinating promotions across divisions (e.g., a joint "Digital Banking Week").

2. Daraz’s Product-Based Structure

   • How it works: Electronics, Groceries, and Fashion teams operate independently but share logistics.
   • Why? Electronics requires tech support; groceries need fresh inventory management.
   • Real Impact: During Diwali, the Groceries team can prioritize stock without IT delays.

3. Toyota’s Process Departmentalization

   • How it works: Assembly line divided into welding, painting, and final assembly teams.
   • Why? Standardization reduces defects (e.g., a painting team can ensure consistent quality).
   • Nepal Link: Himalayan Java uses a similar approach for coffee processing.

5. Hybrid Structures: The Matrix Model

Definition: Combines functional + divisional (e.g., employees report to both a functional manager and a project manager). Example:

• Nepal: A consulting firm where an IT specialist works on both a banking project (divisional) and the IT department (functional).
• Global: Google (employees work on both a product team and a functional team like Ads or Android).

Pros:

• Flexibility: Teams adapt quickly (e.g., Daraz’s matrix structure allows a marketing expert to work on both Electronics and Groceries campaigns).
• Innovation: Cross-pollination of ideas (e.g., IT and Marketing collaborating on a new app).

Cons:

• Conflict: Dual reporting can cause confusion (e.g., "Who has priority, my product manager or my functional manager?").
• Complexity: Requires strong leadership to resolve conflicts.

MERMAID: Matrix Structure (Consulting Firm)

graph TD
  A["CEO"] --> B["Functional Managers"]
  A --> C["Project Managers"]
  B --> D["IT Team"]
  B --> E["HR Team"]
  C --> F["Banking Project"]
  C --> G["Healthcare Project"]
  D --> F
  D --> G
  E --> F
  E --> G

6. Departmentalization in Nepali Context

## Exam Tip

How This Unit Is Tested:

1. Definitions: Expect questions like "Define departmentalization and give two types." (2 marks).

   • Answer: "Departmentalization is grouping jobs to improve coordination. Types: functional, product, customer, geographic, process."

2. Examples: "Which type of departmentalization does NTC use? Why?" (3 marks).

   • Answer: "NTC uses geographic departmentalization (7 regional offices) to handle local power distribution issues efficiently."

3. Pros/Cons Tables: "Compare functional and product departmentalization." (5 marks).

   • Use a table (like above) and add one real-world example (e.g., Nabil Bank vs. Daraz).

4. Worked Examples: "How would you organize Pathao if it expanded to 10 cities?" (5 marks).

   • Structure:
     1. Start with geographic (10 city teams).
     2. Add product-based (Ride-hailing, Food Delivery).
     3. Use a matrix for shared services (e.g., Tech team reports to both city and product managers).

5. Diagrams: "Draw a matrix organization structure for a Nepali IT firm." (3 marks).

   • Tip: Use a simple mermaid-like sketch in your exam book:

     CEO
     ├── Functional: IT, HR
     └── Projects: Banking App, Healthcare App
     

Common Mistakes to Avoid:

• Vague examples: Don’t say "a company"; name Nepali firms (Nabil Bank, Daraz, NTC).
• Ignoring trade-offs: Always mention one pro and one con for each type.
• Overcomplicating: Exams favor clear structures (tables, bullet points) over essays.

Final Visual Summary: