The one question that saves product careers | Matt LeMay

Matt LeMay frames the current product-career risk in blunt commercial terms: product managers and teams are increasingly being laid off, and executives have described eliminating teams that do “work around the work” instead of pursuing opportunities with real impact. The episode’s central question is simple: if you were the CEO, would you fully fund your own team? LeMay says many teams cannot answer immediately, which is itself a warning that they may not understand why the business should keep investing in them.

The proposed remedy is not a new layer of process. LeMay identifies three moves: set team goals no more than one step from company goals, keep the impact goal visible throughout the product-building process, and connect every piece of work back to that impact. The point is to make the team’s contribution legible to the wider business rather than assuming that following product rituals will protect it.

The argument also has a career dimension. Lenny Rachitsky’s introduction presents LeMay as a long-time product leader and author of Product Management in Practice and Impact First Product Teams, while describing the conversation as a discussion of business-critical outcomes, low-impact work, and how teams can respond when executives ask them to build questionable ideas. The episode includes sponsor and subscription material, but its editorial thesis is that product work should be tied to outcomes the business can recognize.

LeMay’s background in music provides the episode’s human counterpoint to its commercial argument. He spent 13 years reviewing music for Pitchfork and has also toured as a musician. He says the common thread between music and product development is the way people with different perspectives work together to create something greater than the sum of its parts. In an AI-heavy environment, he expects those messy interactions to become more valuable because technology can make it easier to avoid the moments when other people expose the limits of one’s own perspective.

Rachitsky introduces LeMay’s newer book by emphasizing two constraints: an individual team must align its work with business-critical outcomes, and it must be able to do so even when other functions or the wider organization use a different product-development approach. LeMay’s answer is that business-critical outcomes are the measures against which a team is ultimately evaluated. If the CEO and CFO can understand a team’s contribution and see it as a good investment, continued investment is more defensible; if the team cannot explain its value, merely showing up and shipping is not enough.