the problem solving approach involves

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

Overview of the Problem-Solving Mental Process

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

Rachel Goldman, PhD FTOS, is a licensed psychologist, clinical assistant professor, speaker, wellness expert specializing in eating behaviors, stress management, and health behavior change.

• Identify the Problem
• Define the Problem
• Form a Strategy
• Organize Information
• Allocate Resources
• Monitor Progress
• Evaluate the Results

Frequently Asked Questions

Problem-solving is a mental process that involves discovering, analyzing, and solving problems. The ultimate goal of problem-solving is to overcome obstacles and find a solution that best resolves the issue.

The best strategy for solving a problem depends largely on the unique situation. In some cases, people are better off learning everything they can about the issue and then using factual knowledge to come up with a solution. In other instances, creativity and insight are the best options.

It is not necessary to follow problem-solving steps sequentially, It is common to skip steps or even go back through steps multiple times until the desired solution is reached.

In order to correctly solve a problem, it is often important to follow a series of steps. Researchers sometimes refer to this as the problem-solving cycle. While this cycle is portrayed sequentially, people rarely follow a rigid series of steps to find a solution.

The following steps include developing strategies and organizing knowledge.

1. Identifying the Problem

While it may seem like an obvious step, identifying the problem is not always as simple as it sounds. In some cases, people might mistakenly identify the wrong source of a problem, which will make attempts to solve it inefficient or even useless.

Some strategies that you might use to figure out the source of a problem include :

• Asking questions about the problem
• Breaking the problem down into smaller pieces
• Looking at the problem from different perspectives
• Conducting research to figure out what relationships exist between different variables

2. Defining the Problem

After the problem has been identified, it is important to fully define the problem so that it can be solved. You can define a problem by operationally defining each aspect of the problem and setting goals for what aspects of the problem you will address

At this point, you should focus on figuring out which aspects of the problems are facts and which are opinions. State the problem clearly and identify the scope of the solution.

3. Forming a Strategy

After the problem has been identified, it is time to start brainstorming potential solutions. This step usually involves generating as many ideas as possible without judging their quality. Once several possibilities have been generated, they can be evaluated and narrowed down.

The next step is to develop a strategy to solve the problem. The approach used will vary depending upon the situation and the individual's unique preferences. Common problem-solving strategies include heuristics and algorithms.

• Heuristics are mental shortcuts that are often based on solutions that have worked in the past. They can work well if the problem is similar to something you have encountered before and are often the best choice if you need a fast solution.
• Algorithms are step-by-step strategies that are guaranteed to produce a correct result. While this approach is great for accuracy, it can also consume time and resources.

Heuristics are often best used when time is of the essence, while algorithms are a better choice when a decision needs to be as accurate as possible.

4. Organizing Information

Before coming up with a solution, you need to first organize the available information. What do you know about the problem? What do you not know? The more information that is available the better prepared you will be to come up with an accurate solution.

When approaching a problem, it is important to make sure that you have all the data you need. Making a decision without adequate information can lead to biased or inaccurate results.

5. Allocating Resources

Of course, we don't always have unlimited money, time, and other resources to solve a problem. Before you begin to solve a problem, you need to determine how high priority it is.

If it is an important problem, it is probably worth allocating more resources to solving it. If, however, it is a fairly unimportant problem, then you do not want to spend too much of your available resources on coming up with a solution.

At this stage, it is important to consider all of the factors that might affect the problem at hand. This includes looking at the available resources, deadlines that need to be met, and any possible risks involved in each solution. After careful evaluation, a decision can be made about which solution to pursue.

6. Monitoring Progress

After selecting a problem-solving strategy, it is time to put the plan into action and see if it works. This step might involve trying out different solutions to see which one is the most effective.

It is also important to monitor the situation after implementing a solution to ensure that the problem has been solved and that no new problems have arisen as a result of the proposed solution.

Effective problem-solvers tend to monitor their progress as they work towards a solution. If they are not making good progress toward reaching their goal, they will reevaluate their approach or look for new strategies .

