lean problem solving sheet

An A3 Report is a Toyota-pioneered practice of getting the problem, the analysis, the corrective actions, and the action plan down on a single sheet of large (A3) paper, often with the use of graphics. At Toyota, A3 reports have evolved into a standard method for summarizing problem-solving exercises, status reports, and planning exercises like value-stream mapping.

But it is much more than a sheet a paper with facts and figures. It is a management process  learned through dialogue about concrete problems. It does this by means of a dialogue between a lean manager and a subordinate who learns lean management and leadership as she solves an important problem.

This process of solving problems while creating better employees—A3 analysis—is core to the Toyota management system. An A3 report guides the dialogue and analysis. It identifies the current situation, the nature of the issue, the range of possible counter- measures, the best countermeasure, the means (who will do what when) to put it into practice, and the evidence that the issue has actually been addressed.

The lean leader’s job is to develop people. If the worker hasn’t learned, the teacher hasn’t taught. Training Within Industry Report (Washington, DC: War Manpower Commission, Bureau of Training, 1945).

Effective use of the A3 process can facilitate the shift from a  debate  about who owns what (an authority-focused debate) to a  dialogue  around  what is the right thing to do  (a responsibility-focused conversation). This shift has a radical impact on the way decisions are made. Individuals earn the authority to take action through the manner in which they frame the issue. They form consensus and get decisions made by focusing relentlessly on indisputable facts that they and their peers derive from the gemba.

As a result, A3 management can best be understood as neither “top-down” nor “bottom-up.” The process clarifies responsibility by placing ownership squarely on the shoulders of the author-owner of the A3, the individual whose initials appear in the upper right-hand corner of the paper. This person may not have direct authority over every aspect of the proposal. Yet this owner is clearly identified as the person who has taken or accepted responsibility  to get decisions made and implemented .

Example A3s

The Many Facets of A3

• A standard paper size:  At its most fundamental, “A3” is the international term for a sheet of paper 297 millimeters wide and 420 millimeters long. The closest U.S. paper size is the 11-by-17-inch tabloid sheet. 
• A template:  Many companies and individuals use an A3-sized document pre-printed with the steps needed to conduct lean problem-solving or improvement efforts, with generous white space for “A3 owners” to record their progress. While they refer to this document as a template, an “A3” is not a template.
• A storyboard:  As users record their problem-solving or improvement project’s progress, the A3 becomes a storyboard used to facilitate communication, collaboration, and coordination with other stakeholders affected by the goal the A3 owner is working toward (e.g., solving a problem or improving a  process ). By having all the facts about the effort in one place, logically presented and summarized, the A3 owner is better able to gain buy-in from other stakeholders for recommended process changes. 
• A report:  Once the A3 problem-solving effort concludes, the A3 storyboard serves as a report of the problem-solving or improvement initiative, including the facts and data gathered, hypotheses considered, countermeasures tried, experiment results, corrective actions taken, and the overall thinking of the A3 owner and stakeholders. At Toyota and elsewhere, A3 reports have evolved into a standard method for summarizing problem-solving exercises, status reports, and planning exercises like value-stream mapping.  
• A problem-solving methodology (or process):  Most lean practitioners know “the A3” as a problem-solving process guided by specific steps or questions. The left side of the A3 focuses on various elements of the problem or current condition, and the right on the countermeasures considered, tested, and chosen that resolves the issue or creates a higher standard.
• A management discipline (or process):  At a higher level, lean leaders, managers, and supervisors use “the A3” as a means by which they oversee and guide subordinates while simultaneously helping them develop their  lean thinking and practice  — particularly lean leadership and problem-solving — capabilities. With A3 management, leaders challenge their direct reports to solve a problem. Then, with the A3 report guiding the dialogue and analysis, leaders coach them through the problem-solving process. Importantly, leaders coach by asking questions versus providing answers, ensuring responsibility remains with the subordinate to solve the problem by pursuing facts and building consensus. Through this interaction, subordinates address the issue, allowing them to make progress toward the objective and, in so doing, learn the lean approach to leadership and management and gain problem-solving capability.
• A3 thinking (or analysis):  Most A3 coaches and advanced lean practitioners refer to “the A3” as a thinking process. In this case, the term refers to a systematic approach to resolving problems or improving  work  processes. Someone can follow this systematic approach, regardless of whether they are guided by or record their findings on an A3 document.
• An alignment tool:  Advanced lean organizations that have incorporated lean thinking and practices throughout their operations use “A3s” as part of their  strategy deployment  and execution efforts. In this case, the A3 process ensures a standard approach to managing and  coaching  people, all directed toward solving problems that help achieve corporate objectives.

Additional Resources

How Do I Start My A3?

When asked “where do I start to write my A3,” David Verble responds “don’t start by writing.” His piece, the first in a series about getting started, offers lessons he has learned about the nature of thinking, and a productive way to start the A3 by recognzing it as a thinking process. 

Don’t Present Your A3: Share Your A3

When asked “where do I start to write my A3,” David Verble responds “don’t start by writing.” His piece, the first in a series about getting started, offers lessons he has learned about the nature of thinking, and a productive way to start by recognizing it as a thinking process. 

Related Books

Related Online Courses

Intro to Problem Solving

Problem-solving is critical to every position in every industry. In this course, you will learn to grasp the situation at the gemba (where the work is done) and use all of your senses to understand what is truly happening.

See: Value Stream Mapping

Privacy Overview

Continuous Improvement Toolkit

Effective Tools for Business and Life!

A3 Problem Solving Template

A3 thinking is a logical and structured approach to problem solving adopted by Lean organizations around the world. It can be used for most kinds of problems and in any part of the business. This A3 template uses a four stages model that is based on the PDCA management philosophy. It makes the problem-solving progress visible to the entire team while allowing the lessons to be learned by others.

This template is a Microsoft Excel spreadsheet that you can use and modify to meet your specific requirements. For example, you may expand the implementation or follow-up plans by increasing the number of rows. The template is available in two variations: a user-friendly straightforward version, and a more detailed one that requires providing in-depth information.

A3 Template (32 KB)

A3 Template – Simple (216 KB)

A3 Template – Detailed (340 KB)

Related Templates

Written by:

CIToolkit Content Team

Free Lean Six Sigma Templates

By Kate Eby | June 12, 2017

• Share on Facebook
• Share on LinkedIn

Link copied

Lean Six Sigma combines two methods that streamline business processes in order to reduce waste, improve quality, and increase efficiency and product value. Both approaches originated in the manufacturing industry - Lean by Toyota and Six Sigma by Motorola - but today they are used to improve many processes within an organization, from customer support to administration.    The templates provided here are suitable for Yellow, Green, and Black Belts. You’ll find Six Sigma project templates designed to support the different phases of an improvement process, all of which are free to download. Simply click on the link to download and open a template file, and customize it to suit your needs.

Six Sigma Tools

Six Sigma is a quality measurement that represents 3.4 Defects Per Million Opportunities. That’s a lofty goal for many business processes, but you can use Six Sigma methods to improve quality and performance in varying degrees based on the needs and objectives of a business or project. Six Sigma tools range from statistical charts, illustrative diagrams, and data collection methods to project management and process analyzation worksheets. These tools may not be exclusive to Six Sigma, but they can be applied in specific ways to focus on process improvement. The tools required depend on the project requirements and team roles. Depending on one’s training and experience, a Six Sigma professional may be involved in improvement initiatives at the White, Yellow, Green, or Black Belt level. White Belts generally have supporting roles, while Yellow Belts act as team members, Green Belts collect and analyze data, and Black Belts serve as project leaders.    In the following sections, you’ll find a number of free, downloadable templates that you can use as Six Sigma tools.

Project Management Guide

Your one-stop shop for everything project management

Ready to get more out of your project management efforts? Visit our comprehensive project management guide for tips, best practices, and free resources to manage your work more effectively.

View the guide

Project Charter Template

This Six Sigma Excel template is designed to help you create a project charter that will serve as an agreement between management and your team. A project charter provides an overview of a project including team roles and responsibilities, financial information, goals, and constraints. Creating a detailed project charter will help define your project and its expected outcome, and provide a high-level roadmap to follow.  

Download Project Charter Template

Excel | Word | Smartsheet

Implementation Plan Template

It’s important to refer to previous research and planning to help create an effective action plan. Once you know what actions to take, this implementation plan template helps you organize them by priority, assign ownership, track progress, and update the plan as needed. This is an important Six Sigma tool for taking concrete actions toward achieving measurable objectives.

Download Implementation Plan Template

Excel | Smartsheet

Stakeholder Analysis Template

You can use this template to identify and analyze stakeholders in order to enlist support for a project. The template allows you to closely examine important factors such as issues that may be influencing stakeholders, their vested interest in a project, or the level of influence and support. Understanding the views and expectations of stakeholders can help you anticipate and address issues in advance and move your project toward success.

Download Stakeholder Analysis Template

SWOT Analysis Template

Use this SWOT analysis template for strategic planning and to create dynamic PowerPoint presentations. List the strengths, weaknesses, opportunities, and threats related to an idea, process, or organization, and use this information for strategic analysis. Easily add this PowerPoint slide to any presentation for visual communication with project team members or other stakeholders.  

Download SWOT Analysis Template - PPT

PPT | Smartsheet

Fishbone Diagram Template

A fishbone diagram, also known as a cause and effect diagram or Ishikawa diagram, helps  teams brainstorm the causes of a certain event. Use this Six Sigma tool along with the 5 Whys template to determine root causes. One of the benefits of using a fishbone diagram is the visual layout, which makes it easy to compile and view information, and see the relationships between different elements. 

‌ Download Fishbone Diagram Template - Excel

A3 Template

A3 is an approach to problem solving that grew out of Lean Manufacturing at Toyota. The A3 report condenses project information onto a single page in an easy-to-read, graphical format. This A3 template provides sections for describing background information, current conditions, root cause analysis, target conditions, implementation plan, and follow-up.

‌ Download A3 Template - Excel

5 Whys Template

A 5 Whys worksheet can help you undertake a root cause analysis to determine the sources of defects or performance issues. After defining the problem, you ask five questions to drill down into why the problem is happening, and track the issue back to its root cause. The final step is to determine what action you should take to eliminate that root cause.

Download 5 Whys Template

 Excel  |  Word | PDF   

Project Prioritization Analysis

This template can help you prioritize and select projects based on various factors, such as likeliness to succeed, cost, and how critical a project is to business processes. Once you collect your data, you can also use a Pareto chart to get a visual representation of the results. This Six Sigma project template is a simple tool that can have a big impact on decision making.

‌ Download Project Prioritization Analysis - Excel

SIPOC Diagram Template

SIPOC stands for Suppliers, Inputs, Process, Outputs, and Customers. A SIPOC diagram provides a high-level, visual overview of a business process, which is helpful for identifying and summarizing all of the elements in a process improvement project from start to finish. This Excel template provides five columns to create a simple, easy-to-read diagram. 

‌ Download SIPOC Diagram Template - Excel

Communication Plan Template

A communication plan outlines how and when you will communicate a project to stakeholders. Effective messaging is important for securing buy-in as well as ensuring continued support for the duration of a project. Consistent reporting on project progress and milestones can help keep stakeholders informed and engaged.

Download Communication Plan Template

  Excel | PDF

