ASQ-CQE Section 3: Product, Process, and Service Design

Section 3 Flashcards

Use this deck to rehearse the design domain quickly. Press Space to flip the card and use the left and right arrow keys to move through the deck.

Section Scope and How the Exam Uses It

Product, process, and service design sits at the prevention side of quality engineering. That makes it strategically important. If design inputs are weak, CTQs are vague, tolerances are poorly defined, or verification logic is incomplete, downstream control becomes expensive and fragile.

Expect the CQE exam to test this section with applied prompts such as:

• How should a requirement be classified: critical, major, minor, CTQ, or key characteristic?
• Which tool is the best next step: QFD, FMEA, DFX, DFSS, traceability matrix, or design review?
• What do the drawing or GD&T callouts actually require?
• Is the issue about verification, validation, IQ, OQ, or PQ?
• Which reliability or maintenance metric or model applies?

The strongest study approach is to treat each subtopic as a decision framework rather than a memorization list.

Classification of Quality Characteristics

One of the first design responsibilities is deciding which characteristics matter most and why. This is not just labeling. Classification drives control intensity, reaction plans, validation depth, and risk treatment.

CQE questions often test context rather than labels. A cosmetic issue can become critical if it obscures a safety label or damages a sealing surface. A dimensional feature that looks routine can become critical if it governs torque retention, electrical fit, or fluid containment.

This section also connects directly to Kano and VOC thinking. A customer statement such as “easy to use” or “lasts all day” is not yet a usable CTQ. It must be translated into a measurable requirement with explicit conditions and acceptance criteria.

• Must-be: basic expected requirements that mainly prevent dissatisfaction.
• One-dimensional: performance requirements that scale satisfaction up or down.
• Attractive: delighters that create positive surprise but are not always expected.

The exam trap here is assuming that every customer-stated need is already a CTQ. It is not. The CQE answer is usually to translate VOC into measurable engineering or service targets first.

Design Inputs, Design Techniques, and Review

Design inputs

Design begins with customer needs, regulatory requirements, field knowledge, risk, and business constraints. The CQE is expected to turn those inputs into robust design logic rather than vague objectives.

The high-value relationship to remember is: QFD helps determine what matters, FMEA helps protect what matters, DFX improves downstream performance, and DFSS is how you design for capability before production starts.

Design review

Design review is a preventive checkpoint, not a ceremonial meeting and not the same thing as verification testing. Strong design reviews are staged, cross-functional, evidence based, and action-tracked.

• Include design, manufacturing, quality, supply chain, service, and customer or supplier voices when needed.
• Use objective evidence, not unsupported opinion.
• Document actions, owners, due dates, and closure evidence.
• Review risks, assumptions, interfaces, tolerances, and verification coverage.

The CQE exam often rewards the answer that brings in cross-functional review early rather than the answer that adds more downstream inspection. This aligns directly with Crosby’s prevention logic, Juran’s quality planning, and Toyota’s emphasis on consensus before execution.

Technical Drawings and Specifications

This domain is about design intent and interpretation. A CQE does not have to be a full drafting specialist, but must understand what a drawing or specification is trying to control and how that links to process capability and inspection.

Core interpretation areas

• Orthographic, isometric, and section views
• Title blocks, revisions, units, and default tolerances
• Bilateral, unilateral, and limit tolerances
• Surface finish, material requirements, notes, and process specs
• GD&T intent: datums, form, orientation, location, runout, and profile

Common CQE traps in this area are basic but costly: overlooking units, missing default tolerances in the title block, ignoring revision level, or focusing only on dimensions while missing note-driven requirements such as heat treat, coating, or inspection method.

A strong mental model is that GD&T exists to protect functional relationships, not just individual coordinates. It often enables more economical manufacturing than tight coordinate tolerancing because it aligns variation with actual assembly and use.

Tolerance stack-up thinking

CQE candidates should distinguish worst-case and statistical stack-up.

• Worst-case: assumes all contributors hit their extreme limits together; used when guaranteed fit is required.
• RSS / statistical: assumes variation behaves probabilistically and contributors are reasonably independent; can reduce apparent stack-up but relies on assumptions.

When the consequence of interference or loss of clearance is severe, worst-case logic is usually the safer answer unless the scenario explicitly supports statistical treatment.

