LLenny's Podcast
← All episodes
Karri Saarinen (co-founder, designer, CEO)08 October 2023

Inside Linear: Building with taste, craft, and focus

8Frameworks
15Insights

Frameworks in this episode

Entrepreneurship3 steps

Cohort-Gated Private Beta

Onboard early users in small waves so each cohort surfaces new bugs instead of duplicating the last cohort's feedback.

Read →
Marketing3 steps

Design as Category-Crowding Leverage

The more crowded and mature a category, the more design and brand become the deciding differentiator.

Read →
Leadership4 steps

Hire People Bigger Than Their Title

Build a small team of high-caliber people who each own more scope than their role, and screen for it with a paid work trial.

Read →
Strategy3 steps

Magic and Science Decision-Making

Replace A/B tests and metric goals with deep shared customer understanding, then decide by informed intuition.

Read →
Productivity3 steps

Main Quest vs Side Quest Focus Filter

Filter every opportunity by 'does this advance the main quest, and is it important now or later?'

Read →
Innovation3 steps

Opinionated Software: Good Defaults Over Flexibility

Ship the one best workflow as a strong default so users spend time on their work, not on configuring your tool.

Read →
Entrepreneurship4 steps

Product-Market Fit as Segment Territory

Treat PMF not as a binary but as territory won segment by segment, and double down hard on whatever segment is pulling.

Read →
Innovation3 steps

Ship-Ugly-Then-Polish Craft Loop

Combine shipping fast with fixing fast: get rough builds in front of real users, reserve polish for general release.

Read →

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Hot Take· 4

Hot Take16:30

Why Linear Runs on One PM and Pushes PM Work to Engineers

Linear has a single PM (its head of product) and instead gives project ownership to engineering and design. Karri argues that over-specializing roles is efficient but that quality comes when the people building also spend time thinking about scope, direction, and communication. Each project has a lead (engineer or designer) responsible for getting it started and communicating progress.

  • Only one PM in the company, who acts as head of product setting direction
  • Specialization is efficient but building quality needs builders who also think, not just execute
  • Every project has a lead who can be an engineer or designer, not a formal role
  • Requires a very high, product-minded hiring bar and people who want broader scope

“we actually don't have much BMS in the company we only have one”

Karri Saarinen · 14:00

“we just think that in in order to like build quality things or build things in a certain way it's actually better if people actually…”

Karri Saarinen · 19:00
#product-management#team#ownership#hiring
Hot Take25:30

The More Crowded the Category, the More Design Wins

Karri's belief is that the more a domain matters and the more mature it is, the more design matters. Early products in a new paradigm can look basic, but once there are hundreds of competitors the design bar becomes table stakes just to be taken seriously. Still, he cautions design is never the sole reason a company wins, the product must also be better or different.

  • New paradigms tolerate basic design at first; maturity raises the bar to table stakes
  • Old landing pages (Google, YouTube) would be dismissed if launched today
  • When buyers have many choices they pick what looks highest-quality
  • Design enables acquisition, retention and perception but isn't sufficient alone
  • Design is strongest leverage early, before anyone knows you

“my belief is that like any domain or industry the more it matters the more the design matters”

Karri Saarinen · 25:30

“design is never going to be like uh the reason or like the the the reason why a company is successful”

Karri Saarinen · 27:00
#design#differentiation#branding#strategy
Hot Take45:30

No A/B Tests, No Metric Goals: Building on 'Magic and Science'

Linear doesn't run A/B tests or set per-feature metric goals. Karri describes a mix of 'science' (heavy user research, talking to customers, shared Slack channels) and 'magic' (using intuition once the whole team deeply understands customers). He warns that over-relying on data is often fear of making a wrong choice, and that a team must be okay making and fixing its own decisions.

  • No A/B testing and no specific per-feature metric goals
  • 'Science' = deep, continuous user research and customer contact across the team
  • 'Magic' = shared customer understanding enabling intuition-led decisions
  • Over-using data is often fear of being wrong, letting data decide for you
  • Team must accept it will sometimes make mistakes and fix them

“we we like to like talk about this inite like this like a mixture of like magic and science”

Karri Saarinen · 45:30

“sometimes people use data a lot or too much because they just are they're worrying or they're afraid that will I make a wrong choice”

Karri Saarinen · 49:00
#product#metrics#decision-making#research
Hot Take1:16:00

Product-Market Fit Is a Spectrum You Win Segment by Segment

Karri reframes product-market fit not as binary but as a spectrum of confidence within specific market segments. Linear first won the early-stage startup segment (becoming the default tool) before working toward fit with larger companies. He cites Zoom's Eric Yuan doubling down on winning customer types, arguing you should follow the pull and capture a category before expanding.

  • PMF is a spectrum, not a binary you simply have or don't
  • In B2B, fit differs by customer size, domain, and category
  • Linear won early-stage startups first, then pushed into larger companies
  • Zoom's Eric Yuan doubled down on winning customer types (e.g. universities)
  • Find the pull, double down until the category is captured, then expand

