3.5 · Quality tools (5S, Pareto, Ishikawa, PDCA)

Level 3 · Quality & ISO 9001

3.5Quality tools (5S, Pareto, Ishikawa, PDCA)

Goal: chain the tools: tidy (5S), prioritise (Pareto), understand (Ishikawa), prove (PDCA).
Estimated time: 10 min · self-paced reading · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • 5S tidies the workstation: sort, set in order, shine, standardise, sustain.
  • Pareto prioritises: few causes cause most damage — hit enemy No. 1.
  • Ishikawa understands, PDCA proves: causes in 5M, pilot test, standardisation.

Threaded mini-case — Hakim halves defects

Final act: Hakim's paint shop accumulates dust, runs and shades. Pareto names dust (nearly half the defects). As a group, the 5M Ishikawa points to clogged filters and skipped de-dusting. Hakim tests on one booth (PDCA): down 60%, before/after photos posted — then rollout. 5S sustains the gain.

Final episode of cases 3.1-3.4 — Hakim chains the tools.

1. 5S and Pareto: order and priority

The 5S (sort, set in order, shine, standardise, sustain) gains time, safety and quality: pilot area, before/after photos, scored audits posted. A rising score motivates.

The Pareto chart ranks defects by cost and frequency: about 20% of causes cause 80% of damage. The sorted bar chart names enemy No. 1. Without it, efforts scatter.

2. Ishikawa and PDCA: understand and loop

The Ishikawa diagram (5M: environment, manpower, equipment, methods, materials) trawls causes as a group, with the 5 whys down to the root cause. Alone in the office, it is worthless.

The PDCA cycle (plan, do, check, act) tests the fix small before standardising. Chained: Pareto chooses, Ishikawa understands, PDCA proves.

Common misinterpretation: “5S is punishment cleaning” or “Ishikawa alone is enough”. No. 5S without meaning or standard collapses within a week; with photos, audits and ritual, it holds. And analysing alone in the office misses shop-floor causes: it is as a group, at the workstation, that the 5M speak.
Solve instead of suffering 5S tidies, Pareto chooses, Ishikawa understands, PDCA proves 5S One tidyworkstationPareto Enemynumber oneIshikawa Causes in 5MPDCA The testthat proves
5S tidies, Pareto chooses, Ishikawa understands, PDCA proves
Text version of the diagram (SEO / screen readers / translation): 1) 5S: Hakim tidies one pilot booth and audits it. 2) Pareto: dust comes out on top of defects. 3) Ishikawa: as a group, filters and method named. 4) PDCA: test on one booth, down 60%, rollout. Lesson: choose, understand, prove — with before/after photos.

The tool wall, no jargon

“We did 5S: we find wrench No. 2 without searching.”
Order that saves time
“Pareto named dust: we stopped attacking everything at once.”
Priority that relieves

Sober tools: less talk, more posted evidence.

🔎 Concrete example — Paint defects halved

Hakim puts the right tool at each step.

Pareto: dust far ahead, then runs, shade.
Ishikawa 5M: clogged filters, skipped de-dusting.
PDCA: filters + sheet on 1 booth, measured fall.
→ roll out, post the curve.

Result: enemy No. 1 treated first.

Reflex: Pareto first, always.

Section vocabulary

5S
Method in 5 steps: sort, set in order, shine, standardise, sustain.

Simple example: Hakim's pilot booth, audited and posted.

What it is not: a big punitive clean-up with no standard.

Reflex: before/after photos at each pilot.

Pareto (80/20)
Ranking by importance to target the few causes causing most effects.

Simple example: Dust targeted before runs and shade.

What it is not: treating the easy small defect first.

Reflex: always sort by cost before acting.

Ishikawa (5M)
Fishbone: causes classified into environment, manpower, equipment, methods, materials.

Simple example: The group names filters (equipment) and method.

What it is not: an analysis done alone in the office.

Reflex: run it as a group, at the workstation.

5 whys
Asking why in cascade down to the root cause.

Simple example: Why dust? Filters. Why? Never changed.

What it is not: stopping at the first symptom.

Reflex: dig to an actionable cause.

PDCA
Deming wheel: plan, do, check, act, in a loop.

Simple example: Test on one booth, measure, roll out.

What it is not: rolling out with no test and no measure.

Reflex: test small before standardising.

In practice — Using quality tools

  1. Apply 5S to one pilot workstation, with photos and audit.
  2. Build a Pareto by cost to name enemy No. 1.
  3. Analyse as a group (5M Ishikawa + 5 whys).
  4. Close the loop with PDCA: small test, measure, standardise.
You make improvement methodical: prioritise, understand, prove.

Ready-to-say script — launching the project (1 min)

“This week, 5S pilot on booth 1, before/after photos. Then a Pareto of our defects: we attack enemy No. 1 together with Ishikawa, then test the fix on one booth before rolling out.”

Say it at the workshop point, with the defect board in front of you.

Copy-paste template — Pareto-to-PDCA sheet

SORTED DEFECTS (Pareto, by cost): _______________
ENEMY No. 1: _______________
5M CAUSES (Ishikawa, as a group): _______________
PDCA TEST (where, what, until when): _______________
BEFORE / AFTER MEASURE: _______________

Very small business / tight budget

One pilot corner, one hand-drawn Pareto board, one PDCA in a notebook: method matters more than tools.

SME in Algeria

Hakim runs the Ishikawa with operators and maintenance, in workshop language, with photos.

Services

Pareto on complaint motives, Ishikawa on the file journey, PDCA on one pilot counter.

Safety

Couple 5S with safety: clear, mark, signpost — without replacing HSE instructions.

Caution: Tools complementing instructions: 5S erases neither safety rules nor work instructions; any change to equipment or method stays validated by the supervisor and, if needed, the prevention officer before rollout.

✓ Best practices

  • Start with a pilot, with before/after photos.
  • Run Pareto before any analysis.
  • Chain the tools instead of isolating them.

✗ Common pitfalls

  • Making 5S a meaningless punishment.
  • Attacking the easy small defect first.
  • Analysing alone in the office, without the shop floor.

Key takeaways

  • 5S: tidy workstation = efficiency, safety, quality.
  • Pareto: the few causes causing most effects.
  • 5M Ishikawa + 5 whys: climbing back to root causes.
  • PDCA: test small, measure, standardise.

48h challenge — apply it tomorrow

Launch a 5S on one workstation (before/after photos) and list your top 3 defects for a future Pareto.

Section exit checklist
  • I can name 5S, Pareto, Ishikawa and PDCA.
  • I can chain: choose, understand, prove.
  • I have launched 1 5S pilot or 1 Pareto sort.
Self-assessment 1-5: do I prioritise on facts?do I test small before rolling out?

Frequently asked questions

How do you chain Pareto and Ishikawa effectively?

Pareto prioritises (which cause to treat: the few causing most), Ishikawa analyses (which root causes, in 5M and as a group). Together with the 5 whys, they target the essential then treat real causes — before proving with a pilot PDCA.

Does 5S really improve quality and safety?

Yes, beyond tidying: less time lost, less clutter and risk, visible anomalies (leak, cable, floor), fewer errors. Standardised and audited, it holds; without ritual, it collapses.

Check your understanding

Multiple defects: where to strike first under Pareto?

Additional resources (optional, to go further)

Level 3 examFresh, harder questions to test what you've learned