Verification and Validation

This distinction is a recurring CQE exam favorite. A product can pass all internal requirements and still fail validation if it does not work for the customer in real use conditions.

For equipment and process qualification, remember the common sequence:

• IQ: Installation Qualification. Was it installed correctly per requirements?
• OQ: Operational Qualification. Does it operate across the defined parameter space, including challenge conditions?
• PQ: Performance Qualification. Does it consistently produce acceptable output under normal operating conditions?

The exam trap is confusing OQ and PQ. OQ is about parameter range and challenge testing. PQ is about routine, sustained performance under actual use conditions.

Another trap is assuming that “we tested it” means verification is complete. It does not unless the test is traceable to requirements and has explicit acceptance criteria.

Reliability and Maintainability

Reliability engineering in the CQE context is about understanding how systems fail, how often they fail, how quickly they can be restored, and how design and maintenance choices influence performance over time.

Maintenance approaches

• Preventive maintenance: time-based replacement or servicing.
• Predictive maintenance: condition-based actions using vibration, thermography, oil analysis, or similar signals.
• Reliability-Centered Maintenance: selects strategy based on function, failure mode, and consequence.
• Total Productive Maintenance: operator-involved equipment care tied to OEE and process stability.

Key metrics

The exam trap is mixing up reliability and availability. Reliability is about failure-free performance over time. Availability includes repair time, so it reflects both reliability and maintainability.

Common reliability models

• Exponential: constant failure rate, often associated with random useful-life behavior.
• Weibull: flexible model that can represent infant mortality, random life, or wear-out depending on beta.
• Bathtub curve: infant mortality, useful life, and wear-out phases.

A Weibull beta below 1 suggests early-life failures. Around 1 suggests roughly constant failure behavior. Above 1 suggests wear-out. The practical point is that your maintenance and corrective actions should change depending on the failure pattern.

Risk Assessment Tools in Design and Reliability

Section 3 expects the CQE to know the intent and structure of the major reliability and hazard tools, especially FMEA and related methods.

• dFMEA: protects the design against functional and failure risks.
• pFMEA: protects the manufacturing or service delivery process.
• uFMEA: focuses on failure in actual use conditions.
• FMECA: extends FMEA with criticality emphasis.
• Hazard analysis: used when system hazards and safety consequences must be examined more formally.

For the CQE exam, know the logic of severity, occurrence, and detection, but also know the limitation of RPN. Different S/O/D combinations can produce the same RPN while representing very different risks. Severity deserves special attention, especially when safety or regulation is involved.

Another strong exam cue is that prevention is stronger than inspection. If the answer choice merely adds appraisal to a high-risk design problem while ignoring prevention, it is often the weaker choice.

High-Value Exam Traps and Decision Cues

• If a requirement is not measurable, it is not ready to act as a CTQ.
• Do not confuse characteristic classification with defect classification.
• QFD translates needs; FMEA protects needs; traceability proves coverage.
• Design review is not the same as verification testing.
• Title blocks, notes, and revisions are often the hidden answer in drawing questions.
• Verification checks specified requirements. Validation checks intended use.
• IQ, OQ, and PQ primarily qualify equipment or process performance, not just product output.
• Availability is not the same thing as reliability.
• RPN is useful, but severity and consequence still require separate judgment.
• For safety-critical or hard-fit questions, worst-case logic is often safer than RSS unless assumptions are clearly supported.

Study Recommendations for Section 3

The best way to internalize this section is to practice with actual engineering and operations artifacts rather than only reading definitions.

1. Take a real VOC statement and rewrite it into one or more measurable CTQs.
2. Compare QFD, FMEA, DFX, and DFSS on the same example so the tool boundaries become clear.
3. Review a real drawing and force yourself to read the title block, notes, and tolerances before answering any question.
4. Write a short verification versus validation comparison using an actual product or service.
5. Calculate availability from MTBF and MTTR and explain why that is not the same as reliability.
6. Review a dFMEA or pFMEA and identify where prevention is weak or where severity is being understated.

This section rewards candidates who can move from philosophy to design decisions. That is the real CQE expectation: not just knowing the tool names, but knowing which one to use, why, and what poor reasoning looks like.