“the way I think about is like do we have the do we have the fit in this specific segments and like how strong that…”

Karri Saarinen · 1:17:30

“if you have some like you see that something's working really well then it's almost like you should focus on doing that more”

Karri Saarinen · 1:20:30
#product-market-fit#b2b#strategy#segments

Explainer· 4

Explainer09:00

Ship Rough Early to Yourselves and Opt-In Customers, Polish at GA

Linear avoids over-polishing up front because you only learn how a feature should work once you start building it. New features get shipped to production but visible only internally, then to a handful of opt-in customers who accept a janky experience in exchange for early access. Real craft and polish come at the full general release stage.

  • Don't spend lots of time designing and polishing before building
  • Ship to production visible only to the team first, then to 1-10 opt-in customers
  • Early stages can be janky because it's explicitly unfinished and about feedback
  • Reserve real polish for the full general release
  • Timelines can slip days, not full redos, when something doesn't feel right

“we don't want to spend tons of time up front just like designing it and polishing it perfectly because we actually believe that when when…”

Karri Saarinen · 09:00

“we're okay with it because we are saying it's not finished like we just want to get your feedback early so we can make it”

Karri Saarinen · 09:30
#product#craft#shipping#feedback
Explainer30:30

A Brand Isn't a Logo, It's Built Over Time and Must Be Authentic

Karri argues brand is not the logo or website colors; copying another company's look isn't a brand. A real brand is the message and voice, and it accrues over time through what you do, say, and how you treat customers. He points to Airbnb, where brand was treated as part of everything, as the model.

  • Brand is the message/voice, not the logo or colors
  • People sense when a brand is inauthentic even if they can't articulate it
  • You start with no brand and build it over time through actions and words
  • At Airbnb brand was the most important thing and part of everything the company did

“the brand doesn't happen overnight so it's basically just you start in the beginning”

Karri Saarinen · 31:30
#branding#marketing#authenticity
Explainer57:00

Hire Fewer, Higher-Caliber People Who Are More Than Their Title

Karri's core belief is you can build better with fewer people than with more. Linear has never more than doubled headcount in a year and looks in every role for taste and a broader perspective than the job strictly requires, engineers with product sensibility, marketers who can tell stories. People who exceed their title make the company easier to run because they pick up work together instead of saying 'not my job.'

  • Belief: smaller teams of high-quality people out-build larger average teams
  • Never more than doubled headcount in a year (may slow further)
  • Every role screened for taste and judgment beyond the core skill
  • Engineers need product thinking; marketers need storytelling taste, etc.
  • People 'more than their title' avoid the 'not my job' problem

“we we just believe that you can actually build better with less people than you can with more people”

Karri Saarinen · 57:30

“when you have these people that are a little bit more than their title it's like the company is I think much more easier to…”

Karri Saarinen · 1:00:00
#hiring#team#talent#culture
Explainer1:06:00

How Karri Tests for Product Sensibility: Keep Asking Why

