The last time to the customer unit, the module's developer and the user directly communicates the demand, listening to the changes in demand, the effect is very good, so that one representative does this thing is significantly improved. There is a suggestion in the exchange of software demonstrations and demand: 1. When we go to the user's demo software, it is best to show the actual effect of software. Sometimes there will be only language descriptions, but don't do it. This is not conducive to the user discovery problem. Recommendation: If the time is proven, the operation is made to make each feature to see the effect of actual use, and can be demonstrated as an example of the user's actual workflow, so it is easy to use for the user's understanding and acceptance. 2. Demonstration to display the features of the software to users, such as: There is a QuickSelect control in our software. Just enter the first few numbers of the application number, then press the cursor key to select, and finally the carriageway can be called out. data. However, demonsions may not understand its skills. When the demo, the mouse keyboard is used together, and the user will make the user's cumbersome impression, and this control characteristics (Quick) is not reflected. Recommendation: Before the demo gives the user, you must communicate more with developers, not only to know each function, but also know how to operate each function, and clearly describe these techniques when using the software instruction manual. 3. From the beginning to the customer unit to collect demand, there has been such a phenomenon: When the user is talking about each function or a new demand, we generally just record, or ask if you don't listen to clear content, not dare to Users think about it, ask a little more, because this sentence is in the case, how to do new demand! So the user said, we do a little, but we don't realize that this process is the user's idea, that is, the user doesn't know how to do it, the user is inadvertently in our next step. To achieve his thoughts, are we paying too much? Recommendation: Users put forward new needs, what is our first question is what the user's purpose is? Know the purpose of the user, we can help users analyze the problem, find a way we have a minimum workload and meet the user requirements. We have to guide users to say demand, don't be afraid that the problem will lead to new needs. We don't think more about users when they organize demand, and the demand may be less, but users realize that a feature is necessary, we will change the amount of work paid to the original architecture than the original design. . So we have to dig the potential needs of users.
