
Noah Weiss: How to Master Product-Led Growth; Scaling PLG to Enterprise at Google & Slack | E1026
Noah Weiss (guest), Harry Stebbings (host)
In this episode of The Twenty Minute VC, featuring Noah Weiss and Harry Stebbings, Noah Weiss: How to Master Product-Led Growth; Scaling PLG to Enterprise at Google & Slack | E1026 explores noah Weiss on renewing product-market fit and scaling product-led growth Noah Weiss, CPO at Slack, reflects on product lessons from Google, Foursquare, and Slack, focusing on portfolio thinking, speed, and continuously renewing product‑market fit as markets and users evolve.
Noah Weiss on renewing product-market fit and scaling product-led growth
Noah Weiss, CPO at Slack, reflects on product lessons from Google, Foursquare, and Slack, focusing on portfolio thinking, speed, and continuously renewing product‑market fit as markets and users evolve.
He explains how Slack scaled from a 5–50 person team tool into an enterprise platform by listening deeply to new customer types, building product principles, and balancing end‑user delight with enterprise buyer requirements.
Weiss breaks down what truly drives product‑led growth: consumer‑grade UX at work, smart freemium and trials, and prioritizing the daily end user even in large enterprises.
He also covers operating mechanics—product reviews, hybrid collaboration, PLG mistakes, when to move upmarket, buy‑vs‑build, PM career advice, and the art/science balance in modern product management.
Key Takeaways
Continuously renew product‑market fit as audiences and context change.
Weiss argues PMF is not a permanent state; Foursquare’s early success faded as user types evolved and competitors like Instagram shifted behavior. ...
Get the full analysis with uListen AI
Use portfolio thinking (e.g., 70/20/10) but don’t worship fixed ratios.
From Google he adopted the idea of intentionally allocating most effort to core improvements, some to scaling new bets, and a slice to far‑out ideas—while stressing that each team and company stage justifies its own mix.
Get the full analysis with uListen AI
Codify product principles early to scale founder taste and speed decisions.
Slack introduced simple, memorable principles like “be a great host” and “don’t make me think” once Stewart couldn’t be in every room, giving teams a shared language to judge quality and make faster, decentralized calls.
Get the full analysis with uListen AI
Distinguish two‑way vs one‑way door decisions to maintain speed.
Most feature decisions are reversible and should be made quickly by teams; truly hard‑to‑reverse calls (e. ...
Get the full analysis with uListen AI
In PLG, pair generous freemium with a compelling, guided paid trial.
Slack long relied on freemium alone, then realized many users didn’t even know a ‘full’ Slack existed. ...
Get the full analysis with uListen AI
Prioritize the daily end user, even when selling to enterprises.
Over 85% of Slack’s enterprise customers began in self‑serve pockets. ...
Get the full analysis with uListen AI
Speed and quality (especially performance) are non‑negotiable product foundations.
He calls speed “the most important feature” of any product; Slack’s failed ‘Post’ editor showed that even a seemingly obvious feature won’t stick if it feels slow or clunky compared to existing alternatives.
Get the full analysis with uListen AI
Notable Quotes
“The most important feature by far for any product is actually speed.”
— Noah Weiss
“Product‑market fit isn’t something you unlock and then have forever; you have to keep renewing it as your audience and the world change.”
— Noah Weiss
“Why does someone at work deserve a software experience that feels so much more painful than what they use on nights and weekends?”
— Noah Weiss
“If we have to choose who we’re serving above all else, it’s the end user who’s living in Slack for ten hours a week.”
— Noah Weiss
“Deliver impact. Everything else is an input.”
— Noah Weiss
Questions Answered in This Episode
How can a startup practically tell when its initial product‑market fit is starting to decay, and what leading indicators should a PM watch?
Noah Weiss, CPO at Slack, reflects on product lessons from Google, Foursquare, and Slack, focusing on portfolio thinking, speed, and continuously renewing product‑market fit as markets and users evolve.
Get the full analysis with uListen AI
When expanding from SMB to enterprise, how do you avoid over‑rotating on buyer requirements and losing the product’s original end‑user magic?
He explains how Slack scaled from a 5–50 person team tool into an enterprise platform by listening deeply to new customer types, building product principles, and balancing end‑user delight with enterprise buyer requirements.
Get the full analysis with uListen AI
What’s the right moment for a PLG company to introduce a paid trial, and how do you design one that feels helpful instead of salesy?
Weiss breaks down what truly drives product‑led growth: consumer‑grade UX at work, smart freemium and trials, and prioritizing the daily end user even in large enterprises.
Get the full analysis with uListen AI
How would you design an internal product‑principles process for a 10–20 person startup so it scales without becoming vague slogans?
He also covers operating mechanics—product reviews, hybrid collaboration, PLG mistakes, when to move upmarket, buy‑vs‑build, PM career advice, and the art/science balance in modern product management.
Get the full analysis with uListen AI
In the age of generative AI, how should product teams calibrate what they promise in the UI with what the underlying models can reliably deliver?
Get the full analysis with uListen AI
Transcript Preview
The most important feature by far for any product is actually speed. (instrumental music)
Noah, I am so excited for this. I've really been looking forward to this one. So thank you so much for joining me today.
Thanks so much for having me here. I've been a long time listener, excited to finally join.
Well, that is very, very kind of you. Now I wanted to kind of chronologically unpick your career before we dive in, and start as your career starting as PM at Google. What is the single biggest product lesson you took from the three to four years or two to three years at Google, and how did that impact your mindset?
Yeah, I mean, Google is definitely where kind of I started my career in product and it was the formative part of my kind of journey there. And I think the thing that struck me the most, because back then I worked on a feature team within search, but you kind of saw how the executives viewed product strategy. In that room they used to have this model, they called it the 70/20/10 model. And it's actually a pretty fascinating way of thinking about just a product roadmap and the distribution within it. So 70% of the product teams were focused on what are things that are known valuable things for our customers that are in some ways more incremental. 20% were new product areas that had already kind of taken off, but they were trying to further refine and incubate. So, you know, after Gmail took off, how do you scale it to a billion users? And then 10% were the far out bets, the self-driving cars, the, you know, Android before Android existed, the building a web browser. And I think the thing that stuck out to me was the combination of deliberate approach to what the portfolio looked like and the constant kind of Larry and Suriya refrain of whatever your ideas you bring to them, what would 10X a bigger scale look like? So I, I think that caused a level of ambition for product thinking at Google that it's kind of hard to afford at min- early stage startups, but I think is aspirational to bring to every company.
Can I ask, do you do the 70/20/10 at Slack?
You know, it's funny. I feel like it almost became so well known for Google that it would feel a little bit cargo culting to bring it exactly, but we do talk a lot about kind of the portfolio and diversification within different product areas. So, you know, we might ask of team, "When you think about the breakdown of your roadmap for the next two quarters, where, where is it allocated? How much of this is maintenance, performance and quality? How much of this is refining and kind of customer delight? And how much of this is you're incubating new ideas, you're trying out new levers?" So we don't call it 70/20/10, but it's definitely part of how we look at the structure of products and roadmaps and try... And every team is different too. You know, even at Google, I would say that was at the corporate level. But take a team like AdWords, their allocation didn't look like 70/20/10. They might look like 95/5. So I, I think it, it's a interesting framework, but I don't think it is something that is like a perfect ratio to apply in every context.
Install uListen to search the full transcript and get AI-powered insights
Get Full TranscriptGet more from every podcast
AI summaries, searchable transcripts, and fact-checking. Free forever.
Add to Chrome