5 step problem solving template

Lean Events and Training / Forms and Templates

Forms and Templates

Downloads for A3 problem solving, standard work , project management, and value stream mapping .

Problem Solving Templates

A3 Action Plan Form (from Getting the Right Things Done)

• The action plan template helps define the who, what, when, where, and how of a plan on one page.
• Helps track progress and highlight problems so action can be taken.

A3 Status Review Form (from Getting the Right Things Done)

• Top box provides an overview with respect to our critical end-of-pipe metrics.
• Second box provides an overview of activities, and usually reflects what’s been prescribed on the action plan of the right side of the strategy A3.

A3 Strategy Form (from Getting the Right Things Done)

• A strategy A3 is a one-page storyboard on 11-inch by 17-inch paper that helps tell the strategy “story.”
• Logic flows from top left to bottom right, and each box leads to the next one.

Detailed A3 Template (from Managing to Learn)

• Print this A3 template out to remind you of each section of the problem-solving A3 as you are creating your own.

PDSA A3 Template (from On the Mend)

• A3 Template, in Excel, following the PDSA cycle.

Problem Definition Worksheet

• This worksheet can help you breakdown the problem into a clearly defined gap as well as see how the problem aligns to the needs of the business or your True North purpose.

Root Cause Template

• This template gives you space to record the problem as well as the direct causes and underlying causes.

Four Types of Problems

Art Smalley

Managing to Learn: Using the A3 management process

Perfecting Patient Journeys

Beau Keyte , Tom Shuker and Judy Worth

Getting the Right Things Done

Pascal Dennis

Standard Work Templates

Standard Work Operator Balance Chart (OBC)

• The operator balance chart helps create continuous flow in a multi-step, multi-operator process by distributing operator work elements in relation to takt time.

Standard Work Process Study Sheet

• The Process Study Sheet is used to define and record the time for work elements in a process.

Standard Work Production Analysis Board

• A Production Analysis Board is a display that must be located at the exit of the cell (or the line) to show actual performance compared with planned performance on an hourly basis.

Standard Work Skills Training Matrix

• The Skills Training Matrix shows the required and attained skills of every operator.
• The training schedule also should be shown.

Standardized Work Chart

• The standardized work chart shows operator movement and material location in relation to the machine and overall process layout.
• It should show takt time, work sequence, and standard WIP.

Standardized Work Combination Table

• The standardized work combination table shows the combination of manual work time, walk time, and machine processing time for each operation in a production sequence.
• This form is a more precise process design tool than the Operator Balance Chart.
• It can be very helpful to identify the waste of waiting and overburden, and to confirm standard.

Standardized Work Job Instruction Sheet

• The job instruction sheet is used to train new operations.
• It lists the steps of the job, detailing any special knack that may be required to perform the job safely with utmost quality and efficiency.
• It can also be useful for experienced operators to reconfirm the right operations.

Standardized Work Process Capacity Sheet

• The Process Capacity Chart is used to calculate the capacity of each machine to confirm true capacity and to identify and eliminate bottlenecks.
• Processing capacity per shift will be calculated from the available production time, completion time, and tool-change time (and other factors as necessary) for each work piece.

Waste Walk Template (from Perfecting Patient Journeys)

• Taking a “waste walk” is one way to make the waste visible again.
• A waste walk is simply a planned visit to where work is being performed to observe what’s happening and to note the waste. It differs from go-see activities in that you are specifically looking for waste.

Kaizen Express

Toshiko Narusawa and John Shook

Lean Lexicon 5th Edition

Lean Enterprise Institute

Training Within Industry (TWI) Templates and Downloads

8-step TWI problem solving card - as presented by IBM

• 8-steps to problem solving handy pocket card printable.

Solving Problems with TWI

• Solving problems with TWI deployment graphic.

Template of Job Breakdown Sheet

• Job breakdown sheets are created to list the steps and highlight the main factors or key points that go into completing a job.
• It also provides reasons for these key points.

TWI Job Instruction Card

• TWI Job Instruction card in a handy pocket printable.

TWI Job Methods Card

• TWI Job Methods Card in a handy pocket printable.

TWI Job Relations Card

• TWI Job Relations Card in a handy pocket printable.

Lean Solutions

James (Jim) Womack, PhD and Dan Jones

Lean Thinking, 2nd Edition

Project Management Templates

Master Schedule and Action Plan Template for One Goal (from Perfecting Patient Journeys)

• Use this template in your project tracking center so you can track both goals and action items on the same form.

End of Project Review Template (from Perfecting Patient Journeys)

• The following template will help you capture your end-of-project reflections and make decisions about what to do next.

Master Schedule Template (from Perfecting Patient Journeys)

• This template will help you answer this question by letting you include the project goals with space to indicate whether each goal is on track as originally planned and whether the scheduled progress review has taken place.

Team Board Form (from Getting the Right Things Done)

• A team board is a window on both routine and improvement work.
• The board on this template addresses both daily production and strategic issues, and is organized according to SQDCM—safety, quality, delivery, cost, and morale.

Value Proposition Template (from Perfecting Patient Journeys)

• Align the stakeholders around what will be included in addressing the problem,
• Identify the stakeholders who will be added to the project team and actively engaged in creating the current- and future-state value-stream maps,
• Identify additional stakeholders necessary to drive the implementation of the future state,
• Serve as an agreement—a proof of consensus—on the specific problem to be solved, and with the problem statement serve as authorization for the entire project.

Action Planning Template (from Perfecting Patient Journeys)

• Identify the specific changes that need to be made and translate those changes into clearly stated goals and actions (i.e., the means) to achieve those goals.
• Identify the specific methods and action steps you think will help you achieve the goals. These action steps and targets constitute the action plan to achieve a specific goal.

Value-Stream Mapping Templates

Value-stream Mapping Icons for Excel

• At the request of some of our readers we have posted the most commonly used mapping icons so that they can be downloaded for Excel spreadsheets.

Learning to See

Mike Rother and John Shook

VSM Getting Started Set

Lean Enterprise Institute , Mike Rother and John Shook

Mapping to See: Value-Stream Improvement Workshop

Beau Keyte , Jim Luckman , Kirk Paluska , Guy Parsons , John Shook , Tom Shuker and David Verble

Improvement Kata / Coaching Kata

Improvement Kata Learner's Storyboard

Subscribe to get the very best of lean thinking delivered right to your inbox

Privacy overview.

Free Problem Statement Templates: All Formats

By Kate Eby | March 4, 2024

• Share on Facebook
• Share on LinkedIn

Link copied

We've collected the top problem statement templates to help you identify and articulate challenges clearly and concisely in any business context. Download any of these free templates that align with your needs, and customize it for your organization.

On this page, you’ll find a  customer problem statement template , a  problem and solution slide template , a  problem statement document template , and more. You’ll also find information on different  types of problem statement templates and related  problem-solving tools .

5 Ws Problem Statement Template

Download a 5 Ws Problem Statement Template for

Microsoft Word | Adobe PDF | PowerPoint | Google Slides

When to Use This Template:  Use this 5 Ws problem statement template to create a methodical breakdown of issues at team meetings or brainstorming sessions. Ensure that nothing is overlooked by answering who, what, when, where, and why questions about a problem. By doing so, you can create a clear and concise problem statement.

Notable Template Features: Using five key questions to explore a problem fosters a comprehensive understanding of the issue while helping to narrow the focus of your final problem statement. Each segment of the template is color-coded and provides bullet points to delve into specifics, such as who is affected and the problem's scope and significance.

Customer Problem Statement Template

Download a Customer Problem Statement Template for

When to Use This Template:  This template provides a structured approach to translating client issues into an effective problem statement. It is especially useful for customer experience teams, marketing personnel, and product developers who are tasked with turning customer feedback into actionable insights.

Notable Template Features: This template takes you through the steps of clarifying customer issues and perspectives to help teams find customer-focused solutions. Download the template in PowerPoint or Google Slides  for presentations, or try the Microsoft Word or Adobe PDF versions to create a printable worksheet.

Three-Part Problem Statement Slide Template

Download a Three-Part Problem Statement Slide Template for

PowerPoint | Google Slides

When to Use This Template: Use this slide template to present key points to stakeholders in project reviews or strategic planning sessions. Teams can also use this template to facilitate problem-solving meetings.

Notable Template Features:  This template guides the audience from problem to solution to result, promoting a thorough understanding of the problem’s context. Each section includes bullet points to organize and present complex details in a simple yet engaging format.

Single-Problem Statement and Solution Slide Template

Download a Single-Problem Statement and Solution Slide Template for

When to Use This Template: This problem statement slide template allows you to clearly outline a problem and propose a viable solution in one visually dynamic slide, making it a perfect addition to business proposals, project pitches, and strategy meetings.

Notable Template Features:  This slide template separates the problem on the left from the solution on the right, using a clear layout and colorful symbols to grab the viewer's attention. This simple design ensures that the audience grasps the core issue quickly, facilitating a focused and efficient discussion.

For more slide template resources like this one, see this collection of free  PowerPoint problem statement templates .

Project Problem Statement Document Template

Download a Project Problem Statement Document Template for

Microsoft Word | Adobe PDF

When to Use This Template: Use this document template to draft a comprehensive problem statement report. The template is best for individuals or teams tasked with in-depth analysis and documentation of business issues, ensuring that they cover all relevant aspects of the problem.

Notable Template Features: This template features a structured outline with labeled sections for documenting the problem statement, background information, impact, and potential solutions. The outline takes readers through a logical progression — from identifying the problem to proposing solutions — for a clear and persuasive presentation.

Problem Statement Worksheet Template

Download a Problem Statement Worksheet Template for

Excel | Microsoft Word | Adobe PDF

When to Use This Template:  Use this worksheet to create an effective problem statement when starting a new project. The template is particularly useful for project teams that need to align on the specifics of a problem, set measurable goals, and identify obstacles and solutions.

Notable Template Features:  This problem statement worksheet guides you through a step-by-step process to craft a concise and impactful problem statement. The template includes clear sections where you can provide details about the problem, the gap between the current state and the goal, and the people or processes affected. It includes space for setting SMART goals related to the problem, identifying barriers, and formulating a plan to overcome these challenges.

Problem Statement Matrix Template

Download a Problem Statement Matrix Template for

When to Use This Template:  This template helps teams and managers prioritize multiple problems. Teams can assess and sort problems based on urgency and potential impact to effectively guide strategic action plans. 

Notable Template Features:  This template organizes essential aspects of each problem into a simple matrix, including a problem statement, priority, visibility, impact, response timeframe, and proposed solutions. The matrix format is useful when you want an overview of problems with key details highlighted.

Types of Problem Statement Templates

Problem statements are used in business settings and academic research to clearly define a problem that needs to be solved. A well-written statement is concise, narrow in focus, and based on evidence. While all problem statements include similar elements, they will vary depending on the context and type of issue. There are many tools that can aid in this process. 

Here’s a closer look at the different types of problem statement templates for project and product management:

Customer Problem Statement Templates

Customer problem statement templates guide you through the process of viewing issues from the customer’s perspective. They provide a structured approach to mapping out the customer journey, pinpointing the underlying cause of problems, and understanding their emotional impacts on customers.

Customer problem statement templates typically organize information into five key elements:  

• I Am: Who is the customer? This could be as broad as a demographic group or as specific as a user persona. Clearly defining your customer sets the foundation for a more targeted analysis.
• I Am Trying To: What is the customer trying to achieve? Articulate the customer's goal or what they hope to accomplish with your product or service. This helps in aligning your solutions with customer needs.
• But: What is getting in their way? Identify the challenges that prevent the customer from achieving their goals. These could be related to product features, service limitations, or external factors.
• Because: What is the root of the issue? Analyze the internal and external factors that contribute to the problem to uncover the underlying causes.
• Which Makes Me Feel: What is the customer's emotional response to this issue? Emotions can affect how customers perceive your product or service. If they're feeling frustration, disappointment, or confusion, they might be less likely to engage positively with your brand or recommend your services to others. Knowing this helps convey the urgency of addressing the problem.

Using a customer problem statement template shifts the focus from internal perceptions of what the problem might be to a clearer understanding of the customer's experience. The process involves gathering and analyzing customer feedback, conducting market research, and possibly engaging directly with customers through interviews or surveys. 

Product Problem Statement Templates

Since having a customer-centric perspective is vital for developing successful products, there is overlap between product and customer problem statement templates. However, understanding customer issues is just one step in the development process. Product teams must consider whether the solutions they come up with will truly benefit the customer, what value a product will bring to the company, what steps are needed to solve the problem, and how to measure success. 

One common structure for product problem statement templates is the 5 Ws framework, which involves answering the following questions:  

• Who: Who is the problem affecting?
• What: What is the unmet need?
• When: When is the problem happening?
• Where: Where is the problem occurring?
• Why: Why is this worth solving?

Some templates might include a sixth question: How are you going to solve the problem?

These templates can help teams identify initial product opportunities, refine product concepts, and diagnose issues in existing products. They help in prioritizing features, making strategic adjustments, and communicating the product vision and challenges internally.

Project Problem Statement Templates

Similar to customer and product templates, project problem statement templates help teams articulate the core issue they aim to address with their project. They are often used at early planning stages to gain clarity and consensus among stakeholders on the project's direction.

A project problem statement template typically includes the following elements:  