Voice of Customer (VOC) Six Sigma Template

Use this VOC template to gather information about customer expectations and needs. Gaining insight into customer requirements can inform your improvement process and help ensure a successful end product. This template is designed to help you document the voice of the customer and translate those messages into measurable requirements.

‌ Download Voice of Customer (VOC) Template - Excel

Data Collection Plan Template

During the “measure” phase of DMAIC, you can use a data collection plan template as a framework for describing what type of data to collect, how to gather it, when, and by whom. This spreadsheet template provides columns for entering data sources and locations, operational definitions, what statistical tools to use, and more. You can also edit the template to include any additional information that is relevant for your project.

‌ Download Data Collection Plan Template - Excel

FMEA Template

A Failure Modes and Effects Analysis (FMEA) seeks to prevent possible failures in a design or process. This FMEA template is designed to help you follow a systematic approach to identifying, understanding, and preventing failures. The template includes a section for recording what actions were taken to address each issue, as well as the completion date.

‌ Download FMEA Template - Excel

Control Plan Template

During the “control” phase, an effective plan serves as a guide for monitoring process and sustaining improvements. In this simple spreadsheet template, you can document process control activities to help ensure that quality standards continue to be met. Customize the template as needed to create a control plan for your specific project.

‌ Download Control Plan Template - Excel

Cause and Effect Matrix

A cause and effect matrix allows you to evaluate and quantify the relationships between process inputs and outputs. Use the matrix to prioritize process inputs based on the level of impact each one has on outputs. Once you collect your data in the matrix, you can also represent the results in a Pareto chart.

‌ Download Cause and Effect Matrix - Excel

Pareto Chart Template

Use this template to perform a Pareto analysis of your data to determine the frequency of problems or defects occurring in a process. The template provides a typical Pareto diagram, with a bar chart representing whatever issues you want to analyze, and a line graph showing the cumulative percentage of occurrences.

‌ Download Pareto Chart Template - Excel

Tree Diagram Template

A tree diagram breaks down a central concept, issue, or activity into increasingly smaller components. In Six Sigma, tree diagrams are used for determining root causes, brainstorming ideas related to a central topic, understanding a process from top to bottom, and approaching issues systematically. This is a useful tool for teams at many levels.

‌ Download Tree Diagram Template - Excel

8D Report Template

This template guides you through the 8D (eight disciplines) approach to problem solving and process improvement. The 8D report includes separate sections for each step, from describing the problem and root causes to identifying corrective actions and ways to prevent reoccurrence. This is a systematic way to help organizations attain their Lean Six Sigma goals.

‌ Download 8D Report Template - Excel

Six Sigma Process Map Template

Create a process flow diagram using flowchart symbols to show each step in a Six Sigma process. This provides a visual representation of process flow with a map that is easy to understand and modify. As a Six SIgma tool, you can use this template for analyzing and revising a process, and as a communication tool for stakeholders.

‌ Download Six Sigma Process Map Template - Excel

Check Sheet with Histogram Template

This template combines a weekly check sheet with a histogram for a graphical representation of defects or issues occurring over time. Enter your data on the check sheet, and the template will automatically create the histogram for your analysis. You can also print the check sheet to collect data by hand.

‌ Download Check Sheet with Histogram Template - Excel

Force Field Analysis Template

A force field analysis helps determine what factors are driving or inhibiting efforts to reach a goal. Identifying these forces and rating the strength of each can provide insight on how to maximize the driving forces and reduce inhibiting forces. On the template, list the desired change along with acting forces, then use your analysis to create an action plan.

Download Force Field Analysis Template

  Word  | PDF

How Lean and Six Sigma Work Together

While both Lean and Six Sigma aim to reduce waste, they are distinct methodologies. Six Sigma focuses on reducing defects by limiting variation within a process, while Lean removes unnecessary steps for a more efficient process. Combining these two methodologies can improve business performance by emphasizing both quality improvement and profitability. Learn more about Lean Six Sigma by reading Everything You Need to Know About Lean Six Sigma .   The acronym “DMAIC” represents a key aspect of Lean Six Sigma. DMAIC stands for the five phases of an improvement cycle: Define, Measure, Analyze, Improve, Control. You can use these steps as a roadmap for resolving issues with a Six Sigma approach:  

• Define the project goals or problem to be addressed, internal and external customer requirements, and project boundaries.
• Measure the current performance of the process and describe the process in quantifiable terms.
• Analyze the process and identify the root causes of defects and sources of variation.
• Improve performance by resolving the root causes of issues and eliminating defects.
• Control future process performance by maintaining improvements.

  Another version of this process is DMADV (Define, Measure, Analyze, Design, and Verify). The DMADV framework is typically applied to new products or services, rather than improving an existing process, or when an existing process has been improved but is not meeting a Six Sigma level. The process is similar to DMAIC but focuses on product or process design and how to implement that design effectively.

Discover How Six Sigma Practitioners use Smartsheet Templates for Optimal Results

Empower your people to go above and beyond with a flexible platform designed to match the needs of your team — and adapt as those needs change. 

The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed. 

When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time.  Try Smartsheet for free, today.

Discover why over 90% of Fortune 100 companies trust Smartsheet to get work done.

• MY LCI Login
• LCI Design & LCI Engineering Design Award
• Our Mission & Vision
• Our Strengths
• History of LCI
• How We Serve
• Board of Directors
• LCI Congress 2024
• Lean in Design Forum 2024
• Respect For People
• Communities
• New to Lean
• Learn by Pathway
• For Designers
• For Constructors
• Field Crew Huddle
• Assessments
• Classroom Learning
• Instructor Program
• LCI Publications
• Learning Videos
• Partner Programs
• Simulations
• Certification FAQs
• Certification Practice Quiz
• Designation Directory

• Lean Construction
• Lean Design
• Lean Project Delivery
• What is Lean?
• Founder’s White Papers
• Lean Construction Journal
• LCI Research
• Newsletter Archives
• Past Event Presentations
• Blog & Buzz
• Lean Consultant Members
• Member Directory

A3: Thinking, Reports, Examples & Templates

A3 thinking, an introduction to a3.

In the design and construction industry – as in all industries – complex problems arise daily. Each project contains hundreds of decisions containing thousands of variables, and sorting them out to arrive at the best outcome is critical.

A3 problem solving provides teams with a strategy to effectively and efficiently deal with problems that they encounter and decisions that need to be reached. In true Lean fashion, A3 process improvement brings the entire team into the collaborative problem-solving process and allows teams to embrace out-of-the-box solutions.

What is A3?

An A3 is a one-page report prepared on a single 11 x 17 sheet of paper that adheres to the discipline of PDCA thinking as applied to collaborative problem solving, strategy development or reporting. The A3 includes the background, problem statement, analysis, proposed actions, and the expected results.

The History

A3 thinking was developed by Toyota in the 1940s. Toyota believed that any problem should be capable of being explained and solved using one sheet of paper (an 11 x 17 sheet being the largest sized paper that is capable of being faxed and closest in size to the traditional A3). 

The company also believed that if a problem is too complex to fit onto an A3 report, it should be broken down into smaller bits that would be solved individually. If your problem cannot fit onto an A3, you should reconsider the scope of what you are hoping to accomplish.

Who Uses A3 Strategies?

Today, A3 strategies are deployed across various industries that employ Lean thinking such as:

• Design & Construction
• Manufacturing
• Project Management
• Engineering & Architecture
• Service Industries

LCI’s Meaning of A3

A3 thinking is an extremely useful tool when utilized correctly. By distilling the entirety of a problem on a single sheet of paper, A3 Lean thinking forces team members to collaborate and rationalize through the problem solving process. A3 thinking makes for more effective problem solving and produces written explanations that can then be passed on to senior management. An effectively completed A3 report will also build management’s confidence in the team and its ability to solve problems.

A3 Reporting

A well-written A3 report should show and explain the consideration that went into the counter-measure to the problem listed. Properly executed plans include the input of team members from all across the stakeholder spectrum and should allow members to emerge as leaders in its problem solving. A3 papers can also be referenced later, allowing the lessons learned during the process to be shared with future project teams.

Understanding A3 Thinking

A3 thinking does not provide a solution to the problem your team is facing. Rather, it guides your team’s process to help it reach the best possible countermeasure with the tools it has at its disposal.

An A3 report is to be filled out by one person on the team – the “champion” – who will gather assessments and intel from other members in a collaborative fashion. Bringing all of the knowledge and expertise of the team to bear when solving a problem is the best way to come to a satisfying outcome.

Problem Solving: An A3 Process

A3 thinking allows for many different types of decision-making. But ultimately, all decisions are fundamentally a form of problem solving. For example, A3 thinking can be deployed to guide the team in optimizing decisions during the design phase, or for solving a constructability challenge.

The First Step to A3 Thinking

The first step of the A3 process for problem solving is to correctly identify the problem. From unexpected lead times on materials to communication breakdowns among design teams, “problems” are in no short supply in the design and construction industry. Before engaging in A3, ask yourself the following questions about the problem you are working to solve.

Questions to Facilitate the Process

• What are you trying to address or solve?
• What is the current situation?
• What are clear Conditions of Satisfaction (CoS) I can develop?
• Where can I brainstorm and analyze the 5 whys/root cause ideas?
• What’s a recommendation I can put forth?
• What is my plan to implement the recommendation above (if applicable)?

State plan to check and adjust using the PDCA cycle.

More on the PDCA Cycle

PDCA stands for Plan, Do, Check, Adjust. Explore each element of this acronym for more information about how it supports both the problem solving questions above as well as A3 problem solving as a whole.

Identify an issue in your process and exercise continuous improvement by planning your course of change.

Perform your case study by applying the corrective actions outlined in the “plan” stage in an experimental manner.

Follow the performance of your experiment and measure it to determine whether it is having the desired effect.

If your plan worked, implement the change to the necessary areas of your process. If it did not, determine what you will do differently next time and repeat the cycle.

A3 Reports for Solutions

While A3 reports broadly follow the PDCA cycle, the actual journey of an A3 process is a bit more granular. Let’s analyze the various steps and sections of an A3 report.

Describe the problem, theme, or issue. List out all of the details including the champion’s name, date, and the names of all of the collaborators who will be helping with the report.

Establish the business context & importance. Provide additional information on the problem being addressed.

Current State

Describe what is currently known about the problem. Note potential variables and roadblocks that may stop your team from solving this problem and additional information you hope you acquire.

Future State or Goal

Identify the desired outcome for your experiment. Identify the Conditions of Satisfaction (CoS) for the project.

Analyze the situation and underlying cause.

Recommendation

Provide a recommendation for process improvement that your team can implement for the future.

Create a follow-up/review process.

A3 Examples

A3 thinking is frequently applied in Lean design and Lean construction during all phases of the process for the purposes of making sound decisions. In the example below, A3 thinking is applied to the process of learning Lean design and construction techniques.

A3 Template

The Lean Construction Institute seeks to educate companies all throughout the design and construction industry on Lean practices and methods. Here is our A3 template which you can use to guide your decision-making processes.

A3 Training

The Lean Construction Institute offers A3 training as well as tools , events , education , and networking opportunities for Lean practitioners in design and construction all around the world. Whether you’re a Lean expert or are just learning about Lean for the first time, LCI can provide the tools you need for problem solving and continuous improvement in your business.

