Structure Follows Strategy — Not the Other Way Around

Alfred Chandler established the principle in 1962: structure follows strategy. When a company's organizational structure does not match its strategic priorities, execution degrades — not because people are incompetent, but because the system is working against them.

Consider a company that sets innovation as a strategic priority but organizes entirely by function. The functional structure optimizes for efficiency within disciplines but creates barriers between them. Innovation, which typically requires cross-functional collaboration, gets stuck in handoffs between departments. The strategy says innovate; the structure says stay in your lane.

The most common reason for organizational dysfunction is not bad people but misaligned structure. Before blaming execution, examine whether the organization is designed to execute the strategy you have chosen.

Four Common Structures and What They Optimize For

Functional: Organized by discipline (engineering, marketing, sales, finance). Optimizes for deep expertise and efficiency within functions. Works best when the company has a single product line and efficiency is the priority. Weakness: cross-functional coordination is difficult.

Divisional: Organized by product line, geography, or customer segment. Optimizes for responsiveness to specific markets. Works best for multi-product companies or businesses serving distinct customer segments. Weakness: duplicated functions across divisions reduce efficiency.

Matrix: Dual reporting to both functional and business unit leaders. Theoretically combines the benefits of functional and divisional. In practice, creates confusion about priorities and decision authority. Works only when governance is extremely clear about who decides what.

Networked/Team-Based: Organized around autonomous cross-functional teams. Optimizes for speed and innovation. Works best in rapidly changing environments where adaptation matters more than efficiency. Weakness: coordination across teams requires strong shared culture and technical infrastructure.

Designing the Right Structure for Your Strategy

Start with your strategic priorities, not your current org chart. If your strategy emphasizes customer intimacy, organize around customer segments. If it emphasizes operational efficiency, organize around functions. If it emphasizes innovation speed, organize around autonomous cross-functional teams.

Then design three elements: decision rights (who decides what), information flows (who needs what information to make those decisions), and incentives (what behaviors are rewarded). A structure that assigns the right decisions to the right people, gives them the information they need, and rewards the outcomes that strategy requires will execute effectively regardless of what the org chart looks like.

Reorganizations are disruptive. Do not reorganize because a new executive wants to put their stamp on the company or because someone read about a trendy structure. Reorganize only when there is clear evidence that the current structure is blocking strategic execution — and when you have a specific hypothesis about how the new structure will remove that blockage.