Karri Saarinen

Co-founder, designer, and CEO of Linear — founding designer at Coinbase and principal designer at Airbnb. Built Linear into what Lenny calls the fastest-growing and most beloved issue tracking tool, with a net negative lifetime burn rate (more cash than total raised). Their core argument: As markets mature, the design bar rises to table stakes — the 100,000th email client has to be pretty good to even be considered. Craft is no longer optional; it is a basic entry requirement. The evidence is specific: Engineer Andreas independently building macOS-style safe zones for sub-menus — dynamically calculated hit targets so users don't miss by a few pixels — without being asked to do so.. Furthermore, linear's approach: ship to internal production in week one, then to opt-in beta customers, then polish for general release.. Linear having a net negative lifetime burn rate — proof that craft can be capital-efficient, not capital-intensive.. In Karri Saarinen's own words: "The more it matters, the more the design matters. Pretty much from the very beginning, you need pretty high level design for people to even pay attention or consider you seriously." (On craft as a rising bar — design quality is now table stakes.)

Built Linear into the most beloved issue tracking tool in the world with no A/B tests and only one PM, while being profitable for 2+ years with net negative lifetime burn rate (more cash than total raised) and only $35K ever spent on marketing. Their core argument: Taste-driven, no A/B tests, no metrics-based goals. Decisions are validated by taste and opinions, with beta testing for feedback -- but data never drives the decision. The evidence is specific: Linear has no A/B tests, one PM (Head of Product), and no metrics-based goals. Furthermore, profitable for 2+ years, $35K total marketing spend, net negative burn rate, only 2 departures ever. Ship features to production in the first week, visible only to internal team and opt-in beta customers. In Karri Saarinen's own words: "We don't do A/B tests. We validate ideas and assumptions that are driven by taste and opinions, rather than the other way around where tests drive decisions. There is no specific engagement or other number we look at. We beta test, see the feedback, iterate, and eventually we have the conviction that the change or feature is as good as it can be at this point and we should release it." (Explaining Linear's decision-making process in the newsletter.)

Founding designer at Coinbase, principal designer at Airbnb; co-founder and CEO of Linear, used by Block, Vercel, Ramp, Retool, Mercury, and thousands of other companies Their core argument: Productivity software should be opinionated by default -- design something for someone rather than everything for everyone. The evidence is specific: Linear engineer Andreas independently built dynamic safe zones for right-click sub-menus, matching Mac OS behavior -- nobody asked him to do it. Furthermore, linear ships features to production early (internal only), then to 1-10 co-development customers, then general release with full polish. In Karri Saarinen's own words: "Productivity software should be, and especially company software should be opinionated. I think that what the productivity software is trying to do is make people productive. And I think what productive means is you actually do something that matters for the company." (Explaining the philosophy behind building opinionated software.)

Karri Saarinen co-founded Linear, which became one of the fastest-growing and most beloved issue tracking tools in the world, building the product with just one PM (as head of product) across approximately 50 employees -- a deliberate structure enabled by hiring engineers for product judgment, not just technical skill. Their core argument: Small, high-caliber teams of engineers and designers can delay the PM hire if you hire for product judgment at every level. Linear has one PM (as head of product), and the secret is that engineers are interviewed not just for engineering skills but for product opinions and judgment. The evidence is specific: Linear at ~50 employees with just one PM serving as head of product. Furthermore, no durable cross-functional teams: teams assemble around a project and disperse once it's done. Engineering candidates are interviewed for product opinions and judgment, not just technical ability. In Karri Saarinen's own words: "You cannot really interview engineers only for the engineering skills. You also have to interview them for the product skills." (On how Linear's hiring bar enables them to operate with minimal PMs.)

Karri came from Airbnb's Chesky-centralized environment and deliberately built Linear the other way. Linear has exactly one PM (the head of product) for the whole company. Engineers and designers do the PM work themselves — scoping, writing specs, running projects — which only works because the hiring bar interrogates product judgment alongside craft skills. His argument is that specialization destroys craft because it turns ICs into executors instead of thinkers. If every person has high craft instincts, you don't need a bottleneck — you just need rituals to keep everyone calibrated. Karri still plays last-line reviewer (he personally found janky animations in Linear's comment threading by clicking around before launch) but the taste check is distributed, not gated. In Karri's own words: "You cannot really interview engineers only for the engineering skills. You also have to interview them for the product skills... We just look for does this person have opinions about products and how they work? Can they form opinions and can they use their own judgment at times?" (Describing how Linear distributes the taste bar through hiring, not gating.)

Karri's contribution to the AI-taste debate is historical rather than AI-specific. His claim, built over years of running Linear, is that taste and quality track the maturity of a medium. When a medium is new, rough work wins because everything is rough. As the medium matures and tools commoditize production, the bar to even be considered rises until 'pretty high level design' becomes table stakes. Linear itself is the evidence: profitable, net-negative lifetime burn, customers like Vercel, Ramp, and Block, and imitators scrambling to copy the aesthetic — all built in a commoditized category by refusing A/B tests and running on taste and opinions. Applied to AI, this is an argument that AI is simply the next wave of production-tool commoditization, and historically those waves make craft a stronger differentiator, not a weaker one. In Karri's own words: "Then, as you build the 100,000 different email clients, any email client now has to be pretty good to be even considered an email client. It's like the bar is so high. I think today it's almost a very basic thing now. Pretty much from the very beginning, you need pretty high level design for people to even pay attention or consider you seriously." (The core structural claim — commoditization raises the craft bar rather than lowering it.)

Linear's model is a deliberate rejection of scaled-org design practice. There is no durable cross-functional team; project teams assemble around a piece of work, ship, then disperse. No company-wide design reviews of everything that ships. Saarinen's causal story: craft emerges when the people building the feature see it all day and have the authority to fix it without going through a review process. The concrete example: an engineer, Andreas, implementing a right-click submenu noticed that most software requires pixel-perfect hovering, so he built dynamic safe zones so users can move diagonally into the submenu — work that no one asked for and no PM would have specced. That's the craft payoff of a small empowered team. Karri is also explicit that heterogeneous quality cultures break craft. In Karri's own words: "When you build a team and you start creating these very specific roles for everything I think that often the PM can be the ones figuring things out and making decisions and guiding the team, but they're not the ones building the feature. They're not there looking at it the whole day... I think a lot of that, this craft for us happens when we give the project team this ownership and the project team is just engineering and design." (The core structural argument: fewer roles, tighter ownership, better craft.)