Lean Assessments

How strong is your Lean knowledge? Take a Lean assessment to determine your current state so you have a baseline for improvement. Lean assessments are available for individuals, teams, and organizations alike. Whether you’re new to Lean or are an experienced Lean practitioner, Lean assessments are a great way to get started at LCI!

William R. (Bill) Seed, Executive Editor

Executive Editors: Kristin Hill, Katherine Copeland and Christian Pikel

More lean topics.

From 5s to IPD, explore more popular Lean design and construction topics below.

• Consultancy
• Online Courses

SIGN UP TODAY

• Lean , Lean Culture , Lean Training , Lean Wiki , Tools

A Deep Dive into the A3 Problem-Solving Approach

• 11 mins to read
• June 20, 2023
• By Reagan Pannell

In today’s fast-paced and fiercely competitive business world, organisations must find ways to continuously adapt, evolve, and excel. Amidst the myriad methods and techniques for achieving improvements and driving continuous improvement, few have proven as profound and transformative as Toyota’s A3 problem-solving approach. 

A significant driving force behind the company’s rise to global prominence, the A3 process fosters a culture where problems are embraced as opportunities for growth and learning. In this article, we’ll explore the origins and underlying principles of the A3 approach and uncover the secrets to its success in unlocking the power of improvements.

Understanding the A3 Approach

The A3 methodology is an integral part of the Toyota Production System (TPS), a set of principles and practices that have shaped the company’s approach to manufacturing, management, and continuous improvement over the years. Named after the A3 sheet of paper that was historically used to capture the plan, analysis, and follow-up on a single page, the A3 process represents a simple, yet powerful, tool for addressing complex challenges and discovering lasting solutions.

At its core, the A3 approach is rooted in three key elements:

1. Thorough problem analysis: The foundation of the A3 process lies in digging deep to diagnose the true nature and root cause of an issue, rather than jumping to hastily devised fixes that merely address symptoms.

2. Structured documentation: The A3 report serves as both a communication tool and an iterative planning device, with each section building on the previous ones to guide problem solvers through a comprehensive analysis, solution development, and execution process. It’s the foundation of good continuous improvement.

3. Cyclical learning and improvement: Leadership and employees alike are encouraged to commit to hypothesis-driven inquiry, observation, experimentation, and reflection, leading to a culture that actively seeks and leverages opportunities for growth by solving problems.

How to Implement the A3 Process in Your Organisation

The Lean Thinking A3 approach can be distilled into seven essential steps:

1. Identify the problem: 

Clearly articulate and define the issue at hand, avoiding the temptation to jump to solutions or assume important facts to be self-evident..

When identifying the problem, it is important to ensure that all relevant stakeholders in the organisation are consulted. This helps to ensure that the issue is accurately described and understood from multiple perspectives. A thorough problem analysis should also include conducting research into possible causes or root issues, and clearly documenting any observed symptoms of the problem. Additionally, it is essential to identify any major risks associated with not finding a solution and recognise any constraints (both external and internal) that may exist which could limit potential solutions. Lastly, it is important to consider any potential opportunities which may arise from addressing the issue that may have been overlooked at first glance. This is the problem statement part which is a critical component that identifies the difference between the current condition and the target condition.

At this stage, we are not looking at how to solve problems being faced or at the potential solution to solving problems. It’s about developing a good understanding of how the actual results differ from the expected results and providing an in-depth systematic approach to process improvement and developing problem-solving skills.

2. Establish the context and background: 

Provide a high-level overview of the problem, describing the stakeholders involved, relevant data, and the broader organisational context in which the challenge has arisen..

It is important to ensure that all stakeholders are properly considered when identifying any potential solutions as their perspectives can play a vital role in determining an effective solution. All related data should be thoroughly analysed to understand the full scope of potential solutions. This includes resources, costs, timelines, and any legal or regulatory issues that may need to be considered. Additionally, it is important to consider how well-proposed solutions fit within existing organisational policies and procedures as this could impact implementation success. Finally, understanding how proposed solutions would interact with other initiatives or processes currently taking place in the organisation can help inform decisions about whether or not they are viable options. It may include conducting some value stream mapping to dig deeper into the current state.

It is important to fully explore any underlying factors that may be contributing to the issue at hand and ensure in-depth problem analysis. This includes looking deeper into existing systems, structures, and processes related to the problem in order to identify potential areas of improvement or optimisation. Additionally, it is essential to consider any relevant industry trends or external influences that could impact how the problem manifests within the organisation.

When analysing a problem, collecting data from various sources is important to get a more comprehensive understanding of how a particular issue can be addressed. This includes mapping the current process using the VSM, SIPOC, Process Mapping or Flowcharting techniques. Additionally, interviews and surveys can be conducted with stakeholders to gain insights into how they perceive the issue and their perspectives on potential solutions. Lastly, it is important to observe any real-world activities related to the problem to uncover key areas where time, effort, resources, money etc is being wasted. This is the time improvement that may not have been identified otherwise.

GB MASTERCLASS COURSE

Get access to our free gb mastercourse classes, free course previews, fundamentals of lean.

Ready to start your journey into the world of Lean with this free course?

FREE COURSE

Lean Thinking

A Lean focused continious improvement certification course

LSS Yellow Belt

Propel your career forward, tackle complex problems and drive change

LEAN SIX SIGMA GREEN BELT

Get 3-days free access to our green belt course, accelerate your career, 3. set a goal:, now that you have identified the problem and outlined the relevant context, it is time to set a project goal or outcome..

This involves clearly articulating the desired state of affairs and any key deliverables of the proposed solution. Whether it is reducing operational costs, increasing efficiency, improving customer experience, or something else entirely – defining specific objectives with measurable metrics can help ensure that project teams stay focused and remain aligned on their ultimate destination.

At this stage, it is also important to consider how long it will take to reach the desired outcome. Establishing an implementation timeline will help safeguard progress and provide a framework for tracking results along the way. Setting milestones for achieving particular goals at certain points in time can be especially helpful in keeping teams accountable throughout the process. Additionally, having a plan for evaluating success after reaching the end target will allow stakeholders to gain further insights into how effective their approach has been in addressing underlying problems, as well as how well-proposed solutions have fared once implemented.

4. Investigate root causes:

Use a variety of techniques (e.g., the 5 whys, fishbone diagrams, pareto charts) to probe the problem’s underlying causes and avoid settling on proximate reasons..

The process of identifying root causes is essential when using data-driven tools. We always want to find the simplest root cause approach.

One of the most widely used methods for root cause analysis is the ‘5 Whys’ technique. This method involves asking a series of ‘why’ questions to determine the underlying cause of a particular symptom or issue. The goal is to keep asking “Why?” until you reach an answer that can provide insight into how to address the problem and prevent it from occurring in the future.

Another commonly used tool for root cause analysis is the fishbone diagram (also known as Ishikawa diagrams). This approach involves visualising all potential causes which could be causing a symptom or issue in a logical format, allowing users to identify patterns and uncover links between root causes and their respective effects. This technique can be helpful in identifying and focusing on key areas for improvement, as well as helping to identify interdependencies between components within an organisation’s systems.

Finally, Pareto Charts are useful for analysing data collected from surveys, interviews, observations, etc., concerning the severity or frequency of occurrence. This type of chart helps users quickly identify which factors are contributing most significantly towards an issue, allowing them to focus resources towards addressing those areas first and foremost. Additionally, Pareto charts can also be used to prioritise different solutions based on their estimated effectiveness in addressing an issue.

In conclusion, understanding the root cause of an issue through rigorous techniques such as 5 Whys, fishbone diagrams, and Pareto charts provides invaluable insight into how best to address it effectively while preventing it from reoccurring in the future. By leveraging these tools along with other data-led approaches such as process mapping and flowcharting, organisations can ensure that any proposed solutions are well-informed by both qualitative and quantitative data sources as well as ensure they are building consensus across the entire organisation.

5. Countermeasures:

Identify the right countermeasures (corrective actions) to implement that will directly impact the root causes identified..

Brainstorming is a useful tool for identifying potential improvements. It involves coming up with ideas and solutions in an open and collaborative manner, without judgement or criticism. By allowing team members to share their thoughts freely, brainstorming can help uncover innovative solutions that may have otherwise gone unnoticed. Additionally, looking at how waste reduction, flow and pull can be used to improve processes can also provide valuable insights into where improvement opportunities lie.

Brainstorm potential solutions that directly target the root causes and create detailed action plans for implementation, complete with assigned roles, responsibilities, and timelines.

Once the countermeasures are identified, it is important to design an implementation plan and assign roles & responsibilities. This will help ensure that all stakeholders understand their part in the implementation and can work together to achieve the desired outcome. Additionally, it is important to track progress along the way – setting measurable milestones that can be tracked against goals established during the initial problem-solving phase will help keep teams accountable and allow for course corrections if needed.

By utilising A3 Problem Solving Tools such as a template, organisations can easily document and share their analyses with relevant stakeholders throughout each stage of the project. Having detailed record-keeping like this also helps teams stay on target over time while providing insights into how proposed solutions may need to be re-evaluated down the line. This implementation plan provides the entire organisation with a clear project status on a one-page report.

6. Evaluate the results:

Measure the impact of your countermeasures against the problem, using well-defined success criteria, key performance indicators, or other relevant metrics..

Once the countermeasures have been implemented, it is essential to measure and evaluate their success. This can be done by tracking performance against the initial objectives established during the goal phase, as well as establishing key performance indicators to gauge how well the proposed solutions have fared.

Additionally, stakeholders should also consider conducting a post-implementation evaluation in order to assess how successful their approach has been in addressing underlying issues and determining what lessons can be learned from the experience. This will enable teams to identify strengths and weaknesses within their existing processes and make any necessary adjustments going forward. By understanding the outcomes of their improvements, organisations are able to gain valuable insights into how well they’ve succeeded in achieving their goals and ensure continued success moving forward.

Once the countermeasures have been implemented and their success measured, it is important to compare the results against the initial objective. This can be done in a variety of ways, including graphical analysis such as charts, process maps or flow diagrams. Graphical analysis helps to visualise the differences between results achieved before and after the implementation of new measures in a meaningful way. It also provides an increased level of clarity when assessing whether the desired outcomes have been achieved or not.

Process maps can be useful in understanding how changes made during the improvement phase have impacted processes within an organisation. By mapping out existing processes and then comparing them against those following implementation of countermeasures, teams can easily pinpoint where improvements were made and analyse how they led to improved performance overall.

Charts, on the other hand, enable users to quickly identify trends that may have emerged from data collected during the project. For example, if performance metrics are tracked before and after countermeasures are implemented, users can use charts and graphs to more clearly observe any patterns that may indicate an improvement or regression in performance over time – providing further insights into which areas need further attention or adjustment moving forward.

Finally, dashboard views provide an effective means of displaying results at a glance while highlighting any anomalies that might warrant further investigation. Dashboards allow stakeholders to gain access to important information quickly and easily while also helping them keep track of progress towards goals set out during initial problem-solving phases. Additionally, because dashboards support data visualisation capabilities they offer a highly interactive user experience which can help teams understand underlying trends with greater clarity and precision.

7. Standardise and share:

