Talking about Learning and Implementation from the Quality Management Practices of Japanese Enterprises: Observations and Reflections on Several Core Issues
I. First, let's talk about the mindset: The "tool attribute" of quality management has nothing to do with the country
Many people have a preconceived prejudice against Japanese enterprises. However, the essence of quality management is a "universal toolkit" for problem - solving. For example, the PDCA cycle, 5S on - site management, and the seven QC tools. These methodologies originating from Japanese enterprises have long become the "underlying logic" of global enterprises. Take a real - life example: A domestic home appliance enterprise used the "fishbone diagram" from Japanese enterprises to analyze the abnormal noise problem of its products and located the root cause of "insufficient screw torque" in just three days. A certain automobile parts factory used the "5S" method to organize its workshop and reduced the time for finding tools from 15 minutes to 2 minutes.
Rather than getting entangled in the "Japanese enterprise" label, it's better to focus on "whether the tools are effective". Just as we wouldn't refuse to use chopsticks to eat because "they were invented in China" - the core of learning is to "absorb the strengths" rather than "negate everything". Only by putting aside prejudices can we truly obtain "practical methods" from the practices of Japanese enterprises.
II. Non - controlled Records: Balancing Departmental Individualized Needs and Data Authenticity
Someone in the forum asked, "How to manage non-controlled records? Are the data real? Will there be conflicts between departments?" In fact, this is a typical product of the "departmental system" in Japanese enterprises. The essence of non-controlled records is that departments use them to address "individualized needs that standard forms cannot cover."
For example, there is an old injection molding machine in the production department. The standard record only requires filling in the "start-up time", but the "temperature rise" of this equipment directly affects the product deformation rate. So the production department made its own "Equipment Temperature Rise Hourly Record Form"; the quality department made a "Batch Traceability Supplementary Account Book" to track a specific batch of customer complaints. These forms are kept by the departments themselves because they meet the "immediate needs" on-site. It may take a month for the headquarters to update the standard forms, which can't solve the current problems in time.
The contradiction regarding data authenticity is even more realistic: on one hand, it is related to the KPIs of relevant departments, so they "dare not falsify"; on the other hand, it involves the boundaries of interests, so the data "won't be completely true". For example, the qualification rate of the production department directly affects performance bonuses, so more than 90% of the data is real - no one would joke about their own salary. However, if the low qualification rate of a certain batch of products is due to "employees' operational errors", the department may write the cause as "raw material fluctuations" (to avoid affecting the team assessment). Nevertheless, such "adjustments" are partial because the final products have to pass the customer's factory inspection, and no one dares to falsify the core data.
The logic for cross - departmental use is very clear: general data is shared, and personalized data is "requested on demand". For example, "public information" such as material batch numbers and finished product inspection reports will be synchronized to the internal OA system. However, "cost details" and "equipment failure cause analysis" within departments have to go through the "Internal Collaboration Form". For instance, if the Quality Department wants to check the "molding temperature records" of the Production Department, it has to get the signature of the Production Department manager. The other party will provide the original data but will not disclose the "decision - making process for temperature adjustment" (that is the department's "improvement privacy").
III. Hierarchical Subdivision: Make the "Responsibility Chain" Precise at Each Level
The management levels in Japanese enterprises are extremely detailed: employee → team leader → squad leader → technician → engineer → deputy section chief → section chief → manager → deputy department head → department head. Many people think that "too many levels lead to low efficiency", but in fact, the opposite is true - the responsibility boundaries at each level are as tightly interlocked as "gears", avoiding the "responsibility vacuum".
For example, when the production line stops: The employee should first find the team leader (to report the situation), and the team leader should find the technician (to troubleshoot equipment failures). The technician determines that "the heating coil is damaged" and then finds the engineer (to confirm the inventory of spare parts), and the engineer contacts the purchasing department (to arrange for the supply of goods). There is no "bypassing of levels" or "shifting of responsibilities" in the entire process - because each level knows "what problems they should solve". Another example is quality abnormalities: When an employee discovers scratches on the product, they should find the team leader. The team leader should find the quality shift supervisor, and the quality shift supervisor should find the engineer to conduct a cause - effect analysis. The engineer formulates an improvement plan, and the team leader is responsible for implementation - there is a clear "responsible person" for each step, and there will be no chaos of "not knowing whom to turn to".
The core of this hierarchical structure is "professional division of labor": Employees focus on "operational proficiency", team leaders on "team coordination", technicians on "equipment maintenance", and engineers on "process optimization" — each level delves deeply within its own "circle of competence", and there will be no internal strife like "employees doing the work of engineers and engineers doing the work of team leaders".
IV. "On - site teaching" by Japanese experts: Transforming "knowledge" into "action"
The "Japanese expert exchange" in Japanese companies is never about "sitting in the meeting room to talk about theories", but rather squatting at the site to "teach methods hands - on". For example, the injection molding process expert who came last month went straight to the production line to watch the employees' operations and pointed out that "the timing of adjusting the injection molding pressure was wrong". Employees were used to adjusting the pressure all at once when starting the machine. The expert taught them to "make a fine - adjustment according to the mold temperature every time 100 pieces are produced", and then drew a "pressure adjustment record sheet" together with the engineers and will directly check the results next week.
The key to this kind of communication is "learning for application": Experts won't talk about "the definition of a cause-and-effect diagram". Instead, they take the defective products of the day as an example, draw a cause-and-effect diagram together, and identify that "high humidity of raw materials" is the main cause. Then they teach "how to measure humidity" and "how to adjust the drying time". They won't talk about "the concept of line balancing" either. Instead, they lead the production department manager to measure the time of each process and increase the production capacity of the bottleneck process by 15%. After learning, the management can directly apply what they've learned in their work, and the results are immediate.
V. Data analysis: Use "numbers" to force improvements and rely on "supervision" to ensure the implementation of results
The "monthly data analysis" in Japanese companies is never just "going through the motions," but rather using numbers to "force the exposure of problems." For example, in the monthly report of the production department, items such as "production volume achievement rate," "qualified rate," and "equipment utilization rate" will be listed, and histograms are used to observe trends. If the qualified rate drops from 95% to 93%, immediate questions will be asked: Is it the raw materials, the equipment, or the operation?
After finding the cause, an "Improvement Committee" will be established (for example, led by the Quality Department, with participation from Production and Procurement). Weekly progress meetings will be held, and the progress will be tracked using a Gantt chart: I. Test the humidity of raw materials in the first week; II. Adjust the drying time in the second week; III. Verify the effect in the third week; IV. Write the "Operation Standard Manual" in the fourth week. The core of supervision is "closed-loop" - it's not just about "making improvements", but about "whether the improvements are effective". For example, if the pass rate returns to 95% after the improvement, the committee will check "whether the employees have learned the standard manual" and "whether the site has implemented according to the standards" to ensure that the problem will not recur.
Conclusion: Let's talk about something "specific" next time
That's all for today. Next time, I'd like to talk about "the improvement proposal system in Japanese companies". For example, how can an employee's idea like "moving the tool cabinet next to the production line" turn into a "company standard"? Also, "5S management at the workplace" is not about "cleaning up" but the specific operations for "reducing waste". Due to time constraints, let's continue this discussion next time.