“It happened mid-workflow — it's Thursday.. linear-projects handled something they'd been doing manually, and it just worked. That was the moment it stopped being a tool they were evaluating and became one they relied on.”
When I'm the product review is monday, I want to know the health of every active project without a weekly status sync that pulls, so I can people out of work.
An engineering manager or head of engineering at a startup of 20–150 engineers who uses Linear at the issue level to track work and at the Projects level to communicate progress. The ICs live in issues and cycles. The EM lives in projects and the roadmap view. They're the translation layer between "what the team is building" and "what the company thinks we're building" — and Linear Projects is the interface they use to close that gap.
To reach the point where know the health of every active project without a weekly status sync that pulls happens through linear-projects as a matter of routine — not heroic effort. Their deeper aim: people out of work.
linear-projects becomes invisible infrastructure. Know the health of every active project without a weekly status sync that pulls works without intervention. The old problem — project status that's accurate when it's updated and stale 48 hours later — is a memory, not a daily fight. Project health inference from issue velocity and cycle completion rate replaces.
It's Thursday. The product review is Monday. Four projects are active. One is on track. One is 2 weeks behind but the team hasn't updated the status. One has a blocker that the EM knows about from a Slack message but that's not reflected in Linear. One was completed last week but nobody marked it done. They're spending 40 minutes updating Linear before the Monday review so the dashboard reflects reality. This is the work that shouldn't exist.
Manages 3–8 active projects across 2–4 engineering teams. Uses Linear's roadmap view as their primary interface. Reviews project milestones and status weekly. Creates projects from cycle issues that have reached sufficient size and scope. Links projects to product initiatives. Shares roadmap views with the VP of Product and occasionally the CEO. Has tried to get ICs to update project status themselves. The hit rate is 60%. They update the rest themselves.
The proof is behavioral: know the health of every active project without a weekly status sync that pulls happens without reminders. They've customized linear-projects beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
It's not one thing — it's the accumulation. Project status that's accurate when it's updated and stale 48 hours later that they've reported, worked around, and accepted. Then a competitor demo shows the same workflow without the friction, and the sunk cost argument collapses. Their worldview — a roadmap is a commitment with uncertainty, not a schedule with certainty — makes them unwilling to compromise once a better option is visible.
Pairs with `linear-primary-user` (the IC cycle-level user) for the full team workflow from issue to project. Contrast with `jira-primary-user` for the flexible-modern vs. process-heavy planning tool philosophy. Use with `pitch-primary-user` for the engineering roadmap-to-board-deck workflow translation.