• Problem: Clearly define the issue at hand with a precise description of the gap between the current state and the desired state.
• Background: Provide context for the problem by offering insights into its origins and scope. This helps stakeholders understand the complexity and nuances of the issue.
• Relevance: Highlight the significance of the problem, its potential impacts, and why addressing it matters to the organization or stakeholders.
• Objectives: Outline the objectives of the project with SMART goals that guide the project's direction and help in measuring its success.  

Some templates, such as a problem statement worksheet, are designed to help you craft an effective statement, while others are suitable for presentations or reports to stakeholders. For some helpful options, see this collection of free  problem statement slide templates .

Related Problem-Solving Templates

Fully understanding a problem and finding effective solutions requires in-depth analysis. Here is a list of problem-solving templates that can help with that process:

Fishbone Diagram Template

A  fishbone diagram template organizes the causes of a problem into categories, enabling teams to identify, analyze, and address root causes by branching out possible contributing factors from a central problem statement.

8D Report Template

An  8D report template guides teams through a structured eight-step process to identify, correct, and eliminate recurring problems. This problem-solving approach emphasizes root cause analysis and long-term solutions.

A3 Template

An  A3 template offers a concise framework for problem solving, encouraging teams to identify issues, find root causes, and develop solutions on a single A3-sized sheet of paper for clarity and efficiency.

Simple Root Cause Analysis Template

Use our  simple root cause analysis template to map out symptoms, effects, causes, and suggested solutions in a color-coded spreadsheet. Each section includes important details, such as urgency, risks, and success criteria for a systematic approach to analyzing problems.

DMAIC Root Cause Analysis Template

A  DMAIC analysis template outlines a structured, five-phase approach to problem solving

— define, measure, analyze, improve, control — guiding teams through a detailed process to identify problems, analyze causes, and improve processes.

For more problem-solving templates, see this collection of free  root cause analysis templates and  Lean Six Sigma templates .

Solve Organizational Issues with Real-Time Work Management in Smartsheet

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.

• RCA 101 – 5-Why Analysis (Free Training)
• RCA 201 – Basic Failure Analysis
• RCA 301 – PROACT® RCA Certification
• RCA 401 – RCA Train The Trainer
• Other Trainings
• 5 Whys Root Cause Analysis Template
• RCA Template
• Chronic Failure Calculator

Root Cause Analysis with 5 Whys Technique (With Examples)

By Sebastian Traeger

Updated: April 23, 2024

Reading Time: 7 minutes

What Is the 5 Whys Technique?

Example of the 5 whys technique, how to conduct a 5 whys analysis in 5 steps, when to use a 5 whys analysis, using 5 whys template, tips for mastering the 5 whys technique, frequently asked questions about 5 whys.

With over two decades in business – spanning strategy consulting, tech startups and executive leadership – I am committed to helping your organization thrive.

At Reliability, we’re on a mission to help enhance strategic decision-making and operational excellence through the power of Root Cause Analysis, and I hope this article will be helpful! 

Our goal is to help you better understand 5 whys techniques by offering insights and practical tips based on years of experience. Whether you’re new to doing RCAs or a seasoned pro, we trust this will be useful in your journey towards working hard and working smart.

The 5 Whys Technique is like peeling an onion – it helps you uncover the underlying reasons behind a problem, layer by layer. By repeatedly asking “why” at least five times, this method digs deep to reveal the root cause of an issue. It’s a simple yet powerful problem-solving approach that aims to get to the heart of the matter rather than just addressing surface-level symptoms.

5 Whys Technique: A method that involves iteratively asking “why” five times to unveil the fundamental cause of a problem.

In essence, the 5 Whys Technique is not just about fixing what’s broken on the surface; it’s about understanding and addressing the deeper issues that lead to problems in the first place.

The 5 Whys Technique is like a detective, uncovering the truth behind recurring problems. Let’s take a look at how this method works in two different scenarios.

Case Study: Manufacturing Defects

Imagine a company that keeps encountering the same manufacturing defects despite various attempts to fix them. By using the 5 Whys Technique, they discovered that the defects were not caused by faulty machinery, as previously assumed, but rather by human error due to unclear operating instructions. This realization led to improved training procedures and clear work guidelines, ultimately eliminating the defects.

Application in Service Industry

Now, consider a service industry struggling with frequent customer complaints and service failures. Through the 5 Whys Technique, it was revealed that these issues stemmed from inadequate staffing levels during peak hours. By addressing this root cause, such as hiring additional staff or adjusting schedules, the service quality can significantly improve, leading to higher customer satisfaction.

These examples illustrate how the 5 Whys Technique can be applied across different sectors to identify and address underlying issues effectively.

Step 1: Identify the Problem

Before diving into a 5 Whys analysis, it’s crucial to clearly identify the problem or issue at hand . This step sets the stage for the entire process and ensures that the focus remains on addressing the right concern. Take the time to gather relevant data, observe patterns, and consult with team members or stakeholders to gain a comprehensive understanding of the problem.

Step 2: Ask ‘Why’ Five Times

Once the problem is clearly defined, it’s time to start peeling back the layers. The process involves asking “why” five times, not necessarily limited to five questions but enough to delve deeper into the underlying causes of the problem . Each “why” serves as a gateway to uncovering additional factors contributing to the issue. This iterative approach helps in identifying not just one cause, but multiple interconnected elements that may be at play.

By consistently probing deeper with each “why,” you can reveal hidden complexities and nuances that may have been overlooked initially. This method allows for a more thorough understanding of the situation, paving the way for effective solutions that address root causes rather than surface-level symptoms.

This structured approach encourages critical thinking and enables teams to move beyond quick fixes towards sustainable improvements.

The 5 Whys Technique is a versatile problem-solving approach that can be applied in various scenarios to uncover root causes and drive continuous improvement. Here are two key situations where the 5 Whys Analysis can be particularly beneficial:

Recurring Issues

• The 5 Whys Technique is especially useful when dealing with recurring issues. Whether it’s a manufacturing defect that keeps resurfacing or a persistent customer complaint in the service industry, this method helps identify the underlying reasons behind these repetitive problems. By repeatedly asking “why,” it becomes possible to trace the issue back to its root cause, allowing for targeted solutions that prevent reoccurrence.

Process Improvement

• Organizations constantly strive to enhance their processes and workflows for increased efficiency and quality. When seeking to improve existing procedures, the 5 Whys Technique serves as a valuable tool. By systematically analyzing the factors contributing to inefficiencies or bottlenecks, teams can gain insights into how processes can be optimized at their core. This method enables organizations to make informed decisions about process improvements based on a deep understanding of the underlying issues.

In both cases, the 5 Whys Analysis offers a structured yet flexible approach to delve into complex problems, making it an indispensable tool for driving meaningful change and progress within organizations.

When it comes to conducting a 5 Whys analysis, utilizing a structured template can greatly facilitate the process and ensure a comprehensive investigation into the root cause identification. Using RCA software such as EasyRCA can benefit the team by streamlining your 5-why process. Here’s how organizations can benefit from using a template:

Benefits of Using a Template

• Streamlined Process: A well-designed 5 Whys template provides a clear framework for conducting the analysis, guiding teams through the iterative questioning process. This streamlines the investigation, making it easier to navigate and ensuring that no crucial aspects are overlooked.
• Thorough Investigation: By following a predefined template, teams are prompted to explore various facets of the problem systematically. This ensures that all relevant factors are considered, leading to a more thorough and insightful investigation into the underlying causes.
• Consistent Approach: Templates offer a standardized approach to conducting 5 Whys analyses within an organization. This consistency promotes uniformity in problem-solving methods across different teams or departments, enhancing overall efficiency and effectiveness.

Customizing the Template

Organizations have the flexibility to customize 5 Whys templates according to their specific needs and industry requirements. This adaptability allows for tailoring the template to address unique challenges and incorporate industry-specific considerations. Customization may include:

• Adding Industry-Specific Prompts: Tailoring the template by incorporating prompts or questions relevant to particular industries or types of issues being analyzed.
• Incorporating Visual Aids: Enhancing the template with visual aids such as flow charts or diagrams can help teams better understand and communicate complex causal relationships.
• Iterative Refinement: Regularly reviewing and refining the template based on feedback and evolving organizational needs ensures that it remains aligned with current processes and challenges.

Customizing the template empowers organizations to harness the full potential of the 5 Whys Technique in addressing diverse problems while aligning with their unique operational contexts.

Encouraging Open Communication

In mastering the 5 Whys Technique as a problem-solving method, creating an environment that fosters open communication is paramount. When team members feel comfortable expressing their perspectives and insights, it leads to a more comprehensive exploration of the underlying causes of a problem. Encouraging open communication allows for diverse viewpoints to be considered, providing a holistic understanding of the issue at hand.

By promoting an atmosphere where individuals are empowered to voice their observations and concerns, the 5 Whys analysis can benefit from a rich tapestry of ideas and experiences. This inclusive approach not only enhances the depth of the analysis but also cultivates a sense of ownership and collective responsibility for addressing root causes within the team or organization.

Continuous Improvement Mindset

A key aspect of mastering the 5 Whys Technique is embracing a continuous improvement mindset. Rather than viewing problems as isolated incidents, this approach encourages teams to see them as opportunities for growth and development. By instilling a culture of continuous improvement, organizations can leverage the insights gained from 5 Whys analyzes to drive positive change across various aspects of their operations.

Fostering a mindset focused on continuous improvement entails actively seeking feedback, evaluating processes, and implementing iterative enhancements based on the findings. It involves an ongoing commitment to learning from past experiences and leveraging that knowledge to proactively address potential issues before they escalate. Embracing this mindset ensures that the 5 Whys Technique becomes ingrained in the organizational ethos, leading to sustained progress and resilience in problem-solving efforts.

As we wrap up our exploration of the 5 Whys Technique, let’s address some common questions that may arise regarding this powerful problem-solving method.

What is the primary goal of the 5 Whys Technique?

The primary goal of the 5 Whys Technique is to uncover the root cause of a problem by iteratively asking “why” at least five times. This approach aims to move beyond surface-level symptoms and address the underlying issues that lead to recurring problems.

Is the 5 Whys Technique limited to specific industries or sectors?

No, the 5 Whys Technique is versatile and can be applied across various industries and sectors. Whether it’s manufacturing, healthcare, service, or technology, this method offers a structured yet flexible approach to identifying root causes and driving continuous improvement.

How does the 5 Whys Technique contribute to continuous improvement?

By delving into the fundamental reasons behind problems, the 5 Whys Technique provides organizations with valuable insights for driving continuous improvement. It not only helps in resolving immediate issues but also fosters a culture of ongoing enhancement and development within an organization.

Can the 5 Whys Technique be used for complex problems with multiple contributing factors?

Yes, while initially designed as a simple and straightforward method, the 5 Whys Technique can certainly be applied to complex problems with multiple interconnected factors. By systematically probing deeper into each layer of causality, this technique enables a comprehensive understanding of intricate issues.

I hope you found this guide to 5 whys technique insightful and actionable! Stay tuned for more thought-provoking articles as we continue to share our knowledge. Success is rooted in a thorough understanding and consistent application, and we hope this article was a step in unlocking the full potential of Root Cause Analysis for your organization.

Reliability runs initiatives such as an online learning center focused on the proprietary PROACT® RCA methodology and EasyRCA.com software. For additional resources, visit Reliability Resources .

• Root Cause Analysis /

Recent Posts

Ultimate Guide to Swiss Cheese Model and Its Applications

5 Root Cause Analysis Examples That Shed Light on Complex Issues

What Is Fault Tree Analysis (FTA)? Definition & Examples

Root Cause Analysis Software

Our RCA software mobilizes your team to complete standardized RCA’s while giving you the enterprise-wide data you need to increase asset performance and keep your team safe.

Root Cause Analysis Training

[email protected]

Tel: 1 (800) 457-0645

Share article with friends:

• Product overview
• All features
• App integrations

CAPABILITIES

• project icon Project management
• Project views
• Custom fields
• Status updates
• goal icon Goals and reporting
• Reporting dashboards
• workflow icon Workflows and automation
• portfolio icon Resource management
• Time tracking
• my-task icon Admin and security
• Admin console
• asana-intelligence icon Asana Intelligence
• list icon Personal
• premium icon Starter
• briefcase icon Advanced
• Goal management
• Organizational planning
• Campaign management
• Creative production
• Content calendars
• Marketing strategic planning
• Resource planning
• Project intake
• Product launches
• Employee onboarding
• View all uses arrow-right icon
• Project plans
• Team goals & objectives
• Team continuity
• Meeting agenda
• View all templates arrow-right icon
• Work management resources Discover best practices, watch webinars, get insights
• What's new Learn about the latest and greatest from Asana
• Customer stories See how the world's best organizations drive work innovation with Asana
• Help Center Get lots of tips, tricks, and advice to get the most from Asana
• Asana Academy Sign up for interactive courses and webinars to learn Asana
• Developers Learn more about building apps on the Asana platform
• Community programs Connect with and learn from Asana customers around the world
• Events Find out about upcoming events near you
• Partners Learn more about our partner programs
• Support Need help? Contact the Asana support team
• Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Featured Reads

• Project management |
• What is 8D? A template for efficient pr ...

What is 8D? A template for efficient problem-solving

How you respond when problems arise is one of the most defining qualities of a manager. Luckily, there are tools you can use to master problem-solving. The 8D method of problem-solving combines teamwork and basic statistics to help you reach a logical solution and prevent new issues from arising.

You’ve spent months overseeing the development of your company's newest project. From initiation, planning, and execution, you’re confident this may be your best work yet.

