Opinionated Software: Good Defaults Over Flexibility
Ship the one best workflow as a strong default so users spend time on their work, not on configuring your tool.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 88%
Flexible software forces every team to figure out its own way to use each feature, burning time on the tool instead of the work. Linear's principle is to provide good defaults and strong opinions: decide the best workflow, build that, and let the user simply agree. The design mantra is 'design something for someone' rather than everything for everyone, which only yields generic solutions.
Origin
A core tenet of 'the Linear Method,' articulated by Karri Saarinen; echoes Christopher Alexander's pattern thinking he cites as an influence.
Core principles
- 01Productivity software exists to let people do work that matters, not to be configured
- 02Flexibility pushes the cost of figuring out the workflow onto every user and every team
- 03A strong default is the most-optimized solution you can offer; ideally the user feels its optimization and agrees
- 04Designing for a specific someone beats designing for everyone, which produces generic results
How to run it
- 1
Define the single best workflow
For each feature, decide the most optimized way it should work rather than exposing ten configurable paths.
Pro tip Resist copying how other tools do it; work out what is actually the useful way for the job to be done.
Watch out A feature usable in 10 different ways means every team invents a different way, fragmenting the experience.
- 2
Build that opinion as the default
Ship the chosen workflow as the out-of-the-box behavior so users don't have to think about setup or configuration.
Pro tip Make defaults good enough that agreeing with them feels obvious, so the tool disappears behind the work.
- 3
Design for a specific someone, not everyone
Target a concrete user and use case; a generalized 'works for everyone' solution ends up optimized for no one.
Pro tip When usage differs by company, hold the opinion anyway rather than adding configuration for every edge case.
In the wild
Linear's Cycles run on an automated schedule so teams don't manually set start dates each time; the tool encodes an opinion about how time-boxed focus should work, and teams can toggle it on or off.
→ Teams focus on a short priority list instead of an infinite backlog, without configuring the mechanism.
Common mistakes
Equating flexibility with quality
Making a feature work ten ways feels generous but forces every user to spend time figuring out how to use it instead of doing their work.
Designing for everyone
Trying to serve all users at once yields a very generalized solution that is optimized for no one in particular.
Is it for you?
Best for
Product builders in productivity/B2B tools deciding between configurability and a strong prescribed workflow
Not ideal for
Platforms or infrastructure whose value is precisely user-defined extensibility and customization
From the transcript
“productivity software should be and especially Company software should be opiated”
“what happens is like people start spending a lot of time like figuring things out like how how does this feature work like you can…”
“we like to provide this like good defaults or good opinions like this is how the feature works and this is how the workflow works…”
“my design Mantra is always like design something for someone”
From the episode
Inside Linear: Building with taste, craft, and focus
Karri Saarinen (co-founder, designer, CEO)