Green Belt Projects Launched in Batches, Abandoned in Batches? — A Case Study of the Rebuilding of a Green Belt Grading Management Mechanism in an Electronics Manufacturing Company

1. Forty-Three Project Proposals, Only Nine Completed by Year-End

An electronics manufacturing company (mainly producing server power supplies) launched Six Sigma initiatives over the past two years, sending sixty engineers to obtain Green Belt certification, with forty-eight successfully obtaining it. In the spring of the second year, the Six Sigma promotion office was eager to make significant progress, and departments collectively proposed forty-three Green Belt projects. The project initiation review meeting lasted a whole day, with everyone claiming "great improvement potential." However, by year-end, the situation was grim: only nine projects were completed on time; twenty-one were halted halfway, six of which did not even gather all the data for the M phase; and thirteen were never started, with the project proposals left in drawers. Even more critical was that among the nine "completed" projects, five could not provide financial benefits recognized by the finance department—reports were neatly written, but the benefits were vaguely calculated. At the annual review meeting, the boss asked a single question: "We spent over two million over two years, where are the benefits?" The promotion office had no answer. When the call for project proposals was made again the following year, there were few takers. Engineers privately shared a harsh truth: "Green Belt projects mean working during the day and doing homework at night; whether you do them well or poorly makes no difference, so why bother?"

2. The Problem Lies Not in the Learners, but in the Mechanism

The promotion office reviewed each of the forty-three projects and found that the root cause of abandonment was not "incompetent people," but five systemic flaws. First, project proposals were assigned rather than selected—engineers with Green Belt certification were required to submit topics, which often had no connection to customer complaints, scrap rates, or departmental KPIs. Many topics were chosen just to meet the quota, and as the projects progressed, the engineers found them increasingly meaningless. Second, there was no time guarantee—Green Belts were part-time, and when their primary duties became busy, the projects were the first to be sacrificed. The company did not allocate specific work hours or prioritize the projects. Third, mentoring was superficial—while nominally "Black Belts mentoring Green Belts," the Black Belts were often overwhelmed with their own projects, meeting with Green Belts only a few times a year. No one reviewed the deliverables at each stage, and it took two months to notice when a project went off track. Fourth, there were no process checkpoints—once initiated, projects ran until year-end with no interim checks. All reviews were squeezed into the last two days, with each project getting only twenty minutes, focusing on whether the slides were complete rather than the logical soundness of the project. Fifth, there were no differentiated outcomes—whether a project was completed well or poorly, with or without financial benefits, had no impact on personal performance evaluations or promotions. The lifetime Green Belt certificate became a safeguard. These five flaws were interconnected: unworthy topics received no investment, lack of time and mentoring led to project stagnation, no checkpoints allowed projects to drag on, and no consequences for poor performance led to a lack of seriousness.

3. Entry Point: From "Assigned Topics" to "Selected Initiations"

The first reform targeted project initiation. The new rules stipulated that Green Belt projects must not be based on whims but must come from three specific sources: gaps in departmental annual KPIs, top customer complaint items, and significant cost items related to scrap and rework. The project proposal form had to clearly state four key points: baseline data of the current situation, not just "many defects," but a thirty-day statistical record; quantified target values; the method for calculating benefits, detailing how savings and revenue increases would be measured; and the project scope and involved departments. The promotion office, along with the finance department and department managers, held a project initiation review meeting every month, scoring proposals on the spot. Proposals with unclear baselines were returned for additional data, those with unquantifiable benefits were rejected, and projects with overly broad scopes were escalated to Black Belt projects. In the first round, forty-three topics were reviewed, eighteen were returned for revision, and seven were rejected, including one titled "Enhancing Quality Awareness Among All Employees"—a noble goal, but without a baseline or clear boundaries, it was destined to be another abandoned project. After a year of implementing the selection system, the number of project proposals decreased from forty-three to twenty-eight, but none were abandoned mid-way—the initial screening saved ten times the firefighting costs later on.

4. Pathway: Graded and Categorized, Lightening the Load for Green Belts

Many companies require Green Belts to follow the full DMAIC process used by Black Belts, leading learners to spend excessive time on tools: those unfamiliar with statistical software were forced to learn regression, and those lacking data were forced to conduct hypothesis testing, often losing sight of the project's essence. This company divided projects into three levels: A-level projects, which were cross-departmental and had significant benefits, were led by Black Belts with Green Belt participation; B-level projects, which were departmental and lasted three to five months, were primarily the responsibility of Green Belts with monthly mentoring from Black Belts; and C-level projects, which were clear and small in scope, followed a lightweight eight to twelve-week path—Define with a one-page document, Measure using existing reports, Analyze with fishbone diagrams and stratification, Improve with a small batch validation, and Control by implementing control plans and standard work instructions. The principle was simple: tools should follow the problem, not be used for show. C-level projects did not require lengthy reports; a single A3 sheet explaining the "problem, root cause, measures, validation, and standardization" was sufficient. The project level was determined at the initiation review meeting, with work hour budgets and mentoring frequencies adjusted accordingly. This eliminated the need for learners to guess "how deep this project needs to be to be considered complete."