Until the feedback starts rolling in.

There’s no sugar-coating it—things don’t always go as planned. But production or process issues are hardly a signal to throw in the towel. Instead, focus on honing your problem-solving skills to find a solution that keeps it from happening again. 

The 8D method of problem solving emphasizes the importance of teamwork to not only solve your process woes but prevent new ones from occurring. In this guide, we’ll break down what 8D is, how to use this methodology, and the benefits it can give to you and your team. Plus, get an 8D template to make solving your issue easier. 

What is 8D?

The eight disciplines (8D) method is a problem-solving approach that identifies, corrects, and eliminates recurring problems. By determining the root causes of a problem, managers can use this method to establish a permanent corrective action and prevent recurring issues. 

How do you use the 8D method?

The 8D method is a proven strategy for avoiding long-term damage from recurring problems. If you’re noticing issues in your workflow or processes, then it’s a good time to give this problem-solving method a try. 

To complete an 8D analysis, follow “the eight disciplines” to construct a statistical analysis of the problem and determine the best solution.

The eight disciplines of problem-solving

8D stands for the eight disciplines you will use to establish an 8D report. As you may notice, this outline starts with zero, which makes nine total disciplines. The “zero stage” was developed later as an initial planning stage. 

To illustrate these steps, imagine your organization experienced a decline in team innovation and productivity this past year. Your stakeholders have noticed and want to see changes implemented within the next six months. Below, we’ll use the 8D process to uncover a morale-boosting solution.

D0: Prepare and plan

Before starting the problem-solving process, evaluate the problem you want to solve. Understanding the background of the problem will help you identify the root cause in later steps. 

Collect information about how the problem has affected a process or product and what the most severe consequences may be. Planning can include:

Gathering data

Determining the prerequisites for solving the problem

Collecting feedback from others involved

If we look back at our example, you may want to figure out whether this decline in morale is organization-wide or only applies to a few departments. Consider interviewing a few employees from different departments and levels of management to gain some perspective. Next, determine what knowledge and skills you will need to solve this lapse in productivity. 

D1: Form your team

Create a cross-functional team made up of people who have knowledge of the various products and workflows involved. These team members should have the skills needed to solve the problem and put corrective actions in place. 

Steps in this discipline may include:

Appointing a team leader

Developing and implementing team guidelines

Determining team goals and priorities

Assigning individual roles

Arranging team-building activities

From our example, a solid team would consist of people with first-hand experience with the issues—like representatives from all departments and key people close to workshop-level work. You may also want to pull someone in from your HR department to help design and implement a solution. Most importantly, make sure the people you choose want to be involved and contribute to the solution.

D2: Identify the problem

You may have a good understanding of your problem by now, but this phase aims to break it down into clear and quantifiable terms by identifying the five W’s a and two H’s (5W2H):

Who first reported the problem?

What is the problem about?

When did it occur and how often?

Where did it occur (relating to the sector, supplier, machine, or production line involved)?

Why is solving the problem important?

How was the problem first detected?

How many parts/units/customers are affected?

Use your team’s insights to answer these questions. From our example, your team may conclude that: 

Employees feel overwhelmed with their current workload. 

There is no real structure or opportunity to share new ideas.

Managers have had no training for meetings or innovation settings.

Disgruntled employees know they can achieve more—and want to achieve more—even if they seem disengaged.

Once you answer these questions, record an official problem statement to describe the issue. If possible, include photos, videos, and diagrams to ensure all parties have a clear understanding of the problem. It may also help to create a flowchart of the process that includes various steps related to the problem description.

D3: Develop an interim containment plan

Much like we can expect speedy first aid after an accident, your team should take immediate actions to ensure you contain the problem—especially if the problem is related to customer safety. 

An interim containment plan will provide a temporary solution to isolate the problem from customers and clients while your team works to develop a permanent corrective action. This band-aid will help keep your customers informed and safe—and your reputation intact.

Because your findings revealed workers were overworked and managers lacked training, your team suggests scheduling a few mandatory training sessions for leaders of each department covering time and stress management and combating burnout . You may also want to have a presentation outlining the topics of this training to get key managers and stakeholders interested and primed for positive upcoming changes. 

D4: Verify root causes and escape points

Refer back to your findings and consult with your team about how the problem may have occurred. The root cause analysis involves mapping each potential root cause against the problem statement and its related test data. Make sure to test all potential causes—fuzzy brainstorming and sloppy analyses may cause you to overlook vital information. 

In our example, focus on the “why” portion of the 5W2H. You and your team identify six root causes:

Managers have never had any training

There is a lack of trust and psychological safety

Employees don’t understand the objectives and goals

Communication is poor

Time management is poor

Employees lack confidence

In addition to identifying the root causes, try to pinpoint where you first detected the problem in the process, and why it went unnoticed. This is called the escape point, and there may be more than one. 

D5: Choose permanent corrective actions

Work with your team to determine the most likely solution to remove the root cause of the problem and address the issues with the escape points. Quantitatively confirm that the selected permanent corrective action(s) (PCA) will resolve the problem for the customer. 

Steps to choosing a PCA may include:

Determining if you require further expertise

Ensuring the 5W2Hs are defined correctly

Carrying out a decision analysis and risk assessment

Considering alternative measures

Collecting evidence to prove the PCA will be effective

Your team decides to roll out the training used in the interim plan to all employees, with monthly company-wide workshops on improving well-being. You also plan to implement meetings, innovation sessions, and team-coaching training for managers. Lastly, you suggest adopting software to improve communication and collaboration. 

D6: Implement your corrective actions

Once all parties have agreed on a solution, the next step is to create an action plan to remove the root causes and escape points. Once the solution is in effect, you can remove your interim containment actions.

After seeing success with the training in the interim phase, your stakeholders approve all of your team’s proposed PCAs. Your representative from HR also plans to implement periodic employee wellness checks to track employee morale .

To ensure your corrective action was a success, monitor the results, customer, or employee feedback over a long period of time and take note of any negative effects. Setting up “controls” like employee wellness checks will help you validate whether your solution is working or more needs to be done. 

D7: Take preventive measures

One of the main benefits of using the 8D method is the improved ability to identify necessary systematic changes to prevent future issues from occurring. Look for ways to improve your management systems, operating methods, and procedures to not only eliminate your current problem, but stop similar problems from developing later on.

Based on our example, the training your team suggested is now adopted in the new manager onboarding curriculum. Every manager now has a “meeting system” that all meetings must be guided by, and workloads and projects are managed as a team within your new collaboration software . Innovation is improving, and morale is at an all-time high!

D8: Celebrate with your team

The 8D method of problem-solving is impossible to accomplish without dedicated team members and first-class collaboration. Once notes, lessons, research, and test data are documented and saved, congratulate your teammates on a job well done! Make an effort to recognize each individual for their contribution to uncovering a successful solution.

8D report template and example

Check out our 8D report template below to help you record your findings as you navigate through the eight disciplines of problem solving. This is a formal report that can be used as a means of communication within companies, which makes for transparent problem-solving that you can apply to the entire production or process chain.

Benefits of using the 8D method

The 8D method is one of the most popular problem-solving strategies for good reason. Its strength lies in teamwork and fact-based analyses to create a culture of continuous improvement —making it one of the most effective tools for quality managers. The benefits of using the 8D method include: 

Improved team-oriented problem-solving skills rather than relying on an individual to provide a solution

Increased familiarity with a problem-solving structure

A better understanding of how to use basic statistical tools for problem-solving

Open and honest communication in problem-solving discussions

Prevent future problems from occurring by identifying system weaknesses and solutions

Improved effectiveness and efficiency at problem-solving

Better collaboration = better problem solving

No matter how good a manager you are, production and process issues are inevitable. It’s how you solve them that separates the good from the great. The 8D method of problem solving allows you to not only solve the problem at hand but improve team collaboration, improve processes, and prevent future issues from arising. 

Try Asana’s project management tool to break communication barriers and keep your team on track.

Related resources

What are story points? Six easy steps to estimate work in Agile

What is a flowchart? Symbols and types explained

How to choose project management software for your team

7 steps to complete a social media audit (with template)

• Skip to main content
• Skip to primary sidebar
• Skip to footer

Additional menu

The 5 steps of the solving problem process

August 17, 2023 by MindManager Blog

Whether you run a business, manage a team, or work in an industry where change is the norm, it may feel like something is always going wrong. Thankfully, becoming proficient in the problem solving process can alleviate a great deal of the stress that business issues can create.

Understanding the right way to solve problems not only takes the guesswork out of how to deal with difficult, unexpected, or complex situations, it can lead to more effective long-term solutions.

In this article, we’ll walk you through the 5 steps of problem solving, and help you explore a few examples of problem solving scenarios where you can see the problem solving process in action before putting it to work.

Understanding the problem solving process

When something isn’t working, it’s important to understand what’s at the root of the problem so you can fix it and prevent it from happening again. That’s why resolving difficult or complex issues works best when you apply proven business problem solving tools and techniques – from soft skills, to software.

The problem solving process typically includes:

• Pinpointing what’s broken by gathering data and consulting with team members.
• Figuring out why it’s not working by mapping out and troubleshooting the problem.
• Deciding on the most effective way to fix it by brainstorming and then implementing a solution.

While skills like active listening, collaboration, and leadership play an important role in problem solving, tools like visual mapping software make it easier to define and share problem solving objectives, play out various solutions, and even put the best fit to work.

Before you can take your first step toward solving a problem, you need to have a clear idea of what the issue is and the outcome you want to achieve by resolving it.

For example, if your company currently manufactures 50 widgets a day, but you’ve started processing orders for 75 widgets a day, you could simply say you have a production deficit.

However, the problem solving process will prove far more valuable if you define the start and end point by clarifying that production is running short by 25 widgets a day, and you need to increase daily production by 50%.

Once you know where you’re at and where you need to end up, these five steps will take you from Point A to Point B:

• Figure out what’s causing the problem . You may need to gather knowledge and evaluate input from different documents, departments, and personnel to isolate the factors that are contributing to your problem. Knowledge visualization software like MindManager can help.
• Come up with a few viable solutions . Since hitting on exactly the right solution – right away – can be tough, brainstorming with your team and mapping out various scenarios is the best way to move forward. If your first strategy doesn’t pan out, you’ll have others on tap you can turn to.
• Choose the best option . Decision-making skills, and software that lets you lay out process relationships, priorities, and criteria, are invaluable for selecting the most promising solution. Whether it’s you or someone higher up making that choice, it should include weighing costs, time commitments, and any implementation hurdles.
• Put your chosen solution to work . Before implementing your fix of choice, you should make key personnel aware of changes that might affect their daily workflow, and set up benchmarks that will make it easy to see if your solution is working.
• Evaluate your outcome . Now comes the moment of truth: did the solution you implemented solve your problem? Do your benchmarks show you achieved the outcome you wanted? If so, congratulations! If not, you’ll need to tweak your solution to meet your problem solving goal.

In practice, you might not hit a home-run with every solution you execute. But the beauty of a repeatable process like problem solving is that you can carry out steps 4 and 5 again by drawing from the brainstorm options you documented during step 2.

Examples of problem solving scenarios

The best way to get a sense of how the problem solving process works before you try it for yourself is to work through some simple scenarios.

Here are three examples of how you can apply business problem solving techniques to common workplace challenges.

Scenario #1: Manufacturing

Building on our original manufacturing example, you determine that your company is consistently short producing 25 widgets a day and needs to increase daily production by 50%.

Since you’d like to gather data and input from both your manufacturing and sales order departments, you schedule a brainstorming session to discover the root cause of the shortage.

After examining four key production areas – machines, materials, methods, and management – you determine the cause of the problem: the material used to manufacture your widgets can only be fed into your equipment once the machinery warms up to a specific temperature for the day.

Your team comes up with three possible solutions.

• Leave your machinery running 24 hours so it’s always at temperature.
• Invest in equipment that heats up faster.
• Find an alternate material for your widgets.

After weighing the expense of the first two solutions, and conducting some online research, you decide that switching to a comparable but less expensive material that can be worked at a lower temperature is your best option.

You implement your plan, monitor your widget quality and output over the following week, and declare your solution a success when daily production increases by 100%.

Scenario #2: Service Delivery

Business training is booming and you’ve had to onboard new staff over the past month. Now you learn that several clients have expressed concern about the quality of your recent training sessions.

After speaking with both clients and staff, you discover there are actually two distinct factors contributing to your quality problem:

• The additional conference room you’ve leased to accommodate your expanding training sessions has terrible acoustics
• The AV equipment you’ve purchased to accommodate your expanding workforce is on back-order – and your new hires have been making do without

You could look for a new conference room or re-schedule upcoming training sessions until after your new equipment arrives. But your team collaboratively determines that the best way to mitigate both issues at once is by temporarily renting the high-quality sound and visual system they need.

Using benchmarks that include several weeks of feedback from session attendees, and random session spot-checks you conduct personally, you conclude the solution has worked.

Scenario #3: Marketing

You’ve invested heavily in product marketing, but still can’t meet your sales goals. Specifically, you missed your revenue target by 30% last year and would like to meet that same target this year.

After collecting and examining reams of information from your sales and accounting departments, you sit down with your marketing team to figure out what’s hindering your success in the marketplace.

Determining that your product isn’t competitively priced, you map out two viable solutions.

• Hire a third-party specialist to conduct a detailed market analysis.
• Drop the price of your product to undercut competitors.

