Tyranny of the SBU
The tyranny of the SBU is Prahalad's diagnostic name for a specific organizational pathology he observed across American conglomerates in the 1980s. The Strategic Business Unit structure made each division accountable for its own profit and loss, which encouraged short-term optimization within each silo at the expense of the cross-divisional learning that produced long-term competitive advantage. The result was organizations that looked efficient on paper — each division optimized for its own market — but were strategically hollowed out, unable to combine capabilities across divisions, unable to enter new markets requiring cross-divisional collaboration, unable to develop the integrated capabilities the next generation of competition would demand.
In the AI Story
Headcount reduction in the AI age is the new tyranny of the SBU. It fragments the organization's collective intelligence by removing the nodes through which cross-functional learning flows. It optimizes the current quarter's profit and loss statement at the expense of the organizational capacity future competition will demand. It makes the numbers look good while destroying the capability that generates sustainable competitive advantage.
The parallel operates at the level of mechanism, not just metaphor. When an SBU-organized corporation lost a key engineer who understood how division A's optical technology could combine with division B's microprocessor controls, the corporation did not merely lose one person. It lost the connection between two domains of expertise — the living bridge that enabled cross-divisional integration. The loss was invisible in any single division's P&L. It became visible only when the corporation attempted to enter a new market requiring the combination, and discovered the capability was gone.
The same mechanism operates when AI-augmented teams are reduced. The senior architect who understands how the backend system interacts with the user experience layer is not merely an individual contributor whose output can be measured in lines of code. She is a node in the organization's collective intelligence — a point of integration between domains whose interaction produces the organization's most valuable capabilities.
Origin
The concept emerges from Prahalad and Hamel's 1990 HBR article The Core Competence of the Corporation, which diagnosed the SBU structure as the primary obstacle to competence-based strategy in American corporations.
Key Ideas
Silo optimization. Each division optimizes locally, eroding cross-divisional integration.
Looks efficient, is hollow. The numbers appear strong while capability is destroyed.
Bridge engineers invisible. The people who connect domains do not show up as valuable in any single P&L.
Reduction reproduces SBU logic. Headcount cuts in AI-era orgs fragment the same way SBUs fragmented conglomerates.
New market entry fails. The consequences surface only when integrated capabilities are needed.
Appears in the Orange Pill Cycle
Further reading
- Prahalad, C. K. & Hamel, Gary. The Core Competence of the Corporation (Harvard Business Review, 1990).
- Chandler, Alfred D. Strategy and Structure (MIT Press, 1962).