7. Evaluating the Results

After a solution has been reached, it is important to evaluate the results to determine if it is the best possible solution to the problem. This evaluation might be immediate, such as checking the results of a math problem to ensure the answer is correct, or it can be delayed, such as evaluating the success of a therapy program after several months of treatment.

Once a problem has been solved, it is important to take some time to reflect on the process that was used and evaluate the results. This will help you to improve your problem-solving skills and become more efficient at solving future problems.

A Word From Verywell​

It is important to remember that there are many different problem-solving processes with different steps, and this is just one example. Problem-solving in real-world situations requires a great deal of resourcefulness, flexibility, resilience, and continuous interaction with the environment.

Get Advice From The Verywell Mind Podcast

Hosted by therapist Amy Morin, LCSW, this episode of The Verywell Mind Podcast shares how you can stop dwelling in a negative mindset.

Follow Now : Apple Podcasts / Spotify / Google Podcasts

You can become a better problem solving by:

• Practicing brainstorming and coming up with multiple potential solutions to problems
• Being open-minded and considering all possible options before making a decision
• Breaking down problems into smaller, more manageable pieces
• Asking for help when needed
• Researching different problem-solving techniques and trying out new ones
• Learning from mistakes and using them as opportunities to grow

It's important to communicate openly and honestly with your partner about what's going on. Try to see things from their perspective as well as your own. Work together to find a resolution that works for both of you. Be willing to compromise and accept that there may not be a perfect solution.

Take breaks if things are getting too heated, and come back to the problem when you feel calm and collected. Don't try to fix every problem on your own—consider asking a therapist or counselor for help and insight.

If you've tried everything and there doesn't seem to be a way to fix the problem, you may have to learn to accept it. This can be difficult, but try to focus on the positive aspects of your life and remember that every situation is temporary. Don't dwell on what's going wrong—instead, think about what's going right. Find support by talking to friends or family. Seek professional help if you're having trouble coping.

Davidson JE, Sternberg RJ, editors.  The Psychology of Problem Solving .  Cambridge University Press; 2003. doi:10.1017/CBO9780511615771

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

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

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

By Status.net Editorial Team on May 7, 2023 — 4 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 skill that allows you to tackle complex situations, adapt to changes, and overcome difficulties with ease.

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.

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

When brainstorming:

• 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.

• Problem Solving Skills: 25 Performance Review Phrases Examples
• How to Resolve Employee Conflict at Work [Steps, Tips, Examples]
• 30 Examples: Self Evaluation Comments for Problem Solving
• Effective Decision Making Process: 7 Steps with Examples
• 174 Performance Feedback Examples (Reliability, Integrity, Problem Solving)
• How to Write Inspiring Core Values? 5 Steps with Examples

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

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

StrategyPunk

Introduction

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

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

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

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

Step 1: Define the Problem

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

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

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

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

Step 2: Disaggregate

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

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

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

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

Step 3: Prioritize

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

There are several ways to prioritize issues, including:

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

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

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

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

Step 4: Workplan

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

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

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

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

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

Step 5: Analysis

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

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

• Root cause analysis
• Pareto analysis
• SWOT analysis

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

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

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

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

Step 6: Synthesize

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

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

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

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

Step 7: Communicate

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

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

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

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

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

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

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

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

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

7-Step Problem-Solving Process PPT Template

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

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

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

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

Please buy me a coffee.

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

7-Step Problem-Solving Process PDF Template

7-step problem-solving process powerpoint template.

SWOT Analysis Volvo (based on Capital Markets Day 24)

Volvo's SWOT analysis shows a strong brand and tech focus but faces challenges like China dependence and competition. Download the free PDF.

The Innovation Playbook: Understanding and Applying the Four Types of Innovation (FREE PPT)

Explore how mastering Product, Process, Business Model, and Management innovations can transform your organization and drive sustainable growth.

SWOT Analysis Kinnevik (based on Capital Markets Day 24)