Since you’re in a hurry for results, you decide to immediately reduce the price of your product and market it accordingly.

When revenue figures for the following quarter show sales have declined even further – and marketing surveys show potential customers are doubting the quality of your product – you revert back to your original pricing, revisit your problem solving process, and implement the market analysis solution instead.

With the valuable information you gain, you finally arrive at just the right product price for your target market and sales begin to pick up. Although you miss your revenue target again this year, you meet it by the second quarter of the following year.

Kickstart your collaborative brainstorming sessions and  try MindManager for free today !

Ready to take the next step?

MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster.

Why choose MindManager?

MindManager® helps individuals, teams, and enterprises bring greater clarity and structure to plans, projects, and processes. It provides visual productivity tools and mind mapping software to help take you and your organization to where you want to be.

Explore MindManager

Protect your data

This site uses cookies and related technologies for site operation, and analytics as described in our Privacy Policy . You may choose to consent to our use of these technologies, reject non-essential technologies, or further manage your preferences.

• Career Advice
• Five Steps To Create a...

Five Steps To Create a Problem-Solving Process (Plus Tips!)

8 min read · Updated on August 31, 2023

Conquering workplace challenges fuses strategy and art

Sometimes, it can seem that obstacles are as prevalent as opportunities. When you're good at solving problems, though, you have the power to navigate issues with relative ease. In fact, problem solving is more than a skill - it's a tool that you can use to fuel career growth and success. 

As an effective problem solver, you use innovative thinking, demonstrate leadership, and build resilience and confidence. Often, the people you work with come to trust that you're the person to go to when there's a challenge. This could be just the stepping stone you need to move into a leadership role . 

Of course, problems range in complexity depending on your industry. But by having a five-step problem-solving process in place, you can enhance both efficiency and effectiveness. In this article, we'll explore tips to help you master the skill, strategy, and art of problem solving.

Identify, analyze, resolve, execute, evaluate

What's the definition of problem solving? It's quite simple. You have to come up with solutions to challenges or issues. 

The first step to fixing any problem is recognizing that there is one. Then the trick is to engage with each step of the problem-solving process to incorporate analytical thinking , adaptability, and collaboration skills to build a framework for addressing challenges and driving positive outcomes. 

Step 1: Identify

Identifying the problem may be simple, or it could be a detailed cognitive process that breaks the issue into manageable components. Either way, what you do during the identify step of the problem-solving process sets the stage for the next steps in problem solving. 

Step 2: Analyze

Consider underlying factors and devise strategies. Here's where the art part of your problem-solving strategy becomes important. As you gather details about the problem, employ critical thinking to uncover the root causes and potential implications. 

Step 3: Resolve

Once you have a thorough understanding of the issue, it's time to get creative. Develop some reasonable solutions that are aligned with the capabilities of your team and the mission, vision, and values of your company. Your problem-solving method could involve any one of the following - or even a combination of several:

Encourage your team to learn new technologies

Reallocate some resources

Restructure organizational elements

Draft new operating procedures

Implement brainstorming sessions

Develop metrics 

Step 4: Execute

After you've outlined the solutions and decided which ones you think will resolve the problem, it's time to put them into place. The execution phase is the bridge between theory and practice. 

Translate the solutions into actionable steps that produce tangible results

Clearly communicate the actionable steps to the relevant stakeholders - your team, colleagues, or managers

Delegate tasks based on team member acumen

Empower those you delegate tasks to by fostering a sense of ownership

Track the progress of your solutions

Overcome challenges, including unforeseen obstacles and stakeholder resistance

Step 5: Evaluate

Just because you think you solved the problem doesn't mean you actually did. It's critical to double-check your work and make sure there are no hiccups. Here's a list of 10 evaluative questions you can work through, to ensure that your problem-solving solutions were impactful:

Did the solutions effectively address the root cause of the problem?

Do you see the desired results? 

What impact can you see on your team or the company?

Has there been a noticeable enhancement in efficiency, productivity, or overall performance?

Have any unintended consequences or new challenges arisen as a result of the implemented solution?

Can the solution be sustained in the long term, or is it a short-term fix?

Have stakeholders, such as team members or customers, reported positive experiences or feedback?

Have the predefined performance metrics and goals been achieved or exceeded?

Are there any new aspects of the problem that emerged after implementing the solution?

Which aspects of the solution would you retain and which would you modify?

When you reflect on the outcome of your problem solving strategies, you not only validate the effectiveness of your approach but you can also find insights for continuous improvement and refinement for future endeavors. 

Problem solving isn't just for leaders

Sometimes, it seems that only managers and senior executives can engage in effective workplace problem solving. That's simply not the case. It doesn't matter if you're a fresher who's just graduated college or someone with decades of experience, you can employ problem-solving techniques and become a master problem solver. 

You've likely heard of hard skills and soft skills ; you may have even seen problem solving lumped in with other soft skills. There are three essential soft skills you'll need to be good at to solve workplace problems:

Analytical thinking

Adaptability, collaboration.

Let's start with a foundational problem-solving skill. Analytical thinking is something you'll use in every step of your five-step problem-solving process, from identifying the problem to coming up with and executing solutions and measuring the success of those solutions. Being able to analyze trends, anticipate shifts, and make informed decisions along the problem-solving path, you'll be assured of success. 

A real-world example: Sally is a new graduate and has secured her first job. After a few days at work, she wants to start making a name for herself by identifying a dip in sales. She dissects the customer engagement data and finds there has been a shift in consumer preferences. She knows that a new targeted marketing strategy could re-engage customers and bring sales back up. 

Toss aside any notions that the plans you set into place to solve a problem are set in stone. They're not! Being able to make course corrections to change outcomes is at the heart of being adaptable . This soft skill becomes more and more important every day because of how quickly things change in business. Technology advances, economic fluctuations come into play, and unforeseen global events can wreak havoc on the best-laid problem-solving solutions. Think about how adaptable people had to be a few years ago when Covid shut the world down – there were tons of never-before-faced problems that ultimately got solved. 

A real-world example : John has been employed in the technology sector for a little over 20 years. He's achieved the coveted role of CTO and found himself overseeing a team that had to transition into remote work. Because he's kept up with emerging technologies and the latest trends, he sets up processes that allow his team to enjoy a seamless shift with minimal impact on productivity.

When you have a problem-solving project in front of you, you'll often have to get people involved to help you to execute the solutions you come up with. Effective communication , organizational synergy, and a harmonious fusion of experiences can lend fresh insights to problem solving. 

A real-world example: Marcus is involved in a complex project involving supply chain optimization. He works with geographically-dispersed stakeholders of all levels and has become an expert at pooling together specialized knowledge to create holistic solutions. 

How do great problem-solving skills affect your career goals?

Challenges in life and at work are inevitable; by aligning your problem-solving skills with your career goals, not only will you be able to overcome immediate challenges, but you'll also cultivate a powerful tool for your job search toolkit. When you're good at solving problems and can show that you're good at it through accomplishment statements on your resume, your career trajectory will likely be positively impacted. In fact, there are several success stories that prove the journey to excellence is marked by innovative problem solving. Here are just a few:

Elon Musk: Musk's SpaceX faced immense challenges in developing reusable rockets. His innovative, problem-solving approach led to breakthrough solutions, revolutionizing space travel.

Indra Nooyi: As the former CEO of PepsiCo, Nooyi tackled the declining demand for sugary beverages by diversifying the product portfolio and focusing on healthier options, showcasing adaptability and strategic problem solving.

Nelson Mandela: Mandela's ability to collaborate across racial divides and negotiate solutions was instrumental in ending apartheid in South Africa.

Grace Hopper: A computer science pioneer, Hopper's analytical thinking led to the development of the first compiler, revolutionizing programming.

An invaluable asset

As you progress in your career, your skill in resolving a problem will set you apart from the rest of the job-seeking crowd as an invaluable asset. Whether you're identifying opportunities for growth, addressing operational inefficiencies, or strategizing through crises, the ability to solve problems creatively and effectively can become one of the key drivers for the advancement of your career. Essentially, strong problem-solving skills empower you to overcome challenges, seize opportunities, and carve a path of consistent achievement in your professional journey.

TopResume can help you to showcase exceptional problem-solving skills on your resume. Why not submit yours for a free resume review today, to make sure that you're giving this skill the prominence it deserves?

Recommended reading:

How to List Problem Solving Skills on a Resume

Divergent Thinking: Should You Include This Skill on Your Resume?

Higher Order Thinking Explained

Related Articles:

Don't “Snowplow” Your Kids' Job Search — Set Them Up for Success Instead

What Kind of Job Candidate Are You?

Why December is the Best Time of Year to Look for a Job

See how your resume stacks up.

Career Advice Newsletter

Our experts gather the best career & resume tips weekly. Delivered weekly, always free.

Thanks! Career advice is on its way.

Share this article:

Let's stay in touch.

Subscribe today to get job tips and career advice that will come in handy.

Your information is secure. Please read our privacy policy for more information.

Researched by Consultants from Top-Tier Management Companies

Powerpoint Templates

Icon Bundle

Kpi Dashboard

Professional

Business Plans

Swot Analysis

Gantt Chart

Business Proposal

Marketing Plan

Project Management

Business Case

Business Model

Cyber Security

Business PPT

Digital Marketing

Digital Transformation

Human Resources

Product Management

Artificial Intelligence

Company Profile

Acknowledgement PPT

PPT Presentation

Reports Brochures

One Page Pitch

Interview PPT

All Categories

Top 10 Problem Solving Templates with Samples and Examples

In today's competitive business world, excelling at problem solving is crucial for achieving success. A recent study by McKinsey has shown that companies that are skilled at problem solving tend to outperform their peers in terms of revenue growth and shareholder returns. In fact, the top quartile of problem-solving organizations achieved 50% higher revenue growth and 33% higher total returns to shareholders compared to the bottom quartile. Therefore, it's clear that mastering problem solving is essential for any business to thrive.

Finding effective solutions to business challenges, however, can be daunting. That's where SlideTeam's Problem-solving Templates come in to provide a step-by-step approach enabling you to break down complex issues into manageable parts and develop effective solutions. We offer a range of templates, including SWOT analysis, Fishbone diagrams, and Root Cause Analysis, that will equip you with the tools you need to tackle any business problem.

Problem-Solving Templates

If you're tired of struggling to find solutions to the challenges your business faces, explore these Problem-Solving Templates. Don't let obstacles hold your business back – try our templates today and take your business to the next level.

Let’s begin.

Template 1: Organizational Problem-Solving Tool PowerPoint Presentation

For an organization, problem-solving is required in all its operational aspects-right, from planning, controlling, marketing, and manufacturing to managing financial aspects, products as well as customers. This PPT template presents slides that enable an organization to analyze information across all its operations and departments and identify problems and then solve these problems. This editable PPT Template enables an organization to plan its progress path by allocating the right people and resources to solve problems.

Download Now!

Template 2: Problem Solving Approach Business Organizational Analysis Assessment Systems

This editable PPT Template with its attractive graphics and design, enables any business to adopt the right approach to problem-solving. The template enables any organization to analyze different approaches like three-phase approach, collaborative approach, strategy-based approach, etc.

Template 3: Sample A3 Problem Solving Report Collection of Quality Control Templates PPT Diagrams

This easy-to-use PPT template helps organizations solve problems related to quality control. Using this template, an organization can identify the root cause of the problem and the background of the problem and formulate a plan of action to solve the problem. It includes sections for the current situation, checking, acting, and rectifying the errors.

Template 4: Sample A3 Problem Solving Report

This customizable and readily downloadable PPT template enables an organization to solve problems that are reflected in quality assurance reports. Any business can identify a quality-related problem, its background, its cause, as well as other aspects of the problem and then find the best solution to the problem using this template.

Template 5: Optimizing Transformation Strawman Proposal

For any organization, it is important to achieve operational efficiency. However, several issues are often faced when it comes to the operational aspects of a business, and identifying these is mandatory for an organization. Using this PPT Template, an organization can analyze its operational problems and discuss in detail how technology can be used to solve the problem and bring about a transformation that can help to enhance operational efficiency.

Template 6: Collaborative Problem Solving and Assessment Approach

This PPT template, available for instant download, helps an organization to use a collaborative problem-solving and assessment approach to analyze problems related to new products, technologies, ideas, etc., and adopt the best practices to solve the problem.

Template 7: Situation Complication Resolution Framework for Problem Solving

This attractive PPT Template, with its colorful graphics, enables an organization to adopt the framework model to solve a problem. This model enables any business to analyze the current situation, identify the complications associated with the situation, and then find the solution or the best way to resolve the problem.

Template 8: Five-circle Arrow Process for Problem Solving

This adaptable PPT template, with its attractive design, provides a five-circle arrow process for solving problems related to any aspect of the organization. Using this PPT template, an organization can define a problem, generate new ideas to solve the problem, evaluate and select solutions and implement and evaluate the solutions to ensure that the problem gets solved in the most optimal manner.

Template 9: 3-Step Process of Problem-solving Analysis

The process of problem-solving is not always easy because, most of the time, a business fails to identify the problem. Using this customizable PPT Template, a business can adopt a 3-step approach to problem-solving. With the help of this template, an organization can implement the stages of problem identification, problem analysis, and solution development to solve the problem in the most effective manner.

Template 10: 6 segments of problem-solving model

