What we made

Lenny's archive is enormous, and reading it end to end is not a realistic thing for anyone to do. The individual episodes and essays are extraordinary — candid, specific, often at odds with the conventional wisdom in their own quiet way — but there is so much of it that the connections between them are invisible on a first read. Someone working on pricing would need to find every time Madhavan Ramanujam, Patrick Campbell, Elena Verna, and Bob Moesta had talked about it, hold all four conversations in mind at once, and then work out how the advice from each one applied to their own situation. That is not something even a careful reader can really do.

The Rachitsky Atlas takes a different approach. We read everything Lenny has published, find the questions his guests keep coming back to, and pull together the positions each of them takes on those questions — not as a compilation, but as a map. For every topic, we show where each leader lands, what brought them there, what kind of situation their advice was built for, and how their view sits next to the other views on the same question.

The map, not the territory

The point of a map is not to tell you where to go. It is to show you the terrain so that you can pick a route once you know where you are.

That distinction matters here, because the product leaders in Lenny's archive are not all giving the same advice — and they should not be, because they did not all start from the same place. Jason Fried has run a small, profitable, deliberately bounded company for two decades. Elena Verna has spent her career running growth at hyperscalers. They will sometimes offer opposite advice on the same question, and both of them will be right, because they are describing the route they took through their own terrain, not a universal law of product management. A founder at a ten-person company and a PM at Meta are both trying to get somewhere, but they are starting from different places, and the route that works for one of them does not necessarily work for the other.

The Atlas is built around that idea. Every deep dive treats a question as a destination, and the positions leaders take as different routes toward it. You can see who took which route, what their conditions were, and what they learned along the way. The work you have to do is the work a map always asks of you: figure out where you are, decide where you want to go, and pick the route whose terrain looks most like yours.

How it is built

The Atlas goes through the archive in four passes.

Topic discovery. Every podcast transcript and newsletter essay is read for the questions guests keep coming back to. Not surface-level categories like "growth" or "hiring," but the specific questions underneath them — when to trust your instinct over your data, when to hire a specialist instead of a generalist, when to raise prices and when to leave them alone. A topic only becomes a deep dive if enough guests have something real to say about it.

Evidence collection. Once a topic is on the list, we pull every quote, example, and piece of reasoning that belongs to it. Each claim is anchored to a specific episode or essay, with the timestamp and the link, so nothing in the Atlas floats without a source you can check yourself.

Position synthesis. We group the evidence into distinct positions. Most questions have somewhere between two and five — not because we force a count, but because that is how the views usually sort themselves out. Each position names its advocates and the reasoning they actually used, not a paraphrase of it.

Tension review. Finally, we score how sharply the positions diverge from each other. This is the one place the word "tension" shows up in the Atlas as a number, and it is worth explaining what it means, because it is not quite what it sounds like.

On tension

Tension is not disagreement in the way people usually mean the word. The leaders in Lenny's archive are not arguing with each other. They are mostly not even in the same conversation. What they are doing is giving advice from very different vantage points, and on some questions those vantage points produce advice that lines up cleanly, and on other questions they do not.

A low-tension topic is one where the different positions are basically variations on the same idea. The advocates would all nod along to each other. A high-tension topic is one where the positions actually pull in different directions — where following what one of them recommends would mean not following what another one recommends. Tension is not a measure of conflict; it is a measure of how much the map forks at that point.

Those are the places in the archive where the thinking is most worth slowing down for, because they are the places where you cannot follow everyone's advice at once. You have to read the positions, think about which starting conditions each one is answering to, and work out which of them is describing the situation you are actually in. High-tension topics are where the map stops being a single route and starts being a real decision.

What the Atlas is not

It is not a search engine. The transcripts are already out there, and the Atlas does not try to replace them. It is a reading on top of them.

It is not a summary. We do not condense episodes. We organize the ideas inside them into positions, and every position links back to the specific moment in the source it came from.

It is not a ranking. We do not say who is right. Different leaders are right about different situations, and the value of the Atlas is holding all of their views in one place so you can choose between them rather than inheriting whichever one you read last.

It is not a replacement for Lenny's work. Everything on this site is derivative of the archive he has built. The synthesis is ours; the thinking, the examples, and the hard-won experience all belong to the guests.

The sources

The Atlas currently draws from 291 podcast conversations and 349 newsletter essays. 138 guests contribute positions across 58 deep dives, anchored by 533 linked quotes and 280 evidence cards. Every figure on this page is generated from the archive itself, so the numbers move as new episodes and essays come in.