Discover Kinnevik's strategic position with a SWOT analysis from Capital Markets Day 2024, highlighting key strengths, growth opportunities, and sector insights.

Mastering Your Go-To-Market Strategy: 7 Crucial Steps for Success (Plus Free PPT Template)

Launch your product with confidence. Our step-by-step guide shows you how to build a winning go-to-market strategy, plus grab our free PowerPoint template to get started.

What are the 7 Steps to Problem-Solving? & Its Examples

By Teach Educator

Published on: October 31, 2024

7 Steps to Problem-Solving

7 Steps to Problem-Solving is a systematic process that involves analyzing a situation, generating possible solutions, and implementing the best course of action. While different problem-solving models exist, a common approach often involves the following seven steps:

Define the Problem:

• Clearly articulate and understand the nature of the problem. Define the issue, its scope, and its impact on individuals or the organization.

Gather Information:

• Collect relevant data and information related to the problem. This may involve research, observation, interviews, or any other method to gain a comprehensive understanding.

Generate Possible Solutions:

• Brainstorm and generate a variety of potential solutions to the problem. Encourage creativity and consider different perspectives during this phase.

Evaluate Options:

• Assess the strengths and weaknesses of each potential solution. Consider the feasibility, potential risks, and the likely outcomes associated with each option.

Make a Decision:

• Based on the evaluation, choose the most suitable solution. This decision should align with the goals and values of the individual or organization facing the problem.

Implement the Solution:

• Put the chosen solution into action. Develop an implementation plan, allocate resources, and carry out the necessary steps to address the problem effectively.

Evaluate the Results:

• Assess the outcomes of the implemented solution. Did it solve the problem as intended? What can be learned from the process? Use this information to refine future problem-solving efforts.

It’s important to note that these steps are not always linear and may involve iteration. Problem-solving is often an ongoing process, and feedback from the implementation and evaluation stages may lead to adjustments in the chosen solution or the identification of new issues that need to be addressed.

Problem-Solving Example in Education

• Certainly: Let’s consider a problem-solving example in the context of education.
• Problem: Declining Student Engagement in Mathematics Classes

Background:

A high school has noticed a decline in student engagement and performance in mathematics classes over the past few years. Students seem disinterested, and there is a noticeable decrease in test scores. The traditional teaching methods are not effectively capturing students’ attention, and there’s a need for innovative solutions to rekindle interest in mathematics.

Steps in Problem-Solving

Identify the problem:.

• Clearly define the issue: declining student engagement and performance in mathematics classes.
• Gather data on student performance, attendance, and feedback from teachers and students.

Root Cause Analysis

• Conduct surveys, interviews, and classroom observations to identify the root causes of disengagement.
• Identify potential factors such as teaching methods, curriculum relevance, or lack of real-world applications.

Brainstorm Solutions

• Organize a team of educators, administrators, and even students to brainstorm creative solutions.
• Consider integrating technology, real-world applications, project-based learning, or other interactive teaching methods.

Evaluate and Prioritize Solutions

• Evaluate each solution based on feasibility, cost, and potential impact.
• Prioritize solutions that are likely to address the root causes and have a positive impact on student engagement.

Implement the Chosen Solution

• Develop an action plan for implementing the chosen solution.
• Provide training and resources for teachers to adapt to new teaching methods or technologies.

Monitor and Evaluate

• Continuously monitor the implementation of the solution.
• Collect feedback from teachers and students to assess the effectiveness of the changes.

Adjust as Needed

• Be willing to make adjustments based on ongoing feedback and data analysis.
• Fine-tune the solution to address any unforeseen challenges or issues.

Example Solution

• Introduce a project-based learning approach in mathematics classes, where students work on real-world problems that require mathematical skills.
• Incorporate technology, such as educational apps or interactive simulations, to make learning more engaging.
• Provide professional development for teachers to enhance their skills in implementing these new teaching methods.

Expected Outcomes:

• Increased student engagement and interest in mathematics.
• Improvement in test scores and overall academic performance.
• Positive feedback from both teachers and students.

