A3 Problem Solving

The A3 is named after the paper size (roughly 11x17 inches). It's a structured approach to problem-solving that forces clear thinking by constraining everything to one page.

The constraint is the point. If you can't explain a problem and its solution on one page, you don't understand it well enough.

A typical A3 has sections:

1. Background/Context: Why does this problem matter? What's the business impact?

2. Current Condition: What's happening now? Data, not opinions. Observations, not assumptions.

3. Goal/Target Condition: What should be happening? What does success look like?

4. Root Cause Analysis: Why is the current condition as it is? (More on this in the next lesson.)

5. Countermeasures: What actions will move us from current to target?

6. Action Plan: Who does what, by when? Specific, assigned, dated.

7. Follow-up: How will we know if it worked? When will we check?

The A3 is not just a document—it's a thinking process. Creating an A3 forces you to understand before acting.

Good A3s take time and iteration. They're not created in one sitting.

Start with observation: Go to the Gemba. See what's actually happening. Collect data. Talk to people involved. Don't start writing until you've observed.

Define the problem precisely: "Deploys are slow" isn't precise. "Average deploy time is 4 hours, causing teams to batch changes and increasing lead time by 3 days" is precise.

Use data, not opinions: "The process is broken" is opinion. "47% of items require rework" is data. Numbers ground the discussion.

Get input from others: Show the A3 to people involved. What did you miss? What do they see differently? Iterate based on feedback.

Keep it visual: Diagrams, charts, and maps communicate faster than text. Use visuals to show the problem.

Commit to follow-up: An A3 without follow-up is wish-listing. Schedule the check-in before you implement.

The A3 is typically reviewed with a mentor or manager. This isn't approval-seeking—it's collaborative refinement. The mentor asks questions that sharpen the thinking.

You don't need a formal A3 document to use A3 thinking. The mindset applies to any problem:

Understand before solving: Resist the urge to jump to solutions. Spend time in the current condition. Ask: Do I really understand what's happening?

Quantify the problem: How big is it? How often does it occur? What's the impact? Numbers create clarity and enable before/after comparison.

Seek root causes, not symptoms: If you fix symptoms, the problem returns. Go deeper. (Next lesson covers techniques.)

Propose countermeasures, not solutions: A "solution" implies certainty. A "countermeasure" acknowledges that you're experimenting. You'll check if it worked.

Follow up relentlessly: Set a date to evaluate. Did the countermeasure work? Measure against your target. Adjust or try something else.

A3 thinking can be applied in a team discussion, a Slack thread, or a quick one-on-one. The structure matters more than the format.