Speed & Quality:
The False Tradeoff

Nan Yu

Head of Product, Linear

2025

The Insight

Competence Looks Like Speed

"You can basically tell how good the output is going to be of their work product by how fast they're going. If they're going really fast and they're not being sloppy, it's because this is second nature to them."

Speed and quality are correlated, not opposed
Experts move fast because excellence is second nature
The only way to iterate is by moving quickly
More iterations = better product

Framework

The 10% Rule: Release Early, Test Often

110%Working
Internal DemoBeta
PartnersGA
Release

10%

Time to Working Version

∞

Feedback Loops Unlocked

Week 1 (10%): Ship something that works and tests your hypothesis internally
Don't wait for 80% done to validate; you're too invested by then
Use internal users first (Linear uses its own product daily)
Graduated circles: internal → beta partners → wider beta → GA
First version doesn't need to be perfect, just functional

The Core ShiftNo expectation the first version is great. It's your best guess. Some need minor tweaks, some need major rethinking. But you know fast.

Product Philosophy

Protect the IC. Say No to Middle Managers.

The misaligned incentive: Managers want detailed reporting; ICs want simple workflows
What Linear refuses: Customization features for middle management at the cost of IC experience
The bloat trap: One "yes" to reporting customization = cascading feature sprawl that kills engineering joy
The lever: If ICs disengage because tools are painful, no amount of manager reporting matters

The False Trade-off

Sales pressures you to add a feature for the buyer. But the IC never has to use the tool. They choose. One bad workflow = disengagement.

The Real Win-Win

Find where incentives are misaligned. Then solve the actual underlying problem instead of papering over it with features.

Playbook

Ask Like You're Digging for Emotion

Find the specific person with the problem (not a generalized ask)
Understand what emotion they're trying to avoid or achieve
Ask follow-up questions until you feel the same frustration they do
Your mental model of the user is your most valuable asset

Nan's customer talk philosophy"My goal is to feel bad in the same way that customers feel bad." Only then do you truly understand what to build.

The Creative System

How to Think Beyond Your Constraints

✗Speed means sloppy & rushedINSTEAD →✓ Speed is a signal of competence & mastery. The fast ones are the good ones.

✗Wait until 80% to test your ideaINSTEAD →✓ Release at 10%. Test immediately. You're too committed at 80%.

✗A bigger feature set wins dealsINSTEAD →✓ A joyful IC experience wins retention. Protect the user over the buyer.

✗Ask users what they want to buildINSTEAD →✓ Ask users what emotion they're avoiding. Build for that emotion.

Based on Nan Yu's episode on Lenny's Podcast. All ideas on this page are from the episode.Watch on YouTube Follow @thenanyu on X

GO DEEPER IN THE EPISODE

04:54 Survey insights: Linear vs. Jira 07:51 The speed vs. quality myth 09:24 Building and iterating quickly 15:31 Avoiding bloat in enterprise software 23:57 Understanding user needs deeply 30:09 How to approach customer calls 34:10 Creating strong emotional hooks 40:31 Managing the product backlog 44:46 Systemizing creativity 48:16 Demo: Saving drafts in Linear 51:38 Breaking constraints and building at extremes 54:15 Adopting new tools 58:22 The “double triangle” framework for product management 01:04:23 Effective job-hunting strategies for PMs 01:09:15 Thoughts on deadlines 01:14:15 Lightning round

Every sketch here began as a transcript.

Send us yours and we’ll draw it. $1 a transcript.

Sketch mine →

0:00