We started this because the tools we used every day felt like they were written by committees, for committees. What we wanted — what most people quietly wanted — was a smaller thing. A thing with a point of view.
So we built one.
We think about this work as editorial, not engineering. Every feature goes through drafts; every draft gets read out loud; every sentence earns its place — or it comes out.
The result is not for everyone. It is for the people who notice.
Every feature is a promise — that we'll maintain it, that it will work when you need it, that it won't get in the way of the next thing. Promises compound. Eventually the thing that was supposed to help you starts scolding you instead.
So we cut. Constantly. Ruthlessly. In public.
Continue reading →It's not a feature problem.— From the essay “Against More”
It's a taste problem.
We think of the UI the same way we think of a paragraph. There's a rhythm to it, a rise and fall. The user should feel led — never hustled, never left wondering where the sentence is going.
This is why our buttons are boring. It's also why our empty states aren't.
Continue reading →One feature that sings beats ten that mumble.
Copy is product. Edit it like a cover line.
Someone else will read it tomorrow — probably with a headache.
An argument you avoid becomes a feature you regret.
Ship the whole thing. Half-built is worse than unbuilt.
Every answer we give should make the next question easier to ask.