“They're back from a two-day sprint on a difficult bug.. Something that used to take 30 minutes took 30 seconds. When the duplicate issue detection caught a bug report they were about to file — no more searching before creating. That was the aha.”
When I'm back from a two-day sprint on a difficult bug, I want to track their work without the tool requiring more work than the work, so I can surface blockers and priorities without a standup for every question.
A software engineer at a startup of 10–100 people who has used Jira and has Opinions. They switched to Linear — or advocated for switching — because it's fast, opinionated, and built for people who care about the work rather than the process around it. They use Linear every day to track their own work, manage issues, and follow the work of their small team. The keyboard shortcuts aren't optional to them — they're the point.
To make linear the system of record for track their work without the tool requiring more work than the work. Not aspirationally — operationally. The kind of intention that shows up as a daily habit, not a quarterly goal.
The tangible result: track their work without the tool requiring more work than the work happens on schedule, without manual intervention, and without the anxiety of issue hygiene problems — stale issues, wrong priorities, wrong assignees — that accumulate in any system. linear has earned a place in the daily workflow rather than being tolerated in it.
They're back from a two-day sprint on a difficult bug. They have six issues to update, two that can be closed, and one that needs to be split into three separate issues now that they understand the scope. There's also a GitHub PR linked to an issue that was closed last month and shouldn't have been. They're going to do all of this in under 8 minutes because they have a keyboard and they know how to use it.
Uses Linear as both a daily task manager and a team-wide project tracker. Follows 2–3 cycles per team with 2-week cadence. Uses the Linear CLI and GitHub integration. Creates issues from Slack via the Linear bot. Has strong feelings about priority labels. Keeps the "My Issues" view open at all times. Has set up custom views that the rest of the team uses without knowing who built them. Uses Linear on Mac. The Windows app is for other people.
They've stopped comparing alternatives. linear is open before their first meeting. GitHub PRs automatically update issue status — no manual state changes. The strongest signal: they've started onboarding teammates into their setup unprompted.
Not a feature gap — a trust failure. Issue hygiene problems — stale issues, wrong priorities, wrong assignees — that accumulate in any system happens at the worst possible moment, and linear offers no path to resolution. A major bug in a release disrupted their sprint planning and Linear's response time wasn't fast enough. Their belief — software tools should have opinions — the absence of opinion is a design failure — has been violated one too many times.
Pairs with `startup-pm` for the issue creation and prioritization workflow from both sides. Contrast with `jira-primary-user` to map exactly why engineers choose Linear and what they give up. Use with `senior-engineer-skeptic` for Linear evaluation scenarios in teams considering migration.