The Linear method: why saying no to half the roadmap builds the better startup

Every startup tutorial repeats the same instruction: ship fast and ship often. Linear quietly runs the opposite experiment — a release cadence that looks slow from the outside while the product feels faster than almost anything else in its category. The two ideas are not actually in conflict. Linear ships fast internally and publishes slowly and deliberately.

The three decisions worth studying

• Opinion over options. The settings surface is small because most decisions were made once and made well.
• Speed as a feature. Every screen responds under a blink — performance budgets treated as product requirements.
• A small public surface. The team writes about how they work and lets the method do the marketing.

What a smaller team can actually take

You cannot copy a design culture in a weekend. What transfers is the filter: before adding a feature ask what the product says no to. A roadmap that tries to please everyone ships a mediocre version of everything. My own rule for client products is the same — the second version of a feature is where the product starts to rot. This is exactly how I scope work on the product services side.

The trade-off is real

Saying no costs growth in the short term. Some segments never convert because the product refuses their workflow. The bet is that depth wins retention and retention compounds into word of mouth. For teams with runway the math works. For teams chasing their first revenue a stricter filter can starve the machine — know which situation you are in before borrowing the method.