Quality Management Course Guide

What should a Quality Management course cover?

A Quality Management course should teach students how organisations define customer requirements, design and measure processes, distinguish routine variation from meaningful signals, evaluate process capability, diagnose root causes, improve flow and prevent recurrence. A coherent course moves from quality strategy and voice of the customer through process mapping, cost of quality, measurement systems, statistical process control and capability, then into root-cause analysis, Lean, Six Sigma, design quality, supplier quality and the management systems that sustain improvement.

The 12-session model in this guide fits final-year undergraduate, MSc, MBA and executive cohorts, typically within 24-36 contact hours and roughly 150-180 notional learning hours. The distinctions students must learn are central: control limits are not specification limits; inspection is not assurance; correlation is not root cause; certification is not proof of effective quality management; and a technically correct tool does not substitute for a defensible management decision.

Quality Management course overview

67%

teach Quality Management as a named or closely related course

72%

run across 10-12 sessions

56%

taught at undergraduate level

79%

taught at postgraduate level (levels overlap)

31%

offered as core; the rest elective

76%

include an applied or simulation-based component

Why this course matters

Quality Management connects operations, analytics, strategy, supply chain and customer experience. That mix makes it a useful integrative course for students who need to turn process evidence into improvement decisions.

Career path fit

How well this course prepares students for six role families, scored out of 10. Indicative, based on how directly the concepts map to each path - not a placement statistic.

Typical course structure

Foundations and strategy 15%
Customer and process design 15%
Measurement and variation 20%
SPC and capability 15%
Lean and Six Sigma improvement 20%
Systems, leadership and Quality 4.0 15%

Applied learning opportunities

These are secondary adjuncts rather than direct Quality Management simulations. Each is mapped only where students already hold the quality concepts needed to analyse the adjacent decision.

Who this guide is for

This guide is for professors, lecturers, module leaders, unit convenors, instructors of record, course coordinators and programme directors designing or refreshing Quality Management at university or business-school level. It is globally portable across course, module and unit terminology and can be used for final-year undergraduate, MSc, MBA and executive education teaching.

It is especially useful where a programme needs a coherent bridge between operations, business analytics, supply chain, process improvement and management systems. The design is written so a course owner can translate it into credit value, intended learning outcomes, constructive alignment, assessment briefs and assurance-of-learning evidence without turning the module into either a certification course or a statistics-only technical subject.

What does a Quality Management course cover?

A Quality Management course covers how organisations define quality, translate customer needs into measurable requirements, design and map processes, quantify the cost of poor quality, build credible measures, understand variation, use statistical process control, judge process capability and diagnose the causes of failure. It then moves into improvement through the seven basic quality tools, Lean, Kaizen and Six Sigma, before shifting upstream into design quality, FMEA and supplier management.

The applied distinction is that students should not leave merely knowing tool names. They should be able to judge whether the data are trustworthy, whether a process is stable and capable, whether a proposed root cause is actually supported, whether an intervention addresses the system rather than the symptom, and whether a quality management system, including ISO 9001-oriented controls and Quality 4.0 technology, creates real organisational learning. The course therefore rewards evidence, assumptions and defended action rather than mechanical calculation alone.

The course at a glance

A one-screen planning view for course approval, module refresh or syllabus design. The detailed teaching logic sits in the sections below.

Planning area	Suggested approach
Best fit	Final-year or senior undergraduates, specialist MSc students, MBA/EMBA cohorts and executive education. It also works as an elective within Operations Management, Supply Chain, Business Analytics or Operational Excellence.
Typical length	10, 12 or 14 teaching sessions, with 12 as the standard model. Roughly 24-36 contact hours plus independent study, data work and assessment - about 150-180 notional learning hours for a semester-format course.
Course role	A named Quality Management course or a specialist operations/continuous-improvement elective. It can generate strong assurance-of-learning evidence because students repeatedly select methods, analyse data and defend improvement decisions.
Useful prerequisites	Introductory operations, management or business analytics is useful. Basic numeracy and spreadsheet confidence are more important than advanced statistics; quantitative scaffolding can increase by level.
Main student output	A quality-improvement recommendation or DMAIC-style project supported by a process map, measurement plan, SPC/capability evidence, root-cause analysis, improvement design and control plan.
Best assessment fit	One group applied output carrying most of the summative weight plus an individual defence, assumptions note, reflection or viva that produces attributable evidence. Most courses use two assessment points rather than every option listed below.
Best simulation fit	No strong direct simulation fit. Startup Creation can support customer requirements, MVP and quality-planning discussion; Working Capital Management can support inventory, supplier continuity and operational trade-offs. Core TQM, SPC, Six Sigma and QMS teaching should use dedicated cases, data labs and workshops.

Learning outcomes

The outcomes are written as assessable intended learning outcomes and aligned to observable outputs. They use Bloom's taxonomy once as a design check, but the important point is constructive alignment: students should be assessed on the analytical and evaluative work the course says it develops, and lecturers should be able to point to evidence for course review.

Each outcome begins with an assessable verb. “Understand” and “be familiar with” are avoided because they are difficult to grade. Early outcomes establish language and planning; later outcomes carry more of the judgement, evidence and defence expected in summative work.

Explain competing definitions of quality and distinguish quality control, quality assurance, total quality management and performance excellence.
Translate voice-of-customer evidence into critical-to-quality requirements, operational definitions and a defensible quality plan.
Analyse an end-to-end process using SIPOC, process mapping and appropriate performance measures to locate failure points and improvement opportunities.
Evaluate the economics of quality using prevention, appraisal and failure costs alongside balanced leading and lagging indicators.
Assess whether a dataset and measurement system are fit for statistical quality analysis, including sampling, operational definitions and measurement error.
Apply statistical process control by selecting and interpreting appropriate control charts and distinguishing common-cause from special-cause variation.
Evaluate process capability against customer specifications while checking process stability, centring and the assumptions behind capability indices.
Diagnose quality problems using the seven basic quality tools, stratification and evidence-based root-cause analysis rather than unsupported causal claims.
Design and defend a Lean, Kaizen or DMAIC improvement intervention with a credible pilot, risk controls, success measures and sustainment plan.
Critically evaluate design quality, FMEA, supplier quality, ISO 9001, leadership and Quality 4.0 choices and defend a system-level quality recommendation.

Core concepts

The structure reflects course-design patterns commonly seen in Ivy League and leading global business-school teaching on Quality Management and related course families such as Operations Management, Operations Strategy, Supply Chain Management and Operational Excellence. This is a design pattern, not a claim that every leading school teaches the subject in the same way.

The sequence deliberately moves from foundations and customer requirements into process evidence, statistical control, diagnosis, improvement and finally management systems. That keeps the course academically coherent while giving lecturers enough flexibility to adjust technical depth by cohort.

There are twelve core concepts in this Quality Management course:

Quality as strategy, customer value and total quality management
Voice of the customer, critical-to-quality requirements and quality planning
Process thinking, SIPOC and process mapping
Cost of quality, KPIs and performance measurement
Variation, measurement systems and data quality
Statistical process control and control charts
Process capability, specification limits and acceptance decisions
Root-cause analysis and the seven basic quality tools
Lean quality, Kaizen and waste reduction
Six Sigma and DMAIC
Design for quality, FMEA, QFD and supplier quality
Quality management systems, ISO 9001, leadership and Quality 4.0

Concept Details

Each concept below is written as a lecturer-facing teaching note. The fictional cases contain enough data to run as short seminar exercises, and simulation notes appear only where one of the two approved secondary simulations genuinely adds value.

Central question: How should an organisation define quality when customers, operations and financial performance do not always point to the same answer?

Open the course by moving quality beyond inspection. Students need a strategic definition that connects fitness for use, conformance, customer value, prevention, systems thinking and organisational performance. Total quality management is most useful when taught as a management philosophy that integrates customer focus, process discipline, people involvement, evidence and continuous improvement rather than as a historical label.

What this concept covers

