Linear’s secret to building beloved B2B products | Nan Yu (Head of Product)
Nan Yu, Head of Product at Linear, shares how to build beloved B2B SaaS products by challenging the speed-quality trade-off, prioritizing ICs, deeply understanding customer emotions, and systemizing creativity. He also offers advice on strategic job searching and effective deadline management.
Deep Dive Analysis
14 Topic Outline
Linear's Success: Why Users Love It
Debunking the Speed vs. Quality Trade-off
Iterating Quickly and Building Workable Solutions
Linear's Strategy for Avoiding Software Bloat
Understanding User Needs Through Specific Use Cases
Extracting Emotional Insights from Customer Calls
Leveraging Emotional Hooks in Product Development
Managing the Product Backlog and Capacity Planning
Systemizing Creativity: Building Extreme Versions
Demo: Iterating on Linear's Draft Saving Feature
B2B Software as a Teacher of Work Processes
The Double Triangle Framework for Product Management
Effective Job-Hunting Strategies for Product Managers
Taking Deadlines Seriously and Cutting Scope
4 Key Concepts
Speed vs. Quality Myth
The idea that speed and quality are at odds is a misconception. True competence and expertise allow individuals and teams to produce high-quality work at a rapid pace, as seen in top performers across various crafts. Speed in this context means quickly iterating and testing hypotheses, not rushing or being sloppy.
Schlep Blindness
This concept describes the tendency for people to become accustomed to tedious or annoying tasks in their daily lives, making them 'blind' to the 'schlep' or effort involved. Product developers can identify opportunities by observing where users feel 'bad' or frustrated, even if the users themselves don't articulate it as a problem to be solved by a tool.
Double Triangle Framework
This framework describes product management as the central connector between two 'triangles' of organizational functions. One triangle is the 'building' side (engineering, product, design), and the other is the 'selling' side (sales, marketing, product management). The PM's role is to bridge commercial motivations with technical possibilities, ensuring what is built aligns with company goals and market needs.
B2B Software as Teacher
Adopting B2B software is not just about solving a specific problem; it's also about adopting a new way of working or a set of best practices. Tools often embed workflows and processes, effectively teaching organizations how they 'ought to be doing' certain tasks, thereby raising the baseline competency within the organization.
6 Questions Answered
Teams can build quickly and maintain quality by focusing on competence, aiming to have a workable solution that tests key hypotheses within the first 10% of the allotted time, and then iterating rapidly based on feedback, rather than striving for perfection in the initial version.
Linear avoids bloat by strictly saying no to customization features requested by middle managers primarily for reporting, especially if they worsen the workflow for individual contributors (ICs). They prioritize features that make ICs more effective and engaged, believing that better IC experience leads to more accurate data and overall team effectiveness.
Product managers should dig beyond stated requests to understand the underlying emotional 'bad feeling' or frustration motivating the customer's need. By asking probing questions and empathizing with the customer's negative experiences, PMs can uncover the true problem to solve, rather than just building what is explicitly asked for.
A systematic approach to creativity involves exploring extreme versions of potential solutions. By asking 'how extreme can you take it?' and building the most outrageous or luxurious version, teams can break free from perceived constraints, expand the possibility space, and learn valuable lessons that inform the development of a balanced, effective solution.
Product managers should treat the job interview process as a discovery exercise to identify the hiring manager's 'burning problem' or 'job to be done'. By making a strong case that they are the specific solution to that problem, candidates can differentiate themselves from others who merely highlight their general skills.
Companies should set deadlines sparingly, typically for external marketing or launch events. When a deadline is set, it must be treated as a 'P zero' priority, meaning all other work is secondary, and the PM's role is to aggressively cut scope to ensure a shippable product can be delivered by that date, even if it's not the full desired feature set.
10 Actionable Insights
1. Prioritize ICs Over Manager Reporting
Absolutely say no to customization features requested by middle managers for easier reporting if they worsen IC workflows, as this leads to bloated software and disengaged users. Prioritize the individual contributor’s experience to ensure product adoption and data accuracy.
2. Embrace Speed for Quality
Reject the notion of a trade-off between speed and quality by focusing on competence and rapid iteration. Aim to have a workable solution that tests key hypotheses within 10% of the allotted time, allowing for early learning and adjustments.
3. Uncover User’s Emotional ‘Bad Feelings’
When talking to customers, dig beyond surface-level requests to understand the underlying emotional ‘bad feeling’ motivating their needs. This deeper empathy helps identify core problems and build solutions that truly alleviate user pain.
4. Systemize Creativity with Extreme Thinking
To generate non-obvious solutions, explore the most outrageous or ‘11-star’ versions of a product idea, disregarding initial constraints like cost or practicality. This expands the possibility space and helps discover innovative choices.
5. Commit to Deadlines as P0 Problems
Limit the number of deadlines, but when committed, treat them as P0 problems where all other work is secondary. As a PM, aggressively cut scope to ensure a shippable product is ready for a go/no-go decision, especially for external marketing launches.
6. Integrate PM with Go-to-Market
View product management as a go-to-market discipline, fostering deep collaboration between PMs, sales, and marketing. PMs should originate product messaging and language, leveraging their deep customer understanding to ensure authentic and effective communication.
7. Recognize Software Teaches How to Work
Understand that adopting B2B software isn’t just solving a problem; it’s also adopting a new way of working and a baseline of competency. Choose tools thoughtfully, recognizing they will shape internal processes and practices.
8. Develop a Dynamic Product Backlog
Maintain a backlog of 20-30 product opportunities, continuously accumulating understanding and re-evaluating conviction without immediately building. Focus on defining how much of a problem to take on, rather than solving the entire problem.
9. Strategic Job Search: Solve Their Problem
For job interviews, identify the hiring manager’s ‘burning problem’ or ‘job to be done’ by asking specific questions like their OKRs. Position yourself as the unique solution to that problem, acting as if you already work there.
10. Apply ‘Too Much Minus One’ Principle
To find the optimal amount or solution, deliberately test the extreme (’too much’) to understand its limits. The ideal is often ’too much minus one,’ helping to pinpoint the right balance after exploring the boundaries.
5 Key Quotes
My goal is to feel bad in the same way that customers feel bad.
Nan Yu
I increasingly believe that good, cheap, fast, choose to maxim as devious misinformation spread by the slow. In my experience, slow and expensive usually go together.
Patrick Collison
The biggest risk is you didn't see the right choice to begin with. You have these three choices and like none of them were right. It's this fourth one that was like over in this corner. But you didn't look at that corner. So you never found it.
Nan Yu
The correct amount is too much minus one.
Nan Yu
If you miss one of the opportunities, you don't get it back again. You can't like time travel back and say like, okay, actually let's redo first quarter and like say this message that we wish we, we could have gotten out into the, into the field.
Nan Yu
4 Protocols
Rapid Iteration and Feedback Loop for New Features
Nan Yu- Develop a workable solution that tests a key hypothesis within the first 10% of the allocated time for a feature.
- Release this early version to internal users for feedback and validation.
- If satisfactory, release to a small group of beta customers for early access and feedback, ensuring data integrity and basic quality.
- Gradually expand to additional beta audiences.
- Release the final, refined feature to General Availability (GA) for all users.
Systemized Creativity for Product Design
Nan Yu- Identify a problem or solution to explore.
- Ask: 'How extreme can you take it?' along a specific trait (e.g., fastest, safest, most luxurious).
- Build or conceptualize this 'most outrageous' extreme version, disregarding initial constraints like cost or practicality.
- Test or experience this extreme version (e.g., internally or with a small group).
- Learn from the experience of the extreme version to understand the boundaries of the possibility space.
- Repeat with another extreme (e.g., the opposite extreme) to further explore the spectrum.
- Find a balanced solution that incorporates learnings from the extreme explorations.
Strategic Job Hunting for Product Managers
Nan Yu- Adopt a 'discovery hat' mindset during the interview process, aiming to uncover the hiring manager's specific 'burning problem' or 'job to be done'.
- Act as if you already work at the company, asking specific questions like 'What are your OKRs this quarter?' and 'How can someone help you achieve those?'
- Seek to connect with engineers or other team members working on the problem area to gather more intelligence and demonstrate deep engagement.
- Formulate your pitch to clearly position yourself as the direct solution to the identified problem, making your hiring a binary choice between solving the problem or not.
Managing Product Deadlines
Nan Yu- Set deadlines sparingly, primarily for external marketing or launch-related events.
- When a deadline is set, treat it as a P-zero priority, ensuring no team members are pulled onto other tasks.
- As a PM, aggressively cut scope to ensure a workable, shippable product can be delivered by the deadline.
- Commit to the process from the beginning by building and iterating very fast, allowing the team to make a go/no-go decision on a functional product, even if it lacks some desired features.