Talking about Project Management------Part 1: Comprehensive Quality
Note: This article is original by the author, please do not use it for commercial use. Reprints must be approved by the author and the source should be indicated.
This part of the comprehensive quality that has nothing to do with technology is only the experience and lessons or summary of personal practice, and it is inevitable that there are biases.
02 Details
details make a difference. This sentence is familiar, although it is not so absolute, but it also fully shows the importance of details.
The first time I worked with my current good friend to report to a client leader had a profound impact on me. My storytelling may be more verbose and less exciting:
This good friend is the company's salesman. We cooperated for the first time, and we did not meet before. The leader asked the two of us to briefly report the technical solution to the customer leader. Before we went, we communicated with each other, and the friend told me three points:
1. Be sure to arrive at least half an hour in advance;
2. The first time you meet, the impression is very important, and the spirit of wearing it;
3. Explanation of technical solutions, I believe in you.
We arrived at least an hour earlier. Beijing is a place with traffic jams and unreliable, so it was a lot earlier. While waiting for the customer, my friend insisted on waiting at the door. At the beginning, we went over the main points and strategies to be discussed. After all, there was plenty of time, and it was not a problem to wait all the time, so I went into the lobby and sat down. The customer leader did not come at the agreed time, and my friend was still waiting at the door. At this time, I went out and asked him, why do you have to wait at the door?
why? Why does this affect me until now, and he has become my good friend. I always feel that it is impossible for me to become friends with sales. This kind of prejudice and even too conservative thinking was finally thrown away by me because of the excellence of my friends. "The big things in the world must be done in detail, and the difficult things in the world must be done in the easy ".
why? Here's what he told me:
1. I must let the customer leader see that I am waiting for him, not that he can't see me or look for me when he comes;
2. I can find a lot of information, information? More? Yes, next he said:
A. I can know his travel restrictions on that day through the license plate number (this information played a crucial role in the in-depth communication between my friend and the customer leader. Later, the friend learned that the customer leader was going to travel on a certain day, according to the license plate number. It was just that day when he restricted his travels and drove over to pick up customers to the airport at a good time. The customer leaders were moved by his care and sincerity. This is a good stepping stone. Relationships need to be cultivated, and opportunities need to be cultivated. Opportunities are everywhere, it depends on the intention not serious);
B. I can see what kind of car I drive, and I can analyze his corresponding character through the car (it makes sense, what kind of car likes what kind of car, not precise, but roughly enough);
C. I can try my best to find an opportunity to have a brief chat with the customer leader before the meeting, and observe his clothing, conversation and whether he smokes?
......
This thing is shocking enough for me. I have always been a techie, and I don’t pay attention to these things at all. Even if I pay attention, I never consider these details, but this time I was shocked.
In the subsequent project management, more attention was paid to the details, and a few points were briefly summarized, but it was impossible to summarize:
1. Must arrive earlier than the customer. This is absolute and unbreakable. The easiest way to hold a meeting is to prepare the PPT environment in advance. When the customer leader comes, the projector can't be turned on, the computer projector can't match, the laptop is out of power... Customers, etc. Not to mention the results.
2. Do not fight unprepared battles. For the demonstration system, you need to prepare the network environment of the conference room and prepare it one day in advance. Serious enough, right? When you prepared in advance, the network was good, but you found that the network was broken during the meeting that day? How to do? You can use the prepared operation manual to deal with it, the prepared video demonstration...you can, and then coordinate and solve the network in the process. In short, don't fight unprepared battles, and this is the biggest advantage brought by the obsession with details. .
Of course, not everything can be prepared, and sometimes emergencies need to be adaptable.
3. Zero tolerance for details. In all aspects of the project, some things have no effect even if there is a problem, but some require zero tolerance. In software projects, we all know that system failures are unavoidable, but systemic downtimes, especially long-term downtimes, are absolutely zero-tolerance. This needs to be implemented from the beginning of the project to the details of each link:
A. The system architecture design cannot have major defects;
B. System development quality control, A-type bugs must not be launched;
C. System pressure test;
D. System deployment disaster recovery;
E. System operation and maintenance monitoring;
......
The details are so silent throughout the entire life cycle of the project.
What are the details? The details are the stitches made into a piece of clothing to wear and wear, simple, ordinary, and repetitive but absolutely essential .