Jun 14, 2022
In Welcome to the Forum
In the annual debriefing season, I spent several days and nights writing my own PPT, during which I also participated in the debriefing process of other students. Overall, the debriefing progress was completed as scheduled, but there were still some twists and category email list turns in the process. Take this opportunity to share the common problems and summary ideas of the work summary, so as to avoid continuing to step on the pit in the future. 1. How to write a year-end summary Normally, the category email list work of the year is carried out and implemented around the personal OKRs formulated at the beginning of the year, so the personal summary PPT at the end of the year should also be explained and reported around their own OKRs. What are the pits in the summary Usually everyone's summary routine is: business data → current stage → what to do → follow-up plan, the process seems to be perfect, but in fact there are many pits in it, which are often challenged: How is the data part linked to the back category email listoffice are more difficult, they are far away from the business, their positioning is to do functions, and they are less business? GMV or Human Effect? In the stage part, what is the overall category email list play style? How many specific actions are there? priority? What is done, what is the result of each action? Follow-up plans, when will the project end? What is expected to be done? ROI of the project, loss or gain When the five moves are made together, the students who report their jobs are often stunned. Usually, the relevant students on the business side are better, because the things they do are executed around the business goals, but the students in the category email list middle and back office are more difficult, they are far away from the business, their positioning is to do functions, and they category email list are less sensitive to data. . 2. How to write a summary Only the method is mentioned here. The object of debriefing is often the boss of the first-level department, and the department boss is not very comprehensive about the details of the project. If he looks directly at your data, he will be confused. Therefore, the relevant background and goals need to be clearly explained at the beginning.