This PPT template presents 6 steps to solve a problem that an organization may face in any of its operational aspects. This PPT template is easy to edit and enables any business to adopt the stages of defining a problem, determining the root cause of the problem, evaluating the outcome, selecting a solution, implementing the solution, and developing alternative solutions. This model, when adopted by an organization, enables it to find the most optimal solution to the problem.

The Final Word

Every problem is a gift - without problems, we would not grow." - Tony Robbins. This quote highlights the importance of embracing challenges as opportunities for growth and development. When businesses approach problem-solving with a positive mindset and a willingness to learn, they can turn even the most challenging situations into valuable learning experiences.

Now that you know how using problem-solving templates can assist you in streamlining the entire process, it’s time to download these templates and get started.

FAQs on Problem-Solving

What are the 7 steps to problem-solving.

A business, during its operations, may face several problems that need to be solved so that the problem does not impact the organization in an adverse manner. However, to solve a problem in the most efficient manner, a business must adopt a seven-step approach to problem-solving. These steps include:

• Identifying the problem.
• Analyzing the problem.
• Describing the problem and all its parameters.
• Identifying the root cause of the problem.
• Developing solutions to solve the problem.
• Implementing the solution that seems to be the most effective.
• Measuring the results.

Why is problem-solving important?

Problem-solving enables an organization to handle unexpected situations or face challenges that it may face during its operations. For every organization, problem-solving is important as it enables the organization to:

• Identify activities, processes, and people that are not working in an efficient manner.
• Identify risks and address these risks.
• Implement changes when required.
• Enhance performance and productivity.
• Innovate and execute new ideas.
• Make effective decisions.

What are the five problem-solving skills?

Problem-solving is not an easy task, and any consultant in the organization who works to solve problems needs to exhibit some specific skills. These skills include but are not limited to:

• Creativity that enables the consultant to assess and analyze the problem from various perspectives to come up with the best idea.
• Communication to ensure that the problem and its solutions are easily communicated with others in the organization.
• Teamwork so that everyone in the team can work to solve the problem.
• Critical analysis to think analytically about a problem and solve it in the best manner possible.
• Information processing to process and analyze all information that is associated with the problem.

What are the 4 steps of problem-solving?

Problem-solving needs to be carried out using a series of steps that include:

• Identifying and analyzing the problem so that its cause is known.
• Planning and determining how to solve the problem by finding various solutions.
• Implementing the chosen solution to solve the problem.
• Evaluating solutions to know whether the problem has been resolved or not. 

Related posts:

• How to Design the Perfect Service Launch Presentation [Custom Launch Deck Included]
• Quarterly Business Review Presentation: All the Essential Slides You Need in Your Deck
• [Updated 2023] How to Design The Perfect Product Launch Presentation [Best Templates Included]
• 99% of the Pitches Fail! Find Out What Makes Any Startup a Success

Liked this blog? Please recommend us

Top 5 Data Flow Chart Templates With Samples and Examples

Must-Have Data Analyst Resume Sample Templates for Job Seekers

This form is protected by reCAPTCHA - the Google Privacy Policy and Terms of Service apply.

Digital revolution powerpoint presentation slides

Sales funnel results presentation layouts

3d men joinning circular jigsaw puzzles ppt graphics icons

Business Strategic Planning Template For Organizations Powerpoint Presentation Slides

Future plan powerpoint template slide

Project Management Team Powerpoint Presentation Slides

Brand marketing powerpoint presentation slides

Launching a new service powerpoint presentation with slides go to market

Agenda powerpoint slide show

Four key metrics donut chart with percentage

Engineering and technology ppt inspiration example introduction continuous process improvement

Meet our team representing in circular format

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

How it works

For Business

Join Mind Tools

Article • 11 min read

Getting to the Root of a Problem Quickly

By the Mind Tools Content Team

5 Whys Root-Cause Analysis

Have you ever had a problem that refused to go away? No matter what you did, sooner or later it would return, perhaps in another form.

Stubborn or recurrent problems are often symptoms of deeper issues. "Quick fixes" may seem convenient, but they often solve only the surface issues and waste resources that could otherwise be used to tackle the real cause.

In this article and in the video, below, we look at the 5 Whys technique (sometimes known as 5Y). This is a simple but powerful tool for cutting quickly through the outward symptoms of a problem to reveal its underlying causes – so that you can deal with it once and for all.

Origins of the 5 Whys Technique

Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries, developed the 5 Whys technique in the 1930s. It became popular in the 1970s, and Toyota still uses it to solve problems today.

Toyota has a "go and see" philosophy. This means that its decision making is based on an in-depth understanding of what's actually happening on the shop floor , rather than on what someone in a boardroom thinks might be happening.

The 5 Whys technique is true to this tradition, and it is most effective when the answers come from people who have hands-on experience of the process or problem in question.

The method is remarkably simple: when a problem occurs, you drill down to its root cause by asking "Why?" five times. Then, when a counter-measure becomes apparent, you follow it through to prevent the issue from recurring.

The 5 Whys uses "counter-measures," rather than "solutions." A counter-measure is an action or set of actions that seeks to prevent the problem from arising again, while a solution may just seek to deal with the symptom. As such, counter-measures are more robust, and will more likely prevent the problem from recurring.

When to Use a 5 Whys Analysis

You can use 5 Whys for troubleshooting, quality improvement, and problem solving, but it is most effective when used to resolve simple or moderately difficult problems.

It may not be suitable if you need to tackle a complex or critical problem. This is because 5 Whys can lead you to pursue a single track, or a limited number of tracks, of inquiry when, in fact, there could be multiple causes. In cases like these, a wider-ranging method such as Cause and Effect Analysis or Failure Mode and Effects Analysis may b e more effective.

This simple 5 Whys technique, however, can often direct you quickly to the root cause of a problem. So, whenever a system or process isn't working properly, give it a try before you embark on a more in-depth approach – and certainly before you attempt to develop a solution.

The tool's simplicity gives it great flexibility, too, and 5 Whys combines well with other methods and techniques, such as Root Cause Analysis . It is often associated with Lean Manufacturing , where it is used to identify and eliminate wasteful practices. It is also used in the analysis phase of the Six Sigma quality improvement methodology.

How to Use the 5 Whys

The model follows a very simple seven-step process: [1]

1. Assemble a Team

Gather together people who are familiar with the specifics of the problem, and with the process that you're trying to fix. Include someone to act as a facilitator , who can keep the team focused on identifying effective counter-measures.

2. Define the Problem

If you can, observe the problem in action. Discuss it with your team and write a brief, clear problem statement that you all agree on. For example, "Team A isn't meeting its response time targets" or "Software release B resulted in too many rollback failures."

Then, write your statement on a whiteboard or sticky note, leaving enough space around it to add your answers to the repeated question, "Why?"

3. Ask the First "Why?"

Ask your team why the problem is occurring. (For example, "Why isn't Team A meeting its response time targets?")

Asking "Why?" sounds simple, but answering it requires serious thought. Search for answers that are grounded in fact: they must be accounts of things that have actually happened, not guesses at what might have happened.

This prevents 5 Whys from becoming just a process of deductive reasoning, which can generate a large number of possible causes and, sometimes, create more confusion as you chase down hypothetical problems.

Your team members may come up with one obvious reason why, or several plausible ones. Record their answers as succinct phrases, rather than as single words or lengthy statements, and write them below (or beside) your problem statement. For example, saying "volume of calls is too high" is better than a vague "overloaded."

4. Ask "Why?" Four More Times

For each of the answers that you generated in Step 3, ask four further "whys" in succession. Each time, frame the question in response to the answer you've just recorded.

What Is a 5 Whys Template?

The diagram, below, shows an example of 5 Whys in action, following a single lane of inquiry.

Figure 1: 5 Whys Example (Single Lane)

The 5 Whys method also allows you to follow multiple lanes of inquiry. An example of this is shown in Figure 2, below.

In our example, asking "Why was the delivery late?" produces a second answer (Reason 2). Asking "Why?" for that answer reveals a single reason (Reason 1), which you can address with a counter-measure.

Similarly, asking "Why did the job take longer than expected?" has a second answer (Reason 2), and asking "Why?" at this point reveals a single reason (Reason 1). Another "Why?" here identifies two possibilities (Reasons 1 and 2) before a possible counter-measure becomes evident.

There is also a second reason for "Why we ran out of printer ink" (Reason 2), and a single answer for the next "Why?" (Reason 1), which can then be addressed with a counter-measure.

Figure 2: 5 Whys Example (Multiple Lanes)

Step 5. Know When to Stop

You'll know that you've revealed the root cause of the problem when asking "why" produces no more useful responses, and you can go no further. An appropriate counter-measure or process change should then become evident. (As we said earlier, if you're not sure that you've uncovered the real root cause, consider using a more in-depth problem-solving technique like Cause and Effect Analysis , Root-Cause Analysis , or FMEA .)

If you identified more than one reason in Step 3, repeat this process for each of the different branches of your analysis until you reach a root cause for each one.

6. Address the Root Cause(s)

Now that you've identified at least one root cause, you need to discuss and agree on the counter-measures that will prevent the problem from recurring.

7. Monitor Your Measures

Keep a close watch on how effectively your counter-measures eliminate or minimize the initial problem. You may need to amend them, or replace them entirely. If this happens, it's a good idea to repeat the 5 Whys process to ensure that you've identified the correct root cause.

Appreciation

A similar question-based approach known as "appreciation" can help you to uncover factors in a situation that you might otherwise miss.

It was originally developed by the military to assist commanders in gaining a comprehensive understanding of any fact, problem or situation. But you can also apply it in the workplace.

Starting with a fact, you first ask the question, "So what?" – in other words, what are the implications of that fact? Why is this fact important?

You then continue asking that question until you've drawn all possible conclusions from it.

The major difference between this and the 5 Whys technique is that appreciation is often used to get the most information out of a simple fact or statement, while 5 Whys is designed to drill down to the root of a problem.

Tips for Using the 5 Whys Technique

• Try to move quickly from one question to the next. That way, you'll have the full picture before you jump to any conclusions.
• The "5" in 5 Whys is really just a " rule of thumb ." In some cases, you may need to ask "Why?" a few more times before you get to the root of the problem. In other cases, you may reach this point before you ask your fifth "Why?" If you do, make sure that you haven't stopped too soon, and that you're not simply accepting "knee-jerk" responses.
• Know when to stop! The important point is to stop asking "Why?" when you stop producing useful responses.

Frequently Asked Questions About 5 Whys

1. what is the 5 whys technique.

The 5 Whys Technique is a problem-solving method involving repeatedly asking "why?" It's a way of quickly getting to the root cause of a situation.

2. Who Invented 5 Whys?

The 5 Whys technique was invented in the 1930s by Sakichi Toyoda, the Japanese industrialist, inventor, and founder of Toyota Industries.

5 Whys Infographic

See our infographic on the 5 Whys and use it to get to the root of your problems!

Bear in mind that appreciation can restrict you to one line of thinking. For instance, once you've answered your first "So what?" question, you might follow a single line of inquiry to its conclusion. To avoid this, repeat the appreciation process several times over to make sure that you've covered all bases.

The 5 Whys strategy is a simple, effective tool for uncovering the root of a problem. You can use it in troubleshooting, problem-solving, and quality-improvement initiatives.

Start with a problem and ask why it is occurring. Make sure that your answer is grounded in fact, and then ask the question again. Continue the process until you reach the root cause of the problem, and you can identify a counter-measure that will prevent it from recurring.

Bear in mind that this questioning process is best suited to simple or moderately difficult problems. Complex problems may benefit from a more detailed approach, although using 5 Whys will still give you useful insights.

[1] Pojasek, R. (2000). 'Asking "Why?" Five Times,' Environmental Quality Management , Volume 10, Issue 1, 79–84. Available here . [Accessed July 1, 2022.]

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Using root cause analysis.

Find the Root of Your Problems

Root Cause Analysis

Tracing a Problem to Its Origins

Add comment

Comments (0)

Be the first to comment!

Gain essential management and leadership skills

Busy schedule? No problem. Learn anytime, anywhere. 

Subscribe to unlimited access to meticulously researched, evidence-based resources.

Join today and save on an annual membership!

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Latest Updates

Better Public Speaking

How to Build Confidence in Others

Mind Tools Store

About Mind Tools Content

Discover something new today

How to create psychological safety at work.

Speaking up without fear

How to Guides

Pain Points Podcast - Presentations Pt 1

How do you get better at presenting?

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

Strategic speed: how to accelerate execution.

Jocelyn Davis

Expert Interviews

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

Home 5 Step Problem Solving Process Diagram for PowerPoint Step 2 of 5 Steps Problem Solving Diagram Template

Step 2 of 5 Steps Problem Solving Diagram Template

Return to 5 Step Problem Solving Process Diagram for PowerPoint .

Download unlimited PowerPoint templates, charts and graphics for your presentations with our annual plan.

Template Tags:

Download unlimited content, our annual unlimited plan let you download unlimited content from slidemodel. save hours of manual work and use awesome slide designs in your next presentation..

A guide to problem framing: best practices & templates

When creating solutions and products, it’s critical to correctly frame the problem you’re attempting to solve. 

Remember the Google Glass? What about the Segway? Taken on their own account, these were groundbreaking products with cutting-edge technology. No one had seen anything like them before. Yet they failed for a simple reason: They were solutions in search of a problem.

