Module 06
How does the system know whether it is delivering what customers were promised?
Quality is not a slogan and it is not a software package. It is the operating system's ability to keep a promise, notice when it drifts, and improve the process that created the drift.
This Arc
Finish Case 3. Start measuring the promise.
01
Tuesday · Sep 29
6:00–7:20 PM
Module 6 live session
One online discussion lecture: customer quality, costs of quality, variation, and improvement tools.
02
Saturday · Oct 3
still due
Case Study 3: Inventory
Finish the inventory policy this week. Quality thinking should already start informing the project story.
03
Tuesday · Oct 6
next module
Project management
Next week turns operations ideas into scope, milestones, and the final presentation plan.
Course Roadmap
Inventory bought a buffer. Quality asks whether the promise still holds.
01
Orientation
02
Supply Chain
03
Forecasting
04
Capacity
05
Inventory
06
Quality
Tuesday · 6:00–7:20
One 80-minute discussion: from a failed customer promise to a project quality measure.
6:00–6:08
What went wrong for the customer?
Start from a failed promise, not from a chart.
6:08–6:18
Two views of quality
Customer experience versus process conformance.
6:18–6:28
Costs of quality
Prevention, appraisal, internal failure, and external failure.
6:28–6:40
Variation and process thinking
Common cause, special cause, and why reaction can make things worse.
6:40–6:52
Control and capability
Is the process stable? Is it capable of the promise?
6:52–7:06
Tools that change decisions
Pareto, cause-and-effect, and when each tool earns its keep.
7:06–7:14
Project quality measure
Choose one measure and one improvement opportunity.
7:14–7:20
Takeaways
Quality is how the system knows whether it delivered the promise.
Learning Objectives
Leave able to diagnose a quality problem before you decorate it with a tool.
Explain quality from the customer’s promise and from the operating system that must keep it.
Distinguish product and service quality and say why the measurement problem changes.
Classify costs of quality and see why external failure is usually the most expensive.
Recognize common-cause and special-cause variation before reaching for a tool.
Use control-chart and capability intuition to judge a process, not to run software.
Connect quality tools to a concrete improvement decision in the project organization.
Predict
The customer did not get the promise they bought.
Start from the experience, not from a control chart. The first diagnosis usually reveals how a manager thinks about quality.
Take a Position
A meal-kit company promised 'dinner ready in 20 minutes.' One in six boxes is missing an ingredient or arrives too late to cook that night.
Where should the manager put the first intervention?
Learn
Operations can hit its internal spec and still lose the customer.
Reliability, speed, courtesy, recovery, and whether the offering felt worth the effort.
Conformance, stability, yield, rework, and the variation hidden inside average performance.
Not every dimension deserves equal investment. Choose the quality that customers will pay for or leave over.
Learn
Goods make some quality dimensions easy to measure. Services hide them in the moment.
Durability can sit on a shelf. Empathy cannot. Most student projects are bundles: a good plus a service experience that either protects or wrecks the good.
Classify
Which quality story is this?
Classify each example as product-heavy, service-heavy, or both.
Tap a bucket for the selected item
0/4 classified
Learn
You will pay for quality either before the defect or after the customer finds it.
Training, process design, supplier development, mistake-proofing, and better specifications.
Inspection, testing, audits, and incoming checks. Useful, but not the same as improvement.
Scrap, rework, downtime, and the hidden factory that exists to fix yesterday’s work.
Returns, warranty, lost accounts, complaint handling, and reputation damage.
Classify
Which cost of quality is this?
Prevention and appraisal are investments. Failure costs are the invoice for not investing earlier.
Tap a bucket for the selected item
0/4 classified
Which statement is the best managerial reading of quality cost?
Learn
Managers get into trouble when they treat noise as a signal, or a signal as noise.
Everyday variation from the current method, materials, people, and environment.
A new supplier, a broken tool, a one-off event, or a method that changed without being named.
Adjusting a stable process after every point often increases variation instead of reducing it.
A stable packing line has one slower hour. What should the manager do first?
Predict
Click a point. Decide whether you are seeing noise or a signal.
These are order-cycle times in minutes. The center line is the process average. The dashed lines are control limits from the process, not from the customer promise.
Manager takeaway
Point 9 sits outside the control limits. Investigate a special cause before you redesign the whole process.
Pink point: beyond a control limit. Gold points: inside the current process voice.
Which statement is the best way to read a control chart in this class?
Learn
A process can be perfectly consistent at disappointing the customer.
Control charts describe the voice of the process. Specifications and service promises describe the voice of the customer. Both matter, and they are not the same question.
A control chart asks whether the process is statistically consistent, not whether customers like the result.
A stable process can still be consistently too slow, too wide, or too late for the customer.
Unstable processes need investigation. Stable but incapable processes need redesign or a different promise.
Learn
Do not start with a favorite tool. Start with the decision you need to make.
A few causes or defect types often create most of the pain. Rank before you brainstorm forever.
Fishbone thinking organizes people, method, machine, material, measurement, and environment.
Many quality problems are handoff, wait, and rework problems that a map makes visible.
Count and plot before you argue. Data beats the loudest anecdote in the room.
Classify
Which tool should lead?
Choose the tool that would change the next conversation, not the tool that looks most technical.
Tap a bucket for the selected item
0/4 classified
Apply
Your project needs one measure and one improvement opportunity, not a quality textbook.
Name the customer promise that would hurt most if it failed.
Choose one quality measure the project organization can actually collect.
Say whether the current pain looks like common-cause or special-cause.
Pick one tool that would change the next management decision, not just decorate a slide.
Hint: Name the promise, the measure, whether the pain looks common-cause or special-cause, and the first tool you would use.
Wrap-Up
Quality is how operations learns whether the promise survived contact with the process.
Quality is the system’s way of knowing whether the customer promise was kept.
Customer experience and process conformance are related, but they are not the same view.
Prevention is usually cheaper than paying for failure after the customer sees it.
Managers must separate common-cause variation from special-cause signals.
Control asks if the process is stable. Capability asks if the stable process can keep the promise.
A tool matters only when it changes where attention, money, or process design goes next.