Product philosophy

A product should be simple to use. Users should never have to look for help to do something. That being said, a link to the help center should be present on every screen in order to assist users if, unfortunately, the UI is not clear enough.

We should always iterate. The first version of a feature should be an embarrassing but very functional solution to a problem or a need. Then, using a fast-paced build-measure-learn feedback loop, we can create a better version.

We should always start with the problem, not the solution. We should focus on well-formed problem statements in order to understand the core of the issues faced by the user. Only after a long process of thought can we fully get the big picture and envision the solution.

As much as possible, you should resist adding configuration options or settings. It's much better to have smart defaults than to pollute the product with options. Every option adds complexity in terms of engineering, testing, and understanding. One of the personality traits of a project maintainer is to please people. We want users to love what we've spent nights and years creating. So, every time we receive a feature request, it's only natural to try to implement this feature, especially if it's about an option, so we give users a choice. This is not a good strategy. We should resist, as much as possible, creating a situation where your product is so complex that it has become unmaintainable. 37Signals has a great article about saying no . Read this.

Finally, we will never, ever implement a feature tool that will remove the need to make the effort of keeping healthy relationships. What do I mean by that? Having a social circle requires time and effort. There is no easy way in for having great relationships. PeopleOS will help you document but it won't replace the need to, you know, actually work on your relationships.