Problem Solving A3 / RCA Template (A3, RCA, 8D variants)

Purpose

This compact A3-style template helps teams run disciplined, coachable problem solving that finds real root causes, creates measurable corrective actions, and converts those actions into day-to-day standard work. Use this for recurring escapes, quality escapes, equipment failures, process breakdowns, or when you want a single-sheet narrative that leaders can coach against.

How to use this template

1. Fill the Problem Statement with concrete facts and the measurable gap (what, where, when, impact).
2. Implement immediate Containment to stop customer impact while you investigate.
3. Run a focused Root Cause Analysis using 5 Whys or fishbone and collect evidence.
4. Define Countermeasures with owners, due dates, and clear acceptance criteria.
5. Plan Verification and Sustaining actions that make the fix standard work.

Template fields (complete each section with evidence and dates)

1. Problem statement

Describe the problem in one or two sentences, including facts, location, time frame, and measurable impact.

Guidance: Avoid vague language. Use numbers (defect rate, scrap %, downtime minutes, customers affected).

Example: Paint flake defects on Widget A in Line 2 increased from 0.3% to 2.1% during the overnight shift between 2026-06-01 and 2026-06-07, causing 18 reworks and delayed shipments.

2. Containment (Immediate actions to limit harm)

List temporary actions to protect customers/processes. Include owner, start date, duration, and how to tell when containment is active.

• Action: Stop shipments from Batch X — Owner: Shift Lead — Start: 2026-06-07 — Status: In place
• Action: Inspect and sort product at end of line — Owner: QA — Frequency: every hour

3. Root cause analysis

Choose the method(s) you will use and attach evidence (logs, photos, measurements, shift notes).

5 Whys — record each why and the evidence supporting it.

Fishbone / Ishikawa — map likely causes across categories (Man, Machine, Material, Method, Measurement, Environment) and indicate which causes you will test.

Evidence required: timestamps, machine settings, material lots, operator statements, SPC charts, images.

4. Countermeasures & owner

For each root cause, list the corrective actions (short-term and longer-term), the owner, resources required, due date, and success metric.

• Countermeasure: Adjust curing temp on Oven #2 — Owner: Maintenance — Due: 2026-06-10 — Success metric: defect rate <0.5% for 2 shifts
• Countermeasure: Retrain night operators on handling procedure — Owner: Team Lead — Due: 2026-06-12 — Success metric: observed compliance 100%

5. Verification plan

How will you verify that countermeasures solved the problem? Specify data sources, measurement frequency, acceptance criteria, and the time window for verification.

Example: Daily SPC run charts for Widget A for 10 production lots; acceptance: defect rate ≤0.5% for 5 consecutive lots and no customer complaints for 30 days.

6. Standardization & sustainment

Describe how the change becomes standard work: update SOPs, work instructions, training, checklists, audits, and handover across shifts/sites.

Assign who will update documents, who trains, and how compliance will be audited (frequency, auditor).

7. Lessons captured & knowledge transfer

Summarize key learning, root-cause evidence, and where the record will be stored (team folder, knowledge base). Note any broader opportunities or preventive actions for similar processes.

Coaching prompts for leaders

• What evidence shows this happened? Can we trace it to a time, person, or machine setting?
• Which countermeasures are hypothesis-driven experiments vs. assumptions?
• Who will own follow-through and how will you hold them accountable?
• How will we ensure the solution survives shift changes, weekends, and staffing changes?
• What would success look like in 30, 60, and 90 days?

Common mistakes to avoid

• Stopping at containment without testing root causes.
• Assigning ambiguous owners or due dates.
• Confusing corrective actions with preventing recurrence (no standard work updates).
• Relying on anecdotes instead of verifiable evidence.

Quick worked example (summary)

Problem: Increased paint flake defects on Widget A (2.1%). RCA: 5 Whys found Oven #2 set 15°C below standard due to a manual reset after maintenance. Countermeasure: Restore correct temp, add bake-temp interlock, and update maintenance checklist. Verification: defect rate <0.5% for 5 consecutive lots. Standardize: update SOP, add daily oven-temp check to start-of-shift checklist.

Implementation checklist (RACI-friendly)

1. Document problem with data and evidence — R: Team, A: Supervisor
2. Put containment in place and communicate to shifts — R: Shift Lead, C: QA
3. Run RCA with evidence and list tested hypotheses — R: Problem Solving Team
4. Assign countermeasures with owners, dates, and metrics — R: Improvement Owner
5. Execute verification plan and log results — R: QA / Process Owner
6. Update standard work and train operators — R: Process Owner, A: Training Lead
7. Schedule follow-up audit (30/60/90 days) — R: Continuous Improvement

Where to store the record

Keep the completed A3 and all supporting evidence (photos, logs, test results) in the team’s knowledge folder and link it to your manufacturing knowledge system so lessons are searchable by problem type, machine, and root cause.

Next steps

Use this template as the base for a coached problem solving session. If your team will run many A3s, consider creating a local collection of completed examples, a coach checklist, and a simple audit to ensure fixes persist across shifts.