Competing definitions of quality: conformance, fitness for use, customer value and performance excellence.
Quality control, quality assurance, quality management and total quality management.
Customer focus, process orientation, leadership, employee involvement and continuous improvement.
Quality as a source of cost, risk, reputation and strategic differentiation.
Balancing short-term output targets with long-term process capability and learning.

Learning outcomes

By the end of this concept, students should be able to:

Distinguish quality control, assurance and management.
Explain how quality can support strategy and customer value.
Identify the organisational choices implied by a TQM philosophy.
Evaluate tensions between speed, cost, flexibility and quality.

How to teach it

Ask groups to define quality for the same product from customer, operations, finance and regulator viewpoints.
Contrast an inspection-led system with a prevention-led system.
Use a short service and manufacturing comparison to show that quality is not synonymous with physical defects.

Case-style example

Aster Home Appliances sells premium kettles for GBP45. Product returns are 1.8%, on-time delivery is 96%, customer ratings average 4.2/5 and complaint closure takes 4.5 days. A rival has 0.9% returns but only 3.7/5 ratings. Management has GBP300,000 to spend on reliability engineering or service recovery. Students define quality, choose the priority and defend the trade-off. They discover that the answer changes with the stakeholder and the evidence selected.

Where students struggle

Students often reduce quality to defect counts or assume that the most expensive product must be the highest quality. Keep returning to requirements, customer value, process performance and the cost of failing to meet needs.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Ask students to write one sentence each for quality control, quality assurance and quality management, then identify which statement in a short scenario belongs to which category.

Where it leads

This strategic frame makes the next question unavoidable: whose needs should be translated into measurable requirements, and how should those requirements guide the process?

Central question: How do broad customer needs become measurable quality requirements that designers and operations teams can act on?

Quality planning starts before production or service delivery. Lecturers should teach students to gather and prioritise the voice of the customer, distinguish stated wants from underlying needs, translate those needs into critical-to-quality requirements and define measures with tolerances or service standards. This is where market insight becomes an operational specification.

What this concept covers

Voice-of-customer sources, segmentation and evidence quality.
Critical-to-quality characteristics and operational definitions.
Kano-style thinking, prioritisation and trade-offs.
Service quality requirements, response standards and failure points.
Quality plans that link need, measure, target, owner and evidence.

Learning outcomes

By the end of this concept, students should be able to:

Translate ambiguous customer statements into measurable CTQs.
Prioritise quality requirements using evidence rather than anecdote.
Construct a basic quality plan with owners and measures.
Explain where customer expectations should and should not become specifications.

How to teach it

Give students raw interview comments and ask them to code needs before creating CTQs.
Require operational definitions so two teams would measure the same thing the same way.
Use a service example to avoid the idea that specifications only apply to factories.

Case-style example

LoopCare, a digital GP service, has median booking time of 8 minutes but a 90th-percentile wait of 22 minutes. No-shows are 11%, and 17% of complaints mention uncertainty about appointment status. With GBP120,000 available, leaders can upgrade scheduling capacity or automate status notifications. Students convert the evidence into CTQs, set targets and write a quality plan. They discover that average speed alone misses a major source of perceived quality.

Where students struggle

Students jump too quickly from a customer quote to a solution. Force a separation between need, CTQ, measure, target and intervention.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Provide five customer statements and ask students to turn two into measurable CTQs with an operational definition and data source.

Where a simulation fits

The Startup Creation Simulation can be used as a secondary application after customer requirements and quality planning. Startup teams define a customer problem, value proposition, market and business model before pitching, which gives lecturers a context for asking whether the proposed MVP has clear CTQs and what quality evidence would be required before scale. Keep the quality analysis professor-defined because the simulation is not a TQM or SPC simulation.

Where it leads

Once requirements are clear, students need to see the process that creates them. That leads into SIPOC, process mapping and the identification of handoffs, queues and failure points.

Central question: Where in an end-to-end process is quality created, delayed or lost?

Quality problems rarely belong to a single task. Process thinking helps students move from departmental explanations to end-to-end flow. SIPOC gives a high-level boundary; detailed maps reveal decisions, queues, handoffs, rework and information gaps. The teaching goal is not drawing symbols neatly but choosing the right boundary and locating leverage points for measurement and improvement.

What this concept covers

Process boundaries, customers, suppliers, inputs and outputs.
SIPOC as a scoping tool.
Current-state process maps, decision points, handoffs, queues and rework loops.
Value-added and non-value-added activity.
Process ownership and measurement points.

Learning outcomes

By the end of this concept, students should be able to:

Construct a SIPOC for a defined process.
Map an end-to-end process at an appropriate level of detail.
Identify failure points, delays and rework loops.
Recommend measurement points that would distinguish causes from symptoms.

How to teach it

Map a familiar process such as student registration or online returns live in class.
Ask different teams to choose process boundaries and compare what each boundary hides.
Require a problem statement before any redesign suggestions are allowed.

Case-style example

HarborLab processes 480 diagnostic samples per day. Average turnaround is 9.2 hours against an 8-hour promise; 7% of samples need relabelling and 3% require a rerun. Samples pass through reception, accessioning, testing, clinical review and release. Students build a SIPOC and current-state map, then nominate three measurement points. They discover that the visible delay at clinical review may originate in information defects created much earlier.

Where students struggle

Maps become either too high level to diagnose anything or so detailed that no one can see the flow. Use the decision at hand to determine the level of detail.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Give a process map with one deliberately missing supplier, one ambiguous output and one hidden rework loop. Ask students to identify the three defects.

Where it leads

A mapped process creates a place to attach economics and performance measures. The next concept asks what poor quality costs and which indicators should be managed.

Central question: How should managers quantify the economics of quality without rewarding the wrong behaviour?

The cost of quality helps students see that prevention and appraisal are investments while internal and external failures consume resources and trust. The framework is most valuable when tied to performance measurement: a dashboard must balance outcome, process and leading indicators and avoid gaming. Students should learn to ask whether a KPI changes behaviour in the intended direction.

What this concept covers

Prevention, appraisal, internal failure and external failure costs.
Cost of poor quality and hidden failure costs.
Leading versus lagging indicators.
Customer, process, financial and risk measures.
Metric definitions, ownership, cadence and unintended consequences.

Learning outcomes

By the end of this concept, students should be able to:

Classify quality-related costs consistently.
Estimate visible and hidden failure costs.
Design a balanced quality dashboard.
Critique KPIs for gaming risk and weak causal logic.

How to teach it

Give a mixed cost ledger and require students to classify every line before debating budget shifts.
Show how a target such as calls-per-hour can damage first-contact resolution.
Ask teams to propose one leading and one lagging measure for the same CTQ.

Case-style example

Crestline Furniture records GBP420,000 of scrap and rework, GBP160,000 of final inspection, GBP85,000 of supplier audits, GBP55,000 of quality training and GBP310,000 of warranty and complaint costs. Finance proposes cutting audits and training by 40%. Students classify the costs, estimate the direct saving and write a recommendation. They discover why cutting visible prevention and appraisal can increase less visible failure cost.

Where students struggle

Students treat all quality spending as waste or assume more inspection always means better quality. Keep prevention, detection and failure separate, and ask what each pound is intended to prevent.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Give six cost items and ask students to classify them, then choose one metric that could reveal whether prevention spending is working.

Where it leads

Metrics are only as good as the data that feed them. Before students interpret control charts, they need to understand variation, operational definitions and the quality of the measurement system.

Central question: Can managers trust the data enough to decide whether the process changed?

Quality management becomes statistical at this point, but the first lesson is conceptual: every process varies and every measurement process can add variation of its own. Students should distinguish common from special sources later, but first they need stable definitions, sampling logic, repeatability and reproducibility thinking, and a healthy suspicion of false precision.

What this concept covers

Natural process variation and observed variation.
Operational definitions and sampling plans.
Repeatability, reproducibility and measurement-system error.
Attribute versus variable data.
Data completeness, timestamp integrity, subgrouping and bias.

Learning outcomes

By the end of this concept, students should be able to:

