A choice, not a limitation
Most software grows by addition. A request comes in, a feature ships, and over time the product becomes harder to learn, slower to use and more fragile to change.
We try to treat each new feature as a decision with consequences, not a default. Keeping a product small is something we choose to do, deliberately and repeatedly.
The cost of every option
Each setting is something a person has to understand. Each screen is something we have to maintain, test and explain. The cost isn’t paid once at launch — it’s paid every day after.
The best feature is often the one that makes another feature unnecessary.
How we decide
Before something is built, we ask three questions: what problem does it solve, who has that problem, and what would happen if we didn’t build it. If the answers are vague, the feature waits.
This doesn’t mean saying no to everything. It means saying yes for a reason we can explain.
What this means in practice
Fewer screens. Sensible defaults. Interfaces that explain themselves. And more time spent making the things that remain fast, reliable and easy to use.