MGT320 Engineering Management

Engineering ManagementUnit 323 min read

Organization Structure: Types, Design & Real-World Applications

Unit 3 of Engineering Management explores the design principles of organizational structures, including functional, divisional, matrix, and network models, their advantages/disadvantages, and real-world applications in Nepali and global companies like Nabil Bank and Toyota.

TAKEAWAYS:

  • Organizational structure defines roles, responsibilities, and relationships to achieve efficiency and coordination.
  • Five common structures (functional, divisional, matrix, network, and hybrid) suit different organizational needs.
  • Span of control and centralization vs. decentralization impact communication and decision-making speed.
  • Real-world examples (e.g., Nabil Bank’s hierarchical structure, Daraz’s flat network model) show how structures align with business goals.
  • Organizational charts visually represent hierarchy, authority, and workflow.
  • Challenges like communication gaps or role conflicts arise in poorly designed structures.

1. Definition and Importance of Organizational Structure

Organizational structure is the framework that outlines how activities, roles, and responsibilities are formally divided, grouped, and coordinated. It acts as a blueprint for how work flows within an organization, ensuring efficiency, accountability, and alignment with strategic goals.

Why Does Structure Matter?

  • Clarifies roles: Employees know their responsibilities and reporting lines.
  • Improves coordination: Reduces confusion in decision-making.
  • Enhances accountability: Clear chains of command ensure responsibility.
  • Supports scalability: Helps organizations grow without losing efficiency.
  • Facilitates change: A well-designed structure adapts to market or technological shifts.

2. Key Elements of Organizational Structure

Every structure is built on three core elements:

Element Description Example in Nepal
Division of Work Tasks are divided among employees to avoid overload and improve specialization. At NTC (Nepal Telecommunications Corporation), IT, customer service, and engineering teams handle separate functions.
Departmentalization Grouping jobs into units (e.g., by function, product, or region). Nabil Bank groups employees into Retail Banking, Corporate Banking, and Operations.
Span of Control Number of subordinates a manager directly oversees (narrow vs. wide). Pathao uses a wide span of control for its delivery drivers, reporting to regional managers.
Authority & Responsibility Who has the power to make decisions and who is accountable. NEPSE (Nepal Stock Exchange) has a CEO with authority over trading, compliance, and IT teams.
Centralization vs. Decentralization Where decision-making power lies (top-down vs. distributed). Himalayan Java (a Nepali coffee brand) decentralizes marketing decisions to regional teams.

3. Types of Organizational Structures

Different structures suit different organizational needs. Below are the five most common types, visualized and explained.

A. Functional Structure

Definition: Employees are grouped by specialized functions (e.g., marketing, finance, HR, engineering). Best for: Small to medium-sized businesses with stable environments and clear expertise needs.

graph TD
    A["CEO"] --> B["Marketing"]
    A --> C["Finance"]
    A --> D["Engineering"]
    A --> E["HR"]
    B --> F["Digital Marketing"]
    B --> G["Branding"]
    C --> H["Accounting"]
    C --> I["Treasury"]

Advantages:

  • Clear career paths in specialized areas.
  • Economies of scale (e.g., shared resources in engineering).
  • Strong expertise in each function.

Disadvantages:

  • Slow decision-making (must go through multiple layers).
  • Lack of cross-functional collaboration.
  • Rigid—struggles with rapid changes.

Real-World Example: Nabil Bank

  • Uses a functional structure where:
    • Retail Banking handles customer accounts.
    • Corporate Banking manages loans for businesses.
    • IT develops banking software.
  • Why? Ensures deep expertise in each area while maintaining regulatory compliance.

Worked Example: Kathmandu Traffic Management Imagine Kathmandu’s traffic police are organized functionally:

  • Traffic Control Unit: Manages signals and routes.
  • Enforcement Unit: Issues fines for violations.
  • Public Awareness Unit: Runs campaigns on road safety. Problem: If a major protest blocks a route, the Traffic Control Unit must coordinate with Enforcement to redirect traffic and with Public Awareness to inform drivers. This silos slow down response time.

B. Divisional Structure

