Linear

Linear is an issue tracker and project management tool for software teams, built around the conviction that the speed of the interface is a feature - and that most project tools fail not because they lack capability but because they are slow and tedious enough that people stop updating them. Everything follows from that. The application is keyboard-first, with a command menu that reaches any action in a couple of keystrokes; state is synced locally so views open instantly rather than waiting on a request; and the data model is deliberately narrow - issues, projects, cycles, and roadmaps, with a triage inbox for incoming work. There is no configuration surface where you can spend a week designing a workflow, which is exactly why teams that adopt it tend to keep it current. Alongside the product, the company published the Linear Method - an opinionated set of practices about working in fixed-length cycles, keeping a small set of issues in flight, writing project specs before building, and treating the backlog as something to prune rather than accumulate. Adopting the tool without the method is possible, but most of the benefit comes from the pair. Pricing is freemium: a free tier covers small teams with a cap on issues, and paid plans add unlimited issues, more integrations, and the reporting and admin controls larger organisations need. It is priced per user, which stays reasonable for a startup engineering team. The obvious comparison is Jira, which is more configurable, more powerful for large organisations with compliance and audit requirements, and considerably heavier to live in day to day. Linear's counter-argument is that most product teams do not need that configurability and pay for it in friction. Against Notion or ClickUp, the trade is focus: those tools do many things adequately and can be shaped into an issue tracker, while Linear does one thing and does not bend. Against GitHub Issues, Linear adds cycles, roadmaps, and triage while keeping a tight two-way sync with pull requests, so engineers rarely have to leave their editor. Choose it when your team is small enough that process should be lightweight and disciplined enough to actually run cycles. It is a poor fit for organisations that need heavy customisation, non-engineering workflows, or a single tool that also serves as a wiki, a CRM, and a spreadsheet.