User requirements Getting started is simple: the appropriate user requirements for new products

Article Description: from user needs and feedback on the new product out of the Amazon road.

The first step in the birth of new products, is to do the product of the students most care about the user needs, users why to use this product? Before the development of products, experienced market research, user demand analysis, competitor analysis of the rounds through, but for God horse many products after the advent of a lot of things with the previous imagination or different? And some of the products are dismissive of the user instead of flocking?

User needs to get started is very simple, is to meet the needs of users, but it is a bit esoteric. Online vibe of the play said the user needs of the small story believe that everyone has seen, have a mm choose boyfriend, the first man said, I want to take you to the happiest place, the second man said, nowhere to go, as long as with you, everywhere is the happiest. The girl was so moved that she finally chose the richer one. This story tells us, grasps the user the demand, actually is not simple, perhaps the user knows wants what and tells you, but makes the product to understand wrong, thought the user wants other, but missed the opportunity. Perhaps users know what to want, but do not tell you, or tell you the opposite, and you fell into the trap, the results must be unsightly. Therefore, the user needs the excavation, needs quweicunzhen.

The user needs, you dig or not dig, it is there, indifferent. The user does not say, does not represent he does not have this demand, the user describes, does not represent him to understand own this demand, perhaps the user oneself also does not know oneself wants anything, but you gave, he will, he likes, wants more. So user needs can not stay on the surface, need to do a detailed survey before the product analysis, to tap the potential needs of users. Sometimes understand the user needs to use a simple and direct thinking, in fact, the user is simple and lovely, too cumbersome too loud, but the superfluous counterproductive.

Effectively mastering the needs of users can help the new product win at the starting line, for the future development of products to provide a strong help: first, in-depth understanding of users and use of the environment, to find the target users, to find their environment and potential behavior; second, the real comprehensive data analysis and support; again, Quweicunzhen, think one more step, you know. , competitors know that you only need a little more than they know, grasp the inspiration to embody creativity, reasonable choice, like in Noah's Ark to throw away all the burden of things, and finally the courage to do the product to dare to try, so that the opportunity to break through.

Appropriate user requirements to ensure that the new product after the birth of father and mother Love, and the development is the key to determine the life of the product.

Everywhere can hear the product to "small run" of the argument, this statement itself is not wrong, wrong in the implementation. After the product on the line iteration, remove the plan has not yet been designed and developed features, but also a very important part is the collection of online advice on quick fixes and corrections, but the feedback from online advice from where?

The first is of course the user feedback, and then itself online has been tested feedback feedback.

Self-feedback found that the problem can be corrected immediately, and the collection channel is simple. User feedback is not, the site itself, QQ Group, micro-blog, mail and so on, of course, the most important is the site itself to provide feedback portal.

The problem is that sometimes when we think we can get a lot of feedback from our users about our products, we often suffer from cold water. We think that users will use our carefully set feedback channel to provide the feedback we want, we think users will be happy to help us grow, we think that users of the products will be criticized or even curse, but the sad thing is sometimes users have problems with the product will choose silence.

Sometimes the user's endurance is stronger than we think, and the defective places they choose to bypass, find a way to go, if there is no way, then they will give up.

Say, for new product improvement, do not want too much to the user feedback, to find the problem from the data.

From the demand for new products in the market to find a place, in the feedback to the growth and development of new products to provide a reliable help to promote new products out of the Amazon!