practical problem solving a3

• A Step-by-Step Guide to A3 Problem Solving Methodology

• Learn Lean Sigma
• Problem Solving

Problem-solving is an important component of any business or organization. It entails identifying, analyzing, and resolving problems in order to improve processes, drive results, and foster a culture of continuous improvement. A3 Problem solving is one of the most effective problem-solving methodologies.

A3 Problem solving is a structured and systematic approach to problem-solving that originated with the lean manufacturing methodology. It visualizes the problem-solving process using a one-page document known as an A3 report. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner.

A3 Problem Solving has numerous advantages, including improved communication, better decision-making, increased efficiency, and reduced waste. It is a powerful tool for businesses of all sizes and industries, and it is especially useful for solving complex and multi-faceted problems.

In this blog post, we will walk you through the A3 Problem Solving methodology step by step. Whether you are new to A3 Problem Solving or simply want to improve your skills, this guide will help you understand and apply the process in your workplace.

Table of Contents

What is a3 problem solving.

A3 Problem Solving is a structured and systematic approach to problem-solving that makes use of a one-page document called an A3 report to visually represent the process. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner. The method was created within the framework of the Lean manufacturing methodology and is based on the principles of continuous improvement and visual management.

Looking for a A3 Problem solving template? Click here

Origin and History of A3 Problem Solving

A3 Problem Solving was developed by Toyota Motor Corporation and was first used in the manufacture of automobiles. The term “A3” refers to the size of the paper used to create the report, which is an ISO standard known as “A3”. The goal of the A3 report is to provide a visual representation of the problem-solving process that all members of the organisation can easily understand and share. A3 Problem Solving has been adopted by organisations in a variety of industries over the years, and it has become a widely used and recognised method for problem-solving.

Key Principles of A3 Problem Solving

The following are the key principles of A3 Problem Solving:

• Define the problem clearly and concisely
• Gather and analyze data to gain a deep understanding of the problem
• Identify the root causes of the problem
• Develop and implement effective solutions
• Evaluate results and continuously improve

These principles serve as the foundation of the A3 Problem Solving methodology and are intended to assist organisations in continuously improving and achieving their objectives. Organizations can effectively solve problems, identify areas for improvement, and drive results by adhering to these principles.

Step 1: Define the Problem

Importance of clearly defining the problem.

The first step in the A3 Problem Solving process is critical because it lays the groundwork for the remaining steps. To define the problem clearly and accurately, you must first understand the problem and identify the underlying root cause. This step is critical because if the problem is not correctly defined, the rest of the process will be based on incorrect information, and the solution developed may not address the issue effectively.

The significance of defining the problem clearly cannot be overstated. It aids in the collection and analysis of relevant data, which is critical for developing effective solutions. When the problem is clearly defined, the data gathered is more relevant and targeted, resulting in a more comprehensive understanding of the issue. This will enable the development of solutions that are more likely to be effective because they are founded on a thorough and accurate understanding of the problem.

However, if the problem is not clearly defined, the data gathered may be irrelevant or incorrect, resulting in incorrect conclusions and ineffective solutions. Furthermore, the process of collecting and analysing data can become time-consuming and inefficient, resulting in resource waste. Furthermore, if the problem is not accurately defined, the solutions developed may fail to address the root cause of the problem, resulting in ongoing issues and a lack of improvement.

Techniques for Defining the Problem

The first step in the A3 Problem Solving process is to clearly and accurately define the problem. This is an important step because a clearly defined problem will help to ensure that the appropriate data is collected and solutions are developed. If the problem is not clearly defined, incorrect data may be collected, solutions that do not address the root cause of the problem, and time and resources may be wasted.

A problem can be defined using a variety of techniques, including brainstorming , root cause analysis , process mapping , and Ishikawa diagrams . Each of these techniques has its own advantages and disadvantages and can be used in a variety of situations depending on the nature of the problem.

Best Practice for Defining the Problem

In addition to brainstorming, root cause analysis, process mapping, and Ishikawa diagram s, best practices should be followed when defining a problem in A3 Problem Solving. Among these best practices are:

