← All Guests
ML

Matt LeMay

The one question that saves product careers, covering team leadership, product design, and product strategy and execution.

August 14, 2025·17,480 words
AI & Machine LearningGrowth & MetricsLeadership & ManagementProduct StrategyStartup BuildingDesign & UXEngineeringSales & GTMCareer & Personal GrowthUser PsychologyData & Analytics

Episode

The one question that saves product careers | Matt LeMay

Summary

Matt LeMay lays out a three-step framework for escaping the "low-impact PM death spiral" — where product teams do work that feels productive but doesn't connect to company-level outcomes. The framework: set team goals no more than one step from company goals, keep impact first at every execution step, and connect every prioritization decision to the same unit of measure as your goals.

Key Takeaways

1

Ask "if you were the CEO, would you fully fund your own team?" — if you can't answer yes, your goals are probably not close enough to outcomes the company cares about.

2

Set team goals no more than one mathematical operator away from company goals — if there are multiple steps of logic between your goal and the company goal, you've cascaded into irrelevance.

3

Keep impact-first at every step, not just goal-setting: the failure mode is setting good goals and then letting roadmap items accumulate without re-checking whether they move the number.

4

Estimate impact in the same unit as your goal: replace abstract "impact scores" in RICE with actual numbers like "this reaches 400 users" vs "this converts 50,000."

5

When stakeholders push you to build something, present options with trade-offs and a recommendation rather than saying yes or no — this keeps impact-first discipline visible.

Notable Quotes

You can follow all the best practices, but if your company goes out of business, they're not going to keep writing your paycheck for two years because all of your OKRs were a 0. 6 or a 0.7.

General
00:00:52

It's important because at the end of the day, it is those business critical outcomes against which you and your team will be evaluated. That's the reality of working for a business, right?

AI & Machine LearningData & Analytics
00:07:51

And that really struck a nerve because I've been on those supporting teams before. I've done the work around the work. And I've assumed that if I was given work around the work to do, that surely it must be critical to the business, otherwise they wouldn't have hired me to do it.

General
00:09:25