
Sign up to save your podcasts
Or
One thing I learned in building products is to always question the core of your product and if you need a feature.
Each feature initially decreases the user experience. First it adds only complexity (for the UX and for development). So the benefits of the feature have to be significantly higher to justify the added complexity. That is why I became very rigid to decide if a feature should be added.
When I was talking about datatasks with other people I recognized that two features I had planned needed more explanations. Especially why they are in datatasks.
So I decided to remove them (and eventually build own products with them at the core).
One thing I learned in building products is to always question the core of your product and if you need a feature.
Each feature initially decreases the user experience. First it adds only complexity (for the UX and for development). So the benefits of the feature have to be significantly higher to justify the added complexity. That is why I became very rigid to decide if a feature should be added.
When I was talking about datatasks with other people I recognized that two features I had planned needed more explanations. Especially why they are in datatasks.
So I decided to remove them (and eventually build own products with them at the core).