Lenny's PodcastMatt LeMay: Why one CEO question saves PMs from layoffs
How asking whether you would fund your own team breaks the low-impact death spiral; rhinestone features and missed OKRs leave your paycheck at risk.
At a glance
WHAT IT’S REALLY ABOUT
One question every product manager must answer to stay indispensable
- Matt LeMay argues that most product teams underestimate how directly their work must tie to business-critical outcomes, especially in an era of frequent PM layoffs.
- He introduces the idea of asking, “If you were the CEO, would you fully fund your own team?” as a forcing function to escape the ‘low‑impact PM death spiral’ of cosmetic, low‑stakes work.
- LeMay outlines three practical steps for any individual team—regardless of company maturity or structure—to align goals, day‑to‑day decisions, and prioritization directly to company-level impact.
- He also shares tactics for pushing back on low-impact executive requests without saying a hard no, instead framing options and trade-offs grounded in business results.
IDEAS WORTH REMEMBERING
5 ideasAsk yourself if you’d fund your own team as CEO.
Regularly pose, “If I were the CEO, would I fully fund this team?” If you can’t confidently answer yes—or can’t articulate why—it’s a signal your work may not be clearly contributing to the company’s survival or growth.
Set team goals no more than one step away from company goals.
Avoid endlessly cascading OKRs and intermediate metrics; instead, define a team goal that connects to the company goal via a single ‘why’ or a simple numeric relationship (e.g., converting X users yields $Y in revenue toward a top-line target).
Keep impact visible at every stage of the product process.
From strategy decks to epics and prioritization sessions, continuously reference the core impact goal; don’t let it vanish into OKR season artifacts that nobody revisits or ties back to business outcomes.
Prioritize work by estimated contribution to your impact goal, not generic ‘impact’.
When using frameworks like RICE/ICE, quantify impact in the same unit as your team goal (e.g., additional users converted, revenue, profit) so that prioritization decisions are grounded in how much each bet can move the actual company needle.
Escape the low-impact death spiral by tackling harder, higher-impact work.
Continuously shipping ‘rhinestone’ features that are safe and cosmetic makes the product heavier, coordination harder, and truly impactful changes more difficult—so deliberately seek work that affects the commercial engine, even if it’s riskier and more cross-functional.
WORDS WORTH SAVING
5 quotesIf you were the CEO of this company, would you fully fund your own team?
— Matt LeMay
Low impact work begets low impact work. The more low impact work you do, the harder it is to do high impact work.
— Matt LeMay
You can follow all the best practices, but if your company goes out of business, they’re not going to keep writing your paycheck because all of your OKRs were at 0.6 or 0.7.
— Matt LeMay
What I’m actually saying is that the things you think you’re fighting against are usually the things that are giving your work shape if you let them be.
— Matt LeMay
If you’re doing product management really well, you never have to say yes and you never have to say no. You’re giving people options and helping them understand the trade-offs.
— Matt LeMay
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome