SYE6047 Chap.4 Define and Measure in DMAIC
Define and Measure in DMAIC
Define the gap without solving it
A DMAIC project begins with an observable gap, not a favourite cause or solution. A useful problem statement identifies the symptom, magnitude, location and period. It avoids blame and keeps the target separate from the present condition.
The business case explains why the gap matters, while scope identifies the process boundaries and prevents the team from quietly expanding the project.
Translate voice into a CTQ
Voice of customer statements are often emotional or broad: service is slow, the form is confusing, the product feels unreliable.
A critical-to-quality characteristic turns that language into a measurable requirement with a unit, target or boundary and population. The translation must preserve the customer's meaning. Measuring call length may be convenient, but it is a poor substitute if the concern is resolution on first contact.
Map before measuring
A SIPOC map names suppliers, inputs, the high-level process, outputs and customers.
It defines the system around the CTQ and exposes missing stakeholders without becoming a detailed flowchart. The measurement plan then fixes the operational definition, source, sampling unit, timing, collector and recording method.
It should also anticipate missing data, repeat observations and changes in case mix.
Establish a defensible baseline
The Measure phase quantifies present performance and assesses whether the data deserve trust. Teams check the measurement system, sampling design and data integrity before interpreting charts or rates. A baseline is not just a number.
It is a number tied to a definition, process boundary and collection method that another analyst could reproduce.
What this chapter covers
- 01
Problem statement
- 02
Business case and goal statement
- 03
Project scope
- 04
Voice of customer
- 05
Critical-to-quality translation
- 06
SIPOC boundaries
- 07
Operational definitions
- 08
Sampling and baseline planning
Worked example · free
Repair a solution-shaped project charter
- 3Remove the assumed cause and remedy.
- 4Write a measurable problem statement and CTQ.
- 3Specify a reproducible baseline plan.
Key terms
- Problem Statement
- A neutral description of the observable gap, magnitude, location and period.
- Business Case
- The reason the performance gap matters to customers and the organisation.
- CTQ
- A measurable requirement translated from a customer need.
- SIPOC
- A high-level map of suppliers, inputs, process, outputs and customers.
- Operational Definition
- A precise rule that allows different observers to measure the same characteristic consistently.
Define and Measure in DMAIC FAQ
Why should a problem statement exclude causes?
An untested cause narrows investigation and makes contrary evidence harder to see. Define the performance gap first; candidate causes belong in Analyze after the measurement system and baseline are credible. A neutral statement also lets the team compare explanations and remedies without treating disagreement as resistance to a solution already embedded in the charter. It keeps project approval separate from solution approval.
How detailed should a SIPOC be?
It should show the few high-level process steps needed to establish boundaries and interfaces. If it contains every decision and rework loop, it is functioning as a detailed process map rather than a SIPOC.
What makes a baseline reproducible?
Another analyst should be able to identify the same eligible cases, apply the same definitions and calculate the same measure from the stated source. Document exclusions, time rules, missing values and sampling method.
Exam move
Take five solution-shaped statements and rewrite each into symptom, magnitude, location and period. Then build a one-line CTQ and a compact measurement plan with who, what, where, when and how. Check that the chosen measure still represents the original customer voice. For every rewritten charter, underline any word that assumes blame, cause or remedy and remove it until evidence can test the proposition.
Draw a five-box SIPOC that stops at the stated process boundary, then list the detailed questions that belong in a later process map rather than forcing them into the high-level view. Audit the measurement plan with awkward cases: reopened work, missing timestamps, partial service, duplicate records and excluded periods. Decide each rule before seeing the baseline.
Finally, ask another person to apply the operational definition to the same five cases and compare classifications. If the observers disagree, repair the rule before calculating performance. A timed response should finish with the exact field that crosses from Define into Measure, its unit, its source and the rule that makes the value reproducible.
