How to open a project start-up conference

How to open a project start-up conference

The launch of the project is a crucial step in the implementation process. At the start of the project, the equivalent of the implementation of the team's first collective appearance, this debut, if successful, although can not be said to determine the success of the project, but for future implementation has laid a good foundation, but if unsuccessful, the project is not successful.

Why do you say that? As we all know, under normal circumstances, the project start-up conference will have the enterprise "number one" to the scene, together with the management staff at all levels and the project team members, generally have more than 20 people. Many of these people are not involved in project selection, so they are not aware of the companies and people who are implementing them, and this is the first time they have seen and understood the implementation consultant. It's like we love each other for the first time, first impressions are very important.

First impressions include: one, the manner of speech embodies professionalism: this actually requires long-term accumulation, there is not too much skill to say, but for the project start content, it can be well prepared to fully reflect the professional. Here's what you want to mention: 1) Be sure to emphasize risk management at the start of the project. This first begins with the "cooling down" function mentioned in the previous article, and secondly, it can also reflect the professionalism of the consultant. 2) The rationality of the implementation plan: this mainly relies on the experience and the understanding of this customer, repeated consideration, to obtain a reasonable implementation plan. Personally, the implementation of the plan is the soul of the implementation of the project, and in practice, most of the implementation of the consultant only to the original customer's implementation plan after the copy, after a simple date modification, half an hour to complete.

If you are such a habit, then advise you to change it. In formulating a project implementation plan, first of all, do not say the preparatory work (such as understanding of the customer's situation and the implementation of the system module, etc.), light production of a project schedule will take half a day to the time: I will carefully consider the number of items on hand not to crash (this is a basic requirement, but if the time is short, is often the case of two project crashes during the actual operation, and more time will be placed on how to fully guarantee the completion of the Project key node (milestone) buffer time. For example, the demand research phase began on January 1, based on experience, estimated to be about 3 days of time to conduct on-site research, another 2 days or so of time to collate documents, it is very unwise to submit the demand research report on January 6, The right approach is to carefully assess the customer's level of coordination (because the research needs to be closely aligned with the customer), and set aside a 1-2-day buffer time (which is, of course, allowed under the project's entire cycle).

Second, to let the customer know that this project is you in the lead, you are the creator of the game rule: In general, I will ask the customer's "number one" at the meeting to read out a well-prepared "project rewards and Punishments system", in the reward and punishment system, to fully reflect the implementation of the project leader: for example, all project team members must , the assigned tasks must be completed on time, otherwise, not only the direct responsibility of the people to be prosecuted, but also the direct boss of the penalty. This will prevent the enterprise from delaying the project process with the "busy work on hand" as an excuse for the implementation process.

In fact, to sum up, there is no more than two objectives: one is to embody professionalism, and the other is to make the rules of the game. The role of professionalism can be illustrated in such an example: in the Obstetrics and gynecology room, if the doctor is male, if the doctor does not wear a white coat, the patient will not cooperate with the examination. Because in the eyes of the patient, wearing a white coat is the first symbol of professionalism.

And the role of the rules of the game, there is a story: a fool who can not marry a daughter-in-law and a neighboring village to marry not to go out of the provocative lazy woman by matchmaker to make a couple. A week after marriage, old father-came to see his daughter and son-in-law, to his surprise, his pungent lazy daughter and changed a personal like, fool son-in-law what to do, obediently waiting for a fool son-in-law. Old father-busy quietly asked fool son-in-law, with what way the daughter to uniform (because old mother is same, old father-has endured for decades). The fool said: Nothing, the wedding night, the groom said to the dog at home, "give me a wash feet water", of course, the dog did not understand, so the groom hand up the knife fell, the family's dog to cut, then, the cat said, "Give me wash feet water", the cat of course also do not understand, so, the groom again hand up knife fell, the cat also cut; Turned to the bride, said, "Give me wash feet water", the bride has been frightened pale, immediately obediently to wash feet water. Old father-Heard, suddenly, then, immediately go home to do the same. When he used the same method to cut off the cat, and then ready to say to his wife, suddenly found that his wife has taken a bigger kitchen knife out of it, frightened old father-fled.

Why the same method old father-not work. The reason is simple, because the fool son-in-law is the first time to become the rules of the game, so he can control everything, and for old father-, the rule is the wife, in this case, want to reverse, is impossible.

The same is true for project implementation, where you have to be a game-changer, not a participant, at the start of the project.