The author of this article is the product manager of 360 Qi Dance Company
Product review: insight into the passwords of success and failure
1. What is recovery
Reviewing is a method of learning from one's own past experiences to improve future effective action and performance.
The difference between review and work summary
Work summary:
· The staged conclusion of past work is often linked to performance appraisal or job description;
· The form is relatively free, and there is often no fixed "rules";
· Often "talking to oneself".
Review:
· The purpose of the review is to improve the ability and the effectiveness of future actions, and there must be an open mind and appropriate resources;
· In order for learning to happen, the review must follow specific steps and logic;
· Review can not only be done by yourself, but also the "management language" and "methodology" shared by the team and the organization.
2. How to carry out project review
1. The "three-stage nine-step method" of project review
2. Checklist of project review meeting
3. Review goals: original goals and expectations
Review the list of questions, as shown below:
4. Evaluation results: compare the original goals and analyze the completion status
In terms of establishing a realistic review atmosphere, the primary task is to clearly present the gap between the results and the expected goals. The presentation of this gap is not meant to rush to find the root cause of the problem, nor is it intended to blame, complain, or avoid responsibility. Focus on "problem definition" and accurately describe the inconsistency between goals and actual results.
In this description, equal attention needs to be paid to successes and shortcomings, and the existence of bright spots must not be underestimated. You can't downplay your achievements because of being too modest, let alone ignore those truly outstanding jobs. Therefore, when describing data, work results, and accomplishing goals, it is necessary to evaluate objectively from multiple perspectives. These figures not only include absolute figures, but also relative to expected targets, highlighting the difference between strengths and weaknesses.
At the same time, it is also necessary to clarify the attitude towards these results. Are you satisfied with the finished result? Use data to express satisfaction and reasons for dissatisfaction. In short, the purpose of this descriptive stage is to lay the foundation for analyzing the cause, rather than rushing to the solution of the problem. In this way, it can be ensured that an objective and comprehensive perspective is always maintained during the review process, providing strong support for future improvements.
5. Analyze the reasons
When analyzing a problem using the "Five Whys" approach, we ask five consecutive "Why" questions to dig deeper into the root cause of the problem. Take the following example for example:
Through this example, we can see that the initial problem was the delay of the project schedule, but by gradually asking the "why" question, we found that the root cause was insufficient technical communication during the project planning stage, resulting in a lack of awareness of the difficulty and requirements of the task insufficient. Such analysis can help the team find the underlying cause of the problem, so as to develop a more targeted solution to ensure that similar problems do not recur.
Another Root Cause Analysis Tool - Fishbone Diagram:
Identify the problem: First, define what the problem is. The problem becomes the "head" of the fishbone diagram.
Draw the skeleton: On paper, a whiteboard, or an electronic drawing tool, draw a straight, horizontal line for the "fish's spine."
Adding branches: Draw branching lines from the top of the spine to the left and right to serve as the "skeleton" of the fishbone. These branches will be used to represent possible factors.
List possible factors: Based on the nature of the problem, identify possible factors. These factors can be various possible influencing factors such as people, process, technology, environment, etc.
Analysis of factor impact: On the branch of each factor, team members can jointly discuss the possible impact of this factor on the problem. analyzed factor by factor.
Ask "why" questions: For each factor, ask yourself why this factor might be causing the problem to occur. This is similar to using the "five whys" approach, asking questions layer by layer.
Detailed factor branch: For each "why", continue to ask, analyze the deeper impact of this factor, until you find the deeper root cause.
Summary: After analyzing the influence of each factor, each branch can be summarized and the root cause can be summarized.
Develop an improvement plan: Based on the results of the analysis, develop a specific improvement plan to solve or mitigate the problem.
6. Summary:
Through the above sections, we can basically complete the review template.
Forming the final review document requires knowledge accumulation for subsequent use.
3. Principles that should be followed in review
Transparency and openness: Reviews should be conducted in a transparent and open manner, encouraging team members to share experiences, opinions and feedback candidly. Avoid finger pointing, complaining, and blame, and foster an environment of mutual respect.
Objectivity and seeking truth from facts: Reviews need to be based on objective data and facts, not subjective assumptions. By analyzing the real situation, the root cause of the problem can be better understood.
Multiple perspectives: Make sure to cover different roles and perspectives in the review, including project team members, stakeholders, etc. This helps to get comprehensive information and perspectives.
Problem-oriented: The purpose of the review is to find out problems and improve them, so keep problem-oriented. The focus is on identifying the root cause of the problem, not just treating the symptoms.
Actively solve: Review should not only stop at the identification of problems, but more importantly, formulate solutions and improvement plans. Avoid recurring problems through proactive improvements.
Continue to learn and reflect: Retrospectives are a continuous learning process, and lessons learned from replays should be applied to future projects. Continuous reflection and optimization is one of the core values of the review.
Data-driven: review based on data and facts, not subjective guesswork. Data can provide a more accurate basis for analysis and support problem location and resolution.
Emphasis on highlights and success: Introspection should not only focus on problems and failures, but also pay equal attention to success and highlights. By analyzing successes, successful experiences can be drawn from them to provide inspiration for future projects.
Implementation and follow-up: The improvement plan formulated needs to be actually implemented and followed up. Continuously monitor the implementation of the improvement plan to ensure that issues are resolved and optimized.
Continuous improvement: One of the purposes of the review is to continuously improve the workflow and methods. Therefore, it is necessary to maintain the thinking of continuous improvement and integrate the results of the review into the daily work of the team.
- END -
About Qi Wu Troupe
Qi Wu Troupe is the largest front-end team of 360 Group, and participates in the work of W3C and ECMA members (TC39) on behalf of the group. Qi Wu Troupe attaches great importance to talent training. There are engineers, lecturers, translators, business interface people, team leaders and other development directions for employees to choose from, and supplemented by providing corresponding training on technical skills, professional skills, general skills, leadership skills, etc. course. Qi Dance Troupe welcomes all kinds of outstanding talents to pay attention to and join Qi Dance Troupe with an open and talent-seeking attitude.