Explain why observed variation may include measurement error.
Select an appropriate data type and sampling approach.
Diagnose weak operational definitions.
Judge whether data are fit for SPC or capability analysis.

How to teach it

Have two groups measure the same object using different instructions, then compare spread.
Use a simple gauge repeatability demonstration rather than a full industrial study if the cohort is non-technical.
Ask students to identify where a dataset was created, transformed and potentially biased.

Case-style example

PineTech machines a shaft with target diameter 20.00 mm and specification limits of 19.90 to 20.10 mm. Inspector A repeats measurements within 0.02 mm, while Inspector B varies by as much as 0.07 mm on the same parts. The process mean is 20.01 mm with sample standard deviation 0.025 mm. Students decide whether to adjust the process or investigate measurement first. They discover that action on noisy measurement can create a real process problem.

Where students struggle

Students often treat a spreadsheet column as truth. Require them to explain who measured what, when, with which instrument and definition before calculation.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Ask students to list three questions they would ask before accepting a quality dataset for control-chart analysis.

Where it leads

Once the measurement system is credible, students can use statistical process control to distinguish routine variation from signals that merit investigation.

Central question: How can a team distinguish a process signal from routine variation without tampering with the system?

SPC is the analytical centre of many Quality Management courses. Teach control charts as decision tools, not decorative graphs. Students should select charts based on the data and subgroup structure, calculate or interpret centre lines and control limits, detect signals, and connect a signal to investigation rather than automatic adjustment. Specification limits answer a different question and should be kept visually and conceptually separate.

What this concept covers

Common-cause and special-cause variation.
Rational subgrouping and sampling cadence.
Variable and attribute control charts at an appropriate introductory depth.
Control limits versus specification limits.
Signal rules, investigation and the risk of tampering.

Learning outcomes

By the end of this concept, students should be able to:

Select an appropriate chart for common data types.
Interpret control limits and process signals.
Distinguish control limits from customer specifications.
Recommend an evidence-based response to a signal.

How to teach it

Build one chart by hand or spreadsheet before using automated software.
Give two charts with the same average but different stability and ask which process is predictable.
Make students state the action they would take and the evidence they need next.

Case-style example

Northstar Bottling samples five bottles each hour for 20 hours. The fill target is 500 ml and customer specifications are 492 to 508 ml. Early subgroup means vary from 498 to 502 ml, but four consecutive means rise from 502.5 to 505.2 ml while within-subgroup spread remains stable. Students construct or interpret the chart, identify the signal and recommend action. They discover that a process can be within specification yet no longer statistically stable.

Where students struggle

The two recurring errors are using specifications as control limits and reacting to every point. Insist that students answer two separate questions: is the process stable, and is it capable?

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Show a control chart and ask for a three-sentence response: signal or no signal, likely type of variation, next management action.

Where it leads

A stable process can still fail customer requirements. Process capability takes the next step by comparing predictable process spread and centring with specifications.

Central question: If a process is stable, is it capable of meeting customer specifications consistently?

Capability analysis links the voice of the customer to process performance. Students should calculate and interpret Cp and Cpk at a level suitable for the course, but lecturers should keep assumptions visible: a capability index is meaningful only if the process is stable and the distributional assumptions are reasonable. The management question is usually whether to centre, reduce variation, change the design or negotiate the specification.

What this concept covers

Specification limits and tolerance.
Cp, Cpk and the difference between potential and realised capability.
Centring versus variation reduction.
Stability as a prerequisite for meaningful capability analysis.
Capability targets, risk and managerial action.

Learning outcomes

By the end of this concept, students should be able to:

Calculate and interpret basic capability indices.
Explain why Cp and Cpk can differ.
Check whether capability analysis is appropriate.
Compare centring and variation-reduction interventions.

How to teach it

Use one stable process with deliberately off-centre data so Cp and Cpk tell different stories.
Ask students to link the choice of improvement to cost and customer risk.
Discuss why an arbitrary benchmark should not replace context and consequence.

Case-style example

Arcadia Plastics produces a seal specified at 9.80 to 10.20 mm. A stable process has mean 10.08 mm and standard deviation 0.045 mm. Recentring costs GBP8,000; a tooling upgrade costing GBP60,000 is expected to reduce standard deviation to 0.030 mm. Students compute Cp and Cpk for the current process and compare the two interventions. They discover that variation reduction is not always the first or cheapest capability improvement.

Where students struggle

Students calculate an index before checking stability, or treat the index as a grade rather than a model with assumptions. Require a one-line appropriateness check before every capability result.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Give a Cp/Cpk pair and ask students to infer whether the main problem is spread, centring or both.

Where it leads

When performance is poor or a signal appears, the next task is diagnosis. The basic quality tools help students move from symptom lists to structured root-cause evidence.

Central question: How can a team move from a visible defect to a cause it has enough evidence to act on?

Root-cause analysis is often taught too casually. Brainstorming a fishbone is not the same as establishing causality. Use the seven basic tools as complementary ways to stratify, visualise and test patterns, then teach students to separate hypotheses from verified causes. Five Whys is useful only when evidence checks each link rather than when a group writes a plausible story.

What this concept covers

Check sheets, Pareto charts, histograms, scatter plots, cause-and-effect diagrams, control charts and process maps.
Stratification by shift, supplier, machine, product, channel or customer.
Five Whys and causal-chain discipline.
Hypothesis generation versus cause verification.
Corrective action and confirmation of effect.

Learning outcomes

By the end of this concept, students should be able to:

Choose a basic quality tool for a specific diagnostic question.
Build a Pareto view and identify high-leverage categories.
Construct a cause hypothesis and an evidence plan.
Distinguish correlation, sequence and causal evidence.

How to teach it

Give an intentionally mixed defect dataset and ask students to stratify before brainstorming causes.
Require each fishbone branch to end with an observable test.
Award marks for disproving a favourite hypothesis when evidence supports a different one.

Case-style example

MetroPrint records 240 defects: 92 colour mismatch, 61 registration errors, 38 scratches, 29 missing pages and 20 other. Most colour mismatches occur on evening shift, but that shift also handles the oldest printer and a different ink batch. Students build a Pareto chart, stratify the data and write a root-cause test plan. They discover that the largest category identifies where to investigate, not which factor caused it.

Where students struggle

Students fall in love with the first plausible cause. Ask, “What observation would prove this explanation wrong?” before accepting corrective action.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Give a defect category and three possible causes. Students must choose the next data to collect rather than choose the cause.

Where it leads

Diagnosis identifies waste and instability. Lean quality and Kaizen then give students a structured way to improve flow, reduce non-value-added work and embed daily problem solving.

Central question: How can an organisation improve flow and quality together rather than trading one for the other?

Lean is sometimes taught as speed or cost cutting. In a Quality Management course it should be framed as a system for exposing problems, reducing waste, improving flow and building quality at the source. Students can use value-stream thinking, standard work, visual management, mistake-proofing and Kaizen while keeping customer value and process stability at the centre.

What this concept covers

Value, flow, pull and the visibility of problems.
Waste, rework, queues, overprocessing and handoff loss.
Standard work, visual management and mistake-proofing.
Kaizen and small-cycle experimentation.
Why removing buffers can expose rather than create underlying quality problems.

Learning outcomes

By the end of this concept, students should be able to:

Identify waste without confusing all non-value-added activity with immediately removable work.
Design a practical Kaizen intervention.
Explain how standard work supports learning rather than rigidity.
Evaluate trade-offs between flow, resilience and control.

How to teach it

Use a process map with touch time and elapsed time so the waiting problem is visible.
Ask groups to redesign the process without adding headcount first.
Require a pilot measure and a rollback criterion for every change.

Case-style example

Beacon Claims processes 1,000 insurance claims each week. Average lead time is 12 days but active handling time is only 95 minutes. Forty percent of delay is waiting for missing information and 18% of claims are reworked after batch approval. Leaders can add two adjusters for GBP90,000 a year or redesign intake for GBP35,000. Students map waste, propose a Kaizen pilot and define measures. They discover that capacity is not the only route to faster service.

