Chapter 7: Organizational Structures

Organizational Structures

Organizational structure defines how activities are directed to achieve goals

Meta Summary: Organizational structure is the system that outlines how activities such as task allocation, coordination, and supervision are directed toward the achievement of organizational aims. This chapter covers structural types, elements, contingency factors, pros and cons, metrics, and case studies for designing effective structures in businesses, nonprofits, and public institutions.

Table of Contents

• Introduction to Organizational Structure
• Key Elements of Structure
• Types of Organizational Structures
• Contingency Factors in Design
• Pros and Cons of Each Structure
• Restructuring and Change Management
• Metrics for Structural Effectiveness
• Case Studies
• Related Topics
• FAQ
• References

Introduction to Organizational Structure

Definition and Purpose

An organizational structure defines how job tasks are formally divided, grouped, and coordinated. It specifies reporting relationships, formal communication channels, and decision-making authority. The structure is typically depicted in an organizational chart.

The purpose of structure is to control and coordinate employee behavior so that the organization achieves its goals efficiently. Structure affects communication patterns, job satisfaction, innovation, and responsiveness. A well-designed structure aligns with strategy, technology, and environment. A poor fit creates bottlenecks, duplication, conflict, and slow decision making.

Structure is not static. As firms grow, diversify, or face new technology and competition, they reorganize to maintain fit between structure and context.

Key Elements of Structure

Six Elements of Organizational Design

Researchers identify six key elements that managers consider when designing structure:

• Work Specialization: The degree to which tasks are subdivided into separate jobs. High specialization increases efficiency for routine work but can reduce flexibility and job satisfaction. Also called division of labor.
• Departmentalization: The basis on which jobs are grouped. Common forms: functional by expertise, product by output, geographic by region, process by workflow, and customer by market segment.
• Chain of Command: The line of authority extending from top to bottom. Includes authority, responsibility, and unity of command principles.
• Span of Control: The number of subordinates a manager can direct effectively. Wider spans reduce layers and costs but risk overload. Narrow spans allow close control but increase hierarchy.
• Centralization vs Decentralization: The degree to which decision making is concentrated at a single point. Centralized structures retain authority at the top. Decentralized structures delegate to lower levels, increasing responsiveness.
• Formalization: The degree to which jobs are standardized and employee behavior is guided by rules and procedures. High formalization reduces discretion; low formalization allows autonomy.

Organizational Behavior: Organizational Structures and Design

Types of Organizational Structures

Traditional Structures

1. Functional Structure: Groups employees by specialized function such as marketing, finance, production, and HR. Most common in small to medium firms. Promotes specialization and efficiency within functions.

2. Divisional Structure: Organized by product line, geography, or customer. Each division operates as a semi-autonomous unit with its own functional resources. Used by large, diversified firms like General Motors and Johnson & Johnson.

3. Matrix Structure: Combines functional and divisional chains. Employees have two bosses: a functional manager and a product or project manager. Improves cross-functional coordination for complex projects. Common in aerospace and consulting.

Investopedia: Organizational Structure

Contemporary Structures

1. Team-Based Structure: Breaks down departmental barriers and uses cross-functional teams. Authority is decentralized to teams. Increases flexibility and employee involvement.

2. Network Structure: Small core organization outsources major functions to other organizations. Also called virtual organization. The core coordinates a network of suppliers, distributors, and partners. Example: Nike focuses on design and marketing while contracting manufacturing.

3. Flat Structure: Few or no levels of middle management. Wide spans of control. Speeds decision making and reduces cost. Used by startups and tech firms. Example: Valve Corporation’s flat structure with no formal managers.

4. Holacracy: Authority distributed across self-organizing teams or circles. Roles replace job titles. Decisions made at the point of work. Zappos adopted holacracy to increase adaptability.

Harvard Business Review: The Right Way to Be Flat

Contingency Factors in Design

Strategy, Size, Technology, Environment

No single structure is best. Contingency theory states that effective structure depends on situational factors:

• Strategy: Innovation strategy requires organic, flexible structure with low formalization. Cost-leadership strategy fits mechanistic, efficient, centralized structures. Alfred Chandler: “structure follows strategy.”
• Size: As organizations grow, they become more formalized, specialized, and decentralized. Large size leads to more hierarchy and rules.
• Technology: Joan Woodward found that unit production uses organic structures, mass production uses mechanistic structures, and continuous process uses organic structures. Charles Perrow classified technology by task variability and problem analyzability.
• Environment: Stable environments favor mechanistic structures. Dynamic, uncertain environments require organic, adaptive structures. Burns and Stalker contrasted mechanistic and organic systems.

