Most stalled Green Belt projects were doomed at selection: too big, too vague or with the answer already decided. How to choose projects that matter to the business, fit the method and can be finished in months.
Two Green Belts started projects in the same week. The first was asked to "improve quality in the moulding department". Nine months later she was still collecting data across 60 products and four types of defect, and the sponsor had stopped attending reviews. The second was asked to "reduce short shots on the three high-volume closure tools from 2.4% to under 0.8% within four months". He finished in three and a half months, saved more than his annual salary and was asked to coach the next wave.
Both were capable people. The difference was project selection.
What makes a good Green Belt project
- Linked to a business priority: cost, quality, delivery, safety or customer satisfaction that leadership already cares about.
- Measurable: a clear metric with a baseline and a target.
- Chronic, with an unknown cause. If the cause and fix are obvious, just do it. Green Belt projects suit problems that have resisted easy fixes.
- Data available, or collectable within a few weeks.
- Scoped to finish in three to six months by someone working on it part-time.
- Within the team's influence. Projects that depend on another site, a major capital purchase or a supplier's internal process are risky for a first project.
Warning signs
- The solution is in the title: "implement a new ERP module" is a project to deliver a solution, not to solve a problem.
- The scope is a department, a plant or "all products".
- There is no data, and no practical way to get it.
- The sponsor is not interested in the result.
- The problem is really a resource shortage or a management decision.
Writing a sharp problem statement
A good problem statement describes the gap in measurable terms without assuming a cause:
- What: the defect, delay or cost.
- Where: the process, product or line.
- When: since when, how often.
- How much: the size of the gap, in units and dollars.
- Target: the improvement and the date.
For example: "Short shots on tools 14, 17 and 22 average 2.4% since January, costing $96,000 a year in scrap and rework. Reduce to below 0.8% by October."
Narrowing the scope
Use data to focus. A Pareto chart of defects by type, product, machine or shift often shows that a small number of categories account for most of the problem. Pick the biggest bar, not the whole chart. That is usually enough for one project, and success creates appetite for the next.
Agree it with the sponsor
Before starting, the Green Belt and sponsor should agree the charter: problem, scope, target, team, timeline and the support the Green Belt will receive, including time. Regular, short sponsor reviews at each DMAIC tollgate keep the project visible and unblocked.
The first project matters most
A new Green Belt's first project shapes their confidence and the organisation's view of the program. Choose one that is important, achievable and visible. Early success builds momentum for everything that follows, as we noted when discussing project-based belt training.
