05 Organization, Talent & LeadershipPublic · Free · Continuously updated

Organization Design: Choosing Among Five Common Structures

How work is divided, how authority flows, and how collaboration happens

Structure answers a basic question: who does what, who decides what, and how teams coordinate. Get it wrong and even a good strategy stalls. Here are five common structures, five diagnostics for choosing, and what organizations look like in the AI era.

Keywords:org designorganizational structurefunctional structuredivisional structurematrixflat organizationplatform organization

1. What an Org Structure Really Is

Organizational structure·The combined system of division of work, reporting lines (authority), and coordination mechanisms. It decides how tasks are assigned, where decisions sit, and how functions work together.

Good structure locks strategy, organization, and people together. Bad structure lets coordination costs eat every bit of efficiency.

2. Five Common Structures

Functional (U-form)

＋ Deep specialization, resource concentration, economies of scale

－ Silos, slow cross-team work, decisions pile up at the top

适合 Single business, small to mid size, stable environment

Divisional (M-form)

＋ Close to the market, clear accountability, own P&L

－ Duplicated resources, fiefdoms, HQ-unit tension

适合 Multiple products, regions, or customer groups

Matrix

＋ Shared resources, flexible staffing, strong cross-functional work

－ Dual bosses, internal conflict, heavy coordination cost

适合 Project work needing frequent cross-functional input

Flat

＋ Few layers, fast response, autonomy, honest information flow

－ Wide spans of control, easy to lose grip, demands mature people

适合 Innovative or knowledge-intensive small teams

Network / Platform

＋ Light assets, fast integration of external resources, scalable

－ Weak control, ecosystem dependence, uneven quality

适合 Platform, ecosystem, or resource-integrating firms

3. How to Choose: Five Diagnostics

Strategy

Integration plays favor functional or divisional forms; ecosystem plays favor networks.

Scale

Small teams stay flat; as you grow, push decisions down through divisions or a matrix.

Environment

Stable settings favor mechanistic forms; fast-changing settings favor organic ones.

Complexity

One business line favors functional design; multiple lines favor divisional design.

People maturity

Strong, accountable teams can take real delegation; newer teams need clearer frameworks first.

4. Organizations in the AI Era

Platform plus front line: a shared platform holds data and capability while small teams move fast
Fluid, mission-based teams form and dissolve around work rather than fixed seats
Human-machine units: AI handles routine execution and screening while people own judgment and creation
Flatter and more transparent: information no longer sits with layers of managers, so decision chains shorten

5. When to Reorganize

Structure follows strategy. Do not reshuffle unless strategy has truly changed; review every one to two years. Warning signs: slow decisions, silos, buck-passing, and customer problems with no owner.

Sequence matters: strategy first, structure second, then processes and incentives, and only then staffing.

Our View

Our view: there is no universally best structure, only the one that fits your strategy, scale, and environment. Copying a famous company is lazy, because its structure grew from its own strategy. And never redraw the boxes without also fixing processes and incentives.

Common Pitfalls

Myth: copying a big company's structure fixes problems. Reality: structure must fit your own strategy and scale.
Myth: redrawing the org chart means the organization has changed. Reality: without clear result ownership, the chart makes things worse.
Myth: reorganizing often keeps a company lively. Reality: every reshuffle has a real cost; change structure only when strategy changes.

FAQ

▸Does a small company need a formal structure?

Yes, even a simple one. If roles and authority are unclear, chaos arrives with growth.

▸Why do matrix structures so often fail?

Dual reporting without clear result ownership confuses everyone. One line must own the final result.

▸Will AI make organizations flat?

Information layers will flatten, but specialization stays. Expect platforms plus small agile teams plus human-machine units.

▸How often should structure change?

Follow strategy. If strategy has not changed, keep structure stable and review every one to two years.

Classes in this domainOrganization, Talent & Leadership

Organization Design: Choosing Among Five Common Structures Authority and Delegation The Talent Cycle: Select, Develop, Deploy, Retain The Logic of Incentives Performance and Goal Management Leadership and Self-Awareness Communicating and Negotiating Well Teamwork and Conflict Making Culture Real Change Management The Human-AI Organization A Map of Organizational Behavior

Next →Authority and Delegation

Back to class center →

Content is a rewritten synthesis of widely shared management consensus, free of any institution- or person-specific attribution, designed for quick foundations.