Every engineering org I've worked in eventually converges on the same ritual: standups reference Linear (or Jira, or Shortcut), sprint planning revolves around Linear, leadership dashboards pull from Linear — and yet the actual work being done rarely matches what the tickets say. This post's title captures something almost every practitioner knows but rarely articulates: the ticket tracker is not where work happens. It's where work is recorded, usually after the fact, and often badly.

Based on the title and the personal-blog format (remark.ing is a lightweight publishing tool favored by developers writing short-form thought pieces), this is almost certainly an argument that leaders who manage their team through Linear are watching a delayed, filtered signal — one that lags the real state of the codebase, the real state of morale, and the real state of customer pain. By the time something shows up as an "Urgent" ticket, the underlying problem has usually existed for weeks. By the time a project is marked "Done," the actual work of shipping, monitoring, and stabilizing has often just begun.

Why this matters for a technical audience:

• It reframes a common management anti-pattern. Executives love ticket dashboards because they feel like ground truth. They aren't. They're a lossy compression of engineering reality, produced by tired engineers under mild social pressure.
• It points at the leading indicators leaders should actually watch. PR review latency, incident frequency, on-call pager load, time-to-first-commit for new hires, the ratio of unplanned to planned work — these move before Linear does.
• It has implications for AI-assisted engineering. As agents start opening PRs and closing tickets autonomously, the gap between "ticket state" and "system state" widens further. If your only view of the org is Linear, you'll be even more blind than before.

The best posts in this genre — Will Larson on engineering strategy, Charity Majors on observability-as-management-tool — argue that leadership requires instrumenting the work itself, not the metadata around it. A short, sharp post with this title likely lands in the same tradition, and deserves more than one upvote on a busy Sunday morning.