When the project is off track

It is difficult to change roles.
In a project, I do system analysis, Project Manager, and programmer. To put it simply, this is a one-person project. However, in the project, I encountered an issue that was not easy to reconcile:
The user does not understand the system and raises some questions from the standard perspective. After receiving the problem, I spent a lot of energy on system analysis. However, the analysis results showed that many of the user's requirements were unreliable, and some were self-contradictory.

After some thinking, I think the real contradiction is that the user does not fully understand the system, and he only wants his convenience and benefits. It ignores the interests of other colleagues and companies. Therefore, users prefer to raise requirements, but are not responsible for the requirements. When programmers are busy, they cannot catch up with these changes. In this regard, my personal experience has two methods that are very effective-adding a buffer zone and handling some problems in the bud.
The specific method is that the project has two windows (similar to the interface in the program ):
Program Project partyAdd a project manager and a system analyst to ask these people and users to discuss their needs without the involvement of programmers. All-round consideration of the system separates the needs and real needs of some users under brainstorming.
User SideAdd a project manager and a user representative. For the selection of project managers, you must find a useful role. Otherwise, when the application is actually launched, it will still appear when someone finds a pick-up. (in many cases, it is not a pick-up program, but is ignored psychologically and requires some comfort. It's just like a child crying and wanting his parents to get him ). For user representatives, more training is required. You taught user representatives and asked them to teach them again and again.

There is only one purpose: to focus on essential issues and reduce the interference caused by noise. Reduces non-essential complexity to the lowest possible.

I have seen many projects and the Project Manager has not handled these noise interference well. These noises make the project deviate from the track. For those projects that deviate from the track, you cannot close your eyes and move forward. This will only make the project go farther and farther, and the noise will increase, eventually, the project aborted in these noises (including buzz.

The current situation is that I do everything by myself. When talking about projects, I thought I was a programmer. Face changing ~