solution occurs during which step of the problem solving process

How it works

For Business

Join Mind Tools

Article • 4 min read

The Problem-Solving Process

Looking at the basic problem-solving process to help keep you on the right track.

By the Mind Tools Content Team

Problem-solving is an important part of planning and decision-making. The process has much in common with the decision-making process, and in the case of complex decisions, can form part of the process itself.

We face and solve problems every day, in a variety of guises and of differing complexity. Some, such as the resolution of a serious complaint, require a significant amount of time, thought and investigation. Others, such as a printer running out of paper, are so quickly resolved they barely register as a problem at all.

Despite the everyday occurrence of problems, many people lack confidence when it comes to solving them, and as a result may chose to stay with the status quo rather than tackle the issue. Broken down into steps, however, the problem-solving process is very simple. While there are many tools and techniques available to help us solve problems, the outline process remains the same.

The main stages of problem-solving are outlined below, though not all are required for every problem that needs to be solved.

1. Define the Problem

Clarify the problem before trying to solve it. A common mistake with problem-solving is to react to what the problem appears to be, rather than what it actually is. Write down a simple statement of the problem, and then underline the key words. Be certain there are no hidden assumptions in the key words you have underlined. One way of doing this is to use a synonym to replace the key words. For example, ‘We need to encourage higher productivity ’ might become ‘We need to promote superior output ’ which has a different meaning.

2. Analyze the Problem

Ask yourself, and others, the following questions.

• Where is the problem occurring?
• When is it occurring?
• Why is it happening?

Be careful not to jump to ‘who is causing the problem?’. When stressed and faced with a problem it is all too easy to assign blame. This, however, can cause negative feeling and does not help to solve the problem. As an example, if an employee is underperforming, the root of the problem might lie in a number of areas, such as lack of training, workplace bullying or management style. To assign immediate blame to the employee would not therefore resolve the underlying issue.

Once the answers to the where, when and why have been determined, the following questions should also be asked:

• Where can further information be found?
• Is this information correct, up-to-date and unbiased?
• What does this information mean in terms of the available options?

3. Generate Potential Solutions

When generating potential solutions it can be a good idea to have a mixture of ‘right brain’ and ‘left brain’ thinkers. In other words, some people who think laterally and some who think logically. This provides a balance in terms of generating the widest possible variety of solutions while also being realistic about what can be achieved. There are many tools and techniques which can help produce solutions, including thinking about the problem from a number of different perspectives, and brainstorming, where a team or individual write as many possibilities as they can think of to encourage lateral thinking and generate a broad range of potential solutions.

4. Select Best Solution

When selecting the best solution, consider:

• Is this a long-term solution, or a ‘quick fix’?
• Is the solution achievable in terms of available resources and time?
• Are there any risks associated with the chosen solution?
• Could the solution, in itself, lead to other problems?

This stage in particular demonstrates why problem-solving and decision-making are so closely related.

5. Take Action

In order to implement the chosen solution effectively, consider the following:

• What will the situation look like when the problem is resolved?
• What needs to be done to implement the solution? Are there systems or processes that need to be adjusted?
• What will be the success indicators?
• What are the timescales for the implementation? Does the scale of the problem/implementation require a project plan?
• Who is responsible?

Once the answers to all the above questions are written down, they can form the basis of an action plan.

6. Monitor and Review

One of the most important factors in successful problem-solving is continual observation and feedback. Use the success indicators in the action plan to monitor progress on a regular basis. Is everything as expected? Is everything on schedule? Keep an eye on priorities and timelines to prevent them from slipping.

If the indicators are not being met, or if timescales are slipping, consider what can be done. Was the plan realistic? If so, are sufficient resources being made available? Are these resources targeting the correct part of the plan? Or does the plan need to be amended? Regular review and discussion of the action plan is important so small adjustments can be made on a regular basis to help keep everything on track.

Once all the indicators have been met and the problem has been resolved, consider what steps can now be taken to prevent this type of problem recurring? It may be that the chosen solution already prevents a recurrence, however if an interim or partial solution has been chosen it is important not to lose momentum.

Problems, by their very nature, will not always fit neatly into a structured problem-solving process. This process, therefore, is designed as a framework which can be adapted to individual needs and nature.

Join Mind Tools and get access to exclusive content.

This resource is only available to Mind Tools members.

Already a member? Please Login here

Team Management

Learn the key aspects of managing a team, from building and developing your team, to working with different types of teams, and troubleshooting common problems.

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

Newest Releases

SWOT Analysis

SMART Goals

Mind Tools Store

About Mind Tools Content

Discover something new today

How to stop procrastinating.

Overcoming the Habit of Delaying Important Tasks

What Is Time Management?

Working Smarter to Enhance Productivity

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

Energizing yourself infographic.

Infographic Transcript

Infographic

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

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

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. You can download the process's free PowerPoint and PDF templates at the end of the blog post .

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 by it.

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.

Considering their concerns and needs, it is important to involve stakeholders in the prioritization process. 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. Organizations can gain a deeper understanding of the issue and make informed decisions by using a combination of methods.

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, remaining open-minded and considering all potential solutions is vital. To ensure everyone's perspectives are considered, it is also essential to involve all stakeholders in the decision-making process.

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.

Xpeng SWOT Analysis: Free PPT Template and In-Depth Insights (free file)

Unlock key insights into Xpeng with our free SWOT analysis PPT template. Dive deep into its business dynamics at no cost.

Strategic Insights 2024: A SWOT Analysis of Nestle (Plus Free PPT)

Explore Nestle's strategic outlook with our SWOT analysis for 2024. This PowerPoint template highlights key areas for growth and challenges.

2024 Business Disruption: Navigating Growth Through Shaping Strategy

Discover the importance of being a shaper in 2023's business ecosystem. Shaping strategy, attracting a critical mass of participants, and finding the right strategic path to create value.

Samsung PESTLE Analysis: Unveiling the Driving Forces (Free PPT)

Download our comprehensive guide: Samsung PESTLE Analysis (Free PPT). Discover the strategic insights & driving forces shaping Samsung's future.

What is Problem Solving? (Steps, Techniques, Examples)

By Status.net Editorial Team on May 7, 2023 — 5 minutes to read

What Is Problem Solving?

Definition and importance.

Problem solving is the process of finding solutions to obstacles or challenges you encounter in your life or work. It is a crucial skill that allows you to tackle complex situations, adapt to changes, and overcome difficulties with ease. Mastering this ability will contribute to both your personal and professional growth, leading to more successful outcomes and better decision-making.

Problem-Solving Steps

The problem-solving process typically includes the following steps:

• Identify the issue : Recognize the problem that needs to be solved.
• Analyze the situation : Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present.
• Generate potential solutions : Brainstorm a list of possible solutions to the issue, without immediately judging or evaluating them.
• Evaluate options : Weigh the pros and cons of each potential solution, considering factors such as feasibility, effectiveness, and potential risks.
• Select the best solution : Choose the option that best addresses the problem and aligns with your objectives.
• Implement the solution : Put the selected solution into action and monitor the results to ensure it resolves the issue.
• Review and learn : Reflect on the problem-solving process, identify any improvements or adjustments that can be made, and apply these learnings to future situations.

Defining the Problem

To start tackling a problem, first, identify and understand it. Analyzing the issue thoroughly helps to clarify its scope and nature. Ask questions to gather information and consider the problem from various angles. Some strategies to define the problem include:

• Brainstorming with others
• Asking the 5 Ws and 1 H (Who, What, When, Where, Why, and How)
• Analyzing cause and effect
• Creating a problem statement

Generating Solutions

Once the problem is clearly understood, brainstorm possible solutions. Think creatively and keep an open mind, as well as considering lessons from past experiences. Consider:

• Creating a list of potential ideas to solve the problem
• Grouping and categorizing similar solutions
• Prioritizing potential solutions based on feasibility, cost, and resources required
• Involving others to share diverse opinions and inputs

Evaluating and Selecting Solutions

Evaluate each potential solution, weighing its pros and cons. To facilitate decision-making, use techniques such as:

• SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
• Decision-making matrices
• Pros and cons lists
• Risk assessments

After evaluating, choose the most suitable solution based on effectiveness, cost, and time constraints.

Implementing and Monitoring the Solution

Implement the chosen solution and monitor its progress. Key actions include:

• Communicating the solution to relevant parties
• Setting timelines and milestones
• Assigning tasks and responsibilities
• Monitoring the solution and making adjustments as necessary
• Evaluating the effectiveness of the solution after implementation

Utilize feedback from stakeholders and consider potential improvements. Remember that problem-solving is an ongoing process that can always be refined and enhanced.

Problem-Solving Techniques

During each step, you may find it helpful to utilize various problem-solving techniques, such as:

• Brainstorming : A free-flowing, open-minded session where ideas are generated and listed without judgment, to encourage creativity and innovative thinking.
• Root cause analysis : A method that explores the underlying causes of a problem to find the most effective solution rather than addressing superficial symptoms.
• SWOT analysis : A tool used to evaluate the strengths, weaknesses, opportunities, and threats related to a problem or decision, providing a comprehensive view of the situation.
• Mind mapping : A visual technique that uses diagrams to organize and connect ideas, helping to identify patterns, relationships, and possible solutions.

Brainstorming

When facing a problem, start by conducting a brainstorming session. Gather your team and encourage an open discussion where everyone contributes ideas, no matter how outlandish they may seem. This helps you:

• Generate a diverse range of solutions
• Encourage all team members to participate
• Foster creative thinking

When brainstorming, remember to:

• Reserve judgment until the session is over
• Encourage wild ideas
• Combine and improve upon ideas

Root Cause Analysis

For effective problem-solving, identifying the root cause of the issue at hand is crucial. Try these methods:

• 5 Whys : Ask “why” five times to get to the underlying cause.
• Fishbone Diagram : Create a diagram representing the problem and break it down into categories of potential causes.
• Pareto Analysis : Determine the few most significant causes underlying the majority of problems.

SWOT Analysis

SWOT analysis helps you examine the Strengths, Weaknesses, Opportunities, and Threats related to your problem. To perform a SWOT analysis:

• List your problem’s strengths, such as relevant resources or strong partnerships.
• Identify its weaknesses, such as knowledge gaps or limited resources.
• Explore opportunities, like trends or new technologies, that could help solve the problem.
• Recognize potential threats, like competition or regulatory barriers.

SWOT analysis aids in understanding the internal and external factors affecting the problem, which can help guide your solution.

Mind Mapping

A mind map is a visual representation of your problem and potential solutions. It enables you to organize information in a structured and intuitive manner. To create a mind map:

• Write the problem in the center of a blank page.
• Draw branches from the central problem to related sub-problems or contributing factors.
• Add more branches to represent potential solutions or further ideas.

Mind mapping allows you to visually see connections between ideas and promotes creativity in problem-solving.

Examples of Problem Solving in Various Contexts

In the business world, you might encounter problems related to finances, operations, or communication. Applying problem-solving skills in these situations could look like:

• Identifying areas of improvement in your company’s financial performance and implementing cost-saving measures
• Resolving internal conflicts among team members by listening and understanding different perspectives, then proposing and negotiating solutions
• Streamlining a process for better productivity by removing redundancies, automating tasks, or re-allocating resources

In educational contexts, problem-solving can be seen in various aspects, such as:

