A3 Problem Solving: The Toyota Method (Template + Example)

A3 problem solving is how Toyota turned a piece of paper into a thinking discipline. The name is literal: all the analysis fits on a single A3-size sheet (11 x 17 inches). But the sheet is really just the visible surface of a structured conversation that runs from the moment a problem surfaces to the point where a fix is confirmed to hold.

What is A3 problem solving?

A3 problem solving is a Toyota-originated method that captures an entire problem-solving cycle, from background through root cause to follow-up verification, on a single A3-size (11 x 17 in) sheet, following the plan-do-check-act (PDCA) cycle.

Toyota developed the A3 format at its production facilities in the mid-twentieth century as a way to standardize how problems were communicated up the chain. Before the A3, engineers wrote lengthy reports that buried the key question and delayed decisions. The A3 forced teams to think clearly: if you can't fit the whole story on one page, you don't understand the problem yet.

The format spread beyond manufacturing as lean thinking crossed into healthcare, software, finance, and government operations. Today it's used anywhere that teams want structured, compact, and visual problem analysis.

Key Facts

• Toyota credits the A3 as one of the core tools that sustained its lean production system for decades, with internal training materials describing it as the "thinking document" behind every improvement (Toyota Production System, 2019).
• A study published in the Journal of Manufacturing Technology Management (2021) found that teams using structured one-page problem reports reduced time-to-resolution by an average of 28% compared to free-form incident reports.
• The Lean Enterprise Institute lists A3 problem solving as the top mentoring and coaching tool for developing lean thinkers, used in over 60% of lean certification programs surveyed in 2022.

The 7 sections of an A3 report

Every A3 report follows the same structure. The left half covers the problem (Plan); the right half covers the response (Do, Check, Act). Here are the seven sections and what goes in each.

The discipline of the A3 is in the constraint. If a section needs three pages of supporting data, the team hasn't yet distilled the insight. The goal is to force that distillation before anyone starts building solutions.

A3 vs other problem-solving methods

A3 is one of several structured approaches teams reach for. How it compares to the most common alternatives:

A3 sits in a practical middle zone. It's more rigorous than a Five Whys session because it demands goal-setting and follow-up, but less heavyweight than DMAIC, which requires statistical project management and a defined sponsor. When a lean team encounters a recurring problem they haven't solved in two previous attempts, the A3 is usually the right next move.

How to complete an A3

Completing an A3 follows the four phases of PDCA. The sheet itself is the artifact, but the thinking happens in conversations between the writer and a coach or manager.

Step 1: Write the background (Plan)

Start by answering why this problem deserves attention now. Include the process affected, the stakeholders who care, and a one-sentence connection to business goals. Keep it to three to five sentences. If you can't write a brief background, the problem scope isn't clear yet.

Step 2: Map the current state (Plan)

Show the problem with data, not opinions. Sketch the relevant process steps (a simple flow or swim-lane), mark where the failure occurs, and include the numbers: frequency, defect rate, cost, customer complaints. A current state built on actual data prevents the team from solving the symptom instead of the cause.

Step 3: Set a specific goal (Plan)

Define the target condition in measurable terms. "Reduce order entry errors from 4.2% to below 0.5% by August 31." A vague goal ("fix the error problem") makes it impossible to evaluate whether countermeasures worked. The goal also sets the baseline for the follow-up section.

Step 4: Analyze the root cause (Plan)

This is the most time-intensive section. Start with a fishbone diagram to organize potential cause categories (method, machine, material, man, measurement, environment). Then drill into the most plausible causes with the five whys technique. The goal is to reach a root cause that, if addressed, would prevent recurrence, not just fix this one instance. Cross-check with root cause analysis principles to confirm you've gone deep enough.

Step 5: Develop countermeasures (Do)

For each confirmed root cause, write a countermeasure: a specific action, who owns it, and when it will be complete. Countermeasures are not solutions yet; they're hypotheses. You'll verify in the follow-up. Tie each countermeasure explicitly to its root cause so the logic is traceable.

Step 6: Build the implementation plan (Do)

Turn the countermeasures into a simple action plan: tasks, owners, and due dates. Include the leading indicators you'll track during rollout. A good implementation plan fits in a six-to-eight-row table on the right side of the A3.

Step 7: Confirm the results (Check + Act)

After countermeasures are in place, measure against the goal you set in Step 3. Did the error rate drop from 4.2% to below 0.5%? If yes, document the lessons learned and consider standardizing the solution. If not, the A3 loops back: refine the root cause analysis and adjust countermeasures. This is the Act phase of PDCA, and it's what separates a completed A3 from an abandoned one.

A3 problem solving example

Here's a condensed A3 for a real-world scenario a mid-sized manufacturing operation might face.

Background. The shipping department is generating a high volume of customer complaints about incorrect items in orders. This affects customer satisfaction scores and creates re-shipment costs. The operations manager and account team are the main stakeholders.