Now imagine if their creators had spent more time trying to understand the problem their customers faced. Imagine they had actually tried to identify a real challenge and properly define how it could be addressed. The result would have likely been closer to a Tesla or even an iPhone — at the very least, we wouldn’t be talking about them in nearly the same way.

This shows just how important it is to frame a problem before trying to solve it. Let’s go over in detail how you can apply problem framing to your next project.

What is problem framing?

Problem framing is a process for analyzing, understanding, and ultimately defining a problem or challenge in order to develop an effective solution. While it can be done on an individual level, it is typically practiced across teams so that you can achieve alignment and work more cohesively toward an agreed-upon outcome. 

In short, problem framing is an opportunity to take a step back, assess the landscape of your problem and break down its root causes, then focus on a solution that is most likely to lead to the outcome you want.

Why problem framing is critical for better outcomes

Framing the problem is important because it sets the direction and scope of the solution design process, ensuring that efforts are focused on addressing the core issues. It helps avoid wasted time and resources on irrelevant or superficial solutions.

Good design and effective iteration can help improve a product, but they won’t tell you if you’re addressing the right problem — only problem framing can do that. Here are some ways this process can ensure your solution achieves better results:

• It provides clarity. Whether your team isn’t sure what problem they’re facing or can’t reach an agreement, taking the time to break the problem apart can ensure everyone understands it. And that is crucial to developing a solution that actually works.
• It narrows the scope. With a better understanding of the problem, you can eliminate everything but the most essential aspects that need to be addressed. That means only addressing underlying issues instead of just their symptoms.
• It achieves alignment. By having a clear definition in hand, you can ensure that all team members and stakeholders share a common understanding of the problem and how to address it. This will help reduce misunderstandings and conflict.
• It increases efficiency. While some may think problem framing is an extra step, it can actually help keep you from wasting resources and time by preventing you from focusing on irrelevant or ineffective solutions.

How to frame a problem

Whether you think you have a good idea of your problem or have no clue where to begin, learning how to properly frame it can give you new insights into how to solve it. Here’s a process for doing just that.

Create a problem statement

A good first step is to make sure that everyone can agree on what exactly the problem is. This is a great opportunity to write out a problem statement, or a clear and concise explanation of the problem or challenge you intend to solve.

The goal behind writing a problem statement is to describe the problem as comprehensively as possible, while also spurring your team into action. If your team can’t even reach an agreement on what the problem is, then try to discuss the problem from multiple angles to ensure you’re incorporating multiple perspectives. This will help you achieve alignment. 

Even when everyone already has a good idea of the problem, this step can still help ensure complete clarity by taking the simple but effective step of making your team write it down. Learn more about what goes into creating a good problem statement in our full guide .

Identify and understand the problem's root cause

Although identifying your problem’s root cause or causes should be a part of writing out your problem statement , it’s important enough to deserve a discussion on its own. After all, if you are just focusing on the symptoms of your problem, then any solution you develop will ultimately fail.

The key to uncovering a problem’s root cause is to ask why it is happening, rather than what. Typically, there will be multiple answers to this. One way to start organizing and categorizing these different causes and their various effects is by using a fishbone diagram . Start out by writing down your problem, then come up with different categories that could be contributing to it. From there, start brainstorming different causes.

Once you have everything laid out cleanly, you can vote on what you think are the most significant contributors — or, if necessary, even rethink the problem itself.

Empathize with the end-users of the problem

Once you have a good idea of your problem and can articulate it, you also need to ensure that this is a problem your stakeholders face. That means being able to properly understand and empathize with their needs.

To accomplish this, consider organizing an empathy mapping session . Start out by gathering a diverse range of stakeholders in order to reduce biases and leverage different perspectives. Ask them to share their opinion regarding the product, service, or situation, encouraging open-ended responses. As you gather this feedback, divide it into four different categories: thoughts, feelings, actions, and observations —then start looking for areas of improvement. This is where your highest priority problems will be.

The act of interviewing your stakeholders, writing down their responses, and organizing them across different categories should give you a much deeper understanding of the user’s point of view and their needs. 

Frame the problem to brainstorm solutions

With your user research in hand and your problem statement honed, it’s time to start framing the problem in order to come up with effective solutions.

During this process, your goal should be to get your team to rethink the problem in creative ways to help you find new ways to solve it. While there are many ways to do this, the Mural problem framing template provides a simple three-step procedure that can help you explore your challenge in new ways to get the right answer. Each person must transform the problem into four different questions that invite deeper, more nuanced thinking. These questions are then discussed, voted on, and narrowed down to the most promising, providing you with a clear frame for future work.

Tips to effectively frame the problem

Thinking through problems in new ways and effectively framing them involves outside-the-box creativity , a healthy dose of empathy, and a willingness to take risks. This can be intimidating for some people. So here are some quick tips to help make this process more effective.

Start with asynchronous collaboration

Focused sessions are the most effective sessions — and what you probably want to focus on the most while problem framing is coming up with possible solutions. That’s why encouraging stakeholders, end-users, and other participants to start collaborating asynchronously on ways to reframe and rethink your problem can be so beneficial. 

Plus, getting participants to work on their own can help avoid groupthink, or the tendency to come up with ideas people will agree with rather than ideas that are actually useful. This will ultimately lead to better decisions and more effective solutions.

In-person sessions aren’t the only way to collaborate!  Learn how async collaboration can solve your meeting problem .

Map out the context of the problem

Helping your team understand the drivers and impacts of the issue you are trying to solve will help them gain a more nuanced view on why this issue exists, as well as how best to solve it. This is why bringing in end users and empathizing with their needs is so important — but there’s no reason you have to stop there. By creating a customer journey map , you can identify vital pain points in the customer experience, locate areas for improvement, and create solutions that are personalized to the customer.

Mural offers several customer journey templates to get you started. For instance, our map template lets you break down the journey across five separate components for a more granular view, while our experience diagramming template is great for examining individual customer’s experiences. 

Don't be afraid to dig deeper with stakeholders and the end-users

Fully understanding an issue and how it affects your stakeholders can take time. For some, this can be frustrating. After all, your objective is to come up with a solution, which will likely require a fair amount of design and iteration itself. 

Try to resist the urge to jump ahead. Instead, embrace the problem-framing process as much as possible by digging in deep with your stakeholders and end users. Really try to explore and understand why their problem exists in the first place so you can find a better potential solution.

Even if all this takes extra time, just remember that it’s better to properly identify and understand the problem you aim to solve rather than solving the wrong problem.

Hold a vote to prioritize solutions

If you’re fortunate, you’ll come to the end of your problem framing session with a wealth of possible solutions to choose from. But this can also be overwhelming. Which is the best course of action? How should you decide?

When faced with these questions, you could try creating a prioritization matrix . This simple tool allows you to quickly identify and weigh the most important factors when making a decision. These could include factors like risk, costs, benefits, and stakeholder interests. You can then place them on a matrix according to the criteria of your choosing, such as potential difficulty and potential impact.

Once you’ve narrowed down your solutions, you could hold a vote to further prioritize what you’ll work on next. Lucky for you, Mural comes with a built-in voting feature that makes this easy.

Hold better problem-framing sessions

Often used in the design thinking process , problem framing is an essential step for understanding the issues you need to solve and uncovering creative new solutions for addressing them. And it doesn’t have to be limited to the beginning of projects. As your projects change and evolve, problem framing can be a useful process for realigning your team and making sure they are staying focused on what matters most.

But you’re not doing it on your own. With its array of tools, templates, and features, the Mural platform is designed to help you at every step of the process: from the first sticky note, to the project’s last step in execution. 

Start designing with digital whiteboard platform or go ahead and dive into our library of templates . And don’t forget to let us know what you come up with!

Looking to level-up client engagements? Learn how to make client collaboration more engaging and personalized with this cheat-sheet.

Frequently asked questions on problem framing

What is the main focus of problem framing.

The main focus of problem framing is to define the problem accurately, understand its underlying causes, and identify its broader implications. It aims to provide a clear and comprehensive view of the problem, enabling teams to develop targeted and effective solutions.

What is the difference between problem statements and problem framing?

Problem statements simply state the issue at hand, while problem framing goes a step further by providing context, boundaries, and a deeper understanding of the problem's root causes and impact.

What are the main benefits of problem framing?

The benefits of problem framing include clear direction for the project, targeted and impactful solutions, user-centric design, fostering innovation and creativity, and improved problem-solving and decision-making. It ensures that organizations solve the right problems and achieve more successful outcomes.

About the authors

David Young

Tagged Topics

Related blog posts

How to Write Problem Statements You’ll Actually Use

How to Identify the Right Problems to Solve

4 common challenges and pitfalls in design thinking

Related blog posts.

Don't do this when using a flowchart builder

How Mural links design thinking and Agile

A guide to the Agile development lifecycle

How to master the seven-step problem-solving process

In this episode of the McKinsey Podcast , Simon London speaks with Charles Conn, CEO of venture-capital firm Oxford Sciences Innovation, and McKinsey senior partner Hugo Sarrazin about the complexities of different problem-solving strategies.

Podcast transcript

Simon London: Hello, and welcome to this episode of the McKinsey Podcast , with me, Simon London. What’s the number-one skill you need to succeed professionally? Salesmanship, perhaps? Or a facility with statistics? Or maybe the ability to communicate crisply and clearly? Many would argue that at the very top of the list comes problem solving: that is, the ability to think through and come up with an optimal course of action to address any complex challenge—in business, in public policy, or indeed in life.

Looked at this way, it’s no surprise that McKinsey takes problem solving very seriously, testing for it during the recruiting process and then honing it, in McKinsey consultants, through immersion in a structured seven-step method. To discuss the art of problem solving, I sat down in California with McKinsey senior partner Hugo Sarrazin and also with Charles Conn. Charles is a former McKinsey partner, entrepreneur, executive, and coauthor of the book Bulletproof Problem Solving: The One Skill That Changes Everything [John Wiley & Sons, 2018].

Charles and Hugo, welcome to the podcast. Thank you for being here.

Hugo Sarrazin: Our pleasure.

Charles Conn: It’s terrific to be here.

Simon London: Problem solving is a really interesting piece of terminology. It could mean so many different things. I have a son who’s a teenage climber. They talk about solving problems. Climbing is problem solving. Charles, when you talk about problem solving, what are you talking about?

Charles Conn: For me, problem solving is the answer to the question “What should I do?” It’s interesting when there’s uncertainty and complexity, and when it’s meaningful because there are consequences. Your son’s climbing is a perfect example. There are consequences, and it’s complicated, and there’s uncertainty—can he make that grab? I think we can apply that same frame almost at any level. You can think about questions like “What town would I like to live in?” or “Should I put solar panels on my roof?”

You might think that’s a funny thing to apply problem solving to, but in my mind it’s not fundamentally different from business problem solving, which answers the question “What should my strategy be?” Or problem solving at the policy level: “How do we combat climate change?” “Should I support the local school bond?” I think these are all part and parcel of the same type of question, “What should I do?”

I’m a big fan of structured problem solving. By following steps, we can more clearly understand what problem it is we’re solving, what are the components of the problem that we’re solving, which components are the most important ones for us to pay attention to, which analytic techniques we should apply to those, and how we can synthesize what we’ve learned back into a compelling story. That’s all it is, at its heart.

I think sometimes when people think about seven steps, they assume that there’s a rigidity to this. That’s not it at all. It’s actually to give you the scope for creativity, which often doesn’t exist when your problem solving is muddled.

Simon London: You were just talking about the seven-step process. That’s what’s written down in the book, but it’s a very McKinsey process as well. Without getting too deep into the weeds, let’s go through the steps, one by one. You were just talking about problem definition as being a particularly important thing to get right first. That’s the first step. Hugo, tell us about that.

Hugo Sarrazin: It is surprising how often people jump past this step and make a bunch of assumptions. The most powerful thing is to step back and ask the basic questions—“What are we trying to solve? What are the constraints that exist? What are the dependencies?” Let’s make those explicit and really push the thinking and defining. At McKinsey, we spend an enormous amount of time in writing that little statement, and the statement, if you’re a logic purist, is great. You debate. “Is it an ‘or’? Is it an ‘and’? What’s the action verb?” Because all these specific words help you get to the heart of what matters.

Want to subscribe to The McKinsey Podcast ?

Simon London: So this is a concise problem statement.

Hugo Sarrazin: Yeah. It’s not like “Can we grow in Japan?” That’s interesting, but it is “What, specifically, are we trying to uncover in the growth of a product in Japan? Or a segment in Japan? Or a channel in Japan?” When you spend an enormous amount of time, in the first meeting of the different stakeholders, debating this and having different people put forward what they think the problem definition is, you realize that people have completely different views of why they’re here. That, to me, is the most important step.

Charles Conn: I would agree with that. For me, the problem context is critical. When we understand “What are the forces acting upon your decision maker? How quickly is the answer needed? With what precision is the answer needed? Are there areas that are off limits or areas where we would particularly like to find our solution? Is the decision maker open to exploring other areas?” then you not only become more efficient, and move toward what we call the critical path in problem solving, but you also make it so much more likely that you’re not going to waste your time or your decision maker’s time.

How often do especially bright young people run off with half of the idea about what the problem is and start collecting data and start building models—only to discover that they’ve really gone off half-cocked.

Hugo Sarrazin: Yeah.

Charles Conn: And in the wrong direction.

Simon London: OK. So step one—and there is a real art and a structure to it—is define the problem. Step two, Charles?

