On Product Philosophy and Strategy

  1. Speed and quality are not a trade-off. Yu explains that for experts, speed is a result of competence, not of rushing or cutting corners. Skilled teams move faster because they have mastered their craft. [Lenny's Podcast, 1, 5, 12]
  2. Avoid software bloat by saying no to certain feature requests. Linear is strict about not adding customization features, like required fields or multiple assignees, that are often requested by managers but could worsen the workflow for individual contributors. [The Glimpse, 1, 10]
  3. Focus on the "main thing." Startups should identify the one thing their product needs to be great at and over-provision resources to it, rather than spreading attention evenly across many features. [LaunchPod, 4, 17]
  4. Embrace being opinionated. Building a product with a strong point of view is essential. Yu states it's better to be decisively wrong and pivot than to be cautiously mediocre. [LaunchPod, 4, 17]
  5. When adopting a new tool, you're adopting a new way of working. Choose tools that align with the practices you want to cultivate within your team, as software comes with embedded best practices. [Lenny's Podcast, 1, 8]
  6. The goal is for users to focus on their jobs, not the tool. A significant part of Linear's philosophy is to minimize the "meta work" so users can concentrate on their actual expertise. [The Glimpse, 10]
  7. Ditch indirectness, including traditional user stories. Yu advocates for clear and direct language in tasks, arguing that "As a user, I want X" can obscure the actual need and is an outdated formalism. [The Linear Method: Deep Dive, 19]
  8. Product management is both a selling and a building function. The role involves understanding the customer's worldview to convince them there is a better way to work and then providing the tools to do so. [LaunchPod, 4]
  9. Be intentional with your org design, just as you are with your product. Founders should follow their intuition and design a team structure that directly supports the product's goals, rather than copying a popular model like Spotify's. [First Round Review, 11, 18]
  10. Good taste is a differentiator, especially in B2B. In a crowded market, design and user experience become critical for standing out and creating a product that users love. [The Linear Method: Deep Dive, 14]

On Team and Culture

  1. Empower engineers and designers to be de-facto product managers. An anti-pattern many companies fall into is having engineers and designers who rely entirely on PMs for product decisions, which can lead to disengagement. [Creator Economy, 2, 17]
  2. Fluid teams over rigid structures. Linear organizes its teams into flexible groups to solve specific problems, avoiding the trap of "shipping the org chart." [Creator Economy, 2]
  3. Hire using paid work trials. This method provides a much clearer sense of a candidate's problem-solving skills and how they collaborate with the team compared to traditional interviews. [Creator Economy, 2, 9]
  4. A quiet Slack can be a sign of an effective, independent team. In a remote environment, self-motivation and agency are crucial, and constant communication isn't always a sign of productivity. [Creator Economy, 2]
  5. Your job title is less important than your impact. Yu moved from a VP of Product role to an individual contributor PM at Linear, emphasizing that the focus should be on making the right product decisions, not the number of direct reports. [Creator Economy, 2]
  6. A small number of problems should be the focus at any given time. Spreading efforts across too many areas is a recipe for going nowhere fast. [Supra Insider, 9]
  7. The feeling of being fast and focused is a precious cultural asset. Many companies lose this as they grow, and it's worth protecting intentionally. [LaunchPod, 17]
  8. Avoid learned helplessness in engineering teams. Over-staffing with PMs can lead to engineers checking out from understanding the customer and the product, a dynamic that is very difficult to reverse. [LaunchPod, 4, 17]
  9. Run marathons, not sprints. Sustainable momentum beats endless "sprints." The goal is to find a comfortable pace that the team can maintain for the long term. [How Linear Built a $1.25B Unicorn, 22]
  10. Integrate quality into every step. At Linear, bugs are either critical or high-priority because even a small bug, seen repeatedly, signals a lack of care to the customer. A feature isn't done until it meets the quality bar. [How Linear Built a $1.25B Unicorn, 22]

