Build
Fadell built the iPod, the iPhone, and Nest. Build is structured as a book of advice organized by career stage and product phase. It is unusually honest about failure, about the texture of executive dysfunction, and about what it actually takes to ship physical products at Apple-level quality. The section on storytelling for products is particularly strong.
Summary
Fadell led the iPod team at Apple, worked on the first iPhone, then founded Nest and sold it to Google. He wrote this as practical advice organised around the stages of a career and a company.
The structure moves from individual to company. The early sections cover choosing what to work on, learning by doing rather than by planning, dealing with managers, and the transition from doing work to managing people, which he treats as a different job requiring different skills rather than a promotion.
The product sections are the strongest. Fadell argues that a product must solve a problem the customer actually has, that the customer journey begins with the advertisement and the packaging rather than with the product itself, and that the first version should be built for people who share the founder's frustration rather than for a mass market. He distinguishes painkillers from vitamins, argues that a product needs both a rational and an emotional justification because customers buy on emotion and justify rationally, and describes the discipline of setting a hard deadline as a forcing function on scope.
The company sections cover hiring, the specific mistakes founders make in fundraising, the difference between a product company and a business, the decision to sell, and the experience of being acquired, on which he is unusually candid about what went wrong at Nest inside Google.
The book is one operator's experience and does not claim research support. Fadell's cases are drawn from consumer hardware at Apple and Nest, and the advice reflects that context: hardware development cycles, physical constraints, retail and packaging. Founders in software or services should translate. He is opinionated and the tone will not suit everyone.
Key takeaways 7
- Managing people is a different job from doing the work, not a promotion, and it requires learning skills the previous role did not develop.
- The customer journey starts with the advertisement and the packaging, so those are part of the product rather than marketing around it.
- A first product should be built for people who share the founder's own frustration rather than for a general market.
- Products need both a rational justification and an emotional one, because customers decide emotionally and justify rationally.
- A hard deadline functions as a scope constraint that no amount of prioritisation discipline can replace.
- Founders should understand what an acquirer intends to do with the company before selling, because the stated intention frequently does not survive.
- Solving a problem the founder personally has is the most reliable source of the judgement required to make product decisions.
Who should read it
Founders and product leaders, particularly in hardware, who want direct operating advice from someone who shipped category-defining products.
Where it sits in the reference 2
Similar books 6
Chosen by shared topics, the entries that hold them, and the people who recommended both.