• Addressing a gap in students’ understanding by employing diverse teaching methods to cater to different learning styles
• Developing a strategy for successful time management to balance academic responsibilities and extracurricular activities
• Seeking resources and support to provide equal opportunities for learners with special needs or disabilities

Everyday life is full of challenges that require problem-solving skills. Some examples include:

• Overcoming a personal obstacle, such as improving your fitness level, by establishing achievable goals, measuring progress, and adjusting your approach accordingly
• Navigating a new environment or city by researching your surroundings, asking for directions, or using technology like GPS to guide you
• Dealing with a sudden change, like a change in your work schedule, by assessing the situation, identifying potential impacts, and adapting your plans to accommodate the change.
• How to Resolve Employee Conflict at Work [Steps, Tips, Examples]
• How to Write Inspiring Core Values? 5 Steps with Examples
• 30 Employee Feedback Examples (Positive & Negative)

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

• The Art of Effective Problem Solving: A Step-by-Step Guide
• Learn Lean Sigma
• Problem Solving

Whether we realise it or not, problem solving skills are an important part of our daily lives. From resolving a minor annoyance at home to tackling complex business challenges at work, our ability to solve problems has a significant impact on our success and happiness. However, not everyone is naturally gifted at problem-solving, and even those who are can always improve their skills. In this blog post, we will go over the art of effective problem-solving step by step.

You will learn how to define a problem, gather information, assess alternatives, and implement a solution, all while honing your critical thinking and creative problem-solving skills. Whether you’re a seasoned problem solver or just getting started, this guide will arm you with the knowledge and tools you need to face any challenge with confidence. So let’s get started!

Table of Contents

Problem solving methodologies.

Individuals and organisations can use a variety of problem-solving methodologies to address complex challenges. 8D and A3 problem solving techniques are two popular methodologies in the Lean Six Sigma framework.

Methodology of 8D (Eight Discipline) Problem Solving:

The 8D problem solving methodology is a systematic, team-based approach to problem solving. It is a method that guides a team through eight distinct steps to solve a problem in a systematic and comprehensive manner.

The 8D process consists of the following steps:

• Form a team: Assemble a group of people who have the necessary expertise to work on the problem.
• Define the issue: Clearly identify and define the problem, including the root cause and the customer impact.
• Create a temporary containment plan: Put in place a plan to lessen the impact of the problem until a permanent solution can be found.
• Identify the root cause: To identify the underlying causes of the problem, use root cause analysis techniques such as Fishbone diagrams and Pareto charts.
• Create and test long-term corrective actions: Create and test a long-term solution to eliminate the root cause of the problem.
• Implement and validate the permanent solution: Implement and validate the permanent solution’s effectiveness.
• Prevent recurrence: Put in place measures to keep the problem from recurring.
• Recognize and reward the team: Recognize and reward the team for its efforts.

Download the 8D Problem Solving Template

A3 Problem Solving Method:

The A3 problem solving technique is a visual, team-based problem-solving approach that is frequently used in Lean Six Sigma projects. The A3 report is a one-page document that clearly and concisely outlines the problem, root cause analysis, and proposed solution.

The A3 problem-solving procedure consists of the following steps:

• Determine the issue: Define the issue clearly, including its impact on the customer.
• Perform root cause analysis: Identify the underlying causes of the problem using root cause analysis techniques.
• Create and implement a solution: Create and implement a solution that addresses the problem’s root cause.
• Monitor and improve the solution: Keep an eye on the solution’s effectiveness and make any necessary changes.

Subsequently, in the Lean Six Sigma framework, the 8D and A3 problem solving methodologies are two popular approaches to problem solving. Both methodologies provide a structured, team-based problem-solving approach that guides individuals through a comprehensive and systematic process of identifying, analysing, and resolving problems in an effective and efficient manner.

Step 1 – Define the Problem

The definition of the problem is the first step in effective problem solving. This may appear to be a simple task, but it is actually quite difficult. This is because problems are frequently complex and multi-layered, making it easy to confuse symptoms with the underlying cause. To avoid this pitfall, it is critical to thoroughly understand the problem.

To begin, ask yourself some clarifying questions:

• What exactly is the issue?
• What are the problem’s symptoms or consequences?
• Who or what is impacted by the issue?
• When and where does the issue arise?

Answering these questions will assist you in determining the scope of the problem. However, simply describing the problem is not always sufficient; you must also identify the root cause. The root cause is the underlying cause of the problem and is usually the key to resolving it permanently.

Try asking “why” questions to find the root cause:

• What causes the problem?
• Why does it continue?
• Why does it have the effects that it does?

By repeatedly asking “ why ,” you’ll eventually get to the bottom of the problem. This is an important step in the problem-solving process because it ensures that you’re dealing with the root cause rather than just the symptoms.

Once you have a firm grasp on the issue, it is time to divide it into smaller, more manageable chunks. This makes tackling the problem easier and reduces the risk of becoming overwhelmed. For example, if you’re attempting to solve a complex business problem, you might divide it into smaller components like market research, product development, and sales strategies.

To summarise step 1, defining the problem is an important first step in effective problem-solving. You will be able to identify the root cause and break it down into manageable parts if you take the time to thoroughly understand the problem. This will prepare you for the next step in the problem-solving process, which is gathering information and brainstorming ideas.

Step 2 – Gather Information and Brainstorm Ideas

Gathering information and brainstorming ideas is the next step in effective problem solving. This entails researching the problem and relevant information, collaborating with others, and coming up with a variety of potential solutions. This increases your chances of finding the best solution to the problem.

Begin by researching the problem and relevant information. This could include reading articles, conducting surveys, or consulting with experts. The goal is to collect as much information as possible in order to better understand the problem and possible solutions.

Next, work with others to gather a variety of perspectives. Brainstorming with others can be an excellent way to come up with new and creative ideas. Encourage everyone to share their thoughts and ideas when working in a group, and make an effort to actively listen to what others have to say. Be open to new and unconventional ideas and resist the urge to dismiss them too quickly.

Finally, use brainstorming to generate a wide range of potential solutions. This is the place where you can let your imagination run wild. At this stage, don’t worry about the feasibility or practicality of the solutions; instead, focus on generating as many ideas as possible. Write down everything that comes to mind, no matter how ridiculous or unusual it may appear. This can be done individually or in groups.

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the next step in the problem-solving process, which we’ll go over in greater detail in the following section.

Step 3 – Evaluate Options and Choose the Best Solution

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the third step in effective problem solving, and it entails weighing the advantages and disadvantages of each solution, considering their feasibility and practicability, and selecting the solution that is most likely to solve the problem effectively.

To begin, weigh the advantages and disadvantages of each solution. This will assist you in determining the potential outcomes of each solution and deciding which is the best option. For example, a quick and easy solution may not be the most effective in the long run, whereas a more complex and time-consuming solution may be more effective in solving the problem in the long run.

Consider each solution’s feasibility and practicability. Consider the following:

• Can the solution be implemented within the available resources, time, and budget?
• What are the possible barriers to implementing the solution?
• Is the solution feasible in today’s political, economic, and social environment?

You’ll be able to tell which solutions are likely to succeed and which aren’t by assessing their feasibility and practicability.

Finally, choose the solution that is most likely to effectively solve the problem. This solution should be based on the criteria you’ve established, such as the advantages and disadvantages of each solution, their feasibility and practicability, and your overall goals.

It is critical to remember that there is no one-size-fits-all solution to problems. What is effective for one person or situation may not be effective for another. This is why it is critical to consider a wide range of solutions and evaluate each one based on its ability to effectively solve the problem.

Step 4 – Implement and Monitor the Solution

When you’ve decided on the best solution, it’s time to put it into action. The fourth and final step in effective problem solving is to put the solution into action, monitor its progress, and make any necessary adjustments.

To begin, implement the solution. This may entail delegating tasks, developing a strategy, and allocating resources. Ascertain that everyone involved understands their role and responsibilities in the solution’s implementation.

Next, keep an eye on the solution’s progress. This may entail scheduling regular check-ins, tracking metrics, and soliciting feedback from others. You will be able to identify any potential roadblocks and make any necessary adjustments in a timely manner if you monitor the progress of the solution.

Finally, make any necessary modifications to the solution. This could entail changing the solution, altering the plan of action, or delegating different tasks. Be willing to make changes if they will improve the solution or help it solve the problem more effectively.

It’s important to remember that problem solving is an iterative process, and there may be times when you need to start from scratch. This is especially true if the initial solution does not effectively solve the problem. In these situations, it’s critical to be adaptable and flexible and to keep trying new solutions until you find the one that works best.

To summarise, effective problem solving is a critical skill that can assist individuals and organisations in overcoming challenges and achieving their objectives. Effective problem solving consists of four key steps: defining the problem, generating potential solutions, evaluating alternatives and selecting the best solution, and implementing the solution.

You can increase your chances of success in problem solving by following these steps and considering factors such as the pros and cons of each solution, their feasibility and practicability, and making any necessary adjustments. Furthermore, keep in mind that problem solving is an iterative process, and there may be times when you need to go back to the beginning and restart. Maintain your adaptability and try new solutions until you find the one that works best for you.

• Novick, L.R. and Bassok, M., 2005.  Problem Solving . Cambridge University Press.

Daniel Croft

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

Free Lean Six Sigma Templates

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

5S Floor Marking Best Practices

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

How to Measure the ROI of Continuous Improvement Initiatives

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

8D Problem-Solving: Common Mistakes to Avoid

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

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

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

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…

• Bipolar Disorder
• Therapy Center
• When To See a Therapist
• Types of Therapy
• Best Online Therapy
• Best Couples Therapy
• Best Family Therapy
• Managing Stress
• Sleep and Dreaming
• Understanding Emotions
• Self-Improvement
• Healthy Relationships
• Student Resources
• Personality Types
• Guided Meditations
• Verywell Mind Insights
• 2023 Verywell Mind 25
• Mental Health in the Classroom
• Editorial Process
• Meet Our Review Board
• Crisis Support

Problem-Solving Strategies and Obstacles

Kendra Cherry, MS, is a psychosocial rehabilitation specialist, psychology educator, and author of the "Everything Psychology Book."

Sean is a fact-checker and researcher with experience in sociology, field research, and data analytics.

JGI / Jamie Grill / Getty Images

• Application
• Improvement

From deciding what to eat for dinner to considering whether it's the right time to buy a house, problem-solving is a large part of our daily lives. Learn some of the problem-solving strategies that exist and how to use them in real life, along with ways to overcome obstacles that are making it harder to resolve the issues you face.

What Is Problem-Solving?

In cognitive psychology , the term 'problem-solving' refers to the mental process that people go through to discover, analyze, and solve problems.

A problem exists when there is a goal that we want to achieve but the process by which we will achieve it is not obvious to us. Put another way, there is something that we want to occur in our life, yet we are not immediately certain how to make it happen.

Maybe you want a better relationship with your spouse or another family member but you're not sure how to improve it. Or you want to start a business but are unsure what steps to take. Problem-solving helps you figure out how to achieve these desires.

The problem-solving process involves:

• Discovery of the problem
• Deciding to tackle the issue
• Seeking to understand the problem more fully
• Researching available options or solutions
• Taking action to resolve the issue

Before problem-solving can occur, it is important to first understand the exact nature of the problem itself. If your understanding of the issue is faulty, your attempts to resolve it will also be incorrect or flawed.

Problem-Solving Mental Processes

Several mental processes are at work during problem-solving. Among them are:

