Inside Linear: How Craft, Focus, and Small Teams Build Category-Defining Products

I’ve long believed that craft and focus are the two most reliable levers in product management, and listening to Karri Saarinen articulate how those principles shaped Linear reaffirmed why they still win. Karri is the co-founder and CEO of Linear, the project management tool built for high-performance software teams. Since its founding in 2019, Linear has achieved a valuation of $1.25B as of 10th June 2025 and now counts companies like OpenAI, Ramp and Vercel as customers. Before founding Linear, Karri led design at Airbnb and Coinbase, and previously co-founded Kippt, a bookmarking tool acquired by Coinbase. From the opening moments (1:37), his childhood love for computers and design felt familiar. Many of us who lead product today started by tinkering—not for a resume line, but out of curiosity. That early bias toward making things, paired with taste, often becomes the quiet engine behind strong product discovery and product-market fit lessons. At (6:54), the story of founding Kippt and the lessons from a failed bookmarking startup reminded me how much scar tissue can accelerate good judgment. Failure clarified what really matters: build for a specific user, ship faster than your uncertainty, and let the market teach you. The thread continues at (13:14) with lessons from a serial entrepreneur—how pattern recognition, not stubbornness, is what you carry forward. The segment at (19:32) hits a nerve for anyone scaling: why teams shouldn’t grow too quickly. I’ve seen small, senior teams accomplish in weeks what larger groups struggle to deliver in quarters. Velocity isn’t headcount; it’s clarity, trust, and an obsession with quality. Smaller teams keep craft close to the metal and reduce coordination tax. At (25: 03), Linear’s early beginnings emphasize how tight validation loops shape a product. Early validation strategies used to shape the product weren’t about chasing breadth—they were about earning depth with a narrowly defined customer. It’s the purest form of product discovery, and it sets the foundation for everything that follows. The conversation at (36:55) on the unexpected power of intuition resonated with how I coach teams: treat intuition as a hypothesis generator, then use data to reduce risk. It’s not intuition versus evidence; it’s intuition prioritized, evidence instrumented. That’s also how outcomes vs output OKRs stay honest—by measuring what matters without drowning product sense in dashboards. Linear’s unusual approach to user growth (42:41) rejects growth theater in favor of signal-rich adoption. Rather than boil the ocean with generic funnels, they doubled down on the right users, in the right sequence. That ties directly to (57:30) and the power of extreme focus, and the reminder at (59:18) to Design “something for someone”. It’s a crisp antidote to generic, over-configurable tools that try to be everything to everyone. If you’re curious what shaped Linear’s early product roadmap (47:29), the answer is principled constraint: a maniacal focus on performance, reliability, and a workflow that feels frictionless to high-performance software teams. When the product coheres around a few non-negotiables, teams can ship faster and with higher quality. The tension between flexibility vs. simplicity (1:04:29) shows up in every roadmap debate I’ve ever led. Flexibility sells demos; simplicity earns daily active usage. Picking simplicity early forces better defaults, clearer information architecture, and fewer surface areas where complexity can metastasize. Principled leadership shows up again at (1:17:27): Lead your team with strong principles. The best teams don’t need long memos to decide; they need clear tenets to align. Finally, (1:24:45) surfaces a nuanced distinction: design founders vs. engineering founders. The best outcomes emerge when design taste and engineering rigor compound—not compete—inside a product culture. A few references that stood out and helped frame the context: Airbnb, Coinbase, Y Combinator, Brian Armstrong, Brian Chesky, Jori Lallo, and Tuomas Artman. The through-line is unmistakable: high-taste product builders who pair speed with standards. If you want to jump to specific moments, here are the timecodes I found most actionable: (1:37), (6:54), (13:14), (19:32), (25: 03), (36:55), (42:41), (47:29), (52:02), (57:30), (59:18), (1:04:29), (1:17:27), (1:24:45). Each one reinforces a simple truth: focus compounds. If you’d like to follow Karri’s work directly, find him on LinkedIn: https://www.linkedin.com/in/karrisaarinen/ and Twitter/X: https://x.com/karrisaarinen. My takeaway for product leaders: revisit your scope, trim the excess, and put a small, senior team on the sharpest problem in your roadmap. Start with a principled bet, instrument outcomes, and keep the bar for craft uncomfortably high. That’s how you build products that feel inevitable—because they’re intentionally, relentlessly focused.

---