Final Words

This problem-solving approach in education involves a systematic process of identifying, analyzing, and addressing issues to enhance the learning experience for students.

Related Post

Top 10 schools & colleges in pakistan – latest update.

Top 10 Schools & Colleges in Pakistan  Now here are the top 10 Schools & Colleges in Pakistan. I can provide you with a list of some well-known ...

Top 10 Schools & Colleges in America – Latest Update

Top 10 Schools & Colleges in America According to my knowledge, there are different ways to rank the top schools & colleges in America, depending on the level ...

Resources for Minority Students in Doctoral Programs – Latest

Minority students pursuing doctoral programs Minority students pursuing doctoral programs may encounter unique challenges and barriers during their academic journey. Fortunately, numerous resources and support systems are available ...

What is School Choice? & Its Benefits – Full Guide

What is a School Choice? “What is School Choice” refers to the concept of allowing parents. And students to choose the educational environment that best fits their needs ...

Leave a Comment Cancel reply

Save my name, email, and website in this browser for the next time I comment.

Latest Post

The increasing demand for additional income for teachers—latest, teach educator.

"Teach Educator aims to empower learners and educators alike through its comprehensive services. Dedicated to bridging educational gaps, it offers a range of resources designed to enhance teaching methodologies, provide updated curriculum insights, and foster professional development. With a commitment to accessibility, Teach Educator ensures that educational tools and information are readily available to all, promoting inclusivity in learning.

© Teach Educator 2021 - 2024 | All Rights Reserved

Privacy policy

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

Want to create or adapt books like this? Learn more about how Pressbooks supports open publishing practices.

9 Chapter 9. Problem-Solving

CHAPTER 9: PROBLEM SOLVING  

How do we achieve our goals when the solution is not immediately obvious? What mental blocks are likely to get in our way, and how can we leverage our prior knowledge to solve novel problems?

CHAPTER 9 LICENSE AND ATTRIBUTION

Source: Multiple authors. Memory. In Cognitive Psychology and Cognitive Neuroscience. Wikibooks. Retrieved from https://en.wikibooks.org/wiki/ Cognitive_Psychology_and_Cognitive_Neuroscience

Wikibooks are licensed under the Creative Commons Attribution-ShareAlike License.

Cognitive Psychology and Cognitive Neuroscience is licensed under the GNU Free Documentation License.

Condensed from original version. American spellings used. Content added or changed to reflect American perspective and references. Context and transitions added throughout. Substantially edited, adapted, and (in some parts) rewritten for clarity and course relevance.

Cover photo by Pixabay on Pexels.

Knut is sitting at his desk, staring at a blank paper in front of him, and nervously playing with a pen in his right hand. Just a few hours left to hand in his essay and he has not written a word. All of a sudden he smashes his fist on the table and cries out: “I need a plan!”

Knut is confronted with something every one of us encounters in his daily life: he has a problem, and he does not know how to solve it. But what exactly is a problem? Are there strategies to solve problems? These are just a few of the questions we want to answer in this chapter.

We begin our chapter by giving a short description of what psychologists regard as a problem. Afterward we will discuss different approaches towards problem solving, starting with gestalt psychologists and ending with modern search strategies connected to artificial intelligence. In addition we will also consider how experts solve problems.

The most basic definition of a problem is any given situation that differs from a desired goal. This definition is very useful for discussing problem solving in terms of evolutionary adaptation, as it allows us to understand every aspect of (human or animal) life as a problem. This includes issues like finding food in harsh winters, remembering where you left your provisions, making decisions about which way to go, learning, repeating and varying all kinds of complex movements, and so on. Though all of these problems were of crucial importance during the human evolutionary process, they are by no means solved exclusively by humans. We find an amazing variety of different solutions for these problems in nature (just consider, for example, the way a bat hunts its prey compared to a spider). We will mainly focus on problems that are not solved by animals or evolution; we will instead focus on abstract problems, such as playing chess. Furthermore, we will not consider problems that have an obvious solution. For example, imagine Knut decides to take a sip of coffee from the mug next to his right hand. He does not even have to think about how to do this. This is not because the situation itself is trivial (a robot capable of recognizing the mug, deciding whether it is full, then grabbing it and moving it to Knut’s mouth would be a highly complex machine) but because in the context of all possible situations it is so trivial that it no longer is a problem our consciousness needs to be bothered with. The problems we will discuss in the following all need some conscious effort, though some seem to be solved without us being able to say how exactly we got to the solution. We will often find that the strategies we use to solve these problems are applicable to more basic problems, too.

