Six Sigma Green Belt Project Examples: 5 DMAIC Walkthroughs and Ideas

Most Green Belt candidates understand the DMAIC phases in theory and then stall on a practical question: what should my project actually be? A good project is narrow enough to finish in a few months, important enough that someone cares, and measurable enough to prove an improvement. A poor one is a vague wish to "improve quality" that never leaves the Define phase.

This guide gives realistic Six Sigma Green Belt project examples across manufacturing, healthcare, IT, finance and service operations, and walks through each with its DMAIC steps. The examples are illustrative scenarios built to teach the method. They are not case studies of real organisations, and any numbers shown are placeholders for the kind of measurement you would collect yourself. You will also find criteria for choosing a project, a charter template and the mistakes that sink first projects.

Key Highlights of Six Sigma Green Belt Projects

• A Green Belt project applies DMAIC (Define, Measure, Analyse, Improve, Control) to one specific, measurable process problem.
• Good projects have a clear problem statement, a baseline measure, a target, a defined scope and a sponsor.
• Examples range from reducing defects on a production line to shortening patient wait times, cutting invoice errors and speeding up IT ticket resolution.
• Scoping matters most. Projects that aim too wide rarely finish, and projects with no baseline cannot prove results.
• Every DMAIC phase produces a deliverable, so the project doubles as a portfolio piece for interviews.

What Counts as a Six Sigma Green Belt Project?

A Six Sigma Green Belt project is a focused improvement effort that uses the DMAIC method to reduce variation, defects or waste in one defined process, backed by data and a measurable target. Green Belts typically lead such projects part time alongside their regular job, often supported by a Black Belt or quality lead.

If DMAIC is new to you, our overview of the Six Sigma DMAIC process and methodology explains each phase. The American Society for Quality also publishes a plain description of the DMAIC method, which is useful as a neutral reference.

A project differs from a general improvement idea in four ways: it has a measurable problem, it has a defined boundary, it follows evidence from data collection through analysis, and it ends with a control plan so gains last. You can read how the Green Belt role fits in our guide to Six Sigma Green Belt roles and responsibilities.

How to Choose a Good Green Belt Project

Before looking at examples, use these tests. A candidate project should pass most of them.

The last test is often missed. If management has already chosen the solution, you have a project execution task, not a DMAIC improvement. DMAIC is for problems where the cause is not yet known.

The Project Charter: Your Starting Document

Every example below begins with a charter. A short charter keeps the team aligned and gives the sponsor something to approve. It usually contains the problem statement, business case, goal statement, scope, team and timeline. Our guide to the elements of a project charter in Six Sigma goes through each field.

Write the problem statement without including a cause or a solution. "Invoices have errors because staff are untrained" already assumes the answer.

Example 1: Reducing Defects on a Manufacturing Line

Scenario. A packaging line produces labelled bottles, and a share of units are rejected at final inspection because labels are misaligned.

Supporting tools include the SIPOC diagram, measurement system analysis and Pareto analysis. A frequent finding in projects like this is that inspectors disagree on what counts as a defect, so fixing the measurement comes before fixing the machine.

Example 2: Reducing Patient Wait Time in an Outpatient Clinic

Scenario. Patients at an outpatient clinic often wait longer than the clinic's own target between check-in and seeing a clinician.

Value stream thinking is helpful here, and our guide to value stream mapping shows the technique. Always involve clinical staff early, because they know the constraints, and respect patient privacy by using aggregated or anonymised data.

Example 3: Cutting Invoice Errors in Accounts Payable

Scenario. An accounts payable team spends time correcting invoices that were entered with wrong amounts, wrong vendors or missing purchase order numbers.

A useful metric set is described in commonly used Six Sigma metrics, including defects per unit and defects per million opportunities. Choose the metric your sponsor understands, because a clear measure is easier to defend than a sophisticated one.

Example 4: Speeding Up IT Service Ticket Resolution

Scenario. An IT support team wants to cut the time it takes to resolve routine tickets, which drifts well beyond its service target for certain categories.

Because ticket data usually exists already, IT projects are a convenient first project, though data quality needs checking before you trust it. Related service management ideas appear in our comparison of ITIL and agile.

Example 5: Reducing Order Fulfilment Delays in a Warehouse

Scenario. A warehouse often ships orders later than promised, and customers complain about missed delivery dates.

The lean lens fits well. Our guide to the seven wastes of Lean lists the types of waste to look for, and the Lean Six Sigma tools article shows which methods apply at each stage.

More Green Belt Project Ideas by Function

Here are shorter ideas that can be shaped into full projects once you add a baseline and target.

Treat each as a starting prompt. Before choosing one, confirm data access and sponsor interest.

How to Run Your Project Week by Week

Teams that finish projects usually plan the rhythm up front. The outline below suits a part-time Green Belt working across roughly four months. Adjust it to your data and sponsor availability.

Hold a short review with the sponsor at the end of each phase. These gates catch scope drift early and give the sponsor a chance to remove obstacles. Practitioner communities such as iSixSigma publish articles and templates that can supplement your own tools, though you should check any template against your certifying body's expectations.

Questions to Ask Before You Close a Project

• Did the measure move against the baseline, and is the change larger than normal variation?
• Does the control plan name an owner and a review frequency?
• Would someone new to the process follow the revised procedure correctly?
• Which of the root causes did we confirm, and which remain untested?
• What did we learn that another team could reuse?

Answering these keeps the final report honest and gives future projects a better starting point.

Common Mistakes in Green Belt Projects

• Starting with the solution. If the answer is already decided, DMAIC becomes a justification exercise.
• Skipping the baseline. Without a starting measure you cannot prove improvement.
• Boiling the ocean. Wide scope stretches the timeline and hides root causes.
• Trusting the data blindly. Check the measurement system before analysing.
• Ignoring the people. Front-line staff know where the process breaks, and ignoring them causes resistance.
• Forgetting the control phase. Gains fade without monitoring and an owner.
• Counting activities as results. Training sessions delivered are not defect reductions.

Our article on Six Sigma implementation challenges covers organisational obstacles in more detail.

Using Your Project for Green Belt Certification and Your Career

Many certification routes expect or encourage a real project, and a completed project gives you concrete evidence for interviews. Requirements differ between certifying bodies, so check the rules of the one you choose before you start. If you are still comparing options, read about the benefits of Six Sigma Green Belt certification and whether Six Sigma Green Belt is worth it, and review the Six Sigma Green Belt tools you will need.

When presenting the project, tell it as a story: the problem and baseline, what the data showed, what you changed, the result and how you protected it. Report results honestly, including partial results. A modest, well-evidenced improvement is more credible than an impressive number with no method behind it.

Conclusion

The best Six Sigma Green Belt project is a small one with a measurable baseline, a defined scope and a cause you do not yet know. The five examples above, covering manufacturing, healthcare, accounts payable, IT support and warehousing, show the same discipline in different settings: define precisely, measure honestly, analyse before acting, test the fix and lock in the gain. Choose a problem that matters to a sponsor, write a clear charter and let the data lead.

Prepare for the credential: See the Lean Six Sigma Green Belt certification training.

Test your knowledge: Try the Lean Six Sigma Green Belt practice tests.