Lean A3 Charter

Solve a problem on a single page. The Lean A3 charter walks a team from background and current condition through root-cause analysis to countermeasures and confirmed results, keeping the whole problem-solving story visible at a glance.

Create A3 Charter →

What is a Lean A3 Charter?

The A3 charter, or A3 report, is a structured one-page problem-solving document from the Toyota Production System, named for the A3 paper size it traditionally fits on. It captures the entire logic of a problem, from background to confirmed results, in a compact, visual format that anyone can follow.

The A3 follows a Plan-Do-Check-Act logic. It states the background and current condition (with data), sets a target condition, analyzes root causes (often with a 5-Why summary), proposes countermeasures with owners and due dates, lays out an implementation plan, and, critically, confirms the effect after the countermeasures are applied.

Its discipline comes from fitting everything on one page. This constraint forces clarity and a coherent story, telling of the problem-solving over a full analytical charter, and makes the A3 both a working document and a communication tool that keeps the team aligned on the same narrative.

In plain terms: An A3 is the whole problem, and its solution, on one page: here's the situation and the data, here's the target, here's why it's happening (5-Why), here's what we'll do about it, and here's proof it worked. The one-page limit forces you to think clearly and tell a coherent story.

The A3 Story

Background & Current Condition

Why this matters, and the current state with data, for example 17% of invoices require manual correction adding 1.6 days to close.

Target & Root Cause

The target condition (a measurable improvement) and a root-cause analysis, often a 5-Why summary of the underlying causes.

Countermeasures & Confirmation

Countermeasures with owners and due dates, an implementation plan, and effect confirmation with a tracked metric and review date.

Key Formulas

Logic: Plan → Do → Check → Act on one page
Current condition: stated with data (the baseline)
Target: from <current> to <target> within <time>
Root cause: 5-Why summary
Confirm: tracked metric + review date

What Makes an A3 Effective

The current condition and target must be quantified: an A3 that says rework is high and we want it lower is not an A3. A strong example states 17 percent rework now, 5 percent within eight weeks, so progress is measurable.

The effect confirmation step is what distinguishes an A3 from a plan. By committing to a tracked metric and a review date, the A3 closes the loop, checking whether the countermeasures actually moved the metric, and prompting follow-up if they did not.

Assumptions & Validation

Quantified Current State

The current condition is described with data.

If violated: Add the baseline numbers; without them the target is meaningless.

Genuine Root Cause

Countermeasures address root causes, not symptoms.

If violated: Deepen the 5-Why analysis until the true cause is reached.

Owned Countermeasures

Each countermeasure has an owner and due date.

If violated: Assign ownership and dates to every action.

Effect Confirmation

A tracked metric and review date are set to confirm results.

If violated: Define how and when the effect will be checked.

⚠️ Check assumptions first

The most common A3 failure is stopping at countermeasures without confirming their effect, which turns a problem-solving report into a to-do list. The A3's discipline is the check step: a tracked metric and a review date that verify whether the countermeasures actually improved the current condition. An A3 without quantified current and target conditions, or without effect confirmation, is missing the point of the format.

When NOT to Use Lean A3 Charter

Large Complex Projects

For a project too big for one page, a full DMAIC charter provides the needed structure and depth.

Designing Something New

For designing a new process or product, a DMADV charter with CTQs and verification fits better.

Formal Statistical Study

For a hypothesis-driven experiment, a Research charter captures variables and success criteria.

Industry Applications

Process Problem Solving

Work a focused operational problem, such as invoice rework or defects, from cause to confirmed fix.

Kaizen Documentation

Capture the story of a Kaizen improvement on a single, shareable page.

Root-Cause Communication

Communicate a problem, its causes and the countermeasures to stakeholders at a glance.

Continuous Improvement

Standardize how teams frame, solve and confirm everyday improvements.

Frequently Asked Questions

What is an A3 report or A3 charter?

An A3 report is a structured one-page problem-solving document originating in the Toyota Production System, named for the A3 paper size it fits on. It captures the full logic of a problem, background, current condition, target, root-cause analysis, countermeasures and confirmed results, in a compact visual format. Its one-page constraint forces clarity and a coherent story, making it both a working tool and a communication device.

What sections does an A3 charter contain?

A typical A3 contains the background, the current condition described with data, a target condition, a root-cause analysis such as a 5-Why summary, countermeasures with owners and due dates, an implementation plan, and an effect-confirmation section with a tracked metric and review date. Together these follow a Plan-Do-Check-Act logic from understanding the problem through to verifying the solution.

Why is the A3 limited to one page?

The one-page constraint is deliberate. It forces the author to distill the problem, its causes and the countermeasures into a clear, coherent story rather than a sprawling document, which improves both thinking and communication. Fitting everything on a single page also makes the A3 easy to share and discuss, keeping everyone aligned on the same narrative of the problem and its solution.

When should I use an A3 instead of a DMAIC charter?

Use an A3 for focused, relatively contained problems where a one-page root-cause-and-countermeasure format is enough, and speed and clarity matter. Use a full DMAIC charter for larger projects that need more structure, extensive data collection or statistical analysis than a single page can hold. The A3 favors lean, visual problem solving; DMAIC favors depth and rigor for complex problems.

What is the effect confirmation step?

Effect confirmation is the check step of the A3, where the team verifies whether the countermeasures actually improved the current condition. It specifies a tracked metric and a review date, so that after implementation the results are measured against the target rather than assumed. This step distinguishes an A3 from a simple action plan, closing the loop and prompting further action if the target was not met.

How does the 5-Why fit into an A3?

The 5-Why is a common root-cause technique used in the analysis section of an A3. By repeatedly asking why a problem occurs, it traces a symptom back to its underlying causes, so the countermeasures address the real source rather than the surface issue. The A3 typically summarizes the 5-Why findings concisely, since the whole report must fit on one page.

Solve a Problem on One Page

Build a Lean A3 from background through to confirmed results. Free during Beta.

Create A3 Charter →