Organizational Structure & Design: Types, Architecture, Culture & Challenges

TAKEAWAYS:

• Organizational architecture combines structure (who reports to whom), culture (shared values), and processes (how work flows) to align strategy with execution.
• Structure types (functional, divisional, matrix, network) are chosen based on size, technology, and environment—each has trade-offs in flexibility vs. control.
• Organizational culture (visible artifacts, values, assumptions) acts as "social glue" but can become a barrier to change if rigid.
• Emerging issues like AI, remote work, and sustainability force redesigns (e.g., modular teams at Daraz, agile at Ncell).
• Case analysis (e.g., Dreams Pvt. Ltd., Terminal 5) tests your ability to diagnose structural flaws and propose fixes.
• Exam focus: Sketch structures, compare pros/cons, and link theory to real cases (e.g., Nabil Bank’s decentralization vs. NTC’s bureaucracy).

1. Organizational Architecture: The Invisible Blueprint

Organizational architecture is the framework that defines:

• Structure: Hierarchy, reporting lines, and departments (e.g., functional vs. divisional).
• Culture: Norms, rituals, and shared mindsets (e.g., Google’s "innovation culture").
• Processes: Workflows, decision-making, and control systems (e.g., Kathmandu’s supply chain).

Key Elements of Architecture

mindmap
  root((Organizational Architecture))
    Structure
      Hierarchy
      Span of Control
      Centralization vs. Decentralization
    Culture
      Artifacts (Symbols, Stories)
      Values (Mission, Vision)
      Assumptions (Unspoken Rules)
    Processes
      Decision-Making (Top-Down vs. Bottom-Up)
      Coordination Mechanisms (Teams, IT Systems)
      Control Systems (Feedback Loops)

Why It Matters:

• Alignment: Structure must match strategy (e.g., a startup’s flat hierarchy vs. a bank’s rigid layers).
• Adaptability: Culture that resists change (e.g., NTC’s "this is how we’ve always done it") stifles innovation.
• Performance: Poor architecture leads to silos (e.g., Daraz’s early functional silos slowed cross-department collaboration).

2. Classical Organizational Structures

These are the foundational models still used today, each with strengths and weaknesses.

A. Functional Structure

Definition: Groups employees by specialized functions (e.g., marketing, finance, HR). Example: Nabil Bank organizes teams by departments like Retail Banking, Corporate Banking, and IT.

Pros/Cons:

Real-World Trace:

• Nabil Bank uses a functional structure for standardized services (e.g., loan processing). However, for customized corporate banking, it relies on divisional teams.
• Problem: If a customer needs a loan and IT support, they must navigate multiple departments—leading to delays.

B. Divisional Structure

Definition: Groups by products, regions, or customers (e.g., Unilever’s Home & Personal Care division). Example: Dreams Pvt. Ltd. (eco-friendly handicrafts) might have divisions for Domestic Sales and International Exports.

Pros/Cons:

Worked Example:

• Dreams Pvt. Ltd.’s International Exports Division faces higher costs because each team has its own marketing and logistics. However, it can tailor products to European vs. Asian tastes (e.g., organic certifications for EU markets).

C. Matrix Structure

Definition: Dual reporting lines (functional and project-based). Used in complex, dynamic environments. Example: Terminal 5 (Heathrow) combined functional teams (engineering, operations) with project teams for construction phases.

Pros/Cons:

Real-World Trace:

• Terminal 5’s Challenge: The matrix structure led to conflicts between functional managers (who wanted to stick to budgets) and project managers (who needed speed). The solution? Clear roles: Project managers owned timelines; functional managers owned quality.

D. Network Structure

Definition: Outsourcing core functions to external partners (e.g., contractors, vendors). Example: Daraz (Alibaba-owned) uses a network of third-party sellers, logistics (J&T Express), and payment (Khalti).

Pros/Cons:

Worked Example:

• Daraz’s Network: By outsourcing logistics to J&T Express, Daraz avoids capital expenditure on warehouses. However, during monsoon season, delays in J&T’s rural routes hurt Daraz’s customer satisfaction.

3. Contemporary Structures: Beyond the Classics

Modern businesses use hybrid or adaptive models to tackle globalization, technology, and agility.

A. Modular Structure

Definition: Self-contained "modules" (teams/products) that can be added/removed like Lego blocks. Example: Toyota’s "Modular Production System" allows it to reconfigure factories for different car models.

Why It’s Used:

• Agility: Toyota can pivot from sedans to EVs without rebuilding entire factories.
• Innovation: Modules can be experimented with independently (e.g., testing EV batteries in Module 3).

B. Virtual Structure

Definition: No physical office; teams collaborate digitally (e.g., freelancers, remote workers). Example: Freelance platforms like Upwork or Nepal’s remote IT firms (e.g., F1Soft).

Challenges in Nepal:

• Internet reliability: Slow connections in rural areas delay collaboration.
• Time zones: A Kathmandu team working on a Daraz project may need to sync with Singapore’s HQ.

C. Holacracy (Flat Structure)

Definition: No traditional managers; roles are defined by circles and spheres (e.g., Zappos). Example: Zappos replaced managers with self-organizing teams.

Pros/Cons:

Nepali Context:

• Why it’s rare: Nepali work culture often expects clear hierarchies (e.g., "boss knows best"). Holacracy would struggle in traditional firms like NTC or Ncell.

4. Organizational Culture: The Unseen Force

Culture is how things "really" get done—not just policies. It’s shaped by:

1. Artifacts (visible): Dress code, office layout, rituals (e.g., Google’s free meals).
2. Values (espoused): Mission statements, slogans (e.g., "Innovation at Ncell").
3. Assumptions (unconscious): "We always meet deadlines" or "Hierarchy matters."

Two Key Features of Culture

