Build: An Unorthodox Guide to Making Things Worth Making
Source: https://www.harpercollins.com/products/build-tony-fadell ↗
Fadell brought us the iPod and then went on to start Nest, and the book is his distillation of decades of building hardware and software products at Apple and beyond.
The format is advice-driven — chapters on what to do in your twenties, how to manage, how to deal with lawyers, how to decide when to quit — and the advice is specific because Fadell has done most of it wrong at least once.
For product direction it is one of the best books by a product-minded entrepreneur: Fadell thinks about products as physical objects with emotional relationships, which is a discipline that pure-software product people usually lack.
Ken Norton calls it one of the essential PM reads; the chapters on storytelling and on the difference between data and opinion are the strongest.
Opinionated, practical, honest about failure.
Central argument
Fadell argues that making products worth making requires treating them as physical objects with emotional relationships — not just feature sets or metrics dashboards — and that this discipline must be earned through repeated, specific failures across the full arc of a career: hiring, managing, storytelling, legal, and knowing when to quit. The book's central thesis is that good product judgment is inseparable from personal integrity and organizational honesty, and that most product failures are downstream of human and cultural decisions made long before any roadmap is written. Fadell grounds this in his own record at Apple and Nest, including mistakes he names explicitly.
Critique
Fadell's framework is built almost entirely from hardware product experience — the iPod and Nest — where physical constraints, manufacturing timelines, and retail presence impose a discipline that pure-software environments rarely face; his advice on iteration speed, organizational structure, and investor relationships may not translate cleanly to SaaS or platform product contexts where the feedback loops, cost structures, and reversibility of decisions are fundamentally different. There is also a tension between the book's anti-corporate posture and the fact that Fadell operated inside Apple, one of the most resource-rich and brand-protected environments in product history, which limits how far his risk tolerance and execution instincts can generalize.
Why it matters for product
The chapters on the distinction between data and opinion are directly useful for CPOs navigating the common organizational failure mode where quantitative metrics crowd out qualitative product judgment — Fadell gives a defensible framework for when to override the data and own the decision. His thinking on storytelling as a core product leadership competency, not a communications afterthought, is actionable for anyone trying to align executives, engineers, and designers around a product direction before evidence is conclusive.