LLenny's Podcast
← All episodes
David Singleton (CTO of Stripe)04 May 2023

Building a culture of excellence

8Frameworks
14Insights

Frameworks in this episode

Innovation6 steps

Alpha Co-Creation Loop

Pick the users who are already pushing the boundary, build with them in a shared channel, ship only when they're thrilled.

Read →
Productivity6 steps

Friction Logging

Adopt a specific user's identity, walk your own product end-to-end, and log every point of friction.

Read →
Leadership6 steps

Group UX Review and Walking the Store

Taste the soup together — experience the product as a group, log issues live, then debate each one.

Read →
Leadership6 steps

Hire for Autonomy: References, Real Work, and Default Trust

You'll be in none of the decisions that matter — so hire people you can hand autonomy to, and verify via references.

Read →
Productivity6 steps

Internal Tools as a Product (The Crying Octopus)

Run your dev-productivity team like a product team: monthly surveys, hard metrics, and one-click paper cuts.

Read →
Strategy6 steps

Ship Fast Without Breaking Money

Reject the reliability/velocity trade-off: automated gauntlet, ramped exposure, and remediations ahead of roadmap.

Read →
Leadership6 steps

The Engineer-cation

Leaders clear 3-4 days, join a team as an IC, ship one small feature to production, and log the friction.

Read →
Strategy6 steps

The Inverted W Planning Process

Teams propose, leaders synthesise, teams adjust, leaders resynthesise, orgs distribute with context.

Read →

Insights & moments

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

Explainer· 4

Explainer18:00

How Stripe Co-Creates Products With a Small Group of Early Users

Singleton describes Stripe's core product-development approach: find the right set of early users and co-create the product with them. For Stripe Billing they partnered with existing customers like Figma and Slack, ran shared Slack channels, showed product regularly, and only broadened access once that alpha group was thrilled.

  • Product development starts by finding the correct set of early users to co-create with
  • Stripe Billing was built alongside subscription customers already on Stripe, like Figma and Slack
  • Shared Slack channels and frequent product demos kept the feedback loop tight
  • The product only went to a broader audience once the alpha group was super happy

“And only when that original kind of alpha group was super, super happy with the product, did we then think it might be ready to…”

David Singleton · 19:30
#product-development#user-feedback#stripe-billing#co-creation
Explainer22:30

What Stripe's 'Operating Principles' Actually Are

Singleton distinguishes operating principles from abstract corporate values: they are concrete behaviors distilled from the most effective Stripes. The early team took a deliberate detour to codify what had made them successful. Principles are grouped into how we work, who we are, and ones leaders must execute, with 'users first' as the very first.

  • Operating principles are behaviors distilled from the most effective Stripes, not abstract values
  • The early team paused to capture what made Stripe successful so it would survive scaling
  • Principles are segmented into how we work, who we are, and leader-must-execute categories
  • The first operating principle is 'users first'; 'be meticulous in your craft' is a 'how we work' one

“So, they are behaviors distilled from the most effective Stripes.”

David Singleton · 23:00

“The very first operating principle we have, by the way, is users first.”

David Singleton · 23:00
#culture#operating-principles#values#leadership
Explainer53:30

How Stripe Deploys Constantly While Staying 99.999% Reliable

Singleton explains how Stripe reconciles rapid change with extreme reliability. There are no manual testers; automated test suites run on every change, then staged environments and gradual production ramps catch issues. A change typically reaches production automatically within about 45 minutes, enabling same-day feedback loops with users.

  • No manual testers; automated tests cover the vast array of API endpoints and configs
  • Changes flow through staging environments, then ramp from a small traffic percentage to full
  • A change typically reaches production automatically in about 45 minutes
  • Reliability also depends on incident response and prioritizing 'instant remediations' ahead of roadmap work

“We don't have manual testers because manual testers couldn't possibly cover the the vast array of API endpoints and configurations that we offer.”

David Singleton · 54:00

“every change that a Stripe engineer submits once it's passed those tests, it actually ends up in production automatically over the course of the next…”

David Singleton · 55:00
#reliability#deployment#testing#engineering-culture
Explainer1:03:30

How Stripe Is Already Using LLMs Across Its Products

