Organizing: Structures, Design & Coordination in Hotels

TAKEAWAYS

• Organizing is the process of grouping activities, assigning authority, and coordinating resources to achieve goals efficiently.
• Organizational structures (line, functional, divisional, matrix) determine how power, communication, and accountability flow in a hotel.
• Departmentalization (by function, product, geography, or customer) helps specialize roles but can create silos if poorly managed.
• Delegation involves assigning authority, responsibility, and accountability—critical for managing workload in large hotels.
• Span of control (narrow vs. wide) impacts supervision efficiency; too wide leads to micromanagement, too narrow creates bottlenecks.
• Coordination ensures departments work together seamlessly, especially in high-volume operations like banquets or housekeeping.

What is Organizing?

Organizing is the third function of management (after planning and decision-making) and involves:

1. Dividing work into manageable tasks.
2. Grouping tasks into departments or teams.
3. Assigning authority to complete tasks.
4. Coordinating activities to achieve organizational goals.

Why is organizing crucial in hospitality? Hotels like Hyatt Regency Kathmandu or Dwarikas Hotel must structure their workforce to handle:

• Front-office (reception, reservations)
• Housekeeping (room service, laundry)
• Food & Beverage (restaurants, room service)
• Maintenance (repairs, security)

Without clear organizing, chaos arises—imagine a Daraz warehouse where inventory, shipping, and customer service teams aren’t aligned!

Key Elements of Organizing

1. Division of Work

• Specialization improves efficiency (e.g., a KFC chef focuses only on frying, not cooking full meals).
• Adam Smith’s pin factory example: One worker shapes pins, another cuts, another polishes—hotels apply this too (e.g., a buffet server only refills plates, not cleans rooms).

2. Departmentalization

Hotels use four main types of departmentalization:

3. Delegation: Authority, Responsibility, and Accountability

Delegation is assigning work to subordinates while retaining accountability. In hotels:

• Authority: Power to make decisions (e.g., a F&B manager can approve menu changes).
• Responsibility: Duty to perform (e.g., a room attendant must clean rooms daily).
• Accountability: Answering for results (e.g., if a banquet fails, the event manager is accountable).

**How delegation works in Pathao’s driver-hub system:

1. Hub (Headquarters) delegates routes to drivers.
2. Drivers (Subordinates) have authority to pick up passengers but must follow safety rules.
3. Accountability: If a driver causes an accident, Pathao’s system holds them responsible.

Mermaid Diagram: Delegation Process

flowchart TD
    A["Manager (Hotel GM)"] -->|"Delegates"| B["Authority"]
    A -->|"Assigns"| C["Responsibility"]
    B --> D["Subordinate (F&B Manager)"]
    C --> D
    D -->|"Performs"| E["Task: Organize Buffet"]
    D -->|"Reports Back"| A
    A -->|"Holds Accountable"| D

4. Span of Control

• Narrow span: Few subordinates per manager (e.g., Michelin-starred chef supervising 2 sous-chefs).
• Wide span: Many subordinates (e.g., housekeeping supervisor managing 20 attendants).

Impact on hotels:

**Real-world case: Nabil Bank’s branch structure

• Narrow span: Branch managers oversee only 3-4 tellers for high security.
• Wide span: Regional managers handle 10+ branches but rely on technology (ATMs, online banking).

5. Coordination

Ensures departments work together smoothly. Three key methods:

1. Direct Contact: Managers meet daily (e.g., hotel morning briefing).
2. Rules & Policies: Standard operating procedures (SOPs) (e.g., Daraz’s return policy).
3. Technology: ERP systems (e.g., Opera PMS in hotels tracks reservations, billing, and housekeeping).

**Case Study: Khalti’s Payment Coordination

• Problem: Multiple banks, fintech firms, and merchants must sync transactions.
• Solution:
  • Centralized API (like a hotel’s POS system) coordinates payments.
  • Real-time updates ensure no double-bookings (like NTC’s ticketing system).

In the Real World

1. Daraz (Nepal’s Amazon)

   • Organizational Structure: Uses a divisional model—separate teams for inventory, logistics, and customer service.
   • Challenge: Coordination between warehouses in Kathmandu, Pokhara, and Biratnagar requires matrix management for seasonal sales (e.g., Dashain).
   • Example: During Black Friday, Daraz’s Fulfillment team (logistics) and Marketing team must align promotions with stock availability.

2. Nabil Bank (Nepal)

   • Departmentalization: Functional structure with Retail Banking, Corporate Banking, and Digital Banking departments.
   • Delegation: Branch managers have authority to approve loans up to Rs. 5 lakhs but must report larger decisions to the Credit Committee.
   • Span of Control: Wide span for regional managers (10+ branches) but narrow span for fraud detection teams (high accountability).

