The Challenge
Project management tools have a predictable lifecycle: they start simple, users request features, the product becomes bloated, and eventually a new simple tool replaces it. Jira is the poster child — once loved, now the punchline of developer jokes.
Karri Saarinen and the Linear team faced a constant tension: users requested features every day (custom fields, complex permissions, Gantt charts, resource management). Saying yes to everything would create another Jira. Saying no to everything would limit growth. How do you build a tool that stays fast and focused while still evolving?
The Approach — Tools in Action
- Urgent + Important: Performance optimization, keyboard shortcuts, offline support → build now
- Important, not urgent: API improvements, integrations with key tools → schedule
- Urgent, not important: Feature requests from individual loud customers → deprioritize
- Neither: Complex permission systems, Gantt charts, resource management → actively decline
- Reach: How many users does this affect?
- Impact: How much does it improve their experience?
- Confidence: How sure are we this will work?
- Effort: How long will it take?
This data-driven approach prevented the team from being swayed by the loudest voice in the room.
The Impact Effort Matrix visualized the results:
- Quick wins (high impact, low effort): Keyboard shortcuts, instant search, cmd-K palette → built first
- Major projects (high impact, high effort): GitHub integration, cycles feature → scheduled carefully
- Thankless tasks (low impact, high effort): Complex admin panels, custom workflows → declined
The Outcome
Linear became the fastest-growing project management tool among developers and startups:
- Known for its blazing speed — the app loads instantly and feels native
- Opinionated design that does less but does it perfectly
- Grew rapidly through word-of-mouth without enterprise sales teams
- Companies like Vercel, Ramp, and Cash App adopted Linear specifically because of its focus
By saying no to most feature requests, Linear built a product people love — not a product that tries to do everything. The prioritization frameworks made "no" a strategic decision, not a reactive one.
Key Takeaway
The best products are defined by what they don't do. Use prioritization frameworks to make "no" a strategic decision backed by data, not a gut feeling.
Tools Used in This Story
Eisenhower Matrix
Decision MakingPrioritize your actions and tasks by importance and urgency
RICE Scoring
Decision MakingPrioritize ideas and features with a simple scoring framework
Impact Effort Matrix
Decision MakingPrioritize by weighing impact against the effort required