A3 Problem-Solving Template with Coaching Cues

A3 Problem-Solving Template (with Coaching Cues)

Use this A3 to lead a structured team problem-solving conversation that surfaces evidence, tests hypotheses, and verifies that countermeasures fix root causes (not symptoms). Remember: this is a learning tool. Keep entries concise, evidence-focused, and oriented to measurable verification.

Header / Identification

• Title: (Short, outcome-focused)
• Date:
• Owner / Team:
• Scope / Area: (what process, line, or shift is included/excluded)
• Revision / Version:

Background — Why this matters

Describe the organizational or customer impact that motivates solving this problem. Keep it brief and tied to a measurable outcome (safety, quality, delivery, cost, morale).

Coaching cues:

• Ask: Who feels the pain? Whose work or which customers are affected?
• Prefer facts (incidents, defect counts, downtime minutes) over opinions.

Problem / Current Condition (with evidence)

Describe what is happening now. Include concrete evidence: metrics, charts, photos, timestamps, test results, sample sizes, and brief observations from people doing the work.

What to capture:

• Clear problem statement: "What is the gap between desired and actual?" (e.g., "Customer complaints for dimension X increased from 1% to 6% over 3 months")
• Supporting evidence: relevant data and visualizations (trend chart, pareto, photos with captions).
• Where/when the problem occurs (process step, shift, supplier, machine).

Coaching cues:

• Encourage the team to bring real samples or screenshots. If you claim a trend, show the trend.
• Ask: What did you observe directly? What did you infer? Label them clearly.

Target / Goal

State the measurable target and the timeframe (e.g., reduce defect rate to <1% within 90 days). Include acceptance criteria and any constraints.

Coaching cues:

• Make targets specific, measurable, and time-bound.
• Confirm the target is realistic and aligned with business priorities.

Root-Cause Analysis

Use a fishbone (Ishikawa) to brainstorm potential causes across categories (People, Process, Equipment, Materials, Environment, Measurement). Then apply 5 Whys to the most likely causes to reach actionable root causes.

Template prompts:

• Fishbone summary: list top 3 candidate causes with short notes.
• For each candidate cause, perform a 5 Whys chain and record the key finding.

Coaching cues:

• Focus the team on cause-and-effect, not blame. Ask "what allowed this to happen?" rather than "who failed?"
• Validate each step of a 5 Whys with data or observation when possible (e.g., "Why did the sensor read incorrectly? Because calibration interval was missed — show calibration records").
• Be suspicious of single-cause stories; complex problems often have multiple contributing root causes.

Analysis Findings (What we learned)

Summarize the evidence-supported root causes and the reasoning that links current condition to target gap.

Coaching cues:

• Ensure each listed root cause has explicit evidence or a testable hypothesis.
• Document remaining uncertainties and the data needed to confirm them.

Countermeasures (Short-term and Long-term)

List proposed actions to address the root causes. For each countermeasure include: description, expected effect, owner, timeline, resources, and how success will be measured (verification method).

1. Quick containment (if needed): actions to limit immediate customer or safety exposure.
2. Permanent countermeasure: changes to process, training, design, or systems that remove the root cause.
3. Control plan: monitoring or standard work to sustain improvement.

Coaching cues:

• Prefer countermeasures that are specific and testable. Avoid vague language like "improve training" without what and how to verify.
• For each countermeasure, define a clear verification metric and a date to check it.

Implementation Plan

Use a simple action table (who/what/when/resources/risk). Keep tasks small enough to complete in days or weeks, not months.

Coaching cues:

• Ensure owners have the authority and capacity. If not, adjust plan or escalate.
• Include short pilot tests when uncertainty exists.

Verification & Follow-up

Define how you will verify that countermeasures removed the root cause(s). Use baseline and post-implementation measures, sampling plans, and observational checks. Schedule follow-up reviews (e.g., 7 days, 30 days, 90 days).

Verification checklist:

• Did the planned metric move in the expected direction? (show charts)
• Are leading indicators stable (process items completed, calibrations done)?
• Has the problem reappeared in adjacent areas or shifted elsewhere?

Coaching cues:

• If verification is incomplete, plan a focused experiment (PDSA) to reduce uncertainty before standardizing.
• Document what was learned and update standard work, training, and control plans accordingly.

Results & Reflection (Learning)

After the verification period, record outcomes versus target, what worked, what didn’t, and recommended next steps. Capture transferable lessons for other teams.

Reflection prompts:

• Which countermeasure had the biggest effect? Why?
• What unintended consequences appeared?
• What will we standardize, and how will we spread the learning?

Common Pitfalls & Tips

• Treating the A3 as a report rather than a coaching conversation — use the board to facilitate discussion and update it as learning occurs.
• Rushing from problem to solution without evidence — gather a small amount of focused data first.
• Documenting fixes without defining verification methods — always include how you will know the fix worked.
• Blaming individuals — center system causes and process design.

Quick Example (illustrative)

Background: Customer returns for torn packaging increased from 0.4% to 2.3% in 6 weeks. Target: <0.5% in 60 days. Root cause: mismatched conveyor guard height during changeover (confirmed by observation + changeover logs). Countermeasure: update changeover checklist and add a visual gauge; pilot on two lines. Verification: track return rate weekly and audit 10 changeovers per week for 4 weeks.

Using this Template as a Coach

Before filling every cell, run a 30–60 minute huddle with the team to align on scope and evidence. Use the coach prompts to push for data and to keep the problem statement narrow. Keep the A3 evolving — a living record of what the team learns.

When to Escalate

Escalate when owners lack authority to implement necessary countermeasures, or when the problem threatens safety, regulatory compliance, or major customer commitments.

Image / Evidence Guidance

Include annotated photos, process maps, time-stamped data extracts, and short video clips when they add clarity. Label every piece of evidence with date, source, and who collected it.

Suggested Next Steps After Finalizing A3

• Update standard work and training materials.
• Schedule spread activities if improvement is relevant to other lines/sites.
• Archive the A3 with verification evidence for organizational learning.

Suggested image search phrase: a3 problem solving template