Three years as a full-time Six Sigma Black Belt: A spiritual practice of "sharpening the sword with data"
I. From Tool User to Problem Translator: The Core Positioning of BB
Three years of full-time experience as a Six Sigma Black Belt (BB) is more like a spiritual practice of "climbing stairs with tools" - there is no overnight transformation, but each step is taken on the bricks of data and processes, gradually grinding the "methodology" into the "muscle memory for problem-solving". I'm no longer "a consultant who follows the manual and uses templates", but "an interpreter who can understand the language of engineers":
- When the production manager says, "This production line keeps producing defective products," I'll first ask, "Have you measured the dimensional deviation of the defective products? What's the result of the MSA of the calipers used?"
- When the customer says, "Your delivery is too slow," I will help the salesperson translate "slow" into "Orders with a time from order placement to shipment exceeding 72 hours account for 25%, resulting in a 30% loss of customers."
The value of BB has never been "solving problems on behalf of others", but rather "transforming vague problems into quantifiable goals and turning experience-driven judgments into data-driven decisions" - it's like "installing a data navigation system" for chaotic problems, enabling everyone to find answers along the same logical path.
II. Why does Six Sigma emphasize "engineering"? Because it is a "replicable problem-solving formula"
Many people ask, "Why is the word 'Engineering' added to 'Six Sigma'?" The answer lies in its "rigorousness" — every step of it is "decomposable, verifiable, and replicable" just like in engineering design. It is not an "inspiration that comes out of the blue" but an "inevitable result following a process."
Taking the most basic DMAIC framework as an example, the tools in each stage are all about "clarifying the vague".
VOC (Voice of the Customer): It's not simply a questionnaire. It means transforming "customers think the packaging is brittle" into a quantifiable indicator of "the breakage rate
SIPOC (Process Input - Output): It's not just about drawing a flowchart. It's necessary to mark "12 nodes from raw material warehousing to finished product outbound, the input variables (such as raw material humidity), output indicators (such as defective product rate) and responsible departments for each node". This step is to "transform the invisible process into a 'visible causal chain'".
ANOVA (Analysis of Variance): Instead of running software to obtain the P - value, it is necessary to judge whether the influence of "machine rotation speed (500 rpm vs 600 rpm) on the defective rate is significant (P"< 0.05)" —— this step is "using mathematics to identify the 'key causes'".
MSA (Measurement System Analysis): It's not about "calibrating the instrument". Instead, it's to confirm "whether the error of the caliper you use to measure defective products exceeds the allowable range of ±0.02mm" — this step is about "ensuring 'measurement credibility' first, and then talking about problem - solving".
The essence of these tools is to "transform 'intuitive problems' into 'clear mathematical problems' using scientific methods." To make good use of them, BBs must have engineering backgrounds and process management experience: If you don't understand processes, you won't be able to find where the "waiting time for workshop changeovers" is in SIPOC; if you don't understand engineering, you'll have a hard time communicating with mechanical engineers when talking about "the impact of tool wear on dimensional tolerances" — BBs are "the bridge connecting engineering and data with tools," not "the masters of the tools."
III. From DMAIC to DFSS: The "Upgrade" of Problem - Solving —— From "Tinkering" to "Error Prevention at the Source"
DMAIC is the "basic boxing technique" of Six Sigma, which addresses the "problems in existing processes." However, after three years, I have a deeper understanding that the real improvement in efficiency comes from "designing processes without problems" - this is the value of DFSS (Design for Six Sigma).
The core framework of DFSS is IDOV (Identify - Design - Optimize - Verify), which takes a step further than the "problem - solving" approach of DMAIC, changing from "fixing problems after they occur" to "blocking problems during the design phase". Specifically in engineering practice, its subdivided directions are all "tangible goals":
DFM (Design for Manufacturability): Change the curved surfaces of parts to flat surfaces, increasing the yield rate of injection molds from 85% to 95% - reducing the waste of "designs that cannot be manufactured".
DFA (Design for Assembly): Change the fixation method from using 3 screws to a snap - fit design, reducing the assembly time from 5 minutes to 1 minute - reducing the variation caused by "assembly complexity".
DFR (Design for Reliability): Through FMEA analysis, reduce the risk of "connector looseness" from "occurrence rate 8" to "occurrence rate 2" – reduce the probability of "problems during use" from the source.
I once participated in a DFSS project for a battery pack. The R & D team originally designed a structure with "10 screws for fixation". Through DFA analysis, it was found that changing to a combination of "4 clips + 2 screws" not only reduced the assembly time by 60%, but also avoided the risk of loosening caused by "uneven screw torque". This is the power of DFSS - not "more complex design", but "smarter design".
IV. The core bottleneck in cross - departmental promotion: It's not that engineers are resistant, but that senior management "didn't understand"
After three years of doing BB projects, the most common dilemma encountered is not "not knowing how to use the tools" but "being unable to push forward the process" - the production department is afraid that conducting MSA during production stoppages will affect output, the quality department is worried that changing standards will increase inspection costs, and the R & D department is concerned that implementing DFSS will extend the project cycle. Behind these resistances, it's not "opposing improvement" but "each department has its own 'efficiency inertia'". And the key to breaking this inertia has never been the persuasive power of BBs, but the "cognition and support" of senior management.
Why did GE's Six Sigma succeed? It's not because the tools were more advanced. It was because Jack Welch turned Six Sigma into "KPIs for senior executives" – each vice president had to complete three Six Sigma projects before getting promoted, and each senior executive had to spend two weeks learning "how to drive change with data". However, most company executives still perceive Six Sigma as "a tool for the quality department": they won't take the time to understand the difference between "variation" and "waste", and they definitely won't include "promoting Six Sigma" in their annual goals.
The most helpless scenario I've ever witnessed: A DFSS project that could save the company 2 million yuan annually was postponed for half a year before being launched because the president thought it was "too troublesome." Only then did I realize that what ASQ calls the "systematic methodology" is never a "system of tools," but a "system of people" — if the senior management fails to understand the value of Six Sigma, no matter how capable the BBs are, they are merely "firefighters," not "process transformers."
V. Return to the essence of Six Sigma: It's not "performing magic," but "using data to solve problems more stably."
ASQ's definition of Six Sigma is "a systematic methodology based on facts, driven by data, and aimed at reducing variation and waste." However, after three years, I think a more straightforward explanation is: Replace "gut - feeling judgments" with "quantifiable standards" and "fragmented fire - fighting" with "systematic processes."
For example, when it comes to solving the problem of "delivery delay", in the past, it was "sales urging production, and production urging procurement". Now, it is:
1. Use SIPOC to draw the "8 nodes from order to shipment" and find that "the procurement waiting time accounts for 40% of the total cycle".
2. Use the CE Matrix (Cause - Effect Matrix) to identify that "unstable supplier delivery cycle" is the key factor.
3. Use ANOVA to analyze that "the delivery standard deviation of Supplier A (3 days) is much larger than that of Supplier B (1 day)".
4. Adjust the supplier ratio (A:B = 3:7). The total delivery cycle is shortened from 14 days to 10 days, and the customer repurchase rate is increased by 22%.
This is the "stability" of Six Sigma - not "quickly solving problems", but "no recurrence after problem - solving". It doesn't deny experience, but rather "lets experience follow the data"; it doesn't pursue "subversion", but rather "makes every step solid".
VI. Finally: It's not about "changing the world," but about "turning the methodology into muscle memory."
After three years of working on BB, I no longer dwell on "why the company's progress is slow". Instead, I care more about "every time I solve a problem, I plant the seed of Six Sigma in an engineer's mind". For example, in the past, when I talked to a production engineer about DMAIC, he would say "it's too troublesome". Now, he will actively ask for the "CE Matrix template". Another example is that in the past, when I talked to a R & D engineer about DFSS, he would say "I don't have time to do FMEA". Now, he will mark on the drawing "this part needs to go through DFM".
This is progress—Six Sigma is not about "changing the whole company", but about "enabling everyone who comes into contact with it to learn to solve problems with data". The journey is indeed long, but as long as there is data accompanying every step, there's no need to worry about going astray.
As stated in *Lean Thinking*, "Improvement is not a revolution; it's a 1% daily progress." For the past three years, what I've been doing every day is to record the "1% progress" in data and gradually accumulate it into "the ability to solve problems".
We are not "ordinary people." Instead, we are "those who walk with tools." The journey is long, but every step counts.