Definition: Employees are grouped by products, services, customers, or regions. Best for: Diversified companies with multiple products or geographic markets.

graph TD
    A["CEO"] --> B["North Region"]
    A --> C["South Region"]
    A --> D["East Region"]
    B --> E["Retail Division"]
    B --> F["Corporate Division"]
    C --> G["Retail Division"]
    C --> H["SME Division"]

Types of Divisional Structures:

  1. Product Division: Grouped by products (e.g., Toyota has divisions for cars, trucks, and motorcycles).
  2. Geographic Division: Grouped by location (e.g., Daraz has separate teams for Kathmandu, Pokhara, and online).
  3. Customer Division: Grouped by customer type (e.g., Nabil Bank has Retail and Corporate Banking).

Advantages:

  • Faster decision-making (divisions operate independently).
  • Flexibility to adapt to local market needs.
  • Clear accountability for each division’s performance.

Disadvantages:

  • Duplication of resources (e.g., multiple HR teams).
  • Lack of coordination between divisions.
  • Higher costs due to redundancy.

Real-World Example: Daraz (Nepali e-commerce giant)

  • Uses a geographic divisional structure:
    • Kathmandu Division: Manages local warehouses and delivery.
    • Pokhara Division: Handles regional inventory.
    • Online Division: Manages the website and customer service.
  • Why? Allows Daraz to customize marketing (e.g., promoting winter gear in Pokhara vs. Kathmandu) and optimize logistics.

Worked Example: Chaudhary Group’s Diversification Chaudhary Group (owners of Nabil Bank, CG Group, and CG Cement) uses a divisional structure:

  • Nabil Bank: Focuses on financial services.
  • CG Cement: Manages manufacturing and sales.
  • Retail (e.g., CG Mart): Handles consumer goods. Challenge: If Nabil Bank launches a new digital banking app, it must coordinate with CG Group’s IT team to avoid conflicts with existing systems.

C. Matrix Structure

Definition: Employees report to two bosses (e.g., a functional manager and a project manager). Best for: Project-based industries (e.g., construction, IT, research).

graph TD
    A["CEO"] --> B["Functional Manager (Engineering)"]
    A --> C["Project Manager (Software Development)"]
    B --> D["Developer 1"]
    B --> E["Developer 2"]
    C --> D
    C --> E

Advantages:

  • Flexibility to adapt to project needs.
  • Cross-functional collaboration (e.g., engineers + marketers work together).
  • Efficient resource use (employees work on multiple projects).

Disadvantages:

  • Conflict between functional and project managers.
  • Unclear reporting lines (who has final authority?).
  • Stress on employees (dual accountability).

Real-World Example: Himalayan Java (Nepali Coffee Brand)

  • Uses a matrix structure for new product launches:
    • Functional Teams: Marketing, Supply Chain, R&D.
    • Project Team: Led by a Product Manager for a new coffee blend.
  • Why? Allows quick innovation (e.g., launching a limited-edition winter coffee) without restructuring permanently.

Worked Example: NTC’s Network Expansion Project NTC is expanding its 5G network in Pokhara. The project involves:

  • Engineering Team (functional manager): Designs the infrastructure.
  • Project Manager: Oversees timeline and budget.
  • Marketing Team: Promotes the launch. Conflict: The Engineering Team wants to delay to ensure quality, but the Project Manager needs to meet the deadline for a government deadline. Solution: A matrix governance committee (CEO + both managers) resolves the conflict.

D. Network (Virtual) Structure

Definition: A core organization outsources functions to independent contractors or partners. Best for: Startups, freelance-heavy industries, or global companies needing flexibility.

graph TD
    A["Core Company (eSewa)"] -->|"Outsources"| B["Payment Processing (Fintech Partner)"]
    A -->|"Outsources"| C["Customer Support (Third-Party Call Center)"]
    A -->|"Outsources"| D["IT Infrastructure (Cloud Provider)"]

Advantages:

  • Cost-effective (no need for full-time employees).
  • Access to specialized expertise (e.g., AI for fraud detection).
  • Scalability (easy to add/remove partners).

