Lenny's PodcastNan Yu: How Linear ships beloved B2B software at speed
Through week-one V1s shipped first to internal users then waves of beta rings; Linear refuses customization that helps managers and breaks IC workflow.
At a glance
WHAT IT’S REALLY ABOUT
Linear’s playbook: fast iteration, opinionated design, deeply empathetic product discovery
- Lenny interviews Nan Yu, Head of Product at Linear, about how the company builds a beloved, high-velocity B2B product without sacrificing quality. Nan explains why speed and quality are not opposites, describing Linear’s practice of shipping a working version in the first 10% of a project’s timeline and iterating from there. He details how Linear avoids enterprise bloat by refusing features that worsen individual contributor (IC) workflows, instead digging deeply into real user pain and emotional triggers to design native, opinionated solutions. They also cover Nan’s systematized creativity process, the PM’s role as a bridge between building and selling, and his approach to landing PM roles by treating the interview like solving the hiring manager’s real job-to-be-done.
IDEAS WORTH REMEMBERING
5 ideasTreat speed as competence and iteration, not rushing or sloppiness.
Linear rejects the idea that speed inherently lowers quality; instead, they aim to have something functional in the first 10% of the schedule, enabling many iterations and reality checks before launch.
Get a working V1 into real hands extremely early.
Nan pushes teams to produce a rough but usable version in week one, first for internal use, then for concentric rings of beta users, so they can validate core assumptions and avoid investing heavily in unwanted solutions.
Refuse customization that helps managers but harms IC workflows.
Linear has a hard rule: they say no to customization features requested by middle managers for reporting if they degrade IC experience, because such features lead to disengaged users and bad data, and ultimately to bloated, hated software.
Anchor product decisions in specific real users and their emotions.
Rather than aggregating generic “user requests,” Nan ties features to named individuals and digs until he feels the same negative emotion they feel (e.g., embarrassment over missed dates), then designs to eliminate that feeling.
Use extreme designs to expand the solution space and then dial back.
To systematize creativity, Nan deliberately explores the most extreme versions of a solution (e.g., maximum speed vs maximum safety for draft-saving), builds and tests them, and then finds the practical middle that feels obviously right in hindsight.
WORDS WORTH SAVING
5 quotesThere’s not actually a trade-off between speed and quality. People overindex on rushing when what they should index on is being really competent.
— Nan Yu
By the time 10% of the time has passed, you should have something that works and tests a key hypothesis.
— Nan Yu
The stuff we absolutely have to say no to is customization features requested by middle managers to make reporting easier at the cost of making IC workflows worse.
— Nan Yu
My goal is to feel bad in the same way that customers feel bad.
— Nan Yu
The biggest risk is you didn’t see the right choice to begin with. You had three options, and the right one was in a corner you never looked at.
— Nan Yu
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome