Software Engineering psychology 5-awareness of user needs in advance

A few months later, I had blown up several articles in yuanzi. I wrote four articles about some application and precautions of software engineering psychology.
1. Software Engineering Psychology 1 ---- opening
2. Software Engineering psychology 2 ---- about party a project leader
3. Software Engineering psychology 3 --- party a project leader PK Party B
4 software engineering psychology 4-Analysis of Party A's incorrect examples

This time I want to explain how to perceive the user's needs in advance. At first glance, this question seems strange, but I feel that in some periods and occasions, it is necessary
The user's psychology should be properly grasped.
First, at work, a project manager once chatted with the information project owner of a client.
The project has entered the maintenance stage, and the money has been paid to the developer. However, the information project owner of the customer talked about the system's shortcomings and hopes for improvement.
. Of course, the atmosphere is very good, and there is no formal negotiation that is so serious. The person in charge complained about many system problems during the period, but at the same time, he lamented that the project funds were so little,
Strong and insufficient feelings. Of course, this is not the case for developers.
As a result, three months later, the client suddenly informed the developer of the meeting, saying that they could continue to invest money and asked the developer to add new functions and improve old functions. The demand is exactly
As a result, the developer started to discuss the demand with the customer three months ago. As a result, the developer started to discuss the demand with the customer. As a result, the developer took over the project for the sake of money, but found that
The technology is difficult for you and has encountered many obstacles. As a result, you have made a lot of effort with the customer to deny some unrealistic requirements of the customer, my team spent a lot of time learning new technologies for projects, wasting time.
As you can see, when dealing with customers, you should pay special attention to some seemingly immature ideas of the customers, whether they are chatting at the dinner table or talking privately, in particular, attention should be paid to the comments made by the Information owner of the customer. People's psychology is very subtle. Sometimes the opinions and opinions of the customer owner may not have to be put forward at the project meeting, but may have been put forward in some informal occasions, but since he is the owner, although not the leader, how can he be sure that he has no influence in decision-making? As mentioned above,
If developers can make an early observation, they can at least know the future trend of the customer and make a possible decision, which is quite helpful. They can even make the customer less practical.
The idea is eliminated from the negotiating table, and you can even know the ideas of the customer's leadership.
For another example, a team takes over a new system and tries to modify the system. The project owner is still relatively smart. After a bug is fixed, when the project owner is normal, he asks the user about any new demand plans recently, the user's MM also occasionally gives feedback on some of his ideas and desired changes to the customer. Although the customer did not officially place an order through the official order, the developer pays more attention to it, some technical issues were solved in advance, and the results were quickly realized when the official requirements put forward by users were really needed. If he doesn't have a good relationship with the user before and does not listen to the user's opinions or preference when he is idle, the result will be very troublesome.
So, to sum up, when dealing with users,
1. Do not underestimate users' opinions on the system on unofficial occasions. You must listen carefully to them in a timely manner to discover exceptions.
2. Do a good job in the relationship with the customer at ordinary times. If possible, eliminate the unrealistic ideas of the customer as soon as possible on unofficial occasions.