Where students struggle

Students equate Lean with headcount reduction or try to remove every buffer. Emphasise customer value, stability, safe experimentation and system effects.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Ask students to identify one waste, one root cause, one countermeasure and one measure from a short process scenario.

Where a simulation fits

The Working Capital Management Simulation can be used as a secondary application where inventory reliability, supplier continuity or customer-service choices intersect with operating performance. Students manage receivables, inventory and payables across a 12-month scenario. The Quality Management debrief should ask which service, defect, supplier or availability measures would be needed alongside the financial metrics.

Where it leads

Lean provides a strong improvement philosophy. Six Sigma and DMAIC add a more formal problem-solving and project-governance structure for material, data-rich problems.

Central question: When does a quality problem merit a structured DMAIC project, and what evidence is needed at each gate?

Six Sigma should not become a vocabulary quiz. Teach DMAIC as a disciplined project logic: define a problem that matters, measure the current state credibly, analyse causes, improve using tested interventions and control the gains. Statistical sophistication can scale by cohort, but the quality of the problem statement, evidence and control plan should remain assessable at every level.

What this concept covers

DMAIC phases and project selection.
Problem statements, charters, CTQs and baseline measures.
Measurement planning and cause analysis.
Pilot design, risk management and improvement selection.
Control plans, ownership and sustainment.

Learning outcomes

By the end of this concept, students should be able to:

Frame a quality problem suitable for DMAIC.
Select evidence appropriate to each DMAIC phase.
Design an improvement pilot with success and risk criteria.
Create a control plan that can sustain the change.

How to teach it

Give a poor project charter and ask teams to repair it before analysis.
Use a gate review format: each team has to earn permission to move to the next phase.
Keep statistical tools subordinate to the decision they support.

Case-style example

SilverLine Support handles 18,000 tickets a month. First-contact resolution is 68%, repeat contacts average 1.6 per case and complaints from premium customers are up 24%. Management wants to deploy a chatbot immediately. Students write a DMAIC charter, define measures, identify evidence needed before selecting a solution and propose a pilot. They discover that naming a technology before validating the problem can lock the project onto the wrong cause.

Where students struggle

Students often make DMAIC a five-heading report written after the solution is already chosen. Use gate reviews and require evidence that justifies movement from one phase to the next.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Present five project activities and ask students to place each in the correct DMAIC phase and explain one dependency.

Where it leads

Improvement is only one side of quality. The next concept shifts upstream to designing quality into products, services and supply relationships before failures emerge.

Central question: How can managers prevent failure by designing requirements, risk controls and supplier relationships into the system?

Prevention becomes concrete when students connect customer needs to design characteristics, anticipate failure modes and manage supplier quality. Quality function deployment can be used selectively to show requirement translation, while FMEA teaches prioritised prevention. Supplier quality should be framed as a relationship and system design problem, not only incoming inspection.

What this concept covers

Design quality and prevention before launch.
QFD logic from customer need to technical or service characteristic.
FMEA severity, occurrence, detection and action prioritisation.
Supplier selection, incoming quality, development and continuity.
Trade-offs among unit price, defect risk, delivery reliability and resilience.

Learning outcomes

By the end of this concept, students should be able to:

Translate requirements into design characteristics.
Construct a basic FMEA and recommend risk-reduction actions.
Evaluate supplier quality beyond price.
Design a supplier scorecard with quality and continuity indicators.

How to teach it

Use a simple product or service feature to illustrate QFD without turning the session into matrix mechanics.
Give teams the same FMEA and ask them to prioritise different actions under a fixed budget.
Link supplier quality to total cost and operational continuity.

Case-style example

NexaMed buys a critical component from Supplier A at GBP4.20 with 0.4% defects and 98.5% on-time delivery, or Supplier B at GBP3.75 with 1.6% defects and 94% on-time delivery. A production stoppage costs GBP7,500 per hour. Students build a supplier scorecard and FMEA for supply failure, then recommend allocation. They discover why lowest unit price can be the highest-risk quality decision.

Where students struggle

Students treat FMEA scores as mathematically objective rankings. Make them defend severity and action priority in context, especially when a low-frequency failure has major consequence.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Give one failure mode and ask for cause, effect, current control, recommended action and evidence that the action worked.

Where a simulation fits

The Working Capital Management Simulation can be used as a secondary application where inventory reliability, supplier continuity or customer-service choices intersect with operating performance. Students manage receivables, inventory and payables across a 12-month scenario. The Quality Management debrief should ask which service, defect, supplier or availability measures would be needed alongside the financial metrics.

Where it leads

The course now closes by moving from individual projects to the organisation-wide management system that sustains quality, including ISO 9001, leadership, audit, learning and digital Quality 4.0.

Central question: How does an organisation make quality a repeatable management system while adapting to new technology and changing risk?

The final concept integrates the course. Students should see a quality management system as the operating architecture that connects context, leadership, planning, support, operations, performance evaluation and improvement. ISO 9001 provides an internationally recognised structure, but certification is not the learning objective. Close with Quality 4.0: digital traceability, AI, connected measurement and the governance risks that come with faster automated decisions.

What this concept covers

Process-based quality management systems and risk-based thinking.
ISO 9001 requirements as a management-system architecture.
Internal audit, corrective action, management review and continual improvement.
Leadership, culture, psychological safety and escalation.
Quality 4.0, digital traceability, AI-enabled inspection and data governance.

Learning outcomes

By the end of this concept, students should be able to:

Evaluate whether a QMS creates learning or merely documentation.
Explain the purpose of major ISO 9001 management-system elements without memorising clauses.
Design evidence for audit, review and corrective action.
Critically assess digital quality tools for data, bias, governance and human-oversight risk.

How to teach it

Use a mock audit finding and ask whether the problem is local nonconformance or system weakness.
Compare an organisation that passes audits but repeats failures with one that uses audit evidence to redesign processes.
Ask students to write a governance rule for an AI-enabled quality decision.

Case-style example

Orion Devices is ISO 9001 certified, yet repeated audit actions remain open and field returns have risen from 1.1% to 1.9%. A new AI vision system flags 6% of units while human inspectors flag 2.5%, but the false-positive rate is unknown. Students prepare a board recommendation covering corrective action, management review and AI validation. They discover that certification and automation do not substitute for a functioning learning system.

Where students struggle

Students may treat ISO as a checklist or assume digital inspection is inherently more objective. Keep asking how the system learns, how evidence is validated and who remains accountable for decisions.

Reading and a quick check

Use the core textbook or a current reading from the Recommended Readings section. Ask students to name three pieces of evidence a management review should use to decide whether the QMS is effective.

Where it leads

This concept completes the lifecycle. Students can now move from customer requirements and process evidence through control and improvement to governance, assurance and continuous organisational learning.

Connecting the concepts

This alignment map shows the progression from foundations to applied decisions. The useful design principle is that every stage leaves behind evidence: a map, calculation, diagnostic plan, recommendation or defence. That gives lecturers formative evidence throughout the course and makes the summative task an assembly of prior reasoning rather than an end-of-term cliff.

Stage of quality work	Principal concepts	Expected student output	Assessment evidence
Define value and requirements	Concepts 1-2	Quality strategy map, customer evidence, CTQ definitions and quality plan.	Formative: requirement translation and short recommendation.
See the process	Concept 3	SIPOC, current-state map, process boundary and measurement points.	Formative: process diagnosis workshop.
Build credible measures	Concepts 4-5	Cost-of-quality analysis, balanced KPIs, sampling and measurement-system plan.	Formative: data credibility note.
Control and judge capability	Concepts 6-7	SPC chart interpretation, signal response, capability analysis and assumption check.	Individual or group technical memo.
Diagnose causes	Concept 8	Pareto/stratification view, cause hypotheses and evidence plan.	Formative investigation plan.
Improve the system	Concepts 9-10	Lean/Kaizen pilot, DMAIC charter, selected intervention and control plan.	Main group applied output.
Design prevention and governance	Concepts 11-12	FMEA, supplier-quality decision, QMS/ISO critique and Quality 4.0 governance recommendation.	Individual defence, viva or capstone board memo.