To assess product judgment, Karri digs into a candidate's past projects, asking why decisions were made, whether they were right, and what they'd do differently. Weak answers stop at 'I didn't like it'; strong ones give reasoning tied to users, context, and purpose. People who really think about product can go deeper and deeper, and it shows quickly.

  • Probe past projects with repeated 'why was this decision made?'
  • Weak signal: opinions with no reasoning ('I just didn't like it')
  • Strong signal: reasoning tied to users, context, and purpose
  • People with real sensibility can keep going deeper; it's clearly visible

“ask people that like we asked about their projects and I try to go deeper it's like why was this decision made”

Karri Saarinen · 1:06:30

“well I don't like it because in this case like it would not work well for this kind of users”

Karri Saarinen · 1:07:00
#hiring#product#interviews#judgment

Story· 4

Story06:00

Linear Is Profitable With a Net-Negative Lifetime Burn Rate

Karri shares that Linear has been profitable for two years and has a net-negative lifetime burn rate, meaning it holds more cash today than it ever raised. Because the business worked early, they never had to spend raised capital to build it. He frames this as the inverse of the typical raise-then-burn startup path.

  • Profitable for the last two years
  • Net-negative lifetime burn rate: more cash in the bank today than total raised
  • Never spent raised money to build the business because it became a business early
  • Contrasts with the normal startup path of raising and burning to build

“we actually have this net negative lifetime burn rate um which means that like we just have more cash in the bank today than we…”

Karri Saarinen · 06:00
#startups#finance#profitability#linear
Story15:00

The Engineer Who Fixed Context-Menu 'Safe Zones' Nobody Asked Him To

Karri tells how an engineer, Andreas, noticed that Linear's right-click submenus only worked if you hovered exactly over the item, unlike macOS which lets you move diagonally through a dynamic safe zone. Without being told to, he rebuilt the menus with dynamic safe areas so users stop missing by a few pixels. It's a concrete example of craft emerging when project teams own their work.

  • macOS lets you move diagonally into submenus via a 'safe zone'; most software forces exact hovering
  • Users often miss submenu targets by a few pixels in naive implementations
  • Andreas built dynamic safe areas based on submenu positioning, unprompted
  • Craft like this happens when project teams (engineering + design) own the feature

“so what Andress it like which we didn't tell him to do is like yeah this kind of sucks and like we should make this…”

Karri Saarinen · 16:00
#craft#ux#ownership#engineering
Story1:12:30

Why Linear Invited Beta Users in Small Cohorts, Not All at Once

During its year-long private beta, Linear invited roughly 10 people a week rather than opening the floodgates. Inviting everyone at once would mean many users hitting the same early-stage bugs and sending duplicate feedback, wasting effort. Instead each cohort surfaced a problem, the team fixed it, then invited the next cohort, an effective way to drive early development.

  • Year-long private beta with staged, small invites (~10/week early on)
  • Mass invites cause duplicate feedback on the same early bugs
  • Each cohort surfaces issues, team fixes, then invites the next cohort
  • Karri personally read survey responses and emailed invite links early on

“if you just invite everyone at once or a lot of people at once all of those people going to probably hit the same problems…”

Karri Saarinen · 1:13:00
#beta#growth#product#feedback
Story1:14:30

The Pay-What-You-Want Slider That Tested Linear's Pricing

Before formal pricing, Linear added a settings page with a slider letting users choose how much to pay per seat. Some paid $28 a seat, some $1, and it wasn't meant to yield hard data so much as to test the payment function and gauge willingness. Seeing people voluntarily pay up to the ~$20 max gave the team confidence there was a market at a sub-$20 price.

  • Optional settings page with a self-set per-seat price slider
  • Payments ranged from $1 to $28 per seat; ~$20 was the practical max
  • Goal was testing the payment flow, not gathering precise pricing data
  • Voluntary payments gave confidence a market existed under $20

“we just give you a slider that like how much do you want to pay per seat”

Karri Saarinen · 1:15:00

“some people pay like $28 per seat and some people pay like $1”

Karri Saarinen · 1:15:00
#pricing#monetization#experiments#growth

Tool· 1

Tool1:02:00

Linear's Paid Work Trial as the Final Hiring Step

Every Linear hire does a paid work trial as the last step of the loop, joining as a mini-contractor to tackle a deliberately vague problem in the real codebase, then presenting what they built. It reveals how a candidate operates, scopes, and makes progress in a short window, and lets candidates evaluate the company, its clean codebase, meetings, and Slack. Almost no one declines, and most are glad they did it.

  • Paid trial is the final step after hiring-manager and skill interviews
  • Candidate acts as a mini-contractor on a vague, real problem in the codebase
  • Tests scoping, approach, and ability to make progress in a short time frame
  • Two-way: candidates see the codebase, meetings, Slack, and teammates
  • Scheduled around weekends/holidays; very few have ever declined

“we give them a very like usually fairly vague problem statements like if you're engineer like hey there's this feature that needs to be built…”

Karri Saarinen · 1:02:30

“how does this person operate in this kind of environment and like how do they approach problems”

Karri Saarinen · 1:05:30
#hiring#interviews#process#startups

Takeaway· 2

Takeaway53:30

Avoid Side Quests: Ask if It Advances the Main Quest

Karri stays focused by asking whether something is important to do now or can wait, drawing on YC advice to only talk to customers, build the product, and exercise. Internally Linear frames ideas as RPG main quests vs side quests, rejecting anything that doesn't progress building the core product. He applies the same filter personally, including to things like this podcast.

  • YC advice: focus on three things, talk to customers, build the product, exercise
  • Constantly ask: is this important to do now, or better later?
  • Frame work as main-quest vs side-quest; kill side quests that don't help customers/product
  • Applied the filter to delay SOC 2 and to timing appearances like this podcast

“what you should be focusing on when you build a startup is like talk to customers build the product exercise”

Karri Saarinen · 53:30

“avoid the side quests like like there is always like ideas people have”

Karri Saarinen · 55:30
#focus#prioritization#startups#leadership
Takeaway1:35:30

'Go Slow to Go Fast'

Karri's life motto is 'go slow to go fast.' People, especially in startups, tend to rush from urgency, then have to come back and fix what they rushed. Taking time to think through what you're going to do first ends up being faster than going back and forth.

  • Motto: go slow to go fast
  • Urgency matters, but too much urgency causes rushed work you must redo
  • Thinking first before acting is faster overall than back-and-forth fixes

“go slow to go fast”

Karri Saarinen · 1:35:30

“sometimes people have tendency to rush into things and especially in I think in startups”

Karri Saarinen · 1:35:30
#leadership#focus#philosophy