Overview
Define is where a selected opportunity becomes a bounded project. Voice of the customer covers identifying internal and external customers, collecting their needs through surveys, interviews, focus groups and complaint data, and translating vague needs into measurable critical-to-quality (CTQ) requirements with tools such as CTQ trees, the Kano model and quality function deployment (QFD). Business case and project charter covers the problem statement, scope, SMART goals, project performance measures and charter review with the sponsor. Project management tools cover Gantt charts, work breakdown, critical path, PERT estimates and toll-gate reviews. Analytical tools cover the seven management and planning tools, such as affinity diagrams, interrelationship digraphs, tree diagrams, matrix diagrams, prioritization matrices, process decision program charts and activity network diagrams.
Candidates must write and judge charter elements and pick the right planning tool for a situation. Define relies on Domain 2's financial measures and sets up the baseline work of Measure.
How it's tested
Questions mix judgment and calculation. You will judge charter elements (is this problem statement acceptable), classify customer requirements with Kano, read a QFD matrix, choose among the management and planning tools, and compute PERT durations or critical path slack. Look for the answer that keeps the project measurable, bounded and free of assumed causes.
-
Fix the charter
A draft problem statement, goal or scope is shown and you identify the flaw, such as an embedded solution, missing baseline, or unbounded scope.
-
Classify the requirement
A customer need is described and you place it in the Kano model or decide how it should flow into a CTQ or QFD matrix.
-
Pick the planning tool or compute the schedule
A planning need is described and you choose the management tool, or you calculate PERT expected time, variance, or the critical path.
A draft problem statement reads: "Late deliveries are caused by the outdated scheduling software, which must be replaced." The options praise it for being specific, or criticize it. A problem statement describes what is wrong, where, when and how much, with a baseline; it must not name a cause or solution, because Analyze has not happened. The correct choice rewrites it with the measured late-delivery rate and removes the software reference.
Subsections 4
Official subsections from the ASQ outline, in outline order.
4.1 Voice of the customerIdentifying customers, collecting their needs, and translating needs into CTQ requirements.
- What it means
- Voice of the customer (VOC) means identifying internal and external customers, gathering their stated and unstated needs with surveys, interviews, focus groups, observation and complaint data, and converting them into measurable requirements using CTQ trees, the Kano model and quality function deployment (QFD).
- What to understand
- Customer statements are usually vague ("fast service") and must be decomposed into measurable CTQs with specification limits ("order shipped within 24 hours"). The Kano model separates must-be, one-dimensional (performance) and attractive (delighter) needs, and QFD's house of quality relates customer needs to technical requirements with weighted relationships, often 9, 3 and 1.
- How it shows up
- A customer need or survey result is described and you classify it, choose a collection method, or read a house of quality to find the highest-priority technical requirement.
- Common confusion
- Treating must-be requirements as minor because customers rarely mention them; they cause strong dissatisfaction when absent even though they never delight.
4.2 Business case and project charterProblem statement, scope, goals, performance measures and charter review.
- What it means
- The business case explains why the project is worth doing, usually in financial or customer terms. The charter records the problem statement, scope (in and out), SMART goals, project metrics, team, timeline and sponsor approval, and is reviewed with the champion.
- What to understand
- A good problem statement states the gap with data (what, where, when, how big) without blaming a cause or prescribing a solution. Scope is bounded by process start and end points, often from a SIPOC, and goals are specific, measurable, achievable, relevant and time-bound. Primary metrics measure the improvement; secondary or consequential metrics guard against harming something else.
- How it shows up
- A draft charter element is presented and you identify its flaw, or a scope creep situation arises and you choose the right response.
- Common confusion
- Embedding a suspected root cause or solution in the problem statement, which locks the team into an answer before Measure and Analyze.
4.3 Project management (PM) toolsGantt charts, work breakdown structures, critical path, PERT and toll-gate reviews.
- What it means
- These tools plan and track the project: a work breakdown structure decomposes deliverables, Gantt charts show activities over time, the critical path method finds the longest path and slack, PERT estimates durations under uncertainty, and toll-gate (phase-gate) reviews confirm each DMAIC phase is complete before moving on.
- What to understand
- The critical path is the longest path through the network and has zero total slack; a delay on it delays the project. PERT expected time is (optimistic + 4 × most likely + pessimistic) / 6, with standard deviation (pessimistic − optimistic) / 6. Toll-gate reviews are where the champion confirms deliverables and decides to continue, redirect or stop.
- How it shows up
- Activity estimates or a network are given and you compute an expected duration, find the critical path, or decide which delay matters.
- Common confusion
- Assuming the critical path is the path with the most activities or the riskiest activity, rather than the longest total duration.
4.4 Analytical toolsThe seven management and planning tools used to organize ideas and plan action.
- What it means
- These are the affinity diagram, interrelationship digraph, tree diagram, matrix diagram, prioritization matrix, process decision program chart (PDPC) and activity network diagram, used mostly with qualitative information in Define and later phases.
- What to understand
- Affinity diagrams group many ideas into natural themes; interrelationship digraphs show cause and effect links, where the item with most outgoing arrows is a key driver; tree diagrams break a goal into actions; matrix diagrams show relationships between sets; prioritization matrices rank options against weighted criteria; PDPC anticipates what could go wrong in a plan; activity network diagrams sequence tasks.
- How it shows up
- A planning situation is described and you choose the tool that fits, or read a digraph to find the root driver.
- Common confusion
- Mixing up the affinity diagram (organizes ideas into groups) with the interrelationship digraph (shows causal links among them).
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Kano model
Kano classifies needs as must-be (expected; absence causes dissatisfaction), one-dimensional or performance (satisfaction rises with level) and attractive or delighters (unexpected; presence delights), plus indifferent and reverse.
- Remember
- Delighters decay into performance and then must-be needs over time as customers come to expect them.
- Tested as
- Classification items describe a feature and customer reaction and ask for its Kano category.
- Trap
- Labeling a basic safety or hygiene feature as a delighter because customers do not mention it.
-
Critical to quality (CTQ) tree
A tree that breaks a broad customer need into drivers and then into measurable CTQ characteristics with targets and specification limits.
- Remember
- A CTQ must be measurable and tied to what the customer values.
- Tested as
- Asked when converting vague VOC statements into project metrics.
- Trap
- Stopping at a driver such as "friendly service" that cannot be measured directly.
-
Quality function deployment (house of quality)
A matrix that relates customer needs (rows, with importance weights) to technical requirements (columns), scoring strength of relationships, commonly 9 strong, 3 medium, 1 weak; the roof shows correlations among technical requirements.
- Remember
- Technical priority = sum over needs of (importance × relationship score).
- Tested as
- Items give a small matrix and ask which technical requirement has the highest priority.
- Trap
- Ranking technical requirements by the number of relationships instead of the weighted sum.
-
Problem statement
A factual description of the gap: what is wrong, where and when it occurs, its magnitude with a baseline, and its impact.
- Remember
- No causes, no solutions, no blame.
- Tested as
- Frequently tested by showing a flawed draft.
- Trap
- Accepting a statement that names a suspected cause because it sounds specific.
-
SMART goal statement
A goal that is specific, measurable, achievable, relevant and time-bound, for example reduce billing errors from 4.2% to 1.5% by June 30.
- Remember
- Include baseline, target and date.
- Tested as
- Charter items ask which goal statement is best.
- Trap
- Choosing an aspirational goal such as "eliminate all errors" that is neither achievable nor time-bound.
-
Scope and SIPOC
SIPOC (suppliers, inputs, process, outputs, customers) maps a process at high level and sets the start and end points that bound project scope.
- Remember
- State what is in scope and what is out of scope.
- Tested as
- Asked when a project is too broad or when scope creep appears.
- Trap
- Absorbing new requests into the current project rather than taking them to the champion as a change or a new project.
-
PERT estimate
Expected time te = (a + 4m + b) / 6 and standard deviation σ = (b − a) / 6, where a is optimistic, m is most likely, b is pessimistic.
- Remember
- Path variance is the sum of activity variances (σ²), not the sum of standard deviations.
- Tested as
- Calculation items: for a = 4, m = 6, b = 14 days, te = 7 days and σ ≈ 1.67 days.
- Trap
- Averaging the three estimates equally, which gives 8 days instead of 7.
-
Critical path and slack
The critical path is the longest-duration path through the activity network; total slack = late start − early start (or late finish − early finish).
- Remember
- Critical activities have zero slack; delaying any of them delays the whole project.
- Tested as
- Network questions ask for project duration or which activity can slip without delay.
- Trap
- Thinking a non-critical activity can slip by any amount; once it exceeds its slack it becomes critical.
-
Interrelationship digraph
Shows cause-and-effect links among issues with arrows; items with most outgoing arrows are drivers, items with most incoming arrows are outcomes.
- Remember
- Work on the key driver to influence many outcomes.
- Tested as
- Items show arrow counts and ask which issue to address first.
- Trap
- Choosing the item with most incoming arrows, which is an effect.
-
Process decision program chart (PDPC)
Extends a tree diagram by listing what could go wrong at each step of a plan and the countermeasures.
- Remember
- PDPC is a contingency-planning tool for implementation risk.
- Tested as
- Chosen when a team must anticipate problems in a plan before rollout.
- Trap
- Confusing it with FMEA, which rates risk numerically on a process or design.
-
Toll-gate review
A formal review at the end of each DMAIC phase where the champion confirms deliverables and decides to continue, redirect or stop the project.
- Remember
- Stopping a project that no longer has a business case is a valid outcome.
- Tested as
- Appears when a project's data reveal the problem is smaller than expected.
- Trap
- Assuming a project must always continue once chartered.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Must-be vs. performance vs. attractive requirements (Kano)
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Must-be | Basic expectations taken for granted | Absence causes strong dissatisfaction; presence earns no extra credit | Ignored because customers rarely state them |
| One-dimensional (performance) | Satisfaction rises with how well it is delivered | Linear relationship, such as fuel economy | Treated as a delighter because customers mention it often |
| Attractive (delighter) | Unexpected features that surprise customers | Presence delights; absence causes no dissatisfaction | Forgetting delighters become expected over time |
Affinity diagram vs. interrelationship digraph vs. tree diagram vs. PDPC
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Affinity diagram | Groups many ideas into natural themes | Organizes; shows no causation | Used to find root drivers |
| Interrelationship digraph | Maps causal links among issues | Arrow counts identify drivers and outcomes | Picking the most-incoming item as the driver |
| Tree diagram | Breaks a goal into progressively detailed actions | Hierarchical decomposition | Confused with a fishbone, which organizes causes of an effect |
| PDPC | Lists what could go wrong in a plan and countermeasures | Contingency planning added to a tree | Confused with FMEA's numeric risk rating |
Problem statement vs. goal statement vs. scope
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Problem statement | Describes the current gap with data | What, where, when, how big; no cause or solution | Naming a cause |
| Goal statement | States the target improvement and date | Baseline to target by a deadline | Vague or unachievable targets |
| Scope | Boundaries of the process the project may change | Start and end points, in and out of scope | Unbounded scope that cannot finish in four to six months |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Specific but presumptive problem statement
- What candidates pick
- A problem statement naming the suspected cause.
- Why it looks right
- It sounds concrete and actionable.
- Why it's wrong
- The cause is unproven until Analyze; naming it biases data collection and may solve the wrong problem.
Clue to watch for The statement contains words such as caused by, due to, or must implement.
-
Absorbing scope creep
- What candidates pick
- Add a stakeholder's related request to the current project.
- Why it looks right
- It seems helpful and efficient.
- Why it's wrong
- Expanding scope without sponsor approval endangers the timeline; the request should go to the champion as a scope change or separate project.
Clue to watch for A new request arrives after the charter was signed.
-
Most arrows in
- What candidates pick
- The digraph item with the most incoming arrows as the issue to fix.
- Why it looks right
- It looks central because many arrows point to it.
- Why it's wrong
- Incoming arrows mark an outcome; the key driver has the most outgoing arrows.
Clue to watch for The question gives in and out arrow counts.
-
Simple average in PERT
- What candidates pick
- (a + m + b) / 3 as the expected duration.
- Why it looks right
- It is the familiar mean of three numbers.
- Why it's wrong
- PERT uses a beta-distribution approximation weighting the most likely value by 4 and dividing by 6.
Clue to watch for Three time estimates are given.
-
Longest list is critical
- What candidates pick
- The path with the most activities as the critical path.
- Why it looks right
- More activities seem to mean more time.
- Why it's wrong
- The critical path is the path with the greatest total duration, regardless of activity count.
Clue to watch for Paths have different numbers of activities and different durations.
-
Project must continue
- What candidates pick
- Continue the project at the Measure toll gate even though baseline data show the problem is far smaller than estimated.
- Why it looks right
- Stopping feels like failure.
- Why it's wrong
- Toll gates exist to confirm the business case; a project without one should be redirected or closed.
Clue to watch for New data undermine the original financial justification.
Answer framework
Use these steps to judge Define-phase choices the way the exam expects.
- Confirm who the customers are and translate their stated needs into measurable CTQs with targets and limits.
- Check every charter element: the problem statement has a baseline and no cause or solution, the goal is SMART, and the scope has clear start and end points.
- For schedule questions, compute PERT values with the 1-4-1 weighting and find the longest-duration path before judging any delay.
- Choose the planning tool by purpose: group ideas, find causal drivers, decompose goals, relate two sets, rank options, anticipate failure, or sequence tasks.
- When new information or requests appear, return to the champion at a toll gate rather than changing scope or continuing silently.
Practice question
Want more like this? The CSSBB practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the charter because it is the most frequently tested skill. Collect ten flawed problem statements and goal statements from practice material and rewrite each until spotting causes, solutions, missing baselines and missing dates is automatic. Add scope work with SIPOC so you can tell a bounded project from an unbounded one.
Next, cover VOC: the Kano categories with one example each, CTQ trees, and QFD. Work at least two small house-of-quality calculations by hand so the importance-times-relationship sum is familiar.
Then practice the calculations: PERT expected time and standard deviation, path variance as the sum of activity variances, and critical path with forward and backward passes. These are quick points when practiced and costly time sinks when not.
The commonly underestimated area is the seven management and planning tools. They look similar, so learn each by the question it answers. Put a one-line tool selector and the PERT formulas on a tabbed page in your open-book reference.
Afterwards, practice integrated scenarios that move from charter to measurement plan, then continue to Measure, where the CTQs defined here become operational definitions and data collection plans.
FAQ
How many questions come from Define?
ASQ assigns 20 of the 150 scored questions to Define, about 13.3% of the exam.
What makes a good problem statement?
It states what is wrong, where and when it occurs, and how big it is with baseline data and impact. It does not name a cause, propose a solution or assign blame.
How do I calculate a PERT estimate?
Expected time is (optimistic + 4 × most likely + pessimistic) / 6 and the standard deviation is (pessimistic − optimistic) / 6. Add variances, not standard deviations, along a path.
What is the difference between a must-be and a delighter in Kano?
A must-be need causes dissatisfaction when missing but no extra satisfaction when present. A delighter creates satisfaction when present but causes no complaint when absent.
Which management tool finds root drivers among many issues?
The interrelationship digraph. The issue with the most outgoing arrows is the key driver; the one with the most incoming arrows is a key outcome.
What should a Black Belt do about scope creep?
Document the request and take it to the champion, who decides whether to change the charter or start a separate project. The Black Belt should not silently expand scope.
How does Define connect to Measure?
The CTQs and project metrics defined here become the operational definitions, data collection plan and baseline capability work done in Measure.
Other Quality Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 4 knowledge
You have covered voice of the customer, charters and scope, project scheduling with PERT and critical path, and the management and planning tools. Test whether you can spot a flawed charter and solve schedule items under time pressure.