Your Linear Is Not Engineering Management

It is Monday, 9:04 AM. Your VP of Engineering opens Linear before standup. 2,400 open issues across six squads, 94 in-flight stories tied to the Q4 roadmap, 240 tickets with no activity in 21 days, 42 stories blocked on a sibling squad, and 18 reviews sitting past the two-day SLA. The sprint review on Thursday reads a 61 percent commit-hit rate for the second quarter running. The founder opens the roadmap at 9:08 AM and asks why the three features promised to the design partner on the Series B pitch still read "in progress" four months later. The VP writes a 320-word reply at 11:12 AM. The ticket tracker did not write the reply. A human did.

Every founder who confuses Linear with engineering management is quoting the wrong tool. Linear is a brilliant issue tracker. It stores the queue. It does not run the function.

What Linear stores vs what the function owns

Linear stores 2,400 issues, 320 cycles of history, 94 labels, and a dependency graph across the six squads. Engineering management is the function that keeps the 94 stories tied to the roadmap closing on cadence, the 42 cross-squad blockers escalated inside 24 hours, the 240 stale tickets triaged or closed on a weekly cadence, and the scope cuts logged against the quarterly commit on the ledger the CEO reads at the board meeting.

The gap between the two is not a Linear feature request. The function reads six systems. Linear for the issue graph, GitHub for the review queue and merge-cycle data, PagerDuty or Opsgenie for the on-call interrupt load, the deploy pipeline for lead-time-to-production, the design-partner CRM for the three features that unblock the Series B commit, and the Slack channel where every "quick ask" lands between the standups. The ticket tracker is one of six inputs. The function is the synthesis.

The 32 hours a week the VP spends below the roadmap

A $280K to $340K VP of Engineering reads $380K to $470K loaded against the US entity. The scope reads architecture, hiring, roadmap, cross-functional alignment, and the executive brief. The reality reads 32 to 40 hours a week on queue hygiene the ticket tracker was supposed to run on its own.

Stale-ticket chase. The 240 tickets with no activity in 21 days are not going to triage themselves. The VP opens Linear on Thursday afternoon, reads 42 of them, pings six engineers in Slack, and closes maybe 18 before the retro. The remaining 222 roll into next week.

Blocker escalation. The 42 cross-squad blockers surface in standup, get a comment in the ticket, and sit on a 72-hour average time-to-resolution against the 24-hour target. Three of them are blocking the Series B design-partner commit. The VP finds out on the Thursday roadmap review from the design partner, not from the queue.

Review-queue drag. The 18 reviews past the two-day SLA cost the team 6 to 9 engineer-days a week on context-reload. The VP nudges three reviewers in DM every Monday. The queue clears on Friday and refills on Monday.

Scope-cut logging. The six features cut from the Q4 commit never land on the ledger the CEO reads. The board asks why the Q4 velocity went up and the commit-hit rate went flat. Nobody can cite the three scope cuts that moved the number.

What the function should ship on cadence

Monday 8:00 AM. Cycle-health brief. 94 in-flight stories against the two-week median cycle time, 42 cross-squad blockers routed to the owning tech lead with the sibling squad, the blocking commit, and the ask pre-cited, the 11 stories past the planned finish date flagged for a scope conversation, and the 18 reviews past SLA routed to the three reviewers with the diff size and the author pre-cited.

Tuesday 8:00 AM. Stale-queue brief. The 240 tickets past 21 days of inactivity grouped by squad, 94 proposed for close-as-stale with the ticket, the last touch, and the owning engineer pre-cited, 42 proposed for roadmap-promotion against a Q1 theme, and 104 queued for a Wednesday owner-nudge block.

Wednesday 8:00 AM. Review-queue reconciliation. 18 reviews past the two-day SLA cleared, the three recurring long-review authors flagged against the trailing 60-day median, and the two squads carrying 61 percent of the review drag flagged for a pairing-cadence review.

Thursday 8:00 AM. Roadmap-commit brief. The 94 in-flight stories against the Q4 commit, the three design-partner features ranked by remaining blocker count, the six scope cuts logged against the quarterly ledger with the reason and the trade-made cited, and the two outlier squads flagged against the plan.

Friday 8:00 AM. Weekly delivery brief. The commit-hit rate against the trailing six cycles, the lead-time-to-production against the 30-day baseline, the on-call interrupt load against the trailing 60-day median, and the four decisions ranked for the following week by expected roadmap movement. The VP reads the brief at 8:09 AM and the Monday standup opens with the blocker list already cleared.

The unit economics on the function

A $280K VP of Engineering reads $380K loaded. Six tech leads at $220K base read $300K to $360K loaded each, so $1.8M to $2.2M a year on the leadership seat line before an engineer writes a line of code. 32 hours a week on queue hygiene across the VP plus the six tech leads at a loaded hour of $150 to $220 costs the function $240K to $460K a year in senior time on work the queue was supposed to run on its own.

A 14-day sprint to stand up the engineering-management agent runs in the low to mid five figures. Ongoing cost lands at $3K to $8K a month on API spend, read access to Linear and GitHub, and the operator who owns the Monday review. The sprint-versus-hiring-another-tech-lead math lands four to seven times cheaper on year one. The VP and the six tech leads stop running the queue and land on the architecture and the roadmap, which is what the ledger was paying them to run on in the first place.

What the sprint ships in 14 days

Day one, the agent reads against Linear, GitHub, the deploy pipeline, PagerDuty, and the design-partner CRM. Day seven, the first Monday cycle-health brief lands in the VP inbox with the 42 cross-squad blockers routed to the six tech leads. Day fourteen, the Thursday roadmap-commit brief lands at 8:00 AM with the three design-partner features ranked, the six scope cuts logged, and the Friday delivery brief sitting on cadence.

If your Linear reads 2,400 open issues, 240 of them stale, and the Thursday sprint review still ships a 61 percent commit-hit rate, the version where the brief lands at 8:00 AM and the VP owns the architecture is fourteen days away. Linear still runs the queue. GitHub still runs the reviews. The agent closes the function the stack was already supposed to close. You can keep running the Monday standup on a stale-ticket export, or you can scope a sprint and have the Thursday brief landing before the next board pack.