The method of judging the core requirements has been mentioned, so when we enter the design and development stage, what is the basis for decision-making and judgment?
Case: We are working on the deployment and email list registration functions of a product. After the design of the scheme is completed, the following problems are found during the review:
The performance test suggested that if the container that comes with the deployment package is replaced from tomcat to SpringBoot, the startup performance will be better;
Product operation: It is expected that there will be richer reminders for registration, which will be more user-friendly;
R&D feedback: Some functions in the design may not be implemented.
Faced with the above problems, how should we make decisions?
You can't just make a decision by slapping your head, and you may not be able to make good decisions if your head is too big. When making decisions, there needs to be a marker, and this marker is the goal of product design.
When a lot of suggestions are input, and the pre-set design goals are aligned (unless the goals are problematic, the goals should be calibrated) to make decisions, the thinking will be much clearer:
Functions that need to be added, evaluate whether they are necessary to achieve the goal, if not necessary, cannot be easily added;
The functions that need to be reduced, evaluate whether it is necessary to achieve the goal, if it is necessary, it cannot be easily reduced;
After evaluating the functions that need to be modified, whether they can still achieve our expected goals.
Goals are the compass for our decisions.