On Product Development and Execution

  1. Build and iterate quickly from the start. Within the first 10% of a project's timeline, you should have a working version that tests a key hypothesis, allowing for early feedback and validation. [Lenny's Podcast, 1, 5, 16]
  2. Use deadlines sparingly but take them extremely seriously. When a deadline is set, it becomes the absolute priority, and scope should be cut aggressively to meet it. [Lenny's Podcast, 1, 8]
  3. Don't waste time on detailed estimates; focus on shipping. The market will provide fast feedback on whether you're on the right track. Unshipped code is a form of debt. [Lenny's Podcast, 1, 19]
  4. Use your own product as prescribed. Avoid contorting your tool to fit every use case, as this can blind you to its limitations and the pain points of real users. [Supra Insider, 9]
  5. The "double triangle" framework for creativity. To find non-obvious solutions, explore the extremes of a problem (e.g., the fastest version vs. the safest version) to break out of conventional thinking, then converge on a solution. [Lenny's Podcast, 1, 3, 8]
  6. Launch and keep launching. Continuous delivery and iteration are core to the Linear Method, ensuring the product evolves based on real user feedback. [Linear Method, 6]
  7. Scope issues to be as small as possible. This allows the team to ship constantly, which provides a continuous sense of reward, immediate user feedback, and tangible progress. [How Linear Built a $1.25B Unicorn, 15, 22]
  8. Minimize friction to restore the joy in software development. The goal is to get out of the way so that developers can focus on the inherently fun and interesting work of creating software. [YouTube - Lenny's Podcast, 5]
  9. Write issues, not user stories. Focus on clear, direct tasks rather than the "As a user..." format to avoid ambiguity. [Linear Method, 6]
  10. Automate the administrative burden. A tool should work for you, not the other way around. Linear aims to remove or automate "work around work" so teams can focus on what matters. [Linear Method, 7, 13]

On Understanding Users

  1. The goal of customer calls is to feel what the customer feels. Dig deep in customer conversations to understand the underlying emotions they want to avoid, which helps in creating strong emotional hooks for the product. [Lenny's Podcast, 1, 5, 12]
  2. Look beyond surface-level feature requests. Understand the deeper needs and contexts of your users to build truly valuable solutions. [Creator Economy, 2]
  3. Connect with customer support and sales teams. They are on the front lines and have invaluable insights into what customers want and how they feel about the product. [Creator Economy, 2]
  4. Centralize feature requests for visibility. Anyone in the company should be able to see what customers are asking for to spot trends and inform development. [Linear Method, 7]
  5. Close the loop with users. When a requested feature is shipped, letting the user know is a delightful experience that builds loyalty. [Creator Economy, 2]
  6. Understand who is making the feature request. The needs of a manager (e.g., for reporting) may differ significantly from those of an individual contributor (e.g., for productivity), and Linear prioritizes the latter. [Lenny's Podcast, 1, 3]
  7. Your users aren't a feature checklist. Listen intently to feedback, but don't take every request literally. The goal is to understand core frustrations, not just to add features that could lead to bloat. [How Linear Built a $1.25B Unicorn, 22]
  8. Build with users, not just for them. Involve users early in the development process to gather feedback and iterate. [Linear Method, 6, 15]
  9. Solve the problem, don't just build the feature. Use customer feedback as a research library to understand the underlying problem before jumping to a solution. [Top Priority Newsletter, 15]
  10. AI can help in understanding user feedback. Nan Yu notes that as things move quickly, AI can be applied to tasks like analyzing and de-duplicating the large volume of user requests. [The Glimpse, 10]

On Career and Personal Growth

  1. Treat job hunting like a product discovery exercise. Understand the hiring manager's key problems and position yourself as the clear solution. [Lenny's Podcast, 1, 8]
  2. Get to know and stay in touch with good people. This was key to how Nan Yu joined Linear, having connected with the founders years before formally working with them. [Creator Economy, 2]
  3. Have conviction in your decisions. As a leader, you own the choices you make. It's better to be decisively wrong and learn from it than to be indecisive and wait. [LaunchPod, 4, 17]
  4. The "heirloom tomato" org chart. Instead of a perfectly symmetrical structure, a startup's organization should reflect the product's priorities, with the most critical area receiving the most resources. [First Round Review, 11, 18]
  5. Don't be afraid to take a step back in title for the right opportunity. Focus on the impact you can have and the quality of the team, not just the hierarchy. [Creator Economy, 2]
  6. Understand the context behind management wisdom. A nugget of wisdom from one context (like Spotify's team structure) may not apply to yours. [First Round Review, 11]
  7. The era of the PM-as-builder is here. Product managers who can go from tasks to actual changes in the app will have an advantage. [The Linear Method: Deep Dive, 19]
  8. Continuously re-evaluate your approach. Every day presents an opportunity to think about your product differently. [Reforge, 20]
  9. Focus on the "main thing" in your career. Just as a startup should focus on its core strength, individuals should identify where they can over-deliver and make the biggest impact. [LaunchPod, 17]
  10. My job is to connect different teams to each other. Yu sees his primary responsibility as a product leader as ensuring seamless communication and collaboration across the organization. [The Glimpse, 10]

Learn more: