Simulation dialogue of important communication scenarios in the project


01 project start

Speech:XX, XX, dear colleagues, hello.

Background:After preliminary investigation, the…….。For this XX project, we have preliminarily arranged the project implementation plan, and have reached an agreement with the business and it. Next week, we will start our XX project research work.

thank:Thank President XX and President XX for their great support to the project.

Statement:Under the painstaking XX coordination of key users’ time, we will start a three-month joint operation and work together to ensure the stable delivery of the project and launch on time.

02 invitation for meeting

Four elements(time, place, character theme)Good morning, XXX. Everyone is free at 10:00. Let’s continue to talk about XXX in conference room XX.

03 meeting report

Address: XX, XX, dear colleagues, hello.

Purpose / Topic:The main purpose of today’s meeting is XX.

Agenda:The agenda is mainly divided into several parts, XXX, XXX, XXX

Summary:Finally, summarize the key points of this meeting:. If there are no problems, this is the end of the meeting. If there are any problems, please communicate with us in time. Thank you for your hard work.

04 how to close a case

Meet the closing conditions:The system is stable and the system problem has been basically solved.

initial results:According to the contract and the regular project implementation cycle, generally speaking, the case will be closed within one month after the launch, which is also a phased achievement of our company.

Better knowledge transfer:After the case is closed, it will be handed over to the after-sales department. The project has a process to support the transfer. The sooner the knowledge transfer starts, the better. Not only our internal, but also your business it, can better participate in the future operation and maintenance. Of course, we can rest assured that we will deal with any problems.

05 requirements meeting

Please attend the meeting on time.

If it is impossible not to participate in or propose requirements, the requirements shall be subject to other business departments.

If the requirements are raised later, the main line requirements can be communicated. If they are not on the main line, the changes shall prevail.