• Perceptually recognizing the problem
• Representing the problem in memory
• Considering relevant information that applies to the problem
• Identifying different aspects of the problem
• Labeling and describing the problem

Problem-Solving Strategies

There are many ways to go about solving a problem. Some of these strategies might be used on their own, or you may decide to employ multiple approaches when working to figure out and fix a problem.

An algorithm is a step-by-step procedure that, by following certain "rules" produces a solution. Algorithms are commonly used in mathematics to solve division or multiplication problems. But they can be used in other fields as well.

In psychology, algorithms can be used to help identify individuals with a greater risk of mental health issues. For instance, research suggests that certain algorithms might help us recognize children with an elevated risk of suicide or self-harm.

One benefit of algorithms is that they guarantee an accurate answer. However, they aren't always the best approach to problem-solving, in part because detecting patterns can be incredibly time-consuming.

There are also concerns when machine learning is involved—also known as artificial intelligence (AI)—such as whether they can accurately predict human behaviors.

Heuristics are shortcut strategies that people can use to solve a problem at hand. These "rule of thumb" approaches allow you to simplify complex problems, reducing the total number of possible solutions to a more manageable set.

If you find yourself sitting in a traffic jam, for example, you may quickly consider other routes, taking one to get moving once again. When shopping for a new car, you might think back to a prior experience when negotiating got you a lower price, then employ the same tactics.

While heuristics may be helpful when facing smaller issues, major decisions shouldn't necessarily be made using a shortcut approach. Heuristics also don't guarantee an effective solution, such as when trying to drive around a traffic jam only to find yourself on an equally crowded route.

Trial and Error

A trial-and-error approach to problem-solving involves trying a number of potential solutions to a particular issue, then ruling out those that do not work. If you're not sure whether to buy a shirt in blue or green, for instance, you may try on each before deciding which one to purchase.

This can be a good strategy to use if you have a limited number of solutions available. But if there are many different choices available, narrowing down the possible options using another problem-solving technique can be helpful before attempting trial and error.

In some cases, the solution to a problem can appear as a sudden insight. You are facing an issue in a relationship or your career when, out of nowhere, the solution appears in your mind and you know exactly what to do.

Insight can occur when the problem in front of you is similar to an issue that you've dealt with in the past. Although, you may not recognize what is occurring since the underlying mental processes that lead to insight often happen outside of conscious awareness .

Research indicates that insight is most likely to occur during times when you are alone—such as when going on a walk by yourself, when you're in the shower, or when lying in bed after waking up.

How to Apply Problem-Solving Strategies in Real Life

If you're facing a problem, you can implement one or more of these strategies to find a potential solution. Here's how to use them in real life:

• Create a flow chart . If you have time, you can take advantage of the algorithm approach to problem-solving by sitting down and making a flow chart of each potential solution, its consequences, and what happens next.
• Recall your past experiences . When a problem needs to be solved fairly quickly, heuristics may be a better approach. Think back to when you faced a similar issue, then use your knowledge and experience to choose the best option possible.
• Start trying potential solutions . If your options are limited, start trying them one by one to see which solution is best for achieving your desired goal. If a particular solution doesn't work, move on to the next.
• Take some time alone . Since insight is often achieved when you're alone, carve out time to be by yourself for a while. The answer to your problem may come to you, seemingly out of the blue, if you spend some time away from others.

Obstacles to Problem-Solving

Problem-solving is not a flawless process as there are a number of obstacles that can interfere with our ability to solve a problem quickly and efficiently. These obstacles include:

• Assumptions: When dealing with a problem, people can make assumptions about the constraints and obstacles that prevent certain solutions. Thus, they may not even try some potential options.
• Functional fixedness : This term refers to the tendency to view problems only in their customary manner. Functional fixedness prevents people from fully seeing all of the different options that might be available to find a solution.
• Irrelevant or misleading information: When trying to solve a problem, it's important to distinguish between information that is relevant to the issue and irrelevant data that can lead to faulty solutions. The more complex the problem, the easier it is to focus on misleading or irrelevant information.
• Mental set: A mental set is a tendency to only use solutions that have worked in the past rather than looking for alternative ideas. A mental set can work as a heuristic, making it a useful problem-solving tool. However, mental sets can also lead to inflexibility, making it more difficult to find effective solutions.

How to Improve Your Problem-Solving Skills

In the end, if your goal is to become a better problem-solver, it's helpful to remember that this is a process. Thus, if you want to improve your problem-solving skills, following these steps can help lead you to your solution:

• Recognize that a problem exists . If you are facing a problem, there are generally signs. For instance, if you have a mental illness , you may experience excessive fear or sadness, mood changes, and changes in sleeping or eating habits. Recognizing these signs can help you realize that an issue exists.
• Decide to solve the problem . Make a conscious decision to solve the issue at hand. Commit to yourself that you will go through the steps necessary to find a solution.
• Seek to fully understand the issue . Analyze the problem you face, looking at it from all sides. If your problem is relationship-related, for instance, ask yourself how the other person may be interpreting the issue. You might also consider how your actions might be contributing to the situation.
• Research potential options . Using the problem-solving strategies mentioned, research potential solutions. Make a list of options, then consider each one individually. What are some pros and cons of taking the available routes? What would you need to do to make them happen?
• Take action . Select the best solution possible and take action. Action is one of the steps required for change . So, go through the motions needed to resolve the issue.
• Try another option, if needed . If the solution you chose didn't work, don't give up. Either go through the problem-solving process again or simply try another option.

You can find a way to solve your problems as long as you keep working toward this goal—even if the best solution is simply to let go because no other good solution exists.

Sarathy V. Real world problem-solving .  Front Hum Neurosci . 2018;12:261. doi:10.3389/fnhum.2018.00261

Dunbar K. Problem solving . A Companion to Cognitive Science . 2017. doi:10.1002/9781405164535.ch20

Stewart SL, Celebre A, Hirdes JP, Poss JW. Risk of suicide and self-harm in kids: The development of an algorithm to identify high-risk individuals within the children's mental health system . Child Psychiat Human Develop . 2020;51:913-924. doi:10.1007/s10578-020-00968-9

Rosenbusch H, Soldner F, Evans AM, Zeelenberg M. Supervised machine learning methods in psychology: A practical introduction with annotated R code . Soc Personal Psychol Compass . 2021;15(2):e12579. doi:10.1111/spc3.12579

Mishra S. Decision-making under risk: Integrating perspectives from biology, economics, and psychology . Personal Soc Psychol Rev . 2014;18(3):280-307. doi:10.1177/1088868314530517

Csikszentmihalyi M, Sawyer K. Creative insight: The social dimension of a solitary moment . In: The Systems Model of Creativity . 2015:73-98. doi:10.1007/978-94-017-9085-7_7

Chrysikou EG, Motyka K, Nigro C, Yang SI, Thompson-Schill SL. Functional fixedness in creative thinking tasks depends on stimulus modality .  Psychol Aesthet Creat Arts . 2016;10(4):425‐435. doi:10.1037/aca0000050

Huang F, Tang S, Hu Z. Unconditional perseveration of the short-term mental set in chunk decomposition .  Front Psychol . 2018;9:2568. doi:10.3389/fpsyg.2018.02568

National Alliance on Mental Illness. Warning signs and symptoms .

Mayer RE. Thinking, problem solving, cognition, 2nd ed .

Schooler JW, Ohlsson S, Brooks K. Thoughts beyond words: When language overshadows insight. J Experiment Psychol: General . 1993;122:166-183. doi:10.1037/0096-3445.2.166

By Kendra Cherry, MSEd Kendra Cherry, MS, is a psychosocial rehabilitation specialist, psychology educator, and author of the "Everything Psychology Book."

What is the problem-solving process?

Reading time: about 6 min

Much of your day is spent subconsciously and consciously solving problems. It’s second nature to you. So much so that, when problems arise at work, you likely have your own methods of tackling them. But there will come a time when you encounter a problem and realize your methods for solving it don’t match the methods other people are using. Suddenly, your team or your business is facing a large challenge, and team members are pinballing in dozens of directions attempting to solve it, creating more chaos and prolonging the solution. 

This is what happens without having a problem-solving process. A cohesive problem-solving process needs to be defined and must include identifying the problem, gathering potential solutions, deciding on one of them, and implementing that solution. Without agreeing on a specific problem-solving process, your company will struggle to choose a solution, lack innovative solutions from which to choose, and ultimately create more problems than it solves. 

But a company that has standardized its problem-solving is able to be lean, rise to pivots in the market, and improve business value over time. We’ll teach you the components of problem-solving and give you techniques to implement a process in your own business.

6-step problem-solving process 

While your preferred method for solving problems may involve more or fewer steps, these six components comprise the backbone of any good process. 

1. Identify and define the problem 

This step seems like the most basic but can actually be the most surprising part of the process. Without agreeing on what the problem is, there’s no way to actually fix it. And sometimes, it may appear that you have one issue when the root of the problem is something else entirely.

• Write down the problem. It’s not enough to just state it aloud.
• Get granular. List everything known about the issue, from when it began to how broad it is.
• List the problem’s cascading effect to understand how broad of an issue you face.

2. Generate possible solutions

Get brainstorming. Start talking. Think big.

• Narrow down your solutions to the best few.

3. Evaluate alternatives

Before settling on the solution, make sure that you’ve examined all angles.

• Widen the response base. Consider soliciting solutions from beyond your own team to gather a different perspective.
• Carefully weigh the options against each other. What are the risks of each? What are the benefits? Is there a clear winner?

4. Decide on a solution

• Prepare to back up your choice with metrics. Data goes a long way in getting stakeholders on board.
• Detail what you expect the solution to achieve. Why are you taking this approach, and what will the perfect implementation look like?
• Determine what success will look like with this solution. How will you measure it?

Consider using a decision-making matrix template (like the one below) to help with this step. 

5. Implement the solution

This can often be the most difficult step. Implementing a solution involves change management and getting people on board with your solution. 

• Consider communications. How will you get the message out broadly about this solution, how you chose it, and why it’s important? Being completely transparent about the process can help convince your broader team you’ve put considerable thought into all aspects of the solution, which increases trust. 
• Figure out training around the solution, as well as any technical requirements. Will the solution need new software? Will it require a change in process? Outline all this in a single source of truth document that can be referred to often.

6. Evaluate the outcome 

There’s a good chance your solution won’t go perfectly. And you may need to reevaluate it in the future. Periodically evaluating your solution is a valuable tool for improving over time and learning from past mistakes.

Tips for effective problem-solving

As you move through the problem-solving process, you may feel tempted to figure things out as you go, but that can end up wasting valuable time. Consider these tips before you begin so you can avoid missing the best solution.

Don’t jump to conclusions

It’s likely you’ll start the problem-solving process with a clear favorite solution in mind. You may even subconsciously start trying to convince others on your team of the correctness of your solution instead of allowing them space to develop their own solutions. That’s when sticking to the process works the best—it eliminates bias and encourages free thinking. 

Get the right people in the room

This means doing some work ahead of time. Who has the right expertise, as well as the right authority to contribute solutions? Who’s particularly familiar with the problem? Gathering solution-minded people who have the correct understanding of the issue at hand will go far in problem-solving. 

Design a thoughtful agenda

Ever been in a meeting that’s been a waste of time? That could have been because there wasn’t an effective agenda . The agenda should walk the team through the entire process and should be divided into time segments to keep things moving.

Techniques for developing solutions 