Tools support quality judgement. They do not make the management decision.

Credit method selection, data credibility, interpretation, assumptions, recognition of missing information and the link between technical evidence and operational consequence. A polished control chart with the wrong subgroup logic should not outscore a simpler analysis that is methodologically defensible and transparent about limitations.

Adapting for undergraduate and postgraduate students

The architecture can stay constant across final-year undergraduate, MSc, MBA and executive cohorts. What changes is the scaffolding, statistical depth and tolerance for ambiguity. A common design error is to remove SPC or capability from the undergraduate version because it appears technical. A better approach is to keep the concepts but provide cleaner datasets, more explicit chart-selection cues and structured interpretation prompts.

At postgraduate and MBA level, give students more incomplete information and make method selection part of the problem. Executive education can compress calculations while increasing the use of participants' own processes, leadership questions and implementation barriers. The table below gives a portable course/module/unit comparison.

Course design area	Undergraduate version	Postgraduate / MBA / executive version
Course emphasis	Build a clear quality lifecycle from customer requirements through measurement, control, diagnosis, improvement and management systems.	Move faster into ambiguous cases, competing metrics, incomplete datasets, change politics and system-level recommendations.
Statistical depth	Use carefully scaffolded control charts, basic capability analysis and spreadsheet-supported interpretation.	Expect stronger statistical justification, sampling critique, assumption testing and more independent analysis.
Process improvement	Use structured maps, Pareto analysis, Kaizen and guided DMAIC projects with defined data.	Use open-ended improvement briefs where students must decide which method, data and intervention are defensible.
ISO and systems	Teach the purpose of QMS elements and evidence without clause memorisation.	Add audit interpretation, governance, management review, organisational learning and system-design critique.
Reading load	Textbook chapters, accessible articles, short technical notes and instructor-curated datasets.	Academic papers, standards commentary, complex cases, practitioner evidence and competing interpretations.
Student activity	Guided calculations, structured process maps, team workshops and short recommendations.	Consulting-style projects, live challenge, policy critique, simulation debriefs and oral defence.
Assessment style	Credit correct method selection, accurate calculation, clear causal reasoning and a justified recommendation.	Credit judgement under uncertainty, evidence quality, methodological limits, implementation risk and response to challenge.
Simulation use	Use secondary simulations selectively as adjacent decision contexts, not as substitutes for SPC, Six Sigma or TQM teaching.	Use the same adjacent simulations for richer discussion of scaling, supplier continuity and cross-functional trade-offs where relevant.

The 12-session syllabus

The syllabus follows the full quality-management lifecycle: define value and requirements, see the process, build trustworthy measures, control variation, judge capability, diagnose causes, improve flow and variation, design prevention, and sustain the system through leadership and quality management systems. It can be taught weekly, in intensive blocks or as a blended module.

The design principle worth keeping if you change nothing else: application should begin before the final assessment. Each session should produce something that can be discussed, marked or reused later - a CTQ, map, measure, chart, capability judgement, root-cause test, pilot, FMEA or system recommendation.

THE QUALITY MANAGEMENT COURSE GUIDE

A 12-session arc from customer requirements to sustained improvement

A 12-SESSION ARC · DEFINE - MEASURE - CONTROL - IMPROVE - SUSTAIN

Students move from defining quality to diagnosing and improving real processes, with evidence produced at every stage.

Define qualityHear the customerMap the processMeasure variationControl the processDiagnose causesImprove flowSustain the system

Sessions 1-2

Define quality and requirements

Strategic quality, customer value, VOC, CTQs and quality planning.

STUDENTS PRODUCE

Quality strategy map and CTQ plan

Session 3

See the process

SIPOC, process boundaries, flow, handoffs and failure points.

STUDENTS PRODUCE

Current-state process map

Sessions 4-5

Measure what matters

Cost of quality, KPIs, variation, sampling and measurement-system credibility.

STUDENTS PRODUCE

Quality dashboard and data plan

Sessions 6-7

Control and capability

SPC, control charts, specification limits and capability decisions.

STUDENTS PRODUCE

SPC and capability memo

Session 8

Diagnose causes

Pareto, stratification, root-cause hypotheses and evidence testing.

STUDENTS PRODUCE

Root-cause evidence plan

Sessions 9-10

Improve the system

Lean, Kaizen, waste reduction, Six Sigma and DMAIC project governance.

STUDENTS PRODUCE

Improvement pilot and DMAIC control plan

Session 11

Design prevention

QFD logic, FMEA, supplier quality, resilience and total-cost trade-offs.

STUDENTS PRODUCE

Supplier-quality and FMEA recommendation

Session 12

Govern and sustain

QMS, ISO 9001, audit, leadership, Quality 4.0 and AI governance.

STUDENTS PRODUCE

Board recommendation and individual defence

Use this visual above the detailed syllabus. The two Finsimco simulations are optional secondary applications and are not shown as replacements for the core Quality Management methods.

Session	Topic	Teaching focus	Student activity	Best-fitting simulation, where relevant	Assessment or output
1	Quality foundations and strategic quality	Define quality, quality control, assurance, TQM and performance excellence. Connect customer value, process performance, risk and strategy.	Groups compare quality definitions for a product and service and build a one-page quality strategy map.		Quality strategy note with definitions, stakeholder tensions and three course-level measures.
2	Voice of the customer and quality planning	Gather customer evidence, translate needs into CTQs, write operational definitions and build a quality plan.	Students code customer comments, prioritise CTQs and specify measures, targets and owners.	Optional: Startup Creation	VOC-to-CTQ matrix and quality plan.
3	Process thinking, SIPOC and process mapping	Scope processes, identify suppliers, inputs, customers and outputs, then map handoffs, queues, decisions and rework.	Teams map a service or operating process and nominate measurement points before proposing solutions.		SIPOC plus current-state process map and problem statement.
4	Cost of quality and performance measurement	Classify prevention, appraisal and failure costs; design balanced leading and lagging quality indicators.	Students classify a quality-cost ledger and redesign a dashboard that currently rewards the wrong behaviour.		Cost-of-quality analysis and KPI rationale.
5	Variation, measurement systems and data quality	Introduce variation, sampling, operational definitions, repeatability and reproducibility, attribute/variable data and data fitness.	Students audit a measurement process and decide whether the data are credible enough for control analysis.		Measurement-system risk note and sampling plan.
6	Statistical process control	Teach rational subgrouping, control limits, common/special causes, chart selection and management response to signals.	Students build or interpret a control chart and recommend the next investigation without tampering.		SPC memo: chart, signal interpretation and next action.
7	Process capability and specification limits	Compare process spread and centring with customer specifications using capability logic and Cp/Cpk where appropriate.	Students calculate capability, test assumptions and compare recentering with variation-reduction options.		Capability recommendation with assumptions and economics.
8	Root-cause analysis and the seven basic quality tools	Use Pareto, stratification, check sheets, histograms, scatter plots, fishbones, Five Whys and evidence plans.	Teams turn a defect dataset into a ranked investigation plan and distinguish hypothesis from verified cause.		Root-cause evidence plan and corrective-action proposal.
9	Lean quality, Kaizen and waste reduction	Connect customer value, flow, waste, standard work, visual management, mistake-proofing and iterative improvement.	Students analyse touch time versus elapsed time and design a low-risk Kaizen pilot.	Optional: Working Capital Management	Lean redesign with pilot measures, owner and rollback criteria.
10	Six Sigma and DMAIC	Use DMAIC as a project-governance structure from problem framing and measurement through analysis, improvement and control.	Teams repair a weak charter, pass gate reviews and defend why their intervention follows from the evidence.		DMAIC charter, analysis summary and control plan.
11	Design for quality, FMEA and supplier quality	Move prevention upstream through QFD logic, FMEA, supplier scorecards and supply-continuity decisions.	Students compare suppliers using quality, delivery, cost and risk data, then prioritise FMEA actions.	Optional: Working Capital Management	Supplier-quality recommendation and FMEA action register.
12	Quality management systems, ISO 9001 and Quality 4.0	Integrate QMS architecture, audit, corrective action, management review, leadership, culture, digital traceability and AI governance.	Students respond to repeated audit failures and evaluate an AI-enabled inspection proposal.		Board-level quality-system recommendation and individual defence.

