Lenny's PodcastThe 10 traits of great PMs, AI, and Slack’s approach to product | Noah Weiss (Slack, Google)
CHAPTERS
- 0:00 – 0:43
Taking bigger, bolder bets: “get to the next hill” (cold open)
Noah shares Slack’s metaphor for escaping incrementalism: getting to the next hill to reveal a bigger opportunity range beyond current KPIs. He explains how Slack incubates new teams for emerging areas like AV (Huddles/Clips) and now AI, driven by customer “superpower” requests.
- •Avoiding teams getting stuck optimizing small KPI lifts
- •The ‘next hill’ metaphor to discover larger strategic terrain
- •Incubating new teams to explore immature product areas
- •Pandemic-driven creation of Huddles and Clips
- •Applying the same incubation formula to AI prototypes and pilots
- 0:43 – 1:43
Show setup: Noah’s background and what this episode will cover
Lenny introduces Noah Weiss, his career path (Google, Foursquare, Slack), and the main themes of the conversation. The episode scope is set: PM traits, working with opinionated founders, AI/ML lessons, complaint storms, and Slack’s growth inflection points.
- •Noah’s roles: CPO at Slack; prior PM leadership at Foursquare and Google
- •Topics preview: 10 traits of great PMs, founder collaboration, AI, prioritization
- •Slack-specific practices: complaint storms and self-serve turnaround
- •Competitive landscape: Microsoft Teams and Discord
- •Personal angle: new-parent advice is also included
- 1:43 – 4:21
Sponsor break and pre-interview transition
A short sponsor segment runs before the main interview begins. It focuses on career peer groups and email productivity tools.
- •Sidebar: peer groups as a ‘personal board of directors’
- •Superhuman: speed, AI features, and inbox workflows
- •Context switch reduction and productivity positioning
- •Transitions into the interview proper
- 4:21 – 7:23
Advice for new parents: maxims from paternity leave
Noah and Lenny connect over paternity leave timing, and Noah shares three grounding maxims for the first months. The advice emphasizes gradual improvement, keeping perspective, and being fully present (including a digital detox).
- •“A little bit better every day” as the core mindset
- •Don’t extrapolate the first days into the next 18 years
- •Be fully involved: diapers, feeds, talking to the baby
- •Digital detox to strengthen connection and presence
- •Lenny’s plan to backlog content to be present during leave
- 7:23 – 11:34
Foursquare lessons: social vs. place framing, and the pivot to B2B
Lenny and Noah revisit Foursquare’s journey, including how the product’s ‘atomic unit’ framing shaped outcomes. Noah reflects on competition timing (Instagram, Google Maps) and why B2B models often provide faster feedback loops than ad-supported consumer growth.
- •Foursquare’s key misframing: place-centric vs. moment/experience-centric sharing
- •Local discovery and recommendations as enduring user value
- •Google Maps distribution advantage over time
- •Learning from ‘scar tissue’ when outcomes fall short
- •Why B2B monetization gives clearer, faster signal than ads-at-scale
- 11:34 – 16:54
Working with strongly opinionated founders: principles + the “U-shaped” involvement model
Noah explains how to be effective when the CEO/founder is also product-minded and highly involved. The playbook: align on product principles and vision early, then use a U-shaped involvement curve—deep involvement at the start and end, with team autonomy in the middle.
- •Expect both high learning and high frustration with founder-led product orgs
- •Codify shared product principles to avoid ‘Goldilocks’ feedback loops
- •Founder holds vision; teams need room to explore within aligned constraints
- •U-curve involvement: early alignment, mid autonomy, late quality/taste checks
- •Make late-stage refinement collaborative (e.g., bug-bash style sessions)
- 16:54 – 19:32
Slack’s product principles: craft, clarity, and ‘Don’t make me think’
Noah shares how Slack formalized product principles to scale consistent decision-making. He highlights principles like being a great host and reducing cognitive load, including the nuance that more clicks can be acceptable when they increase trust and comprehension.
- •Principles as the language for scaling product quality across teams
- •Slack mission translated into product behavior: simpler, more pleasant, more productive
- •“Be a great host” as a craft and foresight standard
- •“Don’t make me think” and designing for diverse user sophistication
- •Counterintuitive idea: sometimes more steps improves confidence and clarity
- 19:32 – 22:42
Implementing ML/AI/LLMs: trust, transparency, and virtuous data loops
Noah traces his AI experience from Google’s Knowledge Graph to recommendations at Foursquare and ML/search at Slack. He stresses matching UI promises to model quality, reducing overconfidence/hallucinations, and designing product loops that generate training signal naturally.
- •Knowledge Graph roots: extracting structured facts via NLP
- •LLMs’ new capability: human-like natural language generation
- •Critical risk: confident hallucinations undermine trust
- •Use transparency and provenance to build credibility
- •Design virtuous cycles where usage naturally produces better training data
- 22:42 – 25:11
Slack’s AI vision: enterprise knowledge access and a ‘chief of staff’ north star
Lenny probes Slack’s potential for AI over company knowledge, and Noah shares internal prototyping and a long-held ‘magic AI stuff’ aspiration. They discuss a north star where Slack summarizes what matters and helps users drill down—without overpromising what the tech can’t yet deliver.
- •Internal prototypes for Q&A over Slack conversations
- •2014-era roadmap joke turned real: “magic AI stuff on top”
- •Opportunity: unlocking hard-to-reach organizational knowledge
- •North star: personalized summaries prioritized by what you care about
- •Balancing ambition with realistic delivery quality expectations
- 25:11 – 27:00
How Slack structures AI teams today: shared infrastructure + parallel prototypes
Noah outlines Slack’s hybrid org approach to AI: a central ML/search infrastructure team plus multiple prototyping teams working on different customer problems. The structure is intentionally flexible because the tech, risks, and trade-offs are evolving month to month.
- •Central ML/search team builds reusable infrastructure
- •Multiple focused teams prototype in parallel across problem areas
- •Current structure optimized for speed amid fast-changing capabilities
- •Not the long-term steady state; AI will become embedded in every roadmap
- •Analogy: like mobile roadmaps—eventually owned by each product area
- 27:00 – 32:26
Complaint storms and customer-love sprints: turning friction into roadmap work
Noah describes Slack’s ‘complaint storms’—group sessions to critique user journeys (starting with other products to calibrate taste). He then explains how Slack prioritizes fixes via a portfolio roadmap and recurring customer-love sprints to ship lots of small, high-impact improvements.
- •Complaint storms address empathy gaps for new and less-expert users
- •Start by critiquing adjacent products to build shared calibration
- •Shift from pain discovery to actionable inspiration and creativity
- •Roadmap as a portfolio: new capabilities, risky bets, and incremental quality
- •Customer-love sprints: 2-week bursts to ship many small delight improvements
- 32:26 – 34:41
Delight as Slack’s DNA: CE feedback loops, hiring, and user-research rituals
Noah explains why delight is foundational at Slack, tracing it to the founders’ Glitch background and consumer-grade expectations for work software. He also shares operational mechanisms—Customer Experience insights, support shifts, and live-commentary usability sessions conducted in Slack threads.
- •Origins in Glitch shaped a playful, consumer-grade craft mindset
- •Hiring skewed toward consumer/game backgrounds vs. traditional enterprise
- •CE team as the closest continuous link to customer pain and confusion
- •Product teams historically did CE shifts to build empathy
- •Usability sessions with real-time team commentary in Slack threads as a ritual
- 34:41 – 38:04
Competition: HipChat, Discord, and Microsoft Teams—customer-obsessed, competitor-aware
Noah breaks down Slack’s competitive posture across eras: winning early via a 10x leap on key axes, staying focused on work (not communities), and differentiating from Teams via channel-centric workflows and an open ecosystem. He emphasizes Slack’s maxim: customer obsessed, competitor aware.
- •Slack’s early edge: mobile sync, working search, consumer messaging patterns
- •Discord seen as adjacent; different audience (communities) vs. work teams
- •Teams as the largest competitor, born partly defensively to protect Office
- •Many enterprises use both—Slack as ‘connective tissue’ across tools
- •Strategy mantra: customer obsessed, competitor aware
- 38:04 – 44:51
Scaling innovation at Slack: incubators, pilots, and prototyping in real software
Noah explains how Slack preserves startup-like innovation through cultural norms and structural incubation. He also shares a small but high-leverage execution change: moving faster from static mocks to real prototypes to resolve debates by ‘feeling’ the software.
- •Cultural self-image: staying ‘startup-like’ to encourage boldness
- •Incubating net-new teams to explore new categories before they mature
- •Learning pace as a primary metric for incubator teams
- •Shift from static design debates to early, disposable real-software prototypes
- •Rituals that keep teams grounded in real user feedback and quality bars
- 44:51 – 53:22
Reviving Slack’s self-serve business: new levers, trials, and ‘Successful Teams’
Noah recounts how Slack’s self-serve growth plateau revealed an empathy and market-shift problem as Slack moved beyond early adopters. The turnaround required throwing out the old roadmap, investing in learning, introducing trial experiences, and adopting a new activation metric (‘Successful Teams’) predictive of upgrade.
- •Self-serve fundamentals weakened as Slack moved beyond tech early adopters
- •Decision to prioritize learning over short-term impact for multiple quarters
- •Comprehension + desirability as core onboarding challenges
- •Introducing trial strategies to ‘taste’ premium value (beyond pure freemium)
- •North star activation: ‘Successful Teams’ (critical mass predicts upgrades)
- 53:22 – 1:02:04
Slack’s early product-led growth and scaling customer pilots for new features
Noah explains what Slack did early that people often miss: it wasn’t a PLG playbook—it was obsessive focus on a product users would evangelize inside teams. He then details Slack’s mature pilot program: diverse, high-tolerance customers testing multiplayer features in the wild before broad launch.
- •PLG term didn’t exist—Slack won by building something teams wanted to share
- •Dual audience: SMBs (entire company) and teams inside large enterprises
- •Enterprise sales motion built atop organic internal adoption signals
- •Robust pilot program with progressive rollout to thousands of customers
- •Selecting pilots: diversity (industry/size/location) + willingness to tolerate churn/changes
- 1:02:04 – 1:17:17
Noah’s “10 Traits of Great PMs”: skills by seniority, writing, and data/taste balance
Noah walks through core PM traits: future-back thinking, team amplification, decision-quality facilitation, execution, impact, writing, learning velocity, data fluency, and taste. They also discuss book recommendations for writing and how the most important traits shift from early-career (execution/impact/data) to leadership (decision-making, strategy, writing).
- •PMs amplify teams; avoid ‘mini-CEO’ dictator anti-pattern
- •Facilitate pace and quality of decisions vs. personally making them
- •Execution as baseline credibility; impact as the ultimate career unlock
- •Writing as scalable influence; multiple recommended writing books
- •Data fluency + product taste as a powerful, creative decision-making combo
- 1:17:17 – 1:25:33
Lightning round: leadership books, parenting tech, Slack pro tips, and closing
In rapid-fire Q&A, Noah shares favorite books, shows, interview questions, and surprisingly impactful products—mostly new-parent tech. He closes with two Slack power tips (sidebar sections and quick switcher), plus where to find him and what feedback he wants from listeners.
- •Book recs: Innovator’s Dilemma, Radical Candor, Leadership in Turbulent Times
- •TV recs: Succession and The Bear
- •Interview question: ‘unfair secrets’ to boost team velocity and energy
- •Favorite products: Nanit, SNOO, UPPAbaby stroller system
- •Slack pro tips: customize sidebar sections; use quick switcher (Cmd/Ctrl+K)
