About it services: go to first-line users to find the foundation for system success

Our project manager focuses on the project owners and business contacts of the owners.System PreparationIn the process of requirement, development, and testing, there may be no major problems with such contact. However, if the contact person is always "hidden", the results can be imagined, A lot of information is blocked. Due to information asymmetry, the accuracy and timeliness of decision-making will be greatly affected. If this problem is not solved, it is easy to ignore the following ideas about the System user community:

1. Leader and Management of the Owner: What is the construction goal of the user community, what problems will be solved by the established IT system, and what measurement goals will be achieved, especially inSystem planning phaseAs the system construction orientation, their willingness must be grasped by the project manager;
2. End user of the ownerWhat are the most important issues, how the established IT system will improve their production efficiency and performance, and do not ignore their existence. end users are the Mass Basis of your system, IT systems without mass infrastructure cannot survive for a long time.Production Service phaseTheir feedback and suggestions are an important embodiment of the vitality of the sustainable development of IT systems;

A project is the production management system of the owner and serves the business lines. Because the business lines often have new construction requirements, although the total project is in the production service stage, however, the ongoing business functions require research, development, production, and maintenance. Such system construction poses great challenges to project managers. QA checked the weekly project meeting of the project last time and found that our project manager's awareness of communication needs to be strengthened, and there was no habit of communicating with the contact person of the business team, in addition to weekly reports, the information obtained is not smooth.

What QA and the Project Manager have achievedMonthly Improvement ObjectivesMedium, one improvement in information collection is to collect feedback from five first-line XXX customer managers on the use of the system, and agree that the project manager and the customer manager should adopt face-to-face communication, instead of using a meeting.

One week after the goal is set, QA follows up on the work item, the project manager gives feedback, and contacts F Jun, the organizer of XXX customer manager. f gives us a contact list of customer managers, however, we recommend that you wait for the launch of the system this month to communicate with the customer manager, saying that these customer managers are currently waiting for a launch function.

For this feedback, the QA opinion is that we should stick to the idea of understanding the customer manager before the system goes online, because:

1. It is not the idea that we do not trust F Jun, the organizer of the customer manager;
2. First-hand information is the responsibility of the Project Manager;
3. Based on the situation, if these customer managers attach great importance to a feature to be launched, we should let them know before the launch, and we should attach great importance to their work and opinions, what they pay attention to, we see and constantly improve for them;
4. It is also an important opportunity for them to see what is the deviation between a feature we are going to launch and their expectations;
5. You can also find out whether they care about a function or not?
6. After the system goes online, we can see the difference between before and after an interview with them;
7. It can help the Project Manager overcome the problem of "when I do well and listen to user feedback and praise". The more I feel, the worse I do;
8. The earlier we get user expectations and feedback, the sooner we can make the right decisions or adjustments. Even if we hear complaints and criticisms from customers, the sooner we hear them, the more likely they will solve them.

Don't be afraid to get to know the situation on the first line. Don't ignore this important user group. They are the end users of the system. Their judgment may be sometimes unpleasant, the members of our project team should not be afraid to face it. No one can replace the mass foundation built on them. This is the greatest value of the project team.