• Define the issue in a specific and quantifiable way: It is critical to be specific and concise when defining the problem, as well as to quantify the problem in terms of its impact. This will help to ensure that all stakeholders understand the problem and that data collection is focused on the right areas.
• Focus on the problem’s root cause: The A3 Problem Solving methodology is intended to assist organisations in identifying and addressing the root cause of a problem, rather than just the symptoms. Organizations can ensure that their solutions are effective and long-lasting by focusing on the root cause of the problem.
• Ascertain that all stakeholders agree on the problem’s definition: All stakeholders must agree on the definition of the problem for the A3 Problem Solving process to be effective. This ensures that everyone is working towards the same goal and that the solutions developed are relevant and appropriate.
• Consider the problem’s impact on the organisation and its stakeholders: It is critical to consider the impact of the problem on the organisation and its stakeholders when defining it. This will assist in ensuring that the appropriate data is gathered and that the solutions developed are relevant and appropriate.

Organizations can ensure that their problem is defined in a way that allows for effective data collection, analysis, and solution development by following these best practices. This will aid in the development of appropriate solutions and the effective resolution of the problem, resulting in improvements in the organization’s processes and outcomes.

Step 2: Gather Data

Gathering data in a3 problem solving.

Data collection is an important step in the A3 Problem Solving process because it allows organisations to gain a thorough understanding of the problem they are attempting to solve. This step entails gathering pertinent information about the problem, such as data on its origin, impact, and any related factors. This information is then used to help identify root causes and develop effective solutions.

One of the most important advantages of data collection in A3 Problem Solving is that it allows organisations to identify patterns and trends in data, which can be useful in determining the root cause of the problem. This information can then be used to create effective solutions that address the problem’s root cause rather than just its symptoms.

In A3 Problem Solving, data collection is a collaborative effort involving all stakeholders, including those directly impacted by the problem and those with relevant expertise or experience. Stakeholders can ensure that all relevant information is collected and that the data is accurate and complete by working together.

Overall, data collection is an important step in the A3 Problem Solving process because it serves as the foundation for effective problem-solving. Organizations can gain a deep understanding of the problem they are attempting to solve and develop effective solutions that address its root cause by collecting and analysing relevant data.

Data Collection Methods

In A3 Problem Solving, several data collection methods are available, including:

• Observations
• Process diagrams

The best data collection method will be determined by the problem being solved and the type of data required. To gain a complete understanding of the problem, it is critical to use multiple data collection methods.

Tools for Data Analysis and Visualization

Once the data has been collected, it must be analysed and visualised in order to gain insights into the problem. This process can be aided by the following tools:

• Excel Spreadsheets
• Flow diagrams
• Pareto diagrams
• Scatter Plots
• Control diagrams

These tools can assist in organising data and making it easier to understand. They can also be used to generate visual representations of data, such as graphs and charts, to communicate the findings to others.

Finally, the data collection and analysis step is an important part of the A3 Problem Solving process. Organizations can gain a better understanding of the problem and develop effective solutions by collecting and analysing relevant data.

Step 3: Identify Root Causes

Identifying the root causes of the problem is the third step in the A3 Problem Solving process. This step is critical because it assists organisations in understanding the root causes of a problem rather than just its symptoms. Once the underlying cause of the problem is identified, it can be addressed more effectively, leading to more long-term solutions.

Overview of the Root Cause Analysis Process

The process of determining the underlying causes of a problem is known as root cause analysis. This process can assist organisations in determining why a problem is occurring and what can be done to prevent it from recurring in the future. The goal of root cause analysis is to identify the underlying cause of a problem rather than just its symptoms, allowing it to be addressed more effectively.

To understand Root cause analysis in more detail check out RCA in our Lean Six Sigma Yellow Belt Course Root Cause Analysis section

Techniques for Identifying Root Causes

There are several techniques for determining the root causes of a problem, including:

• Brainstorming
• Ishikawa diagrams (also known as fishbone diagrams)
• Root Cause Tree Analysis

These methods can be used to investigate the issue in-depth and identify potential root causes. Organizations can gain a deeper understanding of the problem and identify the underlying causes that must be addressed by using these techniques.

Best Practices for Conducting Root Cause Analysis

It is critical to follow these best practices when conducting root cause analysis in A3 Problem Solving:

• Make certain that all stakeholders participate in the root cause analysis process.
• Concentrate on determining the root cause of the problem rather than just its symptoms.
• Take into account all potential root causes, not just the most obvious ones.
• To identify root causes, use a systematic approach, such as the 5 Whys or root cause tree analysis.