10-week course structure

A 10-week version should compress adjacent concepts rather than delete the statistical and system elements that make the subject Quality Management. Combine strategy with customer requirements, combine process planning with quality economics, and integrate Lean with Six Sigma while preserving separate time for SPC, capability and QMS governance.

Week	Compressed topic
1	Quality strategy, customer value, VOC and CTQs
2	Process mapping, quality planning and cost of quality
3	Variation, measurement systems and data quality
4	SPC and control-chart interpretation
5	Process capability and specification decisions
6	Root-cause analysis and the seven basic quality tools
7	Lean quality, Kaizen and optional Working Capital Management application
8	Six Sigma and DMAIC project workshop
9	Design quality, FMEA and supplier quality
10	QMS, ISO 9001, Quality 4.0 and final integrated defence

14-week course structure

A 14-week version creates space for measurement-system work, separate SPC practice, a fuller improvement-project gate review and a capstone case. Use the extra time for deeper application and defence rather than simply adding more tool names.

Week	Expanded topic
1	Quality definitions, strategy and customer value
2	Voice of the customer, CTQs and quality planning
3	SIPOC, process mapping and process ownership
4	Cost of quality and performance measurement
5	Variation, sampling and operational definitions
6	Measurement systems and data-quality workshop
7	Statistical process control: variable data
8	SPC extensions, attribute data and management response
9	Process capability and specification decisions
10	Root-cause analysis and corrective-action evidence
11	Lean, Kaizen and process redesign
12	Six Sigma, DMAIC and improvement-project gate review
13	Design quality, FMEA, supplier quality and optional Working Capital Management application
14	QMS, ISO 9001, Quality 4.0, case integration and individual defence

Simulations: What they are and why they belong in this course

Quality Management is a decision-led subject, even when the tools are statistical. Students can learn control-chart rules, capability indices, FMEA or DMAIC from lectures and datasets, but they also need to experience the cross-functional consequences of decisions. In this course, simulations are therefore optional adjacent contexts rather than the centre of the pedagogy. The current Finsimco portfolio has no dedicated TQM, SPC, Six Sigma or quality-system simulation.

The two selected simulations earn their place only where they create a useful quality-management conversation. Startup Creation provides an opportunity to discuss customer requirements, MVP assumptions and evidence before scale. Working Capital Management makes inventory, supplier continuity and customer-credit trade-offs concrete. Neither should be described as a direct Quality Management simulation.

There is also a defensible accreditation rationale for structured experiential work. Applied decision tasks can generate evidence that students can analyse and evaluate rather than recall, provided the lecturer connects the activity to intended learning outcomes and conducts a disciplined debrief. If you need the accreditation language itself, what and say about simulations sets it out.

Traditional case study vs simulation

Teaching format	What it does well	Limitation	Best use in this course
Traditional case study	Provides a rich situation, evidence and a defined management decision.	Students may discuss the decision without experiencing changing constraints or counterparty behaviour.	Core method teaching: TQM, SPC, capability, root cause, Lean, QMS and leadership.
Simulation	Places students into a live or sequential decision context with consequences, trade-offs and comparative outcomes.	Can create false alignment if the activity is only adjacent to Quality Management or if the debrief is weak.	Selective application after the quality concepts are already taught, especially customer/MVP and supplier/inventory trade-offs.

A simulation is not a substitute for teaching the quality method. Use one only when the debrief can make the quality question more visible than a conventional case or dataset would.

Where simulations fit

The two approved simulations are both secondary fits. Startup Creation is strongest after voice-of-customer and quality-planning teaching because students can critique customer evidence, MVP assumptions and scaling readiness. Working Capital Management is strongest after Lean and supplier-quality teaching because students can examine inventory reliability, supplier continuity and service trade-offs alongside financial metrics.

Course point	Simulation	How to use it	Why it fits
Session 2: VOC and quality planning	Startup Creation	Use selected stages or the full activity, then add a professor-defined CTQ and quality-evidence debrief.	Students must define customer problems, value propositions, market assumptions and an MVP context before pitching.
Sessions 9 and 11: Lean / supplier quality	Working Capital Management	Use as an adjacent operating-decision case and require a quality-risk addendum to the CFO recommendation.	The scenario includes inventory, supplier continuity, customer credit and operating-risk choices that can be analysed through a quality lens.

The Startup Creation Simulation is a 6-10 hour team-based entrepreneurship simulation. Startup teams identify a customer problem, define a value proposition, size the market, build a Business Model Canvas and prepare a live pitch. Venture-capital teams establish investment criteria, review competing ventures and negotiate investment amount and equity ownership. For Quality Management, its value is not in teaching quality tools directly, but in giving students a realistic context for asking what customer evidence, CTQs, MVP quality assumptions and validation evidence should exist before a venture scales.

Why it fits here

After Session 2, students already know how to translate customer evidence into measurable quality requirements. They can therefore interrogate a startup proposition rather than simply admire the pitch: which customer need is critical, how would it be measured, what failure would be unacceptable, and what evidence should be collected during MVP testing?

What students do

Startup teams identify the opportunity, customer problem, solution and value proposition, then size TAM, SAM and SOM.
Startup teams develop the Business Model Canvas, including customer segments, channels, resources, partners, cost structure, revenue streams, unit economics and use of funds.
Venture-capital teams write an investment thesis, establish screening criteria and prepare an Investment Process Document.
Startup teams create and submit a pitch; investor teams review ventures and prepare questions.
Teams enter a live pitch and negotiation stage, where founders defend market sizing and unit economics and both sides negotiate investment amount and ownership.
The final market view lets the cohort compare funding, ownership and implied post-money valuations. The lecturer then adds the Quality Management layer: CTQs, MVP evidence, reliability/service standards and the quality risks hidden by a persuasive pitch.

Recommended course placement

After Session 2 as an extended application of voice-of-customer and quality planning.
Across several teaching blocks if the full entrepreneurship experience is useful elsewhere in the programme.
As an optional cross-course activity where Entrepreneurship and Quality Management modules share a cohort.

Knowledge students should have before the simulation

Customer needs and critical-to-quality requirements.
Operational definitions and basic quality planning.
A clear distinction between an attractive proposition and evidence that the delivery process can meet requirements consistently.

Delivery format

Area	Recommended Format
Duration	6-10 hours across five stages; the live page supports one extended session or division across shorter teaching periods.
Format	Team simulation. Around 70% of teams are startups and 30% are investor teams.
Level	Undergraduate, postgraduate and MBA.
Prior knowledge	Beginner accessible; no prior startup or venture-capital experience is required by the simulation.
Delivery	Classroom, online or hybrid. The web-based simulation can also be used as homework within a professor-set timeframe.
Evidence	Team submissions, negotiated terms and comparative results can support professor-defined assessment. They do not establish individual contribution automatically.

Why it fits here

After Lean and supplier-quality teaching, students can challenge the idea that the financially smallest inventory balance or longest supplier terms must be operationally best. The simulation becomes a platform for asking what happens to stock availability, supplier reliability and customer experience when one metric is optimised in isolation.

What students do

Review Northwood Furnishings, the CFO role and the expansion decision.
Calculate receivables, inventory, payables, turnover ratios, DSO, DIO, DPO and the Cash Conversion Cycle under alternative strategies.
Submit strategy choices and rationales, then compare the logic behind balanced working-capital choices.
Manage 12 simulated months in which decisions involve supplier relationships, payment terms, receivables, inventory, customer credit, collections, cash flow, capital expenditure and risk.
Review updated metrics and financial statements after decisions.
Submit a final Expand, Expand with Caution or Delay Expansion recommendation, then compare the resulting financial profile and cohort outcomes.
For Quality Management, add a short quality-risk note specifying which supplier, availability, service or defect measures would be required before accepting the financial recommendation.

