Responsibilities of the project management and implementation manager-a series of articles on project management

The scope of project implementation and project management is relatively small, and the differences between product managers and project managers are also very different. Project product R & D is closely related to project management and is a process of planning and implementation. The relationship between project implementation and project management is also close, which is a process of implementation and deployment.

 

In actual work, project implementation has to do more than just deploy the concept. According to my understanding, project implementation is the pre-sales, sales, and after-sales work mainly around these aspects. Pre-sales refers to the work done before the project is launched. It mainly involves business activities, including communicating with customers, introducing projects, and managing contracts with customers. During sales, it is similar to project management, that is, communicating with the customer, describing the progress of the project, and confirming the project requirements with the customer. After-sales is the work done in the project release trial run or the project progress that has been paid for acceptance. Therefore, the implementation manager has to do a lot of things.

 

This section describes some of the job skills required by the implementation manager.

Pre-sales skills:

1. Company introduction.

Before you start, you must first introduce your company to the customer. Briefly describe the company's qualifications, project solutions, and customers. According to my own understanding, it also takes some time to make some personal introductions. This mainly enables the customer to have a comprehensive understanding of the company and the individual, and increase the customer's self-confidence and expectations for the project.

 

2. Pre-sales Research.

Research is an important part. Pre-sales Research is equally important. Generally, you need to introduce some related products of the company to the customer first. If not, you need to communicate with the customer like a field expert. In this case, the implementation manager must have certain knowledge and experience in this field. The pre-sales survey is similar to the project manager's requirement survey, which communicates with the customer and records the customer's requirements and some public requirements in the field. Therefore, the implementation manager needs to make some implementation preparations before the investigation, in order to integrate into the customer's needs as soon as possible, to better complete the pre-sale research work.

 

3. Pre-sales solutions.

The pre-sales solution is similar to the project solution book written by the project manager, that is, the project solution book is used as a blueprint for the pre-sales solution. Therefore, the pre-sales solution book is very important. It can reduce the content of the project manager's solution writing. Pre-sales solutions must be standardized, and the customer must be able to understand (in fact, an important description of the survey requirements ). That is, the solution must be understood by both parties to reach a consensus and signed and confirmed by the customer.

 

4. Product demonstration.

During the pre-sales process, you also need to demonstrate the company's products (this refers to mature products, that is, projects that have already formed the company's products), that is, to introduce the products to users, let the customer have a certain understanding of the product. At the same time, the demo process is actually a verification of the same importance of product knowledge in this field. It is also a process of training customers. The demonstration process requires patience, just like internal training. Try to give the customer a high-level understanding of the product in the shortest possible time, and improve the customer's satisfaction with our product. In short, we must make preparations.

 

5. Technical exchange.

Several technical exchange meetings should be held during or after the product demonstration. Technical exchanges are primarily conducted with customers to verify the Product Domain integrity, solution methods, and Operation humanization. It is also a way to communicate with the customer. At this stage, the implementation manager must control the technical direction and instruct the customer to explain the functions of the product as much as possible. Of course, technical exchange also communicates some of the technologies used by the product with the customer, in this way, after product acceptance, the customer's R & D team will be able to put forward more and better requirements on the features of the product as soon as possible, and be able to perform secondary development and other operations on the product more quickly.

 

6. Company inspection.

If possible, ask the customer to go to the company for an inspection. It mainly allows customers to understand the company's corporate culture, cultural atmosphere, company norms, and products, and increase the customer's sense of identity with the company. This study plan is generally conducted by the company's Ministry of Commerce. It is sufficient for the implementation manager to accompany the presentation.

 

7. User test.

Customers inspect the company. Similarly, we also need to examine the users. On the one hand, we need to make some research on the user's needs, and on the other hand, we need to know what problems the user has in the field of the product. This is the most direct process of understanding the user's needs (note: Here the user is the most direct user of the software, not the customer, that is, the main person in charge of the project ).

 

Sales skills:

1. High-level communication.

In the process of selling services, it is very important to communicate with senior executives of the company and the customer's senior leaders. It is mainly to gain the trust of the leaders and give the leaders full confidence in the implementation of the project, so as to improve the satisfaction of both parties. This is an important process for promoting Project R & D and implementation.

 

2. Start the conference.

After the project survey is completed, the project should be started after there is a project solution proposal. Project Initiation mainly involves the allocation and integration of various resources. Assign permissions to the project manager and start to assign personnel to build the project team. A milestone that begins the project.

 

3. Conduct research.

In fact, after the pre-sales research is completed, it does not mean that the research is over. The research work is throughout the entire project process. On the one hand, it is a process of verifying the customer's functions completed by the project, and on the other hand, it is also necessary to respond to the customer's demand change process. Then, we will conduct research on the implementation of the project to prepare for subsequent implementation.

 

4. Process user requirements.

The implementation phase also needs to meet user needs. Because, when the project goes to the trial run stage, the direct user of the software is the user. Therefore, at this time, users need to put forward relevant opinions and suggestions on the product. This allows products to better serve users.

 

5. Prepare implementation solutions.

Project implementation is a relatively complex process. The implementation of the project also requires the preparation of solutions (this is estimated to be omitted in many projects ). In fact, the solution book is similar to the project change. Like the outline design of the software.

 

6. Prepare the implementation plan.

After a solution is prepared, an implementation plan is prepared. It mainly determines the implementation time, location, characters, events and other elements. This is the same as the actual project change. A document is prepared to allow the change personnel to complete the change smoothly. Similarly, the implementation plan is the preparation for the implementation manager or implementers to complete the project implementation more accurately and better.

 

After-sales skills:

1. Perform user training.

After the project is launched, user training is required. The training can be conducted by the project manager or the implementation manager. Because the project manager and the implementation manager have a certain degree of understanding and experience in the project requirements and fields. Before conducting user training, customer training has been implemented first, which has been introduced above. The purpose of user training is to allow users to integrate into the product more quickly. It is also a way to communicate with users. In this way, some user requirements for function changes can be collected during the training process to prepare for secondary product development and practical user-friendly operations.

 

2. On-site promotion.

After the project is implemented, you also need to promote the product. This promotion not only includes local customer promotions, but also applies to other customers in this field. The on-site promotion mainly focuses on the product overview and the introduction of the main features of the product, so that the customer can have a certain understanding of the product as soon as possible.

 

3. Project acceptance.

After the project implementation test run is completed, the project acceptance stage is reached. At this stage, the project has basically no requirement research or actual R & D. If the customer needs the product, we recommend that the customer prepare for the second phase of project development. Project acceptance requires the participation of relevant acceptance project teams, including the customer's experts, implementation managers, business managers, and project managers.

 

4. Project refund.

With regard to the remittance of the project, this is the major milestone for the completion of the project. Because the project is completed only after payment is made. In project management, the project manager is responsible for the collection of projects. However, it is more appropriate for the business manager to implement the collection.

 

Finally, the content of project implementation is roughly described above. This article aims to summarize some of the skills required by the implementation manager and give the author some experience in project implementation. If it is helpful to everyone, it will achieve the goal of making common progress.

 

Responsibilities of the project management and implementation manager-a series of articles on project management