Organizations can ensure that root cause analysis is carried out effectively and that the root cause of the problem is identified by adhering to these best practises. This will aid in the development of appropriate solutions and the effective resolution of the problem.

Step 4: Develop Solutions

Developing solutions is the fourth step in the A3 Problem Solving process. This entails generating ideas and options for dealing with the problem, followed by selecting the best solution. The goal is to develop a solution that addresses the root cause of the problem and prevents it from recurring.

Solution Development in A3 Problem Solving

A3 solution development Problem solving is an iterative process in which options are generated and evaluated. The data gathered in the previous steps, as well as the insights and understanding gained from the root cause analysis, guide this process. The solution should be based on a thorough understanding of the problem and address the underlying cause.

Techniques for Developing Solutions

There are several techniques that can be used to develop solutions in A3 Problem Solving, including:

• Brainwriting
• Solution matrix
• Multi voting
• Force field analysis

These techniques can help to generate a range of options and to select the best solution.

Best Practice for Developing Solutions

It is critical to follow the following best practices when developing solutions in A3 Problem Solving:

• Participate in the solution development process with all stakeholders.
• Make certain that the solution addresses the underlying cause of the problem.
• Make certain that the solution is feasible and achievable.
• Consider the solution’s impact on the organisation and its stakeholders.

Organizations can ensure that the solutions they develop are effective and sustainable by adhering to these best practises. This will help to ensure that the problem is addressed effectively and that it does not reoccur.

Step 5: Implement Solutions

The final and most important step in the A3 Problem Solving methodology is solution implementation. This is the stage at which the identified and developed solutions are put into action to address the problem. This step’s goal is to ensure that the solutions are effective, efficient, and long-lasting.

The implementation Process

The implementation process entails putting the solutions developed in the previous step into action. This could include changes to processes, procedures, and systems, as well as employee training and education. To ensure that the solutions are effective, the implementation process should be well-planned and meticulously executed.

Techniques for Implementing Solutions

A3 Problem Solving solutions can be implemented using a variety of techniques, including:

• Piloting the solution on a small scale before broadening its application
• Participating in the implementation process with all relevant stakeholders
• ensuring that the solution is in line with the goals and objectives of the organisation
• Monitoring the solution to determine its effectiveness and make any necessary changes

Best Practice for Implementing Solutions

It is critical to follow these best practices when implementing solutions in A3 Problem Solving:

Make certain that all relevant stakeholders are involved and supportive of the solution. Have a clear implementation plan that outlines the steps, timeline, and resources required. Continuously monitor and evaluate the solution to determine its efficacy and make any necessary changes. Encourage all stakeholders to communicate and collaborate openly. Organizations can ensure that solutions are effectively implemented and problems are effectively addressed by adhering to these best practices. The ultimate goal is to find a long-term solution to the problem and improve the organization’s overall performance.

In conclusion, A3 Problem Solving is a comprehensive and structured methodology for problem-solving that can be applied in various industries and organisations. The A3 Problem Solving process’s five steps – Define the Problem, Gather Data, Identify Root Causes, Develop Solutions, and Implement Solutions – provide a road map for effectively addressing problems and making long-term improvements.

Organizations can improve their problem-solving skills and achieve better results by following the key principles, techniques, and best practices outlined in this guide. As a result, both the organisation and its stakeholders will benefit from increased efficiency, effectiveness, and satisfaction. So, whether you’re an experienced problem solver or just getting started, consider incorporating the A3 Problem Solving methodology into your work and start reaping the benefits right away.

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.

Visual Management

Standard Work Instructions

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…

8D: Tools and Techniques

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…

• 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, poka yoke: the lean concept of mistake proofing, what are some of the benefits of using benchmarking in lean six sigma, data distributions explained | what are the different types of distribution, 90-day facility management turnaround with 27% lift in performance, unlocking the power of the balanced scorecard: maximizing efficiency and driving growth, how “timwoods” and the 8 wastes of lean drive efficiencies in business process, what makes the best lean six sigma certification program, what are the benefits of cpd for lean certifications, facilitation skills for project managers: learning to lead change management, the assessment criteria for solutions, what is the difference between lean & six sigma, principle 4: create balance | heijunka | principles of lean.

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

