Organizing: Structure, Job Design & Authority

TAKEAWAYS:

• Organizing is the process of grouping jobs, establishing authority, and coordinating resources to achieve goals efficiently.
• Organizational structures (functional, divisional, matrix) determine how work flows, power is distributed, and teams collaborate.
• Job design balances specialization (efficiency) and enrichment (motivation) to fit tasks to people and vice versa.
• Authority, responsibility, and accountability form the backbone of delegation—without delegation, managers become bottlenecks.
• Centralization vs. decentralization affects decision speed, innovation, and employee empowerment (e.g., Ncell’s regional autonomy vs. NTC’s top-down control).
• Span of control (how many subordinates report to one manager) impacts communication clarity and workload (e.g., Daraz’s flat structure vs. Himalayan Java’s hierarchical teams).

1. What Is Organizing?

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

• Dividing work into manageable tasks (job design).
• Grouping jobs into departments or teams (departmentalization).
• Establishing authority relationships (who reports to whom).
• Allocating resources (human, financial, technological).

Why is organizing critical? Without organizing, chaos reigns—imagine eSewa’s payment system with no clear roles for fraud detection, customer support, and IT teams. Organizing ensures efficiency, accountability, and adaptability.

2. Steps in the Organizing Process

flowchart TD
    A["Step 1: Define Objectives"] --> B["Step 2: Divide Work into Jobs"]
    B --> C["Step 3: Departmentalization"]
    C --> D["Step 4: Assign Authority & Responsibility"]
    D --> E["Step 5: Coordinate Activities"]
    E --> F["Step 6: Establish Reporting Relationships"]

Worked Example: Pathao’s Rider Management

1. Objective: Deliver orders within 30 minutes.
2. Jobs: Rider, Dispatcher, Customer Support, Data Analyst.
3. Departmentalization: Group riders by city (Kathmandu, Pokhara).
4. Authority: Dispatchers assign orders; riders accept/reject.
5. Coordination: GPS tracks real-time rider locations.
6. Reporting: Riders report to zone managers → Operations → CEO.

3. Principles of Organizing

4. Organizational Structures

A. Functional Structure

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

Advantages:

• Deep expertise in each function (e.g., Himalayan Java’s coffee roasting team).
• Clear career paths (e.g., Ncell’s IT → Network Engineering). Disadvantages:
• Slow cross-department coordination (e.g., Khalti’s payment failure if IT and Customer Support don’t sync).
• Silos (e.g., Daraz’s warehouse and marketing teams not collaborating on promotions).

Real-World Case: Toyota’s Functional Structure

• Finance: Budgeting for new car models.
• R&D: Designing hybrid engines.
• Production: Assembly line management.
• Marketing: Global ad campaigns. Problem: If R&D designs a car but Marketing doesn’t align with regional tastes (e.g., Nepal’s narrow roads), sales suffer.

B. Divisional Structure

graph TD
    A["CEO"] --> B["Product 1 Division"]
    A --> C["Product 2 Division"]
    A --> D["Geographical Division"]
    B --> E["R&D"]
    B --> F["Manufacturing"]
    B --> G["Sales"]

Example: Chaudhary Group

• Divisions: FMCG (Bhatbhateni), Retail (Gorkha Bazar), Banking (Nabil).
• Advantages:
  • Fast decision-making (e.g., Bhatbhateni’s new product launch).
  • Focused expertise (e.g., Gorkha Bazar’s fashion vs. electronics teams).
• Disadvantages:
  • Duplication of resources (e.g., multiple HR teams across divisions).
  • Infighting (e.g., Nabil Bank vs. Global IME’s competing loan products).

Worked Example: Daraz’s Geographical Divisions

• Kathmandu Division: Handles 60% of orders, prioritizes same-day delivery.
• Pokhara Division: Focuses on tourism-related products (e.g., trekking gear).
• Problem: If Pokhara’s warehouse runs out of stock, Kathmandu’s customers face delays.

C. Matrix Structure

graph TD
    A["Project Manager"] --> B["Marketing Team"]
    A --> C["IT Team"]
    D["Functional Manager"] --> B
    D --> C

Example: Nepal’s IT Companies (e.g., F1Soft, Ncell’s Digital Team)

• Dual Reporting: Employees report to both a project manager (e.g., eSewa app development) and a functional manager (e.g., software engineering head).
• Advantages:
  • Flexibility (e.g., Khalti’s cross-functional teams for new payment methods).
  • Shared resources (e.g., NTC’s engineers working on both fiber and mobile networks).
• Disadvantages:
  • Conflict (e.g., Project Manager wants faster delivery; Functional Manager insists on testing).
  • Complex coordination (e.g., Pathao’s rider app updates requiring input from 5 teams).

Real-World Conflict: Google’s Matrix Structure

• Project: Launch a new AI tool.
• Teams: AI Research, Marketing, Legal.
• Issue: Legal slows down AI team’s data collection; Marketing wants features ready before launch.

5. Job Design: Specialization vs. Enrichment

Worked Example: Nabil Bank’s Teller vs. Relationship Manager

• Teller (Specialized): Processes transactions, follows scripts.
• Relationship Manager (Enriched): Advises on loans, builds customer trust. Result: Relationship Managers earn 30% more and retain customers longer.

6. Authority, Responsibility, and Accountability

flowchart LR
    A["Authority"] --> B["Responsibility"]
    B --> C["Accountability"]
    C --> D["Performance Evaluation"]

