Jan 30, 2025 · 1h 21m · lennys-podcast
Linear’s secret to building beloved B2B products | Nan Yu (Head of Product)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, Lenny Rachitsky speaks with Nan Yu, Head of Product at Linear, about building beloved B2B tools by debunking speed-versus-quality trade-offs, defending individual contributor workflows against enterprise bloat, and applying extreme prototyping.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 34.8% of the talking time here. How this is scored →
Lenny as informed peer 3.6 Guest teaching 3.4 Guest disagreement 0.9 Lenny pushing back 0.2
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 16:35 Hard rejection of middle-management feature bloat
Nan forcefully rejects the standard enterprise playbook of accommodating middle-management reporting requests, explaining that such customizations inevitably ruin data quality and make individual contributors miserable.
Hardest push from Lenny ▶ 1:13:00 Host presses on estimation versus scope reductionLenny pushes back on Nan's strict deadline philosophy, questioning whether engineering teams shouldn't invest more in upfront estimation and de-risking rather than solely relying on aggressive scope cuts.
Biggest teaching moment ▶ 8:20 Reframing speed as competence rather than rushingNan dismantles the common industry assumption of a speed-versus-quality trade-off, demonstrating to Lenny that true velocity is a direct byproduct of deep competence and rapid iterative cycles.
Lenny holds their own ▶ 11:55 Lenny cites Patrick Collison and Magnus Carlsen on speedLenny reinforces and elevates Nan's thesis by citing Patrick Collison's insights on slow projects being deviously expensive and drawing an apt parallel to Magnus Carlsen dominating speed chess.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Preview and Key Insights from Nan Yu | 0 | 0 | 0 | 0 | Introductory monologue and teaser clip compilation highlighting key themes from the episode. No live host-guest interaction occurs. | |
| Sponsor Messages: Cinch and Paragon | 0 | 0 | 0 | 0 | Standard sponsor break with ad reads for Cinch and Paragon. Pure host monologue. | |
| The Origin of Linear and Cult Product-Market Fit | 4 | 2 | 0 | 0 | Lenny opens by sharing proprietary stack survey data showing Linear as the top tool users wish to switch to. Nan explains the founding motivation behind Linear to eliminate daily software friction. | |
| Debunking the Speed Versus Quality Trade-Off | 5 | 4 | 2 | 1 | Nan rejects the conventional speed-quality trade-off, arguing speed directly reflects competence. Lenny enhances the discussion by citing Patrick Collison's perspective and Magnus Carlsen's blitz chess mastery. | |
| Rapid Prototyping and Concentric Feedback Loops | 4 | 4 | 0 | 0 | Nan outlines Linear's rule of having a workable test version within the first 10% of a time budget and expanding via concentric user circles. Lenny neatly synthesizes the core principle of early hypothesis validation. | |
| Resisting Feature Bloat and Defending the IC Experience | 3 | 5 | 3 | 1 | Lenny raises the concern of inevitable enterprise feature bloat. Nan forcefully argues against middle-management reporting customization, demonstrating how mandatory dropdowns corrupt data and alienate individual contributors. | |
| Enterprise Expansion and Handling Customer Rejections | 5 | 3 | 1 | 1 | Lenny connects Linear's upmarket enterprise trajectory to Geoffrey Moore's 'Crossing the Chasm' framework. Nan explains that enterprise customer rejections often just mean 'not right now.' | |
| Annealing Features and Grounding Roadmaps in Specific Users | 4 | 4 | 1 | 0 | Nan explains the concept of 'annealing' features in production and anchoring design on specific, named users rather than abstract personas. Lenny draws a parallel to his own newsletter writing strategy. | |
| Case Study: Customer Requests and Emotional Discovery Calls | 4 | 5 | 1 | 0 | Nan shares how Linear transformed custom field demands into automated customer requests by uncovering underlying emotional pain on calls. Lenny praises this definition of product empathy. | |
| Uncovering Emotional Hooks and Overcoming Schlep Blindness | 3 | 5 | 1 | 0 | Nan discusses finding product opportunities through Paul Graham's concept of 'schlep blindness' and illustrates it with Linear's automated triage feature. Lenny actively tracks the tactical mechanisms. | |
| Sponsor Message: Wix Studio | 5 | 3 | 1 | 0 | Following an ad read for Wix Studio, Lenny synthesizes four core Linear tenets and references Patrick Collison's mental model framework. Nan nuances the recap by explaining how to navigate misaligned user incentives. | |
| A Systemized Process for Creative Product Exploration | 4 | 4 | 1 | 0 | Nan details a creative framework of designing extreme, outrageous versions of a feature to break free from hidden constraints. Lenny references Airbnb's 11-star experience concept. | |
| Live Demonstration: Designing Issue Drafts at Linear | 4 | 4 | 0 | 0 | Nan shares his screen to demonstrate how Linear designed issue drafting by testing two opposite extremes (pure speed vs. full auto-save). Lenny validates the workflow and connects it to working backwards. | |
| B2B Software as Encoded Best Practice | 4 | 4 | 1 | 0 | Nan explains that adopting B2B software is fundamentally about adopting codified operational best practices. Lenny ties this to the Linear Method and opinionated software architectures. | |
| The Double Triangle: Bridging Builders and Sellers | 5 | 4 | 0 | 0 | Nan introduces the 'Double Triangle' model where product managers bridge builders and sellers. Lenny connects this to Brian Chesky's overhaul of PM into product marketing at Airbnb and Apple. | |
| Career Strategy: Interviewing by Solving Real Problems | 3 | 4 | 1 | 0 | Nan shares career advice on interviewing by treating the hiring manager as a discovery customer and diagnosing their burning problem. Lenny underscores the tactical effectiveness of this approach. | |
| Managing Deadlines Through Ruthless Scope Cutting | 4 | 5 | 3 | 1 | Nan offers a contrarian view on deadlines, arguing against upfront estimation in favor of ruthless scope cutting and early working builds. Lenny pushes on managing stress and estimation alternatives. | |
| Lightning Round: Books, Culture, and Everyday Design | 4 | 2 | 0 | 0 | In the lightning round, Nan discusses Norman's Design of Everyday Things, Micron pens, his motto 'too much minus one,' and the accidental creation of Everlane's box-cut tee. Lenny contributes Elon Musk's scope-cutting heuristic. |
Statements from this episode (24)
Lenny Rachitsky: Linear is the top tool users want instead of Jira
“And one of the questions asked was, what tool do you wish you could switch to if your IT department allowed you to? The number one answer by far is, people want to switch from JIRA to linear.”
Nan Yu: High execution speed indicates craft mastery rather than sloppiness
“When they think about speed, the thing they over-index on is, is like rushing or being sloppy, and what they should be indexing on is being really competent. Or being like an expert. So if you look at if you look at people who are like at the pinnacle of their…”
Product teams should build workable prototypes within 10% of their time budgets
“Speed, what it really looks like is, you know, you have some rough time budget for how long you think something's gonna take, and by the time 10% of it has passed, you have a workable solution, right? It's not like, oh, at the halfway point, we have something …”
Linear tests every feature through tiered beta rings before full release
“We have a sort of gradually increasing sort of circle of users that use every single feature. So by the time it hits GA, by the time it gets released, it's been used by a lot of different users to that point, right? So the first circle is just internal users. …”
Linear rejects middle-manager reporting features that worsen IC workflows
“It's customization features requested by middle managers in order to make reporting a little bit easier. At the cost of making IC workflows worse, right? Like, it's like, if it fits that description, we're just saying no. There's no debate because we've alread…”
Management reporting features degrade individual contributor compliance and data quality
“The moment you start going down this path and you make you make the IC user experience worse, they're just going to disengage. Right. No one has to do this. Like if I'm an engineer, I get paid to write code. My performance review is based on my like code contr…”
Enterprise buyers can be convinced to drop software bloat requests
“What buyers care about is, is this going to make their team more effective, right? That's the reason that they're making this buying decision in the first place is that they're like, well, you know, the current situation we're in, and especially with larger co…”
Yu: Linear's enterprise growth is outpacing other customer segments
“Growth in enterprise has been, you know, leading the other segments.”
Linear grounds product debates in specific, contactable users rather than hypothetical personas
“Not, not a hypothetical person, right? Not one that you made up, like, you know, Alice, Bob or whatever. It's like, no, I like, here's the first name, last name, here's their email. You can ask them. And I think that being able to tie it all the way back to re…”
Flawed product assumptions do not require high feedback volume to fix
“And if you didn't, then it's like, that's the part where you don't actually need that many. Pieces of feedback against it, right? It's not really a volume thing. It's like, did we think about this right or wrong there?”
Standard analytical PM frameworks miss the emotional pain driving customer requests
“And my goal is to feel bad in the same way that customers feel bad. Right. They come to us with a request. Hey, we want X. And it's like, there's something motivating it. And it's not, you can do the normal analytical thing and be like, ask five Y's and like, …”
Nan Yu: Flexible project target dates prevent false precision and miscommunication
“The thing that we did specifically to solve this was we, you know, on projects in linear, you can just specify of target date at whatever level of granularity you want. Right. You can say it's a December project. You can say it's a Q four project. You can say …”
Competitive software markets have already exhausted standard 'jobs to be done' opportunities
“And I think the more competitive your industry is, the more the sort of like low hang goal oriented stuff is, is already picked, right? Because every PM from every one of these companies has been asking like, well, like, you know, like, what's, what's your goa…”
Linear keeps 20 to 30 unready product opportunities in backlog
“We, at any given moment, we have Probably like 20 or 30 like opportunities that we could possibly explore, right? Just product opportunities, right? Like problems to solve areas to, you know, to kind of improve for our users, but they're not like ready yet, ri…”
Nan Yu: All existing engineering capacity planning tools are bad except spreadsheets
“All the solutions out there are bad, right? Like the best solution is a very, very custom spreadsheet that someone would make.”
Yu: Rapidly building extreme product versions reveals the right solution
“You actually build it, right? You can think of a very extreme version of a product. It's like, Hey, like let's actually for the first version, you know, we talked about like the first version, you know, it's not really the right answer. Sometimes, you know, it…”
Adopting B2B software means adopting its underlying operational practices
“So when you adopt that tool, you're not just adopting, like, the actual software. You're adopting the idea that this is a practice that you ought to be doing in the first place.”
Yu: Linear builds features by encoding consensus practices of top teams
“What we try to do is find where there's actual consensus, right? Amongst a lot of different high performing teams. And then we can, you know, take those practices and say like, okay, for a team, That isn't, you know, already practicing this. Can we give them a…”
Linear embeds a full-time product marketer directly within its PM team
“On the, on our PM team, we actually have a full-time product marketer, right? And her job is to like, you know, like tactically it's like all the change logs come from her. All the release notes. Right. And also like the, you know, she's always crafting the la…”
Product managers typically underperform by neglecting sales and marketing collaboration
“If you're leaving something on the table, right, in terms of like the kind of impact that you are having at your job, that's probably the thing that you're leaving on the table. You're probably already doing a good job of, you know, collaborating with engineer…”
Treat PM interviews as customer discovery to solve the hiring manager's problem
“Everyone who's hiring PMs, just like when they're hiring execs, they're kind of hoping that they bring them on to solve some burning problem that they have. And so it's your job when you're in the interview process to figure out what that burning problem is. R…”
Software teams should set few deadlines but treat each as absolute P0
“The only way to make deadlines real is to take them so seriously that they are basically like a P zero problem. And like everything else has to not matter in comparison to the deadline, because that that's the only way you're going to be able to signal to the …”
Linear does almost no project time estimation to hit engineering deadlines
“We do almost no estimating in order to hit deadlines. What we do, right, is we ship as early as we can.”
Nan Yu: The optimal amount of anything is 'too much minus one'
“The correct amount is too much minus one. And I think this like kind of ties into like the try the extreme version of it of a thing where I don't know, like a stupid example, like how much pizza do you want to eat? It's like, well, five slices was too many. I …”