What a Lean Six Sigma Green Belt Project Actually Looks Like

People hear Six Sigma and picture statistics. Six Sigma Green Belt project examples tell a different story. In practice, the method can be read as five plain questions: what is the problem, how big is it, why does it happen, what do we change, and how do we make the change stick. The fastest way to see that is through a few real-shape projects. This guide from St. Michael's Learning Academy (SMLA) walks three plain-language projects through DMAIC, which stands for Define, Measure, Analyze, Improve and Control. It names the tools used at each step and shows what a project charter contains.

Where are you: operations, logistics, healthcare, or office roles

Lean Six Sigma fits many jobs where work moves through steps and something goes wrong often enough to annoy people. Sort yourself by your status first, and then by the kind of work you do.

Your status shapes funding and timing:

• Still serving. Ask an advisor which in-service options apply to you.
• Separated. Veteran education benefits may apply depending on your status.
• A military spouse. Spouse programs may apply depending on the service member's status and the program.
• Workforce-referred. Your local board decides Workforce Innovation and Opportunity Act (WIOA) training funds.

Your work shapes which example to read first:

• Operations and logistics. Warehouses, maintenance shops, supply rooms, motor pools. You already track errors and delays. Project one will look familiar.
• Healthcare. Clinics, hospitals and front desks where patients wait. Project two is written for you.
• Office and administrative roles. Finance, purchasing, human resources, anywhere paperwork waits for approval. Project three is yours.

See seven ways somebody else pays for your certification →

DMAIC in one paragraph

Define the problem, the customer and the goal, and write them in a project charter. Measure how the process performs today, so you have a baseline you can compare against later. Analyze the data and the process to find the root causes, not just the symptoms. Improve the process by testing and putting in place changes that address those causes. Control the new process with a plan, so it does not drift back to the old way once the project team moves on. Lean adds a focus on removing waste, such as waiting, rework and unnecessary steps, so the process gets faster as well as more reliable.

Explore SMLA's Lean Six Sigma certification program →

Six sigma green belt project examples, walked through DMAIC

The three projects below are illustrations, not case studies from a specific organization. Each one is a DMAIC example project sized for a Green Belt, and like most useful process improvement examples, each is narrow enough to finish and important enough that someone cares about the result.

Project one: a warehouse pick error rate

The situation. Orders leave the warehouse with the wrong item or the wrong quantity. Customers complain, and returns pile up.

• Define. The charter states the problem: too many orders are picked incorrectly. The customer is whoever receives the order. The goal is a measurable reduction in pick errors within a set time, and the scope is limited to one warehouse and one shift pattern.
• Measure. The team defines exactly what counts as a pick error, then collects data for several weeks: which items, which locations, which shifts, which pickers. That becomes the baseline.
• Analyze. A Pareto chart shows that most errors come from a small group of storage locations. A fishbone diagram and a walk through the aisles reveal why: similar items stored side by side with labels that look alike.
• Improve. The team separates look-alike items, relabels bins with clearer markings and adds a scan check at packing. They pilot the change in one zone before rolling it out.
• Control. A simple control chart tracks pick errors each week. The new storage rules are written into standard work, and the supervisor reviews the chart at every shift meeting.

Project two: a clinic check-in wait

The situation. Patients wait too long between walking in and being called back. Staff feel rushed, and appointments run late all day.

• Define. The charter targets the time from arrival to check-in complete. The customer is the patient. The scope covers the front desk process only, not the clinical visit.
• Measure. Staff record arrival and check-in times for a sample of patients over several weeks, along with the appointment type and time of day.
• Analyze. A process map shows every step at the desk. The data shows that waits spike at the start of the morning. Root cause analysis using the five whys points to insurance verification being done at the desk instead of ahead of time.
• Improve. The clinic moves insurance verification to the day before the appointment and sends forms ahead so patients arrive with them completed. A trial run on one weekday tests the change.
• Control. A control plan names who verifies insurance each afternoon and how the daily wait is tracked. If the wait creeps back up, the plan says what to check first.

