The Use of Knowledge in Society
The knowledge relevant for economic decisions is dispersed across society — never concentrated in a single mind.
No central planner can aggregate it well.
Markets work because they are a decentralised mechanism for processing information: prices transmit signals that no committee could ever replicate.
Read next to Coase, the question becomes: when is it worth centralising a decision (the firm) and when should dispersed information rule (the market)? AI reopens this question because it lets every node process more information than ever before.
Central argument
Hayek argues that the central problem of economic organization is not the allocation of given resources but the utilization of knowledge that is dispersed across millions of individuals and never available to any single mind in its totality. This knowledge is largely tacit and local — knowledge of particular circumstances of time and place — and cannot be aggregated or transmitted to a central authority without fatal distortion. The price system solves this problem not by collecting all the information but by condensing it into a single signal that coordinates action without requiring anyone to understand the whole picture.
Critique
Hayek's argument assumes that price signals are a sufficient and reliable encoding of dispersed knowledge, but prices can fail to capture externalities, long-term consequences, or forms of value that markets structurally underprice — commons, trust, public goods. More subtly, his framework treats the dispersion of knowledge as a fixed feature of reality, when in practice institutions actively shape what knowledge gets produced, by whom, and in what form. This is less a refutation of his mechanism than a reminder that the design of the information environment is itself a political and organizational choice, not a natural given.
Why it matters for product
A CPO building discovery processes faces exactly Hayek's dilemma: the knowledge about what users actually need lives at the edges — in support tickets, in sales calls, in the hands of the engineer who noticed a pattern — not in the roadmap meeting. Centralizing decisions about what to build too early destroys precisely the signal quality that makes good product direction possible. The organizational design implication is concrete: the question is not whether to empower teams but what price-equivalent mechanisms — OKRs, metrics, rapid experimentation — can aggregate distributed knowledge without requiring everyone to attend the same meeting.