Singleton walks through Stripe's early large-language-model applications: GPT-4 reads all of Stripe's docs as embeddings to answer developer questions, and the Sigma product now lets non-developers write SQL in natural language. Internally, Stripe stood up a governed GPT-4 UI with shareable prompt presets used across marketing and support, and rolled out Copilot to engineers.

  • GPT-4 reads all Stripe docs as embeddings to answer developer questions inside the docs
  • Sigma lets users ask questions in natural language and the engine writes the SQL
  • An internal governed GPT-4 UI has shareable prompt presets usable by non-engineers
  • Copilot was trialed rigorously, found effective, and rolled out broadly to engineers

“We realized we can have GPT-4 read all of our docs, store them as embeddings, and then answer questions for developers.”

David Singleton · 1:04:00

“you can ask questions in natural language and our engine will actually write the SQL query for you.”

David Singleton · 1:05:00
#ai#llm#gpt-4#developer-tools

Story· 4

Story24:30

The Meticulous Detail That Sold Singleton on Stripe: Error Messages That Link to Docs

Before joining, Singleton played with the product and got stuck integrating the API, but Stripe's error messages linked directly to the docs page that solved the problem. He notes there is actually more code handling those edge cases than in the main flow, and users repeatedly say this detail delights them and speeds adoption.

  • Stripe wired API error messages to link to the exact docs that solve the problem
  • There is more code handling these edge cases than in the main API flow
  • Error messages are a high-stakes moment because a developer is stuck and it matters
  • Users frequently cite this polish as a reason they adopt Stripe faster and keep adopting more products

“we made the error messages coming out of our API linked to the piece of the docs that told you how to solve the problem.”

David Singleton · 25:00

“there's actually more code in the jobs that serve the Stripe API to handle those edge cases than in the actual main flow.”

David Singleton · 27:00
#craft#developer-experience#documentation#api-design
Story38:30

'Walk the Store': Reviewing Product Together as a Whole Company

Singleton describes reviewing products collectively rather than only asynchronously, comparing it to a chef tasting the soup with the kitchen staff or a studio watching movies together. Stripe extends this to 'walk the store,' where critical product flows are examined with the whole company at the weekly Friday Fireside to build shared language and standards.

  • Product reviews are done together, not just as solo async friction logs
  • Analogy: a chef tastes the soup with the kitchen staff; a studio watches movies together
  • 'Walk the store' reviews critical flows with the whole company at Friday Fireside
  • Doing it together teaches the bar for craft and creates shared language

“if you were a chef, you're going to you're going to taste the soup, and you're going to talk to your kitchen staff about like…”

David Singleton · 38:30

“there's something that that that we do occasionally and and I've done it occasionally at Stripe called walk the store, where we'll actually do that…”

David Singleton · 39:00
#ux-review#craft#culture#collaboration
Story46:30

'Engineer-cations': The CTO Clears His Calendar to Ship Real Code

Singleton describes engineer-cations, a portmanteau of engineer and vacation that is not a vacation. He clears three or four days, joins a team with a buddy, and ships a small feature end-to-end to production, keeping a friction log of the developer experience. When he started he had never written a line of Ruby and was scared, but doing it built lasting context and credibility.

  • Clear three to four days, join a team, and take a small feature all the way to production
  • A buddy on the team helps you through the tools and codebase
  • Keep a friction log to write up the developer experience for later prioritization
  • Singleton had never written Ruby before doing this; he advises new eng managers to do one in their first quarter

“it's it's obviously a portmanteau of engineer and vacation, but it's not a vacation.”

David Singleton · 46:30

“When I started, I had never written a line of Ruby in my life.”

David Singleton · 49:00
#leadership#developer-experience#management#getting-in-the-weeds
Story1:12:00

Singleton's 10-Year Sunday-Night Planning Ritual

To keep his time from being controlled by whatever lands in his inbox or calendar, Singleton has run a weekly loop for about ten years. On Sunday afternoons he reads what happened last week, then Sunday evenings writes a list of what would make the coming week a good week, which drives where he spends his time.

  • Left unmanaged, a leader's time gets set randomly by inbox and calendar
  • He has run this Sunday loop for roughly ten years
  • Reads last week on Sunday afternoon, then writes the week's success list Sunday evening
  • The list drives his time allocation, while staying dynamic to surprises

“I make a list of if we got these things done this week, that is a good week.”

David Singleton · 1:12:30
#productivity#leadership#time-management#planning

Q&A· 2

Q&A16:30

Why Stripe Waited Years to Hire Its First Product Manager