Project three: an invoice approval cycle

The situation. Vendor invoices sit for weeks waiting for approval. Late payments strain relationships and create extra work.

• Define. The charter targets the cycle time from invoice received to invoice approved. The customer is both the vendor and the accounts payable team. The scope is one department's invoices.
• Measure. The team pulls dates from the finance system for recent invoices and maps where each one waited.
• Analyze. A value stream map shows most of the time is spent waiting, not working. Invoices bounce between approvers because the approval rules are unclear and some are routed to people who are out of the office.
• Improve. The team clarifies approval thresholds, sets up backup approvers and adds an automatic reminder. They test the new routing with one vendor group first.
• Control. A weekly report shows invoices waiting longer than the agreed standard. The approval rules are documented and reviewed each quarter.

Picking a first project of your own

The three examples share a shape you can copy. Look for a problem in your own work that meets these tests:

• It happens often. A problem that shows up every week gives you data to measure. A once-a-year failure does not.
• It can be counted or timed. Errors, waits, delays and rework are all measurable. Frustration alone is not.
• The cause is not already known. If everyone already agrees on the fix, you need a work order, not a project.
• It sits within your reach. You can see the process, talk to the people who run it, and get a sponsor to support the change.
• Someone cares about the result. A sponsor who wants the improvement will clear obstacles for you.

A problem that passes all five is a good candidate for a first Green Belt project.

See what a Lean Six Sigma Green Belt can earn →

The tools at each step, named plainly

Green Belt tools are mostly ways of seeing a process clearly. Here they are by step, in plain terms.

• Define: the project charter; a SIPOC diagram, which lists Suppliers, Inputs, Process, Outputs and Customers on one page; and voice of the customer, meaning what the customer actually needs.
• Measure: a data collection plan, check sheets for counting events, basic process maps, and simple measures such as averages and spread.
• Analyze: Pareto charts to find the biggest contributors, fishbone diagrams to brainstorm causes, the five whys to dig to a root cause, and basic charts to compare groups.
• Improve: brainstorming and prioritizing solutions, mistake-proofing so an error is hard to make, small pilots before full rollout, and Lean tools such as 5S workplace organization.
• Control: control charts that show whether a process stays stable, standard work that documents the new way, and a control plan that assigns owners and responses.

The project charter

The charter is created at the start of a DMAIC project, in the Define step. It keeps the team and the sponsor aligned on what the project is and is not. A typical Green Belt charter includes:

• Problem statement. What is wrong, where and since when, written without blaming anyone or naming a solution.
• Goal statement. What improvement you are aiming for and by when.
• Business case. Why the organization should care, in plain terms.
• Scope. What is in and, just as important, what is out.
• Team and roles. The Green Belt leading the work, the sponsor and the people who know the process.
• Timeline. Target dates for finishing each DMAIC phase.

A clear scope in the charter helps keep a project from growing until it never finishes.

How SMLA training and the IASSC exam fit

SMLA provides students with training and certifications in high demand professions including SAP, Project Management, CompTIA, Microsoft, and Lean Six Sigma. Ask an advisor how the course covers DMAIC and the tools above. The International Association for Six Sigma Certification (IASSC) is an independent certification body and does not provide training; ask an advisor which exam the course prepares you for.

Training teaches the method; a certification exam tests your knowledge of it. If you recognized your own workplace in one of the projects above, you have already picked a place to practice what you learn. Dates and format for upcoming classes are confirmed with an advisor.

For general background on quality management and Six Sigma, the American Society for Quality (ASQ) is a long-standing professional body: ASQ.

Compare SAP, PMP and Six Sigma →

Frequently Asked Questions

Request info from an advisor

If one of these projects looks like your workplace, Lean Six Sigma training is the next step. Tell us where you are, still serving, separated, a spouse or workforce-referred, and what kind of work you do. An advisor will confirm upcoming class dates and walk through the funding paths that may apply. For stories from people who took the course, see our testimonials page.