When Marketing, Benefits and Talent All Run on Linear Boards

What people were saying

The day belonged to a thread that wasn't really about Linear, except that it was entirely about Linear. @reallygabriella explained that she runs six teams at Warp (marketing, benefits, people, talent, partnerships, ops), none of them engineering, and all of them on Linear plus Claude Code. The argument: engineering teams write everything down, give every task an owner and a state, script the third repetition, and decompose work before promising dates. Her weekly ritual is a standup around each team's Linear board, which she notes almost no operating team does. The line people latched onto was that her teams got addicted not to process but to visibility, because it was the first time their work was legible to everyone else.

Linear COO @cjc quoted it with the tidy version of the thesis: at product-forward companies the whole org is starting to work like an engineering team, with work visible, owned, and increasingly done with agents. This is, conveniently, also the pitch.

She also spent the evening on something unrelated to the product, pushing back on the "they raised too much" narrative around a $1.79B outcome, noting the company is profitable with real cash on hand and that overcapitalization is sometimes a morality tale rather than an explanation. She added that Linear has deliberately declined to raise when it could have, which is the kind of aside that reads as a flex and probably is one.

Notable anecdotes

@gorillasu built a site that renders your Linear projects as a connected graph: every ticket, status, and relationship, so you can see where the remaining work clusters. @mastra launched Mastra Factory, which wires GitHub, Linear and Slack into configurable boards (theirs runs Intake through Triage, Planning, Build, Review, Done). @vahagnzak taught an AI support agent to file bugs and feature requests in Linear and fetch updates when customers ask, and @gm_mertd described using Linear issues as a scratchpad for one coding agent before handing the plan off to another, which is a novel use of an issue tracker and also basically what an issue tracker is.

From the official account, @linear highlighted CommureOS weighting customer feedback by count and by revenue using Customer Requests. And @brendanrc2 posted a recruiting-adjacent manifesto about fixing five things a week instead of debating the system, which drew a gentle amendment from teammate @dparker313: the advice works for any frustrating issue, not just quality ones.

No real pushback today, unless you count the Miro thread, where the argument was about capital rather than software.