Non-trivial, abstract problems can be divided into two groups: well-defined problems and ill- defined problems.

WELL-DEFINED PROBLEMS

For many abstract problems, it is possible to find an algorithmic solution. We call problems well-defined if they can be properly formalized, which involves the following properties:

•        The problem has a clearly defined given state. This might be the line-up of a chess game, a given formula you have to solve, or the set-up of the towers of Hanoi game (which we will discuss later).

•        There is a finite set of operators, that is, rules you may apply to the given state. For the chess game, e.g., these would be the rules that tell you which piece you may move to which position.

•        Finally, the problem has a clear goal state: The equations is resolved to x, all discs are moved to the right stack, or the other player is in checkmate.

A problem that fulfils these requirements can be implemented algorithmically. Therefore many well-defined problems can be very effectively solved by computers, like playing chess.

ILL-DEFINED PROBLEMS

Though many problems can be properly formalized, there are still others where this is not the case. Good examples for this are all kinds of tasks that involve creativity, and, generally speaking, all problems for which it is not possible to clearly define a given state and a goal state. Formalizing a problem such as “Please paint a beautiful picture” may be impossible.

Still, this is a problem most people would be able to approach in one way or the other, even if the result may be totally different from person to person. And while Knut might judge that picture X is gorgeous, you might completely disagree.

The line between well-defined and ill-defined problems is not always neat: ill-defined problems often involve sub-problems that can be perfectly well-defined. On the other hand, many everyday problems that seem to be completely well-defined involve — when examined in detail — a great amount of creativity and ambiguity. Consider Knut’s fairly ill-defined task of writing an essay: he will not be able to complete this task without first understanding the text he has to write about. This step is the first subgoal Knut has to solve. In this example, an ill-defined problem involves a well-defined sub-problem

RESTRUCTURING: THE GESTALTIST APPROACH

One dominant approach to problem solving originated from Gestalt psychologists in the 1920s. Their understanding of problem solving emphasizes behavior in situations requiring relatively novel means of attaining goals and suggests that problem solving involves a process called restructuring. With a Gestalt approach, two main questions have to be considered to understand the process of problem solving: 1) How is a problem represented in a person’s mind?, and 2) How does solving this problem involve a reorganization or restructuring of this representation?

HOW IS A PROBLEM REPRESENTED IN THE MIND?

In current research internal and external representations are distinguished: an internal representation is one held in memory, and which has to be retrieved by cognitive processes, while an external representation exists in the environment, such like physical objects or symbols whose information can be picked up and processed by the perceptual system.

Generally speaking, problem representations are models of the situation as experienced by the solver. Representing a problem means to analyze it and split it into separate components, including objects, predicates, state space, operators, and selection criteria.

The efficiency of problem solving depends on the underlying representations in a person’s mind, which usually also involves personal aspects. Re-analyzing the problem along different dimensions, or changing from one representation to another, can result in arriving at a new understanding of a problem. This is called restructuring . The following example illustrates this:

Two boys of different ages are playing badminton. The older one is a more skilled player, and therefore the outcome of matches between the two becomes predictable. After repeated defeats the younger boy finally loses interest in playing. The older boy now faces a problem, namely that he has no one to play with anymore. The usual options, according to M. Wertheimer (1945/82), range from “offering candy” and “playing a different game” to “not playing at full ability” and “shaming the younger boy into playing.” All of these strategies aim at making the younger boy stay.

