Replay, derived from the terminology of Go, refers to the record of replaying the game after the game is over, in order to check the pros and cons of the game and the key to gain and loss.
I believe that many people have the experience of review, such as review and reflection after a project, such as a day's summary.
The essence of replay is to learn from experience.
2. Why do you want to reset?
If you are like me, a person who wants to continue to grow , then I believe that you are not willing to fall in the same place twice, we all hope that the next time will be better, and recovery is the secret of turning experience into ability , to guide us to act better next time.
The current era is changing too fast. If there is no precedent to follow, then the most effective way to iterate is to learn from your own experience , to continuously improve and approach the goal.
3. How to reset?
Relying on the PDCA cycle:
Plan → Execute → Check → Process → Next Cycle
According to the size of the review items, my strategy is: immediate review of small matters, and periodic review of major events.
1. Instant review of trivial matters
The small things here refer to things Latest Mailing Database that require less energy and consume less time, such as a meeting or a communication, which can be resumed immediately after the end of the matter.
The picture below is my speech on January 13 this year. There is a simple post-speaking review at the bottom, which summarizes the advantages and disadvantages and suggestions for improvement. I will take it out and take a look before the next speech. Because speaking is not a particularly important thing to me (my speaking frequency is once a few months), so I don't review it that much, and you can adjust the degree of review according to your actual situation.
Back to PDCA, the stage of review of trivial matters is in [check] and [action]:
[check] stage: explore the advantages and disadvantages
Advantage => Continue to maintain/continuously optimize
Weaknesses => think of solutions, develop implementation plans
2. Staged review of major events
The major events here refer to the things that put a lot of energy into and attach great importance to. I generally position the major projects in my work as major events, and the others include annual review and so on.
Generally speaking, the battle lines for major events are quite long (for example, in a recent project of mine, it took almost 6 months from product design to demand launch...), if you wait for the whole thing to be completed and then resume the review, there will be two Disadvantages:
First, the time is too long, and the situation at that time cannot be clearly reviewed during the review, which may cause omissions;
Second, if each stage is not reviewed, it may lose its guiding significance for the next stage.
Therefore, the review of major events needs to be carried out simultaneously in the [do] stage of PDCA