July 14, 2026
Ticket to Drift
Linear is always a lagging indicator
When the boss turns your to-do list into a surveillance dashboard, the comments erupt
TLDR: The article argues that task trackers like Linear miss most of the real work, because the important thinking happens in chats, meetings, and drafts before a ticket appears. Commenters split between calling that obvious, calling the post confusing, and roasting bosses who use these tools like employee surveillance.
A spicy little workplace rant about the project-tracking app Linear has turned into a full-blown comment-section therapy session. The big claim? These tools are great when teams use them to avoid duplicating work, but the minute executives start treating them like a live window into "what everyone is doing," the whole thing becomes a lagging indicator — basically, a delayed and incomplete snapshot. The author’s real point is that the messy, human part of work happens before the ticket ever exists: side chats, design debates, one-on-ones, and all the invisible thinking that never makes it into a neat box.
And wow, the community had feelings. One reader flat-out declared the post "incomprehensible," which is always a fun way to start a pile-on. Others jumped in with the more relatable office-drama angle: once leaders get detailed task data, they start trying to "optimize" everything, including the parts they don’t understand — like planning, testing, and the awkward reality that good work often looks slow from the outside. The juiciest comment came from a user who said their old CEO drank the "Linear koolaid" and started demanding meaningless deadlines just because he suddenly had granular visibility. Oof.
But not everyone was anti-Linear. One commenter argued the tool is actually trying to become the place where work begins, not ends, even pointing to Linear Agents as proof. So the drama is clear: is the app the problem, or is it just another innocent tool being turned into corporate binoculars? Either way, the crowd seems united on one thing: nobody wants their to-do list mistaken for reality.
Key Points
- •The article says issue trackers such as Linear can act as lagging indicators when used mainly for management visibility rather than engineer coordination.
- •A detailed ticket often appears only after substantial planning and problem-definition work has already been completed.
- •The article identifies informal conversations, design reviews, and 1:1 meetings as places where important pre-implementation work occurs.
- •It states that implementation, code review, and deployment are increasingly automated relative to the earlier work of defining the task.
- •The article suggests using an LLM to synthesize product-development status from sources like Slack, Google Docs, PRs, and review comments.