The Theory of the Growth of the Firm
Penrose fills the gap between Coase and Chandler.
Coase explained why firms exist; Chandler documented how they grew; Penrose explains the mechanism — firms grow by deploying accumulated knowledge and unused resources into adjacent opportunities.
Growth is not a response to market signals alone but a consequence of what the organisation has learned to do.
This is the origin of the resource-based view of the firm, later developed by Wernerfelt and Barney, and the intellectual ancestor of every "capabilities" argument in strategy.
For product people it reframes the question: the constraint on what you can build next is not the market but the knowledge your organisation has accumulated and can redeploy.
Central argument
Penrose argues that firm growth is not driven primarily by market demand or profit signals but by the productive services that flow from underutilised internal resources — physical assets, but above all managerial and organisational knowledge. As a firm operates, it accumulates capabilities that generate 'slack': resources and competencies not fully deployed, which create internal pressure and opportunity to expand into adjacent activities. Growth is therefore an endogenous process shaped by what the firm has learned to do, not merely a response to external opportunity.
Critique
Penrose's framework is richly explanatory but weakly predictive: it describes conditions under which growth becomes possible without specifying which opportunities firms will pursue or how they will fail. The theory assumes that managerial cognition and resource recombination are largely rational and deliberate, underweighting how political dynamics, inertia, and misaligned incentives inside organisations systematically distort the deployment of accumulated knowledge. For a theory that places management at the centre, it is surprisingly silent on the conditions under which managerial judgement degrades or becomes the binding constraint itself.
Why it matters for product
For a CPO, Penrose reframes roadmap prioritisation as a capabilities audit rather than a market-sizing exercise: the honest question is not where the market opportunity is largest but where your organisation's accumulated product, data, and domain knowledge gives you a genuine deployment advantage over a greenfield team. It also has direct consequences for team design — spinning up a new product area without the requisite organisational knowledge already resident in the team is not a resource problem but an epistemic one, and no amount of hiring velocity closes that gap quickly. This is why platform bets and adjacency moves succeed or fail on capability inheritance, not market logic alone.