Intro to Organizational Behavior (OB): Organizational Structure - Common Structures, Simple Bureaucracy, Functional, Divisional, Matrix, Team-Based, Network, Holacracy

Common Organizational Structures: Study Guide

What This Is

Organizational structure defines how tasks, authority, and communication flow in a company. It shapes efficiency, innovation, and employee behavior. For example, Google uses a team-based structure (small, cross-functional "pods") to foster agility, while McDonald’s relies on a functional bureaucracy (strict roles like marketing, operations, HR) for consistency.

Key Theories & Models

• Simple Structure (Entrepreneurial): Flat hierarchy with one leader (e.g., a startup founder). Implication: Fast decisions but risky as the company grows (e.g., early Zappos under Tony Hsieh).

• Functional Bureaucracy (Weber’s Ideal Type): Groups employees by specialty (e.g., finance, HR). Implication: Efficient for stable environments (e.g., Toyota’s production teams) but slow to adapt.

• Divisional Structure: Organizes by product, region, or customer (e.g., Disney’s divisions: Parks, Studios, Media). Implication: Better for diverse markets but can duplicate resources.

• Matrix Structure: Combines functional and divisional lines (e.g., Nike’s product teams report to both a sport category leader and a functional VP). Implication: Encourages collaboration but creates role ambiguity.

• Team-Based Structure: Cross-functional teams with autonomy (e.g., Spotify’s "squads" and "tribes"). Implication: Boosts innovation but requires strong culture (e.g., Valve’s no-manager policy).

• Network Structure: Outsources non-core functions (e.g., Nike’s manufacturing partners). Implication: Cost-effective but risks dependency (e.g., Apple’s reliance on Foxconn).

• Holacracy (Self-Management): No traditional hierarchy; roles are fluid (e.g., Zappos post-2015). Implication: Empowers employees but can cause confusion (e.g., Medium abandoned it after 4 years).

• Contingency Theory (Burns & Stalker): Structure should match environment: mechanistic (bureaucracy) for stability, organic (team/network) for innovation. Implication: Netflix shifted from DVDs (mechanistic) to streaming (organic).

Step-by-Step Application

1. Diagnose the Environment:
2. Stable industry (e.g., utilities)?-Functional bureaucracy.

3. Fast-changing (e.g., tech)?-Team-based or network.

4. Assess Strategy:

5. Cost leadership (e.g., Walmart)?-Functional.

6. Innovation (e.g., Tesla)?-Matrix or team-based.

7. Evaluate Culture:

8. Control-oriented (e.g., McDonald’s)?-Bureaucracy.

9. Autonomy-driven (e.g., Valve)?-Holacracy or team-based.

10. Address Trade-offs:

11. Matrix: Clarify reporting lines (e.g., Microsoft’s dual-reporting in engineering).

12. Network: Mitigate outsourcing risks (e.g., Boeing’s 787 delays due to supplier issues).

13. Pilot Changes:

14. Test structures in one division (e.g., Amazon’s "two-pizza teams" before scaling).

Common Misconceptions

• Misconception: "Flat structures always improve innovation." Correction: Without clear roles, chaos ensues (e.g., Zappos’ holacracy led to 18% turnover in 2015).

• Misconception: "Bureaucracy is always bad." Correction: It’s efficient for routine tasks (e.g., Southwest Airlines’ standardized boarding process).

• Misconception: "Matrix structures eliminate silos." Correction: They create new silos (e.g., Nike’s product teams vs. regional teams).

• Misconception: "Network structures are cheaper." Correction: Hidden costs (e.g., Apple’s supply chain disruptions during COVID).

Exam / Case Interview Tips

• Question Pattern: "Which structure fits [Company X]’s strategy?" Answer: Link to Contingency Theory (e.g., "For a fast-fashion brand like Zara, a divisional structure by region enables speed").

• Tricky Distinction: Functional vs. Divisional

• Functional: Specialization (e.g., Ford’s engineering teams).

• Divisional: Market focus (e.g., GE’s aviation vs. healthcare divisions).

• Case Trap: Ignoring culture.

• Example: Netflix’s "freedom and responsibility" culture enables its team-based structure.

Quick Practice Scenario

Scenario: A biotech startup (50 employees) is struggling with slow decisions and duplicated work. The CEO wants to restructure. Question: Which structure should they adopt, and why? Answer: Functional bureaucracy (group by R&D, clinical, operations) to reduce redundancy, but keep a simple structure for cross-team projects to maintain agility.

Last-Minute Cram Sheet

1. Simple Structure: One leader, fast decisions (e.g., early Zappos).
2. Functional Bureaucracy: Specialized teams (e.g., Toyota).
3. Divisional: Product/region focus (e.g., Disney).
4. Matrix: Dual reporting (e.g., Nike).
5. Team-Based: Cross-functional (e.g., Spotify).
6. Network: Outsourced non-core (e.g., Nike).
7. Holacracy: No hierarchy (e.g., Zappos).
8. Mechanistic vs. Organic: Bureaucracy (stable) vs. team-based (innovative).
9. Matrix Trap: Role conflict (e.g., Microsoft’s old "two bosses" problem).
10. Network Risk: Dependency (e.g., Boeing 787 delays).