Black Belt Projects: The More You Do, the More You Lose — A Case Study on Rebuilding the Six Sigma Project Initiation Mechanism in an Equipment Manufacturing Company
Six Sigma has been implemented for many years in a certain equipment manufacturing company, but it often encounters an awkward situation: a stack of Black Belt certificates have been issued, and numerous projects have been completed, yet at the end of the year, the financial department calculates that the returns do not justify the investment. Most people attribute this to "poor execution," but the truth is often that the projects were flawed from the moment they were initiated. The more effort put into a poorly chosen project, the higher the sunk costs. This article uses a real case to dissect how the project initiation process can drag down the entire Six Sigma mechanism and the results of the subsequent rebuild.
1. Phenomenon: Thirty Projects, Only Thirty Percent Recognized by Finance
In the third year of Six Sigma implementation, the company had cumulatively trained 32 Black Belts and over 120 Green Belts, with around 30 projects initiated each year. On the surface, everything seemed to be thriving: project review meetings were frequent, and final reports were comprehensive. However, the data provided by the finance department at the end of the year made the management uneasy—out of 30 projects, the annual financial benefits confirmed were less than one-third of the initial predictions. Worse still, six projects that took eight to nine months to complete, with improvement measures fully implemented, yielded no financial benefits. The board began to question whether Six Sigma was just a "show," and the quality department faced the risk of the entire project being halted.
2. Diagnosis: Execution Is Not the Problem, Initiation Is Full of Holes
The quality department did not rush to defend itself but instead reviewed 58 completed projects from the past two years. The results were surprising: very few projects were truly "failed," and most projects followed the DMAIC path, using statistical tools appropriately in the measurement, analysis, and improvement stages. The problem lay before the projects were even initiated. When the 58 projects were re-evaluated based on their initiation quality, nearly 60% had significant flaws: some topics did not align with customer needs or business strategies, others were too broad for a single person to manage, and some had inconsistent benefit calculation methods. Another telling detail was that all 15 projects formally led by division heads and reviewed for initiation were completed on schedule, while over 80% of the "verbally initiated" projects were delayed or scaled down. The conclusion was harsh: projects were not failing due to poor execution but due to a poor start.
3. Root Cause: Three "Assumptions" Leading Projects Astray
The review identified three typical "assumptions" in the project initiation process.
The first assumption is "if a leader decides, it's a project." Most projects originated from a casual remark by a department head, without any demand validation. Some projects focused on metrics that customers did not care about—such as improving the efficiency of an internal process by 20%, while customer complaints were about packaging damage. No matter how well the improvements were executed, they did not translate into any orders.
The second assumption is "the larger the scope, the greater the benefit." A Black Belt project covering three workshops, five production lines, and spanning multiple departments—process, equipment, and planning—was initiated. The Black Belt had neither the authority to command across departments nor enough time, leading to the project dragging on for over a year. Midway through, personnel changes occurred, and the project ended hastily. The review data confirmed this: nine out of ten projects with uncontrolled scope ended up failing.
The third assumption is "the project team decides the benefits." The project team calculated benefits using various methods: some assumed full capacity and included all labor costs, others double-counted capacity improvements—two projects addressing the same bottleneck on the same production line claimed separate benefits, which, when added together, doubled the actual savings. The finance department did not recognize these benefits, and the root cause lay here.
4. Rebuilding: A Project Funnel, Five Key Questions, and Financial Involvement
After identifying the root causes, the company did not rush to replace people or tools but instead rebuilt the project initiation mechanism, focusing on three core actions.
The first action was to establish a "project funnel." All candidate topics must pass through four stages: collection, preliminary screening, review, and initiation. The first stage of the funnel opens during the annual business plan breakdown, ensuring that each topic aligns with one of the company's annual business indicators. Each division proposes candidate topics around the annual goals, and the quality department consolidates and conducts an initial screening, eliminating topics that are not strategic or have unclear problem definitions. The selected topics then enter the initiation review meeting, where a panel consisting of the quality vice president, financial director, and relevant division heads votes on the spot, preventing "whoever shouts the loudest gets the project."
The second action was to set "five key questions." The fixed actions in the review meeting are:
- Does the customer and the boss really care about this issue? Is there data to support it?
- Is the scope manageable? Can a Black Belt complete it within 4 to 6 months?
- How are the benefits calculated? Is the method aligned with finance and auditable?
- Is the data available? Is the measurement system reliable?
- Are the resources in place? Are the responsible person, time, and budget clearly defined? If any of these questions are not satisfactorily answered, the project is sent back for revision or eliminated.
The third action was to involve finance from the beginning. The finance department participates from the initiation review stage, providing a unified benefit calculation template and clarifying that "only savings confirmed by finance count as benefits." A project ledger is also established: when two projects involve the same indicator, finance determines the benefit attribution, preventing double counting. Finance also sends a dedicated person to the mid-term review meetings, and projects with a benefit prediction deviation of more than 20% must provide a new explanation.
5. Effect: On-Time Closure Rate Doubles, Financial Benefits Finally Recognized
In the first year after the mechanism was rebuilt, the changes were immediate. The number of initiated projects was proactively reduced from 30 to 21—fewer projects, but of higher quality: the on-time closure rate increased from 40% to 85%, and the average project duration shortened from 9 months to 5 months. The financial department confirmed that the annual benefits were 2.3 times those of the previous year, and all were verified through audits. More importantly, the attitude of the business departments changed: previously, the quality department had to beg for topics, but now divisions compete to propose projects, as they have seen firsthand that well-chosen projects can indeed turn into profits. Two years later, the greatest value of this mechanism is not just the increased benefits but the transformation of Six Sigma from a "quality department initiative" to a "business system requirement."
6. Insights: Project Initiation Is the First Gate of the Six Sigma Mechanism
This case provides three key insights for companies implementing Six Sigma:
- Choosing the wrong project topic leads to greater waste. No matter how well the DMAIC process is followed, it cannot save a "pseudo-problem." Investing effort in the initiation stage yields a much higher return on investment than trying to fix issues during execution.
- Project initiation is not solely the responsibility of the quality department. Finance, business, and senior management must all be involved, especially the financial department—without clear benefit calculations, the mechanism cannot stand. The Black Belt system and financial benefits are two sides of the same coin.
- The project initiation mechanism must be reviewed annually. Business priorities and customer needs change, so the initiation criteria must be adjusted accordingly. Making the initiation review an annual routine will elevate Six Sigma from a "project-based" to a "business-based" system.
Choosing the right topic is the first and most critical step in creating value for the company through Six Sigma.
Black Belt projects that choose the wrong topic will lose more the harder they are executed—project screening is the first gate of the Six Sigma mechanism.
Knowledge code: 6.1.3
Version: v20260819
Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools to quality management practitioners, helping companies continuously improve their quality capabilities.