Lenny asks how Stripe held off on hiring PMs until ~200 employees. Singleton explains the early team was an engineering team that was extremely product-minded, so every early engineer effectively acted as a PM. He argues the best PMs for developer-focused products are usually technical, often former engineers.

  • Stripe's original team was an engineering team, but every member was product-minded enough to act as a PM
  • The best PMs for developer-focused products are usually very technical, often former engineers
  • Product-minded engineers get to know users deeply and bring those insights into the product loop
  • Stripe now has many PMs; product management is a valuable job family, just added later

“our original team was was really an engineering team. However, they were extremely product-minded.”

David Singleton · 17:00

“The best PMs for developer-focused products, I think, are usually very technical.”

David Singleton · 17:30
#hiring#product-management#engineering-culture#stripe
Q&A1:24:30

Singleton's Favorite Interview Question for Leaders

Singleton shares a leadership interview question that sounds like a softball but is not: which leader they most admire and why. The revealing follow-up asks the candidate to imagine being that admired leader's manager and give the development feedback that would make them more effective, testing their ability to think critically about someone they lionize.

  • Ask which leader the candidate admires most and why, revealing what they value
  • Follow up: imagine you were their manager and give them development feedback
  • The follow-up tests critical thinking about someone they admire
  • Everyone has room to improve, so the answer is telling

“which leader that they've worked with they admire most and why.”

David Singleton · 1:24:30

“imagine you were their manager, tell me the performance review or the development feedback you'd give them to help them be more effective.”

David Singleton · 1:25:00
#hiring#interviewing#leadership#lightning-round

Tool· 2

Tool1:22:00

David Singleton's Most-Recommended Books

In the lightning round, Singleton names the books he recommends most: High Output Management by Andy Grove as his top pick, Build by Tony Fadell for its focus on craft and users, and Scaling People by Claire Hughes Johnson, which references techniques used at Stripe.

  • High Output Management by Andy Grove is his most-recommended book
  • Build by Tony Fadell for practical craft and user thinking
  • Scaling People by Claire Hughes Johnson, which features Stripe techniques

“High Output Management by Andy Grove is definitely the book that I've recommended the most.”

David Singleton · 1:22:00
#books#management#recommendations#lightning-round
Tool1:27:00

The Crying Octopus Button: Stripe's 'Paper Cuts' Feedback Loop

Singleton names the small change with the most impact: a crying-octopus emoji button in every internal developer tool. Engineers click it to type what went wrong, and the developer productivity team reads all of them to prioritize fixes. Stripe calls these 'paper cuts,' and frictionless problem reporting proved very valuable.

  • A crying-octopus button sits in every internal developer tool
  • Clicking it lets an engineer type what went wrong on the spot
  • The developer productivity team reads all reports and prioritizes from them
  • Stripe calls these 'paper cuts'; frictionless reporting was surprisingly valuable

“we put a little button in every single developer tool at Stripe. It is an emoji of an octopus that is crying.”

David Singleton · 1:27:30

“We call those paper cuts.”

David Singleton · 1:27:30
#developer-productivity#feedback#internal-tools#stripe

Takeaway· 2

Takeaway28:30

How Small Checkout Tweaks Compounded Into a 10.5% Revenue Lift

Singleton explains that migrating users from a vanilla self-built checkout to Stripe's payment element or Stripe Checkout raised the average user's revenue by 10.5%. In an industry where even big efforts move conversion by basis points, he stresses that many small, meticulous changes compounding over time produce dramatic impact.

  • Moving users to the payment element or Stripe Checkout increased average revenue by 10.5%
  • Most changes in this industry move conversion only in basis points
  • Stripe scoured checkout flows for broken edges and removed latency and clicks
  • The lift comes from being meticulous at every step, which compounds

“it turns out that it increases the average user's revenue by 10.5%.”

David Singleton · 29:00
#conversion#checkout#craft#metrics
Takeaway1:10:30

Why References Beat the Interview for Hiring Conviction

Singleton stresses how seriously Stripe treats references, especially late in the process. An interview loop gives you maybe 8 hours with a candidate, while people who have worked with them offer thousands of hours of direct experience. For transformative hires, references are often where he gets the best conviction.

  • An interview process is only about 8 hours total with a candidate
  • Former colleagues carry thousands of hours of direct experience with the person
  • Stripe asks smart, specific questions to extract real signal from references
  • References often provide the best conviction on transformative hires

“If you talk to people that actually have worked with them before, you're probably benefiting from thousands of hours of direct experience.”

David Singleton · 1:10:30
#hiring#references#management#recruiting