The older boy instead comes up with a different solution: He proposes that they should try to keep the birdie in play as long as possible. Thus, they change from a game of competition to one of cooperation. The proposal is happily accepted, and the game is on again. The key in this story is that the older boy restructured the problem, having found that his attitude toward the game made it difficult to keep the younger boy playing. With the new type of game the problem is solved: the older boy is not bored, and the younger boy is not frustrated. In some cases, new representations can make a problem more difficult or much easier to solve. In the latter case insight – the sudden realization of a problem’s solution – may be the key to finding a solution.

There are two very different ways of approaching a goal-oriented situation . In one case an organism readily reproduces the response to the given problem from past experience. This is called reproductive thinking .

The second way requires something new and di fferent to achieve the goal—prior learning is of little help here. Such productive thinking is sometimes argued to involve insight . Gestalt psychologists state that insight problems are a separate category of problems in their own right.

Tasks that might involve insight usually have certain features: they require something new and non-obvious to be done, and in most cases they are difficult enough to predict that the initial solution attempt will be unsuccessful. When you solve a problem of this kind you often have a so called “aha” experience: the solution pops into mind all of a sudden. In one moment you have no idea how to answer the problem, and you feel you are not making any progress trying out different ideas, but in the next moment the problem is solved.

For readers who would like to experience such an effect, here is an example of an insight problem: Knut is given four pieces of a chain; each made up of three links. The task is to link it all up to a closed loop. To open a link costs 2 cents, and to close a link costs 3 cents. Knut has 15 cents to spend. What should Knut do?

If you want to know the correct solution, turn to the next page.

To show that solving insight problems involves restructuring , psychologists have created a number of problems that are more difficult to solve for participants with previous experiences, since it is harder for them to change the representation of the given situation.

For non-insight problems the opposite is the case. Solving arithmetical problems, for instance, requires schemas, through which one can get to the solution step by step.

Sometimes, previous experience or familiarity can even make problem solving more difficult. This is the case whenever habitual directions get in the way of finding new directions – an effect called fixation .

FUNCTIONAL FIXEDNESS

Functional fixedness concerns the solution of object use problems . The basic idea is that when the usual function an object is emphasized, it will be far more difficult for a person to use that object in a novel manner. An example for this effect is the candle problem : Imagine you are given a box of matches, some candles and tacks. On the wall of the room there is a cork-board. Your task is to fix the candle to the cork-board in such a way that no wax will drop on the floor when the candle is lit. Got an idea?

Here’s a clue: when people are confronted with a problem and given certain objects to solve it, it is difficult for them to figure out that they could use the objects in a different way. In this example, the box has to be recognized as a support rather than as a container— tack the matchbox to the wall, and place the candle upright in the box. The box will catch the falling wax.

A further example is the two-string problem : Knut is left in a room with a pair of pliers and given the task to bind two strings together that are hanging from the ceiling. The problem he faces is that he can never reach both strings at a time because they are just too far away from each other. What can Knut do?

Solution: Knut has to recognize he can use the pliers in a novel function: as weight for a pendulum. He can tie them to one of the strings, push it away, hold the other string and wait for the first one to swing toward him.

MENTAL FIXEDNESS

Functional fixedness as involved in the examples above illustrates a mental set: a person’s tendency to respond to a given task in a manner based on past experience. Because Knut maps an object to a particular function he has difficulty varying the way of use (i.e., pliers as pendulum’s weight).

One approach to studying fixation was to study wrong-answer verbal insight problems . In these probems, people tend to give an incorrect answer when failing to solve a problem rather than to give no answer at all.

A typical example: People are told that on a lake the area covered by water lilies doubles every 24 hours and that it takes 60 days to cover the whole lake. Then they are asked how many days it takes to cover half the lake. The typical response is “30 days” (whereas 59 days is correct).