In addition to all the above, here are three more problem-solving techniques beyond brainstorming.

Improved solutions

This technique involves improving upon the solutions of others. After presenting the problem, allow each team member to come up with one solid solution and write it down. Then rotate clockwise and encourage the next team member to improve upon the solution that was presented. Continue rotating until all solutions have been improved upon.

A brainwriting template can help with this. 

How-now-wow matrix

Infuse creativity into your process with this technique. The how-now-wow matrix progresses through obvious ideas that are easy to implement through original ideas that may need more effort to implement. This matrix frees up the mind and encourages creative thinking. 

Impact and effort matrix

An impact and effort matrix shows where solutions fall on a scale of their impact vs. how easy they are to complete. This makes it easy for the team to see where there are some quick wins and where there are some high-impact solutions worth putting resources into. 

Problem-solving isn’t going anywhere. The more comfortable you are with tackling problems, the more you’ll train your brain to think of creative solutions, but it all starts with understanding the process. Now that you’ve become more familiar with the problem-solving process, you can better lead your team through the steps, taking a systematic approach to finding solutions. The more you repeat this process, the easier it will be to develop solutions that make a real impact.

Try out this decision-making matrix template for the next problem you need to solve!   

About Lucidspark

Lucidspark, a cloud-based virtual whiteboard, is a core component of Lucid Software's Visual Collaboration Suite. This cutting-edge digital canvas brings teams together to brainstorm, collaborate, and consolidate collective thinking into actionable next steps—all in real time. Lucid is proud to serve top businesses around the world, including customers such as Google, GE, and NBC Universal, and 99% of the Fortune 500. Lucid partners with industry leaders, including Google, Atlassian, and Microsoft. Since its founding, Lucid has received numerous awards for its products, business, and workplace culture. For more information, visit lucidspark.com.

Related articles

To find out how leaders can embrace conflict as a tool for growth, we talked to Samantha Denning, an executive coach and expert in mediation and conflict resolution.

Let's explore a few strategies and collaboration best practices that improve the way work happens at your organization.   

In this blog post, we will identify ways to create more effective meeting agenda, and some templates to get you started.  

Learn and master the five elements of Design Thinking to really start thinking outside of the box.

Bring your bright ideas to life.

or continue with

• Miles Anthony Smith
• Sep 12, 2022
• 12 min read

The Ultimate Problem-Solving Process Guide: 31 Steps and Resources

Updated: Jan 24, 2023

GOT CHALLENGES WITH YOUR PROBLEM-SOLVING PROCESS? ARE YOU FRUSTRATED?

prob·lem-solv·ing noun -the process of finding solutions to difficult or complex issues. It sounds so simple, doesn’t it? But in reality problem-solving is hard. It's almost always more complex than it seems. That's why problem-solving can be so frustrating sometimes. You can feel like you’re spinning your wheels, arguing in circles, or just failing to find answers that actually work. And when you've got a group working on a problem, it can get even muddier …differences of opinions, viewpoints colored by different backgrounds, history, life experiences, you name it. We’re all looking at life and work from different angles, and that often means disagreement. Sometimes sharp disagreement. That human element, figuring out how to take ourselves out of the equation and make solid, fact-based decisions , is precisely why there’s been so much written on problem-solving. Which creates its own set of problems. Whose method is best? How can you possibly sift through them all? Are we to have one person complete the entire problem-solving process by themselves or rely on a larger team to find answers to our most vexing challenges in the workplace ? Today, we’re going to make sense of it all. We’ll take a close look at nine top problem-solving methods. Then we’ll grab the best elements of all of them to give you a process that will have your team solving problems faster, with better results , and maybe with less sharp disagreement. Ready to dive in? Let’s go!

9 PROFITABLE PROBLEM-SOLVING TECHNIQUES AND METHODS

While there are loads of methods to choose from, we are going to focus on nine of the more common ones. You can use some of these problem-solving techniques reactively to solve a known issue or proactively to find more efficient or effective ways of performing tasks. If you want to explore other methods, check out this resource here . A helpful bit of advice here is to reassure people that you aren’t here to identify the person that caused the problem . You’re working to surface the issue, solve it and make sure it doesn’t happen again, regardless of the person working on the process. It can’t be understated how important it is to continually reassure people of this so that you get unfiltered access to information. Without this, people will often hide things to protect themselves . After all, nobody wants to look bad, do they? With that said, let’s get started...

1. CREATIVE PROBLEM SOLVING (CPS)

Alex Osborn coined the term “Creative Problem Solving” in the 1940s with this simple four-step process:

Clarify : Explore the vision, gather data, and formulate questions.

Ideate : This stage should use brainstorming to generate divergent thinking and ideas rather than the random ideas normally associated with brainstorming.

Develop : Formulate solutions as part of an overall plan.

Implement : Put the plan into practice and communicate it to all parties.

2. APPRECIATIVE INQUIRY

Source: http://www.davidcooperrider.com/ai-process/ This method seeks, first and foremost, to identify the strengths in people and organizations and play to that “positive core” rather than focus our energies on improving weaknesses . It starts with an “affirmative topic,” followed by the “positive core (strengths).” Then this method delves into the following stages:

Discovery (fact-finding)

Dream (visioning the future)

Design (strategic purpose)

Destiny (continuous improvement)

3. “FIVE WHYS” METHOD

This method simply suggests that we ask “Why” at least five times during our review of the problem and in search of a fix. This helps us dig deeper to find the the true reason for the problem, or the root cause. Now, this doesn’t mean we just keeping asking the same question five times. Once we get an answer to our first “why”, we ask why to that answer until we get to five “whys”.

Using the “five whys” is part of the “Analyze” phase of Six Sigma but can be used with or without the full Six Sigma process.

Review this simple Wikipedia example of the 5 Whys in action:

The vehicle will not start. (the problem)

Why? - The battery is dead. (First why)

Why? - The alternator is not functioning. (Second why)

Why? - The alternator belt has broken. (Third why)

Why? - The alternator belt was well beyond its useful service life and not replaced. (Fourth why)

Why? - The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)

4. LEAN SIX SIGMA (DMAIC METHOD)

While many people have at least heard of Lean or Six Sigma, do we know what it is? Like many problem-solving processes, it has five main steps to follow.

Define : Clearly laying out the problem and soliciting feedback from those who are customers of the process is necessary to starting off on the right foot.

Measure : Quantifying the current state of the problem is a key to measuring how well the fix performed once it was implemented.

Analyze : Finding out the root cause of the problem (see number 5 “Root Cause Analysis” below) is one of the hardest and least explored steps of Six Sigma.

Improve : Crafting, executing, and testing the solution for measureable improvement is key. What doesn’t get implemented and measured really won’t make a difference.

Control : Sustaining the fix through a monitoring plan will ensure things continue to stay on track rather than being a short-lived solution.

5. ROOT CAUSE ANALYSIS

Compared to other methods, you’ll more often find this technique in a reactive problem-solving mode, but it is helpful nonetheless. Put simply, it requires a persistent approach to finding the highest-level cause, since most reasons you’ll uncover for a problem don’t tell the whole story.

Most of the time, there are many factors that contributed to an issue. The main reason is often shrouded in either intentional or unintentional secrecy. Taking the time to drill down to the root of the issue is key to truly solving the problem.

6. DEMING-SHEWHART CYCLE: PLAN-DO-CHECK-ACT (PDCA)

Named for W. Edwards Deming and Walter A. Shewhart, this model follows a four-step process:

Plan: Establish goals and objectives at the outset to gain agreement. It’s best to start on a small scale in order to test results and get a quick win.

Do: This step is all about the implementation and execution of the solution.

Check: Study and compare actual to expected results. Chart this data to identify trends.

Act/Adjust: If the check phase showed different results, then adjust accordingly. If worse than expected, then try another fix. If the same or better than expected, then use that as the new baseline for future improvements.

7. 8D PROBLEM-SOLVING

While this is named “8D” for eight disciplines, there are actually nine , because the first is listed as step zero. Each of the disciplines represents a phase of this process. Its aim is to implement a quick fix in the short term while working on a more permanent solution with no recurring issues.

Prepare and Plan : Collecting initial information from the team and preparing your approach to the process is a necessary first step.

Form a Team : Select a cross-functional team of people, one leader to run meetings and the process, and one champion/sponsor who will be the final decision-maker.

Describe the Problem : Using inductive and deductive reasoning approaches, lay out the precise issue to be corrected.

Interim Containment Action : Determine if an interim solution needs to be implemented or if it can wait until the final fix is firmed up. If necessary, the interim action is usually removed once the permanent solution is ready for implementation.

Root Cause Analysis and Escape Point : Finding the root of the issue and where in the process it could’ve been found but was not will help identify where and why the issue happened.

Permanent Corrective Action : Incorporating key criteria into the solution, including requirements and wants, will help ensure buy-in from the team and your champion.

Implement and Validate the Permanent Corrective Action : Measuring results from the fix implemented validates it or sends the team back to the drawing board to identity a more robust solution.

Prevent Recurrence : Updating work procedure documents and regular communication about the changes are important to keep old habits in check.

Closure and Team Celebration : Taking time to praise the team for their efforts in resolving the problem acknowledges the part each person played and offers a way to move forward.

8. ARMY PROBLEM SOLVING PROCESS

The US Army has been solving problems for more than a couple of centuries , so why not take a look at the problem-solving process they’ve refined over many years? They recommend this five step process:

Identify the Problem : Take time to understand the situation and define a scope and limitations before moving forward.

Gather Information : Uncover facts, assumptions, and opinions about the problem, and challenge them to get to the truth.

Develop Screening and Evaluation Criteria :

Five screening items should be questioned. Is it feasible, acceptable, distinguishable, and complete?

Evaluation criteria should have these 5 elements: short title, definition, unit of measure, benchmark, and formula.

Generate, Analyze, and Compare Possible Solutions : Most fixes are analyzed, but do you compare yours to one another as a final vetting method?

Choose a Solution and Implement : Put the fix into practice and follow up to ensure it is being followed consistently and having the desired effect.

9. HURSON'S PRODUCTIVE THINKING MODEL

Tim Hurson introduced this model in 2007 with his book, Think Better. It consists of the following six actions.

Ask "What is going on?" : Define the impact of the problem and the aim of its solution.

Ask "What is success?" : Spell out the expected outcome, what should not be in fix, values to be considered, and how things will be evaluated.

Ask "What is the question?" : Tailor questions to the problem type. Valuable resources can be wasted asking questions that aren’t truly relevant to the issue.

Generate answers : Prioritize answers that are the most relevant to solutions, without excluding any suggestion to present to the decision-makers.

Forge the solution : Refine the raw list of prioritized fixes, looking for ways to combine them for a more powerful solution or eliminate fixes that don’t fit the evaluation criteria.

Align resources: Identify resources, team, and stakeholders needed to implement and maintain the solution.

STEAL THIS THOROUGH 8-STEP PROBLEM-SOLVING PROCESS

Now that we’ve reviewed a number of problem-solving methods, we’ve compiled the various steps into a straightforward, yet in-depth, s tep-by-step process to use the best of all methods.

1. DIG DEEP: IDENTIFY, DEFINE, AND CLARIFY THE ISSUE

“Elementary, my dear Watson,” you might say.

This is true, but we often forget the fundamentals before trying to solve a problem. So take some time to gain understanding of critical stakeholder’s viewpoints to clarify the problem and cement consensus behind what the issue really is.

