In the demand research, even if you are very experienced in this type of business and very sure, don't underestimate the questions and requirements put forward by customers when conducting demand research.
I mentioned the “empiricism” of demand research before. Generally, when conducting project demand research, there are usually members who are familiar with the business of the project industry. In many cases, empiricism is very useful, but sometimes, extremes will reverse, and too much reliance on empiricism will often fall into the trap of behind closed doors, burying terrible hidden dangers for future system design and development.
In any case, the user you are conducting research is the person who will use the system directly in the future. No matter whether he is using manual processes to complete business work or using an older software business system to complete business work, he is always concerned about the business. With a relatively deep understanding, or his understanding is not comprehensive enough, he only pays attention to his own one-third of an acre of land, but on this one-third of an acre of land, we must respect users.
The industry norms are general, but in the business operations of specific departments, they still have their particularities. You must pay attention to these particularities. Don’t let your previous experience take it for granted, and use your previous experience to achieve it. It is very likely that it will not be worth it.
In addition, sometimes, users will feel that the questions and requirements raised by users are too strange. In fact, this is just a misunderstanding and poor communication caused by standing in different positions.
What users care about is the business, how to use the new computer system to help complete the work and reduce their workload, instead of increasing their daily workload, so most of the time, their perspective is from their own responsibility Start with the business part, pay attention to this part, and don’t think much about the connection with other departments, business, and overall considerations. We have a lot of experience even in the industry business, but more often, we have a good grasp of the big concept, in various departments, the connection between various businesses is clear, the specific details must start from the grass-roots users, Can't be sloppy. Even from a technical point of view, it is not possible to think that the requirements put forward by users are strange.
What we need to do is to get as much as possible from users about their business descriptions and details, and then rely on our own experience to organize and plan, and become a solid cornerstone of system design.