Everyone is busy, so meeting topics, topics, and business email list outcomes need to be clear and communicated in advance. Taking the above example as a warning, not only the progress and resources are affected, but also the character value of the organization personnel.
If the character score is too low, it will not only affect the organization of the meeting, but other work will also be difficult to carry out within the team.
2. Prepare meeting materials
The requirements documents, prototypes and other materials used in the requirements review meeting need to be prepared and sorted out in advance. You can't just rely on one mouth at the meeting, and let everyone else make up their minds at the meeting.
3. Confirm staff time
Personnel and time are the basic elements of a meeting, and an invitation to a meeting can only be issued after confirmation.
Participants: The personnel who review the requirements generally include UI, R&D (front-end, back-end, mobile), testing, and operations. According to the scope of the requirements, other relevant personnel also need to participate.
Meeting time: As the number of people increases, everyone has their own business, and it is difficult to coordinate the time at this time. We first confirm the attendance time with key stakeholders, and then coordinate the time of other personnel.
4. Multiple channels of notification
Meeting invitations will generally be notified separately via email and WeChat. The email notification is formal and easy to trace the follow-up events, but the attention is not enough. Therefore, after the email notification, the stakeholders will be reminded again on WeChat.
Please attach the meeting materials and key notes to the email meeting invitation, so that the meeting and staff can understand the information in advance. How to write it is not discussed here.
On the day of the meeting or 1 hour before the start of the meeting, wechat reminds the relevant participants again to avoid being busy with other things and forgetting to attend the meeting.