Linear’s secret to building beloved B2B products | Nan Yu (Head of Product)
Executive Summary
Lenny's Podcast episode, sponsored by Sinch and Paragon, in which Lenny Rachitsky talks with Nan Yu, head of product at Linear, about how Linear builds one of the most beloved B2B products in software. Yu rejects the supposed trade-off between speed and quality: teams that believe in it are over-indexing on rushing and sloppiness, when the real index is competence - watch people at the pinnacle of their craft and speed predicts quality. His operating rule is the ten-percent test: by the time a tenth of any project's time budget has passed, something should exist that works and tests a key hypothesis internally. He explains what Linear refuses to build - exactly the features that create the bloat making ICs hate their lives - and his customer-call method: keep digging until you feel bad the same way the customer feels bad, then design against that emotion. PARTIAL COVERAGE: this summary highlights the operating philosophy; his creativity system and career advice segments are not covered. These are Yu's own methods and views, not independently verified.
Key Takeaways
No speed-quality trade-off
He calls the trade-off a red flag: it usually means the team is rushing, not moving fast.
Competence is the index
At the pinnacle of any craft, speed of work predicts quality of output.
The ten-percent rule
After a tenth of the time budget, have something working that tests a key hypothesis.
Say no to bloat
Linear vetoes exactly the feature requests that make software hated by the people who use it.
Feel the customer's bad
His call method: dig until you feel bad the way the customer does, then design away that emotion.
Built against hatred
Linear began when its founder watched Coinbase colleagues hate their day-to-day tools.
Love as strategy
In Lenny's survey, the tool people most wished they could switch to was Linear over Jira.
The Conversation Breakdown
No speed-quality trade-off
⏱ Untimed topicHe calls the trade-off a red flag: it usually means the team is rushing, not moving fast.
Competence is the index
⏱ Untimed topicAt the pinnacle of any craft, speed of work predicts quality of output.
The ten-percent rule
⏱ Untimed topicAfter a tenth of the time budget, have something working that tests a key hypothesis.
Say no to bloat
⏱ Untimed topicLinear vetoes exactly the feature requests that make software hated by the people who use it.
Feel the customer's bad
⏱ Untimed topicHis call method: dig until you feel bad the way the customer does, then design away that emotion.
Built against hatred
⏱ Untimed topicLinear began when its founder watched Coinbase colleagues hate their day-to-day tools.
Love as strategy
⏱ Untimed topicIn Lenny's survey, the tool people most wished they could switch to was Linear over Jira.
Core Frameworks & Ideas
Ten-percent checkpoint - Yu's pacing rule
Any project must produce a working hypothesis test by a tenth of its budget.
Emotion-first discovery - his customer method
Find the feeling the customer wants to avoid, then build the avoidance.
Bloat veto - Linear's scope guard
Refuse the features that add bulk without love, even when requested.
Actionable Next Steps
- ✓Check your current project against the ten-percent rule today.
- ✓On your next customer call, ask one more why than feels polite.
- ✓List the last five feature requests you should have refused.
- ✓Time how long your own product's core flow takes versus the competitor's.
Notable Quotes
“there's not actually a trade-off between speed and quality”
“My goal is to feel bad in the same way that customers feel bad”
“What they should be indexing on is being really competent”
The One Thing to Remember
Nan Yu's Linear doctrine: speed and quality don't trade off when the team is competent - budget ten percent for a working hypothesis, and say no to bloat.