Organizational Structures & Multinational Companies: Types, Designs & Global Impact

TAKEAWAYS:

• Organizational structures determine who reports to whom, how work flows, and how decisions are made—functional structures group by skills, divisional by products/regions, and matrix combines both.
• Multinational companies (MNCs) expand globally to access markets, resources, or talent but face challenges like cultural clashes, regulatory hurdles, and ethical dilemmas (e.g., Daraz’s supply chain vs. local retailers).
• Contingency theory states there’s no "best" structure—it depends on the company’s size, environment, strategy, and technology (e.g., startups use flat structures; banks use hierarchical ones).
• Communication barriers in MNCs (language, time zones, hierarchy) can be mitigated by cross-cultural training, digital tools (Slack, Zoom), and decentralized decision-making.
• Outsourcing (e.g., Ncell’s IT support in India) and joint ventures (e.g., Toyota-Kirloskar in Nepal) are common MNC strategies to reduce costs and risks.
• Organizational charts (trees) and process flows (mermaid) reveal power, accountability, and efficiency—critical for exam questions on "disadvantages of MNCs" or "types of structures."

1. What Is Organizational Structure?

Organizational structure is the framework that defines:

• Roles and responsibilities (who does what).
• Hierarchy (who reports to whom).
• Communication flows (how information moves).
• Decision-making authority (centralized vs. decentralized).

Why does it matter? A poorly designed structure leads to confusion, slow decisions, or inefficiency. For example, if Ncell’s customer service and billing teams are in separate silos, resolving a billing issue for a Pathao driver could take days.

graph TD
    A["Organizational Structure"] --> B["Purpose: Define Roles & Workflows"]
    A --> C["Types: Functional, Divisional, Matrix, Network"]
    A --> D["Key Elements"]
    D --> D1["Hierarchy"]
    D --> D2["Span of Control"]
    D --> D3["Centralization/Decentralization"]
    D --> D4["Formalization"]

2. Types of Organizational Structures

The choice of structure depends on company goals, size, and industry. Below are the four modern types with pros/cons and Nepali/Indian examples.

graph TD
    A["Functional Structure"] --> B["Marketing"]
    A --> C["Finance"]
    A --> D["HR"]
    A --> E["Operations"]

    F["Divisional Structure"] --> G["Product 1"]
    F --> H["Product 2"]
    F --> I["Geographic Region"]

    J["Matrix Structure"] --> K["Project Team"]
    J --> L["Functional Manager"]

    M["Network Structure"] --> N["Outsourced Partners"]
    M --> O["Core Team"]

A. Functional Structure

• Definition: Groups employees by specialized functions (e.g., marketing, finance, HR).
• Example:
  • Nabil Bank: Separate departments for retail banking, corporate banking, and IT.
  • Himalayan Java: Teams for procurement, roasting, and sales.
• Pros:
  • Economies of scale (experts in one area).
  • Clear career paths (e.g., an accountant moves up in finance).
• Cons:
  • Silos: Teams may not collaborate (e.g., Daraz’s marketing and logistics not aligned).
  • Slow cross-functional decisions.

B. Divisional Structure

• Definition: Groups by products, regions, or customers.
• Example:
  • Chaudhary Group: Divisions for cement (Uttam), FMCG (Bhatbhateni), and retail (Megha).
  • Ncell: Divisions for prepaid, postpaid, and enterprise services.
• Pros:
  • Focused on specific markets (e.g., Daraz’s Nepal vs. Bangladesh divisions).
  • Faster decision-making for local needs (e.g., NTC adjusting tariffs by region).
• Cons:
  • Duplication of resources (e.g., each division may have its own HR team).
  • Inter-division rivalry (e.g., Nabil Bank’s retail vs. corporate teams competing for resources).

C. Matrix Structure

• Definition: Dual reporting lines—employees report to both a functional manager and a project manager.
• Example:
  • Toyota’s global R&D: Engineers report to both their department (e.g., electronics) and a project team (e.g., hybrid car development).
  • Nepal’s IT firms: Developers work on both a client’s project (e.g., eSewa integration) and their team’s long-term goals.
• Pros:
  • Flexibility for complex projects (e.g., launching a new Daraz feature).
  • Cross-functional collaboration (e.g., marketing + tech teams for a Pathao promo).
• Cons:
  • Conflict: Who has priority—functional boss or project lead?
  • Complexity: Employees may feel torn (e.g., a bank’s IT staff split between core banking and digital banking projects).

D. Network (Virtual) Structure

• Definition: Outsourcing core functions to external partners (e.g., freelancers, agencies).
• Example:
  • Daraz: Uses third-party logistics (e.g., DHL, local couriers) and dropshipping suppliers.
  • Nepal’s software firms: Outsource UI design to Indian agencies, backend to Sri Lankan teams.
• Pros:
  • Cost savings (no need to hire full-time staff for every skill).
  • Access to global talent (e.g., Ncell’s cybersecurity team in the Philippines).
• Cons:
  • Loss of control (e.g., quality issues with a Daraz supplier in India).
  • Coordination challenges (time zones, cultural differences).

3. How to Choose the Right Structure?

No single structure fits all companies. Use this decision tree to pick the best fit:

flowchart TD
    A["Company Needs Analysis"] --> B["Is the company small/startup?"]
    B -->|"Yes"| C["Flat Structure (Network/Functional)"]
    B -->|"No"| D["Is the focus on products/regions?"]
    D -->|"Yes"| E["Divisional Structure"]
    D -->|"No"| F["Is innovation/collaboration key?"]
    F -->|"Yes"| G["Matrix Structure"]
    F -->|"No"| H["Functional Structure"]
    H --> I["Add decentralization if local autonomy is needed"]

Real-World Tie-In:

• Pathao started as a network structure (outsourced drivers, used Uber’s tech) but shifted to a divisional structure as it expanded into food delivery (Pathao Food) and payments (Pathao Pay).
• NTC uses a functional structure for operations but a matrix approach for large infrastructure projects (e.g., hydropower partnerships).

4. Multinational Companies (MNCs): Global Giants and Challenges

MNCs like Google, Toyota, and Chaudhary Group operate in multiple countries. Their structures often combine divisional (by region) + functional (by expertise).

Advantages of MNCs

Disadvantages of MNCs

5. How MNCs Structure Themselves Globally

MNCs use three common approaches to manage global operations:

A. Ethnocentric Approach

• "Home country knows best."
• Example: Toyota’s early global expansion replicated Japanese management styles.
• Pros: Strong corporate culture, consistent quality.
• Cons: Ignores local needs (e.g., Toyota’s early failure in India due to small-car preferences).

B. Polycentric Approach

• "When in Rome, do as the Romans do."
• Example: McDonald’s offers vegetarian burgers in India and beef in the US.
• Pros: High local acceptance.
• Cons: Loss of brand consistency (e.g., Coca-Cola’s "Thums Up" in India).

C. Geocentric Approach

• "Best of both worlds."
• Example: Google’s global hiring (Nepali engineers in Kathmandu, Indian devs in Bengaluru).
• Pros: Balances global standards with local adaptability.
• Cons: Complex to manage (e.g., Ncell’s IT team in Nepal vs. customer service in India).

6. Case Study: Daraz (Alibaba’s Nepali MNC)

Structure: Divisional + Network

• Divisions: Nepal, Bangladesh, Sri Lanka, Pakistan.
• Network: Outsources logistics, customer service, and some tech to local/Indian partners.

Challenges:

1. Supply Chain Barriers: Delays in cross-border shipments (e.g., Daraz Nepal orders from India face customs issues).
2. Local Competition: Traditional retailers (e.g., Thamel shops) resist e-commerce, leading to protests.
3. Cultural Adaptation: Nepali customers prefer cash-on-delivery; Daraz initially struggled with digital payments (fixed via Khalti integration).

Solution:

• Hybrid structure: Centralized tech (Alibaba’s platform) + decentralized operations (local warehouses).
• Joint ventures: Partnered with local firms for last-mile delivery.

7. Organizational Barriers in Communication (Exam Focus)

Even with the best structure, communication fails in MNCs due to:

8. Real-World Applications: Where You See This Every Day

A. eSewa (Digital Payments)

• Structure: Matrix (functional teams for tech, finance, compliance + project teams for new features like bill payments).
• MNC Link: Uses geocentric approach—global fintech standards (PCI compliance) + local adaptations (Nepali language, cash deposit points).

B. Ncell (Telecom)

• Structure: Divisional (prepaid, postpaid, enterprise) + functional (HR, finance).
• Global Challenge: Partners with MNCs like Ericsson for 5G tech but faces regulatory barriers from NTC.

C. Daraz (E-Commerce)

• Structure: Network (outsourced logistics) + divisional (country-specific teams).
• MNC Strategy: Polycentric—adapts to local payment methods (cash-on-delivery in Nepal vs. digital wallets in India).

D. Toyota Kirloskar (Automotive)

• Structure: Global matrix—engineers report to both regional (Nepal/India) and product (e.g., hybrid cars) teams.
• Challenge: Cultural clash—Japanese efficiency vs. Nepali suppliers’ slower response times.

9. Worked Example: NTC’s Organizational Structure

Scenario: Nepal Transmission and Distribution Company (NTC) wants to improve power distribution efficiency.

Current Structure: Functional (Operations, Finance, HR) but slow decision-making for regional outages.

Proposed Change: Divisional + Matrix

1. Divisions: East, West, Central Nepal zones.
2. Matrix: Each zone has a project team for smart grid upgrades, reporting to both the zone manager and the tech lead.

Impact:

• Faster responses to outages (e.g., Kathmandu traffic lights managed locally).
• Better collaboration between engineers and finance (budget approvals for repairs).
• Local autonomy (e.g., Pokhara zone can adjust tariffs based on demand).

10. Exam Tip: How to Score Full Marks

For Definition-Based Questions (e.g., "Define organizational goals")

• Structure: Definition (1 mark) + Explanation (2 marks) + Example (2 marks).
• Example Answer:

  "Organizational goals are the specific, measurable objectives a company aims to achieve (e.g., revenue growth, market share). They are formulated through top-down planning (CEO sets vision) and bottom-up input (department heads suggest targets). For example, Ncell’s goal of ‘10 million 5G users by 2025’ aligns with its strategy to compete with NTC’s broadband services."

For "Types of Organizational Structures"

• Use a table to compare 2 types (e.g., Functional vs. Divisional) with pros/cons/examples.
• Example:

  Feature	Functional Structure	Divisional Structure
  Grouping	By skill (e.g., all accountants)	By product/region (e.g., Daraz Nepal)
  Pros	Economies of scale, expert teams	Focused on customer needs
  Cons	Slow cross-department work	Duplication of resources
  Example	Nabil Bank’s finance team	Toyota’s global car divisions

For "Disadvantages of MNCs"

• Pick 3 key points and tie to a Nepali example:

  *"Three disadvantages of MNCs are:

  1. Cultural clashes: Daraz’s Indian managers initially imposed rigid KPIs, ignoring Nepali suppliers’ slower payment cycles.
  2. Regulatory hurdles: Ncell faces different telecom laws in Nepal vs. India, increasing compliance costs.
  3. Exploitation: Some Daraz suppliers in Nepal pay workers below the minimum wage to meet low prices."*

For "Organizational Barriers"

• Name the barrier + give a real example + suggest a solution:

  "A language barrier in MNCs occurs when global teams communicate in English, excluding non-native speakers. For example, Ncell’s IT team in Kathmandu struggled with English-based training manuals from its Indian HQ. Solution: Provide Nepali translations and conduct bilingual workshops."

11. Quick Revision Checklist

Before the exam, ensure you can: ✅ Draw 3 types of organizational structures (functional, divisional, matrix) with examples. ✅ Explain how MNCs like Daraz or Toyota structure their global operations. ✅ List 3 advantages and 3 disadvantages of MNCs with Nepali examples. ✅ Describe 2 communication barriers in MNCs and how to fix them. ✅ Compare ethnocentric vs. polycentric vs. geocentric approaches with real-world cases.