01 · Zero to One
Zero to One — Peter Thiel & Blake Masters
The book that made me think differently about building.
This book changed how I think about value creation. The central idea is simple but powerful: building something genuinely new is different from incrementally improving something that already exists. It pushed me toward looking for unoccupied spaces rather than crowded markets.
“What important truth do very few people agree with you on?” became one of the strongest questions I carry into product thinking.
I now approach products by asking what assumptions are baked into the current system—and whether those assumptions are wrong. That instinct shows up in how I think about contact tooling, marketplaces, and information products.
02 · Unlocking the Customer Value Chain
Unlocking the Customer Value Chain — Thales Teixeira
The book that taught me to look at businesses as chains of actions.
Teixeira's framework helped me change the way I analyze markets. Instead of asking how to beat a company, I started asking which part of the customer's journey is under-served and can be owned better.
Discover, compare, research, purchase, use, maintain, and sell are not just stages—they are opportunities. A company doesn't need to dominate an entire category to create real value. Sometimes the best opportunity is a single activity in the chain that incumbents ignore.
This is one reason I think more clearly about product strategy: not just “what is the market,” but “which part of the experience can be made radically better?”
03 · Think and Grow Rich
Think and Grow Rich — Napoleon Hill
The book that made me take psychology, persistence, and self-direction seriously.
I don't take every claim literally, but the book changed how I think about ambition and execution. It pushed me to see success as the result not only of technical ability, but also of mental discipline, decisive action, and the environment around you.
The idea of a mastermind, the importance of definite purpose, and the relationship between self-direction and execution all stuck with me. I increasingly think of building as a practice of connecting disciplines and surrounding yourself with the right kind of people rather than trying to know everything alone.
04 · The Black Swan
The Black Swan — Nassim Nicholas Taleb
The book that made me suspicious of confident predictions.
Complex systems are rarely predictable in the way people want them to be. More information can still leave you unprepared for events outside your model. That lesson changed how I think about markets, product bets, and entrepreneurship.
I became much more interested in the gap between what can be predicted and what can be prepared for. This has made me more careful with certainty, and more focused on learning systems that can adapt when reality diverges from expectation.
05 · Outliers
Outliers — Malcolm Gladwell
The book that complicated my definition of success.
Outliers reframed success as something shaped by opportunity, timing, environment, accumulated practice, culture, and luck—not just talent or effort. It taught me to look beyond the person and ask what conditions made the outcome possible.
That has had a practical effect on how I interpret founders, engineers, and high performers. I care more about context, support systems, and the opportunity landscape than I did before.
06 · Range
Range — David Epstein
The book that gave me a framework for being a generalist.
I have never been interested in staying inside a single discipline. Software, product design, finance, AI, hardware, business, and policy all influence each other in my thinking. Range gave me a way to understand that not as a lack of focus, but as a strength.
The value of interdisciplinary work is that ideas travel. A mental model from one domain can become useful in another if you know how to connect them. That has become one of the ways I define my own learning process.
07 · Digital Fortress
Digital Fortress — Dan Brown
The fiction book that made technology feel like a battlefield of ideas.
This book fed a deeper fascination with the hidden layers of technology: cryptography, information systems, institutional power, and the invisible structures behind user interfaces. It reinforced a belief that the most important parts of technology are often what users never see.
Once information becomes powerful, questions of trust, privacy, and control become unavoidable. That lens has shaped how I think about systems and the responsibility that comes with building them.
What these books have done to my thinking
The common thread
Taken together, these books point to a few recurring principles: I look for assumptions before solutions, I break complex systems into smaller parts, I distrust certainty in uncertain environments, I care about the conditions behind success, and I value the ability to connect different disciplines.
If I had to reduce all of it to one sentence, it would be this: when I see a normal system, I increasingly ask whether it actually has to work that way.
That question has shaped my thinking more than any one framework.