I recently asked Claude for book recommendations tailored to where I am in my career right now. Build by Tony Fadell came up. I started reading it and was really glad I did.
It was written to help founders and executives build companies. The makers inside those companies get just as much from it.
What it actually does is give you precise language for things you’ve already experienced but never had words for. Problems you felt but couldn’t name. Org dynamics you survived but couldn’t diagnose.
A few things that stuck:
On breakpoints. When a company grows, the way it’s organized eventually stops working. Not because people are failing, but because the structure doesn’t fit anymore. The failure is when leadership knows this but tries to preserve the startup feel anyway, hoping the friction resolves itself. It doesn’t. Fadell calls these inflection moments “breakpoints” and describes them as predictable and manageable if you see them coming, and a slow disaster if you don’t.
On leader capacity. There’s a section about how many projects a team leader can actually hold in their head. Smaller than you’d think. Beyond that threshold, projects don’t get dropped because anyone’s failing. The math just doesn’t work. The fix is product-specific teams, not asking people to try harder. He uses Nest creating a dedicated accessories team as the example: the mainline team would always say they’d get to it. They never did.
On mistaking process for growth. Early in the book he draws a line between real skill development and getting better at navigating a specific company’s internal landscape. Both feel like progress. Only one of them is. That framing has been useful.
On finding your heroes. Fadell is deliberate about this in a way most career advice isn’t. He describes going to work at places specifically because of who was there, and gives a simple filter for evaluating a company: 30 to 100 people, building something real, with a few people you’d genuinely want to learn from. “Any job working with your heroes is a good job.” Hadn’t heard it stated that directly before.
What surprised me most was what the book did on the back end. I’m thirteen years into hardware engineering: consumer electronics, defense systems, networking hardware. I’ve shipped real things. But there’s a version of this career I haven’t reached yet, and reading this made that path feel concrete rather than aspirational.
Fadell is specific about the ingredients: the right company size, how to find the engineers you want to become, treating each role as a stage in something longer. Useful framework. And there’s something in that reminder that a long career is still mostly ahead, that the interesting choices are still coming, that kind of lit something back up.
If you’re an IC in consumer hardware, read it. The org design chapters alone are worth the time.