• Authority: Right to give orders (e.g., Daraz’s warehouse manager can assign tasks).
• Responsibility: Duty to perform (e.g., manager must ensure orders ship on time).
• Accountability: Answering for results (e.g., manager is fired if 50% of orders are delayed).

Real-World Failure: Kathmandu Traffic Police

• Authority: Can stop vehicles for violations.
• Responsibility: Reduce accidents.
• Problem: Low accountability → corruption and poor enforcement.

7. Delegation of Authority

Definition: Transferring authority to subordinates to achieve organizational goals. Why Delegate?

• Managers’ workload reduces (e.g., CEO of Chaudhary Group can’t handle all divisions).
• Employee growth (e.g., Ncell’s junior engineers gain leadership skills).
• Faster decisions (e.g., Daraz’s regional managers approve discounts).

Guidelines for Effective Delegation

1. Define Clear Objectives: "Increase Khalti’s transaction speed by 20%."
2. Select the Right Person: Skills + motivation (e.g., tech-savvy employee for app updates).
3. Grant Authority: Not just "do this," but "you have the power to hire contractors."
4. Establish Accountability: "Report weekly progress to me."
5. Provide Support: Training, resources (e.g., NTC gives engineers new software tools).
6. Monitor Progress: Check-ins without micromanaging.

Example: Google’s Delegation

• Project: Improve YouTube’s mobile app.
• Delegated To: Cross-functional team (designers, engineers, UX researchers).
• Authority: Team can pivot features based on user feedback.
• Accountability: Team presents results to VP of Products.

8. Centralization vs. Decentralization

Worked Example: Ncell’s Decentralized Customer Support

• Centralized: All complaints go to Kathmandu → slow resolution.
• Decentralized: Regional teams handle local issues (e.g., Pokhara’s team knows about power outages affecting calls). Result: 30% faster complaint resolution.

9. Span of Control

Definition: Number of subordinates a manager can effectively supervise (ideal: 3–7). Factors Affecting Span:

• Complexity of Work: Simple tasks (e.g., NTC’s meter readers) → wider span.
• Manager’s Skills: Experienced managers (e.g., Google’s engineering leads) can handle more.
• Communication Technology: Tools like Slack/Teams allow wider spans.

Example: Flat vs. Tall Structures

Real-World Impact: Kathmandu Traffic Police

• Problem: Too many subordinates per officer → inefficient traffic management.
• Solution: Reduce span → dedicated zones with 1 officer per 5 blocks.

In the Real World

1. eSewa’s Organizational Structure

   • Functional Teams: Payments, Fraud Detection, Customer Support.
   • Job Design: Fraud analysts (specialized) vs. customer service reps (enriched with complaint resolution tools).
   • Delegation: Regional managers approve local promotions during festivals.

2. Pathao’s Divisional Structure

   • Geographical Divisions: Kathmandu, Pokhara, Bharatpur.
   • Matrix Approach: Riders report to zone managers and app developers (for feedback on delivery challenges).
   • Span of Control: Zone managers handle 5–7 drivers to ensure personal oversight.

3. Nabil Bank’s Centralized vs. Decentralized Loans

   • Centralized: Corporate loans (approved by Kathmandu HQ).
   • Decentralized: Retail loans (approved by branch managers).
   • Result: Faster SME loan approvals in provinces.

Exam Tip

How to Score Full Marks on This Unit

1. Diagrams Are Mandatory:

   • Draw functional/divisional/matrix structures with 3+ levels.
   • Label authority flows (e.g., "CEO → Finance Head → Accountants").

2. Compare with Examples:

   • Centralization vs. Decentralization: Use NTC (centralized) vs. Daraz (decentralized).
   • Job Design: Contrast NTC’s specialized meter readers vs. Ncell’s enriched customer support.

3. Guidelines for Delegation:

   • List all 6 guidelines and link each to a real company (e.g., Google’s delegation of app updates).

4. Case Study Approach:

   • If asked about organizing principles, apply them to Chaudhary Group’s retail vs. banking divisions.
   • For job design, analyze why Nabil Bank’s relationship managers are more productive than tellers.

5. Avoid Common Mistakes:

   • ❌ Saying "delegation is giving work to others." ✅ Say: "Delegation is transferring authority, responsibility, and accountability."
   • ❌ Drawing a matrix structure without dual reporting lines. ✅ Show both project and functional managers.

Sample High-Scoring Answer (2+8 Marks: Delegation Guidelines)

Delegation of authority is the process where a manager transfers specific tasks, authority, and responsibility to subordinates to achieve organizational goals efficiently.

Six guidelines for effective delegation:

1. Define Objectives Clearly: At Daraz, regional managers are given targets like "reduce delivery time by 15%" in their zones.
2. Select the Right Person: Ncell assigns tech-savvy employees to develop new apps, not call center agents.
3. Grant Sufficient Authority: Khalti’s fraud team can freeze accounts without waiting for HQ approval during cyberattacks.
4. Establish Accountability: Nabil Bank’s branch managers must submit weekly loan approval reports.
5. Provide Necessary Resources: NTC engineers are given updated software for network maintenance.
6. Monitor Progress: Google’s project managers hold bi-weekly stand-ups but avoid micromanaging.

Failure to delegate leads to bottlenecks (e.g., NTC’s slow decision-making) and employee disengagement (e.g., Nepal Police’s lack of autonomy). Effective delegation, as seen in Pathao’s rider incentives, boosts productivity and innovation.