Sometimes it feels like you’re on the same page, but minor misunderstandings mean you’re not really in full agreement.. It’s better to take the time to drill down on an issue before you get too far into solving a problem that may not be the exact problem . Which leads us to…

2. DIG DEEPER: ROOT CAUSE ANALYSIS

This part of the process involves identifying these three items :

What happened?

Why did it happen?

What process do we need to employ to significantly reduce the chances of it happening again ?

You’ll usually need to sort through a series of situations to find the primary cause. So be careful not to stop at the first cause you uncover . Dig further into the situation to expose the root of the issue. We don’t want to install a solution that only fixes a surface-level issue and not the root. T here are typically three types of causes :

Physical: Perhaps a part failed due to poor design or manufacturing.

Human error: A person either did something wrong or didn’t do what needed to be done.

Organizational: This one is mostly about a system, process, or policy that contributed to the error .

When searching for the root cause, it is important to ensure people that you aren’t there to assign blame to a person but rather identify the problem so a fix can prevent future issues.

3. PRODUCE A VARIETY OF SOLUTION OPTIONS

So far, you’ve approached the problem as a data scientist, searching for clues to the real issue. Now, it’s important to keep your eyes and ears open, in case you run across a fix suggested by one of those involved in the process failure. Because they are closest to the problem, they will often have an idea of how to fix things. In other cases, they may be too close, and unable to see how the process could change.

The bottom line is to solicit solution ideas from a variety of sources , both close to and far away from the process you’re trying to improve.

You just never know where the top fix might come from!

4. FULLY EVALUATE AND SELECT PLANNED FIX(ES)

Evaluating solutions to a defined problem can be tricky since each one will have cost, political, or other factors associated with it. Running each fix through a filter of cost and impact is a vital step toward identifying a solid solution and hopefully settling on the one with the highest impact and low or acceptable cost.

Categorizing each solution in one of these four categoriescan help teams sift through them:

High Cost/Low Impact: Implement these last, if at all, since t hey are expensive and won’t move the needle much .

Low Cost/Low Impact: These are cheap, but you won’t get much impact.

High Cost/High Impact: These can be used but should be second to the next category.

Low Cost/High Impact: Getting a solid “bang for your buck” is what these fixes are all about. Start with these first .

5. DOCUMENT THE FINAL SOLUTION AND WHAT SUCCESS LOOKS LIKE

Formalize a document that all interested parties (front-line staff, supervisors, leadership, etc.) agree to follow. This will go a long way towards making sure everyone fully understands what the new process looks like, as well as what success will look like .

While it might seem tedious, try to be overly descriptive in the explanation of the solution and how success will be achieved. This is usually necessary to gain full buy-in and commitment to continually following the solution. We often assume certain things that others may not know unless we are more explicit with our communications.

6. SUCCESSFULLY SELL AND EXECUTE THE FIX

Arriving at this stage in the process only to forget to consistently apply the solution would be a waste of time, yet many organizations fall down in the execution phase . Part of making sure that doesn’t happen is to communicate the fix and ask for questions multiple times until all parties have a solid grasp on what is now required of them.

One often-overlooked element of this is the politics involved in gaining approval for your solution. Knowing and anticipating objections of those in senior or key leadership positions is central to gaining buy-in before fix implementation.

7. RINSE AND REPEAT: EVALUATE, MONITOR, AND FOLLOW UP

Next, doing check-ins with the new process will ensure that the solution is working (or identity if further reforms are necessary) . You’ll also see if the measure of predefined success has been attained (or is making progress in that regard).

Without regularly monitoring the fix, you can only gauge the success or failure of the solution by speculation and hearsay. And without hard data to review, most people will tell their own version of the story.

8. COLLABORATIVE CONTINGENCIES, ITERATION, AND COURSE CORRECTION

Going into any problem-solving process, we should take note that we will not be done once the solution is implemented (or even if it seems to be working better at the moment). Any part of any process will always be subject to the need for future iterations and course corrections . To think otherwise would be either foolish or naive.

There might need to be slight, moderate, or wholesale changes to the solution previously implemented as new information is gained, new technologies are discovered, etc.

14 FRUITFUL RESOURCES AND EXERCISES FOR YOUR PROBLEM-SOLVING JOURNEY

Want to test your problem-solving skills?

Take a look at these twenty case study scenario exercises to see how well you can come up with solutions to these problems.

Still have a desire to discover more about solving problems?

Check out these 14 articles and books...

1. THE LEAN SIX SIGMA POCKET TOOLBOOK: A QUICK REFERENCE GUIDE TO NEARLY 100 TOOLS FOR IMPROVING QUALITY AND SPEED

This book is like a Bible for Lean Six Sigma , all in a pocket-sized package.

2. SOME SAGE PROBLEM SOLVING ADVICE

The American Society for Quality has a short article on how it’s important to focus on the problem before searching for a solution.

3. THE SECRET TO BETTER PROBLEM SOLVING: HARVARD BUSINESS REVIEW

Wondering if you are solving the right problems? Check out this Harvard Business Review article.

4. PROBLEM SOLVING 101 : A SIMPLE BOOK FOR SMART PEOPLE

Looking for a fun and easy problem-solving book that was written by a McKinsey consultant? Take a look!

5. THE BASICS OF CREATIVE PROBLEM SOLVING – CPS

If you want a deeper dive into the seven steps of Creative Problem Solving , see this article.

6. APPRECIATIVE INQUIRY : A POSITIVE REVOLUTION IN CHANGE

Appreciative Inquiry has been proven effective in organizations ranging from Roadway Express and British Airways to the United Nations and the United States Navy. Review this book to join the positive revolution.

7. PROBLEM SOLVING: NINE CASE STUDIES AND LESSONS LEARNED

The Seattle Police Department has put together nine case studies that you can practice solving . While they are about police work, they have practical application in the sleuthing of work-related problems.

8. ROOT CAUSE ANALYSIS : THE CORE OF PROBLEM SOLVING AND CORRECTIVE ACTION

Need a resource to delve further into Root Cause Analysis? Look no further than this book for answers to your most vexing questions .

9. SOLVING BUSINESS PROBLEMS : THE CASE OF POOR FRANK

This solid case study illustrates the complexities of solving problems in business.

10. THE 8-DISCIPLINES PROBLEM SOLVING METHODOLOGY

Learn all about the “8Ds” with this concise primer.

11. THE PROBLEM-SOLVING PROCESS THAT PREVENTS GROUPTHINK HBR

Need to reduce groupthink in your organization’s problem-solving process ? Check out this article from the Harvard Business Review.

12. THINK BETTER : AN INNOVATOR'S GUIDE TO PRODUCTIVE THINKING

Tim Hurson details his own Productive Thinking Model at great length in this book from the author.

13. 5 STEPS TO SOLVING THE PROBLEMS WITH YOUR PROBLEM SOLVING INC MAGAZINE

This simple five-step process will help you break down the problem, analyze it, prioritize solutions, and sell them internally.

14. CRITICAL THINKING : A BEGINNER'S GUIDE TO CRITICAL THINKING, BETTER DECISION MAKING, AND PROBLEM SOLVING!

LOOKING FOR ASSISTANCE WITH YOUR PROBLEM-SOLVING PROCESS?

There's a lot to take in here, but following some of these methods are sure to improve your problem-solving process. However, if you really want to take problem-solving to the next level, InitiativeOne can come alongside your team to help you solve problems much faster than you ever have before.

There are several parts to this leadership transformation process provided by InitiativeOne, including a personal profile assessment, cognitive learning, group sessions with real-world challenges, personal discovery, and a toolkit to empower leaders to perform at their best.

There are really only two things stopping good teams from being great. One is how they make decisions and two is how they solve problems. Contact us today to grow your team’s leadership performance by making decisions and solving problems more swiftly than ever before!

• Featured Post

Recent Posts

Does Your Leadership Deserve Two Thumbs Up?

3 Ways to Harness the Power of Inspiration

Leadership Self-Check

Opmerkingen

BUS403: Negotiations and Conflict Management

Problem-Solving and Decision-Making in Groups

This text summarizes common characteristics of problems and the five steps in group problem-solving. The reading describes brainstorming and discussions that should occur before group decision-making, compares and contrasts decision-making techniques, and explores various influences on decision-making. The section "Getting Competent" emphasizes the need for leaders and managers to delegate tasks and responsibilities as they identify specialized skills among their teams and employees.

Group Problem-Solving Process

Group problem-solving can be a confusing puzzle unless it is approached systematically.

There are several variations of similar problem-solving models based on American scholar John Dewey's reflective thinking process. As you read through the steps in the process, think about how you can apply what we learned regarding the general and specific elements of problems. Some of the following steps are straightforward, and they are things we would logically do when faced with a problem.

However, taking a deliberate and systematic approach to problem-solving has been shown to benefit group functioning and performance. A deliberate approach is especially beneficial for groups that do not have an established history of working together and will only be able to meet occasionally.

Although a group should attend to each step of the process, group leaders or other group members who facilitate problem-solving should be cautious not to dogmatically follow each element of the process or force a group along. Such a lack of flexibility could limit group member input and negatively affect cohesion and climate.

Step 1: Define the Problem

Define the problem by considering the three elements shared by every problem: the current undesirable situation, the goal or more desirable situation, and obstacles. At this stage, group members share what they know about the current situation, without proposing solutions or evaluating the information.

Here are some good questions to ask during this stage: What is the current difficulty? How did we come to know that the difficulty exists? Who/what is involved? Why is it meaningful/urgent/important? What have the effects been so far? What, if any, elements of the difficulty require clarification?

At the end of this stage, the group should be able to compose a single sentence that summarizes the problem called a problem statement . Avoid wording in the problem statement or question that hints at potential solutions. A small group formed to investigate ethical violations of city officials could use the following problem statement: "Our state does not currently have a mechanism for citizens to report suspected ethical violations by city officials".

Step 2: Analyze the Problem

During this step a group should analyze the problem and the group's relationship to the problem. Whereas the first step involved exploring the "what" related to the problem, this step focuses on the "why." At this stage, group members can discuss the potential causes of the difficulty. Group members may also want to begin setting an agenda or timeline for the group's problem-solving process, looking forward to the other steps.

To fully analyze the problem, the group can discuss the five common problem variables discussed before. Here are two examples of questions that the group formed to address ethics violations might ask: Why doesn't our city have an ethics reporting mechanism? Do cities of similar size have such a mechanism? Once the problem has been analyzed, the group can pose a problem question that will guide the group as it generates possible solutions. "How can citizens report suspected ethical violations of city officials and how will such reports be processed and addressed?" As you can see, the problem question is more complex than the problem statement, since the group has moved on to more in-depth discussion of the problem during step 2.

Step 3: Generate Possible Solutions

During this step, group members generate possible solutions to the problem. Again, solutions should not be evaluated at this point, only proposed and clarified. The question should be, "What could we do to address this problem?" not "What should we do to address it?" It is perfectly OK for a group member to question another person's idea by asking something like "What do you mean?" or "Could you explain your reasoning more?"

Discussions at this stage may reveal a need to return to previous steps to better define or more fully analyze a problem. Since many problems are multifaceted, group members must generate solutions for each part of the problem separately, ensuring multiple solutions for each part. Stopping the solution-generating process prematurely can lead to groupthink. For the problem question previously posed, the group would need to generate solutions for all three parts of the problem included in the question.