Charles Conn: My favorite step is step two, which is to use logic trees to disaggregate the problem. Every problem we’re solving has some complexity and some uncertainty in it. The only way that we can really get our team working on the problem is to take the problem apart into logical pieces.

What we find, of course, is that the way to disaggregate the problem often gives you an insight into the answer to the problem quite quickly. I love to do two or three different cuts at it, each one giving a bit of a different insight into what might be going wrong. By doing sensible disaggregations, using logic trees, we can figure out which parts of the problem we should be looking at, and we can assign those different parts to team members.

Simon London: What’s a good example of a logic tree on a sort of ratable problem?

Charles Conn: Maybe the easiest one is the classic profit tree. Almost in every business that I would take a look at, I would start with a profit or return-on-assets tree. In its simplest form, you have the components of revenue, which are price and quantity, and the components of cost, which are cost and quantity. Each of those can be broken out. Cost can be broken into variable cost and fixed cost. The components of price can be broken into what your pricing scheme is. That simple tree often provides insight into what’s going on in a business or what the difference is between that business and the competitors.

If we add the leg, which is “What’s the asset base or investment element?”—so profit divided by assets—then we can ask the question “Is the business using its investments sensibly?” whether that’s in stores or in manufacturing or in transportation assets. I hope we can see just how simple this is, even though we’re describing it in words.

When I went to work with Gordon Moore at the Moore Foundation, the problem that he asked us to look at was “How can we save Pacific salmon?” Now, that sounds like an impossible question, but it was amenable to precisely the same type of disaggregation and allowed us to organize what became a 15-year effort to improve the likelihood of good outcomes for Pacific salmon.

Simon London: Now, is there a danger that your logic tree can be impossibly large? This, I think, brings us onto the third step in the process, which is that you have to prioritize.

Charles Conn: Absolutely. The third step, which we also emphasize, along with good problem definition, is rigorous prioritization—we ask the questions “How important is this lever or this branch of the tree in the overall outcome that we seek to achieve? How much can I move that lever?” Obviously, we try and focus our efforts on ones that have a big impact on the problem and the ones that we have the ability to change. With salmon, ocean conditions turned out to be a big lever, but not one that we could adjust. We focused our attention on fish habitats and fish-harvesting practices, which were big levers that we could affect.

People spend a lot of time arguing about branches that are either not important or that none of us can change. We see it in the public square. When we deal with questions at the policy level—“Should you support the death penalty?” “How do we affect climate change?” “How can we uncover the causes and address homelessness?”—it’s even more important that we’re focusing on levers that are big and movable.

Would you like to learn more about our Strategy & Corporate Finance Practice ?

Simon London: Let’s move swiftly on to step four. You’ve defined your problem, you disaggregate it, you prioritize where you want to analyze—what you want to really look at hard. Then you got to the work plan. Now, what does that mean in practice?

Hugo Sarrazin: Depending on what you’ve prioritized, there are many things you could do. It could be breaking the work among the team members so that people have a clear piece of the work to do. It could be defining the specific analyses that need to get done and executed, and being clear on time lines. There’s always a level-one answer, there’s a level-two answer, there’s a level-three answer. Without being too flippant, I can solve any problem during a good dinner with wine. It won’t have a whole lot of backing.

Simon London: Not going to have a lot of depth to it.

Hugo Sarrazin: No, but it may be useful as a starting point. If the stakes are not that high, that could be OK. If it’s really high stakes, you may need level three and have the whole model validated in three different ways. You need to find a work plan that reflects the level of precision, the time frame you have, and the stakeholders you need to bring along in the exercise.

Charles Conn: I love the way you’ve described that, because, again, some people think of problem solving as a linear thing, but of course what’s critical is that it’s iterative. As you say, you can solve the problem in one day or even one hour.

Charles Conn: We encourage our teams everywhere to do that. We call it the one-day answer or the one-hour answer. In work planning, we’re always iterating. Every time you see a 50-page work plan that stretches out to three months, you know it’s wrong. It will be outmoded very quickly by that learning process that you described. Iterative problem solving is a critical part of this. Sometimes, people think work planning sounds dull, but it isn’t. It’s how we know what’s expected of us and when we need to deliver it and how we’re progressing toward the answer. It’s also the place where we can deal with biases. Bias is a feature of every human decision-making process. If we design our team interactions intelligently, we can avoid the worst sort of biases.

Simon London: Here we’re talking about cognitive biases primarily, right? It’s not that I’m biased against you because of your accent or something. These are the cognitive biases that behavioral sciences have shown we all carry around, things like anchoring, overoptimism—these kinds of things.

Both: Yeah.

Charles Conn: Availability bias is the one that I’m always alert to. You think you’ve seen the problem before, and therefore what’s available is your previous conception of it—and we have to be most careful about that. In any human setting, we also have to be careful about biases that are based on hierarchies, sometimes called sunflower bias. I’m sure, Hugo, with your teams, you make sure that the youngest team members speak first. Not the oldest team members, because it’s easy for people to look at who’s senior and alter their own creative approaches.

Hugo Sarrazin: It’s helpful, at that moment—if someone is asserting a point of view—to ask the question “This was true in what context?” You’re trying to apply something that worked in one context to a different one. That can be deadly if the context has changed, and that’s why organizations struggle to change. You promote all these people because they did something that worked well in the past, and then there’s a disruption in the industry, and they keep doing what got them promoted even though the context has changed.

Simon London: Right. Right.

Hugo Sarrazin: So it’s the same thing in problem solving.

Charles Conn: And it’s why diversity in our teams is so important. It’s one of the best things about the world that we’re in now. We’re likely to have people from different socioeconomic, ethnic, and national backgrounds, each of whom sees problems from a slightly different perspective. It is therefore much more likely that the team will uncover a truly creative and clever approach to problem solving.

Simon London: Let’s move on to step five. You’ve done your work plan. Now you’ve actually got to do the analysis. The thing that strikes me here is that the range of tools that we have at our disposal now, of course, is just huge, particularly with advances in computation, advanced analytics. There’s so many things that you can apply here. Just talk about the analysis stage. How do you pick the right tools?

Charles Conn: For me, the most important thing is that we start with simple heuristics and explanatory statistics before we go off and use the big-gun tools. We need to understand the shape and scope of our problem before we start applying these massive and complex analytical approaches.

Simon London: Would you agree with that?

Hugo Sarrazin: I agree. I think there are so many wonderful heuristics. You need to start there before you go deep into the modeling exercise. There’s an interesting dynamic that’s happening, though. In some cases, for some types of problems, it is even better to set yourself up to maximize your learning. Your problem-solving methodology is test and learn, test and learn, test and learn, and iterate. That is a heuristic in itself, the A/B testing that is used in many parts of the world. So that’s a problem-solving methodology. It’s nothing different. It just uses technology and feedback loops in a fast way. The other one is exploratory data analysis. When you’re dealing with a large-scale problem, and there’s so much data, I can get to the heuristics that Charles was talking about through very clever visualization of data.

You test with your data. You need to set up an environment to do so, but don’t get caught up in neural-network modeling immediately. You’re testing, you’re checking—“Is the data right? Is it sound? Does it make sense?”—before you launch too far.

Simon London: You do hear these ideas—that if you have a big enough data set and enough algorithms, they’re going to find things that you just wouldn’t have spotted, find solutions that maybe you wouldn’t have thought of. Does machine learning sort of revolutionize the problem-solving process? Or are these actually just other tools in the toolbox for structured problem solving?

Charles Conn: It can be revolutionary. There are some areas in which the pattern recognition of large data sets and good algorithms can help us see things that we otherwise couldn’t see. But I do think it’s terribly important we don’t think that this particular technique is a substitute for superb problem solving, starting with good problem definition. Many people use machine learning without understanding algorithms that themselves can have biases built into them. Just as 20 years ago, when we were doing statistical analysis, we knew that we needed good model definition, we still need a good understanding of our algorithms and really good problem definition before we launch off into big data sets and unknown algorithms.

Simon London: Step six. You’ve done your analysis.

Charles Conn: I take six and seven together, and this is the place where young problem solvers often make a mistake. They’ve got their analysis, and they assume that’s the answer, and of course it isn’t the answer. The ability to synthesize the pieces that came out of the analysis and begin to weave those into a story that helps people answer the question “What should I do?” This is back to where we started. If we can’t synthesize, and we can’t tell a story, then our decision maker can’t find the answer to “What should I do?”

Simon London: But, again, these final steps are about motivating people to action, right?

Charles Conn: Yeah.

Simon London: I am slightly torn about the nomenclature of problem solving because it’s on paper, right? Until you motivate people to action, you actually haven’t solved anything.

Charles Conn: I love this question because I think decision-making theory, without a bias to action, is a waste of time. Everything in how I approach this is to help people take action that makes the world better.

Simon London: Hence, these are absolutely critical steps. If you don’t do this well, you’ve just got a bunch of analysis.

Charles Conn: We end up in exactly the same place where we started, which is people speaking across each other, past each other in the public square, rather than actually working together, shoulder to shoulder, to crack these important problems.

Simon London: In the real world, we have a lot of uncertainty—arguably, increasing uncertainty. How do good problem solvers deal with that?

Hugo Sarrazin: At every step of the process. In the problem definition, when you’re defining the context, you need to understand those sources of uncertainty and whether they’re important or not important. It becomes important in the definition of the tree.

You need to think carefully about the branches of the tree that are more certain and less certain as you define them. They don’t have equal weight just because they’ve got equal space on the page. Then, when you’re prioritizing, your prioritization approach may put more emphasis on things that have low probability but huge impact—or, vice versa, may put a lot of priority on things that are very likely and, hopefully, have a reasonable impact. You can introduce that along the way. When you come back to the synthesis, you just need to be nuanced about what you’re understanding, the likelihood.

Often, people lack humility in the way they make their recommendations: “This is the answer.” They’re very precise, and I think we would all be well-served to say, “This is a likely answer under the following sets of conditions” and then make the level of uncertainty clearer, if that is appropriate. It doesn’t mean you’re always in the gray zone; it doesn’t mean you don’t have a point of view. It just means that you can be explicit about the certainty of your answer when you make that recommendation.

Simon London: So it sounds like there is an underlying principle: “Acknowledge and embrace the uncertainty. Don’t pretend that it isn’t there. Be very clear about what the uncertainties are up front, and then build that into every step of the process.”

Hugo Sarrazin: Every step of the process.

Simon London: Yeah. We have just walked through a particular structured methodology for problem solving. But, of course, this is not the only structured methodology for problem solving. One that is also very well-known is design thinking, which comes at things very differently. So, Hugo, I know you have worked with a lot of designers. Just give us a very quick summary. Design thinking—what is it, and how does it relate?

Hugo Sarrazin: It starts with an incredible amount of empathy for the user and uses that to define the problem. It does pause and go out in the wild and spend an enormous amount of time seeing how people interact with objects, seeing the experience they’re getting, seeing the pain points or joy—and uses that to infer and define the problem.

Simon London: Problem definition, but out in the world.

Hugo Sarrazin: With an enormous amount of empathy. There’s a huge emphasis on empathy. Traditional, more classic problem solving is you define the problem based on an understanding of the situation. This one almost presupposes that we don’t know the problem until we go see it. The second thing is you need to come up with multiple scenarios or answers or ideas or concepts, and there’s a lot of divergent thinking initially. That’s slightly different, versus the prioritization, but not for long. Eventually, you need to kind of say, “OK, I’m going to converge again.” Then you go and you bring things back to the customer and get feedback and iterate. Then you rinse and repeat, rinse and repeat. There’s a lot of tactile building, along the way, of prototypes and things like that. It’s very iterative.

Simon London: So, Charles, are these complements or are these alternatives?

Charles Conn: I think they’re entirely complementary, and I think Hugo’s description is perfect. When we do problem definition well in classic problem solving, we are demonstrating the kind of empathy, at the very beginning of our problem, that design thinking asks us to approach. When we ideate—and that’s very similar to the disaggregation, prioritization, and work-planning steps—we do precisely the same thing, and often we use contrasting teams, so that we do have divergent thinking. The best teams allow divergent thinking to bump them off whatever their initial biases in problem solving are. For me, design thinking gives us a constant reminder of creativity, empathy, and the tactile nature of problem solving, but it’s absolutely complementary, not alternative.

Simon London: I think, in a world of cross-functional teams, an interesting question is do people with design-thinking backgrounds really work well together with classical problem solvers? How do you make that chemistry happen?

Hugo Sarrazin: Yeah, it is not easy when people have spent an enormous amount of time seeped in design thinking or user-centric design, whichever word you want to use. If the person who’s applying classic problem-solving methodology is very rigid and mechanical in the way they’re doing it, there could be an enormous amount of tension. If there’s not clarity in the role and not clarity in the process, I think having the two together can be, sometimes, problematic.

The second thing that happens often is that the artifacts the two methodologies try to gravitate toward can be different. Classic problem solving often gravitates toward a model; design thinking migrates toward a prototype. Rather than writing a big deck with all my supporting evidence, they’ll bring an example, a thing, and that feels different. Then you spend your time differently to achieve those two end products, so that’s another source of friction.

Now, I still think it can be an incredibly powerful thing to have the two—if there are the right people with the right mind-set, if there is a team that is explicit about the roles, if we’re clear about the kind of outcomes we are attempting to bring forward. There’s an enormous amount of collaborativeness and respect.

Simon London: But they have to respect each other’s methodology and be prepared to flex, maybe, a little bit, in how this process is going to work.

