the reasons and ways structures change, for example due to growth or delayering

7.1 Organisational Structure – Types of Structure

Think of an organisation like a city. The city’s layout (its streets, districts, and public transport) determines how people move, work, and communicate. Similarly, an organisation’s structure defines how tasks are divided, who reports to whom, and how information flows. 📍

Why Organisations Change Structure

Organisations evolve for many reasons, just like a city grows or shrinks. Key drivers include:

  • 📈 Growth – More products, markets, or employees require new departments or roles.
  • 🔄 Strategic shifts – Changing business goals can demand a different organisational layout.
  • ⚙️ Technology adoption – New tools may centralise or decentralise functions.
  • 💸 Cost optimisation – Delayering or merging units can reduce overhead.
  • 🌍 Global expansion – International operations often need regional hubs.

Common Types of Structure

StructureKey FeaturesWhen Used
🧩 FunctionalDepartments by function (e.g., Marketing, Finance)Small to medium firms; clear expertise focus
🏗️ DivisionalSeparate units by product, geography, or marketLarge, diversified companies
🛠️ MatrixDual reporting lines – functional & productComplex projects needing cross‑functional collaboration
🌀 FlatFew or no middle managers; high employee autonomyStart‑ups, creative agencies

Growth & Delayering – How Structures Change

When a company grows, it often needs to add layers (new departments) to handle increased complexity. However, too many layers can slow decisions. Delayering removes unnecessary middle management, speeding up communication – like flattening a multi‑storey building into a single‑floor space. 🏢➡️🏠

  1. 📊 Identify bottlenecks – Where do decisions get stuck?
  2. 🗂️ Merge similar functions – Combine overlapping roles.
  3. 👥 Empower teams – Give them decision‑making authority.
  4. 🔄 Re‑design reporting lines – Reduce the number of people a manager reports to.

Example: A tech start‑up grows from 10 to 200 employees. Initially, a single manager oversees all developers. As the team expands, a product manager is added, then a team lead for each product line. If the company later decides to streamline, it might remove the team leads and give developers more autonomy, creating a flatter structure.

Exam Tips & Quick Facts

Remember:

  • Use the right structure to match the company’s size, strategy, and culture.
  • When answering “Why does a company change its structure?”, mention growth, cost control, technology, and strategic realignment.
  • For delayering, highlight the benefits: faster decisions, clearer accountability, lower costs.
  • In exam questions, use diagrams (simple flowcharts) to illustrate changes.
  • Always link theory to real‑world examples (e.g., Apple’s shift to a product‑based structure).