Picking a Lean Six Sigma Project That Will Actually Finish: A Field Checklist
The single biggest predictor of whether a Lean Six Sigma project succeeds is not the skill of the team or the tools they use. It is whether the right project was chosen in the first place. A poorly scoped project drains a Green Belt's time for months, produces a tidy report nobody acts on, and quietly erodes the credibility of the whole improvement program. With teams still stretched thin from the pandemic and many people working remotely or hybrid, you cannot afford to spend a quarter chasing the wrong problem.
The good news is that project selection is a discipline you can run in an afternoon. Below is a checklist you can take into your next prioritization meeting this week. Score candidate projects against it before anyone opens a fishbone diagram.
Is it a real, measurable problem?
Lean Six Sigma works on processes that have a measurable gap between current and desired performance. If you cannot state the problem as a number that moves, it is not yet a project.
There is a defined process with a start, an end, and a repeatable flow — not a one-off event.
You can name the metric that is suffering: cycle time, defect rate, cost per transaction, on-time delivery, rework hours.
Baseline data exists or can be collected without a six-month measurement system study.
The cause is genuinely unknown. If you already know the fix, just implement it — that is a quick win, not a DMAIC project.
Is it the right size and within your control?
The classic selection mistake is boiling the ocean. A project that touches five departments and re-engineers an entire value stream is a program, not a Green Belt assignment. Scope it down until one team can own it from Define to Control.
Bounded scope. The process fits on one page as a SIPOC. If you need three pages to draw it, split it.
A willing process owner. Someone who controls the process agrees to act on the findings. Without that, Control never happens and the gains reverse.
Achievable in a quarter. Aim for a project a trained belt can close in roughly three to four months. Longer projects lose sponsorship and momentum.
Data you can actually get. If the measurement requires a system that does not exist or access nobody will grant, the project stalls in Measure.
Does it matter to the business?
Even a clean, well-scoped project is the wrong choice if nobody cares about the outcome. Tie every candidate to something leadership is already worried about — cost pressure, a supply disruption that is still fresh in everyone's mind, a customer complaint trend, a compliance risk. A project linked to a live priority gets a sponsor, a budget, and the meeting time it needs. An orphan project linked only to a belt's curiosity gets deprioritized the first busy week.
Run your shortlist through a simple two-axis screen: business impact on one axis, effort and feasibility on the other. Start with the high-impact, lower-effort quadrant. Park the high-impact, high-effort ideas for a chartered project with proper sponsorship, and quietly drop the rest. Write the chosen project down as a one-line problem statement before you leave the room — if you cannot, it was never ready.
If you want a structured way to rank improvement opportunities against your strategy before committing a team, XNM's strategic advisory can help you build a selection framework that fits how your organization actually works.