1005. Project Identification Guidelines

Before launching a continuous improvement initiative, leadership must determine whether a given operational problem warrants the full rigor of Six Sigma DMAIC (Define, Measure, Analyze, Improve, Control). Applying structured project identification guidelines ensures that organization resources, Green Belts, and Black Belts target problems that deliver high-value breakthrough performance rather than misapplying statistical tools to simple administrative tasks.

1. Core Six Sigma Project Identification Guidelines

To ensure a candidate initiative is well-suited for statistical investigation, evaluate the problem against these widely accepted operational rules:

                      ┌──────────────────────────────────────────────────┐
                      │    Essential Project Identification Guidelines    │
                      └─────────────────────────┬────────────────────────┘
                                                │
        ┌───────────────────────┬───────────────┴───────────────┬───────────────────────┐
        ▼                       ▼                               ▼                       ▼
【 Inputs & Outputs 】    【 No Pre-Set Solution 】   【 Adequate Baseline Data 】 【 Variation Focus 】
Identifiable process     Root cause unknown;          Minimum 30–40 verified       Focus on controlling
X's and Y's               avoid "Just Do It"          data points per month        X variation to fix Y

Identifiable Process Inputs and Outputs: The target process must have clearly defined inputs ( $X$ ) and measurable outputs ( $Y$ ). The goal of the project is to quantify how variations in $X$ directly drive defects in $Y$ .
No Pre-Determined Solution: A foundational rule among project identification guidelines is that a Six Sigma project must never have a pre-selected fix. If the cause is obvious and the answer is already known, do not waste belt resources—just go fix it!
Reducing Operator Variation: When human operators or operator training act as process inputs, focus on building robust, mistake-proofed (Poka-Yoke) systems that minimize variation across different shifts or skill levels.
Focus on Process Variation: Every Six Sigma project must be approached from the perspective of understanding, controlling, and eliminating variation in input factors to stabilize process outputs.
Secondary Data Validation: If historical or secondary data is used, perform a Measurement System Analysis (MSA) or data audit first. If the integrity or authenticity of the data is questionable, recollect fresh baseline data under controlled conditions.
Sufficient Sample Size: You must have sufficient data to perform statistical analysis. Ideally, a process should generate a minimum of 30 to 40 reliable data points per month. If data is unavailable or takes too long to collect, evaluate alternative project candidates.
Team and Sponsor Alignment: The improvement team must be committed to the project scope, and the executive sponsor must see clear, quantifiable financial or operational gains to sustain resource support.
Managing Geographical Separation: If team members are geographically dispersed, establish clear virtual collaboration protocols before starting. Cross-location friction is a leading cause of stalled DMAIC projects.

2. When to Use Six Sigma vs. When NOT to Use Six Sigma

A major aspect of practical project identification guidelines is recognizing when Six Sigma is the correct tool versus when an alternative methodology should be chosen.

                                  ┌───────────────────────────────────┐
                                  │      Decision Tree Framework      │
                                  └─────────────────┬─────────────────┘
                                                    │
                      ┌─────────────────────────────┴─────────────────────────────┐
                      ▼                                                           ▼
         [ Is the Root Cause Unknown? ]                              [ Is the Solution Obvious? ]
                      │                                                           │
        ┌─────────────┴─────────────┐                               ┌─────────────┴─────────────┐
        ▼                           ▼                               ▼                           ▼
  (Data Exists)             (No Data / Simple)                (Standard Fix)             (Obsolete Process)
        │                           │                               │                           │
  【 Use Six Sigma 】        【 Use Kaizen / Lean 】           【 "Just Do It" 】          【 Use BPR / DFSS 】

Criteria	WHEN TO USE SIX SIGMA	WHEN NOT TO USE SIX SIGMA
Root Cause	The root cause of defects or variation is unknown.	The root cause is obvious, or the solution is already known.
Data Availability	Quantitative data exists or can be gathered easily $\ge 30\text{–}40$ /month).	Data is non-existent, unverifiable, or extremely difficult to measure.
Process Status	Process is existing, operational, but performing below target.	Process is non-existent, broken beyond repair, or completely obsolete.
Problem Complexity	Multifactorial problem requiring statistical root-cause analysis.	Simple task requiring standard policy enforcement or administrative action.
Time Frame	Project can be completed within a targeted 3 to 6-month window.	Emergency crisis requiring an instant fix within 24–48 hours.
Recommended Approach	DMAIC (Six Sigma)	“Just Do It”, Kaizen Event, BPR, or DFSS

Frequently Asked Questions (FAQ)

Q1: What are the most critical project identification guidelines for data availability?

Following sound project identification guidelines, a candidate process should produce at least 30 to 40 reliable data points per month. If baseline data is untrustworthy or missing, it must be validated or recollected before launching DMAIC.

Q2: When should an organization decide NOT to use Six Sigma?

Six Sigma should not be used if the solution is already known, if the problem can be fixed with a simple “Just Do It” task, if no measurable data exists, or if a brand-new process needs to be built from scratch (where DFSS is preferred).

Q3: Why is a pre-determined solution dangerous in a Six Sigma project?

Pre-determined solutions bypass the Measure and Analyze phases of DMAIC. They risk applying expensive, ineffective fixes without addressing the true, statistically verified root causes of variation.

CSSC Certification Practice Exam Questions

1. A project team is evaluating a process with unknown root causes, but the process only generates 2 data points per year. Based on standard project identification guidelines, what is the primary risk?

A) The team will execute the project too quickly.

B) There is insufficient data to conduct reliable statistical analysis.

C) The executive sponsor will reject the DMAIC charter automatically.

D) Operator variation will be completely eliminated.

Correct Answer: B) There is insufficient data to conduct reliable statistical analysis.
Explanation: Standard guidelines recommend a minimum baseline of 30–40 data points per month to perform statistical testing and root-cause analysis effectively.

2. Which scenario represents an ideal application for a Six Sigma DMAIC project?

A) Replacing an old printer that regularly jams due to a broken gear.

B) Designing a completely new billing system for a startup business.

C) Reducing high yield variation on a chemical line where root causes are unknown.

D) Updating the employee holiday policy in the staff handbook.

Correct Answer: C) Reducing high yield variation on a chemical line where root causes are unknown.
Explanation: High process variation with unknown root causes and existing measurable data is the classic use case for Six Sigma DMAIC.

3. If secondary data collected for a candidate project appears unverified or suspect, what action should the team take first?

A) Proceed with statistical testing using the unverified data.

B) Immediately close the project and abandon the initiative.

C) Validate the data integrity or recollect fresh baseline data.

D) Assume the data is correct if provided by a manager.

Correct Answer: C) Validate the data integrity or recollect fresh baseline data.
Explanation: Six Sigma relies heavily on data integrity; unverified secondary data must be audited or recollected to ensure accurate analysis.

Next Post in Series: 1006. Identification of Six Sigma Projects – Idea Generation

Written by Ravi Prakash—Quality Expert (38+ yrs exp). Connect on LinkedIn or Contact Us.

Support Our Website

Your support helps us continue delivering good content and useful data. If you’d like to contribute, here’s how:

From anywhere in the world (PayPal): https://www.paypal.com/paypalme/rpbehara
From India (UPI): speakingdata@ybl

1005. Project Identification Guidelines: When to Use Six Sigma