Possible solutions for the first part of the problem (how can citizens report ethical violations?) may include an "online reporting system, email, in-person, anonymously, on-the-record," and so on.

Possible solutions for the second part of the problem (how will reports be processed?) may include "daily by a newly appointed ethics officer, weekly by a nonpartisan nongovernment employee," and so on. Possible solutions for the third part of the problem (how will reports be addressed?) may include "by a newly appointed ethics commission, by the accused's supervisor, by the city manager," and so on.

Step 4: Evaluate Solutions

During this step, solutions can be critically evaluated based on their credibility, completeness, and worth. Once the potential solutions have been narrowed based on more obvious differences in relevance and/or merit, the group should analyze each solution based on its potential effects – especially negative effects. Groups that are required to report the rationale for their decision or whose decisions may be subject to public scrutiny would be wise to make a set list of criteria for evaluating each solution. Additionally, solutions can be evaluated based on how well they fit with the group's charge and the group's abilities.

To do this, group members may ask, "Does this solution live up to the original purpose or mission of the group?" "Can the solution be implemented with our current resources and connections?" and "How will this solution be supported, funded, enforced, and assessed?" Secondary tensions and substantive conflict, two concepts discussed earlier, emerge during this step of problem-solving, and group members will need to employ effective critical thinking and listening skills. Decision-making is part of the larger problem-solving process, and it plays a prominent role in this step. While there are several fairly similar models for problem-solving, there are many varied decision-making techniques that groups can use.

For example, to narrow the proposed solutions, group members may decide by majority vote, by weighing the pros and cons, or by discussing them until a consensus is reached. There are also more complex decision-making models like the "six hats method," which we will discuss later. Once the final decision is reached, the group leader or facilitator should confirm that the group is in agreement. It may be beneficial to let the group break for a while or even to delay the final decision until a later meeting to allow people time to evaluate it outside of the group context.

Step 5: Implement and Assess the Solution

Implementing the solution requires some advanced planning, and it should not be rushed unless the group is operating under strict time restraints or delay may lead to some kind of harm. Although some solutions can be implemented immediately, others may take days, months, or years. As was noted earlier, it may be beneficial for groups to poll those affected by the solution to their opinion or even to do a pilot test to observe the solution's effectiveness and how people react to it.

Before implementation, groups should also determine how and when they would assess the solution's effectiveness by asking, "How will we know if the solution is working?" Since solution assessment will vary based on whether or not the group is disbanded, groups should also consider the following questions: If the group disbands after implementation, who will be responsible for assessing the solution? If the solution fails, will the same group reconvene or will a new group be formed?

Once a solution has been reached and the group has the "green light" to implement it, it should proceed deliberately and cautiously, making sure to consider possible consequences and address them as needed. Certain elements of the solution may need to be delegated to various people inside and outside the group. Group members may also be assigned to implement a particular part of the solution based on their role in the decision-making or because it connects to their expertise. Likewise, group members may be tasked with publicizing the solution or "selling" it to a particular group of stakeholders. Last, the group should consider its future. In some cases, the group will get to decide if it will stay together and continue working on other tasks or if it will disband. In other cases, outside forces determine the group's fate.

Getting Competent

Giving a group presentation requires that individual group members and the group solve many problems and make many decisions. Although having more people involved in a presentation increases logistical difficulties and has the potential to create more conflict, a well-prepared and well-delivered group presentation can be more engaging and effective than a typical presentation.

The main problems facing a group giving a presentation are (1) dividing responsibilities, (2) coordinating schedules and time management, and (3) working out the logistics of the presentation delivery.

Regarding dividing responsibilities, assigning individual work at the first meeting and then trying to fit it all together before the presentation (which is what many college students do when faced with a group project) is not the recommended method. Integrating content and visual aids created by several different people into a seamless final product takes time and effort, and the person "stuck" with this job at the end usually ends up developing some resentment toward his or her group members.

While it is OK for group members to work independently outside of group meetings, spend time working together to help set up some standards for content and formatting expectations that will help make later integration of work easier. Taking the time to complete one part of the presentation together can help set those standards for later individual work.

Discuss the roles various group members will play openly to avoid role confusion. There could be one point person for keeping track of the group's progress and schedule, one point person for communication, one point person for content integration, one point person for visual aids, and so on. Each person shouldn't do all that work on his or her own but help focus the group's attention on his or her specific area during group meetings.

Scheduling group meetings is one of the most challenging problems groups face, given people's busy lives. From the beginning, it should be communicated that the group needs to spend considerable time in face-to-face meetings. Group members should know they may have to sacrifice occasionally to attend. Especially important is the commitment to scheduling time to rehearse the presentation. Consider creating a contract of group guidelines that includes expectations for meeting attendance to increase group members' commitment.

Group presentations require members to navigate many logistics of their presentation. While it may be easier for a group to assign each member to create a five-minute segment and then transition from one person to the next, this is not the most engaging method. Creating a master presentation and assigning individual speakers creates a more fluid and dynamic presentation. It allows everyone to become familiar with the content, which can help if a person does not show up to present and during the question-and-answer section.

Once the presentation's content is complete, figure out introductions, transitions, visual aids, and the use of time and space. In terms of introductions, figure out if one person will introduce all the speakers at the beginning, if speakers will introduce themselves at the beginning, or if introductions will occur as the presentation progresses. In terms of transitions, make sure each person has included in his or her speaking notes when presentation duties switch from one person to the next. 

Visual aids can potentially cause hiccups in a group presentation if they aren't fluidly integrated. Practicing visual aids and having one person control them may help prevent this. Know how long your presentation is and know how you're going to use the space. Presenters should know how long the whole presentation should be and how long each segment should be so that everyone can share the responsibility of keeping time. Also consider the size and layout of the presentation space. You don't want presenters huddled in a corner until it's their turn to speak or trapped behind furniture when their turn comes around.

Of the three main problems facing group presenters, which do you think is the most challenging and why?

• Why do you think people tasked with a group presentation (especially students) prefer to divide the parts and have members work on them independently before coming back together and integrating each part?
• What problems emerge from this method? In what ways might developing a master presentation and then assigning parts to different speakers be better than the more divided method? What are the drawbacks to the master presentation method?

• school Campus Bookshelves
• menu_book Bookshelves
• perm_media Learning Objects
• login Login
• how_to_reg Request Instructor Account
• hub Instructor Commons
• Download Page (PDF)
• Download Full Book (PDF)
• Periodic Table
• Physics Constants
• Scientific Calculator
• Reference & Cite
• Tools expand_more
• Readability

selected template will load here

This action is not available.

3.3: Creative Problem-Solving Process

• Last updated
• Save as PDF
• Page ID 62756

LEARNING OBJECTIVES

By the end of this section, you will be able to:

• Describe the five steps in the creative problem-solving process
• Identify and describe common creative problem-solving tools

Creativity can be an important trait of an entrepreneur. In that discussion, we learned about creativity’s role in innovation . Here, we will look in more depth at creativity’s role in problem-solving . Let’s first formally define creativity as the development of original ideas to solve an issue. The intent of being an entrepreneur is to break away from practical norms and use imagination to embrace quick and effective solutions to an existing problem, usually outside the corporate environment.

The Steps of the Creative Problem-Solving Process

Training oneself to think like an entrepreneur means learning the steps to evaluating a challenge: clarify, ideate, develop, implement, and evaluate (Figure 3.3.1).

Step 1: Clarify

To clarify is the critical step of recognizing the existence of a gap between the current state and a desired state. This can also be thought of as having need awareness , which occurs when the entrepreneur notes a gap between societal or customer needs and actual circumstances. Clarifying the problem by speaking with clients and developing a detailed description of the problem brings the specifics of a problem to light. Failure to identify the specifics of a problem leaves the entrepreneur with the impossible task of solving a ghost problem, a problem that is fully unknown or unseen. To establish and maintain credibility, an entrepreneur must clarify the problem by focusing on solving the problem itself, rather than solving a symptom of the problem.

For example, a farm could have polluted water, but it would not be enough to solve the problem only on that farm. Clarifying would involve identifying the source of the pollution to adequately tackle the problem. After gaining an understanding of a problem, the entrepreneur should begin to formulate plans for eliminating the gap. A fishbone diagram, as shown in Figure 3.3.2, is a tool that can be used to identify the causes of such a problem.

In the case of our water pollution example, a fishbone diagram exploring the issue might reveal the items shown in Figure 3.3.3.

Step 2: Ideate

To ideate is the step of the creative problem-solving process that involves generating and detailing ideas by the entrepreneur. After collecting all information relevant to the problem, the entrepreneur lists as many causes of the problem as possible. This is the step in which the largest variety of ideas are put forth. Each idea must be evaluated for feasibility and cost as a solution to the problem. If a farm does not have clean water, for example, the entrepreneur must list causes of toxic water and eliminate as many of those causes as possible. The entrepreneur must then move forward investigating solutions to bring the water back to a safe state. If, say, nearby livestock are polluting the water, the livestock should be isolated from the water source.

Step 3: Develop

To develop is the step in which the entrepreneur takes the list of ideas generated and tests each solution for feasibility. The entrepreneur must consider the cost of each idea and the obstacles to implementation. In the preceding example, adding a chemical to the water may not be a feasible solution to the farmer. Not every farmer wants additional chloride or fluoride added to the water due to the effect on both humans and livestock. These tradeoffs should be addressed in the feasibility assessment. The farmer might prefer a filtration system, but the cost of that solution might not be practicable. The entrepreneur should identify and assess alternative solutions to find one that is most cost-effective and feasible to the customer.

Step 4: Implement

To implement is the step in which the solution to the problem is tested and evaluated. The entrepreneur walks through the planned implementation with the client and tests each part of the solution, if a service, or thoroughly tests a developed good. The entrepreneur implements the solution and goes through a structured system of follow-up to ensure the solution remains effective and viable. In the water example, the solution would be reducing runoff from toxic insecticides by adding prairie strips, buffers of grass, and vegetation along banks of streams.

Step 5: Evaluate

To evaluate is the step in which the final solution is assessed. This is a very important step that entrepreneurs often overlook. Any fallacy in the implementation of the product or service is reassessed, and new solutions are implemented. A continual testing process may be needed to find the final solution. The prairie strips, buffers of grass, and vegetation along banks of streams chosen in the farming water example should then be analyzed and tested to ensure the chosen solution changed the content of the water.

ARE YOU READY?

Implementing Creative Problem Solving

Removing waste is a problem, and it can also present an entrepreneurial opportunity. Try to examine ways in which waste products that you usually pay to have hauled away can now generate revenue. Whether it’s recycling aluminum cans or cardboard, or garbage that could be used to feed animals, your task is to come up with solutions to this entrepreneurial-oriented problem.

• Try following the first step of the creative problem-solving process and clearly identify the problem.
• Next, gather data and formulate the challenge.
• Then, explore ideas and come up with solutions.
• Develop a plan of action.
• Finally, note how you would evaluate the effectiveness of your solution.

Using Creativity to Solve Problems

Entrepreneurs are faced with solving many problems as they develop their ideas for filling gaps, whether those opportunities involve establishing a new company or starting a new enterprise within an existing company. Some of these problems include staffing, hiring and managing employees, handling legal compliance, funding, marketing, and paying taxes. Beyond the mundane activities listed, the entrepreneur, or the team that the entrepreneur puts in place, is indispensable in maintaining the ongoing creativity behind the product line or service offered. Innovation and creativity in the business are necessary to expand the product line or develop a groundbreaking service.