MindTools: Burns and Stalker's Mechanistic and Organic Structures

Pros and Cons of Each Structure

Comparison Table

Structure	Pros	Cons
Functional	Efficiency through specialization, clear career paths, economies of scale	Poor communication across functions, slow response, narrow viewpoints
Divisional	Focus on products or markets, accountability, flexibility	Duplication of resources, silos, competition between divisions
Matrix	Coordination across projects, efficient use of specialists	Dual authority confusion, power struggles, high overhead
Flat/Team	Fast decisions, empowerment, low cost	Role ambiguity, overload, hard to scale
Network	Flexibility, focus on core competence, low overhead	Loss of control, dependence on partners, coordination risk

Restructuring and Change Management

When and How to Reorganize

Restructuring is the act of reorganizing legal, ownership, operational, or other structures to improve profitability or adapt to change. Triggers include mergers, new strategy, technology disruption, or poor performance.

Common actions: downsizing, delayering, outsourcing, reengineering, and spinning off divisions. Risks include employee anxiety, loss of talent, and productivity dip. Success requires clear communication, participation, and alignment with culture.

Case Study: In 2015, Google reorganized under Alphabet Inc., creating a holding structure with separate divisions for core Google and “Other Bets” like Waymo and Verily. Goal: increase focus and transparency for investors while allowing innovation units autonomy.

Alphabet: 2015 Founders’ Letter on Restructure

Metrics for Structural Effectiveness

Measuring Design Outcomes

Effective structures are evaluated on:

• Span of Control Ratio: Average number of direct reports per manager. Too wide reduces coaching; too narrow increases cost.
• Layers of Hierarchy: Number of levels from CEO to front line. Fewer layers speed communication.
• Decision Time: Days from issue identification to decision. Indicates responsiveness.
• Coordination Cost: Time spent in meetings and cross-functional alignment.
• Employee Engagement: Survey scores on role clarity and empowerment.
• Customer Responsiveness: Lead time and service level metrics.

Organizational network analysis maps actual communication patterns versus formal chart to identify bottlenecks and silos.

Case Studies

Spotify: Squads, Tribes, Chapters, Guilds

Spotify developed an agile team-based model to scale engineering. A “Squad” is a small cross-functional team with end-to-end responsibility, like a mini-startup. A “Tribe” is a collection of squads in the same area. “Chapters” group specialists across squads for functional alignment. “Guilds” are communities of interest. The model balances autonomy and alignment without traditional hierarchy.

Outcome: Faster product releases and high employee autonomy. Challenge: Hard to replicate without strong culture.

Spotify Engineering Culture Part 1

Haier: Microenterprises

Chinese appliance maker Haier replaced its hierarchy with 4,000+ microenterprises. Each ME operates as a small business with P&L responsibility, serving internal or external customers. Employees can start MEs and elect leaders. Corporate sets strategy and provides platforms.

Outcome: Increased entrepreneurship and customer responsiveness. Revenue grew from $4B to $35B between 2000 and 2018.

Harvard Business Review: The End of Bureaucracy

Related Topics

• Organizational Culture
• Change Management
• Leadership and Power
• Job Design and Work Teams
• Strategy Implementation
• Corporate Governance

FAQ

What is the difference between mechanistic and organic structures?

Mechanistic structures are rigid, hierarchical, with high formalization, centralization, and specialization. They fit stable environments and routine technology. Organic structures are flexible, decentralized, with low formalization and wide spans. They fit dynamic environments and innovation strategies. Most firms are somewhere between the two.

Can a company have multiple structures?

Yes. Large firms use hybrid structures. A company may be functional at the top, divisional by region, and use project teams or matrix for new products. Structure can vary by business unit based on strategy and environment.

How often should structure be changed?

Only when strategy, size, or environment changes significantly. Frequent reorganization causes fatigue and lost productivity. Incremental adjustments to roles and processes are preferred over wholesale restructuring unless performance demands it.

References

Organizational Behavior: Organizational Structures and Design. OpenStax. Elements of structure and contingency factors.

Investopedia: Organizational Structure. Investopedia. Definitions and types of structures.

Harvard Business Review: The Right Way to Be Flat. HBR. Pros and cons of flat structures.

MindTools: Burns and Stalker's Mechanistic and Organic Structures. MindTools. Environment-structure fit.

Alphabet: 2015 Founders’ Letter on Restructure. Alphabet Inc. Case study of holding company structure.

Spotify Engineering Culture Part 1. Crisp. Squad, tribe, chapter, guild model.

Harvard Business Review: The End of Bureaucracy. HBR. Haier microenterprise case study.