Project management miscellaneous-what should I do If Party A's business representatives have poor capabilities?

In the project process, Customer business representatives play an important role. If a customer representative is proficient in business and has strong coordination capabilities, the project may get twice the result with half the effort. Otherwise, if you do not solve business, capability, mentality, communication, and other problems, the project may fail. Next, let's analyze the role of the customer's business representative.

1. coordinate business and needs: After receiving the requirements, the project team needs to communicate with the business department, hoping that the customer representatives of the business department can understand the real functions behind the requirements.

2. Communicate with the project team: during the project process, communicate with the project team from time to solve the project team's business problems and put forward their opinions.

3. Communicate with Party A's project manager: if the customer has a project manager, the business representative must communicate with the project manager regarding technical issues or other business-related issues.

4. Report the project progress to the leaders: Report the project progress and existing problems to the leaders from time to time.

5. Responsible for project launch implementation, training and promotion

First, let's give a positive example. I once worked on a project. The customer's business representatives are very competent, and the Department's business is well understood. The customer's own business is even better, I have some knowledge about computers, so this project is smooth from the very beginning. This business backbone can describe complicated businesses in a simple and common way that programmers can understand, from the beginning of the requirement to the confirmation of the Function Point, to the final test, it is better to verify the data accuracy, he can even find out where the data difference in the reports provided by the system may be. Although the system lacks the ability to fully grasp the project, it also brings great help to the successful implementation of the project.

Of course, not every customer's business representative is like this. Some of them have general business capabilities, have no overall picture, and are not clear about the business. They like to complicate simple problems; some of them are forced to participate in the project and handle the issue. At this time, the consequences can be imagined if they are taken by their noses.

Most of the time, the project manager or other key personnel will think that since Party A's business representatives are dispatched by Party A, we must take the customer as the center, and Party A is right, the project team does what the business representative says. In most cases, because the business representative has limited capabilities and does specific work, he may be familiar with a piece of business that he is responsible, I do not know much about the overall business involved in the project, and ignore the seriousness of the Project. When I analyze the business, I often make unreasonable demands during the project process. In addition, the project team knows little about the business, this leads to a series of problems in the project process, making the project not a successful project.

What should the project team do when encountering such customer representatives with poor business capabilities?

Since the status quo cannot be selected or changed, we can only change ourselves..

1Attitude: First, we should not despise him because of its poor ability or lack of cooperation, but should respect him more. Second, we should hold a problem-solving attitude, rather than shirking responsibility when encountering problems, putting the project team and customer business representatives on the opposite side, no one wants the project to fail.

2Action:

1) if the business capability is average, the project team should not rely on the idea. In many cases, the project team is passively accepted and is held by customers. The key is that the idea of dependency is at odds, and the business itself knows little about it, so we have to rely on it. It is too late to find the dependency. The project team should learn more about the business field, start from the concept, understand the main business and master its workflow. Only when the water in the bottle is full can you discover the customer's needs. At this time, you should actively communicate with the customer and confirm your ideas, and guide the customer, discover the real needs (which will be involved in subsequent articles on how to obtain the requirements), grasp the requirements, and half of the project is successful.

2) If the ability to cope with the problem is good, we must be sincere and persistent. We should try our best to integrate it into the project, but we must also understand its difficulties, some business representatives are part-time participants in the project. Enterprises are basically a machine, and there is a mess in their own business. Where Are there other things to deal with in the project. In many cases, we can reduce the customer's extra burden. For example, when we submit the test data to the business department, if the test data is accurate, authentic, and objective, I think it will be better if the customer sees it at a Glance instead of looking at a bunch of messy things.

3) If you have unreasonable requirements, the project team, especially the project manager, cannot accept them blindly. Instead, they must learn the methods and methods of rejection. You must know that the company is sending a salary to the project team members, it is only possible to satisfy the customer's interests on the basis of meeting the company's interests.

4) others do not work with each other. There are very few such problems. The project team should not compromise and report the problem to the superiors.