It is not necessary for the entrepreneur to feel isolated when it comes to finding creative solutions to a problem. There are societies, tools, and new methods available to spur the creativity of the entrepreneur that will further support the success and expansion of a new enterprise. 14 Learning and using entrepreneurial methods to solve problems alleviates the stress many startup owners feel. The entrepreneur’s creativity will increase using collaborative methodologies. Some entrepreneurial collaborative methodologies include crowdsourcing, brainstorming, storyboarding, conducting quick online surveys to test ideas and concepts, and team creativity activities.

Crowdsourcing

Professor Daren Brabham at the University of Southern California has written books on crowdsourcing and touts its potential in for-profit and not-for-profit business sectors. He defines it simply as “an online, distributed problem-solving and production model.” 15 Crowdsourcing involves teams of amateurs and nonexperts working together to form a solution to a problem. 16 The idea, as cbsnews.com’s Jennifer Alsever has put it, is to “tap into the collective intelligence of the public at large to complete business-related tasks that a company would normally either perform itself or outsource to a third-party provider. Yet free labor is only a narrow part of crowdsourcing's appeal. More importantly, it enables managers to expand the size of their talent pool while also gaining deeper insight into what customers really want. The challenge is to take a cautionary approach to the ‘wisdom of the crowd,’ which can lead to a ‘herd’ mentality.” 17

LINK TO LEARNING

Read this article that discusses what crowdsourcing is, how to use it, and its benefits for more information.

This new business prototype, similar to outsourcing, features an enterprise posting a problem online and asking for volunteers to consider the problem and propose solutions. Volunteers earn a reward, such as prize money, promotional materials like a T-shirt, royalties on creative outlets like photos or designs, and in some cases, compensation for their labor. Before proposing the solution, volunteers learn that the solutions become the intellectual property of the startup posting the problem. The solution is then mass-produced for profit by the startup that posted the problem. 18 The process evolves into the crowdsourcing process after the enterprise mass produces and profits from the labor of the volunteers and the team. Entrepreneurs should consider that untapped masses have solutions for many issues for which agendas do not yet exist. Crowdsourcing can exploit those agendas and add to the tools used to stimulate personal creativity. This type of innovation is planned and strategically implemented for profit.

For example, Bombardier held a crowdsourced innovation contest to solicit input on the future of train interiors, including seat design and coach class interior. A corporate jury judged the submissions, with the top ten receiving computers or cash prizes. Companies are often constrained, however, by internal rules limiting open source or external idea sourcing, as they could be accused of “stealing” an idea. While crowdsourcing outside of software can be problematic, some products such as MakerBot’s 3D printers, 3DR’s drones, and Jibo’s Social Robot have used developer kits and “makers” to help build a community and stimulate innovation from the outside.

WORK IT OUT

A Crowdsourced Potato Chip

In an effort to increase sales among millennials, PepsiCo turned to crowdsourcing to get new flavor ideas for their Lay’s potato chips (called Walker’s in the UK). Their 2012 campaign, “Do Us a Flavor,” was so successful that they received over 14 million submissions. The winner was Cheesy Garlic Bread, which increased their potato chip sales by 8 percent during the first three months after the launch.

• What are some other products that would work well for a crowdsourced campaign contest?
• What items wouldn’t work well?

Amazon’s Mechanical Turk is an online crowdsourcing platform that allows individuals to post tasks for workers to complete. In many instances, these tasks are compensated, but the payment can be less than one dollar per item completed. Mechanical Turk is one of the largest and most well-known crowdsourcing platforms, but there are a number of other more niche ones as well that would apply to smaller markets. In the case of innovation contests and outsourced tasks from corporations, those tasks may be hosted internally by the corporation.

Brainstorming

Brainstorming is the generation of ideas in an environment free of judgment or dissension with the goal of creating solutions. Brainstorming is meant to stimulate participants into thinking about problem-solving in a new way. Using a multifunctional group, meaning participants come from different departments and with different skill sets, gives entrepreneurs and support teams a genuine chance to suggest and actualize ideas. The group works together to refine and prototype potential solutions to a problem.

Brainstorming is a highly researched and often practiced technique for the development of innovative solutions. One of the more successful proponents of brainstorming is the United Nations Children’s Fund (UNICEF). UNICEF faces unique problems of solving resource problems for mothers and children in underdeveloped nations. See how UNICEF practices brainstorming to solve problems including child survival, gender inclusion, refugee crises, education, and others.

The setting for a brainstorming session should remain as informal and relaxed as possible. The group needs to avoid standard solutions. All ideas are welcome and listed and considered with no censorship and with no regard to administrative restrictions. All team members have an equal voice. The focus of brainstorming is on quantity of ideas rather than on the ideal solution provided in every suggestion. A classic entrepreneurial brainstorming activity, as popularized by business software developer Strategyzer, is known as the “silly cow” exercise. Teams come up with ideas for new business models pertaining to a cow, with the results often outrageous, ranging from sponsored cows to stroking cows for therapeutic release. Participants are asked to identify some aspect of a cow and develop three business models around that concept in a short time period, typically two minutes or fewer. The activity is designed to get creative juices flowing.

Watch this video from ABC’s Nightline that shows how IDEO designed a new shopping cart for an example of a design process that involves brainstorming.

Storyboarding

Storyboarding is the process of presenting an idea in a step-by-step graphic format, as Figure 3.3.4 shows. This tool is useful when the entrepreneur is attempting to visualize a solution to a problem. The steps to the solution of a problem are sketched and hung in graphic format. Once the original graphic is placed, images of steps working toward a solution are added, subtracted, and rearranged on a continual basis, until the ultimate solution emerges in the ultimate graphic format. For many years, entrepreneurs have used this process to create a pre-visual for various media sequences.

Team Creativity

Team creativity is the process whereby an entrepreneur works with a team to create an unexpected solution for an issue or challenge. Teams progress through the same creative problem-solving process described already: clarify, ideate, develop, implement, and evaluate. The main advantage of team creativity is the collaboration and support members receive from one another. Great teams trust in other team members, have diverse members with diverse points of view, are cohesive, and have chemistry.

Team members should work in a stress-free and relaxing environment. Reinforcement and expansion of ideas in the team environment motivates the team to continually expand horizons toward problem solution. A small idea in a team may spark the imagination of a team member to an original idea. Mark Zuckerberg, co-founder of Facebook, once said, “The most important thing for you as an entrepreneur trying to build something is, you need to build a really good team. And that’s what I spend all my time on.” 19

ENTREPRENEUR IN ACTION

Taaluma Totes 20

Young entrepreneurs Jack DuFour and Alley Heffern began to notice the beautiful fabrics that came from the different countries they visited. The entrepreneurs thought about what could be done with the fabrics to create employment opportunities both in the country from which the fabric originated and in their home base of Virginia. They decided to test producing totes from the fabrics they found and formed Taaluma Totes (Figure 3.3.5). DuFour and Heffern also wanted to promote the production of these fabrics and help underserved populations in countries where the fabric originated maintain a living or follow a dream.

The team continued to test the process and gathered original fabrics, which they sent to Virginia to create totes. They trained individuals with disabilities in Virginia to manufacture the totes, thus serving populations in the United States. The entrepreneurs then decided to take 20 percent of their profits and make microloans to farmers and small business owners in the countries where the fabric originated to create jobs there. Microloans are small loans, below $50,000, which certain lenders offer to enterprising startups. These startups, for various reasons (they are in poor nations, at the poverty level), can’t afford a traditional loan from a major bank. The lenders offer business support to the borrower, which in turn helps the borrower repay the microloan. The microloans from Taaluma are repaid when the borrower is able. Repayments are used to buy more fabric, completing Taaluma’s desire to serve dual populations. If the process proved unsuccessful, the co-owners would revise the process to meet the plan’s requirements.

DuFour and Heffern now have fabrics from dozens of countries from Thailand to Ecuador. The totes are specialized with features to meet individual needs. The product line is innovated regularly and Taaluma Totes serves a dual purpose of employing persons with disabilities in Virginia and creating employment for underserved populations in other countries.

The Ultimate Problem-Solving Process Guide: 31 Steps and Resources

[email protected]

16 Min Read

Got Challenges with Your Problem-Solving Process? Are You Frustrated?

prob·lem-solv·ing noun

-the process of finding solutions to difficult or complex issues.

It sounds so simple, doesn’t it?

But in reality problem-solving is hard. It’s almost always more complex than it seems. That’s why problem-solving can be so frustrating sometimes. You can feel like you’re spinning your wheels, arguing in circles, or just failing to find answers that actually work.

And when you’ve got a group working on a problem, it can get even muddier …differences of opinions, viewpoints colored by different backgrounds, history, life experiences, you name it. We’re all looking at life and work from different angles, and that often means disagreement. Sometimes sharp disagreement.

That human element, figuring out how to take ourselves out of the equation and make solid, fact-based decisions , is precisely why there’s been so much written on problem-solving. Which creates its own set of problems.

Whose method is best? How can you possibly sift through them all? Are we to have one person complete the entire problem-solving process by themselves or rely on a larger team to find answers to our most vexing challenges in the workplace ?

Today, we’re going to make sense of it all. We’ll take a close look at nine top problem-solving methods. Then we’ll grab the best elements of all of them to give you a process that will have your team solving problems faster, with better results , and maybe with less sharp disagreement.

Ready to dive in?

9 Profitable Problem-Solving Techniques and Methods

While there are loads of methods to choose from, we are going to focus on nine of the more common ones. You can use some of these problem-solving techniques reactively to solve a known issue or proactively to find more efficient or effective ways of performing tasks. If you want to explore other methods, check out this resource here .

A helpful bit of advice here is to reassure people that you aren’t here to identify the person that caused the problem . You’re working to surface the issue, solve it and make sure it doesn’t happen again, regardless of the person working on the process. It can’t be understated how important it is to continually reassure people of this so that you get unfiltered access to information.

Without this, people will often hide things to protect themselves . After all, nobody wants to look bad, do they?

With that said, let’s get started…

Alex Osborn coined the term “Creative Problem Solving” in the 1940s with this simple four-step process:

• Clarify : Explore the vision, gather data, and formulate questions.
• Ideate : This stage should use brainstorming to generate divergent thinking and ideas rather than the random ideas normally associated with brainstorming.
• Develop : Formulate solutions as part of an overall plan.
• Implement : Put the plan into practice and communicate it to all parties.

Source: http://www.davidcooperrider.com/ai-process/

This method seeks, first and foremost, to identify the strengths in people and organizations and play to that “positive core” rather than focus our energies on improving weaknesses . It starts with an “affirmative topic,” followed by the “positive core (strengths).” Then this method delves into the following stages:

• Discovery (fact-finding)
• Dream (visioning the future)
• Design (strategic purpose)
• Destiny (continuous improvement)

This method simply suggests that we ask “Why” at least five times during our review of the problem and in search of a fix. This helps us dig deeper to find the the true reason for the problem, or the root cause. Now, this doesn’t mean we just keeping asking the same question five times. Once we get an answer to our first “why”, we ask why to that answer until we get to five “whys”.

Using the “five whys” is part of the “Analyze” phase of Six Sigma but can be used with or without the full Six Sigma process.

Review this simple Wikipedia example of the 5 Whys in action:

The vehicle will not start. (the problem)

