The Liquidity Trap of Capability
In Keynes's original liquidity trap, the economy was flooded with cheap money that could not be converted into investment because firms could not identify investments worth making. Adding more liquidity to the saturated system was, as Keynes observed, like pushing on a string. The AI economy of 2026 has entered an analogous trap operating not on financial capital but on productive capability. The capability is abundant. AI tools have multiplied productive capacity by factors that cluster around the extraordinary. And yet organizations discover, with increasing frequency, that the additional capability does not automatically translate into additional value — because the bottleneck has migrated from production to direction.
In the AI Story
Keynes's original concept described the limit case of monetary policy. When interest rates approach zero and expectations collapse, further monetary expansion produces no additional investment because the constraint is not the cost of money but the absence of profitable projects. The Bank of England's experience in 1932 — cheap money sitting unused in vaults — was the empirical foundation.
The capability trap operates through structurally identical logic. AI tools provide productive capacity at near-zero marginal cost. An organization equipping its workforce with these tools and instructing workers to 'be more productive' is adding capability to a system without addressing the demand constraint. Workers produce more — but more of what? If the organization cannot articulate what is worth building, for whom, and why, the amplified output is amplified confusion.
The distinction Segal draws in The Orange Pill between 'doing old things faster' and 'attempting things that would never have been tried before' is, in Keynesian terms, the distinction between adding liquidity to a saturated system and generating new demand. The first activity is subject to the capability trap; the second escapes it.
The vector pods that The Orange Pill describes — small groups tasked not with building but with deciding what deserves to be built — represent one institutional response. They function as the organizational equivalent of Keynesian fiscal stimulus: deliberate investment in the capacity to generate effective demand within the organization rather than relying on the workforce's initiative to generate it spontaneously.
Origin
The liquidity trap concept was developed in the General Theory (1936) as the limiting case of Keynes's liquidity preference theory. The capability trap is an extension proposed in this volume.
Key Ideas
Capacity without direction. Productive capability approaches infinity while the judgment to direct it remains scarce.
Pushing on a string. Additional AI tools provide diminishing returns when the constraint is not capability but the capacity to deploy it.
The marginal efficiency of AI. Each additional subscription earns genuine returns only when directed at a genuine problem serving a genuine need.
Judgment as scarce resource. The bottleneck has migrated from execution to the evaluation of what deserves to be executed.
Institutional response. Escaping the trap requires deliberate investment in judgment cultivation, not additional capability acquisition.
Debates & Critiques
Whether the capability trap is a transitional phenomenon that will resolve as organizations develop judgment or a permanent structural feature of economies with near-zero-cost production.
Appears in the Orange Pill Cycle
Further reading
- John Maynard Keynes, The General Theory (1936), Chapters 13–17
- Paul Krugman, 'It's Baaack: Japan's Slump and the Return of the Liquidity Trap' (1998)
- Lance Taylor, Maynard's Revenge (2010)