“It happened mid-workflow — the CEO asks "are we on track for the Q2 launch?" The PM opens Linear, checks 4 projects across 2 teams, counts completed vs.. The first time they used keyboard shortcuts to triage 30 issues in 5 minutes — it felt like the tool was reading their mind. That was the moment it stopped being a tool they were evaluating and became one they relied on.”
When I'm the ceo asks "are we on track for the q2 launch, I want to maintain a roadmap that connects initiatives to the issues being shipped, so I can prioritize work across multiple teams without losing cross-team dependencies.
A product manager at a 20–200 person startup who moved to Linear because Jira was too heavy and Notion boards weren't structured enough. They work at the initiative and project level while their engineers work at the issue level. They need to see the forest while the team sees the trees. They love Linear's speed and keyboard shortcuts but struggle to get the strategic views they need without building custom views for every stakeholder meeting.
To reach the point where maintain a roadmap that connects initiatives to the issues being shipped happens through linear as a matter of routine — not heroic effort. Their deeper aim: prioritize work across multiple teams without losing cross-team dependencies.
linear becomes invisible infrastructure. Maintain a roadmap that connects initiatives to the issues being shipped works without intervention. The old problem — projects and initiatives that don't roll up into a clear roadmap view for non-engineers — is a memory, not a daily fight. Auto-generated status rollups from project to initiative to roadmap level eliminate the manual compilation tax.
The CEO asks "are we on track for the Q2 launch?" The PM opens Linear, checks 4 projects across 2 teams, counts completed vs. remaining issues, notices one project has 8 issues with no assignee, and discovers a dependency on the platform team that nobody flagged. They spend 40 minutes building a status view, write it up in Slack, and realize they need to do this every Monday. They wish Linear had a "generate status update" button. It doesn't.
Manages 3–8 active projects across 1–3 engineering teams. Works with 10–30 engineers. Uses Linear's Projects for initiatives and Issues for tasks. Creates custom views and filters for different audiences (leadership, engineering, design). Runs weekly planning and monthly roadmap reviews. Spends 4–8 hours per week in Linear. Has tried building roadmap views with Linear's built-in features and supplemented with Notion or slides for leadership presentations.
The proof is behavioral: maintain a roadmap that connects initiatives to the issues being shipped happens without reminders. They've customized linear beyond the defaults — especially keyboard-first navigation and command palette — and their usage is deepening, not plateauing. They've stopped grooming sessions because Linear's triage workflow handles prioritization inline.
It's not one thing — it's the accumulation. Opinionated design limits customization for non-standard workflows 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 — the best project management tool is the one engineers actually update without being asked — makes them unwilling to compromise once a better option is visible.
Pairs with linear-primary-user for the IC engineer vs. PM perspective on the same tool. Contrast with jira-engineering-manager for the enterprise PM tool comparison. Use with notion-primary-user for the roadmap documentation layer.