Questions about product design-less effort is more expensive and less expensive

When making products, everyone must have an impulse to always think about how to perfect the products. As a result, once a product is achieved, it is indeed a good product, and we have a high sense of satisfaction and achievement. However, we all know that a product cannot be perfect at once, this is especially true for Internet products. Why? For example, if your website is only used by a few people, you have created a large system to monitor how users use your products, obviously, they are useless in the cutting edge. However, a product is not necessarily a good product, but it is useless. Therefore, when making products, we need to have a steadfast spirit. We only need to be sufficient, not the most comprehensive, and we must adhere to the principle of small steps to run quickly.

Take the user behavior analysis system as an example. The following methods can be used:

1. At the beginning, we established a perfect system to monitor all aspects of the system;

2. Formulate a scalable implementation scheme, with several key points in mind.

Advantages and disadvantages of the first solution:

1.1 how to collect all monitoring sites? Because a product is designed by multiple people, it is impossible to integrate all the collection items at the moment.

1.2 even if all the points are collected, what is the purpose? It may be said that you can check it whenever you want to use it.

1.3, but when do you want to use it? Will it be used frequently?

After several successive issues, we will find that this solution looks powerful, but it may have done a lot of useless work. At that time, a lot of data will be put there, but it will not play its role. It wastes valuable server resources and has a great impact on client efficiency.

Therefore, we need to break down the letter and return to the most fundamental thing:

1. Why is this system? The answer is "understanding users' behavior habits ". But this is not the reason, so we need to continue to ask "what do we do after we understand it? "This problem requires a feasible solution to support why the data should be monitored. This ensures that appropriate measures can be taken immediately after monitoring data.

2. Who is responsible for this system? This is a good answer: Our product designers and UED staff.

3. Is it what the demand side wants? Therefore, this issue requires the demand side to provide the demand, the basis, and not created out of thin air. Take it for granted to monitor this, monitoring that, the demand should be justified.

After some pushes, we can determine the scope of the demand to monitor user behavior to solve the current problem, rather than large-scale and comprehensive monitoring. Thus, the second set of solutions is formed.

From: http://www.gixing.com /? P = 33