What is happening at present: if you do not plan the worst, things will often go to the worst (4)

Continued 《What is happening at present: if you do not plan for the worst, things will often go to the worst. (3)"

The following happened from to on January 1, September 23 ~ 9: 00 AM

I woke up for breakfast in the morning and called Project Manager A. I first asked the project team's service personnel to arrive at the site of the owner? The answer is that the system has been monitored on site and the current operation status of the system has been queried. The answer is that the system has been operating normally so far. I told a that today I have arranged for my colleague dy to help them locate and solve the problem, and asked yesterday if I had written a report combining the fault problem with the usage on the first day? The answer is that it is not too late. Considering that my colleagues in the project team had a lot of pressure last night and had to go to work on time at in the morning, I told a that it is necessary to sort out and release it today, you still need to hurry up. Otherwise, what if something goes wrong today?

(A bit like in an old movie, the boss of the Kuomintang army wearing a hatter shouted at the phone: "Hold me down ")

 

Within five minutes, I received a call from dy,Ask me if I still need to go to the project team today ?!

I was a little angry. I pressed my anger and did not answer his questions positively. I replied via a counterquestion: "Do you think we should have passed ?"

He replied: "I have already told Project Manager A about the methods and methods to be handled, and I sent an email to a and copied it to you last night, I confirmed with a in the morning that he has opened the access log, so I don't think I need to go to the site!"

My answer is: "No problem. Can you perform more analysis than yesterday if there is another suspected crash today? Can you make a determination and solve the problem when these phenomena occur again ?"

Dy couldn't answer my questions. I went on to say,"If you do not go to the site, you will not be able to feel the pressure on the team.A simple fault may result in a group of people being unable to use it, and the answer to the phone is enough to make you feel soft. If you can sacrifice one person for a team, you don't have to bear the pressure. I 'd rather do this !"

I also talked about some of the previous articles, such as: "Can you tell me that at noon today, you may not go wrong ?" And so on !...

Finally, he replied, "Okay, I'll go to the site to learn more ."

(TMD, I feel like I am the aunt of the neighborhood committee: "Have you got enough clothes today? Are you full today ?")

 

Just put down the call, I received a call from Project Manager A, informing me that my system had just crashed. He had first notified the Contact Manager of the subject, the problem has been rectified urgently. The current situation of the owner is stable and we are required to identify the cause and report it. I asked if the fault was discovered by our service monitoring staff in the project team or reported by the owners? The answer is that we discovered it on our own, so the owner confirmed our monitoring work on the phone number.

I said "OK". It may occur again once. Now we must encrypt the monitoring interval. I will notify relevant colleagues to see you at the site!

Looking back, I called DY: "The World News is very fast. You have just crashed. Unfortunately, you have not caught up. I know that you are on the road now. Be prepared and think about possible situations, we can't be lucky any more. The fact is happening in front of us, and we have a slap in the face. There must be a fierce battle today!"

 

(MD, I am really a joke, but countless experiences tell me that it is true, but I didn't think of such a report !)