Six Sigma Define Phase Tools: Application, Scenario Examples, and Tollgate Preparation
During the initial phase of any continuous improvement project, selecting appropriate six sigma define phase tools determines how effectively a team can validate a problem, scope process boundaries, and present a rock-solid business case to executive leadership. Before requesting formal sponsor sign-off at the Define Tollgate Review, practitioners must transform abstract operational complaints into structured, data-supported process definitions.
Knowing what tool to use and when to apply it through realistic operational scenarios ensures that project teams establish objective baselines without over-analyzing early-stage workflows.
1. Core Tool Matrix: What to Use and When
┌────────────────────────────────────┐
│ Define Phase Tool Application │
└─────────────────┬──────────────────┘
│
┌──────────────────┬───────────────────────┼───────────────────────┬──────────────────┐
▼ ▼ ▼ ▼ ▼
【 High-Level Map 】 【 In/Out Box 】 【 Is / Is Not 】 【 Brainstorming 】 【 Advance Tools 】
Visualizes macro Defines explicit Isolates symptoms Gathers VOC & CTQ Run charts & VSM
process steps process limits & excludes noise requirements previews
| Tool Name | Primary Purpose | When to Apply | Expected Tollgate Output |
| SIPOC Diagram | High-level system structure | At project kickoff to define end-to-end boundaries | Approved high-level process architecture |
| High-Level Process Map | Visualizing macro workflow (3–7 steps) | When defining process limits and key handoffs | Clear visual baseline of current-state workflow |
| In and Out of the Box | Visual boundary setting | During team scoping sessions to prevent scope creep | Agreed-upon operational boundary diagram |
| Is / Is Not Matrix | Scoping problem characteristics | When refining the problem statement to isolate defect factors | Structured comparative boundary matrix |
| Brainstorming & Affinity Map | Gathering VOC and CTQ drivers | When translating customer needs into critical quality metrics | Grouped Voice of Customer (VOC) requirements |
2. Scenario-Based Application of Key Define Phase Tools
High-Level Process Map
Scenario: A corporate logistics manager reports that fulfillment lead times have doubled, but different departmental leads disagree on where delays occur. The team needs a simple, shared macro view of the process without getting bogged down in micro-level tasks.
-
When to Use: When establishing start/stop boundaries (7 to7 steps) and macro departmental handoffs.
-
Practical Output:
In and Out of the Box Method
Scenario: During the charter kickoff for a financial invoicing improvement project, regional leads keep bringing up payment collection delays in Europe and retail store POS transactions. The Belt needs to establish firm boundaries to keep the project focused strictly on North American B2B billing.
-
When to Use: During initial alignment workshops to visually separate in-scope elements from excluded systems, regions, or categories.
-
Practical Output:
┌──────────────────────────────────────────────────────────┐
│ IN THE BOX │
│ * North American B2B Accounts │
│ * Billing Module Version 4.2 │
│ * SAP Enterprise Invoicing │
└──────────────────────────────────────────────────────────┘
OUT OF THE BOX
* B2C Retail Invoices * European Operations
* Payment Collections * Manual Wire Receipts
Is / Is Not Matrix
Scenario: An operations manager states, “Our entire order billing system is failing.” Before accepting this broad statement, the Black Belt gathers data to determine where the defect actually occurs—and where it does not.
-
When to Use: When refining a problem statement to narrow down symptoms, eliminate unrelated variables, and prevent pre-mature root-cause assumptions.
-
Practical Output:
| Dimension | IS (What problem is occurring?) | IS NOT (What could be occurring, but is not?) | Distinction / Key Observation |
| WHAT | Invoice pricing discrepancy errors | Tax calculation errors | Issue is isolated strictly to line-item unit pricing. |
| WHERE | North American Billing System | European ERP Billing System | Limited to regional database tables. |
| WHEN | Occurring during end-of-month runs | Occurring during mid-month daily runs | Correlates with batch transaction spikes. |
| EXTENT | 8.5% error rate across top enterprise accounts | Minor standard retail account orders | Impact is specific to customized corporate tier pricing. |
Brainstorming and Affinity Mapping
Scenario: A healthcare clinic receives negative patient feedback regarding long wait times. The project team conducts focus groups to collect raw Voice of Customer (VOC) feedback and organize the complaints into actionable Critical to Quality (CTQ) categories.
-
When to Use: When converting qualitative customer feedback into structured operational metrics.
3. Introducing Measurement and Analysis Preview Tools (Tools which can also be used as Define Phase tools)
While quantitative tools such as Run Charts, Value Stream Mapping (VSM), and Pareto Charts reach full application in the Measure and Analyze phases, presenting preliminary versions during the Define phase serves a strategic purpose at the Tollgate:
-
Run Charts (Trend Analysis): Scenario: A sponsor questions whether an 8.5% defect rate is just a temporary bad week. A baseline Run Chart showing 6 consecutive months of elevated error rates proves the issue is systemic.
-
Value Stream Mapping (VSM Preview): Scenario: Executives demand to know why cycle time is excessive. Showing a macro value-add vs. non-value-add (VA vs. NVA) time breakdown justifies spending resource hours in the Measure Phase.
Mastering these six sigma define phase tools provides the objective evidence required to defend a business case during executive phase reviews.
Frequently Asked Questions (FAQ)
Q1: Which six sigma define phase tools are mandatory for tollgate approval?
At minimum, a project team must present a high-level SIPOC, a defined In-Scope / Out-of-Scope matrix (or In/Out Box diagram), and an Is/Is Not matrix or refined Problem Statement to prove project boundaries.
Q2: What is the main difference between a High-Level Process Map and a Value Stream Map?
A High-Level Process Map depicts 3 to 7 macro workflow steps to define boundaries, whereas a Value Stream Map quantifies process cycle time, lead time, changeover time, and inventory levels across value-add and non-value-add activities.
Q3: Can Run Charts be used as part of the Define Phase tools?
Yes. A baseline Run Chart is often presented at the Define Tollgate to demonstrate historical performance trends and verify that the problem is persistent.
CSSC Certification Practice Exam Questions
1. A continuous improvement team wants to narrow a problem statement by determining what process areas are experiencing defects versus areas that are operating normally. Which of the define phase tools is best suited for this task?
A) Fishbone Diagram
B) Is / Is Not Matrix
C) Measurement System Analysis
D) Control Chart
- Correct Answer: B) Is / Is Not Matrix
- Explanation: The Is / Is Not Matrix helps isolate problem characteristics by contrasting where, when, and what defects occur against similar areas where they do not occur.
2. What is the recommended number of macro steps when creating a High-Level Process Map in the Define Phase?
A) 1 to 2 steps
B) 3 to 7 steps
C) 15 to 25 steps
D) 50+ steps
- Correct Answer: B) 3 to 7 steps
- Explanation: High-Level Process Maps should remain concise (3 to 7 steps) to establish clear process limits without getting bogged down in micro-level activity details.
3. Why is an In and Out of the Box diagram used during the initial Define phase workshop?
A) To perform statistical hypothesis testing.
B) To visually establish project boundaries and prevent scope creep.
C) To calculate process capability statistics (CP / CPK).
D) To record formal employee performance reviews.
- Correct Answer: B) To visually establish project boundaries and prevent scope creep.
- Explanation: The In and Out of the Box method provides a clear visual distinction between included and excluded process elements.
Previous Post in this Series – 1015. Six Sigma Project Scope, Boundaries, Team Roles and Milestones
Next Post in Series: 1017. Project Charter Finalization and Define Tollgate Review Sign-off
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