• Why? – The battery is dead. (First why)
• Why? – The alternator is not functioning. (Second why)
• Why? – The alternator belt has broken. (Third why)
• Why? – The alternator belt was well beyond its useful service life and not replaced. (Fourth why)
• Why? – The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)

While many people have at least heard of Lean or Six Sigma, do we know what it is? Like many problem-solving processes, it has five main steps to follow.

• Define : Clearly laying out the problem and soliciting feedback from those who are customers of the process is necessary to starting off on the right foot.
• Measure : Quantifying the current state of the problem is a key to measuring how well the fix performed once it was implemented.
• Analyze : Finding out the root cause of the problem (see number 5 “Root Cause Analysis” below) is one of the hardest and least explored steps of Six Sigma.
• Improve : Crafting, executing, and testing the solution for measureable improvement is key. What doesn’t get implemented and measured really won’t make a difference.
• Control : Sustaining the fix through a monitoring plan will ensure things continue to stay on track rather than being a short-lived solution.

Compared to other methods, you’ll more often find this technique in a reactive problem-solving mode, but it is helpful nonetheless. Put simply, it requires a persistent approach to finding the highest-level cause , since most reasons you’ll uncover for a problem don’t tell the whole story.

Most of the time, there are many factors that contributed to an issue. The main reason is often shrouded in either intentional or unintentional secrecy. T aking the time to drill down to the root of the issue is key to truly solving the problem.

Named for W. Edwards Deming and Walter A. Shewhart, this model follows a four-step process:

• Plan : Establish goals and objectives at the outset to gain agreement . It’s best to start on a small scale in order to test results and get a quick win.
• Do : This step is all about the implementation and execution of the solution .
• Check : Study and compare actual to expected results. Chart this data to identify trends.
• Act/Adjust : If the check phase showed different results, then adjust accordingly . If worse than expected, then try another fix. If the same or better than expected, then use that as the new baseline for future improvements.

While this is named “8D” for eight disciplines, there are actually nine , because the first is listed as step zero. Each of the disciplines represents a phase of this process. Its aim is to implement a quick fix in the short term while working on a more permanent solution with no recurring issues.

• Prepare and Plan : Collecting initial information from the team and preparing your approach to the process is a necessary first step.
• Form a Team : Select a cross-functional team of people, one leader to run meetings and the process, and one champion/sponsor who will be the final decision-maker.
• Describe the Problem : Using inductive and deductive reasoning approaches , lay out the precise issue to be corrected.
• Interim Containment Action : Determine if an interim solution needs to be implemented or if it can wait until the final fix is firmed up. If necessary, the interim action is usually removed once the permanent solution is ready for implementation.
• Root Cause Analysis and Escape Point : Finding the root of the issue and where in the process it could’ve been found but was not will help identify where and why the issue happened.
• Permanent Corrective Action : Incorporating key criteria into the solution, including requirements and wants, will help ensure buy-in from the team and your champion.
• Implement and Validate the Permanent Corrective Action : Measuring results from the fix implemented validates it or sends the team back to the drawing board to identity a more robust solution.
• Prevent Recurrence : Updating work procedure documents and regular communication about the changes are important to keep old habits in check.
• Closure and Team Celebration : Taking time to praise the team for their efforts in resolving the problem acknowledges the part each person played and offers a way to move forward.

The US Army has been solving problems for more than a couple of centuries , so why not take a look at the problem-solving process they’ve refined over many years? They recommend this five step process:

• Identify the Problem : Take time to understand the situation and define a scope and limitations before moving forward.
• Gather Information : Uncover facts, assumptions, and opinions about the problem, and challenge them to get to the truth.
• Five screening items should be questioned. Is it feasible, acceptable, distinguishable, and complete?
• Evaluation criteria should have these 5 elements: short title, definition, unit of measure, benchmark, and formula.
• Generate, Analyze, and Compare Possible Solutions : Most fixes are analyzed, but do you compare yours to one another as a final vetting method?
• Choose a Solution and Implement : Put the fix into practice and follow up to ensure it is being followed consistently and having the desired effect.

Tim Hurson introduced this model in 2007 with his book, Think Better. It consists of the following six actions.

• Ask “What is going on?” : Define the impact of the problem and the aim of its solution.
• Ask “What is success?” : Spell out the expected outcome, what should not be in fix, values to be considered, and how things will be evaluated.
• Ask “What is the question?” : Tailor questions to the problem type. Valuable resources can be wasted asking questions that aren’t truly relevant to the issue.
• Generate answers : Prioritize answers that are the most relevant to solutions, without excluding any suggestion to present to the decision-makers.
• Forge the solution : Refine the raw list of prioritized fixes, looking for ways to combine them for a more powerful solution or eliminate fixes that don’t fit the evaluation criteria.
• Align resources: Identify resources, team, and stakeholders needed to implement and maintain the solution.

Steal This Thorough 8-Step Problem-Solving Process

Now that we’ve reviewed a number of problem-solving methods, we’ve compiled the various steps into a straightforward, yet in-depth, s tep-by-step process to use the best of all methods.

Dig Deep: Identify, Define, and Clarify the Issue

“Elementary, my dear Watson,” you might say.

This is true, but we often forget the fundamentals before trying to solve a problem. So take some time to gain understanding of critical stakeholder’s viewpoints to clarify the problem and cement consensus behind what the issue really is.

Sometimes it feels like you’re on the same page, but minor misunderstandings mean you’re not really in full agreement.. It’s better to take the time to drill down on an issue before you get too far into solving a problem that may not be the exact problem . Which leads us to…

Dig Deeper: Root Cause Analysis

This part of the process involves identifying these three items :

• What happened?
• Why did it happen?
• What process do we need to employ to significantly reduce the chances of it happening again ?

You’ll usually need to sort through a series of situations to find the primary cause. So be careful not to stop at the first cause you uncover . Dig further into the situation to expose the root of the issue. We don’t want to install a solution that only fixes a surface-level issue and not the root. T here are typically three types of causes :

• Physical: Perhaps a part failed due to poor design or manufacturing.
• Human error: A person either did something wrong or didn’t do what needed to be done.
• Organizational: This one is mostly about a system, process, or policy that contributed to the error .

When searching for the root cause, it is important to ensure people that you aren’t there to assign blame to a person but rather identify the problem so a fix can prevent future issues.

Produce a Variety of Solution Options

So far, you’ve approached the problem as a data scientist, searching for clues to the real issue. Now, it’s important to keep your eyes and ears open, in case you run across a fix suggested by one of those involved in the process failure. Because they are closest to the problem, they will often have an idea of how to fix things. In other cases, they may be too close, and unable to see how the process could change.

The bottom line is to solicit solution ideas from a variety of sources , both close to and far away from the process you’re trying to improve.

You just never know where the top fix might come from!

Fully Evaluate and Select Planned Fix(es)

Evaluating solutions to a defined problem can be tricky since each one will have cost, political, or other factors associated with it. Running each fix through a filter of cost and impact is a vital step toward identifying a solid solution and hopefully settling on the one with the highest impact and low or acceptable cost.

Categorizing each solution in one of these four categories can help teams sift through them:

• High Cost/Low Impact: Implement these last, if at all, since t hey are expensive and won’t move the needle much .
• Low Cost/Low Impact: These are cheap, but you won’t get much impact.
• High Cost/High Impact: These can be used but should be second to the next category.
• Low Cost/High Impact: Getting a solid “bang for your buck” is what these fixes are all about. Start with these first .

Document the Final Solution and What Success Looks Like

Formalize a document that all interested parties (front-line staff, supervisors, leadership, etc.) agree to follow. This will go a long way towards making sure everyone fully understands what the new process looks like, as well as what success will look like .

While it might seem tedious, try to be overly descriptive in the explanation of the solution and how success will be achieved. This is usually necessary to gain full buy-in and commitment to continually following the solution. We often assume certain things that others may not know unless we are more explicit with our communications.

Successfully Sell and Execute the Fix

Arriving at this stage in the process only to forget to consistently apply the solution would be a waste of time, yet many organizations fall down in the execution phase . Part of making sure that doesn’t happen is to communicate the fix and ask for questions multiple times until all parties have a solid grasp on what is now required of them.

One often-overlooked element of this is the politics involved in gaining approval for your solution. Knowing and anticipating objections of those in senior or key leadership positions is central to gaining buy-in before fix implementation.

Rinse and Repeat: Evaluate, Monitor, and Follow Up

Next, doing check-ins with the new process will ensure that the solution is working (or identity if further reforms are necessary) . You’ll also see if the measure of predefined success has been attained (or is making progress in that regard).

Without regularly monitoring the fix, you can only gauge the success or failure of the solution by speculation and hearsay. And without hard data to review, most people will tell their own version of the story.

Collaborative Contingencies, Iteration, and Course Correction

Going into any problem-solving process, we should take note that we will not be done once the solution is implemented (or even if it seems to be working better at the moment). Any part of any process will always be subject to the need for future iterations and course corrections . To think otherwise would be either foolish or naive.

There might need to be slight, moderate, or wholesale changes to the solution previously implemented as new information is gained, new technologies are discovered, etc.

14 Fruitful Resources and Exercises for Your Problem-Solving Journey

Want to test your problem-solving skills?

Take a look at these twenty case study scenario exercises to see how well you can come up with solutions to these problems.

Still have a desire to discover more about solving problems? Check out these 14 articles and books…

The Lean Six Sigma Pocket Toolbook: A Quick Reference Guide to Nearly 100 Tools for Improving Quality and Speed

This book is like a Bible for Lean Six Sigma , all in a pocket-sized package.

The American Society for Quality has a short article on how it’s important to focus on the problem before searching for a solution. Wondering if you are solving the right problems? Check out this Harvard Business Review article. Looking for a fun and easy problem-solving book that was written by a McKinsey consultant? Take a look!

If you want a deeper dive into the seven steps of Creative Problem Solving , see this article. Appreciative Inquiry has been proven effective in organizations ranging from Roadway Express and British Airways to the United Nations and the United States Navy. Review this book to join the positive revolution. The Seattle Police Department has put together nine case studies that you can practice solving . While they are about police work, they have practical application in the sleuthing of work-related problems. Need a resource to delve further into Root Cause Analysis? Look no further than this book for answers to your most vexing questions .

This solid case study illustrates the complexities of solving problems in business. Learn all about the “8Ds” with this concise primer. Need to reduce groupthink in your organization’s problem-solving process ? Check out this article from the Harvard Business Review.

Tim Hurson details his own Productive Thinking Model at great length in this book from the author. This simple five-step process will help you break down the problem, analyze it, prioritize solutions, and sell them internally.

Critical Thinking : A Beginner’s Guide To Critical Thinking, Better Decision Making, And Problem Solving!

Looking for assistance with your problem-solving process.

There’s a lot to take in here, but following some of these methods are sure to improve your problem-solving process. However, if you really want to take problem-solving to the next level, InitiativeOne can come alongside your team to help you solve problems much faster than you ever have before.

There are several parts to this leadership transformation process provided by InitiativeOne, including a personal profile assessment, cognitive learning, group sessions with real-world challenges, personal discovery, and a toolkit to empower leaders to perform at their best.

There are really only two things stopping good teams from being great. One is how they make decisions and two is how they solve problems. Contact us today to grow your team’s leadership performance by making decisions and solving problems more swiftly than ever before!

Originally published at www.initiative-one.com