Organizing and Structure

Drawing the Machine

Organizing turns a strategy into an architecture: who does what, who decides what, who reports to whom. Six dials define any structure:

• Division of labor — how finely work is split into specialized jobs.
• Departmentalization — how jobs are grouped: by function (all engineers together), product (each line self-contained), geography, customer, or in a matrix (function × project, two bosses per person).
• Chain of command — the line of authority; classical doctrine says each person answers to one boss (unity of command) — the rule the matrix deliberately breaks.
• Span of control — how many report to each manager. Narrow spans mean close supervision and tall structures; wide spans mean autonomy and flat ones. The trade is geometric: with span $s$ and $N$ workers, the hierarchy needs about $\log_s N$ layers — widening the span collapses whole floors of management.

$$\text{layers} \approx \log_s N$$

Example: with a span of 4, 4,096 workers need 6 layers of management; widen the span to 8 and only 4 layers remain.

• Centralization — where decisions live: at the top (consistency, control) or pushed down (speed, local knowledge).
• Formalization — how much behavior is written into rules and procedures.

Two master profiles bundle the dials (Burns & Stalker): the mechanistic organization — tall, centralized, formalized, function-based — thrives in stable environments where efficiency wins; the organic organization — flat, decentralized, informal, team-based — thrives in turbulent ones where adaptation wins. Neither is 'modern' or 'obsolete': the environment grades the design. A nuclear plant should be mechanistic; a game studio organic; a bank needs both, in different rooms.

Staff vs line completes the map: line roles sit on the value chain and command; staff roles (legal, HR, analytics) advise it. The chronic friction between them is structural, not personal.

The six structural dials

Common pitfall: Calling the matrix's two bosses a design flaw. The matrix deliberately breaks unity of command to force the function-project conversation — its failure mode is not the dual reporting itself but leaving the two bosses' conflicts unarbitrated.