These wrong solutions are due to an inaccurate interpretation , or representation , of the problem. This can happen because of sloppiness (a quick shallow reading of the problem and/or weak monitoring of their efforts made to come to a solution). In this case error feedback should help people to reconsider the problem features, note the inadequacy of their first answer, and find the correct solution. If, however, people are truly fixated on their incorrect representation, being told the answer is wrong does not help. In a study by P.I. Dallop and

R.L. Dominowski in 1992 these two possibilities were investigated. In approximately one third of the cases error feedback led to right answers, so only approximately one third of the wrong answers were due to inadequate monitoring.

Another approach is the study of examples with and without a preceding analogous task. In cases such like the water-jug task, analogous thinking indeed leads to a correct solution, but to take a different way might make the case much simpler:

Imagine Knut again, this time he is given three jugs with different capacities and is asked to measure the required amount of water. He is not allowed to use anything except the jugs and as much water as he likes. In the first case the sizes are: 127 cups, 21 cups and 3 cups. His goal is to measure 100 cups of water.

In the second case Knut is asked to measure 18 cups from jugs of 39, 15 and 3 cups capacity.

Participants who are given the 100 cup task first choose a complicated way to solve the second task. Participants who did not know about that complex task solved the 18 cup case by just adding three cups to 15.

SOLVING PROBLEMS BY ANALOGY

One special kind of restructuring is analogical problem solving. Here, to find a solution to one problem (i.e., the target problem) an analogous solution to another problem (i.e., the base problem) is presented.

An example for this kind of strategy is the radiation problem posed by K. Duncker in 1945:

As a doctor you have to treat a patient with a malignant, inoperable tumor, buried deep inside the body. There exists a special kind of ray which is harmless at a low intensity, but at sufficiently high intensity is able to destroy the tumor. At such high intensity, however, the ray will also destroy the healthy tissue it passes through on the way to the tumor. What can be done to destroy the tumor while preserving the healthy tissue?

When this question was asked to participants in an experiment, most of them couldn’t come up with the appropriate answer to the problem. Then they were told a story that went something like this:

A general wanted to capture his enemy’s fortress. He gathered a large army to launch a full- scale direct attack, but then learned that all the roads leading directly towards the fortress were blocked by landmines. These roadblocks were designed in such a way that it was possible for small groups of the fortress-owner’s men to pass over them safely, but a large group of men would set them off. The general devised the following plan: He divided his troops into several smaller groups and ordered each of them to march down a different road, timed in such a way that the entire army would reunite exactly when reaching the fortress and could hit with full strength.

Here, the story about the general is the source problem, and the radiation problem is the target problem. The fortress is analogous to the tumor and the big army corresponds to the highly intensive ray. Likewise, a small group of soldiers represents a ray at low intensity. The s olution to the problem is to split the ray up, as the general did with his army, and send the now harmless rays towards the tumor from different angles in such a way that they all meet when reaching it. No healthy tissue is damaged but the tumor itself gets destroyed by the ray at its full intensity.

M. Gick and K. Holyoak presented Duncker’s radiation problem to a group of participants in 1980 and 1983. 10 percent of participants were able to solve the problem right away, but 30 percent could solve it when they read the story of the general before. After being given an additional hint — to use the story as help — 75 percent of them solved the problem.

Following these results, Gick and Holyoak concluded that analogical problem solving consists of three steps:

1.  Recognizing that an analogical connection exists between the source and the base problem.

2. Mapping corresponding parts of the two problems onto each other (fortress ® tumour, army ® ray, etc.)

3. Applying the mapping to generate a parallel solution to the target problem (using little groups of soldiers approaching from different directions ® sending several weaker rays from different directions)

Next, Gick and Holyoak started looking for factors that could help the recognizing and mapping processes.

The abstract concept that links the target problem with the base problem is called the problem schema. Gick and Holyoak facilitated the activation of a schema with their participants by giving them two stories and asking them to compare and summarize them. This activation of problem schemas is called “schema induction“.