If a countermeasure proves successful, integrate it into the organisation’s standard operating procedures and share it with other teams as a best practice..

Once the countermeasures have been successfully implemented and measured against the initial objectives, these changes need to be integrated into the organisation’s standard operating procedures (SOPs) and shared with other teams as best practices. This will ensure that any improvements made during the problem-solving phase are consistently applied across all teams within the organisation.

In order to ensure that these improvements become part of the organisation’s long-term strategy, process maps should be updated to reflect the new improved way of working. Process maps provide a visual representation of how workflows are structured within an organisation, and by updating them in line with newly-implemented countermeasures, organisations can ensure that their processes continue to remain up-to-date and efficient moving forward. It may also be necessary to build a follow-up plan if not all tasks are fully completed as well as develop a Lean-focused PDCA cycle to ensure long-term effective collaboration on the solutions that were implemented.

Process documentation should also be updated in order to keep track of changes made during problem-solving. By documenting not just the solutions that were proposed but also why they were proposed, teams can gain valuable insights into their decision-making process which they can leverage for similar future problems.

Furthermore, it is important to update key performance indicators (KPIs) to accurately reflect any progress made during problem-solving. By tracking performance against objectives established before and after countermeasures were implemented, organisations will be able to identify any areas that may still need improvement or require further adjustment going forward. Additionally, tracking KPIs over time will help teams understand whether or not their current strategies are leading them towards meeting their goals in a timely manner or if additional measures may need to be taken in order to achieve desired results more quickly.

Finally, organisations should share successful solutions with other teams in order to promote collaboration and knowledge sharing amongst stakeholders throughout different parts of the business. This will allow for ideas generated through one team’s problem-solving efforts to benefit multiple departments – helping foster creativity and innovation while ensuring that everyone is on board with necessary changes being made throughout the organisation. The last step is key to Toyota’s PDCA management system designed for the entire organisation.

By breaking down the problem-solving process into these seven discrete stages, the A3 method offers practitioners a comprehensive, end-to-end framework for tackling complex challenges and driving improvements in any organisation.

• Corporate Training
• Courses for Individuals

Training the team on A3

To get A3 started, everyone in the entire organisation needs to learn how to use this single-sheet or single-page document. This means training people across all parts of the company so that everyone knows how to use the A3 Problem Solving Tool and A3 template. Training will help make sure that everyone follows a structured approach when using A3.

Getting the organisation fully onboard with A3 Problem Solving is not an easy task and will require a dedicated effort to ensure its successful implementation. To this end, it is important to start with specific areas of the business – whether it be operations, finance or marketing – by setting up targeted training sessions for both operational teams and senior managers. This will help everyone understand how and why A3 is used, as well as the potential benefits it can bring to their business.

Once everyone has mastered the basics of working with an A3 template, companies should look to regularly review and evaluate its effectiveness. This could include setting up quarterly reviews or running workshops where teams discuss successes and areas for improvement when using the A3 tool. Doing this will ensure that any issues are identified early on, allowing the team to quickly adjust accordingly.

At Leanscape, we understand that transitioning to A3 Problem Solving can be a daunting task. With our team of specialists, we can provide your teams with the necessary training and coaching to ensure that they are able to adapt quickly and efficiently. Our comprehensive approach to A3 will equip your team with the knowledge and skills needed to successfully use this powerful tool for improving performance in all areas of your business.

We are committed to helping you develop a culture of continuous improvement within your organisation by teaching best practices and providing guidance through every step of the problem-solving process. Through our specialised training programs, we will help your teams learn how to use the A3 template more effectively, as well as how to interpret data visualisations quickly and accurately – enabling them to take action swiftly when required. Our experienced coaches will also share insights from industry experts on how best to integrate countermeasures into standard operating procedures (SOPs) and process maps, keeping up-to-date with industry trends in order to stay ahead of the competition.

By leveraging Leanscape’s expertise in A3 Problem Solving, you can rest assured knowing that your team is in good hands. Our team is dedicated to providing you with the support needed for successful implementation so that you can achieve sustained performance improvements over time.

100% Free Fundamentals of Lean COURSE

Take our free course.

JOIN FOR FREE

Join our Lean Six Sigma Yellow Belt Certification Course

The implementation of A3 Problem Solving provides a comprehensive framework for organisations looking to successfully address complex problems in an efficient and cost-effective manner. By breaking down the problem-solving process into seven distinct stages, users can structure their approach and track the progress of their countermeasures over time.

In order to ensure successful implementation, organisations should dedicate time towards training their teams on how to use the A3 Problem Solving Tool and A3 template. This will give everyone a solid foundation for carrying out future problem-solving activities more effectively, as well as provide insights into the effectiveness of certain countermeasures over time.

Through Leanscape’s specialised training programs, you can ensure that your team is fully equipped with the necessary skills to successfully adopt and incorporate A3 Problem Solving into all areas of your business. Our experienced coaches are committed to helping you develop a culture of continuous improvement within your organisation – providing guidance through every step of the process

Final Thoughts

The A3 approach is an invaluable tool for unlocking the power of improvements within any organisation. By leveraging its structured framework and cyclical learning approach, businesses can remain agile and responsive to ever-changing conditions, allowing them to navigate change more successfully and emerge stronger than ever before. Ultimately, this makes Toyota’s A3 problem-solving process one of the most effective ways to ensure long-term success in today’s fast-paced and competitive market.

Our Newsletter

Reagan pannell.

Reagan Pannell is a highly accomplished professional with 15 years of experience in building lean management programs for corporate companies. With his expertise in strategy execution, he has established himself as a trusted advisor for numerous organisations seeking to improve their operational efficiency.

Our Training Courses

• Lean Six Sigma White Belt Course
• Lean Thinking Business Course
• Lean Six Sigma Yellow Belt Course
• Lean Six Sigma Green Belt Course
• Lean Six Sigma Black Belt Course

Yellow Belt Course

View all courses, recent articles, 5 essential problem-solving strategies every business leader should know, unveiling the secrets of blue ocean strategy for business growth, the difference between strategy and strategic execution, small steps, big gains: the case for incremental improvement, maximising efficiency and profitability: exploring the benefits of lean consultancy, empowering leaders: the imperative for problem-solving training, view all articles, green belt course, other articles, using gr&r to assess measurement system variability, developing the change management mindset, 7 skills that lean managers use to increase productivity, 01 – don’t kill momentum | change management | principles of lean, the vital role of successfully adopting lean in driving operational improvement, how does vuca impact your business, how to get lean six sigma certified in new york, 5 business benefits of lean six sigma, 17 benefits of a lean six sigma certification, principle 11: invest in your lean supply chain | principles of lean, what is sigma in six sigma, and what does it mean for you, what is the johnson transformation.

• | lean , lean thinking , problem solving , toolkit , tools

Related Articles

An alternative to corporate training programs, the quality assurance society: a professional overview, what is the design of experiments tool, the 5 why problem-solving technique | root cause analysis, what is jidoka what does jidoka mean | leanscape, lean six sigma online courses.

FREE COURSE | YELLOW BELT | GREEN BELT | BLACK BELT | MASTERCLASS | WORKSHOPS

Lean Accelerator Progam

A Lean Six Sigma Green Belt Masterclass

LSS Green Belt

The ultimate fast-track for future leadership

LSS Black Belt

Become an expert in change management and complex problem-solving.

Subscribe to Newsletter

Keep up to date to the latest insights, courses, training, webinars and more. Join our newsletter today.

Lean Accelerator Program

Discover the power of problem-solving, 15 min per day | 3-months | only €999 | learn from experts.

• The A3 Report – Part 1: Basics

Why the Shop Floor?

Obviously, that is where the real situation takes place. Only on the shop floor can you observe the real situation. If you use primarily reports and presentations, you will get a filtered opinion on the situation – usually in a way that makes the presenter look good. See also my post Visit the Shop Floor or Your People Will Fool You! – Genchi Genbutsu!

Of course, you could observe the shop floor (or wherever your action happens) and then go back to the computer to add the data. However, while walking back and forth, you are likely to forget details of what you have seen on the way. You may also get distracted. It is also a waste of time walking back and forth repeatedly. Finally, due to the walking distance, you may be inclined to make the document in one go. However, I am a strong believer of iterations and changes to work my way toward an improved (not perfect!) situation. This brings me to my next point:

Why Pencil?

Using pencil has lots of advantages. Most importantly, it makes it easy to change the content by using an eraser. Therefore, there is much less of a mental barrier to change the document. With a pen, you will have the subtle pressure to make it correct in the very first try – which usually does not happen.

Another advantage of the pencil is that it is easy to do. While you can change computer documents, it actually uses a lot of your mental capacity merely to operate the software. Doing a sketch by hand is much easier and faster – and can also easily be done on the shop floor. Yet, if you do an image search for A3 report on Google , almost all are clearly done on a computer 🙁 . For more on the advantages of a pencil, see my last week’s blog post On the Benefits of a Pencil in Lean .

Why One Sheet of Paper?

You are all familiar with stacks of paper. To add more information to a document, you merely add more pages to the stack. This works fine with printouts. However, going through that stack is more cumbersome than having one sheet of paper.

Especially if you are on the shop floor, working with multiple sheets of paper is a pain. Believe me, I have tried. Additionally, if you are working as a small team of two or more people, you can look only at the page that is at the moment on top. If you have only one page, then others can see all the data right away, without asking you to flip to another page.

The idea to fit all information related to one project/problem on one sheet of paper dates back to quality guru Joseph Juran (1904–2008). He was very influential in Japan, possibly even more so than the better known William Edwards Deming (1900–1993). Juran guided Toyota toward using one sheet of paper for problem solving, which then was improved at Toyota to the A3 report.

A0, A1, A2, A3, A4, and so on are part of the ISO 216 standard for paper sizes. All of these paper sizes have the same aspect ratio of \[\frac { 1}{ \sqrt{2}}\] , which means that simply by cutting the page in half you arrive at the next paper size. They were originally developed during the French Revolution, and are now used worldwide – with the exception of the United States, Canada, and Mexico.

In the United States, Canada, the Philippines, and in Chile, the U.S. paper sizes are common. Mexico seems to use both standards. The U.S. system is somewhat less structured compared to the rest-of-world ISO standard. For someone traveling between both worlds, the difference in standards always turns out to be a hassle.

In any case, the most commonly used size in (non-U.S.) offices is the A4 paper size (210 × 297 mm or 8.27 × 11.7 inch), which is similar to the U.S. letter size. Probably over 90% of the paper used in a typical (non-U.S.) office is A4 size.

However, Japanese engineers trying to get an overview of a problem on the shop floor quickly found out that an A4 sheet of paper is simply too small to fit all the information. While it is very practical to use, it just was not big enough to give an overview of the entire problem.

Hence, they doubled the size and used A3 sheets of paper (297 × 420mm or 11.7 × 16.5 inch), which is also still commonly found in most offices. The A3 size is somewhat similar to the U.S. ledger or tabloid size.

Please note that some sources say that A3 was the largest size that fit in a fax machine, although most faxes can do only the smaller A4, and special faxes can do even larger than A3 format. Additionally, the A3 report was developed after World War II, but the first fax was developed only in 1974. In any case, now the page was large enough to fit all the information related to the problem at hand.

