OPEXSTUDIO
← All examples
Manufacturing / 8D / worked example

Stop the recurring leak

Bring your defect counts and build the next cause test.

Take the full example with youPhotos. People. A practical plan.

Project timeline, actions for every S and checks before completion.

Open sample PDF Free to read. No sign-in needed.
Generated illustration: Stop the recurring leak, starting condition
Generated concept: a possible improved arrangement for Stop the recurring leak
Starting pointProposed concept
Generated illustrations. The concept shows a possibility, not a completed improvement or verified safety result.
Learn it, then try it

Understand the method
behind this example.

Two illustrated lessons with practical steps, a question to try and feedback. Read online or follow the teaching pages in the full report.

A clear starting point

Make the problem
small enough to work on.

Contain the issue, then prove the cause.

Sample baseline6%fail final test
Proposed goal1.5%failure goal

Illustrative starting figures. The goal has not been achieved.

Manufacturing / 8DOPEX field notes

Stop the recurring leak

Contain the issue, then prove the cause.

Sample starting point6%fail final test
Goal to work towards1.5%failure goal
01

D0 Plan

Recurring valve leak

02

D1 Team

Quality and production

03

D2 Problem

144 failures / 2,400

04

D3 Contain

Hold affected lots

05

D4 Cause

Why it leaks; why checks miss it

06

D5 Choose

Verify the correction

07

D6 Implement

Pilot 300 units

08

D7 Prevent

Update checks

09

D8 Recognize team

Close after proof

ContainFind the causeTest the fixKeep it working

A worked example to learn from. Sample figures and people; targets are not achieved results.

People, timing and a clear finish

A plan the team can follow.

Read the full report ↗

Project completion timeline

Planned finish · Day 30
  1. Contain affected lotsMaya · Quality

    Day 1–3 · Every held lot has a traceable release decision.

  2. Test the causeLeon · Engineering

    Day 4–10 · Show why the leak happens and why checks missed it, using repeatable tests.

  3. Pilot the correctionAva · Production

    Day 11–17 · No more than four first-test failures in 300 pilot units, no new failure mode.

  4. Verify and standardizeNoah · Quality

    Day 18–30 · Comparable validation meets the 1.5% goal; recurrence response has an owner.

Proposed timing and fictional owners. Close each action after its check is met; a date alone does not prove completion.

Actions for each S

Planned finish · Day 30
  1. SortSeparate suspect assembliesMaya · Quality

    Identify the affected lot boundary and quarantine suspect seals, fixtures and assemblies through the existing containment owner.

    Day 1–3 · Every suspect lot has a traceable disposition; conforming and suspect parts cannot mix.

  2. Set in orderGive fixtures a clear homeLeon · Engineering

    Separate approved fixtures from trial fixtures and arrange the validated setup tools at the test station.

    Day 4–10 · Two operators retrieve the correct fixture without relying on memory; trial items remain segregated.

  3. ShineExpose recurring residueLeon · Engineering

    Clean accessible approved surfaces and record where residue returns; engineering investigates the source before closure.

    Day 4–10 · The residue source is investigated and the approved response is checked on the next comparable run.

  4. StandardizeKeep one approved setupAva · Production

    Issue the accepted fixture/setup check only after the 8D correction passes its trial; remove obsolete copies.

    Day 18–21 · The released revision matches the trial evidence and operators demonstrate the check.

  5. SustainCheck the next lotsNoah · Quality

    Review comparable final-test results and setup records through day 30, recording every failed check and response.

    Day 22–30 · The failure denominator, setup record and unresolved actions are visible; the goal is not reported as achieved without results.

  6. SafetyReview the work controlsMaya · Quality

    The competent area lead reviews handling, isolation and test-station access before any fixture change and after the pilot.

    Day 1–30 · Required work approvals and unresolved concerns are recorded; the project board does not authorize machine changes.

Proposed timing and fictional owners. Close each action after its check is met; a date alone does not prove completion.

Bring the idea back to your work

Start the conversation with your team.

Use the report to choose one area, name the next action and agree how you will check it. Try a photo from your own workplace, then turn the possibility into a practical plan.

Keep exploring

Another useful starting point.

See every example →