QUALITY

Product defect probability tree

This probability tree separates a product's actual condition from the result of an inspection. A defective item can be found or missed, while a good item can be falsely rejected or pass. The branch probabilities describe how the inspection behaves within each condition. This is a useful structure for quality teams because it distinguishes the true state from the observed result. Add the proportion of defective products at the first split when you need overall probabilities, such as the chance that a rejected item was genuinely defective. The same pattern also applies to tests, alarms, and screening processes. It gives readers a concise reference they can reuse when discussing the result with colleagues.

UPDATED 2026-09-24
EXAMPLEProduct defect probability tree
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Inspection accuracy

Key decisions

  • Actual state: Separate defective from good products.
  • Test result: Show found, missed, false reject, and pass.
  • Conditional rates: Put inspection accuracy on each branch.

When to reuse this

Use for explaining sensitivity and false-positive rates in quality control.

FAQ

Frequently asked questions

What is a false reject?01
A good product that the inspection incorrectly marks as defective.
What is a missed defect?02
A defective product that passes the inspection.
Can I add product defect rates?03
Yes. Put those probabilities on the first split.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.