what is the user "G-spot"? I’m here the G-spot is defined as: the user’s cool, which can let users themselves and feel very comfortable place! This is little different approaches but equally satisfactory results with the real life of the G-spot Oh, you know
G is a necessary condition for the success of
successful Internet products, all are to meet one or more of the G-spot users. WeChat’s initial success stems from its ability to send voice mail, which makes use of the user’s lazy nature, making it easy for users to use, and then cool. The success of the QQ address book stems from the fact that it can synchronize the address book to the cloud. At the same time, it can avoid the loss of the address book, and the user must be very comfortable with it.
generally speaking, the G-spot is the user’s a demand point, when the user demand is satisfied, he naturally will have a great feeling, and great degree depends on the interaction design of specific products. On the other hand, to seize the user’s G-spot, products will succeed? This is not necessarily the
Kozmo.com: online storage and delivery service provider. For city people, Kozmo.com is really cool and convenient, you can order everything from movies to snacks, and then you can get them to your home in just an hour. Cool? Definitely cool, and that’s what the user really wants. But for Kozmo.com, this has become a mission impossible! The business extended to 7 city, Kozmo.com found that travel over land and water to send a CD or a pack of gum is just terrible! Finally had to face the consequences of failure.
so that users looking for a G-spot, do when the product is in the primary consideration. Your products to meet the user needs the user to use what? Would it be cool? If you think to find the user’s G-spot, go and see your product really can let the user get up so cool. How to try? There’s a way:
according to the G-spot, began to do product concept map, then according to the concept map build the basic framework of product, function modules of the product, and then according to the design of each functional module interaction. If there are a lot of functions, it might be necessary to do versioning and divide the functional modules into several classes according to priority, and then iterate over them. Then look at the user’s feedback and data during the version upgrade, and then adjust if the data is not ideal.
this should be the product design process for most of the product people. Is this really the right way here? Before we answer this question, we might as well look at the following way,
MVP development model – streamlined, direct, fast
" is for the above