Overview
Domain 1 sets the business context for everything a Green Belt does. It covers how Six Sigma projects connect to organizational goals and metrics, how lean thinking defines value from the customer's point of view and attacks waste across a value stream, and how Design for Six Sigma (DFSS) road maps such as DMADV are used when a process or product must be designed rather than repaired. Failure mode and effects analysis (FMEA) appears here as the risk tool that DFSS and process work share.
Candidates need to judge fit, not recite history: which projects deserve resources, which lean concept explains a delay, and whether a scenario calls for DMAIC or a design road map. The section is lighter in calculation than the Measure and Analyze phases, but its vocabulary (value, flow, pull, RPN, process owner, organizational driver) is reused in Define project selection and in Improve and Control lean tools.
How it's tested
Expect short scenarios about a business problem, a proposed project or a process map, followed by a BEST or MOST appropriate question. Few items need arithmetic beyond an FMEA risk priority number. The right answer usually ties the action to customer value, a measurable organizational goal, or the correct improvement road map for the situation described.
-
Pick the right road map
A scenario describes an existing process with a defect problem or a brand-new product or process; you choose DMAIC for improving what exists and a DFSS road map such as DMADV when the design itself must be created or replaced.
-
Classify the waste or activity
A list of process steps or a short value stream description asks which step is non-value-added, which type of waste it shows, or which lean principle (value, value stream, flow, pull, perfection) is being violated.
-
Rank the FMEA risk
Severity, occurrence and detection ratings are given for several failure modes and you identify the highest risk priority number or decide which action should be taken first, remembering that a very high severity can justify action regardless of RPN.
A hospital wants to cut discharge time and has data showing patients wait hours for paperwork. One option proposes building a new discharge unit from scratch; another proposes a DMAIC project. Ask: does the process exist and produce measurable defects? Yes, so DMAIC fits. DFSS is reserved for when the current design cannot meet requirements or nothing exists yet. The answer is the DMAIC project scoped to the discharge process.
Topics 3
Official topics from the ASQ outline, in outline order.
1.1 Six Sigma and organizational goalsWhy Six Sigma exists and how projects connect to strategic goals, drivers and metrics.
- What it means
- Six Sigma is a disciplined, data-driven approach to reducing variation and defects so that processes reliably meet customer requirements, and it earns its place by moving organizational goals such as cost, quality, delivery and customer satisfaction. Projects are chosen because they move a strategic metric, not because a problem is annoying.
- What to understand
- Know the chain from organizational drivers (profit, market share, customer loyalty) to key metrics such as a balanced scorecard, then to individual projects with measurable objectives. Understand that a project which cannot show a link to a goal or a financial or customer metric is weak, however technically interesting.
- How it shows up
- A scenario lists several candidate projects and asks which one leadership should approve; the correct choice is the one tied to a stated strategic goal with measurable impact, not the cheapest or the most visible.
- Common confusion
- Candidates treat Six Sigma as a statistics toolkit; the exam treats it as a business-improvement system, so answers that start with a tool before establishing a goal are usually wrong.
1.2 Lean principles in the organizationValue, waste, flow, pull and value stream mapping as the lean lens on a process.
- What it means
- Lean defines value from the customer's view and removes everything that consumes resources without adding that value. The five principles are specify value, identify the value stream, make the work flow, let the customer pull, and pursue perfection. A value stream map shows material and information flow, cycle times, inventory and wait time across the whole chain.
- What to understand
- Classify activities as value-added (changes the product in a way the customer will pay for and is done right the first time), business-necessary non-value-added (required by regulation or the business today) and pure waste. Know the classic wastes (overproduction, waiting, transport, overprocessing, inventory, motion, defects, plus unused talent) and how a current-state map leads to a future-state map.
- How it shows up
- A process description notes that parts sit in queues between departments or that reports are produced that nobody reads; you name the waste or the lean principle being broken and pick the countermeasure that improves flow.
- Common confusion
- Inspection feels valuable but is non-value-added from the customer's view, and candidates often label it value-added; in lean terms it may be business-necessary but it does not transform the product.
1.3 Design for Six Sigma (DfSS) methodologiesDFSS road maps such as DMADV and IDOV, and FMEA as the risk analysis tool.
- What it means
- DFSS builds quality into a new product, service or process during design so it meets requirements at launch, rather than fixing defects later. Common road maps are DMADV (define, measure, analyze, design, verify) and IDOV (identify, design, optimize, verify). FMEA, in design (DFMEA) and process (PFMEA) forms, rates each failure mode for severity, occurrence and detection.
- What to understand
- Use DFSS when a process does not exist or when an existing design has hit its entitlement and cannot meet requirements through incremental improvement. Know the risk priority number: RPN = severity x occurrence x detection, each typically rated 1 to 10, with a high detection score meaning the failure is hard to detect. After actions, the FMEA is re-scored to confirm risk dropped.
- How it shows up
- Questions give FMEA ratings and ask which failure mode to address first, or describe a launch of a new service and ask which methodology fits, with DMADV the expected answer over DMAIC.
- Common confusion
- A detection rating of 10 means very poor detection, not excellent detection, so candidates who read it as a good score rank risks backwards.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Risk priority number (RPN)
RPN = severity x occurrence x detection, with each factor usually scored 1 to 10, so the result ranges from 1 to 1,000 and ranks failure modes for action.
- Remember
- A high detection score means the failure is unlikely to be caught before it reaches the customer, so it raises the RPN rather than lowering it.
- Tested as
- FMEA tables with three or four failure modes are the main calculation this section asks for, usually followed by which mode to act on first.
- Trap
- Ranking only by RPN when one mode has severity 9 or 10 with safety or regulatory impact; most practitioners act on very high severity first even if its RPN is lower.
-
Lean's five principles
Specify value from the customer's view, map the value stream, create flow, establish pull from the customer, and pursue perfection through continuous improvement.
- Remember
- The order matters: you cannot improve flow until value is defined and the value stream is visible.
- Tested as
- Scenario stems describe a symptom (large batches, queues, building to forecast) and ask which principle is violated.
- Trap
- Confusing pull (produce only when downstream signals demand) with flow (work moves without stopping), which are related but distinct.
-
Value-added vs. non-value-added
A step is value-added only if the customer would pay for it, it changes form, fit or function, and it is done right the first time; everything else is either business-necessary or waste.
- Remember
- Inspection, approvals, rework and moving material are non-value-added, even when required by policy.
- Tested as
- Value stream maps and process lists ask you to compute or recognize the share of value-added time, often a small fraction of total lead time.
- Trap
- Labeling a step value-added because it is important to the business rather than to the customer.
-
Eight wastes
Overproduction, waiting, transportation, overprocessing, inventory, motion, defects and unused human talent, often remembered as DOWNTIME.
- Remember
- Overproduction is often called the worst waste because it creates inventory, transport and hidden defects downstream.
- Tested as
- A described behavior must be matched to the right waste type, for example extra polishing the customer never sees is overprocessing.
- Trap
- Mixing up transportation (moving material or information) with motion (people moving or reaching unnecessarily at the workstation).
-
Value stream map (VSM)
A one-page picture of material and information flow for a product family, showing process steps, cycle times, inventory between steps and total lead time.
- Remember
- Build the current state first from observation, then design a future state with less waiting and inventory, then plan the transition.
- Tested as
- Questions ask what a VSM shows that a simple flowchart does not (information flow, inventory, timeline) or which number reveals the biggest opportunity.
- Trap
- Drawing the map from the procedure manual instead of walking the actual process, which hides real queues and rework loops.
-
DMAIC vs. DMADV
DMAIC (define, measure, analyze, improve, control) improves an existing process; DMADV (define, measure, analyze, design, verify) creates a new design or replaces one that cannot meet requirements.
- Remember
- The trigger for DMADV is a new product or process, or an existing one that has reached the limit of what incremental improvement can deliver.
- Tested as
- Methodology-selection questions describe the situation and ask which road map fits.
- Trap
- Choosing DMADV just because the problem is large; size is not the test, whether the design itself must change is.
-
DFMEA vs. PFMEA
A design FMEA looks at how a product design could fail to perform its function; a process FMEA looks at how manufacturing or service steps could fail to produce the intended output.
- Remember
- The design FMEA usually comes first and feeds the process FMEA; both feed the control plan later in the Control phase.
- Tested as
- A scenario mentions a failure caused by an assembly step or by a specification choice, and you pick which FMEA should capture it.
- Trap
- Putting a design weakness in the process FMEA and expecting operators to control a failure that only a design change can remove.
-
Organizational drivers and metrics
Drivers are the strategic forces the business must respond to, such as profitability, customer loyalty and market share; metrics such as a balanced scorecard translate them into measurable targets.
- Remember
- A good Six Sigma project charter traces its goal back to one of these metrics so the benefit can be shown in business terms.
- Tested as
- Project-approval questions reward the option with a measurable link to a strategic metric.
- Trap
- Selecting a project because a manager is enthusiastic about it, without evidence it affects a key metric.
-
Sigma level and 3.4 DPMO
Six Sigma performance is commonly expressed as 3.4 defects per million opportunities, which corresponds to a 6 sigma short-term capability after the conventional 1.5 sigma long-term shift.
- Remember
- 3.4 DPMO is a long-term figure from a normal distribution 4.5 standard deviations from the mean; it is a convention, not a law of nature.
- Tested as
- Overview questions use it to describe what Six Sigma quality means; the detailed DPMO calculation is tested in the Define phase business results topic.
- Trap
- Stating that 6 sigma means 3.4 defects per million units; the measure is per million opportunities.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
DMAIC vs. DMADV vs. IDOV
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| DMAIC | Define, measure, analyze, improve, control for an existing process | Fixes a process that exists and has measurable defects | Using it to launch a brand-new service with no baseline data |
| DMADV | Define, measure, analyze, design, verify for a new or redesigned process or product | Ends with verify, proving the new design meets customer requirements | Assuming the design and verify steps are the same as improve and control |
| IDOV | Identify, design, optimize, verify, a DFSS road map common in product design | Starts from identifying customer requirements and optimizes the design before verification | Treating IDOV as a different goal from DMADV; both are DFSS road maps for designing quality in |
Value-added vs. business-necessary vs. waste
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Value-added | Transforms the product or service in a way the customer will pay for, done right the first time | The customer would notice and value its absence | Counting rework as value-added because it eventually fixes the product |
| Business-necessary non-value-added | Required today by regulation, contract or the current system, but not valued by the customer | Minimize it; you cannot simply delete it | Deleting a regulatory check in a future-state map |
| Pure waste | Consumes time or resources with no customer value and no business requirement | Eliminate it | Keeping it because it has always been done |
Severity vs. occurrence vs. detection in FMEA
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Severity | How serious the effect of the failure is for the customer or user | Usually lowered only by a design change | Expecting inspection to reduce severity |
| Occurrence | How likely the cause is to happen | Lowered by preventing the cause, for example mistake-proofing | Rating occurrence by how often the failure is detected |
| Detection | How likely current controls are to catch the failure before it reaches the customer | A high number means poor detection | Reading a 10 as excellent detection |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Lowest cost project wins
- What candidates pick
- The project with the smallest budget or quickest payback.
- Why it looks right
- It sounds financially prudent and easy to approve.
- Why it's wrong
- Project selection is about alignment with strategic goals and measurable impact on key metrics; a cheap project that moves nothing important is a poor choice.
Clue to watch for Look for a stated strategic goal or customer metric in the stem and pick the project that moves it.
-
Inspection as value-added
- What candidates pick
- Labeling a final inspection or approval step as value-added.
- Why it looks right
- Inspection protects the customer and feels essential.
- Why it's wrong
- Inspection does not change the product; at best it is business-necessary non-value-added and a target for reduction through prevention.
Clue to watch for Ask whether the step changes form, fit or function in a way the customer would pay for.
-
Bigger problem means DFSS
- What candidates pick
- DMADV whenever the scenario describes a large or costly problem.
- Why it looks right
- Design sounds more thorough than improvement.
- Why it's wrong
- DFSS is triggered by the need for a new design or by a design that cannot reach requirements, not by problem size; an existing process with measurable defects usually calls for DMAIC.
Clue to watch for Look for words such as new product, new service, launch, or 'the current design cannot meet the requirement'.
-
Detection read backwards
- What candidates pick
- The failure mode with the lowest detection score as the biggest risk.
- Why it looks right
- Low numbers usually mean bad performance in everyday scoring.
- Why it's wrong
- In FMEA a detection rating of 1 means the failure is almost certain to be caught; 10 means it is unlikely to be caught, so it increases risk.
Clue to watch for Compute the RPN and check the scale definitions given in the stem before ranking.
-
RPN only, ignoring severity
- What candidates pick
- Act first on the highest RPN even when another failure mode has severity 10 affecting safety.
- Why it looks right
- RPN is the headline number in the table.
- Why it's wrong
- RPN multiplies three ordinal scales, so very different risks can share a number; standard practice is to address very high severity, especially safety or regulatory effects, regardless of RPN.
Clue to watch for A severity of 9 or 10 with words such as injury, safety or regulatory noncompliance.
-
Pull confused with flow
- What candidates pick
- Calling one-piece flow a pull system, or a kanban signal a flow improvement.
- Why it looks right
- Both reduce inventory and appear together in lean programs.
- Why it's wrong
- Flow is about work moving continuously without stops; pull is about producing only when downstream demand signals it. A scenario about building to forecast is a pull problem.
Clue to watch for Building ahead of demand or pushing work to the next step points to pull; queues and stop-start movement point to flow.
Answer framework
For Domain 1 scenarios about choosing projects, classifying work or picking a road map, use this sequence.
- Identify the organizational goal or customer requirement the scenario names, and treat it as the yardstick for every option.
- Decide whether the process already exists with measurable defects (DMAIC) or must be designed or redesigned to meet requirements (DFSS such as DMADV).
- For process descriptions, classify each step as value-added, business-necessary or waste, and name the specific waste type when asked.
- For FMEA tables, compute severity times occurrence times detection, then check whether any very high severity overrides the RPN ranking.
- Choose the option that improves the process system with data, and reject answers that blame people, add inspection or skip the link to customer value.
Practice question
Want more like this? The CSSGB practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with Six Sigma and organizational goals so that you have the yardstick the rest of the exam uses: every good project ties to a measurable goal and to the customer. Then move to lean principles, because value, waste and flow vocabulary returns in the Improve and Control phases. Finish with DFSS and FMEA, which are the most procedural parts of the section.
High-priority concepts are the value-added test, the eight wastes, the DMAIC versus DMADV decision, and the RPN calculation with its detection scale. Practice rating three or four failure modes by hand until the multiplication and the 'high detection is bad' rule are automatic, and draw a simple current-state value stream map for a process you know to see why lead time dwarfs value-added time.
Candidates underestimate this section because it has little statistics, then lose points on judgment questions where two answers sound like good management. Train yourself to reject answers that add inspection, blame individuals or skip data. After this section, take a short mixed quiz on project selection and FMEA, then move to the Define phase, where project identification and business results build directly on these ideas.
FAQ
How many CSSGB questions come from this section?
ASQ lists 13 of the 100 scored questions for this section, about 13% of the exam. The computer-based exam also carries 10 unscored pretest items that are not assigned to sections publicly.
Is there much math in Domain 1?
Very little. The main calculation is the FMEA risk priority number (severity x occurrence x detection); most other questions test judgment about project fit, waste and methodology choice.
When should a Green Belt use DMADV instead of DMAIC?
Use DMADV or another DFSS road map when designing a new product or process, or when an existing design cannot meet requirements no matter how well it is run. Use DMAIC to improve an existing process with measurable defects.
What is the difference between lean and Six Sigma?
Lean focuses on speed and flow by removing waste and non-value-added time, while Six Sigma focuses on reducing variation and defects with data. Lean Six Sigma combines both, and the CSSGB BoK includes lean principles and lean tools alongside statistical methods.
Does a high detection number in FMEA mean the failure is easy to catch?
No. On standard FMEA scales a detection rating of 10 means current controls are unlikely to catch the failure, so a high detection number increases the RPN.
How long should I spend on this section?
Plan roughly 15–20 hours within a 120-hour plan, with most of that time spent on lean concepts and FMEA practice rather than memorizing definitions.
How does this section connect to the rest of the exam?
Project selection and organizational metrics feed the Define phase charter and business results, lean principles return as Improve and Control lean tools, and the FMEA is a primary input to the control plan when sustaining improvements.
Other Quality Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
You have worked through project alignment, the eight wastes, DMAIC versus DMADV and FMEA risk ranking. Check whether you can make those calls quickly on exam-style scenarios.