Recently, I heard a test colleague share knowledge about VMware, and was finally asked: How many pure VMware questions did you encounter in the test? Although this colleague answered, it seems that he did not answer, or did not answer. Point. In fact, what the person asking the question wants is a summary data about the VMware problem. In fact, I am most afraid of this kind of summary question, because I can judge many things at once! Different conclusions are drawn from different answers.
If we have a summary of VMware issues, classify and summarize each issue according to certain standards; perhaps we may use this data as our own right to speak to do something. For example: If there are many problems, the support is not strong, and the operation is not friendly, you can completely recommend customers not to use VMware. But first of all, there must be data support and the right to speak.
From my understanding, the work of summarizing sometimes cannot be completely relied on employees to do it consciously, but should be given a certain amount of time to do it, and specific employees should be assigned to do the summarizing work in the form of apportionment. Because this work is in actual work, it is actually a very important precipitation for a project team! Whether it is for the management team or the R&D team. Once you have the summary data, you can use it to explain the problem and what is the next plan! Forward-looking work also relies on summarizing data to speak.
Without this part of the summary, or the right to speak, the small team will lose part of its right to speak in the management team and lose its position to fight for certain interests for the small team. Because in a free environment, as a complete group, and they are all highly intelligent life forms, it doesn't mean that those who weigh two hundred catties will have more right to speak, but the more important right to speak is based on data and facts. Be rigorous of course!