A3 Problem Solving: One Page to Clarity

The mental model

A3 Problem Solving is a Lean technique for making your thinking visible. It forces you to distill a complex problem, your analysis, and a proposed solution onto a single sheet of A3-sized paper. The goal isn't just the solution, but a transparent thought process that anyone can follow, question, and learn from.

How it works

The process centers on creating an A3 Report, a standardized, one-page document. This report uses words, charts, and diagrams to tell a story. It typically moves from defining the problem and current state, to analyzing the root causes, to defining a target state and proposing countermeasures or actions. By making the entire thought process visible, teams can surface hidden assumptions and get to an agreement on the solution faster. It also creates a powerful coaching tool; if a solution fails, the A3 shows the thinking that led to it, allowing for targeted feedback.

When to use it

A3 shines in situations where you are open to exploring multiple problem-solving options. It's effective for tactical problems, such as investigating how a critical bug was introduced into production. It's also powerful for strategic challenges, like delving into the reasons behind a drop in market share. A3 can even be used for individual coaching, helping an employee analyze a mistake and find a path for improvement without focusing on blame.

When not to use it

Avoid A3 when the solution path is narrow, controlled, or already decided. If there is no room to explore assumptions and alternatives, the A3 process becomes a bureaucratic exercise in documenting a foregone conclusion. Its value is in the collaborative exploration, not in rubber-stamping a decision that has already been made.

One canonical example

An engineering team faces a recurring production outage. Instead of just applying a quick fix, they use an A3. The report outlines the problem (the outage), the current state (logs, metrics, past incidents), and the target state (zero recurrences). Through analysis, perhaps using a fishbone diagram within the A3, they identify the root cause—a misconfigured cache setting. The A3 then proposes countermeasures, like correcting the configuration, adding specific monitoring, and updating deployment checklists. The single page makes the entire diagnostic and planning process clear to all stakeholders.