The Most Popular Product Lessons of the Year, From Positioning to Hard Conversations

Lenny opens by noting that the podcast launched about six months earlier, has reached exactly 50 episodes, and has passed 2 million downloads. He says the show is a top-10 technology podcast across Apple and Spotify globally, with roughly 40,000 to 50,000 subscribers or followers across those platforms. That growth, he says, blows his mind.

For the final episode of the year, Lenny says he will count down the ten most popular episodes so far, from tenth to number one. He explains that he will play one or two clips from each episode, chosen because they were especially interesting or popular. He admits he has never done this format before and will either repeat it or never do it again depending on how it goes.

April Dunford says the first step in positioning is to understand what you have to position against, or what you have to beat to win a deal. She calls these competitive alternatives and warns that people often hear 'competition' and think only of products that look exactly like theirs. In B2B, she says, there are two sets of competitors: the status quo, meaning whatever the company is doing now even if it is crappy, and the short list a buyer considers if they decide to buy something different. She argues that most people discount the status quo, but in B2B about 40% of deals are lost to 'no decision,' which often means losing to the spreadsheet, pen and paper, or interns.

Once the team has a stake in the ground, Dunford says, it can list capabilities that the alternatives do not have, including product features, pricing, or professional services. The next step is to translate each capability into value by asking why a customer would care, which usually produces two or three differentiated value buckets. From there, the team identifies the characteristics of target accounts that care most about that value, and only then chooses a market category. In her model, the best market category is the context that makes the differentiated value obvious to those best-fit customers.

Crystal Widjaja says she was surprised by how much attention her post 'Why most analytics efforts fail' received, because it came from frustration at repeatedly seeing teams do analytics wrong. She argues that instrumentation is one of the most solvable problems, but it requires mental model shifts. Many teams look at tracking data only to see whether an OKR is going up or down, not to identify insights. She compares that to using Twitter for news when people are actually using it for entertainment: if information does not change what you do in the real world, it is entertainment.

Widjaja says measurements do not equal insights. A measurement is an observation, such as a data point showing that power users do four times more bookings, but that fact lacks context and does not tell you how to act. An insight explains why something is happening and changes your behavior. She uses a relationship example to make the point: seeing a girlfriend with an unknown man is an observed fact, but the insight might be that he is her cousin and the real issue is the observer's paranoia.

For a product example, Widjaja says it is only a fact that a Gojek user will transact and is more likely to use a voucher. A real insight would specify that power users are more likely to use a free-shipping discount on a high-GMV basket than non-power users. That tells the team to offer the discount to power users in those circumstances and not waste it on non-power users who would not convert any better. The insight comes from instrumenting properties into events, segmenting who does what, forming hypotheses, and testing them to get a causal read.

Julie Zhuo says that for her first seven or eight years at Facebook, she felt like an imposter every single week. The constant refrain in her head was whether she really deserved to be there and whether she really knew what she was doing. Looking back, she realized that being in uncomfortable situations coincided with the fastest and most intense periods of growth. She advises people to seek environments that are scaling, where opportunities appear because someone has to do the work, and to embrace not knowing with curiosity.

Zhuo also argues that everyone feels imposter syndrome to some extent, because anything new is unlikely to feel totally comfortable the first time. She says she has become much better at asking for help instead of trying to fake it until she made it. Finding support groups and being vulnerable about what is hard can create deeper connections and let a team spread the load. Even as a department head or founder, she says, sharing a problem can help a group collectively find a better solution.

Shishir Mehrotra uses a made-up interview question about a teleportation device to test whether candidates can identify eigenquestions. The scientists who invented the device will answer only two questions, so the candidate must decide which two matter most. Strong product managers ask questions like whether it is safe enough for humans and whether it is more expensive to buy or run the devices, which then generate quadrants of possible use cases. Mehrotra also describes a P-S-H-E career framework: junior people get a problem, solution, and how to execute; more senior people get a problem and figure out the how or the solutions; the most senior people identify the problems themselves.

Kristen Berman presents the Three B's of behavior change: behavior, barriers, and benefits. The first B means choosing the specific action you want someone to take, not just logging in; for a Peloton app, she suggests defining a behavior like doing two 10-minute workouts with two different instructors within seven days of starting. The second B is reducing logistical barriers such as credit-card forms and cognitive barriers such as uncertainty aversion and status quo bias. The third B is increasing immediate benefits, because people prioritize their present self; for Asana, logging a task may be driven by completion bias or social desirability rather than long-term project outcomes.