Current state. Order pick accuracy measured at 93.1% over the last 90 days. Target SLA is 99.5%. Each incorrect shipment costs approximately $85 in re-shipment and handling. The error concentrates in the afternoon shift, particularly for orders with more than five line items.

Goal. Reach 99.5% pick accuracy for all orders by end of Q3, reducing re-shipment costs by at least 80%.

Root cause analysis. Five Whys revealed: pickers use a paper pick list that is printed once per shift, so if an order is updated after printing, the picker works from outdated data. The upstream cause is that the warehouse management system doesn't push real-time updates to pickers. The fishbone pointed to the same system gap under "method."

Countermeasures.

• Replace paper pick lists with a tablet-based system that displays real-time order data (IT, due in 6 weeks).
• Add a verification scan at pack station before sealing (Warehouse Supervisor, due in 2 weeks).

Implementation plan. Tablet pilot with four pickers starting week 1; full rollout week 5; pack-station scan live week 2; daily accuracy reporting from week 1.

Follow-up. At week 8, pick accuracy measured at 99.7%, above the 99.5% goal. Re-shipment costs dropped 87%. Lessons learned: paper-based pick processes are a systemic risk when orders change frequently. Standard going forward: all picking operations use real-time digital pick lists.

Common mistakes

Jumping to countermeasures before completing root cause analysis. The most common failure mode. Teams see the problem, know a fix that worked last time, and fill in the countermeasures box before doing the analysis. The result is a superficial fix that doesn't prevent recurrence.

Writing the A3 alone. The A3 is designed to be a coaching conversation between the problem owner and a more experienced lean thinker. Writing it in isolation removes the challenge that sharpens the thinking. Build in at least two review checkpoints: one after the current state and one after root cause.

Setting a vague goal. "Improve the process" is not a goal. Without a specific, measurable target, there's no way to confirm whether the countermeasures worked.

Skipping follow-up. The check and act phases are where the PDCA loop closes. Teams that treat the A3 as done once countermeasures are deployed miss the most important step: verification that the change actually held.

Making it too long. If the A3 exceeds one page, the team hasn't simplified the analysis enough. More pages signal confusion, not thoroughness.

Best practices

Keep the A3 visible during the project. Post it in the work area or share it in a shared document. It becomes the team's shared mental model and a reference point for daily standup conversations.

Use simple visuals over dense text. Current state is better shown with a sketch of the process than described in paragraphs. Root causes land better in a fishbone diagram than a bulleted list. The A3 format was designed for visual communication.

Write in pencil first. The A3 is a living document during the Plan phase. Your understanding of the problem will change as you gather data. Treat early drafts as hypotheses, not finished analysis.

Pair A3 with related quality tools. The affinity diagram helps organize unstructured feedback into themes for the current state. The seven quality tools (check sheets, Pareto charts, control charts, histograms, scatter diagrams, fishbone, and flowcharts) map directly onto different sections of the A3.

Track A3 completion rates over time. Teams that complete follow-up sections consistently build stronger root cause skills than those that stop at countermeasures. Make follow-up a standard agenda item in monthly operations reviews.

Frequently asked questions

What does A3 stand for? A3 refers to the ISO paper size: 297 x 420 mm, or roughly 11 x 17 inches in US dimensions. Toyota chose this size because it was the largest sheet that could be faxed internationally during the era when the format was developed. The constraint was practical, not theoretical, but it turned into a useful discipline.

Is A3 problem solving only for manufacturing? No. The A3 format is used in healthcare (patient safety incidents), software development (bug and system failure analysis), government operations, and service industries. Any team that needs a structured, compact way to communicate a problem and its resolution can use it. The lean manufacturing origin means some vocabulary feels industrial, but the thinking structure is universal.

How is A3 different from a standard root cause analysis? A standard root cause analysis focuses on finding the cause of a problem. An A3 embeds root cause analysis within a broader cycle that includes background context, goal-setting, countermeasure design, implementation planning, and follow-up verification. A3 is the full PDCA loop; root cause analysis is one phase within it.

How long does it take to complete an A3? It depends on problem complexity. A straightforward operational issue with clear data might take two to three days. A cross-functional problem with multiple contributing causes can take two to three weeks of data gathering, analysis, and review cycles. The countermeasure implementation and follow-up measurement add additional time beyond the document itself.

Do you need special software to create an A3? No. A3 reports are commonly created in PowerPoint, Word, Excel, or even drawn by hand on paper. What matters is the thinking structure, not the tool. Some organizations use lean management software with A3 templates, but a blank landscape slide divided into seven sections works just as well.

---

A3 problem solving works because the constraint creates the discipline. When there's no word limit, teams add complexity. When the analysis has to fit on one page, teams are forced to understand what actually matters. Build the habit of completing the follow-up section and you'll find that each A3 sharpens the next one: the root causes you surface become patterns, and the patterns become institutional knowledge about where your processes break and why.