Organizing: Structures, Design, and Coordination

TAKEAWAYS:

• Organizing is the process of defining roles, grouping tasks, and establishing authority to achieve organizational goals efficiently.
• Formal organization follows a structured hierarchy (e.g., Nabil Bank’s branch network), while informal organization emerges organically (e.g., employee friend groups).
• Departmentalization (functional, product, geographic, process) determines how work is grouped—Daraz uses product-based departments (electronics, fashion) for specialization.
• Delegation involves assigning authority and responsibility (e.g., a Pathao driver’s route planning autonomy) but requires accountability.
• Span of control (narrow vs. wide) affects efficiency—NTC’s regional offices use narrow spans for tight oversight, while startups like Himalayan Java use wide spans for flexibility.
• Organizational design (mechanistic vs. organic) adapts to environment—mechanistic (Nepal Rastra Bank) suits stability, while organic (Daraz) thrives in dynamic markets.

1. Definition and Purpose of Organizing

Organizing is the arrangement of resources (human, financial, physical) and activities to implement plans efficiently. It answers:

• Who does what? (Task allocation)
• Who reports to whom? (Authority structure)
• How are resources grouped? (Departments/teams)

Why it matters: Without organizing, chaos reigns—imagine Nepal’s traffic system without designated lanes (like Kathmandu’s chaotic roads). Organizing ensures:

• Division of labor (specialization increases productivity).
• Clear communication channels (e.g., Ncell’s customer support hierarchy).
• Efficient resource use (e.g., Daraz’s warehouse organization for fast deliveries).

2. Formal vs. Informal Organization

Formal Organization

• Definition: Structured, officially sanctioned hierarchy with defined roles, rules, and reporting lines.
• Example: Nabil Bank’s branch structure
  • Advantages:
    • Clear authority (e.g., loan approval chains).
    • Standardized procedures (e.g., KYC norms).
  • Disadvantages:
    • Rigidity (slow adaptation, e.g., Nabil Bank’s slow digital loan approvals).
    • Red tape (e.g., NTC’s bureaucratic delays in license issuance).

Informal Organization

• Definition: Unofficial networks formed by social interactions (e.g., employee gossip groups, WhatsApp chats).
• Example: Khalti’s "power users" who share payment hacks via informal groups.

  flowchart TD
    A["Formal Org\n(Ncell HR Policy)"] -->|"Follows"| B["Informal Org\n(Employee WhatsApp Group)"]
    B --> C["Shares tips\non customer complaints"]
    C --> A["Influences\nformal training"]

• Advantages:
  • Faster problem-solving (e.g., Daraz sellers helping each other with order issues).
  • Employee morale (e.g., Pathao drivers’ informal support groups).
• Disadvantages:
  • Rumors/spread of misinformation (e.g., NEPSE stock tips via unofficial groups).
  • Lack of accountability.

3. Departmentalization: How Work is Grouped

Organizations group tasks into departments based on similarities. Common types:

Worked Example: Chaudhary Group’s Hybrid Model Chaudhary Group (e.g., Chaudhary Group’s retail and manufacturing arms) uses a mixed functional-product structure:

• Functional: Shared HR/Finance across all businesses.
• Product: Separate teams for retail (Bhatbhateni) vs. manufacturing (CG Cement). Why? Balances efficiency (shared services) with innovation (product-specific teams).

4. Delegation: Authority and Responsibility

Delegation is assigning tasks to subordinates while retaining accountability. Key elements:

1. Authority: Right to give orders (e.g., a Daraz store manager can approve discounts).
2. Responsibility: Duty to perform (e.g., a Pathao driver must deliver on time).
3. Accountability: Answerability for results (e.g., a NTC engineer is liable for outages).

Process of Delegation:

flowchart TD
  A["Manager\n(e.g., Daraz Store Manager)"] --> B["Assigns Task\n(Stock management)"]
  B --> C["Delegates Authority\n(Set price limits)"]
  C --> D["Subordinate\n(Store Assistant)"]
  D --> E["Performs Task"]
  E --> F["Reports Back\n(Sales data)"]
  F --> A["Manager Evaluates"]

Barriers to Delegation:

• Fear of losing control (e.g., Nabil Bank’s top-heavy loan approvals).
• Lack of trust (e.g., NTC’s reluctance to delegate fieldwork to junior engineers).
• Over-delegation (e.g., a Khalti CEO micromanaging transactions).

Exam Tip: Always link delegation to span of control (see next section).

5. Span of Control: How Many Subordinates?

Span of control = Number of subordinates a manager directly oversees.

• Narrow span (3–6 subordinates): Tall hierarchy (e.g., Nepal Rastra Bank).
• Wide span (7+ subordinates): Flat hierarchy (e.g., Himalayan Java coffee shops).

Worked Example: Kathmandu Traffic vs. Daraz Warehouse