3. Himalayan Java (Coffee Chain)

   • Geographical Departmentalization: Separate teams for Kathmandu, Pokhara, and Chitwan outlets.
   • Coordination: Uses a centralized POS system to track inventory (e.g., if Pokhara runs out of cardamom coffee, Kathmandu’s supply chain alerts them).
   • Matrix Structure: Temporary teams for corporate events (e.g., a Google Nepal team event requires F&B, AV, and HR coordination).

Organizational Structures in Hotels

Hotels commonly use three structures:

1. Line Structure (Simple, direct chain of command)

   • Example: Small boutique hotels like The Pearl Hotel, Pokhara.
   • Pros: Clear authority, fast decisions.
   • Cons: Overburdened top management, slow adaptation.

   flowchart TD
       A["General Manager"] --> B["Front Office Manager"]
       A --> C["F&B Manager"]
       A --> D["Housekeeping Manager"]
       B --> E["Receptionists"]
       C --> F["Chefs"]
       D --> G["Room Attendants"]

2. Functional Structure (Specialized departments)

   • Example: Hyatt Regency Kathmandu (HR, Finance, F&B, Housekeeping).
   • Pros: Expertise, efficiency.
   • Cons: Poor cross-department coordination.

   flowchart TD
       A["GM"] --> B["HR Manager"]
       A --> C["Finance Manager"]
       A --> D["F&B Manager"]
       A --> E["Housekeeping Manager"]
       D --> F["Chef"]
       D --> G["Waitstaff"]

3. Matrix Structure (Project-based teams)

   • Example: Sofitel Kathmandu for wedding planning (combines F&B, HR, and Events teams).
   • Pros: Flexibility, innovation.
   • Cons: Complex reporting, conflicts.

   flowchart TD
       A["GM"] --> B["Functional Managers"]
       A --> C["Project Manager (Wedding)"]
       B --> D["HR"]
       B --> E["F&B"]
       C --> D
       C --> E
       C --> F["Events Team"]

Factors Affecting Organizational Design

1. Nature of Business: A luxury hotel (e.g., Dwarikas) needs a narrow span for personalized service, while a budget hotel (e.g., Hotel Everest) can have a wide span.
2. Size of Organization: Small hotels (10 rooms) use line structure; large chains (e.g., Taj Hotels) use functional or matrix.
3. Technology: ERP systems (like Opera PMS) reduce the need for wide spans by automating coordination.
4. Environment: Unstable markets (e.g., post-earthquake Kathmandu) require flexible structures.

Worked Example: Organizing a Banquet at Sofitel Kathmandu

Scenario: Sofitel is hosting a 500-guest corporate event. How would they organize?

1. Departmentalization:

   • F&B Team: Catering, bar service, dietary restrictions.
   • Housekeeping: Table settings, linen, cleanup.
   • Events Team: AV, seating, guest list.
   • Security: Crowd control, emergency exits.

2. Delegation:

   • Banquet Manager (authority to approve menu changes).
   • Chef (responsibility for food quality).
   • Event Coordinator (accountable for AV setup).

3. Span of Control:

   • Narrow span: Banquet manager supervises 3 team leads (F&B, Events, Housekeeping).
   • Wide span: Each team lead manages 10+ staff.

4. Coordination:

   • Daily briefings at 8 AM.
   • Walkie-talkies for real-time updates.
   • SOP checklist (e.g., "All tables set by 4 PM").

Potential Challenges & Solutions:

Exam Tip

1. Define organizing clearly: Start with "Organizing is the process of..." and link it to efficiency and coordination.
2. Compare structures: Always draw two organizational charts (e.g., line vs. functional) and explain pros/cons in a table.
3. Use real-world examples:
   • Hotels: Hyatt (functional), Sofitel (matrix for events).
   • Nepali companies: Daraz (divisional), Nabil Bank (functional).
   • Global: McDonald’s (geographical), Google (matrix for projects).
4. Delegation questions: Expect 3-4 marks on authority vs. responsibility vs. accountability. Use the Pathao driver example or Nabil Bank loan approvals.
5. Span of control: Relate to hotel sizes—small hotels = narrow span; large chains = wide span with technology support.
6. Coordination methods: Mention at least two (e.g., SOPs + technology) with an example like Khalti’s API system.

Common Mistakes to Avoid:

• Confusing delegation with decentralization (delegation is task-specific; decentralization is power-sharing).
• Ignoring real-world constraints (e.g., saying a 5-star hotel should have a wide span without considering service quality).
• Forgetting visuals—examiners love organizational charts and comparison tables.