Quick Take
- Narration: Tristan Morris handles the technical and human threads of Davies’s narrative with consistent energy, keeping a sprawling cast of engineers, academics, and executives distinct.
- Themes: Technological competition and collaboration, the gap between ambition and engineering reality, Silicon Valley’s relationship with the auto industry
- Mood: Propulsive and character-driven, like a Silicon Valley drama with actual technical stakes
- Verdict: The definitive popular account of how the driverless car went from DARPA competition to industry obsession, told with the depth of someone who was there for most of it.
I finished Driven on a Sunday evening, sitting in a car that I had, in fact, driven myself, and felt the particular strangeness of that fact in a way I hadn’t before. Alex Davies’s history of the autonomous vehicle industry does something that good technology journalism does when it’s working at its best: it makes you see a familiar object, in this case the car and the assumption of human control built into its design, as a genuinely contingent historical artifact rather than an inevitable fact of life.
Davies covered the self-driving car beat for WIRED for years, which gives him access and context that general-interest writers rarely have. This is reporting, not synthesis. He spoke to the people who built these systems, attended the DARPA Grand Challenges, and watched the industry’s relationships, rivalries, and disasters develop in real time. That proximity shows in the texture of the book.
The DARPA Moment That Started Everything
The book’s best section concerns the DARPA Grand Challenges, the federal competitions in the early 2000s that functioned as a kind of accelerant for the entire field. Davies is brilliant on the chaos and energy of those early races, when teams of amateurs and academics were competing against each other in the desert with vehicles that, by current standards, barely functioned. The human drama is rich: rivalries between teams, the outsider status of many of the participants, the way that failure at these competitions could paradoxically advance the technology by revealing where the real problems lay.
This section is also where Davies establishes his book’s central argument about the sociology of innovation: the best people who emerged from the Challenges weren’t necessarily the winners, and the talent that eventually moved to Google and Uber came from across the competitive field. The academic tournament as a talent identification system is a real phenomenon, and Davies traces it with precision.
The Silicon Valley Chapter and Its Complications
The middle section, covering Google’s self-driving car project and the subsequent industry scramble, is where the cast expands and the narrative becomes most complex. Davies manages this with skill, but it also raises the question of whether any single book can fully contain the story. The Uber chapter, which includes the corporate espionage case involving Anthony Levandowski, is necessarily compressed here despite being a story that could sustain its own book. Davies handles it fairly, but readers who want the full depth of that particular drama will need to seek it out elsewhere.
Tristan Morris’s narration is well-matched to the material. He gives the technical passages enough weight without slowing them down, and he differentiates the large cast of engineers and executives through subtle vocal adjustments rather than distinct character voices, which is exactly right for a work of journalism. Reviewer Chris Anderson, who knows this industry from the inside, praised Davies’s technical accuracy, and Morris’s reading honors that precision.
The Honesty About Where Things Stand
What distinguishes Driven from more enthusiastic accounts of the self-driving future is Davies’s willingness to sit with the difficulty of the problem. The early promises of imminent autonomous vehicles proved premature, and Davies doesn’t paper over this. The book’s closing section, which maps the distance between the industry’s ambitions and its deliverables at the time of writing, is more nuanced than triumphalist. The technology is real. The timeline projections were not.
Reviewer Noelle S. notes that the book is mostly about people and personal dynamics rather than engineering deep-dives, and this is accurate. Davies isn’t writing a technical manual. He’s writing a history of a competitive field populated by distinctive individuals. Listeners who come in wanting to understand the specific algorithmic challenges of machine perception may find themselves wanting more technical content. But for anyone who wants to understand how this industry came to be, who the players are, and why the gap between ambition and reality opened up the way it did, this is the book.
Who Should Listen, Who Should Skip
Listen if you’re interested in the history of technological competition and want an account written by someone with genuine access to the principals. The 9-hour runtime earns its keep through the depth of the reporting.
Skip if you want a technical breakdown of autonomous vehicle engineering or a policy analysis of regulatory challenges. This is character-driven narrative journalism, not a technical assessment.
Frequently Asked Questions
How current is the book’s account of the self-driving car industry?
Davies covers the story through its origins to the point of publication, but the industry has continued to evolve significantly. The book should be treated as a history of the industry’s formative period rather than a current status report. Some of the specific predictions and timelines it mentions have not played out as anticipated.
Does the book cover the Uber/Waymo lawsuit in detail?
It covers it with appropriate context, but the case is complex enough to fill its own book. Davies gives you enough to understand why it mattered and what it revealed about the industry’s competitive dynamics, but readers who want the full legal and ethical story will need additional sources.
Is this accessible to readers with no background in automotive engineering?
Yes. Multiple reviewers with no technical background in the field found it engaging and accessible. Davies is a journalist, not an engineer, and he translates technical challenges into narrative terms without requiring prior knowledge.
How does Driven compare to Autonomy by Lawrence Burns, which covers similar ground?
The two books are natural companions. Burns writes as an industry insider with a GM and Google advisory perspective, which gives his account different depth on corporate strategy but also different biases. Davies is a journalist writing from the outside, which gives him more freedom to describe failures and internal conflicts. Reading both provides a fuller picture.
