LLenny's Podcast
← All episodes
Noah Weiss (Slack, Foursquare, Google)23 July 2023

The 10 traits of great PMs, how AI will impact your product, and Slack’s product development process

7Frameworks
14Insights

Frameworks in this episode

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Hot Take· 4

Hot Take11:00

Why So Many Consumer Companies End Up Pivoting to B2B

Noah argues B2B is an easier path to an incremental, sustainable business than pure consumer. The reason is the feedback loop: whether people will pay is a far faster signal than trying to build enough consumer reach to later slap ads on it. Pure consumer is a swing-for-a-home-run bet where you don't know if it's working along the way.

  • Willingness-to-pay is a much faster signal than large-scale consumer reach
  • The ad-supported consumer path is a home-run bet with no signal along the way
  • B2B makes incremental, provable business-building easier
  • Both Foursquare and Slack are examples of the consumer-to-B2B arc

the feedback something that you get from are people willing to pay for the product that you're building is so much faster than can I…

Noah Weiss · 11:00
#b2b#business-model#monetization
Hot Take21:30

The UI Must Match the Data: LLMs Look Confident Even When Hallucinating

From 15 years of AI work at Google and Slack, Noah's guiding principle is that the confidence of the UI must match the quality of the underlying data. A key failing of current LLMs is that they appear supremely confident even when completely hallucinating, which erodes user trust. He argues for transparency about data sources and models that acknowledge uncertainty.

  • The promise of the UI has to match the quality of the underlying data
  • Current LLMs appear supremely confident even when completely hallucinating
  • Systems should acknowledge uncertainty rather than sound faultless
  • Transparency about where data comes from builds credibility
  • Design virtuous cycles so usage generates training data (like Netflix's feedback loop)

the promise of the UI has to match the quality of that underlying data

Noah Weiss · 21:30

they all appear supremely confident even when they're completely hallucinating

Noah Weiss · 21:30
#ai#llms#product-design#trust
Hot Take51:00

Product-Market Fit Is Stacking S-Curves, Not a One-Time Win

Responding to founders at billion-dollar companies who still feel they lack product-market fit, Noah frames PMF as stacking S-curves. You win a small group, hit exponential growth, then plateau as you saturate that audience, and must build fresh PMF for the next curve (non-developers, enterprises, non-US teams). It demands a beginner's mindset and self-criticism at each new audience.

  • PMF is not permanent; it's a series of stacked S-curves
  • Each curve grows exponentially, then declines as you hit that audience's ceiling
  • The next curve is a new audience with needs the previous one didn't have
  • Requires humility and a beginner's mindset, not presuming you've cracked it forever
  • Successful B2B founders often feel they've lost PMF with the audience they want next

product Market fit is almost like you keep stacking these S curves where you get product Market fit in a small group

Noah Weiss · 51:00
#product-market-fit#growth#strategy
Hot Take1:05:30

'PM as Mini-CEO' Is the Most Dangerous Advice in Product Management

Noah calls the classic 'PMs should be mini-CEOs' framing the most dangerous piece of advice in product management history, because it produces PMs who act like dictators instead of facilitators. The real job is to amplify the team and facilitate the pace and quality of decision-making, not to make every decision or play arbitrary tiebreaker.

  • 'PM as mini-CEO' breeds dictator behavior and teams that reject having a PM
  • A great PM amplifies the team and helps them do the best work of their lives
  • The job is to facilitate the pace and quality of decisions, not make them all
  • New PMs often crave power then find the job is influence and facilitation
  • Good PMs help the team make high-quality decisions quickly without a tiebreaker

PM should be mini CEOs I think that's the most dangerous piece of advice ever in the history of product management

Noah Weiss · 1:05:30
#product-management#leadership#careers

Explainer· 3

Explainer13:30

The U-Curve of When to Involve a Product-Minded Founder

Working with strong founders like Stewart Butterfield and Dennis Crowley, Noah found founder involvement should follow a U-curve over a project's timeline. Get them deeply involved early to agree on principles, goals and anti-goals, let the team run in the middle, then bring them back at the very end to 'taste the soup.' Skipping that final co-creation step makes launches far more painful.

  • Involvement should be high early, low in the middle, high again at the end (a U-curve)
  • Early: align on principles, the vision, goals and anti-goals so the team can explore
  • End: the founder must taste the finished product and catch what's missing
  • Refine in code, not static mocks, because using software is different from viewing it
  • Slack ran collective 'bug bash' sessions with Stewart and the whole team to refine

almost like a u curve where the x-axis is time and the y-axis's level of involvement

Noah Weiss · 14:00

customers like literally taste the soup what's missing in it

Noah Weiss · 14:30
#founders#product-leadership#process
Explainer27:00

Complaint Storms: Critique a Rival's Product Before Your Own

Slack's 'complaint storms' ritual, started around 2019-2020, helps a team look at software with fresh eyes. The trick is to start by walking through an adjacent or competitor product on one shared screen, listing every confusing point and pain point, before turning that same critical lens on your own product. Starting with someone else's product removes the sting and generates a backlog of ideas.

  • Power users (like people who live in Slack all day) lose empathy for new users
  • The team projects one product on a screen and logs every confusion and pain point
  • Starting on an adjacent/competitor product first makes self-critique less painful
  • Used whenever a team feels stuck or hits a dead end
  • Similar in spirit to Stripe's 'friction logging'

or myself would also join and we'd actually start off with other products first like an adjacent spaces

Noah Weiss · 28:00
#product-process#ux#slack#rituals
Explainer49:00

Slack's 'Successful Teams' Metric: Get Five People Communicating for a Week

Through data science, Slack landed on a new North Star called 'successful teams': if five people used Slack for the majority of their work week just to communicate, that team was far more likely to upgrade within six months. It seems like a low bar, but hitting that critical mass meant the rest took care of itself, and it rallied product teams across the company.

  • The metric sat earlier in the funnel than paid customers but predicted upgrades
  • Threshold: five people using Slack most of the work week to communicate
  • Teams that hit it were far more likely to upgrade over the next six months
  • A low but predictive activation bar that reaches critical mass
  • It aligned teams beyond just self-serve around driving successful teams

five people using slack the majority of their work week to just communicate at all that would be a successful team

Noah Weiss · 49:30
#metrics#activation#growth#slack

Story· 3

Story05:00

Noah Weiss's Three Maxims for Surviving the First Two Months of Parenthood

Just back from paternity leave, Noah shares the three maxims he and his wife used to stay grounded as new parents. The through-line: give yourself grace, don't project the newborn phase onto the future, and fully immerse yourself including a digital detox. It's a warm aside that opens the episode.

  • Get a little bit better every day and give yourself permission when something doesn't go right
  • Don't over-extrapolate from the early days; the newborn 'fourth trimester' is not the next 18 years
  • Fully get into it as a parent, including a full digital detox to be present
  • Nothing replaces actually doing it no matter how many books you read

number two don't over extrapolate from the early days

Noah Weiss · 05:30

you gotta fully get into it as a parent like there's nothing that replaces actually you got to change the diapers you got to do…

Noah Weiss · 06:00
#parenting#advice#work-life
Story09:00

The Foursquare Mistake: Betting on the Wrong Atomic Unit vs Instagram

Noah's mini post-mortem on why Foursquare never became a massive consumer app. The core error was believing the atomic unit was a person talking about a place they're physically at, rather than a person sharing a moment or experience anywhere. Instagram, an early Foursquare API developer, won the social side; Google later caught up on utility.

  • You learn more from things that don't fully work out because of the negative feedback loop
  • The fatal frame was 'a person at a place' instead of 'a person sharing a moment or experience'
  • Instagram used the Foursquare API before Facebook acquired them
  • Google's billion+ Maps users on Android/iOS eventually replicated the utility
  • Foursquare ultimately pivoted to a valuable B2B data/API business

there's something actually where you learn more from the things that don't solely work out or don't quite achieve what you wanted to achieve

Noah Weiss · 08:00

mistaken to believe that the idea that the atomic unit would be a person talking about a place that they're at and you have to…

Noah Weiss · 09:30
#foursquare#product-market-fit#post-mortem#startups
Story46:30

When Slack's Self-Service Plateaued, They Threw the Roadmap Away

Around 2019 Slack's self-service business quietly plateaued as it moved from early adopters to a later-majority market with different needs. Instead of optimizing what had worked, the team threw out the roadmap, generated hypotheses about new levers, and deliberately accepted ~six months of zero impact in exchange for learning. It ultimately doubled the rate of new paid customer growth.

  • Cohort curves looked unhealthy as Slack saturated tech-savvy early adopters
  • They discarded the roadmap and formed hypotheses about new growth levers
  • They chose to sacrifice near-term impact for ~6 months to optimize for learning
  • The payoff: roughly doubling the rate of new paid customer growth
  • Requires humility and not presuming you deserve every company on Earth

let's kind of throw the whole roadmap away and instead let's come up with a bunch of hypotheses about what could be new levers

Noah Weiss · 46:30

for the next like six months we're probably not going to drive any impact at all it's only going to be about learning

Noah Weiss · 47:00
#growth#self-service#slack#learning

Tool· 1

Tool31:00

Customer Love Sprints: A Two-Week Hackathon Where You Ship Everything

Slack allocates 'customer love sprints,' a two-week hackathon-style burst focused on the lowest-effort, highest-impact changes to generate customer love in a feature area. Unlike a throwaway hackathon, the explicit goal is to ship all of it. User-facing teams run them at least quarterly; less user-facing teams roughly twice a year.

  • A burn-down list of lowest-effort, highest-impact love-generating changes
  • Design, product and engineering sprint together for two weeks
  • The goal is to ship all of them, not throw the work away
  • A fun change of pace from multi-month feature work
  • Run at least quarterly on user-facing teams

the goal is to ship all of them so this isn't like hacks that you throw away

Noah Weiss · 31:30
#product-process#sprints#slack#prioritization

Takeaway· 3

Takeaway35:00

Customer Obsessed but Competitor Aware

Noah's maxim for operating in a crowded market (HipChat, Discord, Microsoft Teams) is to be customer obsessed but competitor aware, contrasted with companies like Uber that were notoriously competitor-obsessed. Slack didn't set out to kill HipChat; it won by being 10x better on a few axes like cross-client search and bringing consumer messaging delight (emoji, reactions) to work.

  • Be customer obsessed but competitor aware, not competitor-obsessed
  • Slack beat HipChat/Campfire by being 10x better on a few axes
  • Great mobile, search that actually worked, and consumer-grade emoji/reactions
  • Discord serves communities, a fundamentally different audience than work teams
  • Teams was a defensive move to protect Office; many customers happily use both

we're customer obsessed but competitor aware

Noah Weiss · 35:00
#competition#strategy#slack
Takeaway56:00

Slack's Real Growth Engine: A Product People Stake Social Capital On

Asked what Slack did right that people under-appreciate, Noah says 'product-led growth' wasn't even a term yet. The core was building something customers loved enough to put their own social capital on the line to get co-workers on board, easy enough to adopt and pay for without ever talking to a salesperson. In today's saturated acquisition channels, word-of-mouth is increasingly the only way to scale.

  • 'Product-led growth' wasn't a named playbook when Slack started
  • The engine was customers risking their own social capital to onboard co-workers
  • Easy enough to self-serve and expense without talking to a salesperson
  • Small teams inside big companies (IBM, Disney, Apple) discovered Slack independently
  • Echoes Seth Godin: the products that win are the ones you want to tell friends about

building a product that customers loved enough that they would put their own social capital on the line to get their co-workers on board

Noah Weiss · 54:00
#growth#word-of-mouth#product-led-growth
Takeaway1:22:30

The Biggest Unlock: Prototype in Real Software, Not Static Mocks

Asked for a minor change with outsized impact, Noah points to a cultural shift: Slack stopped burning cycles on static design mocks and walkthroughs and started prototyping the real, messy software as fast as possible, even if it gets thrown away. For a product like Slack you have to live, touch and smell the software, and this avoided months of design debates.

  • Stopped spending cycles on static mocks and design walkthroughs
  • Prioritized getting into real, messy prototype software quickly
  • You can't just look at software; you have to live and touch it
  • Avoided months-long design debates by getting to how it actually feels
  • Throwaway prototypes are fine if they reveal the real experience faster

we stopped spending so many cycles on design explorations of like static mocks or walkthroughs and said how quickly can we get into prototyping the…

Noah Weiss · 1:22:30
#prototyping#product-process#design