How to Build a Car: The Autobiography of the World's Greatest Formula 1 Designer
Source: https://www.harpercollins.co.uk/products/how-to-build-a-car-adrian-newey ↗
Adrian Newey has designed more winning Formula 1 cars than any other engineer alive, and the book is his account of how the work actually happens: the tradeoffs, the iteration cycles, the relationship between intuition and data, the specific moments where a decision pays off four years later.
The register is unusual — a serious engineer writing honestly about creative work in a field where marginal improvements are measured in hundredths of seconds.
For product direction the parallels are striking: small teams, short cycles, ruthless measurement, a constant tension between innovation and reliability.
One of the best books about engineering-as-craft written in the last decade.
Central argument
Newey argues that championship-winning design emerges not from genius or resources alone, but from the disciplined integration of intuition and data across very short, high-stakes iteration cycles — and that the quality of a decision is often only legible years after it is made. His core claim is that competitive advantage in Formula 1 is a craft problem as much as an engineering one: it lives in the judgment calls made under constraint, not in the application of superior computation. The book traces how specific technical choices — aerodynamic philosophy, structural tradeoffs, team configuration — compound over seasons into dominant or failed machines.
Critique
The book's central limitation is that it accounts for success from a position of retrospective clarity, which makes the decision-making process look more coherent than it likely was in real time. Newey has spent his career at the frontier of a closed, highly funded system with unusually stable rules of measurement — hundredths of a second on a lap time — and the transferability of his intuitions to domains with messier, slower, or more contested feedback loops is left entirely to the reader to work out. There is also little structural engagement with failure: the near-misses and wrong directions are acknowledged but not analyzed with the same rigor as the wins, which risks producing a survivorship narrative dressed as craft theory.
Why it matters for product
For a CPO, the most useful provocation in Newey's account is the relationship between constraint and creativity: his best cars were often designed under tight regulatory or resource limits that forced genuine ingenuity rather than incremental elaboration, a direct parallel to the product question of whether expanding roadmap scope or headcount actually improves output quality. His framing of iteration cycles — where each design decision is a bet whose return is deferred to race day — maps directly onto the challenge of maintaining strategic coherence across quarterly delivery pressure, where teams optimize for visible short-term output at the expense of compounding architectural choices. The book is also useful on small-team configuration: Newey consistently worked with unusually lean design groups, and his account of how tight information loops and shared context outperformed larger fragmented organizations is a concrete argument against premature scaling in product development.