Disadvantages:

  • Loss of control over outsourced functions.
  • Coordination challenges (time zones, communication barriers).
  • Reputation risk if partners fail (e.g., data breaches).

Real-World Example: eSewa (Nepali Digital Payment Platform)

  • Uses a network structure:
    • Core Team: Handles security and partnerships.
    • Outsourced:
      • Payment Processing: Partnered with Nepal Rastra Bank-approved fintech firms.
      • Customer Support: Handled by third-party call centers.
      • IT Infrastructure: Hosted on AWS (Amazon Web Services).
  • Why? Allows eSewa to focus on innovation (e.g., UPI integration) while leveraging experts.

Worked Example: Pathao’s Driver Network Pathao (ride-hailing app) uses a network model:

  • Core Team: Develops the app and handles marketing.
  • Independent Drivers: Act as a virtual fleet. Challenge: If a driver provides poor service, Pathao’s reputation suffers, but it doesn’t employ them directly. Solution: Pathao uses AI-driven ratings and automated deactivation for repeat offenders.

E. Hybrid Structure

Definition: A combination of two or more structures (e.g., functional + divisional). Best for: Large, complex organizations needing both specialization and flexibility.

graph TD
    A["CEO"] --> B["North Region"]
    A --> C["South Region"]
    B --> D["Marketing (Functional)"]
    B --> E["Engineering (Functional)"]
    C --> F["Sales (Functional)"]
    C --> G["HR (Functional)"]

Real-World Example: Toyota (Global Automotive Giant)

  • Uses a hybrid structure:
    • Divisional: Grouped by products (cars, trucks, hybrids).
    • Functional: Each division has R&D, Manufacturing, and Marketing teams.
  • Why? Allows global standardization (e.g., Toyota’s safety features) while adapting to local markets (e.g., smaller cars in Nepal).

Worked Example: Ncell’s Organizational Design Ncell (Nepal’s largest telecom) combines:

  1. Functional Teams: IT, Customer Service, Network Operations.
  2. Divisional Teams: Prepaid and Postpaid services. Challenge: If Ncell launches a new 5G plan, the Marketing Team (functional) must work with the Postpaid Division (divisional) to ensure promotions align. Solution: A cross-functional task force oversees the launch.

4. Factors Influencing Organizational Structure

The choice of structure depends on internal and external factors:

Factor Description Example in Nepal
Organizational Size Small firms → flat structures; large firms → hierarchical. Local bakery (flat) vs. NTC (hierarchical).
Technology Digital tools enable decentralized structures. eSewa uses cloud-based outsourcing for a network model.
Environment Stable → functional; dynamic → matrix or divisional. Nabil Bank (stable, functional) vs. Daraz (dynamic, divisional).
Strategy Innovation → matrix; cost leadership → functional. Himalayan Java (innovation, matrix) vs. CG Cement (cost leadership, functional).
Culture Collaborative → matrix; hierarchical → functional. Pathao (collaborative, matrix) vs. NTC (hierarchical, functional).

5. Organizational Charts: Visualizing Structure

An organizational chart is a graphical representation of a company’s hierarchy. Below is an example for Nabil Bank:

Key Symbols in Charts:

  • Boxes: Departments or roles.
  • Lines: Reporting relationships.
  • Solid Lines: Direct authority.
  • Dotted Lines: Advisory or indirect relationships.

Why Use Charts?

  • Clarifies roles (who reports to whom?).
  • Identifies bottlenecks (e.g., too many layers slow decisions).
  • Helps with onboarding (new hires understand the structure).

6. Challenges in Organizational Structure

Even the best structures face issues:

Challenge Cause Solution
Communication Gaps Too many layers (tall hierarchy). Flatten structure or use cross-functional teams.
Role Conflicts Unclear responsibilities (e.g., in matrix structures). Define RACI matrices (Responsible, Accountable, Consulted, Informed).
Slow Decision-Making Centralized authority. Decentralize decisions to lower levels.
High Costs Duplication in divisional structures. Use shared services (e.g., HR, IT).
Lack of Innovation Rigid functional silos. Encourage cross-departmental projects (e.g., like Himalayan Java’s new products).

7. Real-World Case Study: Nabil Bank’s Organizational Structure

