By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

The Twenty Minute VC

Noah Weiss: How to Master Product-Led Growth; Scaling PLG to Enterprise at Google & Slack | E1026

Noah Weiss is the Chief Product Officer of Slack, overseeing the product team’s strategy and development.

Noah WeissguestHarry Stebbingshost

Jun 16, 20231h 2mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

CHAPTERS

Jump to publisher timestamps

Chapter summaries

Google’s 70/20/10 roadmap model and the discipline of 10x thinking
Noah reflects on his formative years as a PM at Google, highlighting how leadership thought about product strategy at portfolio level. He explains the 70/20/10 roadmap allocation and how pushing for “10x” ambition shaped his product mindset beyond incremental improvements.
- •70/20/10: core incremental value vs scaling new winners vs far-out bets
- •Portfolio thinking as an explicit executive practice, not an ad-hoc roadmap
- •The cultural forcing function of asking “what would 10x look like?”
- •Why the ratio isn’t universal (different businesses need different allocations)
Foursquare lessons: renewing product–market fit as the world and users change
At Foursquare, Noah learned the most during headwinds rather than during tailwinds. He argues PMF isn’t a one-time unlock; it must be renewed as audiences broaden beyond early adopters and as the competitive landscape shifts.
- •You learn more when growth stalls than when metrics rise effortlessly
- •PMF is not binary; it erodes unless actively renewed
- •Early-adopter novelty doesn’t translate automatically to mainstream users
- •Competition and changing behavior (e.g., Instagram) can redefine the market backdrop
Designing for the ‘next customer’: humility, discovery, and enterprise reality
Noah explains the hardest transition after initial PMF: realizing you’re no longer building for yourself. Using Slack’s evolution from “teams of 5–50” to large enterprises, he emphasizes immersive research into new user segments and buyer needs.
- •Founders often first build for themselves; scaling requires designing for people unlike you
- •Slack’s early intent was small teams; data showed adoption inside big companies
- •Enterprise end users may want the same product, while org buyers require different controls
- •Deep customer immersion: security, compliance, admin, and executive stakeholder discovery
Product principles as culture-at-scale: making craft and decisions portable
Noah defines product principles as shared language that encodes product culture and accelerates decision-making across a scaling organization. He shares why Slack formalized principles as teams grew farther from the founder’s direct influence.
- •Principles help teams make fast qualitative calls without constant founder oversight
- •Slack examples: ‘Don’t make me think’ and ‘Be a great host’
- •Principles gain meaning through local context, not because they’re contrarian slogans
- •Common startup mistake: waiting too long to codify scalable product culture
Speed vs debate: two-way doors, one-way doors, and decision-making hygiene
Harry challenges the idea that more debate improves outcomes; Noah largely agrees with prioritizing speed. He frames the tradeoff using reversible vs irreversible decisions and argues most product decisions should be made locally and quickly.
- •Two-way door decisions: ship/rollback; optimize for speed and empowerment
- •One-way door decisions: pricing, brand, multi-year bets; merit heavier discussion
- •Separating decision types reduces needless process drag
- •Talk is cheaper than a bad irreversible decision—but shouldn’t dominate product work
How Slack runs product reviews: pillar cadence, exec focus, and quality bar checks
Noah describes Slack’s evolved review structure for a large product org: weekly pillar-level workshops plus biweekly/monthly exec reviews. The focus is shifting away from feature-by-feature walkthroughs and toward key irreversible decisions and quality readiness.
- •Weekly reviews inside product pillars to unblock and refine execution
- •Exec reviews focus on one-way door decisions, portfolio alignment, and major launches
- •Avoid ‘15 features’ status theater; prioritize craft (‘taste the soup’)
- •Cadence designed for a ~1,200-person product/design/engineering org
Hybrid work’s unexpected upside: inclusivity and async-first product reviews
Noah argues hybrid changed reviews in a positive way by broadening participation and reducing performative meeting dynamics. He explains how more of the “presentation” moved asynchronous via docs and recorded demos, reserving meetings for real discussion.
- •Hybrid enables larger attendance without turning meetings into performances
- •Async pre-reads and short recorded demos reduce synchronous overhead
- •Designers/engineers share Figma/code walkthrough clips for pre-review
- •Net effect: more context-sharing, less presentation time, more focused debate
Process pain point: the missing ‘bird’s-eye view’ and why spreadsheets still win
Asked what’s still broken, Noah points to the difficulty of seeing an authoritative, current snapshot of priorities and status across the org. Despite using Slack to build Slack, they still rely on spreadsheet-driven operating cadence for quarterly priorities.
- •Hard to know ‘latest state of the world’ across many channels and initiatives
- •Channels are noisy; context and actionability aren’t always obvious
- •Manual PD Monday spreadsheet review creates operational clarity
- •Most SaaS still struggles to replace flexible spreadsheets for status synthesis
Building product-led growth the Slack way: consumer-grade enterprise software
Noah notes Slack didn’t follow a PLG playbook; the term came later. He frames Slack’s PLG foundation as delivering a consumer-grade experience for people at work and rejecting the assumption that work software must be painful.
- •PLG emerged as a label after Slack’s practices were already working
- •Consumer-grade UX for work drives organic sharing and adoption
- •The bar: delight, speed, and reducing friction compared to typical enterprise tools
- •Reframing: people at work deserve great software experiences too
Simplicity at scale: mission clarity, hiring, and ‘simple’ vs ‘few clicks’
Noah explains how Slack preserves simplicity by anchoring on its mission and product principles, and by hiring people not steeped in legacy enterprise patterns. He reframes “simple” as comprehensible rather than minimal clicks—especially important in enterprise flows.
- •Mission as a recurring test: ‘simpler, more pleasant, more productive’
- •Hiring for taste and craft; many Slack product people weren’t from enterprise software
- •Simple = understandable and confidence-building, not necessarily fewer steps
- •Guided multi-step flows can outperform ‘one-screen’ complexity in enterprise contexts
PLG mistakes and speed lessons: trials, Slack Connect timing, and avoiding over-caution
Noah shares two key mistakes: delaying strong in-product paid trials and moving too slowly to launch Slack Connect broadly. He ties both to a broader lesson about actively showcasing value and being careful not to let caution or complexity fears suppress speed.
- •Freemium was generous, but users didn’t experience paid value early enough
- •Robust in-product trials increased self-serve paid conversion by showcasing ‘full Slack’
- •Slack Connect was held in beta ~2 years due to mental-model and complexity concerns
- •Delaying big bets can reduce the ‘gravitational pull’ advantage in competitive windows
Is Slack innovation slower? Enterprise rotations, COVID wake-up call, and renewed urgency
Noah acknowledges innovation slowed most notably from 2018–2020 due to an enterprise-focused rotation. He argues the pandemic clarified new customer needs and re-energized Slack’s roadmap, accelerating innovation with new collaboration modalities.
- •Enterprise compliance/security work can temporarily crowd out visible innovation
- •Diminishing returns after clearing key enterprise blockers (acronym requirements)
- •COVID increased reliance on Slack and expanded expectations overnight
- •Innovation rebound: Huddles, Clips, Canvas, Workflow and hybrid-first capabilities
Scaling SMB to enterprise without losing your DNA: timing signals and who to serve
Noah warns startups not to over-rotate toward enterprise buyers and become culturally conservative. He explains when to move into enterprise (top-down categories vs bottoms-up pockets) and argues Slack prioritizes the end user while balancing admin/buyer constraints.
- •Hire enterprise domain experts to remove blockers; don’t reinvent enterprise basics
- •Risk: enterprise buyers push for slower shipping; SMB expects rapid value expansion
- •Timing signal for bottoms-up: multiple pockets of adoption inside large orgs
- •Slack’s priority: the end user; enterprise growth often starts self-serve (85%+ claim)
Knowing a big product works: internal prototypes, adoption depth, and pilot networks
Noah outlines Slack’s validation loop for major features: start with rough internal prototypes, scale internal adoption, then run progressive pilots with diverse customers. Because many features are social, he emphasizes org-level pilots and mixed quantitative/qualitative feedback.
- •Prototype internally first—ugly but informative—before heavy polish and scaling
- •Measure sustained adoption: daily/weekly retention and depth of usage
- •Use champion/pilot networks across segments and geographies
- •Social features require org-level rollout; classic user-level A/B tests often don’t apply
M&A reality for product leaders: buy vs build, integration challenges, and ‘speed is oxygen’
Noah recounts Slack’s ‘Post’ acquisition and why it failed to gain adoption, highlighting speed/latency as the decisive UX factor. He then broadens into buy-vs-build tradeoffs, arguing product/tech integration is often slower than expected and requires a dedicated muscle many companies lack.
- •‘Post’ underperformed: rich editing experience demands extremely high speed/quality
- •Lesson: speed is the oxygen of product; latency kills otherwise ‘obvious’ features
- •Acquisitions often pursued when ambitions exceed org capacity, but may not reduce time-to-market
- •Slack stronger at talent integration than product/technical integration; integration is a repeatable capability
Product ‘wisdom’ that’s BS + quickfire: promotions, CPO timing, art vs science, and genAI product thinking
Noah critiques overly rigid PM professionalization and framework cargo-culting, arguing PM should be fluid and impact-driven. In quickfire, he covers when to hire product leadership, cross-functional tensions, promotions, art vs science, and the importance of matching AI product promises to model confidence.
- •Rigid role definitions and copy-paste frameworks can reduce impact and joy in PM work
- •Promotion advice: demonstrate real customer/business impact (inputs aren’t enough)
- •CPO timing: hire when founder becomes a decision bottleneck; prioritize accelerators first
- •Product art vs science depends on maturity: early is art-heavy; mature areas are optimization-heavy
- •GenAI: align UX promises with confidence/quality; design for transparency and ‘assistant’ mental models

Publisher timestamps

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.