
A fast, well-designed project and issue tracking tool for software teams.
Linear's polished UX earned wide admiration, and its look was copied by many new sites, with its head of product publicly arguing for taste. But copying it can fail: Rob Snyder's Linear-style HR software flopped because buyers didn't care about UX. Builders also use it as a capture layer, where one dictated idea became ticket STU88. Lesson: better UX wins only for customers blocked by the incumbent.
From Zevi Arnovitz's demo
Copying Linear's better UX failed where buyers weren't blocked by UX. Rob Snyder tried a Linear-style better user experience in HR software and it failed, because the buyer did not care about user experience. His rule is that a better or cheaper copy of a category winner won't sell unless some customer is blocked by the incumbent.
Snyder says Linear beats Jira only if some people are blocked by Jira's experience. He calls building the same product as a visible winner, with no theory of a different customer being unblocked, a common tar pit. Quote: "You could give me a 100x better printer for my house, and I won't buy it cuz I'm not blocked."
Taste means aesthetics plus systems thinking and context, not just polish. Andrew Ambrosino names Linear as his favorite software product until his own team's. He notes that last year every new website copied its look, and that its head of product tweeted about taste.
He defines taste as more than visual polish: how something fits the system, which theme it belongs to, how it is presented, and whether an animation's feel matches its meaning. His example is Paul Graham, who wears cargo shorts yet clearly has taste. The real question, he says, is what a thing should be when anything can be built.
Zevi Arnovitz files bugs and ideas into Linear without breaking flow. He runs a /create-issue command that tells Claude he is busy and should ask only a few brief questions. Claude then files the issue in Linear via MCP, and he dictates it with a voice tool.
In the demo, a spoken description became ticket STU88 with a TLDR, current state and expected outcomes. The goal is to capture the idea fast so he can keep working and explore it later.
Linear gets a working version after about 10% of the time budget and rolls features out to internal users and widening betas. It refuses customization that helps managers but hurts ICs, built Customer Requests after 40% of custom field asks were about tracking customers, and leads growth in enterprise through brand pull. It does almost no estimating.
Copying Linear's better UX failed where buyers weren't blocked by UX. Rob Snyder tried a Linear-style better user experience in HR software and it failed, because the buyer did not care about user experience. His rule is that a better or cheaper copy of a category winner won't sell unless some customer is blocked by the incumbent.
Snyder says Linear beats Jira only if some people are blocked by Jira's experience. He calls building the same product as a visible winner, with no theory of a different customer being unblocked, a common tar pit. Quote: "You could give me a 100x better printer for my house, and I won't buy it cuz I'm not blocked."
Launched in 2019 after a year-long private beta, invited about 10 people a week from a waitlist of around 4,000. It has no A/B tests or feature metric goals, one PM, paid work trials for hires, and is profitable with more cash than it raised.
Taste means aesthetics plus systems thinking and context, not just polish. Andrew Ambrosino names Linear as his favorite software product until his own team's. He notes that last year every new website copied its look, and that its head of product tweeted about taste.
He defines taste as more than visual polish: how something fits the system, which theme it belongs to, how it is presented, and whether an animation's feel matches its meaning. His example is Paul Graham, who wears cargo shorts yet clearly has taste. The real question, he says, is what a thing should be when anything can be built.
Beats Jira only if some people are blocked by Jira's experience. Rob tried a Linear-style better UX in HR software and failed because buyers didn't care. Its former head of product wants founders to feel the customer's pain firsthand.
Zevi Arnovitz files bugs and ideas into Linear without breaking flow. He runs a /create-issue command that tells Claude he is busy and should ask only a few brief questions. Claude then files the issue in Linear via MCP, and he dictates it with a voice tool.
In the demo, a spoken description became ticket STU88 with a TLDR, current state and expected outcomes. The goal is to capture the idea fast so he can keep working and explore it later.
Andrew's favorite software product until his own team's. Last year every new website copied its look, and its head of product tweeted about taste.
His create-issue command files bugs and ideas here via MCP while he's mid-build. A dictated idea became ticket STU88 with a TLDR, current state and expected outcomes.
It beat Jira, Asana and Monday in a crowded category by being thoughtful about every part of the experience. It invested in being more delightful and is winning that space.
Adding a Devin label to a Linear ticket makes Devin scope the task first, showing relevant files and its confidence level, then start work once a human agrees. Product managers also use it to get answers from the code.
Bolt uses it to run engineering. Its ticket style is the model Simons recommends for writing prompts.
Began with two-to-five-person startups using GitHub. It used its launch wait list as a screener survey about auth and code hosting, admitting the people who best matched what the product could do that day.
Jason knows little about it beyond hearing it shares some views. He notes a VC-funded company can work efficiently, but nothing forces it to.
Runs a work trial where candidates work with the team for one to five days before being hired.
The Browser Company has run on Linear since day one, and Lenny groups it with Arc as a product obsessed with user experience.
Developer toolsA chip company whose GPUs and CUDA software power gaming, AI and accelerated computing.
Developer toolsAnthropic's agentic coding tool that lets Claude work on code end to end.
Developer toolsAn AI code editor that lets engineers build software with AI while staying in control.
Developer toolsA code hosting and collaboration platform for software developers, with free and paid plans.
Developer toolsAn AI app builder that lets people create software by chatting with an agent.
An app development company that builds apps for founders and clients.
Developer toolsGoogle's backend platform for building apps.
Developer toolsA cloud platform for building, deploying and scaling front-end and AI web applications.