Hugo Sarrazin: Absolutely.

Simon London: The other area where, it strikes me, there could be a little bit of a different sort of friction is this whole concept of the day-one answer, which is what we were just talking about in classical problem solving. Now, you know that this is probably not going to be your final answer, but that’s how you begin to structure the problem. Whereas I would imagine your design thinkers—no, they’re going off to do their ethnographic research and get out into the field, potentially for a long time, before they come back with at least an initial hypothesis.

Want better strategies? Become a bulletproof problem solver

Hugo Sarrazin: That is a great callout, and that’s another difference. Designers typically will like to soak into the situation and avoid converging too quickly. There’s optionality and exploring different options. There’s a strong belief that keeps the solution space wide enough that you can come up with more radical ideas. If there’s a large design team or many designers on the team, and you come on Friday and say, “What’s our week-one answer?” they’re going to struggle. They’re not going to be comfortable, naturally, to give that answer. It doesn’t mean they don’t have an answer; it’s just not where they are in their thinking process.

Simon London: I think we are, sadly, out of time for today. But Charles and Hugo, thank you so much.

Charles Conn: It was a pleasure to be here, Simon.

Hugo Sarrazin: It was a pleasure. Thank you.

Simon London: And thanks, as always, to you, our listeners, for tuning into this episode of the McKinsey Podcast . If you want to learn more about problem solving, you can find the book, Bulletproof Problem Solving: The One Skill That Changes Everything , online or order it through your local bookstore. To learn more about McKinsey, you can of course find us at McKinsey.com.

Charles Conn is CEO of Oxford Sciences Innovation and an alumnus of McKinsey’s Sydney office. Hugo Sarrazin is a senior partner in the Silicon Valley office, where Simon London, a member of McKinsey Publishing, is also based.

Explore a career with us

Related articles.

Strategy to beat the odds

Five routes to more innovative problem solving

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

Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

• Last Updated: February 14, 2023
• 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.

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.

Was this helpful?

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.

Six Sigma Project Charter Template

Don’t Miss Out: Learn the Power of Lean in the Office and Take Your Business to the Next Level

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…

Structured Problem Solving

The application of a structured, methodical approach to solving a complex problem. Drawing on scientific thinking, this process leads to reaching the root cause and applying countermeasures to ensure the problem does not occur again.

Once a large problem is identified and the target outcome is set, it is broken down to a clearly defined and manageable piece. This is the prioritized problem at the point of occurrence. A root cause analysis is applied, countermeasures identified and implemented to effectively solve that part of the problem. Standard work is then put in place to help sustain the improvement.

A visual that demonstrates and tells the story of the process followed to identify and solve a complex problem.

• Miro Experts
• Strategy & Planning

Submit your template →

Do you have a great board to share with the world? We' ll help you turn it into a template to share with the community.

Similar templates

Problem Prioritization

Flow Improvement Process

SCAMPER Creative problem solving

8 Steps to Problem Solving: Step 5 - Develop Countermeasures

Description

This template is Step 5 of the 8 Steps to Problem Solving developed by Toyota Motor Corporation.

Use this template to brainstorm countermeasures, narrow the criteria matrix, and create an implementation plan.

The template is divided into three sections: List Root Cause, List Countermeasures, and Chart and Rate Countermeasures.

Learn more about how to use this process in our article 8 Steps to Problem Solving: Implement Continuous Improvement in Your Organization

8 Steps to Problem Solving: Step 6 - See Countermeasures Through

8 steps to problem solving: step 4 - root cause analysis.

Master the 7-Step Problem-Solving Process for Better Decision-Making

Discover the powerful 7-Step Problem-Solving Process to make better decisions and achieve better outcomes. Master the art of problem-solving in this comprehensive guide. Download the Free PowerPoint and PDF Template.

StrategyPunk

Introduction

Mastering the art of problem-solving is crucial for making better decisions. Whether you're a student, a business owner, or an employee, problem-solving skills can help you tackle complex issues and find practical solutions. The 7-Step Problem-Solving Process is a proven method that can help you approach problems systematically and efficiently.

The 7-Step Problem-Solving Process involves steps that guide you through the problem-solving process. The first step is to define the problem, followed by disaggregating the problem into smaller, more manageable parts. Next, you prioritize the features and create a work plan to address each. Then, you analyze each piece, synthesize the information, and communicate your findings to others.

By following this process, you can avoid jumping to conclusions, overlooking important details, or making hasty decisions. Instead, you can approach problems with a clear and structured mindset, which can help you make better decisions and achieve better outcomes.

In this article, we'll explore each step of the 7-Step Problem-Solving Process in detail so you can start mastering this valuable skill. At the end of the blog post, you can download the process's free PowerPoint and PDF templates .

Step 1: Define the Problem

The first step in the problem-solving process is to define the problem. This step is crucial because finding a solution is only accessible if the problem is clearly defined. The problem must be specific, measurable, and achievable.

One way to define the problem is to ask the right questions. Questions like "What is the problem?" and "What are the causes of the problem?" can help. Gathering data and information about the issue to assist in the definition process is also essential.

Another critical aspect of defining the problem is identifying the stakeholders. Who is affected by it? Who has a stake in finding a solution? Identifying the stakeholders can help ensure that the problem is defined in a way that considers the needs and concerns of all those affected.

Once the problem is defined, it is essential to communicate the definition to all stakeholders. This helps to ensure that everyone is on the same page and that there is a shared understanding of the problem.

Step 2: Disaggregate

After defining the problem, the next step in the 7-step problem-solving process is to disaggregate the problem into smaller, more manageable parts. Disaggregation helps break down the problem into smaller pieces that can be analyzed individually. This step is crucial in understanding the root cause of the problem and identifying the most effective solutions.

Disaggregation can be achieved by breaking down the problem into sub-problems, identifying the contributing factors, and analyzing the relationships between these factors. This step helps identify the most critical factors that must be addressed to solve the problem.

A tree or fishbone diagram is one effective way to disaggregate a problem. These diagrams help identify the different factors contributing to the problem and how they are related. Another way is to use a table to list the other factors contributing to the situation and their corresponding impact on the issue.

Disaggregation helps in breaking down complex problems into smaller, more manageable parts. It helps understand the relationships between different factors contributing to the problem and identify the most critical factors that must be addressed. By disaggregating the problem, decision-makers can focus on the most vital areas, leading to more effective solutions.

Step 3: Prioritize

After defining the problem and disaggregating it into smaller parts, the next step in the 7-step problem-solving process is prioritizing the issues that need addressing. Prioritizing helps to focus on the most pressing issues and allocate resources more effectively.

There are several ways to prioritize issues, including:

• Urgency: Prioritize issues based on their urgency. Problems that require immediate attention should be addressed first.
• Impact: Prioritize issues based on their impact on the organization or stakeholders. Problems with a high impact should be given priority.
• Resources: Prioritize issues based on the resources required to address them. Problems that require fewer resources should be dealt with first.

It is important to involve stakeholders in the prioritization process, considering their concerns and needs. This can be done through surveys, focus groups, or other forms of engagement.

Once the issues have been prioritized, developing a plan of action to address them is essential. This involves identifying the resources required, setting timelines, and assigning responsibilities.

Prioritizing issues is a critical step in problem-solving. By focusing on the most pressing problems, organizations can allocate resources more effectively and make better decisions.

Step 4: Workplan

After defining the problem, disaggregating, and prioritizing the issues, the next step in the 7-step problem-solving process is to develop a work plan. This step involves creating a roadmap that outlines the steps needed to solve the problem.

The work plan should include a list of tasks, deadlines, and responsibilities for each team member involved in the problem-solving process. Assigning tasks based on each team member's strengths and expertise ensures the work is completed efficiently and effectively.

Creating a work plan can help keep the team on track and ensure everyone is working towards the same goal. It can also help to identify potential roadblocks or challenges that may arise during the problem-solving process and develop contingency plans to address them.

Several tools and techniques can be used to develop a work plan, including Gantt charts, flowcharts, and mind maps. These tools can help to visualize the steps needed to solve the problem and identify dependencies between tasks.

Developing a work plan is a critical step in the problem-solving process. It provides a clear roadmap for solving the problem and ensures everyone involved is aligned and working towards the same goal.

Step 5: Analysis

Once the problem has been defined and disaggregated, the next step is to analyze the information gathered. This step involves examining the data, identifying patterns, and determining the root cause of the problem.

Several methods can be used during the analysis phase, including:

• Root cause analysis
• Pareto analysis
• SWOT analysis

Root cause analysis is a popular method used to identify the underlying cause of a problem. This method involves asking a series of "why" questions to get to the root cause of the issue.

Pareto analysis is another method that can be used during the analysis phase. This method involves identifying the 20% of causes responsible for 80% of the problems. By focusing on these critical causes, organizations can make significant improvements.

Finally, SWOT analysis is a valuable tool for analyzing the internal and external factors that may impact the problem. This method involves identifying the strengths, weaknesses, opportunities, and threats related to the issue.

Overall, the analysis phase is critical for identifying the root cause of the problem and developing practical solutions. By using a combination of methods, organizations can gain a deeper understanding of the issue and make informed decisions.

Step 6: Synthesize

Once the analysis phase is complete, it is time to synthesize the information gathered to arrive at a solution. During this step, the focus is on identifying the most viable solution that addresses the problem. This involves examining and combining the analysis results for a clear and concise conclusion.

One way to synthesize the information is to use a decision matrix. This involves creating a table that lists the potential solutions and the essential criteria for making a decision. Each answer is then rated against each standard, and the scores are tallied to arrive at a final decision.

Another approach to synthesizing the information is to use a mind map. This involves creating a visual representation of the problem and the potential solutions. The mind map can identify the relationships between the different pieces of information and help prioritize the solutions.

During the synthesis phase, it is vital to remain open-minded and consider all potential solutions. Involving all stakeholders in the decision-making process is essential to ensure everyone's perspectives are considered.

Step 7: Communicate

After synthesizing the information, the next step is communicating the findings to the relevant stakeholders. This is a crucial step because it helps to ensure that everyone is on the same page and that the decision-making process is transparent.

One effective way to communicate the findings is through a well-organized report. The report should include the problem statement, the analysis, the synthesis, and the recommended solution. It should be clear, concise, and easy to understand.

In addition to the report, a presentation explaining the findings is essential. The presentation should be tailored to the audience and highlight the report's key points. Visual aids such as tables, graphs, and charts can make the presentation more engaging.

During the presentation, it is essential to be open to feedback and questions from the audience. This helps ensure everyone agrees with the recommended solution and addresses concerns or objections.

Effective communication is vital to ensuring the decision-making process is successful. Stakeholders can make informed decisions and work towards a common goal by communicating the findings clearly and concisely.

The 7-step problem-solving process is a powerful tool for helping individuals and organizations make better decisions. By following these steps, individuals can identify the root cause of a problem, prioritize potential solutions, and develop a clear plan of action. This process can be applied to various scenarios, from personal challenges to complex business problems.

Through disaggregation, individuals can break down complex problems into smaller, more manageable parts. By prioritizing potential solutions, individuals can focus their efforts on the most impactful actions. The work step allows individuals to develop a clear action plan, while the analysis step provides a framework for evaluating possible solutions.

The synthesis step combines all the information gathered to develop a comprehensive solution. Finally, the communication step allows individuals to share their answers with others and gather feedback.

By mastering the 7-step problem-solving process, individuals can become more effective decision-makers and problem-solvers. This process can help individuals and organizations save time and resources while improving outcomes. With practice, individuals can develop the skills to apply this process to a wide range of scenarios and make better decisions in all areas of life.

7-Step Problem-Solving Process PPT Template

Free powerpoint and pdf template, executive summary: the 7-step problem-solving process.

The 7-Step Problem-Solving Process is a robust and systematic method to help individuals and organizations make better decisions by tackling complex issues and finding practical solutions. This process comprises defining the problem, disaggregating it into smaller parts, prioritizing the issues, creating a work plan, analyzing the data, synthesizing the information, and communicating the findings.

By following these steps, individuals can identify the root cause of a problem, break it down into manageable components, and prioritize the most impactful actions. The work plan, analysis, and synthesis steps provide a framework for developing comprehensive solutions, while the communication step ensures transparency and stakeholder engagement.

Mastering this process can improve decision-making and problem-solving capabilities, save time and resources, and improve outcomes in personal and professional contexts.

Please buy me a coffee.

I'd appreciate your support if my templates have saved you time or helped you start a project. Buy Me a Coffee is a simple way to show your appreciation and help me continue creating high-quality templates that meet your needs.

7-Step Problem-Solving Process PDF Template

7-step problem-solving process powerpoint template.

Lidl SWOT Analysis: Free PPT Template and In-Depth Insights

Discover Lidl's strengths, weaknesses, opportunities, and threats with our free PowerPoint template. This in-depth SWOT analysis provides valuable insights to help you understand Lidl's market position and strategic direction.

Global Bites: PESTLE Insights into Nestlé (Free PPT)

Download our free PPT template for in-depth PESTLE insights into Nestlé's global strategy. Learn more today!

PESTLE Analysis: Decoding Reddit's Landscape (Free PPT)

Decode Reddit's global influence with our free PowerPoint PESTLE Analysis. Explore the hub of vibrant discussions and ideas.

Navigating the Terrain: A PESTLE Analysis of Lululemon (Free PowerPoint)

Explore Lululemon's business terrain with our free PESTLE analysis PowerPoint. Instant access!