A3 problem solving is a structured, one-page method for working through a problem from symptom to verified fix, developed at Toyota and named after the ISO A3 paper size (roughly 297 by 420 millimeters) that the whole report must fit on. It forces a team to tell the complete story of a problem, the current condition, the target, the root cause, the countermeasures, and the follow-up, in a single visual document. The size constraint is the discipline: if it does not fit on one A3 sheet, the thinking is not yet clear enough.
The A3 is as much a thinking tool as a report. By limiting the space, it removes padding and forces the author to separate signal from noise. A good A3 can be read left to right, top to bottom, in a few minutes, and a reviewer can see the logical thread from the problem to the proposed action. It travels well on a shop floor, pins to a board, and becomes a shared reference during a review meeting. The document is also a coaching artifact: a mentor reads the A3 and asks questions, which is how problem-solving skill spreads through an organization.
Most A3 templates follow a consistent left-to-right flow across seven sections:
The word countermeasure is deliberate. A solution implies the problem is gone forever, while a countermeasure is a considered response that you will measure and adjust. That mindset keeps teams honest during follow-up.
The A3 is essentially a written form of the Plan, Do, Check, Act cycle. The first five sections (background through countermeasures) are Plan. Executing the plan is Do. The follow-up section, where you compare the after result against the target, is Check. Deciding whether to standardize the fix, adjust it, or escalate is Act. Because the follow-up column loops the author back to reassess the current condition, the A3 makes continuous improvement visible rather than a one-time event. It pairs naturally with structured improvement frameworks such as DMAIC and sits at the heart of a total productive maintenance culture.
The A3 does not replace root-cause tools, it houses them. Two show up most often in the root-cause section:
Teams often combine them: a fishbone to surface candidate causes, then 5 Whys on the most likely branch. For failure-prevention work, an FMEA and a Pareto analysis help you prioritize which causes to chase first.
Consider a packaging line running one shift of 8 hours (480 minutes). The team notices frequent short stops and wants to build an A3.
Current condition (with data): Over one shift, the line logged 90 minutes of unplanned stops. Machine data shows 60 of those minutes came from one labeler jamming. The line was scheduled for 480 minutes, so available run time was 480 minus 90, which is 390 minutes. Availability was 390 divided by 480, or 81.3 percent.
Goal: Cut labeler-related downtime from 60 minutes to 15 minutes per shift within four weeks, lifting availability to about 88.5 percent (480 minus 45, giving 435 divided by 480).
Root cause (5 Whys): Why did the labeler jam? Labels misfed. Why? The label roll slipped. Why? The tension roller was worn. Why? It was never on a maintenance schedule. Why? No preventive task existed for that part. The true cause is a gap in preventive maintenance, not operator error.
Countermeasure and plan: Add a preventive task to inspect and replace the tension roller every 30 days, assigned to the maintenance lead, starting next week.
Follow-up: After four weeks, labeler downtime measured 12 minutes per shift, beating the 15-minute target. Availability rose to about 89 percent. The countermeasure is standardized. This closes the proactive maintenance loop and reduces future unplanned downtime.
An A3 is only as strong as the numbers in its current-condition and follow-up sections. Estimates and hand-tallied logs undermine the whole exercise. This is where a real-time monitoring platform becomes the evidence base. Fabrico captures machine states and stop reasons automatically, so your current condition is grounded in measured OEE and downtime data rather than recollection. Because Fabrico offers camera and computer-vision monitoring, it can track stops even on older machines without a PLC, which is often exactly where the messiest, least-documented problems hide.
For the follow-up section, the same live data confirms whether the countermeasure held: you compare the before and after on the identical metric, with the timestamps to prove it. Fabrico is the data foundation here, not a substitute for the A3 thinking or the root-cause judgment your team brings. When a countermeasure is a maintenance change, Fabrico's CMMS turns it into a scheduled preventive task with an owner, closing the plan section with an auditable trail. Related reliability metrics such as MTBF and MTTR give the follow-up even sharper before-and-after context.
No. 5 Whys and the fishbone diagram are root-cause techniques that live inside the root-cause section of an A3. The A3 is the broader one-page framework that carries a problem from background all the way through to verified follow-up, using those techniques as tools along the way.
No. The A3 originated as a physical A3-sized sheet, and many teams still sketch by hand because it is fast and encourages clear thinking. Digital A3 templates are common too. What matters is the one-page discipline and the seven-section logical flow, not the medium.
Fabrico supplies the measured evidence for the two data-heavy sections. Its real-time and computer-vision monitoring produces the current-condition baseline and the follow-up confirmation automatically, and its CMMS turns maintenance countermeasures into scheduled, owned tasks. Fabrico does not do the problem-solving for you, it makes the numbers in your A3 trustworthy.
Ready to ground your A3 reports in measured data instead of guesswork? Book a Fabrico demo and see how real-time OEE and computer-vision monitoring give your current-condition and follow-up sections evidence you can defend.
Login
Blog