• Kathmandu Traffic Police: Narrow span (1 inspector per 5–10 signals) due to high complexity (accident handling, coordination).
• Daraz Warehouse: Wide span (1 supervisor for 15+ pickers) because tasks are standardized (order packing).

6. Organizational Design: Mechanistic vs. Organic

Organizations adapt their structure to their environment. Two extremes:

Case Study: Toyota’s Hybrid Model Toyota uses a mechanistic core (strict production lines) with organic flexibility (employee suggestion systems, cross-team problem-solving).

mindmap
  root((Toyota’s Structure))
    Mechanistic
      Production Lines
      Standardized Processes
    Organic
      Kaizen Teams
      Cross-Functional Projects
    Result
      Efficiency + Innovation

7. Centralization vs. Decentralization

Real-World Example: NEPSE vs. Daraz

• NEPSE (Centralized): All trading decisions made by the central board → slow to adapt to global trends.
• Daraz (Decentralized): Regional teams set promotions → faster response to local demand (e.g., Diwali sales).

8. Coordination Mechanisms

Organizations use tools to sync departments:

1. Direct Contact: Face-to-face meetings (e.g., Chaudhary Group’s monthly reviews).
2. Rules/Procedures: Standardized processes (e.g., NTC’s license application forms).
3. Plans: Cross-departmental goals (e.g., Nabil Bank’s annual customer satisfaction targets).
4. Liaison Roles: Dedicated coordinators (e.g., Daraz’s product managers bridging tech and marketing).
5. Teams: Cross-functional groups (e.g., eSewa’s payment-security teams).

Visual: Coordination in a Bank

flowchart TD
  A["Loan Department\n(Nabil Bank)"] --> B["Liaison Officer"]
  B --> C["Credit Risk Team"]
  B --> D["Customer Service"]
  C --> E["Approves/Rejects\nLoan"]
  D --> F["Notifies Customer"]

In the Real World

1. eSewa’s Payment Network

   • Idea: Departmentalization (Process-based) + Decentralized Coordination
   • How? eSewa groups tasks by process (authentication, transaction processing, customer support) and uses real-time data sharing (like a liaison role) to sync fraud detection and payouts. This reduces delays in Nepali Rupee transfers compared to banks.

2. Pathao’s Driver Management

   • Idea: Wide Span of Control + Informal Networks
   • How? Pathao’s flat hierarchy lets a single area manager oversee 20+ drivers (wide span), while driver WhatsApp groups (informal org) share tips on high-demand routes (e.g., Kathmandu’s Thamel traffic jams). This cuts coordination costs by 30%.

3. Daraz’s Warehouse Organization

   • Idea: Functional + Product Departmentalization + Mechanistic Core
   • How? Daraz’s Pokhara warehouse uses:
     • Functional teams (packing, shipping, returns).
     • Product silos (electronics vs. groceries) for specialized training.
     • Automated sorting (mechanistic) but driver feedback loops (organic) to adjust routes during festivals like Tihar.

Exam Tip

How This Unit is Tested

1. Definitions: Expect 2-mark questions on organizing, delegation, or span of control. Always define + give a Nepali example (e.g., "NTC uses a narrow span of control to manage its regional offices").
2. Diagrams: Draw organizational charts (3 marks) or flowcharts (e.g., delegation process). Use mermaid-style text in exams if drawing isn’t allowed.
   • Example prompt: "Draw the organizational structure of a bank using functional departmentalization."
3. Comparisons: Tables (like the ones above) are high-yield. Memorize pros/cons of:
   • Mechanistic vs. organic.
   • Centralization vs. decentralization.
   • Narrow vs. wide span.
4. Case Applications: Apply concepts to Nepali companies. For example:
   • "How does Daraz use departmentalization to improve efficiency?" → Product-based teams + process automation.
   • "Why does NTC have a tall hierarchy?" → Complex regulatory tasks → narrow span.
5. Short Answers: For 5-mark questions, use the PEEL method:
   • Point (e.g., "Nabil Bank uses functional departmentalization").
   • Explain (how it works).
   • Example (HR, Finance, Operations departments).
   • Link (to efficiency or customer service).

Common Pitfalls

• Ignoring informal org: Always mention its role (e.g., "While NTC has a formal chain, informal networks help resolve field-level issues faster").
• Confusing delegation with authority: Delegation = assigning tasks; authority = right to command. Both must be present.
• Overgeneralizing: Not all banks are centralized (e.g., Global IME Bank is more decentralized than Nabil Bank).

Quick Revision Checklist

Before the exam, verify you can: ✅ Define organizing, formal/informal org, and departmentalization types. ✅ Draw a hybrid organizational chart (e.g., Chaudhary Group). ✅ Explain delegation with a Pathao driver example. ✅ Compare mechanistic vs. organic structures using Toyota/NTC. ✅ List 3 coordination mechanisms and give a Daraz/eSewa example. ✅ Debate: "Is decentralization always better?" (Use NEPSE vs. Daraz).