Loading...
A curated reading list of the books that have shaped real positioning, niche, product, and operational work. Twenty titles across positioning, niche strategy, product thinking, communication, systems, and fintech, each with a short note on when to use it.
A curated reading list on positioning, niche strategy, product thinking, and business clarity. These are books I have actually used in real positioning and product work, not a "30 books every founder must read" listicle.
Read in this order if you are new to the topic. Skip around if you are not.
The most practical positioning book of the last decade. If you read one book on this list, read this. Dunford's "Sales Pitch" framework forces you to define the alternative customers are comparing you to, then build the pitch from that contrast. Most positioning theory is academic. This is operational.
The original. Written in the 1980s and still the most quoted book in the field. The framing of positioning as a battle for limited mental real estate is the foundation everything else builds on. The examples are dated. The principles are not.
A shorter, sharper follow-up. Twenty-two short chapters, each one a hard rule about how categories form, why being first matters more than being better, and what happens when you try to be everything. Worth re-reading every six months.
The middle market is dead. This book argues that being marginally better is not a strategy, and "value" without a sharp point of view is just discount competition. Useful corrective for anyone tempted to be "the affordable option".
The shortest book on this list and the most aesthetically pleasing. Neumeier introduces the "good is the enemy of different" idea in a way that sticks. Easy to read in a single sitting. Good gateway book for non-strategists.
Required reading if you are selling into enterprise or B2B. Moore's "bowling alley" concept - winning one tight beachhead segment, then expanding to adjacent ones - is the original case for niching down deliberately rather than going broad. The book is dense but worth the work.
The sequel. Less famous but more useful once you have a niche working. Covers what happens after the beachhead: how to scale, when to broaden, and how to avoid the classic mistake of broadening too early.
Argues that the winning strategy is to create a new category, not to compete in an existing one. Contrarian to the Ries and Trout view in healthy ways. Useful for founders building something genuinely novel - though most of us are not.
The standard text on modern product management. Cagan separates "delivery" from "discovery" and makes the case that great products come from understanding the buyer's actual problem deeply, not from executing a roadmap faithfully. Read this if you have ever heard yourself say "we just need to ship more features."
The shortest, sharpest book on customer discovery. Most founders ask leading questions ("would you use this?") and accept polite answers. Fitzpatrick's rules - talk about their life, not your idea; ask about past behaviour, not future intentions - are the antidote. Should be required reading before anyone runs their first user interview.
The operating manual for embedding discovery into a product team's weekly rhythm. Torres connects "opportunity solution trees" to actual interview cadences and assumption testing. Pragmatic and execution-focused.
Why some ideas spread and others die in a deck. The SUCCES framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories) is now common vocabulary but the book is still where it lives best. Use it to pressure-test your positioning, pitch, and homepage hero.
A formula for clarifying a brand by casting the customer as the hero and the company as the guide. Some find it formulaic. That is the point - it forces clarity in places where founders default to clever language and obscure themselves out of revenue.
Specifically about high-stakes pitches but useful broadly. Klaff's frame-control ideas explain why some pitches land and others die regardless of the underlying business. The audio version is better than the book.
A 1990s book about why most small businesses fail. The core idea - that a founder who is also a technician will build a job instead of a business - is the most underrated piece of advice on this list. Read it before you have ten employees, not after.
The EOS (Entrepreneurial Operating System) framework. Some of it is dated, some is religion. The "rocks", "scorecards", and "level 10 meetings" sections are still worth lifting for any team trying to install operating discipline without becoming a Notion graveyard.
How Amazon writes one-page memos and six-pagers instead of slides, and why. The "PR/FAQ" format - drafting the press release before building the product - is the cleanest version of writing as a thinking tool you will find. Worth it for that chapter alone.
The reference text for understanding card networks, ACH, interchange, and the payments stack. Dry but accurate. If you work in fintech or payments orchestration, you cannot get away with vibes.
A more readable companion. Walks through what actually happens between dipping a card and the funds settling. Useful for product managers entering fintech without a banking background.
Twenty books is too many to read at once. The trick is to read each one with a current decision in mind. Books read for general inspiration leave nothing behind. Books read against a specific positioning or product problem change how you work.
If you find a book missing here that changed how you build, let me know via the contact page. This list is updated when something earns its way in.