Lenny's PodcastThe happiness and pain of product management | Noam Lovinsky (Grammarly, FB, Thumbtack, YT)
CHAPTERS
- 0:00 – 0:50
Cold open: YouTube money pit, Thumbtack turnaround, and Meta’s internal incubator
A quick montage sets the stakes: YouTube’s early profitability doubts, Thumbtack’s dramatic “smile graph” recovery, and the challenge of building a startup-within-a-startup at Facebook. It ends with a light Grammarly joke that foreshadows the lightning round.
- •YouTube leadership once reconsidered the acquisition due to losses
- •Thumbtack’s growth dipped negative and later rebounded strongly
- •Meta’s New Product Experimentation (NPE) tried to incubate new ideas internally
- •Teaser: Grammarly’s CPO misspells “the”
- 0:50 – 4:27
Who Noam is: building across YouTube, Thumbtack, Facebook, and Grammarly
Lenny introduces Noam’s unusually broad product arc: founding a startup, joining YouTube early, leading Thumbtack’s growth turnaround, and helping build Facebook’s NPE team. The framing is about learning from products at very different “stages” (0→1, -1→1, 1→100).
- •Noam’s roles across multiple iconic companies and problem types
- •Creator + consumer product leadership at YouTube
- •Thumbtack: reigniting growth after SEO-driven downturn
- •Facebook: incubating protected new-product teams
- •Episode roadmap: killing projects, prioritization, incentives, growth channels
- 4:27 – 8:52
Why he’s rarely online: authenticity, focus, and relationship-building through work
Noam explains his lack of social media presence and why it hasn’t hurt his career. He prefers deep focus, hands-on collaboration, and building relationships through helping people rather than broadcasting content.
- •Online content creation doesn’t feel authentic to him
- •Deep work focus crowds out public posting
- •He builds network and industry knowledge through collaboration and “coffees”
- •Advice: lean into what energizes you rather than external pressure to post
- 8:52 – 12:40
YouTube lesson #1: advocate for what’s best—even if it risks your role
Noam recounts joining YouTube via acquisition and quickly telling leadership his project shouldn’t have 50 engineers. That candor led not to punishment but to a bigger leadership opportunity, illustrating how healthy orgs reward prioritizing the company over ego.
- •Noam sees himself as a builder: “IC trapped in a manager’s body”
- •He recommended winding down his own initial project for broader priorities
- •Healthy cultures reward advocating for the org’s best interests
- •The creator/viewer/advertiser structure and stepping into creator leadership
- 12:40 – 16:49
YouTube lesson #2: choosing support over status (asking to be ‘layered’)
He shares an unusual career move: asking to report to another leader because it would help him do better work. The discussion highlights how understanding company strategy, trusting talent around you, and seeking strong teams can make unconventional decisions safe—and productive.
- •Struggling with CEO-level strategic questions early on
- •Requested to report to Hunter Walk for better support and effectiveness
- •Confidence comes from aligning decisions to business outcomes in a healthy culture
- •Developing a “nose” for high-functioning teams and great talent
- 16:49 – 19:38
Prioritization by business outcomes: principles to navigate user vs. business tradeoffs
Noam and Lenny dig into prioritization as a product leader: start from what’s best for the business, while acknowledging it can conflict with what’s best for users in the short term. Noam argues for explicit guiding principles—especially in marketplaces—to avoid local maxima and align decision-making.
- •Best for customer often overlaps with best for business, but not always
- •Use principles to resolve thorny tradeoffs (example: marketplace sequencing)
- •Thumbtack principle: customers first, pros second, Thumbtack last
- •Avoid “local optimization” like price moves that harm marketplace liquidity
- 19:38 – 21:48
When to kill a project: stamina, resilience, and recognizing when teams run out of steam
The conversation turns to the hardest call: when to persist vs. stop. Noam frames most failures as a stamina problem—teams lose energy before they lose money—so leaders must watch motivation, momentum, and the quality of iteration in ambiguous environments.
- •Most early efforts die from lack of stamina, not lack of ideas
- •Resilience matters: “running uphill and chewing glass”
- •Ambiguity requires faith; weak signal is normal early on
- •Team energy and inertia are key indicators of whether to persist or reset
- 21:48 – 26:25
Thumbtack downturn: SEO dependency, negative growth, and rebuilding mid-flight
Noam describes Thumbtack’s growth whiplash: triple-digit growth, then SEO hits, then negative YoY growth. The team had to “change the engine while flying,” and the experience reinforced that hypergrowth can hide fundamental product and marketplace problems.
- •SEO as a ‘live by the sword, die by the sword’ growth channel
- •From triple-digit to double-digit to negative growth after algorithm changes
- •Balancing investment in the old model while building the new one
- •Core lesson: growth masks underlying issues until it slows
- 26:25 – 38:39
Thumbtack turnaround playbook: diversify channels + reduce marketplace friction (instant quotes)
He explains what drove Thumbtack’s recovery: re-opening multiple growth channels and fixing the core customer loop. The key product shift was moving from a slow, high-friction request flow to faster, more “instant” experiences—plus rethinking monetization to keep both sides of the marketplace healthy.
- •Diversified growth: revisiting paid, referrals, and experimentation
- •Thumbtack is thousands of micro-marketplaces; targeting needed to reflect that
- •Old flow caused waiting + friction (“we’ll get back to you in 24 hours”)
- •Rebuilt the loop: instant quotes and a better monetization point
- •Leadership lesson: make product strategy a whole exec-team responsibility
- 38:39 – 46:07
Facebook NPE: why internal incubators matter (starting small, density, and customer access)
Noam reframes NPE success beyond ‘find the next Instagram.’ Its real value included enabling tiny experiments, building community-density products the “normal” org can’t, and removing constraints so teams could talk directly to customers and move faster on discovery.
- •Judging incubators only by unicorn outcomes is the wrong bar
- •Large orgs struggle to start small and build community density
- •At scale, direct customer contact can be blocked by process/legal constraints
- •NPE reduced constraints to validate ideas faster (many later became features)
- •Incubators can also be powerful recruiting/retention mechanisms
- 46:07 – 49:34
How to build a ‘startup within a startup’: incentives, time horizons, and escaping big-company process
Noam’s main advice: design the incentive system first. If you apply standard performance cycles and infrastructure mandates, you’ll kill 0→1 work; incubators need different time horizons, tools, and sometimes even a different operating model (with Nike as a reference point).
- •Incentives drive behavior—misaligned systems create ‘adverse selection’
- •Twice-a-year performance processes can smother incubation efforts
- •Let teams choose scrappy infrastructure and expect to throw code away
- •Different operating model: separate discovery from the scale-up machine (Nike example)
- •Internal incubation must compete with the upside and mindset of founding a startup
- 49:34 – 56:57
Grammarly today: profitable by design, low-friction UX, and building AI that meets users where they are
Noam explains why Grammarly has endured: it’s been profitable from day one, intentionally stayed under the radar, and delivers value with minimal effort across countless daily writing moments. He also notes the strategic shift required at scale—investing ahead, diversifying, and expanding into B2B via product-led motion.
- •Grammarly is larger (revenue-wise) than most people assume; profitable since inception
- •Strategy: thrive between giants while people dismissed the category as a ‘feature’
- •Core advantage: install-and-improve experience across apps (no workflow change)
- •“AI achievement masquerading as a little UX innovation” at massive scale
- •At scale, scrappiness can become limiting—must invest ahead and diversify (including B2B)
- 56:57 – 59:08
Resilience and purpose: Grammarly’s Ukraine team and founder motivation
Noam describes the extraordinary resilience of Grammarly’s team in Ukraine operating amid war conditions. He emphasizes pride, purpose, and how building a generational company is tied to Ukraine’s future—fueling long-term commitment and motivation.
- •Ukraine team continues delivering impact despite extreme circumstances
- •Work can provide structure and distraction during crisis
- •Pride in building one of the country’s largest global tech successes
- •Founder motivation: making Grammarly a ‘generational company’ for Ukraine
- 59:08 – 1:03:54
Career advice: seek growth that stretches you—then know when to pull back
Noam’s core career heuristic is to pick roles that maximize learning—even when it’s painful. He also shares a boundary condition: avoid roles that are too net-new; you need a few strong anchors in your skill set to stay healthy while you stretch.
- •Hard to predict ‘winning’; easier to choose roles that force growth
- •Growth and learning often feel painful before they pay off
- •Don’t choose roles that are entirely unfamiliar—keep 1–2 foundational strengths
- •Use what you’re already strong at to balance discomfort and maintain wellbeing
- •Return to the theme: do work that gives you energy; life is short
- 1:03:54 – 1:09:34
Lightning round + wrap: books, shows, interviewing, Arc, mottos, and misspelling ‘the’
A fast set of personal/product questions: Noam’s most-recommended book (with a personal twist), favorite shows, his interview style, and a shout-out to the Arc browser. They close with where to find him and how listeners can help (use Grammarly and send feedback).
- •Book recommendation: Build (Tony Fadell), co-written by Noam’s wife
- •Shows: For All Mankind and Fargo
- •Interviewing: prefers collaborative product problem-solving over pure behavioral questions
- •Favorite product: Arc (and request to improve Grammarly compatibility)
- •Life motto: “We are meant to struggle”; most misspelled word: “the”
- •Where to reach him: @NoamL; ask for feedback and conversations
