This week, we’re launching a multi-part A3 problem-solving series on the Lean 6 Sigma Hub blog. You’ll get a worked A3 explained box by box, a free copy-and-use template, practical numbers, and coaching questions to help you test your thinking at each stage. The goal is straightforward: help operational managers, improvement leaders and Belt practitioners turn a problem into a clear, evidence-based plan, and keep learning as they put it into action.
What an A3 is, and why the one-page format works
An A3 is a structured problem-solving story laid out on one sheet of paper. The international A3 size is 297 × 420 mm. Its purpose is not simply to make a report shorter. It makes the reasoning visible: what is happening, what should be happening, what is driving the gap, and what the team will do next.
The method is closely associated with Toyota’s approach to making Plan-Do-Check-Act (PDCA) thinking visible. As MIT Sloan Management Review explains, the sequence of sections supports both problem solving and the coaching conversations through which teams build capability.
A common seven-box layout tells the story in order:
- Left side, problem logic: background, current condition, target condition and root-cause analysis.
- Right side, action logic: countermeasures, implementation plan and follow-up.
That structure helps a team connect proposed actions to evidence rather than jumping from a symptom to a preferred solution.
A worked example: distribution-centre pick errors
Consider a distribution centre processing 100,000 order lines per month. Its measured pick error rate is 2.1%, or approximately 2,100 errors a month. Re-picks and freight re-work cost an estimated $214,000 per year.
The team sets a target to reduce pick errors to 0.6% within 90 days. A gemba review, fishbone analysis and 5-Why investigation narrow the verified causes to two conditions: slot mismatches between system locations and physical stock, and ambiguous location labels that make similar products easier to confuse.
Two countermeasures are selected:
- Re-sequence high-frequency slots to better match pick paths and reduce location mismatches: $18,000.
- Redesign location labels for clearer, more distinguishable identification: $4,500.
Together, the planned investment is $22,500. The initial forecast is a 68% reduction in errors, equivalent to a rate of about 0.67%. That would be a substantial improvement, but it would not yet meet the 0.6% target; achieving 0.6% requires a reduction of about 71.4% from baseline. The team should treat that remaining gap as a reason to test, learn and adjust, not to report the target as achieved.
If the forecast 68% reduction is realised, and re-work costs fall in proportion to error volume, estimated annual savings would be $145,520 ($214,000 × 68%). That equates to around $12,127 per month, giving a simple payback of approximately 1.9 months on the $22,500 investment. These are illustrative calculations: the team must validate actual results and cost behaviour before claiming savings.
Your free copy-and-use A3 template
Copy the seven boxes below into a landscape page or your preferred A3 form. Keep the content concise, use charts or sketches where they clarify the story, and update the page as you learn.
| Box | What belongs here | Common failure to watch for | Coaching question |
|---|---|---|---|
| 1. Background | Business or customer context; why this issue matters now. | A broad history with no clear reason to act. | Why is this problem important to the customer or business? |
| 2. Current condition | Observed process, baseline, time period and relevant breakdowns in the data. | A judgement such as “picking is unreliable” instead of a measured fact. | What did you observe, and where is the data? |
| 3. Target condition | A measurable outcome and due date. | A direction such as “improve accuracy” without a number. | What result, by when, and how will you measure it? |
| 4. Root-cause analysis | The logic and evidence connecting the performance gap to confirmed causes. Use tools such as fishbone and 5 Whys. | Treating possible causes as proven, or stopping at a symptom. | What evidence confirms this cause at the workplace? |
| 5. Countermeasures | Actions that address verified causes, with expected effects and risks. | Listing fixes before confirming the causes. | How does each countermeasure address a cause you verified? |
| 6. Implementation plan | Actions, owners, due dates, resources and trial milestones. | A wish list without accountable owners or dates. | Who will do what by when, and what might affect the trial? |
| 7. Follow-up | Outcome measures, review dates, actual results and standardisation or next steps. | Closing the A3 after implementation without checking performance. | How will you know the change worked and stays in place? |
Put the A3 to work as a coaching rhythm
An A3 becomes useful when it is worked, reviewed and revised, not filed away after approval. Start with short coaching conversations: the owner brings the latest evidence, the mentor asks questions, and both agree on the next action, owner and date. The mentor’s role is to develop the problem solver’s reasoning, not to fill in the boxes for them.
Use a daily or weekly visual board to review countermeasure progress and key measures. At 30 days, check whether the process is holding, whether the outcome is moving toward the target, and whether standard work or the control plan needs updating. If results differ from the forecast, record what the data shows and decide the next PDCA cycle.
How A3 connects to Lean Six Sigma, and when to use it
A3 thinking brings familiar tools into one coherent story:
- 5 Whys and fishbone diagrams help structure root-cause investigation; evidence still needs to confirm the cause.
- PDCA supplies the cycle of planning, testing, checking and adjusting.
- Control plans help define how a successful change will be monitored and sustained.
- DMAIC provides a more detailed framework when a project needs deeper measurement, analysis or control.
Use an A3 for a clearly bounded problem where the team can investigate the process, test countermeasures and review results within a practical timeframe. Choose a full DMAIC project when the issue is complex, crosses multiple functions, requires substantial data collection or statistical analysis, carries significant risk, or needs formal phase reviews. An A3 can still communicate the core story within DMAIC; it does not replace analysis the project requires.
For more on the discipline behind problem definition and improvement work, explore our 5W1H Problem Statement Calculator and Lean Six Sigma Project Storyboard Toolkit.
Run your first A3 this month
Choose one observable operational problem, establish a baseline, and work through the seven boxes with the people who do the work. Keep the page live: test, review, update and learn. In the next articles in this series, we’ll continue the box-by-box walkthrough and share practical coaching guidance to help you build the habit.
Join the A3 campaign: copy the free template above, run one A3 this month, and build your problem-solving skill through Lean Six Sigma Hub’s CSSC-accredited, self-paced online training, from White Belt through Master Black Belt. Explore the Green Belt course for practical learning that includes real-world simulations and end-to-end DMAIC case studies.
Kaizen. Kai-Care. Kai-Done. Lean Six Sigma
