A3 Problem Solving Template with Coaching Cues

A3 Problem Solving Template

Use this A3 to structure a clear, evidence-based problem solving story. Capture facts, show causation, assign ownership, and explicitly define how you'll verify that countermeasures worked. Keep the A3 focused, visual, and actionable.

Title / Owner / Date

Title: Concise, outcome-focused statement (e.g., "Reduce late deliveries to <5% by Q3")

Owner: Name and role of the person accountable for driving the A3

Date: Start date (and a revision date field)

Background (Why this matters)

Quick context: why the issue matters to customers, safety, cost, or operations. Keep it to a few sentences and link to any supporting documents or metrics.

• Customer impact
• Financial or safety risk
• Relevant constraints or boundaries

Current Condition (Evidence-based)

Describe what is actually happening, using data and visuals where possible. Include timelines, process maps, photographs, trend charts, or defect samples.

• Key metrics (with baseline numbers and period)
• Observed facts (who, what, where, when, how often)
• Conditional statements to avoid (don’t write opinions as facts)

Goal / Target

Define a specific, measurable target and a timeframe. Make the target clearly testable.

Example: "Reduce scrap rate from 4.2% to ≤1.0% within 90 days; measure by daily line yield."

Root Cause Analysis (evidence-based)

Document the analysis that links the current condition to one or more root causes. Prefer evidence-first techniques and capture supporting data for each suspected cause.

1. Use structured tools: 5 Whys (document each why and the evidence), Fishbone/Ishikawa (populate branches with observed causes).
2. Collect evidence: measurements, timestamps, photos, process observations, error logs, supplier data.
3. Validate causes: Where possible, run quick experiments or checklists to confirm cause-effect (e.g., temporarily restore a suspected failure mode and see if problem returns).

Record conclusions: State the primary root cause(s) as testable hypotheses (e.g., "Root cause: worn turret spacer causing misalignment, evidenced by measured offset > tolerance in 8/12 failed parts").

Countermeasures & Action Plan

List countermeasures tied directly to the root cause hypotheses. For each action include owner, due date, expected result/metric, and resources required.

Prioritize quick, low-risk experiments (PDCA): pilot countermeasures, measure, then scale.

Implementation Plan

Describe the rollout steps. Include pilot scope, training, process changes, and communication plan. Capture who must approve and any gating criteria.

• Pilot dates and scope
• Training and standard work updates
• Materials, parts, or tooling changes
• Escalation path if pilot fails

Follow-up / Verification

Be explicit about how you'll verify success and over what timeframe. Verification is not opinion — it is measurement and observation.

• Primary metric(s) to track and frequency (e.g., daily yield for 30 days)
• Acceptance criteria (e.g., sustained target for N consecutive production days)
• Who will review results and when
• How long the countermeasure will be maintained before declaring closure

Lessons Learned & Standardization

Capture what worked, what didn't, and how to prevent recurrence. If successful, describe how to update standard work, training, and documentation.

• Suggested updates to SOPs, checklists, or visual controls
• Knowledge transfer plan (who needs to know)
• Follow-on improvement opportunities

Coaching Cues for Facilitators

Use these prompts during review meetings to keep the team evidence-focused and accountable.

• "Show me the data." Ask for the actual measurements, charts, photos, or samples supporting each claim.
• "What specifically changed?" Force clarity between symptoms and causes.
• "How will you know this worked?" Require a measurable verification plan before approving implementation.
• "What is the smallest test you can run to validate this hypothesis?" Encourage quick experiments over large rollouts.
• "Who owns the risk if this fails?" Make accountability explicit and ensure escalation paths exist.
• "Are we fixing a process or blaming a person?" Guard against scapegoating; focus on system fixes.

Verification Checklist (quick)

• Problem statement is specific and supported by data
• Target is measurable and time-bound
• Root cause(s) are described as testable hypotheses with evidence
• Countermeasures map to root causes and have owners and due dates
• Verification method and acceptance criteria are defined
• Standard work or controls are planned for sustained improvement

Common Pitfalls & How to Avoid Them

• Jumping to a fix without evidence — require a hypothesis and test
• Confusing correlation with causation — collect causal evidence
• Documentation without follow-up — schedule and commit to verification reviews
• Ownership ambiguity — assign a single accountable person for closure
• No plan to sustain — include standard work and monitoring in the plan

Short Example (mini A3)

Background: Customer complaints about scratched panels increased 300% over 2 months.

Current Condition: Scrap rate rose from 0.5% to 2.0%; inspections show scratches concentrated at Station B during night shift; photos confirm tool interference.

Root Cause: Tool clamp was misaligned due to worn guide sleeve (5 Whys documented; measurements show clearance > spec).

Countermeasure: Replace guide sleeve, add pre-shift clamp check, include inspection in shift checklist. Owner: Maintenance Lead. Due: MM/DD. Verification: Scrap rate ≤0.8% for 20 consecutive production days.

How to Use This Template

Keep the A3 concise and revisable. Attach supporting evidence (charts, photos) rather than writing long paragraphs. Use the coaching cues during weekly reviews. If this A3 will be reused across sites or business units, consider packaging it into a Toolkit (see Capability Notes).