Quality and beauty

There is enough terrible software in the world as it is. Enough untested, half-baked features released to meet arbitrary business deadlines. Enough spaghetti code and quality compromises. For our users, Sustainly should be synonymous with quality, and for us, something to be proud of.

Beauty is a way too overlooked quality in software: Beauty attracts us to products, makes us want to return, increases ease-of-use and removes mental barriers. Also, There is no justification for adding to the world's ugliness, when we can add beauty instead.

Fail fast with users

Quality doesn't oppose swift iterations and feedback-driven development; it complements them. As long as users knowingly are using features in beta, we can improve quality based on data and feedback without compromising with the overall quality of the product.

Don’t compromise

The easy option always is to compromise. If there’s a deadline on the roadmap, an important meeting coming up or something else that would compel us to release a feature before it’s ready, we need to check back in with our values.

Do one thing exceptionally well, not multiple things ok

A product excels when it does one thing exceptionally well, not when it does multiple things adequately. That’s why we should always opt for one exceptional feature over a handful of mediocore ones.