The Dream Machine: J.C.R. Licklider and the Revolution That Made Computing Personal
Waldrop's biography of J.C.R.
Licklider is also the most complete single-volume history of how personal computing came to be — from Vannevar Bush's "As We May Think" through ARPA funding, Xerox PARC, and the early internet.
Licklider is the connecting figure because he funded, inspired or directly enabled almost every major development, often by placing bets on people rather than on specific technologies.
For product direction the book is essential history: the computing environment we ship products into was shaped by specific people making specific decisions under specific institutional constraints, and understanding those decisions clarifies what "technology" actually is.
Long, detailed, written with a biographer's patience. The Stripe Press reissue is the edition to find.
Central argument
Waldrop's central argument is that personal computing was not an inevitable technological progression but the product of one man's vision — J.C.R. Licklider's conviction that computers could augment human thinking rather than merely automate calculation — translated into institutional reality through his control of ARPA funding in the early 1960s. By betting on people like Douglas Engelbart, Ivan Sutherland, and the researchers who would populate Xerox PARC, Licklider seeded a distributed network of talent and ideas whose compounding effects produced the interactive, networked computing environment we inhabit today. The book's implicit thesis is that technological revolutions are fundamentally social and financial before they are technical: the internet and the PC exist because a psychologist with a budget chose to fund curiosity over deliverables.
Critique
Because the narrative is organized around Licklider as the indispensable connective figure, the book risks overfitting the history to a great-man structure that its own evidence quietly undermines — the researchers Licklider funded were already brilliant and motivated, and similar pressures (Cold War funding, academic computing demand) were operating independently. A more structural account might ask whether ARPA's particular funding model, rather than Licklider's personal vision, was the decisive variable, and whether a different program manager with the same institutional latitude would have produced comparable results. The book is also U.S.-centric in a way that treats ARPA as the sole generative environment, leaving the parallel British and European contributions to interactive computing largely outside the frame.
Why it matters for product
The most direct lesson for product leadership is Licklider's method of resource allocation: he funded researchers whose judgment he trusted rather than scoping projects around predetermined outputs, which is a coherent model for how to structure discovery investment inside a product organization where the problem space is genuinely uncertain. More concretely, the book shows how institutional constraints — who controls budget, what counts as a legitimate deliverable, how long a time horizon is tolerated — determine the solution space before any product decision is made, which should sharpen how a CPO reads the organizational conditions surrounding their roadmap. Understanding that the computing substrate product teams ship into was itself the result of specific funding decisions and specific people making bets is a useful corrective to treating 'technology' as a neutral given rather than a sediment of prior choices.