CHAPTER 17
Appreciation
Read It
The acknowledgments page is usually the part everyone skips. But here it's doing real work: it's the book's final proof of its own thesis. Naval has spent hundreds of pages arguing that no significant creation happens through isolated willpower—that leverage, relationships, and specific knowledge from others are what make things possible. The acknowledgment chapter is that argument performed, not just stated. The author thanks people by role, not just by name: the ones who trusted him, the ones who edited, the ones who illustrated, the ones who interviewed. The original interviewers are credited as the true source material, which is a striking admission for a compiler: the ideas weren't his to begin with. He also names the books that inspired this book's format, placing it inside a lineage rather than presenting it as original. Even anonymous online encouragement gets a mention. The structure is not a list of names; it's a map of dependencies.
Open full image ↗Draw It
A written acknowledgment flattens everyone into a single line of gratitude. But the real structure is layered. The first layer is the source: the people who trusted the project and the interviewers who drew out the ideas. Without that, there's nothing to compile. The second layer is the craft: editors, illustrators, early readers who turned raw material into a book. The third layer is the environment: family and partner who kept the whole thing from collapsing. Each layer is a different kind of support, and each is necessary. Mapping them separately makes the point that collaboration isn't just many people helping; it's different kinds of help operating at different levels. If you collapse the layers, you lose the insight that a project can fail at any one of them.
Rethink It
In technical teams, we thank the people who wrote the code. We rarely thank the people who made the code possible—the designer who clarified the spec, the tester who caught the edge case, the manager who deflected the urgent-but-wrong request. A project ships because of all of them, but the retrospective often lists only the engineers. Naval's chapter is a reminder that public acknowledgment is not politeness. It's how you make the support network visible, so that next time, people know their contribution mattered. The cost of skipping this is quiet but real: people stop offering the invisible kinds of help.
Take It With You
How far you can go depends on how many people you're willing to acknowledge, and whether you can put each one's help in the right layer. Gratitude without structure is just noise.