Recommended course placement

After Session 9 when Lean has introduced flow, buffers and waste, or after Session 11 when supplier quality is explicit.
Inside a two- or three-hour applied class with a separate quality debrief.
As optional individual evidence because every participant completes the CFO role independently.

Knowledge students should have before the simulation

Basic process and performance-measure thinking.
The difference between financial efficiency and process reliability.
Lean or supplier-quality concepts sufficient to identify operational consequences of inventory and payment choices.

Delivery format

Area	Recommended Format
Duration	2-3 hours. The live page supports one session or division into shorter teaching blocks.
Format	Single-player CFO simulation. Every participant independently manages Northwood Furnishings.
Level	Undergraduate, postgraduate and MBA.
Prior knowledge	Beginner accessible, with guidance throughout the activity.
Delivery	In class, online or hybrid, through LMS/LTI or the Finsimco website.
Evidence	Individual calculations, decisions, rationales, scores and ending metrics can inform academic judgement. The leaderboard supports comparison, not automatic grading.

AI impact on Quality Management teaching

AI changes the speed of quality work more than the underlying management problem. Students can now draft process maps, fishbones, control-chart code, audit checklists, quality plans and improvement recommendations very quickly. That makes polished artefacts a weaker signal of learning and increases the value of provenance, method selection, missing information, assumption defence and live challenge.

A workable permitted-use policy is to allow AI for brainstorming, coding support, structure and language where declared, while keeping data provenance, calculations, chart selection, causal claims, source verification and the final recommendation attributable to the student. Credit should shift toward what the student can reproduce and defend.

How AI is changing the subject

Teaching area	AI implication	Lecturer response
Customer and VOC analysis	AI can summarise large volumes of feedback and cluster themes, but it can flatten minority needs or invent confident summaries.	Require traceable source samples, CTQ definitions and an explanation of what evidence was excluded.
Process mapping	AI can draft a process map from a narrative, but it may invent steps or hide informal workarounds.	Require validation with process evidence and identification of where the map is assumed rather than observed.
SPC and capability	AI can generate code and interpretations quickly, but chart choice, subgroup logic and assumptions can be wrong.	Mark chart selection, data provenance, subgroup rationale and interpretation rather than polished output.
Root-cause analysis	AI can generate long fishbones and Five Whys chains.	Require students to label hypotheses, specify disconfirming evidence and separate correlation from verified cause.
Improvement design	AI can propose countermeasures immediately.	Require a pilot, risk assessment, success metric and explanation of why the intervention follows from the evidence.
QMS and audit	AI can summarise procedures and draft audit questions.	Assess evidence selection, materiality, corrective-action logic and the governance of AI-generated documentation.

Course session	Core textbook chapter	Supplement with
Session 1 - Quality foundations and performance excellence	Ch. 1: Introduction to Quality; Ch. 2: Foundations of Quality Management	Reading 8
Session 2 - Customer requirements and quality planning	Ch. 3: Customer Focus
Session 3 - Process focus, mapping and ownership	Ch. 5: Process Focus
Session 4 - Cost of quality, measurement and performance	Ch. 13: Measurement and Knowledge Management for Performance Excellence, supported by lecturer material on cost of quality
Session 5 - Statistical thinking, measurement systems and data quality	Ch. 6: Statistical Methods in Quality Management
Session 6 - Statistical process control and control charts	Ch. 8: Measuring and Controlling Quality
Session 7 - Process capability and control interpretation	Ch. 8: Measuring and Controlling Quality, with capability exercises
Session 8 - Root-cause analysis and quality tools	Ch. 9: Problem Solving and Quality Improvement
Session 9 - Lean, Kaizen and continuous improvement	Ch. 9: Problem Solving and Quality Improvement	Reading 2
Session 10 - Six Sigma and structured improvement	Ch. 10: Six Sigma - Concepts and Implementation	Readings 2 and 3
Session 11 - Design quality, reliability and supplier quality	Ch. 7: Design for Quality and Product Excellence, supplemented with supplier-quality material
Session 12 - Quality systems, leadership, performance excellence and Quality 4.0	Ch. 11: The Baldrige Framework for Performance Excellence; Ch. 12: Strategy and Performance Excellence; Ch. 14: Leadership for Performance Excellence; Ch. 15: Building and Sustaining Quality and Performance Excellence	Readings 1, 4, 5, 6 and 7

Real case studies to use

The twelve fictional examples in the Concept Details are designed as licence-free seminar exercises with complete figures. For a longer assessed case, the two externally published cases below provide verified options.

Toyota Motor Manufacturing, U.S.A., Inc.

Kazuhiro Mishina Harvard Business School Case 693-019 1992, revised 1995

Why it fits: A classic production-system case for teaching built-in quality, line stopping, problem visibility, standard work and the organisational consequences of defects.

Best placement: Sessions 6-9, after students can distinguish control, diagnosis and improvement.

Assessment fit: A process diagnosis or memo that separates symptom containment from system-level corrective action.

View case study

Virginia Mason Medical Center (Abridged)

Richard M.J. Bohmer Harvard Business School Case 610-055 2010

Why it fits: Moves Lean and quality thinking into healthcare, making flow, safety, standardisation, leadership and professional autonomy visible in a service setting.

Best placement: Sessions 9-10 for Lean, Kaizen and change implementation.

Assessment fit: A redesign recommendation with measures, implementation risk and stakeholder response.

View case study

Sample session plan

Session title: Statistical Process Control and process capability Best placement: Sessions 6-7 Session aim: move students from plotting data to deciding whether a process is stable, capable and ready for intervention.

Session stage	Time	Teaching purpose	Lecturer approach	Student output
Pre-class preparation	Before class	Give students a short process dataset, operational definition, subgroup structure and specification limits.	Assign one control-chart reading and ask students to state what a control limit means before they calculate anything.	One-page preparation note identifying data type, subgroup logic and three questions about data credibility.
Opening frame	10 minutes	Set the central question: “Is this process changing, and is it capable of meeting requirements?”	Display two charts with similar averages but different stability. Ask students which process is more predictable and why.	A first-pass signal/stability judgement recorded before calculations.
Mini-lecture	20 minutes	Connect common/special cause, control limits, rational subgrouping, specifications and capability.	Review chart selection, why specifications are not control limits and the precondition of stability before capability analysis.	Students annotate the decision sequence: measure -> control -> capability -> action.
Chart build	30 minutes	Make the signal visible and force evidence-based interpretation.	Teams calculate or complete the chart, check for designed signals and identify what evidence should be investigated next.	Control chart plus three-sentence interpretation.
Capability analysis	25 minutes	Connect stable performance with customer specifications.	Students calculate or interpret Cp/Cpk, then state assumptions and whether centring or variation reduction is the main issue.	Capability note with one rejected management action.
Management decision	25 minutes	Turn statistical evidence into a recommendation.	Give two improvement options with different cost and risk. Teams choose, justify and state what result would cause them to reverse the decision.	One-slide recommendation: action, evidence, risk and next measure.
Challenge	20 minutes	Test whether students can defend method and assumptions.	Challenge subgroup logic, measurement-system credibility, specification interpretation and intervention economics.	Short oral defence with an attributable individual response.
Debrief	15 minutes	Reconnect the tools to the course lifecycle.	Ask which conclusion changed after the stability check and which metric mattered most to the decision.	Individual reflection: one technical error to avoid and one management implication.

Why this session matters: It is the point where students learn to stop reacting to every fluctuation. A good session makes them separate process stability from customer specification, question the measurement system, and defend a management action rather than treating an index or chart rule as the final answer.

Assessment options for a Quality Management course

