Lenny's PodcastThe 10 traits of great PMs, AI, and Slack’s approach to product | Noah Weiss (Slack, Google)
CHAPTERS
Teaser: “Next hill” thinking—incubating bold bets in audio/video and AI
Noah opens with Slack’s metaphor of “getting to the next hill” to avoid getting stuck in incremental improvements. He explains how Slack incubates brand-new teams to explore emerging areas like Huddles/Clips during the pandemic and now AI, guided by customer demand and rapid prototyping.
- •“Take bigger, bolder bets” as an explicit product principle
- •Teams can over-focus on near-term climb and miss the bigger opportunity beyond
- •Incubating new teams from scratch before an area matures
- •Pandemic-driven creation of Huddles and Clips
- •Applying the same incubation formula to AI prototypes and pilots
Noah’s career path: Google → Foursquare → Slack CPO
Lenny introduces Noah’s background and the themes for the episode: great PM traits, founder collaboration, AI/ML product lessons, and Slack’s product practices. The stage is set for a wide-ranging conversation spanning leadership, craft, and growth.
- •Noah’s roles: Google Search/Knowledge Graph, Head of Product at Foursquare, CPO at Slack
- •Episode roadmap: PM traits, working with strong founders, AI/ML, prioritization, and growth
- •Slack as a product and org that emphasizes craft and customer love
New parent advice: staying grounded during the “fourth trimester”
Noah shares three practical maxims for new parents—continuous improvement, avoiding early over-extrapolation, and full presence. He emphasizes digital detox and immersion as a way to build connection during the intense early months.
- •“A little bit better every day” mindset
- •Don’t extrapolate the first 18 days to the next 18 years
- •Be fully present: do the diapers/feeds, talk to the baby
- •Digital detox as a tool to deepen family connection
- •Transitioning back to work right after leave
Foursquare postmortem: social vs. utility, timing, and competition dynamics
Noah reflects on why Foursquare’s consumer trajectory was hard to sustain, especially amid Instagram’s rise and Google Maps’ scale. He contrasts a “person-at-a-place” framing with sharing moments/experiences, and explains why the company’s B2B data/API direction emerged as a durable outcome.
- •Atomic unit mismatch: place-tied sharing vs. moment/experience sharing
- •Local discovery and recommendations as a stronger long-term use case
- •Platform relationships (e.g., early Instagram as an API consumer)
- •Google Maps distribution advantage and eventual feature catch-up
- •Why B2B monetization provides faster feedback loops than consumer+ads
Working with strongly opinionated, product-minded founders
Noah shares how to thrive when the CEO is deeply involved in product: align on explicit product principles and treat vision as shared context rather than constant re-litigation. He outlines the tradeoff—high learning potential but lower perceived agency—especially relevant for early PMs at startups.
- •Expect frustration + learning when the CEO overlaps your functional domain
- •Translate taste/intuition into shared product principles and language
- •Maintain CEO as vision-holder while giving teams creative space
- •Avoid “Goldilocks” review cycles by using principles as constructive criteria
The U-shaped founder involvement model—and why shipping requires “tasting the soup”
Noah explains a practical pattern for founder engagement: heavy involvement early (alignment), light involvement midstream (team exploration), and heavy involvement late (quality bar). He describes hands-on end-stage refinement via in-product reviews and group “bug bashes” to collaboratively raise craft.
- •U-curve: early alignment → autonomy → late-stage quality involvement
- •Agree on goals and anti-goals before execution
- •Founder feedback is most effective in real software, not static mocks
- •Collective refinement beats “team wants to ship vs. founder says no” tension
- •Polish and delight are often discovered at the end through use
Slack’s product principles: craft, clarity, and reducing cognitive load
Noah shares how Slack operationalizes product taste through explicit principles tied to its mission. He highlights principles like “Be a great host” and “Don’t make me think,” and explains why sometimes more clicks can be better when they increase confidence and comprehension.
- •Principles as scalable “common language” for product decisions
- •“Be a great host” as craft: foresight and step-saving details
- •“Don’t make me think” for simplicity across diverse user backgrounds
- •Slack’s hidden complexity demands clarity in UX
- •Counterintuitive lesson: more clicks can be okay if it improves understanding
ML/AI/LLMs in product: trust, transparency, and learning loops
Drawing from Google Search and the Knowledge Graph through to Slack, Noah explains what makes AI products succeed: UI promises must match model quality, confidence must be calibrated, and systems need feedback loops that naturally generate training data. He frames LLMs as a major leap in natural language generation—but also a new trust challenge due to hallucinations.
- •From Knowledge Graph to LLMs: evolution from extraction to generation
- •Mismatch risk: confident UI + uncertain/hallucinated output erodes trust
- •Transparency about sources builds credibility
- •Design for virtuous cycles that collect training signals as a byproduct
- •LLMs unlock new experiences but require careful product framing
Slack’s AI org design: shared infrastructure + parallel prototypes
Noah describes Slack’s hybrid approach: a central ML/search team builds shared infrastructure, while multiple teams prototype in parallel on distinct customer problems. He notes this is a transitional model while the technology and tradeoffs evolve rapidly, with an eventual steady state where AI becomes embedded in every product area.
- •Central ML/search team provides reusable infrastructure
- •Multiple prototyping teams explore different AI directions in parallel
- •Fast-moving capability/risk landscape drives a flexible org approach
- •Long-term expectation: AI becomes part of each team’s roadmap (like mobile)
Complaint storms and “customer love sprints”: turning critique into prioritization
Noah explains “complaint storms,” where teams systematically document confusion and pain points—often starting with competitor products to calibrate taste—before applying the process to Slack itself. He then describes how Slack prioritizes these insights using a roadmap-as-portfolio view and executes improvements via focused two-week “customer love sprints.”
- •Complaint storms: structured, critical walkthroughs of user journeys
- •Start with adjacent products first to build calibration and reduce defensiveness
- •Portfolio roadmapping: balance new bets, incremental polish, risk, and learning
- •Customer love sprints: two-week push to ship low-effort, high-impact improvements
- •Quarterly cadence for user-facing teams to maintain delight and quality
Delight as Slack’s DNA: CE feedback loops, user research rituals, and competitive posture
Noah ties Slack’s delight to its origins (Glitch) and to hiring from consumer/game backgrounds. He details how the Customer Experience team and embedded support signals feed product priorities, and how Slack keeps teams close to real user behavior through interactive, threaded reactions during usability sessions. He also explains Slack’s competition mantra: customer-obsessed, competitor-aware.
- •Slack’s “consumer-grade for work” roots from Glitch and founder DNA
- •CE (Customer Experience) as a high-signal pipeline of pain points and insights
- •Ritual: live-commenting in Slack threads during usability sessions to involve engineers/PMs
- •Competition framing: customer-obsessed but competitor-aware (HipChat, Discord, Teams)
- •Slack’s differentiation: channels/workflows + open platform as connective tissue
Re-accelerating self-serve growth: learning-first reset, trials, and a new North Star metric
Noah recounts Slack’s 2019 self-serve plateau and how the team responded by discarding the old roadmap and prioritizing learning over short-term impact. Key levers included improving comprehension/desirability, introducing trial strategies to showcase premium value, and aligning the org around “Successful Teams” as an activation metric predictive of conversion.
- •Plateau diagnosis: new customer cohorts had different needs than early adopters
- •Operational reset: “throw the roadmap away” and run hypothesis-driven learning
- •Comprehension + desirability as core adoption barriers for mainstream users
- •Trial strategy to give users a premium “taste” and drive upgrades
- •North Star metric: “Successful Teams” (critical mass predicts higher conversion)
Scaling innovation: pilot programs, prototyping in code, and taking bigger bets
Noah explains how Slack keeps shipping 0→1 products by preserving startup spirit and structurally incubating new teams with permission to move fast. He details Slack’s robust pilot program for multiplayer features, emphasizes diversity and risk tolerance in pilot customers, and shares a key execution unlock: prototype in real software earlier to avoid endless static mock debates.
- •Cultural guardrail: avoid constant incrementalism; pursue “next hill” visibility
- •Incubated teams for new areas (Huddles/Clips, AI) with learning-focused pace
- •Pilot program at scale: progressively larger rollouts and rich feedback loops
- •Selecting pilot customers: diversity + motivation + higher pain tolerance
- •Execution change: move from static mocks to prototypes in real code early
The 10 traits of great PMs: execution, impact, decision quality, writing, data fluency, and taste
Noah walks through his well-known framework for PM excellence, emphasizing facilitation over “mini-CEO” power fantasies. He highlights how expectations shift by seniority: early-career PMs build credibility through execution, impact, and data fluency, while senior leaders focus on organizational decision quality, longer-term strategy, and writing as scalable influence.
- •Work backward from a future vision; bring inspiration to the team
- •Amplify the team: facilitation, energy, and momentum over control
- •PM as decision-quality accelerator, not the sole decision-maker
- •Execution + impact as foundational career accelerators
- •Senior leverage: writing to scale alignment; combine data fluency with product taste
Lightning round: book recs, interview question, parenting tech, and Slack power tips
Noah shares favorite books (including strategy and leadership), TV picks, a go-to interview question, and standout products he loves as a new parent. He closes with two Slack pro tips—sidebar sections and the quick switcher—plus where to find him and how listeners can help via feature requests.
- •Book recommendations: Innovator’s Dilemma, Radical Candor, Leadership in Turbulent Times
- •Favorite shows: Succession and The Bear
- •Interview question: “unfair secrets” for improving team velocity and energy
- •Parenting tech products: Nanit, SNOO, UPPAbaby
- •Slack tips: organize sidebar into sections; use quick switcher (Cmd/Ctrl+K)
