HomeFrameworksProblem Solving › A3 Problem Solving
// framework

A3 Problem Solving

Toyota Production System, formalised 1960s–80s

A structured problem-solving document confined to one A3 sheet — the constraint forces clarity, and if you can't fit it on one page, you don't understand the problem well enough yet.

// description

A structured problem-solving and continuous improvement process documented on a single A3-size (11×17 inch) sheet of paper, typically covering: background, current state, goals, root cause analysis, countermeasures, plan, and results.

// history

A3 thinking emerged from Toyota's PDCA-based culture as a way to make problem-solving visible, collaborative, and concise. The A3 paper constraint forces clarity — if you can't fit it on one sheet, you don't understand the problem well enough. John Shook and others brought A3 thinking to Western audiences through the Lean Enterprise Institute in the 2000s. It's now widely used in Lean and agile organisations as a one-page strategic and problem-solving document.

// example

Background: your email open rates have dropped 15% in three months. Current state: 22% open rate, down from 37%. Goal: return to 35% within 60 days. Root cause: subject lines have become generic, list has grown with cold subscribers from a giveaway. Countermeasures: rewrite subject line formula, run a re-engagement sequence, prune cold subscribers. Results: track weekly open rates against target.

// katharyne's take

The genius of A3 is the constraint. One page. That's it. It forces you to actually understand your problem instead of writing a ten-page strategy document no one will read. I use a version of this for any project that involves a real problem worth solving — it's become my default thinking tool for "something is broken, let me figure out why." You can absolutely do this in Notion, but I personally still like paper for the first pass.

// creative uses
// quick actions
// prompt ideas
Help me complete an A3 problem-solving document for this issue in my creator business: [describe the problem]. Guide me through all seven sections — Background, Current State, Goal, Root Cause, Countermeasures, Plan, Results tracking — and keep it concise enough to fit on a single page.
I'm doing a post-launch retrospective using the A3 format. My launch was [describe: product, platform, dates, target]. Here are my results: [paste numbers]. Help me fill in the A3 sections, identify the single most leveraged root cause, and define one specific countermeasure I can implement before the next launch.
Build me a reusable A3 template in plain text that I can paste into Notion for quarterly KDP/Etsy portfolio reviews. Include all seven standard sections with brief prompts inside each one to guide my thinking. Keep the whole thing scannable in under five minutes.
See also: PDCA Cycle · 5 Whys · Fishbone Diagram
← Systems Thinking Appreciative Inquiry →