The intended learning outcomes reward judgement rather than recall, so assessment should repeatedly ask students to recommend and defend. A common defensible pattern is a group applied output carrying most of the summative weight plus an individual component that produces attributable evidence. A 60:40 split is one possible model, subject to local regulations and programme policy. The list below is a menu, not a recommendation to use every format.

Assessment option	Mode	What students submit	Best use
Quality improvement report	Group	A process-based diagnosis and recommendation supported by customer requirements, measurement evidence, root-cause logic, improvement design and control plan.	Strong main summative assessment.
SPC and capability memo	Individual or pair	Interpret a process dataset, justify the chart, identify signals, assess capability and recommend action.	Useful technical evidence with clear attribution.
Lean process redesign	Group	Map a current process, identify waste and rework, propose a pilot and specify measures and risks.	Good mid-course applied output.
DMAIC project	Group plus individual defence	Use Define-Measure-Analyse-Improve-Control gates to structure a larger quality problem.	Strong capstone where a credible dataset is available.
QMS / ISO critique	Individual	Evaluate a quality-system scenario, audit findings, corrective actions and management review evidence.	Good for system-level judgement.
Published case analysis	Individual	Use a verified case to diagnose process, design, leadership or governance failure and recommend action.	Good alternative where proprietary organisational data are unavailable.
Simulation reflection	Individual	Analyse an adjacent simulation decision through a Quality Management lens and identify missing quality measures.	Use only if one of the two approved simulations is included.
Viva or oral defence	Individual	Defend method selection, assumptions, evidence and implementation risk.	High-value attribution and AI-resilient evidence.

Make grading criteria explicit: problem definition, data and measurement quality, method selection, causal reasoning, improvement evidence, control/sustainment, communication and judgement. For group work, plan moderation and individual evidence at the design stage rather than trying to reconstruct contribution after marks are disputed.

The platform records different forms of evidence for the two simulations. That evidence can support academic judgement; it does not replace it. Do not infer an individual student's argument from a team result in Startup Creation, and do not turn the Working Capital leaderboard directly into a grade.

Grading with the Startup Creation Simulation

The Startup Creation Simulation is team-based. Teams develop ventures or investment criteria, pitch and negotiate. For Quality Management, assess a separate quality lens rather than the funding result itself.

Traceability from customer problem to CTQs and a proposed quality plan.
Quality of assumptions about the MVP, reliability, service standard or validation evidence.
How investor questioning exposes weak customer or operating evidence.
A professor-assigned individual reflection identifying what quality data are needed before scale.
The distinction between a commercially persuasive pitch and a process that can meet requirements consistently.

The platform provides team submissions, negotiated terms and comparative results. It does not automatically establish which individual student made which argument.

Grading with the Working Capital Management Simulation

The Working Capital Management Simulation is single-player, so calculations, decisions, rationales and the final recommendation can provide individual evidence. Quality marks should focus on the operational implications, not on a low Cash Conversion Cycle or leaderboard rank alone.

How the student balances inventory reliability, supplier continuity, customer discipline, liquidity and operating risk.
Whether the student distinguishes a finance metric from a quality or service-risk measure.
A quality-risk addendum specifying missing KPIs such as stock availability, supplier defects, service level or complaint impact.
Use of calculations and decision evidence to justify the expansion recommendation.
An individual reflection on a decision that looked financially attractive but created operational risk.

The platform score and leaderboard are comparative evidence only. The academic grade remains a lecturer judgement against published criteria.

Common mistakes when teaching Quality Management

The strongest courses do not only teach students to calculate indices or name improvement methods. They repeatedly ask students to use evidence, question assumptions and make a defensible process or system decision.

Common mistake	Why it weakens the course	Better approach
Turning the course into an inspection module	Students learn to detect defects after the event but miss prevention, systems and customer value.	Teach inspection as one control within a wider prevention-and-improvement system.
Teaching quality as a list of gurus and acronyms	Students can recall names without being able to select or apply a method.	Use historical ideas sparingly and require a decision or output in every session.
Starting SPC before checking the measurement system	Students treat observed variation as process variation even when definitions or gauges are weak.	Make data provenance, sampling and measurement credibility a prerequisite for control analysis.
Using specification limits as control limits	Students confuse customer requirements with statistical evidence about process behaviour.	Teach stability and capability as two separate questions, in that order.
Treating capability indices as grades	Students report Cp/Cpk without checking stability, centring or assumptions.	Require an appropriateness statement and a management interpretation with every index.
Accepting a fishbone as root cause	Brainstormed explanations become “findings” without evidence.	Require a test plan, disconfirming evidence and verification before corrective action.
Teaching Lean as cost cutting	Students associate improvement with headcount reduction and overlook flow, quality at source and learning.	Tie Lean to customer value, waste visibility, stable work and low-risk experimentation.
Writing DMAIC after the solution is chosen	The framework becomes retrospective documentation rather than problem solving.	Use gate reviews and require evidence before moving from Define to Improve.
Treating ISO certification as proof of quality	Students confuse conformity with an effective learning system.	Assess the quality of evidence, audit response, management review and repeated corrective action.
Forcing an adjacent simulation into a core quality concept	Students may assume Startup Creation or Working Capital directly teaches SPC, TQM or Six Sigma.	Use simulations only as secondary contexts and keep the core methods in data labs, cases and improvement workshops.

Frequently asked questions

The first questions address subject design; the later questions cover delivery, assessment, simulations and copy-paste material for course approval or handbook use.

Sample wording: Generative AI may be used for brainstorming, coding support, structure and language editing where declared. Students remain responsible for data provenance, calculations, chart selection, assumptions, source verification and the final recommendation. Any AI-assisted analysis must be reproducible and defensible on request.

Adapt the wording to your institution's academic-integrity policy.

Sample descriptor: This module examines how organisations design, measure, control and improve quality across products, services and operating systems. Students apply customer-focused planning, process analysis, statistical process control, capability analysis, root-cause tools, Lean and Six Sigma improvement, design and supplier quality, and quality management systems to evidence-based managerial decisions.

Related course guides and teaching resources

Operations Management Course Guide

A natural adjacent course family for process design, capacity, improvement and operating systems.

Operations Strategy Course Guide

Useful where quality is positioned as a strategic capability and operating-model choice.

Supply Chain Management Course Guide

Closely related for supplier quality, resilience, inventory and end-to-end process performance.

Strategic Management Course Guide

Useful when quality is taught as differentiation, capability, execution and organisational performance.

Startup Creation Simulation

Secondary fit for VOC, value proposition, MVP quality assumptions and validation before scale.

View simulation

Working Capital Management Simulation

Secondary fit for inventory reliability, supplier continuity and customer-service trade-offs.

View simulation

What should a Quality Management course cover?

Quality Management course overview

Why this course matters

Career path fit

Typical course structure

Applied learning opportunities

Who this guide is for

What does a Quality Management course cover?

The course at a glance

Learning outcomes

Core concepts

Concept Details

Concept 1 - Quality as strategy, customer value and total quality management

Concept 2 - Voice of the customer, critical-to-quality requirements and quality planning

Concept 3 - Process thinking, SIPOC and process mapping

Concept 4 - Cost of quality, KPIs and performance measurement

Concept 5 - Variation, measurement systems and data quality

Concept 6 - Statistical process control and control charts

Concept 7 - Process capability, specification limits and acceptance decisions

Concept 8 - Root-cause analysis and the seven basic quality tools

Concept 9 - Lean quality, Kaizen and waste reduction

Concept 10 - Six Sigma and DMAIC

Concept 11 - Design for quality, FMEA, QFD and supplier quality

Concept 12 - Quality management systems, ISO 9001, leadership and Quality 4.0

Connecting the concepts

Adapting for undergraduate and postgraduate students

The 12-session syllabus

Define quality and requirements

See the process

Measure what matters

Control and capability

Diagnose causes

Improve the system

Design prevention

Govern and sustain

Adapting the syllabus to 10-week and 14-week courses

Simulations: What they are and why they belong in this course

Traditional case study vs simulation

Where simulations fit

Startup Creation Simulation