The next even larger A2 size (420 × 594 mm or 16.5 × 23.4 inch) could fit even more data. The A2 could easily be used in the office where you placed it on a a table. However, the idea is to bring the sheet along with you on the shop floor. And remember, the shop floor is the only place where you get an unfiltered version of the real situation. See my post Visit the Shop Floor or Your People Will Fool You! – Genchi Genbutsu . While an A3-sized clipboard is manageable, an A2-sized clipboard is just too much to carry around.

Overall, the A3 report is one sheet of A3 paper, written in pencil, that is created on the shop floor! This makes it more likely (but, of course, by no means certain) that you will get a representation of the actual situation and a workable solution to your problem through multiple iterations.

You may have noted that the above does not (yet) talk about what actually goes in the report. Well, for me, the conditions above are quite important. Hence, I focused my first post on A3 reports on these four factors. But fear not, in my next post I will go into more detail on what an A3 report actually contains. In the meantime, go out (preferably on the shop floor with a pencil and a single sheet of A3 paper) and organize your industry!

Series Overview

• The A3 Report – Part 2: Content
• The A3 Report – Part 3: Limitations and Common Mistakes

Roser, Christoph. “ Der A3-Report: Mehr Als Nur Eine Problemlösungsmethode .” Yokoten 5, no. 3 (2016).

8 thoughts on “The A3 Report – Part 1: Basics”

I would like to add some of the disadvantages of using pencil: 1. Your writing might not be easy to read by others 2. Changing a number in an Excel cell does not require special expertise 3. Soft copy documents can easily be shared with other people even in remote locations in order to validate them or obtain additional inputs 4. You can keep historic files of documents which have had many updates enabling you to go back to previous versions 5. The work gathered in a pencil file might not be accessible when you look at the same problem at a later stage so you might have to do it all over again

Hi Cornelio, Your points are valid. I write a bit more about it in the 3rd post in this series, and why I think paper is still better. If the goal is to show your work to many other people, then computer may be better. If your goal is to actually solve the problem, pencil may be better. It all depends on what your boss wants from you.

Hi Christoph,

Have you published the follow up posts regarding A3 and if so where can I find them? Regards Chris

Hi Chris, Number two will be on Tuesday Noon after Easter (29th of March), and number three will be on Tuesday noon a week later (5th of April).

Value Stream Maps start out with pencil and paper as well. Clean rooms however need audio and video and tablet tools. Permissions from HR, supervision or union stewards sre good ideas in any case.