Related Articles

Dpmo: defects per million opportunities explained, using the probability plot | probability distribution tool, the analysis of variance (anova) explained, what is a priortisation matrix, a comprehensive guide to integrating hoshin kanri into strategic planning, 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.

Toyota Practical Problem Solving (PPS)—Introduction

The Framework: PDCA

• Plan is to identify and clarify the problem, including collecting data to understand the problem, setting a target, and doing a root-cause analysis.
• Do is the development and implementation of countermeasures.
• Check verifies whether these countermeasures were effective and the target has been reached.
• Act is to re-do and further improve if the targets have not been met (yet). If it was successful, the Act part looks for other locations and applications where this solution could be used (e.g., if it was a smaller trial to be rolled out on a larger scale). Toyota also shares these yokoten on an internal website with other plants.

Toyota practical problem solving consists of the steps as listed below. Note that sometimes you have a step more if you decide to split a step into two.

• Clarify the Problem
• Break Down the Problem
• Set a Target
• Root-Cause Analysis
• Develop Countermeasures and Implement
• Monitor Process and Results
• Standardize and Share

I will explain all these steps in much more detail, including the risks and difficulties, throughout this small series of posts. But before explaining these steps in detail, let me also show you the structure.

The Structure: A3

You probably know the structure already, or at least have heard of it: it is the famous A3 . This report, named after the standard A3 paper size, is commonly used at Toyota to tackle medium-sized problems. The A3 format was chosen because it was a good compromise between getting lots of data on a single page and also having a page small enough to be carried around on the shop floor. (And, as legend has it, A3 was supposedly the largest format to fit though a fax machine back in the day).

You will find all the steps from above again in this A3 format, an example of which is shown below, plus the obligatory header row with organizational data like title, date, and so on.

The A3 is intended to be filled out in pencil (not pen), which makes changing content easy by using an eraser. Nowadays digital tools are also often used, although Toyota still does this mostly by hand using pencil on paper. Digital A3s are easier to share and look prettier, but they are harder to make and much more effort is needed in creating the A3. If you have ever created an A3 in Microsoft Excel, you know what I am talking about (as Excel is wholly unsuited for such graphical work…Ugh!)

The “Do” part is actually quite small. If you understand the problem well, the solutions are rather easy. If you don’t understand the problem, you still may have a solution, but it will probably be an inferior one, if it works at all. Similarly, the Check and Act are also rather small.

In my experience, this is often done differently (and in my opinion worse) in many other Western companies. The focus is all on doing something, implementing some sort of solution. There is a bit of planning, but the vast majority of the effort goes into the “Do” part. The “Check” and “Act” parts are quite underdeveloped, if they exist at all.

A fancy presentation often substitutes for “Check,” resulting in many supposedly successful projects that did not improve much or even made it worse. Below I compared the normal representation of the PDCA circle having four equal quadrants with a PDCA circle based on the effort by Japanese or Toyota standards, and another PDCA circle based on the effort of (way too many) Western companies. I’ll let you be the judge on how this is in your company.

Over and over again I guide people through the practical problem-solving process, and at every single step they jump to a solution. Let’s take a (fictitious) example for the steps of the problem solving, where every step is going right for the solution, ignoring the initial purpose of the step:

• Clarify the Problem: Well, we need kanban!
• Break Down the Problem: Okay, how many kanban do we need?
• Set a Target: That’s how many kanban we need!
• Root-Cause Analysis: Um… we did this already. It’s the lack of kanban…
• Develop Countermeasures and Implement: Add kanban!
• Monitor Process and Results: Do we have kanban now? Yes, we do. Case closed.
• Standardize and Share: Hey, guys, use kanban!

PS: Many thanks to the team from the Toyota Lean Management Centre at the Toyota UK Deeside engine plant in Wales, where I participated in their 5-day course. This course gave us a lot of access to the Toyota shop floor, and we spent hours on the shop floor looking at processes. In my view, this the only generally accessible course by Toyota that gives such a level of shop floor involvement.

6 thoughts on “Toyota Practical Problem Solving (PPS)—Introduction”

Great ‘ Flow ‘ and easy to understand , specially for many who have limited exposure. Thanks

Thank you for sharing. PDCA is applicable on the shop floor, logistics, service industry – wherever Problems are accurately defined

