Lean Six Sigma Project Selection: How to Choose the Right Problems

A Lean Six Sigma programme lives or dies on project selection. Organisations that commit experienced Black Belts and Green Belts to the wrong problems waste months of effort, frustrate their best improvement professionals, and ultimately undermine executive confidence in the entire methodology. Yet most LSS guides spend the bulk of their time on the DMAIC phases and treat project selection as an afterthought. That is a serious mistake.

What Makes a Good LSS Project?

A well-chosen LSS project meets four criteria simultaneously. Get any one of them wrong and you will find yourself mid-project wondering why progress has stalled.

1. Linked to a strategic priority. If the project does not connect to something the leadership team genuinely cares about, it will not get the sponsorship, resources, or urgency it needs to succeed. Ask whether the project would appear naturally in a presentation to the CEO. If the answer is no, question whether to proceed.

2. Has a measurable baseline. LSS is a data-driven methodology. If you cannot measure the current state — defect rate, cycle time, cost per unit, customer complaint frequency — you cannot demonstrate improvement. Projects on soft outcomes like "improve morale" or "enhance communication" rarely work well in a DMAIC framework.

3. Root cause is unknown. If you already know the solution, you do not need a DMAIC project — you need an implementation plan. LSS projects should investigate problems where the cause is genuinely unclear. Projects where the team says "we just need to implement X" are almost never true LSS candidates.

4. Realistic scope. A common failure mode is the project that spans too many departments, too many processes, or too long a timeline. The sweet spot for most LSS projects is three to six months, one primary process, and a team of five to eight people. Larger problems should be broken into a portfolio of smaller, linked projects.

The Project Selection Matrix

A selection matrix forces structured thinking and prevents the loudest voice in the room from determining the improvement agenda. A simple but effective version scores each candidate project on five dimensions:

• Strategic alignment (0–10): Does this map to a current organisational priority?

• Financial impact (0–10): What is the estimated annual benefit if the project succeeds?

• Feasibility (0–10): Do we have the data, access, and skills to complete this in a reasonable timeframe?

• Customer impact (0–10): Will improvement be noticed and valued by internal or external customers?

• Urgency (0–10): Is there a regulatory, competitive, or operational reason to act now rather than later?

Weighting can be adjusted to reflect organisational context — a heavily regulated industry might weight customer impact and urgency more heavily, while a margin-pressured business might prioritise financial impact. The matrix is a tool for structured conversation, not a final arbiter. Projects that score well across all five dimensions are genuine priorities. Projects that score high on one dimension only (usually financial) deserve scepticism.

Managing the Project Pipeline

Project selection is not a one-time event — it is an ongoing management discipline. Organisations running mature LSS programmes typically manage a rolling pipeline with three horizons:

1. Active projects (currently in DMAIC): Keep this list lean. Spreading Black Belts across too many concurrent projects is one of the fastest ways to guarantee mediocre results on all of them. Most Black Belts should own two to three projects at a time; Green Belts, one.

2. Staged projects (selected, sponsor assigned, charter drafted, starting within 90 days): These provide continuity. When an active project closes, the next one is ready to launch without a gap.

3. Backlog (identified but not yet prioritised): This is a living list. New problems get added regularly; the list is re-evaluated at a quarterly governance review against the current strategic priorities.

The mix of project complexity also matters. Not every project should be a full Black Belt engagement. A healthy programme balances long-cycle complex projects (six-plus months, cross-functional) with shorter Green Belt or even Yellow Belt Kaizen events (one to four weeks, single-process). The shorter projects generate quick wins, sustain engagement, and surface data that sometimes reframes the scope of a larger project.

Common Selection Mistakes

Even experienced organisations fall into predictable traps. Watch for these warning signs:

• "We already know the solution." This is an implementation project, not an LSS project. Assign it to a project manager, not a Black Belt.

• "The scope keeps expanding." Known as scope creep, this usually means the original project was defined too broadly. Restart the chartering process.

• "Leadership isn't engaged." A sponsor who doesn't actively remove barriers, attend tollgates, or champion the work is a red flag. Projects without genuine sponsor engagement fail at a much higher rate.

• "We can't get clean data." If the measurement system analysis (MSA) reveals that your data is unreliable, you will spend months chasing ghosts. Sometimes the right answer is to pause and fix the measurement system first.

• "The team doesn't have decision authority." If every recommendation requires three layers of approval, the project timeline will slip badly. Confirm the team's decision-making authority before chartering.

The Sponsorship Conversation

Every LSS project should have an executive sponsor who owns the business problem, not just the improvement process. The sponsor's job is to ensure the project stays connected to operational reality, remove political obstacles, validate the financial benefit calculation with Finance, and sustain the gains after the Black Belt moves on. Selecting a great sponsor is as important as selecting a great project.

Before finalising any project charter, have an honest conversation with the sponsor that covers: What will success look like in 12 months? What would cause you to de-prioritise this project? Who in the organisation will resist, and what authority do you have to address that? The answers reveal whether the project has the conditions to succeed.

XNM Consulting helps organisations build LSS project selection frameworks, governance structures, and pipeline management processes that generate measurable results. Learn more about our .