Company: Nabil Bank (Nepal’s largest commercial bank). Industry: Banking and Financial Services. Structure: Hybrid (Functional + Divisional).

How It Works:

  1. Functional Departments:

    • Retail Banking: Manages customer accounts, loans, and deposits.
    • Corporate Banking: Handles business loans, trade finance.
    • IT & Digital Banking: Develops mobile apps and online services.
    • Risk Management: Ensures compliance with Nepal Rastra Bank (NRB) regulations.
  2. Divisional Approach:

    • Regional Branches: Each branch (Kathmandu, Pokhara, etc.) operates semi-independently.
    • Product Lines: Separate teams for mortgages, SME loans, and digital payments.

Why This Structure?

  • Expertise: Functional teams ensure deep knowledge in banking products.
  • Local Adaptation: Regional branches tailor services (e.g., agricultural loans in rural areas).
  • Regulatory Compliance: Clear reporting lines ensure audit readiness.

Challenges Faced:

  • Slow approvals for large loans (due to multiple layers).
  • Silos between Retail and Corporate Banking (e.g., a corporate client might need both services). Solution: Nabil Bank introduced cross-functional loan committees to speed up decisions.

Visual: Nabil Bank’s Partial Org Chart

graph TD
    A["CEO - Nabil Bank"] --> B["COO"]
    A --> C["CFO"]
    B --> D["Retail Banking"]
    B --> E["Corporate Banking"]
    B --> F["Regional Branches"]
    C --> G["Risk Management"]
    C --> H["IT & Digital"]
    D --> I["Loan Processing"]
    D --> J["Customer Service"]
    E --> K["Trade Finance"]
    E --> L["Corporate Loans"]
    F --> M["Kathmandu Region"]
    F --> N["Pokhara Region"]

8. How to Choose the Right Structure?

Use this decision flowchart to select the best structure for your organization:

flowchart TD
    A["Start: What is your business goal?"] --> B{"Is the environment stable?"}
    B -->|"Yes"| C["Use Functional Structure"]
    B -->|"No"| D{"Do you need project flexibility?"}
    D -->|"Yes"| E["Use Matrix Structure"]
    D -->|"No"| F{"Is your business diversified?"}
    F -->|"Yes"| G["Use Divisional Structure"]
    F -->|"No"| H{"Do you need cost efficiency?"}
    H -->|"Yes"| I["Use Network Structure"]
    H -->|"No"| J["Use Hybrid Structure"]

Questions to Ask:

  1. How fast do we need to make decisions? (Matrix/divisional → faster; functional → slower).
  2. Do we need deep expertise or cross-functional collaboration? (Functional vs. matrix).
  3. Can we afford full-time employees, or should we outsource? (Network vs. hybrid).
  4. Is our industry regulated? (Banks → hierarchical; startups → flat).

## In the Real World

Understanding organizational structures helps explain how Nepali and global companies operate. Here’s how these concepts apply in everyday life:

  1. eSewa’s Network Model

    • Idea Used: Network (Virtual) Structure.
    • How? eSewa outsources payment processing to fintech partners and customer support to third-party call centers while keeping its core team focused on security and partnerships.
    • Impact: Allows eSewa to scale quickly without hiring full-time staff for every function.
  2. Daraz’s Divisional Structure

    • Idea Used: Divisional (Geographic + Product).
    • How? Daraz groups teams by region (Kathmandu, Pokhara) and product type (electronics, groceries). This lets them:
      • Run local promotions (e.g., winter sales in Pokhara).
      • Optimize warehouse locations near high-demand areas.
    • Impact: Faster delivery and higher customer satisfaction in regional markets.
  3. NTC’s Functional Structure

    • Idea Used: Functional Structure.
    • How? NTC divides work into:
      • Network Operations: Manages towers and signals.
      • Customer Service: Handles complaints and plans.
      • IT: Develops apps and cybersecurity.
    • Real-Life Example: When NTC launched 4G in Pokhara, the Network Operations team installed infrastructure, while Customer Service trained staff and ran ads. This specialization ensured a smooth launch.
    • Challenge: If a power outage disrupts service, Network Operations must coordinate with Customer Service to inform users, leading to delays due to silos.
  4. Pathao’s Matrix-Like Driver Management

    • Idea Used: Hybrid (Network + Project-Based).
    • How? While Pathao’s core team develops the app, its drivers act like a virtual workforce with dual reporting:
      • To Pathao’s Operations Team (for ride assignments).
      • To Local Government (for vehicle regulations).
    • Impact: Allows Pathao to scale rapidly during festivals (e.g., Dashain) by onboarding temporary drivers.
  5. Nabil Bank’s Loan Approval Process

    • Idea Used: Hybrid (Functional + Divisional).
    • How? When a customer applies for a home loan:
      1. Retail Banking Team collects documents.
      2. Risk Management checks creditworthiness.
      3. Corporate Banking (if it’s a large loan) reviews business plans.
      4. Final approval comes from a cross-functional committee.
    • Real-Life Example: A small business loan might take 3 days (functional silos), while a corporate loan (divisional) could take 2 weeks due to additional checks.

