Intro to Organizational Behavior (OB): Organizational Structure - Six Elements of Structure, Work Specialisation Departmentalization Chain of Command Span of Control CentralizationDecentralization Formalization

Six Elements of Organizational Structure: Study Guide

What This Is

The six elements of structure define how work is divided, coordinated, and controlled in an organization. These elements—work specialization, departmentalization, chain of command, span of control, centralization/decentralization, and formalization—shape efficiency, communication, innovation, and employee autonomy. A well-designed structure aligns with strategy (e.g., Google’s flat, team-based structure fosters innovation, while McDonald’s rigid hierarchy ensures consistency in global operations).

Key Theories & Models

• Work Specialization (Division of Labor – Adam Smith, The Wealth of Nations) Breaking jobs into narrow, repetitive tasks to improve efficiency. Implication: High specialization boosts productivity (e.g., assembly lines) but can reduce motivation and flexibility (e.g., Tesla’s early over-specialization led to burnout).

• Departmentalization (Grouping Jobs – Functional, Product, Geographic, Process, Customer) How jobs are grouped (e.g., marketing vs. engineering, or by region like Coca-Cola’s geographic divisions). Implication: Functional structures (e.g., Apple) improve expertise but create silos; cross-functional teams (e.g., Spotify’s "squads") enhance collaboration.

• Chain of Command (Authority Hierarchy – Max Weber’s Bureaucracy) The unbroken line of authority from top to bottom (e.g., military, Walmart). Implication: Clear chains reduce confusion but slow decision-making (e.g., Netflix’s "no rules" culture minimizes hierarchy to speed innovation).

• Span of Control (Narrow vs. Wide – Graicunas’ Theory) Number of subordinates a manager oversees. Implication: Narrow spans (e.g., traditional banks) allow tight control but increase costs; wide spans (e.g., Zappos’ holacracy) empower employees but risk chaos if leadership is weak.

• Centralization vs. Decentralization (Decision-Making Authority – Burns & Stalker’s Mechanistic vs. Organic Structures) Centralized: Top-down decisions (e.g., McDonald’s). Decentralized: Frontline autonomy (e.g., Nordstrom’s "use your best judgment" policy). Implication: Centralization improves consistency; decentralization boosts agility (e.g., Amazon’s "two-pizza teams").

• Formalization (Rules & Procedures – Weber’s Bureaucracy) Degree of standardization (e.g., UPS’s strict delivery protocols vs. Google’s flexible "20% time"). Implication: High formalization reduces ambiguity but stifles creativity (e.g., 3M’s "15% rule" encourages innovation by relaxing rules).

Step-by-Step Application: Designing or Diagnosing Structure

1. Assess Strategy & Environment
2. Stable environment?-Mechanistic (high specialization, centralization, formalization; e.g., Toyota).

3. Dynamic environment?-Organic (low specialization, decentralization, low formalization; e.g., Airbnb).

4. Map Current Structure

5. Draw an org chart. Identify:

   • Work specialization (e.g., "Are roles too narrow?").
   • Departmentalization (e.g., "Are silos blocking collaboration?").
   • Chain of command (e.g., "Are decisions bottlenecked?").

6. Diagnose Problems

7. Slow decisions?-Decentralize (e.g., Netflix’s "context, not control").
8. High turnover?-Reduce specialization/formalization (e.g., Zappos’ job rotation).

9. Poor coordination?-Cross-functional teams (e.g., Spotify’s squads).

10. Adjust Span of Control

11. Complex tasks?-Narrow span (e.g., NASA).

12. Simple/repetitive tasks?-Wide span (e.g., call centers).

13. Balance Centralization

14. Need consistency?-Centralize (e.g., Starbucks’ global standards).

15. Need local adaptation?-Decentralize (e.g., Unilever’s regional autonomy).

16. Formalize (or Not)

17. High-risk operations?-High formalization (e.g., nuclear plants).
18. Creative work?-Low formalization (e.g., Pixar’s "braintrust" meetings).

Common Misconceptions

• Misconception: "More specialization always increases productivity." Correction: Over-specialization leads to boredom and errors (e.g., GM’s assembly lines in the 1980s). Solution: Job rotation (e.g., Toyota’s "multi-skilling").

• Misconception: "Flat structures (wide spans) are always better." Correction: Without strong leadership, wide spans cause confusion (e.g., early Uber’s "move fast" culture led to scandals). Solution: Balance autonomy with clear accountability.

• Misconception: "Centralization is outdated." Correction: Centralization works for standardized processes (e.g., Amazon’s warehouse operations). Solution: Use hybrid models (e.g., Apple’s centralized design + decentralized retail).

• Misconception: "Formalization kills innovation." Correction: Some formalization is necessary (e.g., FDA drug approvals). Solution: Formalize processes, not creativity (e.g., 3M’s "15% rule" has guardrails).

• Misconception: "Chain of command is irrelevant in modern orgs." Correction: Even flat orgs need clarity (e.g., Valve’s "boss-free" structure still has informal leaders). Solution: Replace rigid chains with "networks of influence."

Exam / Case Interview Tips

1. Spot the Trade-Offs

2. Questions will ask: "Should we centralize or decentralize?" Frame answers with:

   • Centralization: Efficiency, consistency, control (e.g., McDonald’s).
   • Decentralization: Speed, innovation, local adaptation (e.g., Netflix).

3. Link Structure to Strategy

4. "Why does Google use a matrix structure?"-Answer: To balance functional expertise (engineering) with product focus (Google Search, YouTube).

5. Avoid "One-Size-Fits-All"

6. "Is a flat structure better than a hierarchy?"-Answer: Depends on environment (e.g., flat works for startups; hierarchy works for hospitals).

7. Use Real Examples

8. "How would you redesign a bureaucratic bank?"-Answer: Reduce formalization (e.g., ING’s agile "squads"), widen spans, decentralize loan approvals.

Quick Practice Scenario

Scenario: A fast-growing tech startup (100 employees) is struggling with duplicated efforts, slow decisions, and frustrated engineers. The CEO wants to "scale like Google" but isn’t sure how. Question: Which structural elements should they adjust, and how? Answer:
1. Departmentalization: Shift from functional silos (e.g., "engineering" vs. "marketing") to cross-functional teams (e.g., product squads like Spotify).
2. Span of Control: Widen spans for managers to reduce layers (e.g., 1 manager-10 engineers).
3. Centralization: Decentralize decision-making (e.g., let squads approve features).
4. Formalization: Reduce rules (e.g., replace approvals with "guidelines"). Why? Google’s matrix structure balances autonomy and coordination; startups need agility over control.

Last-Minute Cram Sheet

1. Work Specialization: Division of labor-efficiency vs. boredom ( over-specialization = burnout).
2. Departmentalization: Grouping by function, product, geography, or customer ( silos = poor collaboration).
3. Chain of Command: Authority hierarchy ( rigid chains = slow decisions).
4. Span of Control: Narrow (control) vs. wide (autonomy) ( wide spans need strong leadership).
5. Centralization: Top-down decisions ( too much = bureaucracy).
6. Decentralization: Frontline autonomy ( too much = chaos).
7. Formalization: Rules vs. flexibility ( high formalization = less innovation).
8. Mechanistic Structure: Rigid, hierarchical (e.g., McDonald’s).
9. Organic Structure: Flexible, flat (e.g., Google).
10. Matrix Structure: Dual reporting ( can cause role conflict, e.g., "Who’s my real boss?").

Trap: "Flat structures have no hierarchy"-False: They have informal hierarchies (e.g., Valve’s "desk moving" culture).