I read an interesting article the other day on how Facebook scale and manage to actually serve 300 million users with immediate updates made to the network of friends. One thing that strike me when it comes to the article is the part where they discuss the introduction of the “Like”-feature. The discussion before the introduction was wether or not it would effect the use of commenting. It did not, it actually added an extra layer of customer interaction to the product, a feature that quickly became very popular. What is most interesting I think is the evolutionary approach to the user experience such a feature is. When you finally have switched your product development to be user experience driven, you also have to make a choice whether or not your changes to the product will take the revolutionary or the evolutionary approach.
A lot of people will always argue that in order to reach the high set goals you have, you have to take on an revolutionary approach to your product development, and others will say that taking on the revolutionary approach to product development is building a product based on facts and requirements that are not the actual facts and requirements that are present when the revolutionary approach are implemented and put into production.
In this post I will discuss and share my ideas on different strategies and approaches to your product development.