Nice blog. I’m working in an NHS Production System (NHSps) design based on the Toyota and VMI Production Systems. Do you have any experience in this area?

Hi Tom, sorry, I am completely unfamiliar with the NHS production system. if you mean the National Health Service in the UK, I do have a bit of experience with lean Hospital.

Might I suggest a dry erase marker and a whiteboard? After a few times when the document structure is mostly stable, you can add lines with a permanent marker to fix the format in place. That way you’re not creating extra friction for the process.

As for actual A3, that works best when the A3 paper and printers that can print it are already readily available. I’m sure you ran across more than one business where just about every single printer on site can’t print anything larger than A4 or A3 paper simply isn’t available due to A4 used for everything.

Hi Andrey, I am a great fan of erasable notes, and use dry erase whiteboard markers a lot myself. An A3 printer is also really helpful, but just as you said, not every (small) business has one. For example, I only have an A4 printer in my office…

Leave a Comment

Notify me of new posts by email.

• Learn center
• Project management

How to use Toyota’s legendary A3 problem-solving technique

Georgina Guthrie

February 21, 2020

If you came home one day and found your kitchen taps on full-blast and your house full of water, what’s the first thing you’d do? Grab a bucket and start scooping — or turn off the tap?

When it comes to problem-solving, many of us take a rushed, reactionary approach rather than fixing the issue at the source. So in other words, we see the water, panic, and start scooping. If this sounds like something you’ve done recently, then don’t feel too bad: when the pressure’s high, we often jump towards the quickest fix, as opposed to the most effective one.

This is where the A3 technique comes in. It’s a problem-solving approach designed to efficiently address the root cause of issues.

What is the A3 technique?

The A3 technique is a structured way to solve problems. It’s part of the Lean methodology , developed by Toyota back in the mid-’40s. This doesn’t mean you need to implement a Lean way of working to take advantage of this process — it can work as a standalone exercise.

Granted, A3 isn’t an inspiring name, but the story of its origins is actually pretty interesting. Rumour has it that Taiichi Ohno, inventor of the Toyota Production System, refused to read past the first page of any report. In response, his team created A3 address and summarize problem-solving on one side of A3-sized paper. The A3 technique played a huge part in Toyota’s success and all kinds of industries have since adopted it. Here’s how to get started.

How to solve a problem with A3

The first thing to remember is this: A3 is collaborative and relies on good communication. It’s not something you should do by yourself.

There are three main roles involved:

• Owner (that’s you or someone under your charge)

As you’ve probably guessed, these aren’t roles that already exist in your company; you must create them for the purpose of this process. Here’s what they mean.

The owner is responsible for leading the exercise. They are the lynchpin between the two other roles, fostering good communication and keeping documents up to date. It’s tempting to think of the owner as the head of this trio, but that’s not true: everyone is equal here.

The mentor is someone with solid  problem-solving experience. It’s their job to coach the owner and steer them towards finding a solution. It’s not their job to find the answers themselves.

And finally, there are the  responders . This is someone (or a group of people) who have a vested interest in the outcome of the A3 project. Responders might include the client, stakeholders, or managers. A potential problem here is gaining access to them: if you work somewhere with a strict hierarchy — and you’re somewhere near the bottom of that structure — you may face challenges. There’s no easy way around this. Essentially, you need your organization to support this way of working and make it easy for you to access those at the top if needed.

How to create an A3 report

True to its origins, the A3 report is a one-page document. It typically contains 5-7 sections that systematically lead you towards a solution. These are the most commonly used steps, but feel free to modify them.

• Background:  Explain your project in a few sentences, including its context.
• Problem statement:  Explain the current problem. You can use process mapping to see the different tasks that surround the issue. This isn’t essential, but it will make it easier for you to locate the root cause.
• Goals:  Define your desired outcome, and include metrics for measuring success. You won’t know everything until you reach the end, so you may find you need to come back and refine stages 1-3.
• Root cause analysis:  This is a big stage of the process. You need to work out what you think the root problem is. You can use different methods to help you here, including 5 whys or a fault tree analysis .
• Countermeasures:  Once you’ve worked out your root cause, you can start proposing solutions.
• Implementation:  Work out how you’ll implement these solutions, including an action list with clearly defined roles and responsibilities. Project management software is a useful tool here because it can help everyone on the team track each other’s progress in real-time.
• Follow-up:  Using your metrics for success, decide whether the problem was solved. Report your results back to the team/organization. In the spirit of Lean (continuous improvement), you should go back and modify your plan if the results weren’t as expected. And if they were, you should make this process the new standard.

