Free A3 Problem-Solving Template + 5-Whys Guide (for Indian Plant Managers)

If you can't fit your problem on one A3 sheet, you don't understand it yet. That's the rule Toyota engineers grew up on, and it still works.

This is the practical version — the A3 that plant managers in India actually use, not the academic 12-step variant. Print it, hang it on the meeting room wall, run your next root-cause discussion against it.

The 8 boxes of an A3

An A3 sheet is divided into 8 regions. Left side = problem. Right side = solution. You move left-to-right as your understanding deepens.

Left side (problem)

1. Background / Title. One sentence: what's the symptom + where + how often?
2. Current state. What's happening today — with numbers. "Defect rate on Line 2 is 4.2% vs target 1.5%." Use a photo or a chart.
3. Goal / Target state. What does success look like + by when? "Defect rate ≤ 1.5% by end of Q2."
4. Root cause analysis. 5-Whys or fishbone. This is the heart of the A3.

Right side (solution)

5. Countermeasures. What you're going to do, ranked by impact / effort.
6. Implementation plan. Who, what, when. Concrete dates, named owners.
7. Follow-up + verification. How you'll measure if it worked + when you'll check.
8. Lessons learned. What you'd do differently next time + what becomes new standard work.

The 5-Whys, done properly

Five "whys" sounds trivial. It's not. Done right, it surfaces the system root cause, not the proximate cause.

Example from a real plant in Pune:

Problem: Spindle bearing failed on CNC #3 (March).

Why 1? Bearing overheated.
Why 2? Lubrication was inadequate.
Why 3? The operator skipped the morning lube check.
Why 4? The startup checklist doesn't include the lube step.
Why 5? When the new SOP was rolled out last year, the lube step was lost in transcription.

Root cause: SOP version control gap.
Countermeasure: Add the lube step. Audit all SOPs against legacy versions. Set quarterly SOP review cadence.

Notice: the proximate cause was operator error. The root cause was a process gap. If you stop at "operator forgot", you'll punish the wrong person and the problem recurs.

Common mistakes in Indian-plant 5-Whys sessions

1. Stopping at "human error"

Human error is almost never the root cause. It's the surface of a system problem. Ask why the human was set up to fail.

2. Not having data

"We think there are more defects on the night shift." Do you have the numbers? If not, that's not a problem to solve yet — that's a measurement gap to fix first.

3. Multiple problems on one A3

One A3, one problem. If you find yourself listing 3 different defects, you need 3 A3s. Discipline forces clarity.

4. The 5-Whys done solo

Best 5-Whys are done in a small group — 3-5 people who actually know the process. Solo = confirmation bias.

Multi-cause problems (the fishbone)

Some problems don't have a single root cause — they have 3 contributing factors stacking up. For those, run a fishbone alongside the 5-Whys.

The 6M fishbone categories:

• Man — skill gaps, fatigue, communication
• Machine — wear, calibration, maintenance
• Method — SOP gaps, sequence, training
• Material — supplier defects, mixing, storage
• Measurement — gauge accuracy, sample size, frequency
• Environment — temperature, humidity, lighting

One sheet, 6 lines, 2-3 contributing causes per line. Then pick the top 1-2 to attack with countermeasures.

What to do with finished A3s

A3 closed → solution implemented → savings verified → turn it into an OPL (One-Point Lesson) for the operators on that line. The A3 lives in the binder; the OPL lives at the workstation.

This is where most plants miss the multiplier. A solved problem becomes prevention only if the lesson reaches the people doing the work.

What we built

The Solve / A3 module in LeanOS:

• Each finding can be promoted to an A3 case
• 5-Whys + fishbone in-app, with AI suggesting the next "why" question
• Countermeasures tracked with owners, due dates, after-photos
• Two-step close-out: case lead submits evidence, admin verifies (no rubber-stamping)
• Closed A3 auto-drafts an OPL for the operators

Want to see how it'd handle your plant's last 5 nagging issues? Run the 30-second calculator.