## Exam Tip

This unit is heavily tested in PU exams through:

  1. Definitions and Comparisons (e.g., "Differentiate between functional and divisional structures").
  2. Case Studies (e.g., "Analyze NTC’s structure and suggest improvements").
  3. Diagrams (e.g., "Draw and explain a matrix organizational chart").
  4. Scenario-Based Questions (e.g., "A startup wants to expand. Recommend a structure and justify").

How to Score Full Marks:

✅ Memorize the 5 structures and their advantages/disadvantages. ✅ Practice drawing org charts for real companies (Nabil Bank, Daraz, NTC). ✅ Relate theory to Nepal: Always use local examples (e.g., "Nepal’s traffic police could use a matrix structure for protests"). ✅ Use tables for comparisons (e.g., functional vs. divisional). ✅ For case studies, follow this format:

  • Current Structure: Describe it.
  • Problems: Identify 2-3 challenges.
  • Recommendations: Suggest 1-2 improvements with justification.

Common Mistakes to Avoid:

❌ Mixing up matrix and divisional structures (matrix = dual reporting; divisional = grouped by product/region). ❌ Ignoring real-world examples (exams love Nabil Bank, Daraz, NTC, and Pathao). ❌ Overcomplicating answers—stick to clear, concise points with visuals. ❌ Forgetting to link theory to practice (always explain why a structure works for a given scenario).


## Summary Table: Structures at a Glance

Structure Best For Example in Nepal Key Advantage Key Disadvantage
Functional Stable, expertise-driven firms. NTC, Nabil Bank Deep specialization. Slow decision-making.
Divisional Diversified, regional businesses. Daraz, Chaudhary Group Fast local adaptation. Duplication of resources.
Matrix Project-based industries. Himalayan Java, IT firms Cross-functional collaboration. Role conflicts.
Network Startups, cost-sensitive firms. eSewa, freelance agencies Flexibility and scalability. Loss of control.
Hybrid Large, complex organizations. Toyota, Ncell Balances specialization and flexibility. Complex to manage.

## Practice Questions (Exam-Style)

  1. Short Answer:

    • "Define span of control and explain how a wide span affects communication in a tall hierarchy."
  2. Diagram-Based:

    • "Draw an organizational chart for a Nepali software company with functional departments (Development, Marketing, HR) and a project team for a new app."
  3. Case Study:

    • "A local bakery in Kathmandu is growing rapidly. Currently, it has a flat structure with the owner handling everything. Recommend an organizational structure and justify your choice. Include potential challenges."
  4. Comparison:

    • "Compare and contrast a divisional structure with a matrix structure using examples from Nepali companies."

## Final Thought

Organizational structure is not one-size-fits-all. The best structure depends on your goals, industry, and environment. Whether you’re working at Nabil Bank, Daraz, or a startup, understanding these models helps you navigate hierarchies, improve efficiency, and innovate.

Pro Tip: In exams, always draw a diagram—it’s worth extra marks and makes your answer stand out!

Based on the PU BE Computer (PU) syllabus for Engineering Management (MGT320), unit 3.

Discussion

Loading…