Final thoughts

A3 is an efficient, methodical way to solve problems at their source. When issues rear their head, rising stress can lead people to panic. Having a clearly designed system in place to guide you towards a solution minimizes the chances of people settling for a ‘quick fix’ or failing to act altogether.

Beyond being a guiding light in times of pressure, A3 is a great team-building exercise because it encourages individuals to work together towards a common goal — across all areas of the organization. Combine this with collaborative tools designed to help teams track progress and work together more effectively, and you’ll be unstoppable.

What is the Poka-Yoke technique, and how do you do it?

How to do a value stream map with Kanban

Subscribe to our newsletter.

Learn with Nulab to bring your best ideas to life

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 .

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

• Business & Money
• Management & Leadership

Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime Try Prime and start saving today with fast, free delivery

Amazon Prime includes:

Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.

• Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
• Unlimited Free Two-Day Delivery
• Streaming of thousands of movies and TV shows with limited ads on Prime Video.
• A Kindle book to borrow for free each month - with no due dates
• Listen to over 2 million songs and hundreds of playlists
• Unlimited photo storage with anywhere access

Important:  Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.

Buy new: .savingPriceOverride { color:#CC0C39!important; font-weight: 300!important; } .reinventMobileHeaderPrice { font-weight: 400; } #apex_offerDisplay_mobile_feature_div .reinventPriceSavingsPercentageMargin, #apex_offerDisplay_mobile_feature_div .reinventPricePriceToPayMargin { margin-right: 4px; } -44% $43.62 $ 43 . 62 FREE delivery Wednesday, May 29 Ships from: Amazon Sold by: ayvax

Return this item for free.

Free returns are available for the shipping address you chose. You can return the item for any reason in new and unused condition: no shipping charges

• Go to your orders and start the return
• Select the return method

Save with Used - Acceptable .savingPriceOverride { color:#CC0C39!important; font-weight: 300!important; } .reinventMobileHeaderPrice { font-weight: 400; } #apex_offerDisplay_mobile_feature_div .reinventPriceSavingsPercentageMargin, #apex_offerDisplay_mobile_feature_div .reinventPricePriceToPayMargin { margin-right: 4px; } $11.26 $ 11 . 26 FREE delivery Thursday, May 30 on orders shipped by Amazon over $35 Ships from: Amazon Sold by: -OnTimeBooks-

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required .

Read instantly on your browser with Kindle for Web.

Using your mobile phone camera - scan the code below and download the Kindle app.

Follow the author

Image Unavailable

• To view this video download Flash Player

A3 Problem Solving for Healthcare: A Practical Method for Eliminating Waste 1st Edition

Purchase options and add-ons.

The A3 process is a way to look with "new eyes" at a specific problem identified by direct observation or experience. It offers a structure that begins by always defining the issue through the eyes of the customer. In A3 Problem Solving for Healthcare Cindy Jimmerson explains an essential tool borrowed from the Toyota Production System, which is an extension of work identified with the well-known Value Stream Map. She offers an easy-to-learn problem-solving method that can be used in every aspect of healthcare to identify, understand, and improve processes that don't support workers in doing their good work. In this compelling book you get:

• The expertise of a recognized industry expert in Lean principles
• A practical, easy-to-use workbook
• Concepts illustrated with numerous A3s in various stages of development
• Explanation of how to extend the VSM philosophy to a more focused perspective
• An extensive exploration of the A3 problem-solving tool in healthcare―the first book to do so

Through case studies and actual A3s, this book illustrates the simplicity and completeness of the A3 tool and its applications to regulatory documentation as well as activities of daily work.

• ISBN-10 1563273586
• ISBN-13 978-1563273582
• Edition 1st
• Publication date June 11, 2007
• Language English
• Dimensions 11.02 x 8.27 x 0.37 inches
• Print length 176 pages
• See all details

Frequently bought together

Customers who viewed this item also viewed

Editorial Reviews

When applying Lean thinking successfully to healthcare, two things are of paramount importance: (1) Keeping it simple and (2) Providing an engaging route map for improvement. With A3 Problem Solving for Healthcare, you get the recipe for both. I thoroughly recommend it. ― Professor Peter Hines, Director, Lean Enterprise Research Centre, Cardiff University, UK Doing more, better, faster, and with less is our new reality. Cindy, because of her curiosity, creativity and clinical acumen, demonstrates that solutions originating outside of our healthcare enterprise can realize (previously) unrealized results. ― Professor Kathy Okland, RN, MPH, Clinical Applications Consultant, Herman Miller Healthcare

What a great book to address a huge gap in healthcare process improvement! Having a source book to teach continuous change and illustrate waste reduction based on the Toyota Production System to busy healthcare practitioners has been sorely lacking until now. I have used the A3 in my hospital and it works! Clinical workers can see the entire project on one piece of paper as well as areas of obvious waste. Since the A3 clearly focuses on changing processes, the clinical workers are motivated to communicate across silos, successfully implement countermeasures, and look at the achieved target condition as the new current condition. The illustrations are superb and I loved all the practical examples. Great work Cindy! ― James Nesbitt, MD, MMM, Project Manager, Providence Alaska Medical Center This book is to be recommended for all hospitals that want to work with Lean and the A3 Problem Solving methodology. The book gives a great view of how The Toyota Production System can be applied to Healthcare all over the world. This book is written by a clinician for clinicians and is the book we have been waiting for. ― Inge Holck, General Manager, Lean Healthcare Europe

About the Author

Product details.

• Publisher ‏ : ‎ Productivity Press; 1st edition (June 11, 2007)
• Language ‏ : ‎ English
• Paperback ‏ : ‎ 176 pages
• ISBN-10 ‏ : ‎ 1563273586
• ISBN-13 ‏ : ‎ 978-1563273582
• Item Weight ‏ : ‎ 14.4 ounces
• Dimensions ‏ : ‎ 11.02 x 8.27 x 0.37 inches
• #2,094 in Health Care Delivery (Books)
• #2,880 in Environmental Economics (Books)
• #13,956 in Business Management (Books)

About the author

Cindy leduc jimmerson.

Discover more of the author’s books, see similar authors, read author blogs and more

Customer reviews

Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.

To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.

• Sort reviews by Top reviews Most recent Top reviews

Top reviews from the United States

There was a problem filtering reviews right now. please try again later..

Top reviews from other countries

• Amazon Newsletter
• About Amazon
• Accessibility
• Sustainability
• Press Center
• Investor Relations
• Amazon Devices
• Amazon Science
• Sell on Amazon
• Sell apps on Amazon
• Supply to Amazon
• Protect & Build Your Brand
• Become an Affiliate
• Become a Delivery Driver
• Start a Package Delivery Business
• Advertise Your Products
• Self-Publish with Us
• Become an Amazon Hub Partner
• › See More Ways to Make Money
• Amazon Visa
• Amazon Store Card
• Amazon Secured Card
• Amazon Business Card
• Shop with Points
• Credit Card Marketplace
• Reload Your Balance
• Amazon Currency Converter
• Your Account
• Your Orders
• Shipping Rates & Policies
• Amazon Prime
• Returns & Replacements
• Manage Your Content and Devices
• Recalls and Product Safety Alerts
• Conditions of Use
• Privacy Notice
• Consumer Health Data Privacy Disclosure
• Your Ads Privacy Choices

• Lean Philosophy

Eight Steps To Practical Problem Solving

The Toyota Way To Problem Solving

The art of problem solving is constantly trying to evolve and be re-branded by folks in various industries. While the new way might very well be an effective method in certain applications. A tried and true way of identifying and solving problems is the eight steps to practical problem solving developed by Toyota, years ago. The system is structured, but simple and practical enough to handle problems of the smallest nature, to the most complex issues.

Using a fundamental and strategic way to solve problems creates consistency within an organization. When you base your results off facts, experience and common sense, the results form in a rational and sustainable way.

The Eight Step Problem Solving Process

• Clarify the Problem
• Breakdown the Problem
• Set the Target
• Analyze the Root Cause
• Develop Countermeasures
• Implement Countermeasures
• Monitor Results and Process
• Standardize and Share Success

The eight steps to practical problem solving also include the Plan, Do, Check and Act (PDCA) cycle. Steps one through five are the planning process. The doing is found in step six. Step seven is the checking . Step eight involves acting out the results of the new standard.

This practical problem solving can be powerful tool to issues facing your organization. It allows organizations to have a common understanding of what defines a problem and what steps are going to be taken in order to overcome the problem efficiently.

The Eight Steps Broken Down:

Step 1: clarify the problem.

A problem can be defined in one of three ways. The first being, anything that is a deviation from the standard. The second could be the gap between the actual condition and the desired condition. With the third being an unfilled customer need.

In order to best clarify the problem, you have to see the problem with your own eyes. This gives you the details and hands-on experience that will allow you to move forward in the process.

Step 2: Breakdown the Problem

Once you’ve seen the problem first hand, you can begin to breakdown the problem into more detailed and specific problems. Remember, as you breakdown your problem you still need to see the smaller, individual problems with your own eyes. This is also a good time to study and analyze the different inputs and outputs  of the process so that you can effectively prioritize your efforts. It is much more effective to manage and solve a bunch of micro-problems one at a time, rather than try and tackle a big problem with no direction.

Step 3: Set the Target

Step three is all about commitment and focus. Your attention should now turn towards focusing on what is needed to complete the project and how long it will take to finish. You should set targets that are challenging, but within limits and don’t put a strain on the organization that would hinder the improvement process.

Step 4: Analyze the Root Cause

This is a vital step when problem solving, because it will help you identify the actual factors that caused the issue in the first place. More often than not, there are multiple root causes to analyze. Make sure you are considering all potential root causes and addressing them properly. A proper root cause analysis, again involves you actually going to the cause itself instead of simply relying on reports.

Step 5: Develop Countermeasures

Once you’ve established your root causes, you can use that information to develop the countermeasures needed to remove the root causes. Your team should develop as many countermeasures needed to directly address any and all root causes. Once you’ve developed your countermeasures, you can begin to narrow them down to the most practical and effective based off your target.

Step 6: Implement Countermeasures

Now that you have developed your countermeasures and narrowed them down, it is time to see them through in a timely manner. Communication is extremely important in step six. You’ll want to seek ideas from the team and continue to work back through the PDCA cycle to ensure nothing is being missed along the way. Consider implementing one countermeasure at a time to monitor the effectiveness of each.

You will certainly make mistakes in throughout your problem solving processes, but your persistence is key, especially in step six.

Step 7: Monitor Results and Process

As mistakes happen and countermeasures fail, you need a system in place to review and modify them to get the intended result. You can also determine if the intended outcome was the result of the action of the countermeasure, or was it just a fluke? There is always room for improvement in the problem solving process, but you need to be able to recognize it when it comes to your attention.

Step 8: Standardize and Share Success

Now that you’ve encountered success along your problem solving path, it is time to set the new processes as the new standard within the organization and share them throughout the organization. It is also a good time to reflect on what you’ve learned and address any possible unresolved issues or troubles you have along the way. Ignoring unresolved issues will only lead to more problems down the road.

Finally, because you are a true Lean organization who believes continuous improvement never stops, it is time to tackle the next problem. Start the problem solving process over again and continue to work towards perfection.

Additional Resources

• 8D for Problem Solving – creativesafetysupply.com
• Training to Use 8D Problem-Solving Tactics – blog.creativesafetysupply.com
• The Great Root Cause Problem Solving Debate – realsafety.org
• Design Thinking: Empathy and Iteration for Innovation and Problem-Solving – creativesafetypublishing.com
• 10 Commandments to Continuous Improvement – lean-news.com
• Lean Manufacturing Implementation – The First 5 Steps – iecieeechallenge.org
• “No Problem” is a Problem – jakegoeslean.com
• The Transitional Steps Involved In The 5s Principles During Implementation – 5snews.com
• The Tools of Kaizen – blog.5stoday.com

Related posts:

• 3P and Lean
• The Vacation Paradox
• Why Single Minute Exchange of Die (SMED)?
• Total Quality Management And Kaizen Principles In Lean Management
• An Engaged Employee is a Productive Employee
• Jim Womack’s Top Misconceptions of the Lean Movement
• Muda, Mura, and Muri: The Three Wastes