Linear · Product sense · Senior · 45 to 60 minutes

How should Linear shape its first beta?

Linear is a software tool for planning and tracking product development work for teams that build software. Answer this product management case and get it graded line by line against a weighted rubric.

Product strategy
Prioritization
User segmentation
Go to market judgment
Metrics

The situation

It is early 2019. Karri Saarinen and his co founders have left Airbnb, Uber, and Coinbase to build Linear, a new issue tracking tool for software teams. From informal conversations with peers, they believe individual contributors at fast growing product companies are frustrated with existing tools, especially around speed, clutter, and workflows that seem built for admins rather than the people doing the work. The team now has a working prototype that they would use themselves, but it is still incomplete. Karri asks you to advise on the first 12 months of product strategy. The team could broaden the product to appeal to more companies and buying centers, add customization to fit varied processes, and launch widely to collect lots of feedback. Or it could stay narrow, ship a more opinionated workflow, and tightly control who gets access until the experience is strong. The hard part is that issue tracking is a core system of record, so switching costs are high, incumbents are entrenched, and a weak first impression could poison the market. What should Linear build, for whom, and how should it learn fast without diluting the product?

What to produce

Write a 1 to 2 page product strategy memo for Linear's first 12 months.

Your answer must

Define the initial target user and team profile, and name at least two segments you would not prioritize yet.
Recommend a clear product stance on opinionated workflow versus configurability, and on quality and speed versus feature breadth.
Propose a beta launch and learning plan, including how you would recruit early users, gather feedback, and decide who gets access.
Prioritize the first wave of product work, separating features that delight ideal users from changes that remove adoption blockers.
Specify the metrics and qualitative signals you would use to decide whether to broaden access or stay narrow longer.

Constraints

Assume the founding team has 18 months of runway, a working prototype, and no dedicated sales or support team.
Existing issue tracking tools are deeply embedded in team workflows, so migration friction is high.
You cannot rely on enterprise procurement or top down mandates in the first year.

Format

Use sections titled ICP, product principles, beta plan, roadmap sequencing, metrics, and risks.

How Linear actually played it

The CEO explains why Linear stayed opinionated about workflow rather than endlessly configurable, and why quality came before growth. Helps PMs argue for focus and craft.

Strong opinions can beat flexibility in tools
Slow, deliberate quality can compound

Built from Linear's Path to Product-Market Fit: Quality and Craft Over Speed and Scale by First Round Review.