The experimenters had participants read stories that presented problems and their solutions. One story was the above story about the general, and other stories required the same problem schema (i.e., if a heavy force coming from one direction is not suitable, use multiple smaller forces that simultaneously converge on the target). The experimenters manipulated how many of these stories the participants read before the participants were asked to solve the radiation problem. The experiment showed that in order to solve the target problem, reading two stories with analogical problems is more helpful than reading only one story. This evidence suggests that schema induction can be achieved by exposing people to multiple problems with the same problem schema.

HOW DO EXPERTS SOLVE PROBLEMS?

An expert is someone who devotes large amounts of their time and energy to one specific field of interest in which they, subsequently, reach a certain level of mastery. It should not be a surprise that experts tend to be better at solving problems in their field than novices (i.e., people who are beginners or not as well-trained in a field as experts) are. Experts are faster at coming up with solutions and have a higher rate of correct solutions. But what is the difference between the way experts and non-experts solve problems? Research on the nature of expertise has come up with the following conclusions:

1.       Experts know more about their field,

2.      their knowledge is organized differently, and

3.      they spend more time analyzing the problem.

Expertise is domain specific— when it comes to problems that are outside the experts’ domain of expertise, their performance often does not differ from that of novices.

Knowledge: An experiment by Chase and Simon (1973) dealt with the question of how well experts and novices are able to reproduce positions of chess pieces on chess boards after a brief presentation. The results showed that experts were far better at reproducing actual game positions, but that their performance was comparable with that of novices when the chess pieces were arranged randomly on the board. Chase and Simon concluded that the superior performance on actual game positions was due to the ability to recognize familiar patterns: A chess expert has up to 50,000 patterns stored in his memory. In comparison, a good player might know about 1,000 patterns by heart and a novice only few to none at all. This very detailed knowledge is of crucial help when an expert is confronted with a new problem in his field. Still, it is not only the amount of knowledge that makes an expert more successful. Experts also organize their knowledge differently from novices.

Organization: In 1981 M. Chi and her co-workers took a set of 24 physics problems and presented them to a group of physics professors as well as to a group of students with only one semester of physics. The task was to group the problems based on their similarities. The students tended to group the problems based on their surface structure (i.e., similarities of objects used in the problem, such as sketches illustrating the problem), whereas the professors used their deep structure (i.e., the general physical principles that underlie the problems) as criteria. By recognizing the actual structure of a problem experts are able to connect the given task to the relevant knowledge they already have (e.g., another problem they solved earlier which required the same strategy).

Analysis: Experts often spend more time analyzing a problem before actually trying to solve it. This way of approaching a problem may often result in what appears to be a slow start, but in the long run this strategy is much more effective. A novice, on the other hand, might start working on the problem right away, but often reach dead ends as they chose a wrong path in the very beginning.

_________________________________________________________________________________________________________________________________________________________

Chase, W. G., & Simon, H. A. (1973). Perception in chess. Cognitive psychology, 4(1), 55-81.

Chi, M. T., Feltovich, P. J., & Glaser, R. (1981). Categorization and representation of physics problems by experts and novices. Cognitive science, 5(2), 121-152.

Duncker, K., & Lees, L. S. (1945). On problem-solving. Psychological monographs, 58(5).

Gick, M. L., & Holyoak, K. J. (1980). Analogical problem solving. Cognitive psychology, 12(3), 306-355. Gick, M. L., & Holyoak, K. J. (1983). Schema induction and analogical transfer. Cognitive psychology, 15(1), 1-38.

Goldstein, E.B. (2005). Cogntive Psychology. Connecting Mind, Research, and Everyday Experience. Belmont: Thomson Wadsworth.

R.L. Dominowski and P. Dallob, Insight and Problem Solving. In The Nature of Insight, R.J. Sternberg & J.E. Davidson (Eds). MIT Press: USA, pp.33-62 (1995).

Wertheimer, M., (1945). Productive thinking. New York: Harper.

ESSENTIALS OF COGNITIVE PSYCHOLOGY Copyright © 2023 by Christopher Klein is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License , except where otherwise noted.

Share This Book