preface
Main focus this week in a very big demonstration, real one minute on stage, the audience ten years of work, presentation time is half an hour, and I am responsible for the relevant also for 10 minutes, the whole time for 3 ~ 4 days, when the key is in the process encountered a lot of surprise, now finally have a little time to do the review and the closed loop, Record here hope can also give some help to those who have heart.
What is a KeyChance
A KeyChance is an event or opportunity that is critical to the development of an organization or an individual. (Ok, I admit that I invented this word because I didn’t know what word to use to express my meaning…) For individuals, it is easy to identify, such as college entrance examination, job-hopping and partner selection. There are many things for organizations, such as: launching a product at the right event, conducting a large presentation or presentation for key leaders, deciding to invest a lot of resources in developing a key technology, choosing someone to be a CTO, etc.
The principle of
1. Stop praying, Anything can happen. I thought it was a joke to hear about turning on servers until I saw a small company actually doing it, and realized that even with 21st century technology, thinking can be stuck in the 19th century or earlier. In the face of KeyChance, we should stop such useless prayer, but correct our attitude and make clear that all bad things can happen, and the meaning of our existence is to make all these things better. The server frequently freezes or goes down, not the opening way is incorrect or the feng shui is bad, also may be the surrounding environment is not ideal or there is a train nearby when a large pass caused by the disk vibration. It is possible to avoid or mitigate the damage caused by accidents by being down-to-earth, discarding illusions and working hard. 2. Pre-mortem, risk review, pre-mortem, presupposes that there has been a failure before the event, and then reflects on the causes of the failure, what can we do to avoid the loss or mitigate the harm? For example, the reasons for our demonstration failure may be as follows: 1. The network connection is down due to irresistible force, and the demonstration system 2 cannot be accessed. 3. Because the ambient temperature of the demonstration is too low, the power loss of the equipment shuts down too quickly. For each of the above reasons, corresponding prevention or solution strategies should be formulated. The whole team should be involved in this process instead of just one person patting their head, so as to avoid a concussion when one person patting their head, and the rest of them kneel even when they are busy with leg cramps. 3. Prepare a few different levels of contingency plans Through the above analysis, the team should have a lot of risks and plans, should now be similar or related aspects of the merger, not every aspect preparing different levels of plan, this is a bit like down-cycled distributed systems, such as the system is able to normal dynamic retrieval results based on the input, but there is a problem, It may change to hitting Enter before retrieving. Take the demo: 1) normal Normal access and interactive system demo 2) in the event of a network interruption, demoted to drop for the first time to access the system through satcom link, this system basically normal but cannot transmit real-time video, a little slower response time 3) if the response speed of satcom dropped below bear range, then again downgraded to visit local demonstration system, However, the data are all simulated and the effect is not good. 4) If the effect of simulation is too bad, it will be demoted to screen recording for demonstration again, which can also achieve good effect with appropriate explanation. People are particularly likely to follow the advice of others when faced with urgent and unexpected problems. This is mainly because people tend to focus on the problem and narrow their vision, which is why cheaters are often successful. As shown in KeyChance more need to calm down, analysis before action. Such as in the example above, the drop to the lowest level, need to record the screen, but not the latest record local screen, at that time some people say that had, in such and such then most people will start immediately ran past, but in fact can be obtained through other channels, such as through email, or direct video conference in the surface model to display. 5. Multiple solutions Solving problems in the field is often a high-risk, time-sensitive task, so be careful not to put all your eggs in one basket. It is best to carry out multiple solutions at the same time and choose the best solution by comparing the results in parallel. 6. Review and summarize. Sit down after the event is complete and review the decision making process and the environment to see how we could have done it better over time. The best is not a person to think, but more as a bystander’s opinion, so as to be more objective review and summary.
conclusion
- Correct attitude
- Plan well
- 1. Choosing the right people and the team is often the most important. In normal times, I cannot be careful and meticulous, and I am not reliable at critical times. Try to treat everything as a KeyChance. Fortune favors the prepared mind. 3.