1. Strength: How consistent the culture is (e.g., strong at Chaudhary Group, weak at startups).
2. Adaptability: Can it change? (e.g., NTC’s rigid culture vs. Pathao’s flexible one).

5. Emerging Issues in Organizational Design

Technology, globalization, and social demands are reshaping structures.

A. Digital Transformation

• Impact: Cloud computing, AI, and automation reduce the need for middle managers.
• Example: Khalti uses automated fraud detection (AI) to replace manual review teams.
• Challenge: Employees may resist (e.g., bank tellers fearing ATMs).

B. Globalization & Remote Work

• Impact: Teams are geographically dispersed (e.g., F1Soft’s remote developers).
• Solution: Matrix + Virtual hybrids (e.g., Slack for communication, Trello for tasks).

C. Sustainability & Social Responsibility

• Impact: Firms like Himalayan Java (fair-trade coffee) design structures around ethical supply chains.
• Structural Change: Dedicated CSR (Corporate Social Responsibility) divisions.

D. Agile & Lean Structures

• Agile: Cross-functional teams (e.g., Ncell’s product teams).
• Lean: Eliminating waste (e.g., Toyota’s just-in-time inventory).

6. Case Study: Dreams Pvt. Ltd. (Eco-Friendly Handicrafts)

Scenario: Dreams Pvt. Ltd. sells domestically and internationally but struggles with coordination between divisions.

Current Structure (Functional + Divisional Hybrid)

Problems Identified:

1. Duplicated Marketing: Domestic and International teams run separate campaigns, increasing costs.
2. Slow Decision-Making: Production must wait for approvals from both sales divisions.
3. Cultural Clash: Domestic team resists "foreign" ideas (e.g., organic certifications for EU markets).

Recommended Fix: Modular Structure

Benefits:

• Shared resources: One marketing team for both markets.
• Faster innovation: Modules can experiment independently (e.g., testing organic dyes).
• Clear accountability: Each module owner is responsible for profitability.

In the Real World

1. Ncell’s Matrix Structure

   • Idea Used: Matrix structure (functional teams + project teams).
   • How: Ncell’s product development teams (e.g., 4G rollout) report to both technical managers and project leads. This allows fast innovation (e.g., launching new tariffs) but requires strong conflict resolution between departments.

2. Daraz’s Network Structure

   • Idea Used: Network structure (outsourcing logistics, payments, sellers).
   • How: Daraz doesn’t own warehouses—it uses J&T Express for delivery and Khalti for payments. This keeps costs low but means Daraz loses control over delivery times during festivals (e.g., Dashain sales surge).

3. NTC’s Bureaucratic Culture

   • Idea Used: Strong, rigid culture (slow to adapt).
   • How: NTC’s hierarchical structure and "this is how we’ve always done it" mindset delay projects like fiber-optic expansion. Employees fear taking risks without approval from multiple layers of management.

Exam Tip

How to Score Full Marks

1. Sketch Structures Clearly

   • Use Mermaid diagrams (as shown above) or tree-like boxes.
   • Label reporting lines, departments, and key roles (e.g., CEO, Project Manager).
   • Example: For Terminal 5, show dual reporting (functional + project).

2. Compare Structures in Tables

   • Exams often ask: "Which structure is best for X? Why?"
   • Template:

     Structure	Pros	Cons	Best For
     Functional	Efficiency, clear careers	Slow cross-department work	Stable environments
     Divisional	Fast market response	High costs	Diverse products/markets
     Matrix	Flexibility, innovation	Power struggles	Complex projects

3. Link Theory to Cases

   • Terminal 5: Matrix structure → conflict between functional and project managers.
   • Dreams Pvt. Ltd.: Hybrid functional/divisional → duplicated marketing.
   • Ncell: Agile teams → faster tariff launches.

4. Culture Analysis

   • Artifacts: Look for visible symbols (e.g., Google’s shuttles, NTC’s uniforms).
   • Values: Check mission statements (e.g., "Sustainability at Himalayan Java").
   • Assumptions: Infer from behavior (e.g., "No one questions the boss at NTC").

5. Emerging Issues

   • Digital Transformation: Mention automation reducing middle managers (e.g., Khalti’s AI).
   • Remote Work: Highlight coordination tools (Slack, Zoom) and time zone challenges.
   • Sustainability: Example: Himalayan Java’s ethical supply chain structure.

Common Pitfalls to Avoid

• Vague Descriptions: Don’t say "functional structure is good"—explain why (e.g., "efficient specialization for stable markets").
• Ignoring Trade-offs: Every structure has pros and cons; exams test if you recognize them.
• Overlooking Culture: Culture isn’t just "fun office perks"—it’s the unspoken rules that shape behavior.
• Case Study Mismatch: If the case is about slow decision-making, don’t recommend a highly centralized structure.

Practice Question (Solve Before Exam)

Case: A Nepali software firm, F1Soft, has grown from 10 to 100 employees. The CEO notices that:

• Developers spend too much time in meetings.
• Clients complain about slow responses.
• The marketing team and developers work in silos.

Questions:

1. What organizational structure does F1Soft likely have now? Draw it.
2. What two problems does this structure cause?
3. Propose a new structure and explain why it would fix the issues.
4. How would you improve the organizational culture to support this change?

Expected Answer Outline:

1. Current Structure: Likely functional (separate dev, marketing, sales teams).
2. Problems:
   • Poor coordination between teams (e.g., marketing doesn’t understand dev constraints).
   • Slow decision-making (too many approval layers).
3. New Structure: Matrix or Agile teams (cross-functional squads).
4. Culture Change:
   • Artifacts: Open-office layout, shared goals on walls.
   • Values: "Collaboration over hierarchy."
   • Assumptions: "Everyone contributes to decisions."