Unit 4.6 — Quality management
Learning outcomes (from the 9587 syllabus). This note is complete when every bullet below is covered.
Learning outcomes
- Importance of quality: implications of poor quality
- Approaches to ensure quality: quality control; quality assurance; quality improvement phases (Plan, Do, Check, Act)
PDCA is not covered in the coursebook — learn it from this note. (The book teaches TQM and benchmarking, which 9587 does not require.)
Running example: Swift Logistics must deliver parcels undamaged and on time — quality is central to its reputation.
Big picture
In plain English: quality means the product or service meets customer expectations. Quality management is how a business makes sure this happens — by checking at the end (quality control), by preventing errors in the first place (quality assurance), and by continuously improving (PDCA).
Analogy: quality control is inspecting the cake after baking and throwing away burnt ones; quality assurance is using the right recipe and oven temperature so none burn; PDCA is improving the recipe each time.
Core content
1. The importance of quality
Implications of poor quality:
- Lost customers and sales (they go to rivals)
- Complaints, returns and refunds
- Rework and waste (fixing or scrapping defects)
- Damage to reputation and brand
- Possible legal problems (unsafe products)
If Swift Logistics frequently delivers damaged or late parcels, customers switch to a rival courier, Swift must pay compensation, and its reputation suffers — losing future orders too.
2. Approaches to ensure quality
| Approach | What it is | When it happens |
|---|---|---|
| Quality control (QC) | Inspecting/testing the output and rejecting defects | After production (detection) |
| Quality assurance (QA) | Building quality into the process so defects are prevented | During production (prevention) |
- QC is reactive — it catches mistakes after they happen (e.g. checking each parcel before dispatch).
- QA is proactive — it sets standards and checks at every stage so mistakes do not happen (e.g. training couriers, using barcode scanning at every handover).
Swift uses QA by scanning each parcel at every stage so a parcel cannot go to the wrong van unnoticed, and QC by a final check before dispatch. QA prevents most errors; QC catches the rest.
3. The PDCA quality improvement cycle
PDCA (Plan – Do – Check – Act) is a continuous improvement cycle:
- Plan — identify a quality problem and plan an improvement.
- Do — implement the change (often on a small scale first).
- Check — evaluate whether the change improved things.
- Act — if it worked, make it standard practice; if not, adjust and repeat the cycle.
Swift notices parcels are often damaged in transit (Plan). It introduces padded packaging in one depot (Do). After a month, damage has fallen 30% (Check). Swift then rolls out padded packaging to all depots (Act) — and starts the cycle again on the next problem.
Analysis & evaluation points (AO3/AO4)
- QC vs QA trade-off: QC is cheaper to set up but defects are already made (waste); QA prevents defects but costs more to build in.
- Quality costs money but saves more — prevention is usually cheaper than fixing failures and losing customers.
- Quality and productivity can conflict — rushing to raise output may lower quality.
- PDCA is continuous — it never “finishes”; the business keeps improving.
Language bank: however · on balance · it depends on · trade-off · in the long run ·
Worked examples (PEEL)
PEEL = Point → Explain → Example → Link. Use this structure for every written answer.
Worked example 1 — “Explain” (6 marks)
Question: Explain the difference between quality control and quality assurance.
- P (Point): Quality control detects defects; quality assurance prevents them.
- E (Explain): QC inspects finished output and rejects faulty items, while QA builds checks into the process so faults do not occur in the first place.
- E (Example): Swift’s QC checks parcels before dispatch, whereas its QA scans parcels at every handover to prevent misrouting.
- L (Link): So QC is reactive (after the error) and QA is proactive (before the error).
Worked example 2 — “Evaluate” (10 marks)
Question: Evaluate whether spending on quality is worthwhile for a business.
- P (Point): Spending on quality reduces failure costs and protects reputation.
- E (Explain): Preventing defects avoids rework, refunds, complaints and lost customers — which are usually far more expensive than prevention.
- E (Example): Swift’s investment in padded packaging reduces damage claims and keeps customers loyal.
- L (Link): This raises long-run profit.
- Evaluate (AO4): However, quality spending has limits — excessive quality beyond what customers need wastes money. On balance, quality spending is worthwhile up to the point where the cost of improvement exceeds the savings from fewer failures.
Application bank (Singapore quick reference)
| Idea | Singapore example |
|---|---|
| Quality assurance | ISO-certified manufacturers and service firms |
| Quality control | SFA food-safety inspections; electronics final testing |
| PDCA | Continuous-improvement programmes in manufacturing plants |
| Reputation for quality | SIA’s service standards; DBS’s digital reliability |
Exam technique
- How it appears: a case study describes quality problems and asks how the business can improve quality.
- Model skeleton for “improve quality”: identify the problem → choose QC or QA (or both) → explain PDCA to keep improving → justify.
- Common pitfalls: describing QC/QA without the detection/prevention distinction; forgetting the implications of poor quality.
Self-test checklist
Essay practice: “Evaluate the view that quality assurance is better than quality control.” (25 marks)