In PDCA, "C" is often a link that is easy to ignore. This small C is sometimes really fatal. In many cases, I always take it for granted that I am doing well, this step is ignored, and the actual situation is exactly the opposite of what you expected, and it is very realistic, such:
1,ProgramAfter the modification, I think there is no problem. I don't need to test it, but there is a big bug.
2. When commands are completed, the subordinates are often able to understand them, but the actual execution is irrelevant.
3. After an email is written, it will be sent immediately. At this time, the subject of the email is not written.
4. I think the credit card has been paid, but when you get on the plane, you will be reminded by phone that you must make a payment immediately.
5. I made a document and was very satisfied with it. When I gave it to my subordinates, my subordinates had a lot of mistakes.
6. I made a plan and thought it was perfect. I submitted it to my boss, but I was given a bid. The original budget that my boss was most concerned about was incorrect.
7. Prepare for a product demonstration at the customer's place, but find that the customer wants to demonstrate on the virtual machine, and the user's machine does not allow the use of the CD, but his notebook cannot be started at this time.
8. I made an Excel file myself. It was very beautiful. When I gave it to the customer, the customer said it could not be opened. Originally, you made Excel 2010, and the customer used excel2003.
9. After receiving a project from the sales team, I took a few minutes and immediately told the sales team on QQ that it could be done in 3 days, but by 3rd days, it was discovered that the number of tasks in the last document could not be completed within 30 days.
The above examples were all taken by me or my colleagues, living and bloody...
How should we pay attention to this small C?
1. Slow down at work to form your own work cycle
2. Be rational and never be impulsive.
3. develop the habit of reviewing and checking
4. Focus on testing in R & D
5. avoiding mistakes through regulations and regulations is the most effective way.
6. Some management reforms, design trial periods, and opportunities for saving mistakes
7. There must be project review meetings during product development
8. Make analysis and inspection on new claimed tasks, and promise the customer again.
So the little C should never be ignored, otherwise it will really be a fart.