Matt LeMay on Impact-First Product Teams

Speaker: Matt LeMay Source: Lenny’s Podcast

Key ideas

• The Low Impact PM Death Spiral. Teams default to low-impact work — cosmetic features, minor enhancements — because it feels safer than touching the commercial engine. This begets more low-impact work: the product grows cluttered, cross-team dependencies multiply, and high-impact work becomes structurally harder. The cycle continues until layoffs force a reset.
• Set team goals no more than one step from company goals. Most teams sweat the middle — OKRs, initiatives, bets — and lose the thread back to top-line impact. The antidote is a single team goal expressible in one Y-statement or one mathematical operator linked directly to a company-level metric (revenue, user growth, profitability).
• The CEO funding test. Ask: if you were CEO of this company, would you fully fund your own team? Most people cannot answer confidently on the spot. That uncertainty is the signal. A team unable to articulate its own investment case is at structural risk.
• PM as facilitator of CEO-level thinking, not sole owner. The PM’s job is not to be the mini-CEO alone, but to ensure the whole team thinks commercially. Engineers and designers often surface the clearest path to business impact once the goal is framed correctly.
• Constraints as guideposts, not blockers. Regulated industries, B2B models, and quarterly earnings targets are commonly cited as reasons product “can’t be done right.” LeMay inverts this: these constraints give product work its commercial shape and are often a competitive advantage if embraced rather than fought.

References

• Radical Focus by Christina Wodtke — OKR mental model
• The Wisdom of Insecurity — Alan Watts
• Escaping the Build Trap — Melissa Perri — product management as facilitating a value exchange between business and customers