Fiveable

👥Organizational Behavior Unit 15 Review

QR code for Organizational Behavior practice questions

15.3 Organizational Designs and Structures

15.3 Organizational Designs and Structures

Written by the Fiveable Content Team • Last updated August 2025
Written by the Fiveable Content Team • Last updated August 2025
👥Organizational Behavior
Unit & Topic Study Guides

Organizational Structures

Organizational structures shape how companies operate and adapt to their environments. From rigid hierarchies to flexible networks, each structure carries distinct advantages and trade-offs. For managers, choosing the right structure means aligning it with the company's strategy, size, and environment.

Mechanistic vs. Organic Structures

These two categories sit at opposite ends of a spectrum, and most real organizations fall somewhere in between.

Mechanistic structures feature high formalization, clear hierarchies, and centralized decision-making. Think of military organizations or fast-food chains like McDonald's, where standardized procedures drive efficiency.

  • Well-suited for stable, predictable environments with routine tasks (manufacturing, assembly lines)
  • Efficient for large-scale operations producing standardized products or services
  • Drawback: they're slow to adapt when the environment shifts

Organic structures are flexible and decentralized, with fewer rigid rules. Startups and tech companies often operate this way.

  • Thrive in dynamic, rapidly changing environments that demand innovation (software development, consulting)
  • Effective for knowledge-based work and customized services
  • Drawback: can lack the consistency and control that larger operations need

The key takeaway: the best structure depends on the environment. A stable industry rewards mechanistic design; a volatile one rewards organic design. This idea comes directly from contingency theory.

Mechanistic vs organic structures, Common Organizational Structures | Principles of Management

Evolution of Organizational Structures

Organizational structures have shifted over the past century as business environments grew more complex.

  • Traditional hierarchical structures dominated the early 20th century (e.g., Ford Motor Company). These featured clear lines of authority, deep specialization, and centralized decision-making. They worked well for stable environments and mass production like assembly line manufacturing.
  • Divisional structures emerged in the mid-20th century as companies like General Electric expanded. Rather than organizing purely by function, divisions formed around product lines, geographic regions, or customer segments. This allowed faster responses to specific market needs, especially during international expansion.
  • Matrix structures gained popularity in the late 20th century, notably at organizations like NASA. These combined functional departments with project-based teams, creating dual reporting lines. The goal was cross-functional collaboration and better resource sharing, which proved valuable in complex industries like aerospace.
  • Networked team structures became prominent in the 21st century at companies like Google. These are flat and decentralized, emphasizing self-managed teams and horizontal collaboration. Advances in communication technology (including remote work tools) made them feasible. They're especially common in knowledge-intensive industries like software development.
Mechanistic vs organic structures, Organic versus Mechanistic Models | Organizational Behavior and Human Relations

Types of Organizational Structures

Each structure type involves real trade-offs. Here's a breakdown of the four main types, with both their strengths and weaknesses.

Functional Structure

Jobs are grouped by specialty (marketing, finance, operations, etc.), and each department reports up to top management.

Advantages:

  • Efficiency through specialization and shared resources within each function
  • Clear career paths within functional areas
  • Centralized control makes coordination straightforward

Disadvantages:

  • Departments can become silos, with limited cross-functional communication
  • Slow to respond to external changes like market shifts
  • Risk of suboptimization, where departments prioritize their own goals over the organization's

Divisional Structure

The organization splits into semi-autonomous divisions, each responsible for a product line, region, or customer group.

Advantages:

  • Each division can adapt to its specific market or customer needs
  • Decentralized decision-making means faster response times
  • Clear profit-and-loss accountability for each business unit

Disadvantages:

  • Duplication of resources across divisions (e.g., each division may have its own HR department)
  • Potential for inter-divisional conflict over resource allocation
  • Reduced economies of scale compared to functional structures, which can raise costs

Matrix Structure

Employees report to both a functional manager and a project or product manager simultaneously.

Advantages:

  • Strong cross-functional collaboration and knowledge sharing on project teams
  • Specialized experts can be shared efficiently across multiple projects
  • Balances functional depth with project-level focus

Disadvantages:

  • Dual reporting creates role ambiguity and potential conflict between managers
  • Communication overhead increases with multiple stakeholders
  • Maintaining balance between functional and project priorities is an ongoing challenge

Networked Team Structure

Work is organized around autonomous, often cross-functional teams rather than fixed departments.

Advantages:

  • Highly adaptable and responsive to change (often uses agile methodologies)
  • Empowers employees through decentralized decision-making
  • Fosters innovation by bringing diverse perspectives together

Disadvantages:

  • Accountability can be unclear when responsibility is diffused across teams
  • Difficult to maintain consistency and standardization across the organization
  • Coordinating multiple teams introduces communication barriers

Organizational Design Considerations

Beyond choosing a structure type, managers must make several design decisions that shape how the organization actually functions day to day.

  • Centralization vs. Decentralization: Centralization concentrates decision-making authority at higher levels, which improves consistency but can slow responses. Decentralization pushes authority to lower levels, promoting flexibility and faster local decision-making. Most organizations blend both depending on the type of decision.
  • Span of control refers to the number of direct reports a manager oversees. A wide span (many reports) creates a flatter organization with fewer management layers. A narrow span (few reports) creates a taller hierarchy with more oversight. The right span depends on the complexity of the work and how much autonomy employees need.
  • Departmentalization is the process of grouping jobs into logical units. The grouping method you choose (by function, product, geography, or customer) directly determines which structure type you end up with.
  • Organizational culture influences structure from the inside out. The values, norms, and behaviors that define "how things work here" affect whether a structure actually functions as designed. A culture that values autonomy, for instance, will resist a highly mechanistic structure, no matter what the org chart says.