# Product philosophy
### **Simple is better than complex**
The temptation to add more information to help the user make decisions is hard to resist, but it often ends up working against the user. Provide all information that is needed to make decisions, but no more. In the battle between richness and simplicity, bias towards simplicity.
### **Lean is better than heavy**
Nothing renders products more unusable the way feature creep does. The answer to every new problem need not, and should not, be a new feature. Converge all solutions to the minimum number of solutions possible. Design a new feature only if a problem cannot be solved by a feature that already exists.
### **Mainstream is better than special**
Avoid power features as much as possible. If a majority of your users are not going to use it, it’s probably not worth it. Think twice before working on a power feature. If the [Pareto Principle](https://en.wikipedia.org/wiki/Pareto_principle) holds true i.e a feature that might be used by just a handful of users, but it might take a majority of development time, it’s probably best to leave it out.
### **Familiar is better than new**
The interface should not feel alien to the user. It should create a sense of familiarity and connection the first time the user sees it. A good approach might be to leverage the familiarity of an excel sheet, something most companies already use to manage OKRs.
### **Comparable is better than stand-alone**
OKRs by their nature are dependent on multiple other OKRs. Being able to compare the impact of one OKR on the other is quite important for clarity and prioritisation.
##