Hi Michael, yes, clean rooms have some different rules (do not do a literal “ chalk circle ” in a clean room 🙂 . And it is always helpful to talk with HR before measuring shop floors. In Germany you often even need permissions.

The A3-sized clipboard is manageable, an A2-sized clipboard is just too much to carry around.

Open the Netflix app on your smartphone and tap on the profile icon on the top right corner. Go to the “Account” section Scroll down and tap on the “Cancel Membership” option. You will be redirected to the “Cancel Plan” page. Tap on the “Finish Cancellation” option

Leave a Comment

Notify me of new posts by email.

The A3 Problem-Solving Template: A Structured Approach for Lean Organizations

Last updated: November 10, 2023

By Alexander Connor

Discover how the A3 problem-solving template can help lean organizations effectively solve problems and improve processes, enabling them to make informed decisions and drive continuous improvement in a world that constantly demands increased quality and reduced costs.

The A3 problem-solving template is a widely adopted tool in lean organizations. This structured approach allows businesses to effectively address various problems and drive continuous improvement. 

By following a logical and structured approach within the four-stage model based on the PDCA (Plan – Do – Check – Adjust) management philosophy. A3 report templates enables the visibility of problem-solving progress and shared learning among teams, improving the decision-making processes used in the organization.

In a time when efficient problem-solving is crucial, it’s important for leaders, coaches, and project teams to have the ability to think critically and make informed decisions that can be reviewed and understood by all parties involved. 

The implementation of A3 management process can notably enhance the quality of decision-making processes, increasing the capability of teams to confront the root causes of diverse difficulties.

Providing a consistent structure to the problem-solving process, the functionality of the A3 report templates has expanded well beyond its original purpose. Industries worldwide, from manufacturing to retail to healthcare, have begun to embrace this tool in their problem-solving initiatives.

What is the A3 Problem-Solving Template?

The A3 problem-solving template is a one-page report format originally developed by Toyota , a company well-known for its lean thinking. The design of the ledger size paper encourages concise communication and collaboration among team members, as it requires the problem definition, root cause analysis, countermeasures, and follow-up plan to fit on a single page.

Here’s a quick rundown of the components of an A3 problem-solving template:

• Background : A brief explanation regarding the importance of the issue, spanning no more than three to four sentences.
• Current State : Describes the current situation, detailing the problematic area that needs to be addressed.
• Future State / Goal : Highlights the objective or desired state that your organization wants to achieve after resolving the issue.
• Analysis : Incorporates root cause identification and root cause analysis, using tools like fishbone diagrams , Pareto charts, or 5 Whys, to identify the underlying concern.
• Recommendations : Suggests countermeasures to tackle the issues identified during the analysis phase. The proposed solution should aim to remove the root cause of the problem.
• Follow-Up : Stresses an action plan for the implementation plan of the recommended solution, allocating responsibilities to team members, and designating a timeline for completion.

Lean organizations leverage the A3 problem-solving template as a tool to improve their problem-solving initiatives. This is done by encouraging rationalization among team members to ensure a systematic and holistic problem-solving process. 

This form of communication and collaboration brings out the best skills in team members and can be applied across various areas within a business, ranging from manufacturing and supply chain to customer service and process improvement.

Benefits and Applications

The A3 problem-solving template offers an array of benefits to lean organizations. It essentially simplifies the complexity of problem-solving and injects an organized approach to an otherwise daunting task. Here are some key benefits that come with the application of the A3 template:

• Promotes clear and concise communication : The A3 template condenses complex problem-solving steps into a single page. This requires teams to communicate the essential elements of the problem, the analysis, their recommendation, and action plan in a clear, simplified manner. This clarity of communication ensures that every team member, regardless of their expertise, is on the same page.
• Encourages root cause analysis : The template frames problem-solving in the context of root cause analysis. It forces teams to not just focus on symptoms or immediate fixes, but encourages them to dive deeper to identify underlying root causes.
• Facilitates data-driven decision-making : Through requiring an analysis of the current state and concern, the A3 template promotes fact-based, data-driven decisions. This results in more effective and sustainable solutions, as decisions are made based on analysed data and not guesses or assumptions.
• Enhances collaboration and feedback : As the template necessitates input at multiple stages, it forges cohesive relationships among team members. It also promotes feedback at each stage of the problem-solving process, ensuring a more refined and effective solution.

The A3 problem-solving template is a universal tool that can be applied across various departments and diverse industries such as manufacturing, healthcare, retail, construction, etc.

A3 Report Templates and Resources

Several A3 templates and resources are available to assist organizations in implementing the A3 problem-solving structure. These templates equip teams with a standardized structure that guides them through the process of problem definition, root cause analysis, countermeasures, and action planning.

In addition to templates, the market offers a myriad of books and training resources on lean and agile methodologies to enhance the understanding and application of the A3 problem-solving structure. 

There are resources available specially designed for all lean organizations, whether they are just starting their lean journey or are well-established lean practitioners, to ensure a smooth transition to adopting the A3 reporting system.

Several online platforms and software providers also offer A3 report templates tailored to business requirements, making it simpler for organizations to adopt this problem-solving tool and providing them with opportunities for continuous improvement and learning.

A3 Problem-Solving

The A3 problem-solving template is an invaluable tool for lean organizations aspiring to boost their capability in problem-solving and stimulating continuous process improvement. 

By utilizing this structured approach, teams can effectively handle diverse challenges, promote collaboration, make data-driven decisions, and effectively bring continuous improvement into their daily operations with the help of A3 report templates and resources.

In a nutshell, the A3 problem-solving template ingrains a problem-solving culture into organizations, empowering teams to excel in their problem-solving skill sets and consistently deliver improved operations. It’s more than a mere problem-solving tool; it’s a mindset shift towards heightened efficiency and efficacy.

Embrace it today, and witness the transformative power of A3 structured problem-solving for your organization. Unlock the potential to navigate challenges and drive continual improvement proactively, helping your organization adapt and thrive in the ever-evolving business environment.

• Recent Posts

• Maximizing Benefits with Enterprise Agile Planning Tools - February 22, 2024
• Exploring the World of Photochemical Reactors - February 19, 2024
• Revolutionizing Industries with Handheld Lidar Scanners - February 8, 2024

Related Posts:

Safety Protocols: Handling and Using Lithium-Ion Batteries in Electric Vehicles

November 1, 2023

Implementing the Age Appropriate Design Code: Protecting Children’s Data Online

January 17, 2024

Join our newsletter for the latest battery technology news & guides

Contact Info

Office Address: 2233 Heritage Road Fresno, CA 93721 Call us: +1 559-767-6498

Copyright 2024 © IonCore Technology. All Rights Reserved.

Privacy Policy

Partners Zone

• A3 Problem-Solving: Thinking & Templates

As a factory manager, you’re already familiar with problem-solving, but how familiar are you with the A3 problem-solving method?

Today, we tell you everything about the A3 problem-solving method and why it can be precisely what you need to get your factory running as smoothly as ever.

Download your A3 problem-solving template

What is A3?

We already stated that the A3 method is a problem-solving method, so let us dig deeper.

A3 refers to the size of the paper you’d normally use to document this problem-solving process.

A3 paper is bigger than your regular A4, measuring roughly 30 by 42 cm in case you were wondering —or if you’re a fan of the imperial system, 11 by 17 inches—

The reason behind using this specific paper size is that it gives you enough space to present all problem-related information clearly and concisely.

This approach is highly structured, following a step-by-step process to help you develop and implement solutions.

What is A3 thinking?

Before the A3 method, we have A3 thinking. This is the heart of this whole problem-solving process.

A3 thinking deals with issues in a structured and logical way, always relying on the principles of continuous improvement. This means you should look at problems from different angles, gathering as much data as possible. Only then you’ll be able to make a truly informed decision.

The key operating principle behind A3 thinking is that the best way to solve a problem is by having an in-depth understanding of the problem and its causes. This is the only way forward to plan, develop, and implement a permanent solution.

How does the A3 problem-solving method work?

Because this is a structured approach to problem-solving, there are a few key steps to follow to implement it right. Let’s take a look:

STEP 1 ― Identify the problem

As with many other problem-solving methods —if not all— the first thing to do is identify the problem that needs solving. 

You can use root cause analysis to make sure you’re tackling the root of the issue and not just fixing the problem at a superficial level.

STEP 2 ― Gather information

Without proper data, your chances of fixing the problem for good are quite slim.

By getting all the information you can through all the sources available —collecting data, conducting surveys, speaking to relevant people involved with the problem— you make sure you have a complete picture of the problem and its magnitude.

This will help you get a comprehensive understanding of the problem, which is key when developing a solution to fix it permanently.

STEP 3 ― Develop a plan

After gathering all the information, you develop a plan to solve the problem.

In this stage, you can hold a brainstorming session, evaluate different options, and select the best approach.

STEP 4 ― Implement the plan

Time to put your plan into action!

A good way to secure success in your problem-solving efforts is to test your solutions before you implement them, adjust anything according to the situation, and monitor your results.

STEP 5 ― Evaluate your results

When you implement your solution, you need to evaluate your results to make sure your plan is working.

The best way to do this is by collecting additional data or analysing production metrics. 

At this stage, you might identify areas for improvement — don’t ignore them, address them.

Advantages of the A3 problem-solving method

Some of the benefits of the A3 method are more obvious than others. Let’s take a look!

Better collaboration — To get the most out of the A3 method, you need to look at your problem from different angles. The best way to do this is by getting several relevant points of view. This improves collaboration and communication across the whole organisation. 

Increased efficiency — Because this approach has a set number of steps, it becomes a predictable process. This means your teams will work more efficiently to solve the issue, as they’ll know what their next steps are. This also means you’ll successfully avoid wasting time or resources on solutions that won’t work.

Improved decision-making — By gathering data and focusing on factual information rather than opinions or gut feelings, you —and your team— will get better at decision-making. This means you’ll leave the guesswork out of your problem-solving process , ensuring your solutions are based on actual, updated data. 

Continuous improvement — This method is a key part of any continuous improvement process. By identifying and solving problems, you can keep improving your operations, products, and services.

How to use an A3 template successfully

To harness the full potential of this method, you can use an A3 template.

A template helps you present information clearly and concisely, making the process way more efficient.

An A3 template typically includes the following sections:

• Background —   Here you write a short overview of the problem. It should include information about when the problem first emerged, how it’s impacting your operations, and what stakeholders are affected
• Current State — In this section, you describe the current state of the problem. This might involve outlining the symptoms, identifying the root cause, and highlighting any contributing factors
• Goal Set — Time to outline your proposed solution to the problem! This might involve identifying specific actions to take, assigning responsibility for those actions, and setting a timeline for completion
• Analysis — Use this section to highlight what problem-solving method you’re using ( the 5 Whys , 8D , A3…) to identify the underlying causes of the problem. This section might also include information about potential solutions
• Suggestions — This is the time and the place to highlight any suggestions for improvement and problem-solving
• Schedule of Touchpoints — Here, you explain which actions are going to happen when, who’s responsible for them, and an estimated completion date.

By using an A3 template, you can ensure a standardised process for problem-solving. This helps everybody work more efficiently.

mlean ® and the A3 problem-solving method

As far as problem-solving methods go, the A3 is quite effective and straightforward.

But we all know paper is hard to keep track of, and big chunks of A3 that are fundamental for your factory’s operations should be stored away safely for future reference.

Our mlean ® Production System (mPS) is the best way to ensure your problem-solving processes are digitally stored, accessible, and readily available when you need them.

Our software creates a knowledge database using the problems you’ve already solved . This makes your operations much more quick and efficient, increasing productivity, boosting continuous improvement processes, and accelerating your growth.

Book a free demo and see for yourself!

Alba Rodriguez

• Industry Trends (28)
• mlean news (21)
• Product (2)
• Standardization (4)
• Strategy (5)

Recent Post

Factories and the environment: How to make it work

The link between continuous improvement and worker satisfaction

Factory performance: how to level up your game

Connect with us

on social media

with any questions

Book a demo

Duis aute irure dolor in reprehenderit in voluptate.

• Privacy Overview
• Strictly Necessary Cookies
• 3rd Party Cookies
• Cookie Policy

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.

Keeping this cookie enabled helps us to improve our website.

Please enable Strictly Necessary Cookies first so that we can save your preferences!

More information about our Cookie Policy

This page uses JavaScript. Please make sure that JavaScript is enabled in your browser.

• kanban library
• pricing & sign up

Thank you! We have sent you an email with details about your accounts.

• Kanban Guide
• Introduction
• History of Kanban
• Agile Framework
• Kanban Fundamentals
• ⬞ Visualize the Workflow
• ⬞ Limit Work in Progress
• ⬞ Manage Flow
• ⬞ Make Policies Explicit
• ⬞ Improve Continuously
• Kanban Elements
• ⬞ Kanban Method
• ⬞ Kanban Card
• ⬞ Kanban Board
• ⬞ Kanban Software
• ⬞ Personal Kanban
• ⬞ Manufacturing
• ⬞ Business Management
• ⬞ Bottlenecks
• Lean Thinking
• ⬞ Lean & Kanban
• ⬞ Just-In-Time (JIT)
• ⬞ Lean Manufacturing
• ⬞ Theory of Constraints (TOC)
• ⬞ Water Spider
• ⬞ Hoshin Kanri
• ⬞ Toyota Kata
• ⬞ Lean Project Management
• ⬞ Lean Accounting
• Lean Methodology
• ⬞ 5S in Lean
• ⬞ Six Sigma
• ⬞ Gemba Walk
• ⬞ Poka-Yoke
• ⬞ The 5 Whys
• ⬞ Flowcharts
• ⬞ Fishbone Diagram
• ⬞ A3 Problem Solving
• ⬞ SIPOC (COPIS)
• ⬞ Design of Experiments
• Lean Metrics
• ⬞ Cumulative Flow
• ⬞ Cycle Time
• ⬞ Lead Time
• ⬞ Process Throughput
• ⬞ Root Cause Analysis
• ⬞ Takt Time
• Kanban Use Cases

What is A3 Problem Solving?

A3 problem solving is a Lean approach to reporting issues and presenting ways of addressing them. The simple method, developed by Toyota, bases on documenting a problem, together with its current outcome and a suggested change, on a single sheet of A3 paper (420x297mm), giving it the name. You can use it to make a process change proposal, report on project status, or solve a problem.

A3 takes from the Plan-Do-Check-Act cycle . Though it appears to be a step-by-step process, the method tends to be used iteratively, with the problem and solution sections being cyclically updated.

Taiichi Ōno of Toyota was known for not appreciating reports longer than one page, which helped the proliferation of the A3 approach within the automotive giant’s offices. A3 is similar to the 8D report also widespread in the automotive industry, though typically for complaints management. Furthermore, the ability to quickly discern a problem and understand its solution is innate to Lean values.

Lean emphasizes visualization, with examples in value stream mapping and Kanban’s visual workflows. That made a single-page report presenting what is going on was a welcome addition to a Lean operation.

Through shared use of A3s to solve all problems and plan initiatives, companies can start to operate an A3 system thinking methodology: address difficulties, suggest change, innovate, and curate logical reasoning rooted in the current needs.

Why use the A3 approach to solving problems?

Lean provides a competitive advantage, strategic and operational benefits through its objective to increase the value delivered to the customer and to reduce waste. Engaging in a process that allows the team to find the correct, best solution in the shortest possible time is highly beneficial.

Understandably, some reports and proposals must contain extensive amounts of data, and they have their place in a business environment. But imagine the value and advantage that distilling this information to 1 page has. Consider how much faster decisions can be made based on that. Besides the time savings, the opportunity to use the systematic approach of PDCA supplements the problem-solving skills required to propose accurate solutions.

In preparing for battle I have always found that plans are useless, but planning is indispensable. Dwight Eisenhower

It’s the act of planning that is important, as it spells out all known obstacles, visualizes the action plan, and helps to foresee potential outcomes and issues along the way. While documenting your problem on an A3 piece of paper may or may not yield benefits, the act of implementing A3 thinking is what makes the difference.

The benefits of using A3 thinking are:

• Quicker problem solving through logical reasoning and application of a step-by-step, visual process. Demanding a root cause identification ensures that difficulties are dealt with, not just temporarily masked.
• Easier planning thanks to the application of objective, critical thinking promoted by the A3’s structure.
• Team development through repeated use of a structural tool to find root causes of problems and their best solutions. The use of one tool across all company levels also promotes cross-department collaboration and knowledge sharing.
• Company growth A3 reports help maintain and keep company knowledge on record, helping to sustain good operating policies and build a strong growth culture rooted in solving a company’s actual problems, not abstract ideas.

How to create an A3 report?

Step 1: The title

It should focus on the problem you are trying to solve and not the solution you want to convey. Examples of titles are: “Decrease Team Misunderstanding of Task Instructions” or “Reduce Customer Complaints with Product XYZ” .

Step 2: Background

According to the authors of “Understanding A3 Thinking: A Critical Component of Toyota’s PDCA Management System” , one of the main strengths of Toyota is that they place importance on understanding a problem. Rather than rush onto a solution, Toyota takes the time to precisely understand what is going on. The principle of going on a Gemba walk attests to this need to perceive problems first-hand.

The report’s background section conveys important related facts and how the problem aligns with the company’s strategic objectives. Presenting this right there on the page helps minimize the cost that a board of highly paid executives would need to spend looking at a problem, without a guarantee of them understanding it, nor coming up with the right solution. Consider this checklist for your background section:

• Do I know the needs of my report’s audience?
• Have I provided enough context?
• Does what it presents align with the audience’s strategic goals?
• Can the background be explained in 30 seconds?

Step 3: Current condition

A correct definition and a good understanding of the problem is your path to finding the right solution. That makes working on defining the current condition 90 % of the A3 effort.

The objective here is to make sure everyone is aware of the problem, whether the report documents it appropriately, and whether anyone questions the report’s findings. The use of graphs, charts, or other visual aids is beneficial.

Step 4: Goal

Your target - if you hit it, you know that your problem-solving effort has been a success. But you need to know what metrics will measure success and what the definition of success is. An example could be “reducing customer complaints by 15%, as measured by call center statistics” .

Step 5: The root cause

The focus of the root cause section should be to differentiate between facts and opinions regarding a problem’s cause and effect. You can include your findings from 5 Whys exercises , an Ishikawa diagram , or any other result of your RCA efforts . If the root cause is not defined correctly, the problem will likely resurface, causing waste and negating the Lean principles.

Step 6: Countermeasures

The countermeasures should be the corrective actions to take for the root cause of the problem to be resolved. If not possible - without a process overhaul - you can use containment actions instead to stop the issue from directly impacting the customer. It is OK to address complex problems iteratively, along with the values of continuous improvement .

The section may include a table of the problem causes, actions taken, action owners, and the achieved results.

Step 7: Effect confirmation

Since the A3 exercise bases on the PDCA cycle, this section of your report should show the effort you expended to confirm your findings. The proof that you have indeed solved the problem. For example, software engineers include samples that replicate the bugs and verify they are no longer present after a fix.

If the exercise has not taken place yet, i.e., when you’re presenting a plan to gain approval, you should outline what exercises you will conduct to check if the aim is successful.

Step 8: Follow up actions

The final section should include any other actions that you might want to consider. A principle worth adhering to here is the “Shitsuke - sustain” step of the 5S plan . Consider what you should do to ensure the benefits of this exercise are maintained. And could they possibly be translated to other areas of the company?

An A3 problem-solving report will help you deliver information in a way that provides instant value and can quickly reduce waste.

The most important thing to remember is that the act of Lean problem solving is more important than creating an A3 document that may contain no valid data and be simply a tick on some corporate checklist.

The same is true of all Lean methods and tools - their application alone will not make your company Lean. To truly implement Lean principles, your company culture, thinking, and planning all have to transform.

Did you know?

A low-risk, tiny step in attempting a culture change in a company could be getting the teams to collaborate on digital Kanban Tool ® boards. Their WIP limits monitoring and process visualization stand a chance to slowly change people’s way of thinking towards more Lean patterns. Please enter valid URL This name is not available Please enter valid email address

Did you like this article?

Anything to change or improve - let us know.

Further reading

• Understanding A3 Thinking: A Critical Component of Toyota’s PDCA Management System (BOOK)
• Kanban Tool
• Pricing & sign up
• Kanban Tool On-Site
• Kanban Library
• Kanban Tool Support
• Integrations
• Developer API
• Terms of service
• Privacy policy

© 2009-2024 Kanban Tool ® by Shore Labs . All rights reserved. | All other trademarks, logos and images mentioned on this site belong to their respective owners. | We use cookies on our website.

Kanban Tool is a visual management solution that helps companies visualize workflow, track project progress, and analyze and significantly improve business processes. Kanban Tool provides powerful online Kanban boards with seamless time tracking and insightful analytics. Our Kanban software works perfectly in any business process and is designed for teams that want to visualize work on a Kanban board .

8D: Tools and Techniques

• Learn Lean Sigma
• 8D Problem Solving

Are you grappling with recurring problems in your organization and searching for a structured way to resolve them once and for all? Look no further than the 8D Problem-Solving Methodology —a comprehensive eight-step approach initially developed in the automotive industry but widely applicable across various sectors.

This systematic method not only aids in diagnosing the root cause of a problem but also offers a roadmap for effective solutions. However, maximizing the potential of the 8D process involves more than just following its steps. It requires the strategic application of specific tools and techniques at each stage. In this educational blog post, we will guide you through the tools and techniques best suited for each of the 8 Disciplines, empowering you to turn challenges into opportunities for improvement. So, let’s delve into this toolkit and make your problem-solving journey as efficient and effective as possible.

Table of Contents

D1: form a team.

The first step in the 8D Problem-Solving Methodology is to form a cross-functional team. A well-assembled team is the backbone of any successful problem-solving initiative. While it may be tempting to rush through this step, investing time and effort here can pay dividends later. Let’s explore some of the key tools that can assist you in forming an effective team.

Suggested Tools:

1. raci matrix.

The RACI Matrix is an invaluable tool for defining roles and responsibilities within the team. The acronym stands for Responsible, Accountable, Consulted, and Informed. By using this matrix, you can clearly specify:

• Responsible : Who is doing the task?
• Accountable : Who is ensuring the task gets completed?
• Consulted : Who needs to provide input?
• Informed : Who needs to know the outcome?

Clear delineation of roles prevents overlap, ensures accountability, and minimizes confusion later in the process.

2. Skills Matrix

Selecting team members with the right set of skills is crucial. A Skills Matrix can help you in this aspect by providing a visual representation of each potential team member’s skills and competencies. You can rate skills on a scale (e.g., 1 to 5) and identify gaps that need to be filled. The matrix can include both technical and soft skills like communication, leadership, and domain expertise.

Key Takeaway:

An effective problem-solving team is not just a group of people; it’s a carefully chosen set of individuals with complementary skills and clearly defined roles. Utilizing tools like the RACI Matrix and Skills Matrix can immensely help in this phase, setting the stage for a successful problem-solving endeavor.

By taking the time to carefully form your team and define everyone’s roles and responsibilities, you lay a strong foundation for the rest of the 8D process. Remember, a well-prepared team is more likely to find sustainable solutions and less likely to encounter roadblocks down the line.

D2: Define the Problem

After assembling a competent team, the next critical step in the 8D Problem-Solving Methodology is defining the problem. A well-defined problem serves as a clear roadmap, guiding your team in the right direction from the start. Ambiguity at this stage can lead to misdirection and wasted resources. So what tools can help you clearly and concisely articulate the problem?

1. 5W2H Method

The 5W2H method is a powerful tool for problem definition. It involves asking a series of questions to gain a comprehensive understanding of the issue at hand. These questions include:

• Who is involved or affected?
• What exactly is the problem?
• When did it occur?
• Where did it occur?
• Why is it a problem?
• How did it happen?
• How much is it affecting?

By systematically answering these questions, you define the problem in a manner that is both comprehensive and easily understandable for everyone involved.

2. SMART Criteria

The SMART criteria focus on setting specific, measurable, achievable, relevant, and time-bound goals for the problem-solving effort. This approach helps ensure that the problem is clearly defined and that the team has a focused, achievable objective to aim for.

• Specific : Clearly define what needs to be achieved.
• Measurable : Set criteria for measuring progress and success.
• Achievable : Ensure the goals are realistic given the resources.
• Relevant : Align the goals with broader organizational objectives.
• Time-bound : Establish a timeline for solving the problem.

Defining the problem is not a mere formality; it is a necessity for effective problem-solving. A well-defined problem ensures that everyone is on the same page and focused on the right issues. Tools like the 5W2H method and SMART criteria offer invaluable frameworks for achieving this clarity. They help dissect the problem into manageable parts, setting the stage for focused root cause analysis.

D3: Contain the Problem

Once you have a team in place and a well-defined problem, the next step in the 8D Problem-Solving Methodology is containment. This stage is often overlooked but is crucial for limiting the damage and preventing the problem from exacerbating. Containment actions are essentially short-term solutions aimed at halting the spread of the issue while you work on finding a permanent fix. Let’s delve into some tools that can guide you in this phase.

1. Check Sheet

A Check Sheet is a simple yet effective tool for collecting and organizing data. It’s often a paper-and-pencil tool that allows for quick data collection in real-time. For example, if the problem is a high rate of defects in a manufacturing line, a Check Sheet could be used to tally the number of defects by type or time of occurrence. This provides valuable insights into the scope and pattern of the problem, aiding in containment.

2. SWIFT Checklist

The SWIFT (Short Window Immediate Fix Technique) Checklist is a tool designed for rapid assessment. It outlines immediate actions that should be taken to contain the issue. The checklist could include questions like:

• Are there safety issues that need immediate attention?
• Can the affected products be quarantined?
• Do stakeholders need to be informed?

By quickly going through the SWIFT Checklist, you can prioritize the most critical containment actions and implement them without delay.

Containment is not just about putting a temporary fix; it’s about preventing the problem from causing further harm or affecting other processes. Tools like the Check Sheet and SWIFT Checklist can be instrumental in quickly assessing the situation and implementing immediate containment actions.

Utilizing these tools allows you to create a rapid response mechanism, thereby minimizing the impact and scope of the problem. As you transition to finding a long-term solution, these containment measures ensure that the situation remains under control.

D4: Root Cause Analysis

Reaching the root cause analysis stage in the 8D Problem-Solving Methodology signifies a pivotal moment. Here, you transition from understanding and containing the problem to actually solving it. Identifying the root cause(s) is fundamental to ensuring that the issue doesn’t recur. While containment measures provide short-term relief, it’s the root cause analysis that offers a long-term solution. Let’s examine some essential tools that can assist in uncovering the underlying issues.

The “ 5 Whys ” is a powerful questioning technique that helps you drill down into the root cause of a problem by asking “Why?” repeatedly. Often, the apparent issue is just a symptom of a deeper problem. The 5 Whys technique encourages you to move beyond the symptoms and discover the underlying cause.

For instance, if the issue is frequent machine breakdowns, asking “Why?” might reveal:

• Why is the machine breaking down? Because of excessive wear and tear.
• Why is there excessive wear and tear? Because maintenance isn’t performed regularly.
• Why isn’t maintenance regular? Because there’s no schedule.
• Why is there no schedule? Because it was never made a priority.
• Why was it never a priority? Because of a lack of awareness about its importance.

2. Pareto Analysis

Pareto Analysis is based on the Pareto Principle, which states that 80% of problems are often due to 20% of causes. By identifying and focusing on these significant causes, you can resolve the majority of issues with minimum effort. Pareto Analysis typically involves collecting data and creating a Pareto Chart to visualize which factors are most impactful.

3. Fishbone Diagram (Ishikawa)

Though also used in problem definition, the Fishbone Diagram is invaluable for root cause analysis as well. It allows you to categorize potential causes and delve deeper into each, often in combination with other tools like the 5 Whys or Pareto Analysis.

Identifying the root cause is not merely a step in the process; it’s the cornerstone for effective corrective action. Tools like the 5 Whys, Pareto Analysis, and Fishbone Diagram provide a structured approach to dig deep into the problem and unearth its roots. Only by understanding the root cause can you implement solutions that are not just quick fixes but long-lasting remedies.

D5: Choose and Verify Corrective Actions

After identifying the root cause of the problem, the next logical step in the 8D Problem-Solving Methodology is to choose and verify corrective actions. It’s crucial to remember that not all solutions are created equal. Some may offer a quick fix but not a long-lasting one, while others could inadvertently introduce new issues. Therefore, this stage involves a delicate balance of selecting an effective solution and ensuring it doesn’t have unintended consequences. Let’s explore some of the tools that can guide you in making informed decisions.

1. FMEA (Failure Mode and Effects Analysis)

FMEA is a structured approach for evaluating the potential failure modes of a proposed solution and their impact. By predicting how things could go wrong, you can proactively address these issues before they occur. The FMEA process involves the identification of failure modes, assessment of their effects, and prioritization based on their severity, occurrence, and detectability. This prioritization helps you focus your resources where they’ll be most effective.

2. Pilot Testing

Before implementing a corrective action on a full scale, it’s prudent to test it on a smaller scale to verify its effectiveness. Pilot testing allows you to:

• Evaluate the impact of the solution without large-scale commitment.
• Identify any adjustments or optimizations needed.
• Collect data to validate the solution’s efficacy.

Pilot tests should be carefully designed to mimic the conditions under which the full-scale implementation will occur. This way, the results are indicative of what you can expect in the broader application.

Choosing a corrective action is a significant milestone, but verifying its effectiveness is equally crucial. Tools like FMEA and Pilot Testing enable you to rigorously evaluate your chosen solutions, mitigating risks and ensuring that the corrective actions will address the root cause without creating new problems.

By diligently applying these tools, you not only select the right corrective action but also build a robust verification mechanism. This two-pronged approach ensures that your solution is not just theoretically sound but practically effective as well.

D6: Implement Corrective Actions

Reaching the implementation phase of the 8D Problem-Solving Methodology is a big step. You’ve formed a team, defined the problem, contained it, identified its root cause, and chosen and verified corrective actions. Now, it’s time to put those actions into play. However, effective implementation is easier said than done. It requires meticulous planning, execution, and monitoring to ensure the corrective actions yield the desired results. Let’s look at some of the tools that can help you master this crucial stage.

1. Gantt Chart

A Gantt Chart is an excellent tool for project planning and tracking. It provides a visual timeline for the tasks involved in implementing the corrective actions. The chart specifies:

• Start and end dates
• Responsible parties
• Dependencies between tasks

This visual representation makes it easier to manage resources and timelines, ensuring that implementation stays on track.

2. PDCA (Plan-Do-Check-Act)

The PDCA cycle is a four-step approach for implementing changes in a controlled manner. Each step serves a specific purpose:

• Plan : Establish the objectives, processes, and metrics for the corrective action.
• Do : Execute the plan on a small scale initially.
• Check : Measure the outcomes against the planned objectives and analyze the results.
• Act : Make adjustments based on the analysis and either scale the implementation or revisit the plan.

By cycling through these steps, you can continually refine your implementation approach, ensuring it aligns with your objectives.

Implementation is the stage where your problem-solving efforts come to fruition, but it’s not a one-and-done deal. Effective implementation requires continuous monitoring and adjustment. Tools like the Gantt Chart and PDCA cycle provide you with the means to implement corrective actions in a structured, controlled, and measurable way.

Remember, a well-planned implementation not only solves the current problem but also equips your organization with the knowledge and experience to tackle future challenges more effectively.

D7: Prevent Recurrence

Successfully implementing corrective actions is an accomplishment, but the 8D Problem-Solving journey doesn’t end there. The next crucial step is to ensure that the problem doesn’t recur. This phase focuses on institutionalizing the improvements you’ve made, ensuring they are sustainable over the long term. It involves both documentation of new best practices and ongoing monitoring. Let’s explore the tools that can help solidify these new standards.

1. Standard Work

Standard Work refers to the documentation of the new best practices that led to the resolution of the problem. These could be new procedures, guidelines, or checklists that need to be followed. Standard Work serves multiple purposes:

• It provides a clear and easy-to-follow guide for team members.
• It ensures that the successful corrective actions are repeated, thereby making the improvements sustainable.
• It serves as a training resource for new employees or for refresher training for existing staff.

2. Control Charts

Control Charts are used to monitor process performance over time. These charts can help you:

• Identify any variations in the process.
• Distinguish between normal variations and those that need attention.
• Trigger corrective actions if the process goes out of the defined control limits.

Regularly updating and reviewing the Control Charts ensures that you catch any deviations before they turn into bigger problems.

Prevention is indeed better than cure. The most effective problem-solving initiatives are those that not only solve the immediate issue but also prevent its recurrence. Tools like Standard Work and Control Charts offer a structured way to document and monitor the improvements, making them a part of your organizational culture.

By diligently using these tools, you not only secure the gains made but also create a proactive environment where potential issues are identified and addressed before they escalate.

D8: Congratulate the Team

The final step in the 8D Problem-Solving Methodology is often the most overlooked but is crucial for long-term success: congratulating the team. After navigating through a complex problem-solving journey, taking a moment to acknowledge and celebrate the hard work is vital. It not only boosts morale but also encourages a culture of continuous improvement. Let’s delve into some tools and practices that can help you effectively close out your problem-solving initiative.

1. Recognition and Rewards

Acknowledging the hard work and dedication of the team is essential for maintaining a motivated and engaged workforce. Recognition can take various forms:

• Public acknowledgment in team meetings or company-wide announcements.
• Certificates or plaques to commemorate the achievement.
• Small rewards or bonuses, where appropriate.

This recognition serves as a reminder that efforts are appreciated, which in turn fosters a positive work environment.

2. Lessons Learned Document

Closing out a problem-solving initiative offers a prime opportunity to capture what worked and what didn’t. A Lessons Learned Document serves this purpose:

• It details the challenges faced, how they were overcome, and any roadblocks encountered.
• It captures best practices for future reference.
• It identifies areas for improvement, offering a starting point for future problem-solving endeavors.

Sharing this document organization-wide can serve as a valuable resource for other teams facing similar challenges.

A job well done indeed deserves recognition, but it also lays the groundwork for future improvements. Tools like Recognition and Rewards and the Lessons Learned Document not only celebrate success but also institutionalize the knowledge gained. This twofold approach not only marks the successful completion of one problem-solving initiative but sets the stage for ongoing improvements and future successes.

By taking the time to celebrate and reflect, you not only acknowledge the efforts made but also capture valuable insights that can guide your organization’s continuous improvement journey.

Successfully navigating the 8D Problem-Solving Methodology is a commendable achievement, but the journey doesn’t end with implementing a solution. Each step, from forming a team to congratulating them, is a building block in your organization’s culture of continuous improvement.

Employing specific tools like RACI Matrix, 5 Whys, FMEA, and Control Charts at different stages ensures that your problem-solving efforts are not just effective but also sustainable. These tools offer more than just a way to tackle issues; they provide a structured approach to learning from them. Remember, the goal isn’t just to solve a single problem but to refine a system that becomes increasingly resilient and efficient over time. So, take a moment to celebrate your achievements, and then gear up for your next challenge, armed with the knowledge and tools that will make your problem-solving journey even more impactful.

• Sharma, M., Sharma, S. and Sahni, S., 2020. Structured Problem Solving: combined approach using 8D and Six Sigma case study.   Engineering Management in Production and Services ,  12 (1), pp.57-69.
• Broday, E.E. and Júnior, P.P.A., 2013. Application of a quality management tool (8D) for solving industrial problems.   Independent Journal of Management & Production ,  4 (2), pp.377-390.
• Engineer, A.T.D., 2016. Managing project using 8D technique.   Management ,  7 (6), p.67œ76.

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Free Lean Six Sigma Templates

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

The Evolution of 8D Problem-Solving: From Basics to Excellence

In a world where efficiency and effectiveness are more than just buzzwords, the need for…

Are you grappling with recurring problems in your organization and searching for a structured way…

How to Select the Right Lean Six Sigma Projects: A Comprehensive Guide

Going on a Lean Six Sigma journey is an invigorating experience filled with opportunities for…

TheLeanSuite

Got a question? Call us at +1-616-433-6688

People and Morale

Suggestions, suggestion platform.

Collect and implement million dollar ideas

Compentency Planning

Track and upscale workforce skills with ease

Learning Management System

Build and deploy on-demand training with ease

Job Cover Matrix

Loss and cost management.

Collect data and compile production loss trees

Quality Management

Prioritize internal and external quality defects

Issue Tracker

Identify, assign and close shop-floor anomalies quickly

Continuous Improvement

Document and manage quick to complex kaizens

Gemba Walker

Make the most out of the shop floor walks

CILR Management

Schedule & plan maintenance activities

Suggestion Management

Issue tracker for quality, issue tracker for operations, issue tracker for safety, suggestions, suggestion system for hr, suggestion system for operations.

• Why TheLeanSuite

FEATURED BLOG POST

PDCA Cycle: What is the Plan-Do-Check-Act Cycle?

• Five Benefits of Continuous Improvement in Manufacturing

The 8 Wastes of Lean: DOWNTIME

• Continuous Improvement vs Process Improvement: the Differences
• The Most Popular Lean Six Sigma Tools and Techniques

DMAIC Process: A Quick Guide for Beginners

• SCHEDULE FREE DEMO

Depending on the complexity of the problem, some tools are more appropriate than others. That is to say, as the complexity of the problem increases, use the relevant tools (described above in the graph) accordingly. 

What are the Four Lean Tools for Simple Problem Solving?

The most basic and first of four lean tools for simple problem solving is 5G. Also known as the 5 Gen Methodology or the 5 Gen principle, 5G is a popular Japanese problem-solving method used for improving various manufacturing activities. That is to say, it is a tool that describes a loss phenomenon that can be related to safety, quality, parts shortage, etc. 5G is made up of five Japanese words that all start with the letter “G”: Gemba, Gembutsu, Genjitsu, Genri, and Gensoku.

The 5G Procedure

5W1H is the second of four lean tools for simple problem solving. Essentially, it helps contribute to the resolution of a problem by answering existing questions and triggering ideas. 

The 5W1H questions are:

• 1. Who — this refers to a specific person or group of people who are relevant to the problem or situation. For example, this can include who identified the problem, who can potentially solve the problem, and who will be responsible for implementing the solution. 
• 2. What — when answering what,  you should describe the situation and problem in detail. If possible, you should also identify the overall goal for implementing the determined solution.
• 3. Where — for the where , state the exact location, area, or position of the identified problem. For example, this can be at a specific pillar or machine. 
• 4. When — the when should include anything related to the problem that has to do with dates. For example, the timeline, deadline, duration, or any other date-related details that can help solve the identified problem.
• 5. Why — this is the most important element of the 5W1H method. The why details the reason and objectives for why action needs to be taken or why there’s a need to use the 5W1H method. Additionally, this last  W  is usually asked five times to discover the root cause of the problem and to prevent it from happening again — this approach is better known as the 5 Whys analysis.
• 6. How — for the how , specify the steps necessary to implement the solution to solve the problem. This includes all the tools, resources, methods, and even expenses needed to carry out the plan.

4M1D, or also known as the 4M1D fishbone diagram, is the third of four lean tools for simple problem solving. In short, this is a fairly universal tool used to identify as many potential causes for a problem as possible. Moreover, it can be used to structure a brainstorming session and immediately sorts significant contributors into useful categories. The major categories of the 4M1D fishbone diagram are material, method, machine, man, and design. However, other “M’s” that may have an impact include management, money, and maintenance. In essence, the 4M1D fishbone diagram can be adjusted based on the needs of the identified problem. 4M1D  is similar to the  5 Ms of Lean Manufacturing .

The 4M1D Procedure

The procedure for conducting the 4M1D fishbone diagram is usually done with pen and paper, or on a whiteboard, and are as follows:

• 1. Identify a specific problem (in as little as 3-5 words) then write it at the centre right of your paper or whiteboard. Draw a box around it and then starting from the left side of the box, draw a horizontal line running across to the centre left of the page.
• 2. Brainstorm and determine the major categories that may have an impact on the identified problem. Then write each category as branches from the main horizontal line running across the paper or whiteboard. 
• 3. Brainstorm and identify all the possible causes for the specified problem and ask, “why does this happen?” As each idea is given, the leader of this analysis writes it as a branch from the relevant category. It is important to note that possible causes can be placed in more than one category. 
• 4. Again, ask “why does this happen?” for each cause that is written down and write down sub-causes that branch off from the main cause. Continue doing this to create a deeper understanding of the causes — the layers of branches represent causal relationships.

The primary goal of the 5 Whys analysis is to find the root cause of a given problem by asking a series of “why” questions five times. However, in some cases, it may take more or fewer whys, depending on the complexity of the root cause.

The 5 Whys analysis is the final of four lean tools for simple problem solving and it is one of the most powerful assessment tool of all non-statistical analyses. In short, by using this analysis, you’ll be able to identify the root cause of the problem and understand the underlying cause and effect of the identified problem. 

The 5 Whys Procedure

Listed below are the steps you should follow to complete the 5 Whys analysis:

• 1. Start by identifying a specific problem — what is it that you are having difficulties with? Jot this down somewhere. For example, on a piece of paper.
• 2. Ask why this problem has occurred and write the answer below the identified problem.
• 3. Continuously ask “why” to each of the successive answers you write down until you arrive at and determine the root cause of the problem.

To reiterate, again, the 5 Whys analysis may take more or fewer than 5 whys to determine the root cause. Additionally, it is important to ensure that all team members collaborating on the 5 Whys analysis agree with each of the questions being answers, as well as the root cause of the problem.

Share this:

Related blogs.

The Plan-Do-Check-Act (PDCA) cycle is a timeless and iterative management

In the search for operational excellence, businesses are continually refining

The DMAIC process stands out as a powerful tool for

360 Degree view of Lean Program

Ready to Digitze your Lean Manufacturing Journey?

Fill out the form and an advisor will reach out to you at the earliest..

Invalid value

Discover more from TheLeanSuite

Subscribe now to keep reading and get access to the full archive.

Type your email…

Continue reading