Although we have done user research executive list many times, there are very few who can really do it successfully. Most user researchers fall into executive list a misunderstanding: "emphasis on testing and less on requirements", so how to solve this kind of problem? The author summarizes his experience and ideas of total user research and shares it with you to help you better understand users and improve the decision-making efficiency of enterprises.
It is easy for students in product and operation to executive list start a meaningless application research analysis based on a wrong assumption. This wrong assumption is that "ideas lead to behavior, and If you want to change your thoughts, you need to understand your executive list thoughts first”, but in real life, “people don’t know their thoughts at all”, and when their thoughts and actual behaviors contradict each other, people will first to revise your thinking.
Similarly, after those "so-called user analysis", it may still be impossible to draw some correct conclusions, such as: Why did I modify and optimize the product executive list through research , but very few people paid for it; Why the user satisfaction is that the product is executive list very good, but the sales growth is mediocre; Why do I spend a lot of promotion budget , but users are still reluctant to download and use.