Elena Verna argues that every company must first focus on being product-led in retention, because product-led acquisition depends on activation and habitual engagement. If users are not habitually using the product, there are fewer opportunities for them to buy, refer, or create content that attracts others. She says one-to-many or collaborative relationships make product-led growth much more feasible; products without that relationship often rely more on marketing-led and sales-led models. Her freemium framework says to make a feature free if it drives indirect monetization or virality, if it suffices for every user and is commoditized anyway, if it creates the aha moment, or if it creates habit loops; features that create friction for the growth model should be gated.

Ethan Smith says companies often under-resource SEO and over-resource ads. If a company is willing to spend $100 million on ads, he asks, why would it spend only $50,000 on SEO when the traffic opportunity may be comparable? He says SEO is more promising when the addressable market is large and the company already has authority or traction. As rough signals, he looks for at least about 1,000 non-SEO visits per day and roughly 1,000 referring domains, and he uses tools like Similarweb and Ahrefs to assess both authority and market size. He also distinguishes product competitors from audience competitors, such as Investopedia for Robinhood, because audience competitors can reveal the size of the search market.

Shreyas Doshi says his first three years as a PM at Google were perhaps the most stressful of his career, with an endless to-do list and little sense of making a dent. He discovered ideas that became the LNO framework: leverage tasks return 10x or 100x the effort, neutral tasks return roughly what you put in, and overhead tasks return much less than you put in. He argues that ambitious perfectionists often treat all three types the same, which is the core problem. Instead, people should do L tasks when they are most energetic, let their inner perfectionist shine on those tasks, and spend less time on N and O tasks.

Doshi emphasizes that the same activity can be an L, N, or O task depending on the situation. Filing a bug report might deserve a detailed report with annotated screenshots in one case, or just one screenshot and submit in another. Taking meeting notes can be an O task when the only thing people need is three action items, owners, and a quick send. But notes from a contentious product review with the CEO may be an L task that deserves an hour or two of careful wording so there is no room for misinterpretation.

Marty Cagan shares a theory from 1995: as a company gets bigger, product historically becomes less important. The people celebrated and promoted are marketing, sales, and finance leaders, because sales and marketing drive growth while finance cuts costs. Once those leaders run the company, good product people leave for companies that value product. Cagan also criticizes separate product-owner roles as administrative and says product owners usually lack the skills to be product managers.

Cagan says a product manager who has never been coached must first prepare to contribute to an empowered team in four areas. They need to know users and customers, become an expert in the data and how usage changes over time, and learn the different parts of the business including marketing, sales, monetization, and compliance, regulatory, privacy, and security issues. This business knowledge helps earn stakeholder trust, especially by promising to bring a prototype when questions arise. Finally, the PM must know the competitive landscape, industry, and trends, because empowered teams fall down when the PM is ill-equipped.

Matt Mochary says many of the companies he coaches did layoffs in March 2020 because they had to prepare for a possible economic collapse. Within 60 days, CEOs reported back that the company was operating better on an absolute scale, with more features, more code, and higher NPS. His explanation is that fewer people reduce coordination overhead: every additional hire creates more work to keep people informed, give context, and make them feel heard, which creates friction and morale problems. He points to WhatsApp, Instagram, Linear, and Notion as examples of the power of keeping teams very small.

For difficult conversations, Mochary starts by saying, 'This is going to be a difficult conversation' and asking the person to take a few seconds to prepare. He explains that surprise often triggers the amygdala, while a warning lets people see fear, anger, or sadness coming and reduces the reaction. He then delivers the news, invites the person to share what they are feeling and thinking, and actively listens. Sitting with them through the pain, rather than running away from it, helps them get through it.

After the countdown, Lenny says it was hard to make the list because all 50 episodes have something interesting to offer. He points listeners to other episodes for pricing, communication, marketplaces, and marketing, and encourages them to browse the full list for a problem they are facing. He thanks listeners and sponsors, says the plan is to keep refining the podcast with more guests and topics, and asks for feedback by email, newsletter comment, or Twitter DM. He closes by wishing listeners happy holidays and a happy new year.