Software Development myth-Medium

Myth 6: As long as you fully understand the user's needs, you can make perfect products. If the user is not satisfied, it is certainly that the development did not fully follow the user's needs.

Anti-myth: There are many vulnerabilities in demand. users do not know the system at all and will not ask for them.

 

 

 

Since there are also black spots in the sun, "things in the world" cannot be defective.

-- Che yevski

 

 

 

AllAll products come from user needs, but it is difficult for users who have not or seldom used the information systemPerfect. Demand is an expectation for a product that has not yet been seen. After seeing the product, you may find that the original idea is inappropriate, or there are still some urgent needs that you did not expect. How can a person ask a detailed question about something he has never understood? Just like a person who has never driven a car, just imagine driving a car, it can only be roughly proposed that, for example, driving cars should basically master the starting, acceleration, deceleration, and braking functions, but in a specific detail, such as why you need to drive in the nearest Lane when turning (another road to a straight-line car), or how important the rearview mirror is to the driver, it is hard to understand it.

 

 

The sun reflected in the sea, like a shining sword, directed from the sky to his side. He was swimming in the flash of the sword, and to be exact, he kept his head in front of him....... "This is a gift from the sun!"Mr. paloumar tried to think so.......Cohabiting-The self, repressed, and self-blaming, however, retorted:"Anyone with eyes can see reflection following them...

---Palymal carvino

 

 

 

 

RequirementThe product angle is different. Requirements constitute the foundation of the product, but some requirements are contrary to the logic of conflict (for example, both security and ease of operation), some requirements will lead to development costs exceeding the budget, some requirements need to be further refined. Naturally, in the process of communication between the two, there will be information loss or deviations, such as the product does not meet the requirements, or the demand was not clarified at the time, and it needs to be changed repeatedly, however, this cannot be totally attributed to one aspect, but the communication is not thorough enough and the problem is not considered from the perspective of the other party. Complaints cannot solve the problem. If you can consider the problem from the other party or the global perspective, it is possible to create new values from both sides.

 

 

 

The gods punished sisiverand kept pushing a huge rock to the top of the hill, and the stone rolled down the hill due to its own weight.I think there is no more severe punishment than carrying out such ineffective and hopeless work... The struggle he wants to fight on the top of the hill is enough to enrich his mind. We should think that sisiver is happy.

--- Camus in the myth of westphus

 

 

Slave ProcessFor example, a detailed understanding of the requirements is inherently unrealistic. Therefore, demand should be a dynamic thing. It is a dynamic product that is constrained by users' original needs, analyst refining, designer restrictions, and time tempering. Rather than eager for such a perfect user existence, or a ready-to-use development experience, it is better to let users see this system step by step, let him raise questions about the existing system and further expectations for the future system from all the current systems, and develop and improve the system iteratively based on this feedback. Let users participate in the soul of system design, let everyone interact, this can at least make everyone satisfied with the system.