First Pass Yield (FPY) Quick Wins Pack

Quick Wins Pack — Catch defects earlier, raise FPY

First pass yield (FPY) improves when teams detect defects as close to their origin as possible and remove opportunities for human error. This pack gives you short, practical experiments and templates you can pilot within a single shift or week to see measurable FPY gains without large investments.

Why FPY matters

FPY is the share of units that successfully complete a process step (or end-to-end process) without rework or repair. Use it to reduce rework cost, shorten lead-time, and increase effective throughput. FPY (step or process) = good units out / total units started. Track both step-level FPY and end-to-end FPY to avoid masking problems.

How to use this pack

Start small: pick one high-impact process or product family, run a short pilot, measure carefully, and iterate. Use the checklist below to find where to focus, apply a containment gate when needed, try a poka-yoke or simple inspection, and run the pilot measurement plan.

1) Quick scan checklist — find high-impact defect points

• Gather recent scrap, rework and customer-return records and create a Pareto of defect types, processes, and part numbers.
• Interview operators and technicians on the line: where do they spend most rework time? What steps are fiddly or inconsistent?
• Watch the process for one cycle (gemba walk) and note hand-offs, part orientation, tooling changes, or visually ambiguous features.
• Identify where defects are first detected today (incoming inspection, final test, customer) and list the delay and cost to fix.
• Prioritize using expected impact (cost or throughput) × ease of change to create a 2×2 quick target list.

2) Containment gate template (use temporarily while you fix the root cause)

Use a containment gate to keep defects from flowing downstream while you work the root cause. Make it simple and accountable.

3) Simple poka-yoke ideas — low-cost error-proofing

Pick ideas that are cheap to try and reversible. Group by common process types:

• Assembly: color-code mating parts; asymmetrical fixtures so parts only fit one way; torque tools with go/no-go indicators; visual pass/fail stickers for adhesive cures.
• Machining / fabrication: fixture pins for orientation; limit switches that prevent cycle if part not present; simple templates to verify critical dimensions.
• Electronics / testing: keyed connectors, foolproof cables, guided insertion jigs, single-purpose test fixturing that only accepts correctly populated PCBs.
• Packaging / labeling: barcode scan at last step to confirm correct configuration; physical stops to prevent double-feeds; label-verify station with simple light signal.

4) Test & inspection placement guide

Principles for deciding where to place an inspection or test:

1. Detect as early as possible—prefer detection in the same process that creates the defect.
2. Prefer in-process checks that operators can act on immediately rather than end-of-line checks that cause rework upstream.
3. Use lightweight checks first: visual checks, go/no-go gauges, torque verification, simple functional checks before complex tests.
4. Match inspection frequency to risk: 100% for critical features, sampling for lower-risk characteristics with clear accept/reject criteria.
5. Avoid testing that merely shifts failure to another process—pair inspections with corrective actions and root-cause work.

5) Pilot measurement & reporting plan

Keep measurement practical and trustworthy so results drive decisions.

6) Implementation checklist

• Pick owner for the pilot and a daily reporter.
• Train the operators on the containment gate and inspection method (5–15 minutes).
• Prepare simple recording sheets (paper or electronic) and one place to store photos and tags.
• Run pilot for predetermined period; review results in a quick huddle each day.
• If effective, plan standardized work updates and permanent error-proofing; schedule root-cause corrective actions in the backlog.

Common pitfalls & cautions

• Don’t treat inspection as the final solution—use it to buy time while fixing root causes.
• Bad data hides the truth: define clear defect codes and use simple forms so operators record accurate information.
• Vanity FPY: track both step and process FPY and watch for gaming (e.g., shifting defects to unmeasured steps).

Next experiments to try

• Operator-assisted self-checks: add a two-second verification step with a simple visual cue.
• One-point lesson + shadowing for the trickiest step to transfer tacit knowledge fast.
• Temporary physical fixture to force correct orientation for 1000 units — evaluate defect drop.

Templates included (examples inline)

This playbook includes a short checklist, a Containment Gate form, and a pilot measurement sheet you can copy and adapt for your team.

Where this pack connects to broader improvement

Use these quick wins to build momentum. Successful pilots should feed into standard work updates, training, corrective action workflows, and periodic FPY reviews so improvements stick.

Image search phrase: first pass yield improvement