5. Process Control: Work Hour Budgets and Stage Checkpoints to Ensure Project Management and Oversight

Lack of time guarantee was the primary killer of abandoned projects. The new mechanism established a "work hour account" for each Green Belt project: A-level projects received sixteen hours per week, B-level projects eight hours, and C-level projects four hours. These hours were included in the individual's monthly performance, signed off by the department manager, and could not be arbitrarily reallocated during the project period. Mentoring was also scheduled: each project was assigned a mentor for one-on-one sessions every two weeks to review data, logic, and direction. The promotion office updated the project dashboard weekly, using red, yellow, and green colors to indicate project status. Two consecutive yellow lights triggered a meeting, and a red light initiated special mentoring. Checkpoints were set at three key stages: at the end of the M phase to verify data quality—unreliable data led to garbage analysis; at the end of the I phase to ensure the solution had undergone small batch validation; and before the C phase to confirm the implementation of the control plan. Projects that did not pass the checkpoints were not allowed to proceed to the next stage; it was better to pause and retrain than to move forward with flaws. The head of the promotion office put it bluntly: "Previously, we settled accounts at year-end, and the accounts were always messy. Now, we settle small accounts every month, making it difficult for projects to be abandoned."

6. Benefit Verification: Financial Review Before Project Closure, Confirmed Benefits Count

In the past, project closure meetings were essentially "report presentations," with benefits estimated by the project team and no financial oversight. The new mechanism brought the finance department into the review process: two weeks before closure, the project team submitted a benefit calculation sheet to the finance department for verification—savings had to be supported by before-and-after records of scrap rates, work hours, and material losses, while revenue increases needed to be based on orders and unit prices, with all transformation, tooling, and validation costs deducted. If the financial verification failed, the project was considered "technically closed" but not "benefit closed," and it would not be included in the annual Six Sigma report. For longer-term projects, the promotion office also set a nine-month pre-review: confirming the benefits already realized and providing a clear timeline for the remaining benefits to prevent projects from dragging into the next year with benefits perpetually "estimated." The first year's claims of "expected annual benefits of three million" were no longer heard at review meetings—because the finance department would ask: "Where are the three million, on which production line, in which month, and in which account?"

7. Incentives: Different Outcomes for Completion and Abandonment, Certificates No Longer Lifetime

The final piece of the puzzle was incentives. The completion status of Green Belt projects directly impacted individual performance evaluations: projects completed on time and with confirmed financial benefits received bonus points for annual excellence and priority for promotions, and the project team received a one-time reward based on a certain percentage of the confirmed benefits. Abandoned projects were recorded in the mentoring list, and the responsible engineers were not allowed to lead new projects the following year until they completed the outstanding tasks. Certificates were no longer lifetime: Green Belt certification was valid for three years, and renewal required at least one fully completed and financially confirmed project within that period—certificates transitioned from "status symbols" to "performance records." Additionally, department managers were held accountable: the completion rate of departmental Green Belt projects was included in their annual performance evaluations, with completed projects bringing prestige and abandoned projects requiring an explanation. Within a year, the engineers' attitudes changed: previously, they were pushed to propose topics, but now they were eager to do so—everyone realized that completing a project diligently was more effective than writing ten annual summaries.

8. One Year Later: Completion Rate Soared from 21% to 86%

At the end of the second year, the data was clear: twenty-eight projects were proposed, twenty-four were completed on time, and the completion rate rose from 21% to 86%. The confirmed financial benefits for the year were 3.8 million, six times the total investment in Green Belt projects. The average project duration was reduced from seven and a half months to four months. More valuable changes occurred behind the scenes: the number of applicants in the third year doubled, and the proposed topics were clearly more substantial, focusing on customer complaints and scrap rates. Two project leaders who had abandoned their projects the previous year gritted their teeth and completed them the following year, becoming key improvement leaders in their departments. Reflecting on the company's experience: the abandonment of Green Belt projects was never a problem of the learners, but of the mechanism that turned projects into homework—assigned topics left projects undernourished from the start, lack of work hour budgets left projects starved, absent mentoring allowed projects to veer off course, and lack of benefit verification led to superficial project completion. With the installation of five checkpoints, homework turned back into projects, and Green Belts truly grew into Green Belts. The benefits of Six Sigma are not found in certificates but in projects that can be completed, quantified, and sustained.

The root cause of abandoned Green Belt projects lies not in the learners but in the mechanism: entry selection, graded pathways, work hour budgets, stage checkpoints, financial verification, and a closed-loop incentive system. These six pillars ensure that homework turns back into projects.

Knowledge code: 6.1.3

Version: v20260906

Author: QTank QTank is dedicated to providing systematic knowledge, methodologies, and practical tools for quality management professionals, helping companies continuously improve their quality capabilities.