what is the definition problem solving

• Onsite training

3,000,000+ delegates

15,000+ clients

1,000+ locations

• KnowledgePass
• Log a ticket

01344203999 Available 24/7

What is Problem Solving? A Comprehensive Guide

In this blog, we will explore "What is Problem Solving?" In detail. From defining the nature of Problem Solving to understanding the key process in resolving issues, this blog covers it all. So, wait no more; let’s go deeper into this fundamental concept.

Exclusive 40% OFF

Training Outcomes Within Your Budget!

We ensure quality, budget-alignment, and timely delivery by our expert instructors.

Share this Resource

• Introduction to Management
• Personal & Organisational Development
• Workforce Resource Planning Training
• Supervisor Training
• Introduction to Managing Budgets

Table of contents  

1) What is Problem Solving definition?  

2) The process of Problem Solving  

3) Key skills for effective Problem Solving  

4) Strategies for enhancing Problem Solving abilities  

5) Problem Solving tools and techniques  

6) Conclusion       

What is Problem Solving definition?  

The process of Problem Solving  

Understanding the problem   

The first step in Problem Solving is gaining a clear understanding of the issue at hand. Take the time to thoroughly analyse the problem and gather relevant information. Ask yourself questions like:  

1) What is the nature of the problem?  

2) What are the factors contributing to the problem?  

3) What are the desired outcomes?  

4) Are there any constraints or limitations to consider?  

By gaining a comprehensive understanding of the problem, you lay a solid foundation for finding an effective solution.  

Generating possible solutions   

Once you have a clear grasp of the problem, it's time to brainstorm potential solutions. Encourage creativity and think outside the box. Consider all possible options without judgment or criticism. The goal at this stage is to generate a variety of ideas and alternatives.  

Evaluating and selecting the best solution   

After generating a list of possible solutions, it's important to evaluate each option based on its feasibility, effectiveness, and alignment with the desired outcome. Consider the advantages and disadvantages of each and every solution. Assess its practicality and the resources required for implementation.  

Additionally, take into account the potential risks and benefits associated with each solution. Consider any potential consequences or impacts on other aspects. Based on this evaluation, select the solution that appears most viable and promising.  

Implementing the solution   

Once you have chosen the best solution, it's time to put it into action. Develop a detailed plan outlining the necessary steps and allocate the required resources. Determine responsibilities and deadlines to ensure a smooth implementation process.  

During implementation, monitor progress and make any necessary adjustments or adaptations. Stay proactive and address any challenges or obstacles that may arise along the way. Effective communication and collaboration with others involved in the process can greatly contribute to successful implementation.  

Assessing the results   

After implementing the solution, it's essential to assess the results. Evaluate whether the problem has been properly resolved or if further adjustments are required. Analyse the outcomes and compare them against the desired goals and expectations.  

Consider whether the chosen solution has brought about the intended benefits and if any unexpected consequences have emerged. Reflect on the overall effectiveness of the Problem Solving process and identify any lessons learned for future reference.  

Remember, Problem Solving is an iterative process, and it's not uncommon to revisit and refine solutions based on ongoing evaluation and feedback. Embrace a continuous improvement mindset and be open to seeking alternative approaches if necessary.  

By following this Problem Solving process, you can approach challenges systematically and increase your chances of finding effective solutions. Remember that practice and experience play a vital role in honing your skills. 

Master the art of solving problems and become a catalyst for innovation and success with our Problem Solving Training – sign up now!  

Key skills for effective Problem Solving   

What one must do to become an effective problem solver is to develop key skills that enhance your Problem Solving abilities. The skills give you the ability to tackle challenges with a strategic mind and find the needed solutions. Below is a dive into the most important of them:

Critical thinking

Critical thinking is a skill that includes the objective analysis of information, considering different viewpoints, and being able to arrive at a sensible judgment. This helps you to assess problems with the right accuracy in judgment and also find suitable solutions. 

It means that creativity is the ability of a person to think outside the box and come up with innovative solutions. It includes pressing the mind toward new possibilities and viewing the problem in different ways.

Analytical skills

In this ability, there is the aspect of breaking down a problem into subunits that helps in identifying the patterns, relationships, and causes within the problem. 

Decision-making

Sound skills in decision making call for the assessment of the pros and cons of all solutions provided and thus choosing the best alternative. Risks must always be considered with the benefits any alternative might bring.

Strategies for enhancing Problem Solving abilities  

Practice critical thinking

Engage yourself in activities which require critical thinking, including solving puzzles, complex discussion, challenging all assumptions. This will increase your ability to enhance sharpening of your analytical skills and let you think critically at a time when problems are in your way. 

Seek feedback and learn from experience

Seek responses from your mentors, course peers, and Problem Solving experts. From the successes and failures, reflect on the reasons for the occurrences over previous experiences and point out what could be improved. Treat the opportunity of Problem Solving as one of the chances that shall be given to you to grow and develop each time you make it through a problem. 

Embrace challenges

You can redesign your problematic issues and take every challenge coming across as an opportunity for growth. Hence, it paves the way for the ability of resilience and strengthens your Problem Solving abilities. 

Collaborate with others 

In Problem Solving, collaboration is embraced by pooling different perspectives and ideas. Work with others in activities that involve groups to discuss issues and seek input from others, listening actively to various viewpoints. Working collaboratively with others helps expand your knowledge of various ways of Problem Solving and encourages innovation.

Think outside the box 

Encourage creative thinking by exploring unconventional ideas and solutions. Challenge every assumption and all its related alternatives. Shift to this kind of mindset, and it can drive innovative Problem Solving strategies, letting you uncover newer ways to solve age-old complex problems.

Problem Solving tools and techniques  

When faced with complex problems, utilising specific tools and techniques can help facilitate the solving process and lead to more effective solutions. Here are some commonly used Problem Solving tools and techniques:  

Root cause analysis   

Root cause analysis is a methodology used to detect the underlying causes of a problem. It involves investigating the problem's symptoms and tracing them back to their fundamental causes. By addressing the root causes, Problem Solvers can prevent the issue from recurring.  

Strengths, Weaknesses, Opportunities, Threats (SWOT) analysis   

SWOT analysis is a planning tool that strategically helps measure the weaknesses and internal strengths of a situation. Moreover, it can find external opportunities and threats. By assessing these factors, Problem Solvers can gain insights into the current state and make informed decisions about potential solutions.  

Fishbone diagrams   

Fishbone diagrams, also known as cause-and-effect diagrams or Ishikawa Diagrams, visually represent the possible causes contributing to a problem. By organising causes into categories (such as people, process, equipment, and environment), Problem Solvers can systematically analyse the problem's potential sources.  

Decision matrices   

Decision matrices are used to evaluate and compare different options based on multiple criteria. This tool helps Problem Solvers weigh the importance of various factors and objectively assess each alternative, leading to an informed decision.  

Six Thinking Hats   

Six Thinking Hats is a technique initially developed by Edward de Bono that encourages parallel thinking by exploring different perspectives. Each "hat" represents a different thinking approach (e.g., logical, creative, emotional), allowing Problem Solvers to consider diverse viewpoints and generate innovative solutions.  

These are just a few examples of Problem Solving tools and techniques. Depending on the nature of the problem, other methods, such as brainstorming, mind mapping, flowcharts, or Pareto analysis, can also be applied. Choosing the appropriate tool or technique depends on the specific problem and the desired outcome. 

Navigate conflicts with finesse and foster collaboration with our transformative Conflict Management Training – sign up today!  

Conclusion  

We hope you read and understand everything about What is Problem Solving? Developing effective skills is crucial for overcoming challenges, making informed decisions, and achieving success. By embracing problems as opportunities and applying strategic approaches, individuals can become proficient Problem Solvers in various domains of life. 

Unlock your management potential and elevate your skills to new heights with our cutting-edge Management Training Courses – sign up now!  

Frequently Asked Questions

There are two major types of Problem Solving: Reflective and Creative. Regardless of the type, it focuses on understanding the issues, considering all factors and finding a solution.

Problem Solving in the workplace refers to an individual’s ability to manage difficult situations and find solutions to complex business issues.

The Knowledge Academy takes global learning to new heights, offering over 30,000 online courses across 490+ locations in 220 countries. This expansive reach ensures accessibility and convenience for learners worldwide.

Alongside our diverse Online Course Catalogue, encompassing 17 major categories, we go the extra mile by providing a plethora of free educational Online Resources like News updates, Blogs , videos, webinars, and interview questions. Tailoring learning experiences further, professionals can maximise value with customisable Course Bundles of TKA .  

The Knowledge Academy’s Knowledge Pass , a prepaid voucher, adds another layer of flexibility, allowing course bookings over a 12-month period. Join us on a journey where education knows no bounds.

The Knowledge Academy offers various Management Courses including Business Process Improvement Training, Performance Management Training and Introduction to Managing People. These courses cater to different skill levels, providing comprehensive insights into Resource Planning Template .

Our Business Skills Blogs cover a range of topics related to musical instruments, offering valuable resources, best practices, and industry insights. Whether you are a beginner or looking to advance your skills as a Music Producer, The Knowledge Academy's diverse courses and informative blogs have you covered.  

Upcoming Business Skills Resources Batches & Dates

Fri 14th Jun 2024

Fri 23rd Aug 2024

Fri 11th Oct 2024

Fri 13th Dec 2024

Get A Quote

WHO WILL BE FUNDING THE COURSE?

My employer

By submitting your details you agree to be contacted in order to respond to your enquiry

• Business Analysis
• Lean Six Sigma Certification

Share this course

Our biggest spring sale.

We cannot process your enquiry without contacting you, please tick to confirm your consent to us for contacting you about your enquiry.

By submitting your details you agree to be contacted in order to respond to your enquiry.

We may not have the course you’re looking for. If you enquire or give us a call on 01344203999 and speak to our training experts, we may still be able to help with your training requirements.

Or select from our popular topics

• ITIL® Certification
• Scrum Certification
• Change Management Certification
• Business Analysis Courses
• Microsoft Azure Certification
• Microsoft Excel Courses
• Microsoft Project
• Explore more courses

Press esc to close

Fill out your  contact details  below and our training experts will be in touch.

Fill out your   contact details   below

Thank you for your enquiry!

One of our training experts will be in touch shortly to go over your training requirements.

Back to Course Information

Fill out your contact details below so we can get in touch with you regarding your training requirements.

* WHO WILL BE FUNDING THE COURSE?

Preferred Contact Method

No preference

Back to course information

Fill out your  training details  below

Fill out your training details below so we have a better idea of what your training requirements are.

HOW MANY DELEGATES NEED TRAINING?

HOW DO YOU WANT THE COURSE DELIVERED?

Online Instructor-led

Online Self-paced

WHEN WOULD YOU LIKE TO TAKE THIS COURSE?

Next 2 - 4 months

WHAT IS YOUR REASON FOR ENQUIRING?

Looking for some information

Looking for a discount

I want to book but have questions

One of our training experts will be in touch shortly to go overy your training requirements.

Your privacy & cookies!

Like many websites we use cookies. We care about your data and experience, so to give you the best possible experience using our site, we store a very limited amount of your data. Continuing to use this site or clicking “Accept & close” means that you agree to our use of cookies. Learn more about our privacy policy and cookie policy cookie policy .

We use cookies that are essential for our site to work. Please visit our cookie policy for more information. To accept all cookies click 'Accept & close'.

• To save this word, you'll need to log in. Log In

problem-solving

Definition of problem-solving

Examples of problem-solving in a sentence.

These examples are programmatically compiled from various online sources to illustrate current usage of the word 'problem-solving.' Any opinions expressed in the examples do not represent those of Merriam-Webster or its editors. Send us feedback about these examples.

Dictionary Entries Near problem-solving

Cite this entry.

“Problem-solving.” Merriam-Webster.com Dictionary , Merriam-Webster, https://www.merriam-webster.com/dictionary/problem-solving. Accessed 27 May. 2024.

Subscribe to America's largest dictionary and get thousands more definitions and advanced search—ad free!

Can you solve 4 words at once?

Word of the day.

See Definitions and Examples »

Get Word of the Day daily email!

Popular in Grammar & Usage

More commonly misspelled words, commonly misspelled words, how to use em dashes (—), en dashes (–) , and hyphens (-), absent letters that are heard anyway, how to use accents and diacritical marks, popular in wordplay, the words of the week - may 24, flower etymologies for your spring garden, 9 superb owl words, 'gaslighting,' 'woke,' 'democracy,' and other top lookups, 10 words for lesser-known games and sports, games & quizzes.

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)

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

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

What Is Problem Solving? How Software Engineers Approach Complex Challenges

From debugging an existing system to designing an entirely new software application, a day in the life of a software engineer is filled with various challenges and complexities. The one skill that glues these disparate tasks together and makes them manageable? Problem solving . 

Throughout this blog post, we’ll explore why problem-solving skills are so critical for software engineers, delve into the techniques they use to address complex challenges, and discuss how hiring managers can identify these skills during the hiring process. 

What Is Problem Solving?

But what exactly is problem solving in the context of software engineering? How does it work, and why is it so important?

Problem solving, in the simplest terms, is the process of identifying a problem, analyzing it, and finding the most effective solution to overcome it. For software engineers, this process is deeply embedded in their daily workflow. It could be something as simple as figuring out why a piece of code isn’t working as expected, or something as complex as designing the architecture for a new software system. 

In a world where technology is evolving at a blistering pace, the complexity and volume of problems that software engineers face are also growing. As such, the ability to tackle these issues head-on and find innovative solutions is not only a handy skill — it’s a necessity. 

The Importance of Problem-Solving Skills for Software Engineers

Problem-solving isn’t just another ability that software engineers pull out of their toolkits when they encounter a bug or a system failure. It’s a constant, ongoing process that’s intrinsic to every aspect of their work. Let’s break down why this skill is so critical.

Driving Development Forward

Without problem solving, software development would hit a standstill. Every new feature, every optimization, and every bug fix is a problem that needs solving. Whether it’s a performance issue that needs diagnosing or a user interface that needs improving, the capacity to tackle and solve these problems is what keeps the wheels of development turning.

It’s estimated that 60% of software development lifecycle costs are related to maintenance tasks, including debugging and problem solving. This highlights how pivotal this skill is to the everyday functioning and advancement of software systems.

Innovation and Optimization

The importance of problem solving isn’t confined to reactive scenarios; it also plays a major role in proactive, innovative initiatives . Software engineers often need to think outside the box to come up with creative solutions, whether it’s optimizing an algorithm to run faster or designing a new feature to meet customer needs. These are all forms of problem solving.

Consider the development of the modern smartphone. It wasn’t born out of a pre-existing issue but was a solution to a problem people didn’t realize they had — a device that combined communication, entertainment, and productivity into one handheld tool.

Increasing Efficiency and Productivity

Good problem-solving skills can save a lot of time and resources. Effective problem-solvers are adept at dissecting an issue to understand its root cause, thus reducing the time spent on trial and error. This efficiency means projects move faster, releases happen sooner, and businesses stay ahead of their competition.

Improving Software Quality

Problem solving also plays a significant role in enhancing the quality of the end product. By tackling the root causes of bugs and system failures, software engineers can deliver reliable, high-performing software. This is critical because, according to the Consortium for Information and Software Quality, poor quality software in the U.S. in 2022 cost at least $2.41 trillion in operational issues, wasted developer time, and other related problems.

Problem-Solving Techniques in Software Engineering

So how do software engineers go about tackling these complex challenges? Let’s explore some of the key problem-solving techniques, theories, and processes they commonly use.

Decomposition

Breaking down a problem into smaller, manageable parts is one of the first steps in the problem-solving process. It’s like dealing with a complicated puzzle. You don’t try to solve it all at once. Instead, you separate the pieces, group them based on similarities, and then start working on the smaller sets. This method allows software engineers to handle complex issues without being overwhelmed and makes it easier to identify where things might be going wrong.

Abstraction

In the realm of software engineering, abstraction means focusing on the necessary information only and ignoring irrelevant details. It is a way of simplifying complex systems to make them easier to understand and manage. For instance, a software engineer might ignore the details of how a database works to focus on the information it holds and how to retrieve or modify that information.

Algorithmic Thinking

At its core, software engineering is about creating algorithms — step-by-step procedures to solve a problem or accomplish a goal. Algorithmic thinking involves conceiving and expressing these procedures clearly and accurately and viewing every problem through an algorithmic lens. A well-designed algorithm not only solves the problem at hand but also does so efficiently, saving computational resources.

Parallel Thinking

Parallel thinking is a structured process where team members think in the same direction at the same time, allowing for more organized discussion and collaboration. It’s an approach popularized by Edward de Bono with the “ Six Thinking Hats ” technique, where each “hat” represents a different style of thinking.

In the context of software engineering, parallel thinking can be highly effective for problem solving. For instance, when dealing with a complex issue, the team can use the “White Hat” to focus solely on the data and facts about the problem, then the “Black Hat” to consider potential problems with a proposed solution, and so on. This structured approach can lead to more comprehensive analysis and more effective solutions, and it ensures that everyone’s perspectives are considered.

This is the process of identifying and fixing errors in code . Debugging involves carefully reviewing the code, reproducing and analyzing the error, and then making necessary modifications to rectify the problem. It’s a key part of maintaining and improving software quality.

Testing and Validation

Testing is an essential part of problem solving in software engineering. Engineers use a variety of tests to verify that their code works as expected and to uncover any potential issues. These range from unit tests that check individual components of the code to integration tests that ensure the pieces work well together. Validation, on the other hand, ensures that the solution not only works but also fulfills the intended requirements and objectives.

Explore verified tech roles & skills.

The definitive directory of tech roles, backed by machine learning and skills intelligence.

Explore all roles

Evaluating Problem-Solving Skills

We’ve examined the importance of problem-solving in the work of a software engineer and explored various techniques software engineers employ to approach complex challenges. Now, let’s delve into how hiring teams can identify and evaluate problem-solving skills during the hiring process.

Recognizing Problem-Solving Skills in Candidates

How can you tell if a candidate is a good problem solver? Look for these indicators:

• Previous Experience: A history of dealing with complex, challenging projects is often a good sign. Ask the candidate to discuss a difficult problem they faced in a previous role and how they solved it.
• Problem-Solving Questions: During interviews, pose hypothetical scenarios or present real problems your company has faced. Ask candidates to explain how they would tackle these issues. You’re not just looking for a correct solution but the thought process that led them there.
• Technical Tests: Coding challenges and other technical tests can provide insight into a candidate’s problem-solving abilities. Consider leveraging a platform for assessing these skills in a realistic, job-related context.

Assessing Problem-Solving Skills

Once you’ve identified potential problem solvers, here are a few ways you can assess their skills:

• Solution Effectiveness: Did the candidate solve the problem? How efficient and effective is their solution?
• Approach and Process: Go beyond whether or not they solved the problem and examine how they arrived at their solution. Did they break the problem down into manageable parts? Did they consider different perspectives and possibilities?
• Communication: A good problem solver can explain their thought process clearly. Can the candidate effectively communicate how they arrived at their solution and why they chose it?
• Adaptability: Problem-solving often involves a degree of trial and error. How does the candidate handle roadblocks? Do they adapt their approach based on new information or feedback?

Hiring managers play a crucial role in identifying and fostering problem-solving skills within their teams. By focusing on these abilities during the hiring process, companies can build teams that are more capable, innovative, and resilient.

Key Takeaways

As you can see, problem solving plays a pivotal role in software engineering. Far from being an occasional requirement, it is the lifeblood that drives development forward, catalyzes innovation, and delivers of quality software. 

By leveraging problem-solving techniques, software engineers employ a powerful suite of strategies to overcome complex challenges. But mastering these techniques isn’t simple feat. It requires a learning mindset, regular practice, collaboration, reflective thinking, resilience, and a commitment to staying updated with industry trends. 

For hiring managers and team leads, recognizing these skills and fostering a culture that values and nurtures problem solving is key. It’s this emphasis on problem solving that can differentiate an average team from a high-performing one and an ordinary product from an industry-leading one.

At the end of the day, software engineering is fundamentally about solving problems — problems that matter to businesses, to users, and to the wider society. And it’s the proficient problem solvers who stand at the forefront of this dynamic field, turning challenges into opportunities, and ideas into reality.

This article was written with the help of AI. Can you tell which parts?

Get started with HackerRank

Over 2,500 companies and 40% of developers worldwide use HackerRank to hire tech talent and sharpen their skills.

Recommended topics

• Hire Developers
• Problem Solving

Does a College Degree Still Matter for Developers in 2024?

Problem Solving Skills for the Digital Age

Lucid Content

Reading time: about 6 min

Let’s face it: Things don’t always go according to plan. Systems fail, wires get crossed, projects fall apart.

Problems are an inevitable part of life and work. They’re also an opportunity to think critically and find solutions. But knowing how to get to the root of unexpected situations or challenges can mean the difference between moving forward and spinning your wheels.

Here, we’ll break down the key elements of problem solving, some effective problem solving approaches, and a few effective tools to help you arrive at solutions more quickly.

So, what is problem solving?

Broadly defined, problem solving is the process of finding solutions to difficult or complex issues. But you already knew that. Understanding problem solving frameworks, however, requires a deeper dive.

Think about a recent problem you faced. Maybe it was an interpersonal issue. Or it could have been a major creative challenge you needed to solve for a client at work. How did you feel as you approached the issue? Stressed? Confused? Optimistic? Most importantly, which problem solving techniques did you use to tackle the situation head-on? How did you organize thoughts to arrive at the best possible solution?

Solve your problem-solving problem  

Here’s the good news: Good problem solving skills can be learned. By its nature, problem solving doesn’t adhere to a clear set of do’s and don’ts—it requires flexibility, communication, and adaptation. However, most problems you face, at work or in life, can be tackled using four basic steps.

First, you must define the problem . This step sounds obvious, but often, you can notice that something is amiss in a project or process without really knowing where the core problem lies. The most challenging part of the problem solving process is uncovering where the problem originated.

Second, you work to generate alternatives to address the problem directly. This should be a collaborative process to ensure you’re considering every angle of the issue.

Third, you evaluate and test potential solutions to your problem. This step helps you fully understand the complexity of the issue and arrive at the best possible solution.

Finally, fourth, you select and implement the solution that best addresses the problem.

Following this basic four-step process will help you approach every problem you encounter with the same rigorous critical and strategic thinking process, recognize commonalities in new problems, and avoid repeating past mistakes.

In addition to these basic problem solving skills, there are several best practices that you should incorporate. These problem solving approaches can help you think more critically and creatively about any problem:

You may not feel like you have the right expertise to resolve a specific problem. Don’t let that stop you from tackling it. The best problem solvers become students of the problem at hand. Even if you don’t have particular expertise on a topic, your unique experience and perspective can lend itself to creative solutions.

Challenge the status quo

Standard problem solving methodologies and problem solving frameworks are a good starting point. But don’t be afraid to challenge assumptions and push boundaries. Good problem solvers find ways to apply existing best practices into innovative problem solving approaches.

Think broadly about and visualize the issue

Sometimes it’s hard to see a problem, even if it’s right in front of you. Clear answers could be buried in rows of spreadsheet data or lost in miscommunication. Use visualization as a problem solving tool to break down problems to their core elements. Visuals can help you see bottlenecks in the context of the whole process and more clearly organize your thoughts as you define the problem.  

Hypothesize, test, and try again

It might be cliche, but there’s truth in the old adage that 99% of inspiration is perspiration. The best problem solvers ask why, test, fail, and ask why again. Whether it takes one or 1,000 iterations to solve a problem, the important part—and the part that everyone remembers—is the solution.

Consider other viewpoints

Today’s problems are more complex, more difficult to solve, and they often involve multiple disciplines. They require group expertise and knowledge. Being open to others’ expertise increases your ability to be a great problem solver. Great solutions come from integrating your ideas with those of others to find a better solution. Excellent problem solvers build networks and know how to collaborate with other people and teams. They are skilled in bringing people together and sharing knowledge and information.

4 effective problem solving tools

As you work through the problem solving steps, try these tools to better define the issue and find the appropriate solution.

Root cause analysis

Similar to pulling weeds from your garden, if you don’t get to the root of the problem, it’s bound to come back. A root cause analysis helps you figure out the root cause behind any disruption or problem, so you can take steps to correct the problem from recurring. The root cause analysis process involves defining the problem, collecting data, and identifying causal factors to pinpoint root causes and arrive at a solution.

Less structured than other more traditional problem solving methods, the 5 Whys is simply what it sounds like: asking why over and over to get to the root of an obstacle or setback. This technique encourages an open dialogue that can trigger new ideas about a problem, whether done individually or with a group. Each why piggybacks off the answer to the previous why. Get started with the template below—both flowcharts and fishbone diagrams can also help you track your answers to the 5 Whys.

Brainstorming

A meeting of the minds, a brain dump, a mind meld, a jam session. Whatever you call it, collaborative brainstorming can help surface previously unseen issues, root causes, and alternative solutions. Create and share a mind map with your team members to fuel your brainstorming session.

Gap analysis

Sometimes you don’t know where the problem is until you determine where it isn’t. Gap filling helps you analyze inadequacies that are preventing you from reaching an optimized state or end goal. For example, a content gap analysis can help a content marketer determine where holes exist in messaging or the customer experience. Gap analysis is especially helpful when it comes to problem solving because it requires you to find workable solutions. A SWOT analysis chart that looks at a problem through the lens of strengths, opportunities, opportunities, and threats can be a helpful problem solving framework as you start your analysis.

A better way to problem solve

Beyond these practical tips and tools, there are myriad methodical and creative approaches to move a project forward or resolve a conflict. The right approach will depend on the scope of the issue and your desired outcome.

Depending on the problem, Lucidchart offers several templates and diagrams that could help you identify the cause of the issue and map out a plan to resolve it.  Learn more about how Lucidchart can help you take control of your problem solving process .

About Lucidchart

Lucidchart, a cloud-based intelligent diagramming application, is a core component of Lucid Software's Visual Collaboration Suite. This intuitive, cloud-based solution empowers teams to collaborate in real-time to build flowcharts, mockups, UML diagrams, customer journey maps, and more. Lucidchart propels teams forward to build the future faster. 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 lucidchart.com.

Related articles

How you can use creative problem solving at work.

Sometimes you're faced with challenges that traditional problem solving can't fix. Creative problem solving encourages you to find new, creative ways of thinking that can help you overcome the issue at hand more quickly.

Solve issues faster with the root cause analysis process

Root cause analysis refers to any problem-solving method used to trace an issue back to its origin. Learn how to complete a root cause analysis—we've even included templates to get you started.

Bring your bright ideas to life.

or continue with

By registering, you agree to our Terms of Service and you acknowledge that you have read and understand our Privacy Policy .

• Cambridge Dictionary +Plus

Meaning of problem-solving in English

Your browser doesn't support HTML5 audio

• problem-solver

Examples of problem-solving

Word of the Day

mountain climber

a person who climbs mountains as a sport

Apples and oranges (Talking about differences, Part 2)

Learn more with +Plus

• Recent and Recommended {{#preferredDictionaries}} {{name}} {{/preferredDictionaries}}
• Definitions Clear explanations of natural written and spoken English English Learner’s Dictionary Essential British English Essential American English
• Grammar and thesaurus Usage explanations of natural written and spoken English Grammar Thesaurus
• Pronunciation British and American pronunciations with audio English Pronunciation
• English–Chinese (Simplified) Chinese (Simplified)–English
• English–Chinese (Traditional) Chinese (Traditional)–English
• English–Dutch Dutch–English
• English–French French–English
• English–German German–English
• English–Indonesian Indonesian–English
• English–Italian Italian–English
• English–Japanese Japanese–English
• English–Norwegian Norwegian–English
• English–Polish Polish–English
• English–Portuguese Portuguese–English
• English–Spanish Spanish–English
• English–Swedish Swedish–English
• Dictionary +Plus Word Lists
• problem-solving
• All translations

To add problem-solving to a word list please sign up or log in.

Add problem-solving to one of your lists below, or create a new one.

{{message}}

Something went wrong.

There was a problem sending your report.

• Search Menu
• Sign in through your institution
• Browse content in Arts and Humanities
• Browse content in Archaeology
• Anglo-Saxon and Medieval Archaeology
• Archaeological Methodology and Techniques
• Archaeology by Region
• Archaeology of Religion
• Archaeology of Trade and Exchange
• Biblical Archaeology
• Contemporary and Public Archaeology
• Environmental Archaeology
• Historical Archaeology
• History and Theory of Archaeology
• Industrial Archaeology
• Landscape Archaeology
• Mortuary Archaeology
• Prehistoric Archaeology
• Underwater Archaeology
• Urban Archaeology
• Zooarchaeology
• Browse content in Architecture
• Architectural Structure and Design
• History of Architecture
• Residential and Domestic Buildings
• Theory of Architecture
• Browse content in Art
• Art Subjects and Themes
• History of Art
• Industrial and Commercial Art
• Theory of Art
• Biographical Studies
• Byzantine Studies
• Browse content in Classical Studies
• Classical Literature
• Classical Reception
• Classical History
• Classical Philosophy
• Classical Mythology
• Classical Art and Architecture
• Classical Oratory and Rhetoric
• Greek and Roman Papyrology
• Greek and Roman Archaeology
• Greek and Roman Epigraphy
• Greek and Roman Law
• Late Antiquity
• Religion in the Ancient World
• Digital Humanities
• Browse content in History
• Colonialism and Imperialism
• Diplomatic History
• Environmental History
• Genealogy, Heraldry, Names, and Honours
• Genocide and Ethnic Cleansing
• Historical Geography
• History by Period
• History of Emotions
• History of Agriculture
• History of Education
• History of Gender and Sexuality
• Industrial History
• Intellectual History
• International History
• Labour History
• Legal and Constitutional History
• Local and Family History
• Maritime History
• Military History
• National Liberation and Post-Colonialism
• Oral History
• Political History
• Public History
• Regional and National History
• Revolutions and Rebellions
• Slavery and Abolition of Slavery
• Social and Cultural History
• Theory, Methods, and Historiography
• Urban History
• World History
• Browse content in Language Teaching and Learning
• Language Learning (Specific Skills)
• Language Teaching Theory and Methods
• Browse content in Linguistics
• Applied Linguistics
• Cognitive Linguistics
• Computational Linguistics
• Forensic Linguistics
• Grammar, Syntax and Morphology
• Historical and Diachronic Linguistics
• History of English
• Language Evolution
• Language Reference
• Language Variation
• Language Families
• Language Acquisition
• Lexicography
• Linguistic Anthropology
• Linguistic Theories
• Linguistic Typology
• Phonetics and Phonology
• Psycholinguistics
• Sociolinguistics
• Translation and Interpretation
• Writing Systems
• Browse content in Literature
• Bibliography
• Children's Literature Studies
• Literary Studies (Romanticism)
• Literary Studies (American)
• Literary Studies (Modernism)
• Literary Studies (Asian)
• Literary Studies (European)
• Literary Studies (Eco-criticism)
• Literary Studies - World
• Literary Studies (1500 to 1800)
• Literary Studies (19th Century)
• Literary Studies (20th Century onwards)
• Literary Studies (African American Literature)
• Literary Studies (British and Irish)
• Literary Studies (Early and Medieval)
• Literary Studies (Fiction, Novelists, and Prose Writers)
• Literary Studies (Gender Studies)
• Literary Studies (Graphic Novels)
• Literary Studies (History of the Book)
• Literary Studies (Plays and Playwrights)
• Literary Studies (Poetry and Poets)
• Literary Studies (Postcolonial Literature)
• Literary Studies (Queer Studies)
• Literary Studies (Science Fiction)
• Literary Studies (Travel Literature)
• Literary Studies (War Literature)
• Literary Studies (Women's Writing)
• Literary Theory and Cultural Studies
• Mythology and Folklore
• Shakespeare Studies and Criticism
• Browse content in Media Studies
• Browse content in Music
• Applied Music
• Dance and Music
• Ethics in Music
• Ethnomusicology
• Gender and Sexuality in Music
• Medicine and Music
• Music Cultures
• Music and Media
• Music and Culture
• Music and Religion
• Music Education and Pedagogy
• Music Theory and Analysis
• Musical Scores, Lyrics, and Libretti
• Musical Structures, Styles, and Techniques
• Musicology and Music History
• Performance Practice and Studies
• Race and Ethnicity in Music
• Sound Studies
• Browse content in Performing Arts
• Browse content in Philosophy
• Aesthetics and Philosophy of Art
• Epistemology
• Feminist Philosophy
• History of Western Philosophy
• Metaphysics
• Moral Philosophy
• Non-Western Philosophy
• Philosophy of Language
• Philosophy of Mind
• Philosophy of Perception
• Philosophy of Action
• Philosophy of Law
• Philosophy of Religion
• Philosophy of Science
• Philosophy of Mathematics and Logic
• Practical Ethics
• Social and Political Philosophy
• Browse content in Religion
• Biblical Studies
• Christianity
• East Asian Religions
• History of Religion
• Judaism and Jewish Studies
• Qumran Studies
• Religion and Education
• Religion and Health
• Religion and Politics
• Religion and Science
• Religion and Law
• Religion and Art, Literature, and Music
• Religious Studies
• Browse content in Society and Culture
• Cookery, Food, and Drink
• Cultural Studies
• Customs and Traditions
• Ethical Issues and Debates
• Hobbies, Games, Arts and Crafts
• Natural world, Country Life, and Pets
• Popular Beliefs and Controversial Knowledge
• Sports and Outdoor Recreation
• Technology and Society
• Travel and Holiday
• Visual Culture
• Browse content in Law
• Arbitration
• Browse content in Company and Commercial Law
• Commercial Law
• Company Law
• Browse content in Comparative Law
• Systems of Law
• Competition Law
• Browse content in Constitutional and Administrative Law
• Government Powers
• Judicial Review
• Local Government Law
• Military and Defence Law
• Parliamentary and Legislative Practice
• Construction Law
• Contract Law
• Browse content in Criminal Law
• Criminal Procedure
• Criminal Evidence Law
• Sentencing and Punishment
• Employment and Labour Law
• Environment and Energy Law
• Browse content in Financial Law
• Banking Law
• Insolvency Law
• History of Law
• Human Rights and Immigration
• Intellectual Property Law
• Browse content in International Law
• Private International Law and Conflict of Laws
• Public International Law
• IT and Communications Law
• Jurisprudence and Philosophy of Law
• Law and Society
• Law and Politics
• Browse content in Legal System and Practice
• Courts and Procedure
• Legal Skills and Practice
• Primary Sources of Law
• Regulation of Legal Profession
• Medical and Healthcare Law
• Browse content in Policing
• Criminal Investigation and Detection
• Police and Security Services
• Police Procedure and Law
• Police Regional Planning
• Browse content in Property Law
• Personal Property Law
• Study and Revision
• Terrorism and National Security Law
• Browse content in Trusts Law
• Wills and Probate or Succession
• Browse content in Medicine and Health
• Browse content in Allied Health Professions
• Arts Therapies
• Clinical Science
• Dietetics and Nutrition
• Occupational Therapy
• Operating Department Practice
• Physiotherapy
• Radiography
• Speech and Language Therapy
• Browse content in Anaesthetics
• General Anaesthesia
• Neuroanaesthesia
• Clinical Neuroscience
• Browse content in Clinical Medicine
• Acute Medicine
• Cardiovascular Medicine
• Clinical Genetics
• Clinical Pharmacology and Therapeutics
• Dermatology
• Endocrinology and Diabetes
• Gastroenterology
• Genito-urinary Medicine
• Geriatric Medicine
• Infectious Diseases
• Medical Toxicology
• Medical Oncology
• Pain Medicine
• Palliative Medicine
• Rehabilitation Medicine
• Respiratory Medicine and Pulmonology
• Rheumatology
• Sleep Medicine
• Sports and Exercise Medicine
• Community Medical Services
• Critical Care
• Emergency Medicine
• Forensic Medicine
• Haematology
• History of Medicine
• Browse content in Medical Skills
• Clinical Skills
• Communication Skills
• Nursing Skills
• Surgical Skills
• Medical Ethics
• Browse content in Medical Dentistry
• Oral and Maxillofacial Surgery
• Paediatric Dentistry
• Restorative Dentistry and Orthodontics
• Surgical Dentistry
• Medical Statistics and Methodology
• Browse content in Neurology
• Clinical Neurophysiology
• Neuropathology
• Nursing Studies
• Browse content in Obstetrics and Gynaecology
• Gynaecology
• Occupational Medicine
• Ophthalmology
• Otolaryngology (ENT)
• Browse content in Paediatrics
• Neonatology
• Browse content in Pathology
• Chemical Pathology
• Clinical Cytogenetics and Molecular Genetics
• Histopathology
• Medical Microbiology and Virology
• Patient Education and Information
• Browse content in Pharmacology
• Psychopharmacology
• Browse content in Popular Health
• Caring for Others
• Complementary and Alternative Medicine
• Self-help and Personal Development
• Browse content in Preclinical Medicine
• Cell Biology
• Molecular Biology and Genetics
• Reproduction, Growth and Development
• Primary Care
• Professional Development in Medicine
• Browse content in Psychiatry
• Addiction Medicine
• Child and Adolescent Psychiatry
• Forensic Psychiatry
• Learning Disabilities
• Old Age Psychiatry
• Psychotherapy
• Browse content in Public Health and Epidemiology
• Epidemiology
• Public Health
• Browse content in Radiology
• Clinical Radiology
• Interventional Radiology
• Nuclear Medicine
• Radiation Oncology
• Reproductive Medicine
• Browse content in Surgery
• Cardiothoracic Surgery
• Gastro-intestinal and Colorectal Surgery
• General Surgery
• Neurosurgery
• Paediatric Surgery
• Peri-operative Care
• Plastic and Reconstructive Surgery
• Surgical Oncology
• Transplant Surgery
• Trauma and Orthopaedic Surgery
• Vascular Surgery
• Browse content in Science and Mathematics
• Browse content in Biological Sciences
• Aquatic Biology
• Biochemistry
• Bioinformatics and Computational Biology
• Developmental Biology
• Ecology and Conservation
• Evolutionary Biology
• Genetics and Genomics
• Microbiology
• Molecular and Cell Biology
• Natural History
• Plant Sciences and Forestry
• Research Methods in Life Sciences
• Structural Biology
• Systems Biology
• Zoology and Animal Sciences
• Browse content in Chemistry
• Analytical Chemistry
• Computational Chemistry
• Crystallography
• Environmental Chemistry
• Industrial Chemistry
• Inorganic Chemistry
• Materials Chemistry
• Medicinal Chemistry
• Mineralogy and Gems
• Organic Chemistry
• Physical Chemistry
• Polymer Chemistry
• Study and Communication Skills in Chemistry
• Theoretical Chemistry
• Browse content in Computer Science
• Artificial Intelligence
• Computer Architecture and Logic Design
• Game Studies
• Human-Computer Interaction
• Mathematical Theory of Computation
• Programming Languages
• Software Engineering
• Systems Analysis and Design
• Virtual Reality
• Browse content in Computing
• Business Applications
• Computer Games
• Computer Security
• Computer Networking and Communications
• Digital Lifestyle
• Graphical and Digital Media Applications
• Operating Systems
• Browse content in Earth Sciences and Geography
• Atmospheric Sciences
• Environmental Geography
• Geology and the Lithosphere
• Maps and Map-making
• Meteorology and Climatology
• Oceanography and Hydrology
• Palaeontology
• Physical Geography and Topography
• Regional Geography
• Soil Science
• Urban Geography
• Browse content in Engineering and Technology
• Agriculture and Farming
• Biological Engineering
• Civil Engineering, Surveying, and Building
• Electronics and Communications Engineering
• Energy Technology
• Engineering (General)
• Environmental Science, Engineering, and Technology
• History of Engineering and Technology
• Mechanical Engineering and Materials
• Technology of Industrial Chemistry
• Transport Technology and Trades
• Browse content in Environmental Science
• Applied Ecology (Environmental Science)
• Conservation of the Environment (Environmental Science)
• Environmental Sustainability
• Environmentalist Thought and Ideology (Environmental Science)
• Management of Land and Natural Resources (Environmental Science)
• Natural Disasters (Environmental Science)
• Nuclear Issues (Environmental Science)
• Pollution and Threats to the Environment (Environmental Science)
• Social Impact of Environmental Issues (Environmental Science)
• History of Science and Technology
• Browse content in Materials Science
• Ceramics and Glasses
• Composite Materials
• Metals, Alloying, and Corrosion
• Nanotechnology
• Browse content in Mathematics
• Applied Mathematics
• Biomathematics and Statistics
• History of Mathematics
• Mathematical Education
• Mathematical Finance
• Mathematical Analysis
• Numerical and Computational Mathematics
• Probability and Statistics
• Pure Mathematics
• Browse content in Neuroscience
• Cognition and Behavioural Neuroscience
• Development of the Nervous System
• Disorders of the Nervous System
• History of Neuroscience
• Invertebrate Neurobiology
• Molecular and Cellular Systems
• Neuroendocrinology and Autonomic Nervous System
• Neuroscientific Techniques
• Sensory and Motor Systems
• Browse content in Physics
• Astronomy and Astrophysics
• Atomic, Molecular, and Optical Physics
• Biological and Medical Physics
• Classical Mechanics
• Computational Physics
• Condensed Matter Physics
• Electromagnetism, Optics, and Acoustics
• History of Physics
• Mathematical and Statistical Physics
• Measurement Science
• Nuclear Physics
• Particles and Fields
• Plasma Physics
• Quantum Physics
• Relativity and Gravitation
• Semiconductor and Mesoscopic Physics
• Browse content in Psychology
• Affective Sciences
• Clinical Psychology
• Cognitive Psychology
• Cognitive Neuroscience
• Criminal and Forensic Psychology
• Developmental Psychology
• Educational Psychology
• Evolutionary Psychology
• Health Psychology
• History and Systems in Psychology
• Music Psychology
• Neuropsychology
• Organizational Psychology
• Psychological Assessment and Testing
• Psychology of Human-Technology Interaction
• Psychology Professional Development and Training
• Research Methods in Psychology
• Social Psychology
• Browse content in Social Sciences
• Browse content in Anthropology
• Anthropology of Religion
• Human Evolution
• Medical Anthropology
• Physical Anthropology
• Regional Anthropology
• Social and Cultural Anthropology
• Theory and Practice of Anthropology
• Browse content in Business and Management
• Business Ethics
• Business History
• Business Strategy
• Business and Technology
• Business and Government
• Business and the Environment
• Comparative Management
• Corporate Governance
• Corporate Social Responsibility
• Entrepreneurship
• Health Management
• Human Resource Management
• Industrial and Employment Relations
• Industry Studies
• Information and Communication Technologies
• International Business
• Knowledge Management
• Management and Management Techniques
• Operations Management
• Organizational Theory and Behaviour
• Pensions and Pension Management
• Public and Nonprofit Management
• Strategic Management
• Supply Chain Management
• Browse content in Criminology and Criminal Justice
• Criminal Justice
• Criminology
• Forms of Crime
• International and Comparative Criminology
• Youth Violence and Juvenile Justice
• Development Studies
• Browse content in Economics
• Agricultural, Environmental, and Natural Resource Economics
• Asian Economics
• Behavioural Finance
• Behavioural Economics and Neuroeconomics
• Econometrics and Mathematical Economics
• Economic History
• Economic Methodology
• Economic Systems
• Economic Development and Growth
• Financial Markets
• Financial Institutions and Services
• General Economics and Teaching
• Health, Education, and Welfare
• History of Economic Thought
• International Economics
• Labour and Demographic Economics
• Law and Economics
• Macroeconomics and Monetary Economics
• Microeconomics
• Public Economics
• Urban, Rural, and Regional Economics
• Welfare Economics
• Browse content in Education
• Adult Education and Continuous Learning
• Care and Counselling of Students
• Early Childhood and Elementary Education
• Educational Equipment and Technology
• Educational Strategies and Policy
• Higher and Further Education
• Organization and Management of Education
• Philosophy and Theory of Education
• Schools Studies
• Secondary Education
• Teaching of a Specific Subject
• Teaching of Specific Groups and Special Educational Needs
• Teaching Skills and Techniques
• Browse content in Environment
• Applied Ecology (Social Science)
• Climate Change
• Conservation of the Environment (Social Science)
• Environmentalist Thought and Ideology (Social Science)
• Natural Disasters (Environment)
• Social Impact of Environmental Issues (Social Science)
• Browse content in Human Geography
• Cultural Geography
• Economic Geography
• Political Geography
• Browse content in Interdisciplinary Studies
• Communication Studies
• Museums, Libraries, and Information Sciences
• Browse content in Politics
• African Politics
• Asian Politics
• Chinese Politics
• Comparative Politics
• Conflict Politics
• Elections and Electoral Studies
• Environmental Politics
• European Union
• Foreign Policy
• Gender and Politics
• Human Rights and Politics
• Indian Politics
• International Relations
• International Organization (Politics)
• International Political Economy
• Irish Politics
• Latin American Politics
• Middle Eastern Politics
• Political Behaviour
• Political Economy
• Political Institutions
• Political Theory
• Political Methodology
• Political Communication
• Political Philosophy
• Political Sociology
• Politics and Law
• Politics of Development
• Public Policy
• Public Administration
• Quantitative Political Methodology
• Regional Political Studies
• Russian Politics
• Security Studies
• State and Local Government
• UK Politics
• US Politics
• Browse content in Regional and Area Studies
• African Studies
• Asian Studies
• East Asian Studies
• Japanese Studies
• Latin American Studies
• Middle Eastern Studies
• Native American Studies
• Scottish Studies
• Browse content in Research and Information
• Research Methods
• Browse content in Social Work
• Addictions and Substance Misuse
• Adoption and Fostering
• Care of the Elderly
• Child and Adolescent Social Work
• Couple and Family Social Work
• Direct Practice and Clinical Social Work
• Emergency Services
• Human Behaviour and the Social Environment
• International and Global Issues in Social Work
• Mental and Behavioural Health
• Social Justice and Human Rights
• Social Policy and Advocacy
• Social Work and Crime and Justice
• Social Work Macro Practice
• Social Work Practice Settings
• Social Work Research and Evidence-based Practice
• Welfare and Benefit Systems
• Browse content in Sociology
• Childhood Studies
• Community Development
• Comparative and Historical Sociology
• Economic Sociology
• Gender and Sexuality
• Gerontology and Ageing
• Health, Illness, and Medicine
• Marriage and the Family
• Migration Studies
• Occupations, Professions, and Work
• Organizations
• Population and Demography
• Race and Ethnicity
• Social Theory
• Social Movements and Social Change
• Social Research and Statistics
• Social Stratification, Inequality, and Mobility
• Sociology of Religion
• Sociology of Education
• Sport and Leisure
• Urban and Rural Studies
• Browse content in Warfare and Defence
• Defence Strategy, Planning, and Research
• Land Forces and Warfare
• Military Administration
• Military Life and Institutions
• Naval Forces and Warfare
• Other Warfare and Defence Issues
• Peace Studies and Conflict Resolution
• Weapons and Equipment

• < Previous chapter
• Next chapter >

48 Problem Solving

Department of Psychological and Brain Sciences, University of California, Santa Barbara

• Published: 03 June 2013
• Cite Icon Cite
• Permissions Icon Permissions

Problem solving refers to cognitive processing directed at achieving a goal when the problem solver does not initially know a solution method. A problem exists when someone has a goal but does not know how to achieve it. Problems can be classified as routine or nonroutine, and as well defined or ill defined. The major cognitive processes in problem solving are representing, planning, executing, and monitoring. The major kinds of knowledge required for problem solving are facts, concepts, procedures, strategies, and beliefs. Classic theoretical approaches to the study of problem solving are associationism, Gestalt, and information processing. Current issues and suggested future issues include decision making, intelligence and creativity, teaching of thinking skills, expert problem solving, analogical reasoning, mathematical and scientific thinking, everyday thinking, and the cognitive neuroscience of problem solving. Common themes concern the domain specificity of problem solving and a focus on problem solving in authentic contexts.

The study of problem solving begins with defining problem solving, problem, and problem types. This introduction to problem solving is rounded out with an examination of cognitive processes in problem solving, the role of knowledge in problem solving, and historical approaches to the study of problem solving.

Definition of Problem Solving

Problem solving refers to cognitive processing directed at achieving a goal for which the problem solver does not initially know a solution method. This definition consists of four major elements (Mayer, 1992 ; Mayer & Wittrock, 2006 ):

Cognitive —Problem solving occurs within the problem solver’s cognitive system and can only be inferred indirectly from the problem solver’s behavior (including biological changes, introspections, and actions during problem solving). Process —Problem solving involves mental computations in which some operation is applied to a mental representation, sometimes resulting in the creation of a new mental representation. Directed —Problem solving is aimed at achieving a goal. Personal —Problem solving depends on the existing knowledge of the problem solver so that what is a problem for one problem solver may not be a problem for someone who already knows a solution method.

The definition is broad enough to include a wide array of cognitive activities such as deciding which apartment to rent, figuring out how to use a cell phone interface, playing a game of chess, making a medical diagnosis, finding the answer to an arithmetic word problem, or writing a chapter for a handbook. Problem solving is pervasive in human life and is crucial for human survival. Although this chapter focuses on problem solving in humans, problem solving also occurs in nonhuman animals and in intelligent machines.

How is problem solving related to other forms of high-level cognition processing, such as thinking and reasoning? Thinking refers to cognitive processing in individuals but includes both directed thinking (which corresponds to the definition of problem solving) and undirected thinking such as daydreaming (which does not correspond to the definition of problem solving). Thus, problem solving is a type of thinking (i.e., directed thinking).

Reasoning refers to problem solving within specific classes of problems, such as deductive reasoning or inductive reasoning. In deductive reasoning, the reasoner is given premises and must derive a conclusion by applying the rules of logic. For example, given that “A is greater than B” and “B is greater than C,” a reasoner can conclude that “A is greater than C.” In inductive reasoning, the reasoner is given (or has experienced) a collection of examples or instances and must infer a rule. For example, given that X, C, and V are in the “yes” group and x, c, and v are in the “no” group, the reasoning may conclude that B is in “yes” group because it is in uppercase format. Thus, reasoning is a type of problem solving.

Definition of Problem

A problem occurs when someone has a goal but does not know to achieve it. This definition is consistent with how the Gestalt psychologist Karl Duncker ( 1945 , p. 1) defined a problem in his classic monograph, On Problem Solving : “A problem arises when a living creature has a goal but does not know how this goal is to be reached.” However, today researchers recognize that the definition should be extended to include problem solving by intelligent machines. This definition can be clarified using an information processing approach by noting that a problem occurs when a situation is in the given state, the problem solver wants the situation to be in the goal state, and there is no obvious way to move from the given state to the goal state (Newell & Simon, 1972 ). Accordingly, the three main elements in describing a problem are the given state (i.e., the current state of the situation), the goal state (i.e., the desired state of the situation), and the set of allowable operators (i.e., the actions the problem solver is allowed to take). The definition of “problem” is broad enough to include the situation confronting a physician who wishes to make a diagnosis on the basis of preliminary tests and a patient examination, as well as a beginning physics student trying to solve a complex physics problem.

Types of Problems

It is customary in the problem-solving literature to make a distinction between routine and nonroutine problems. Routine problems are problems that are so familiar to the problem solver that the problem solver knows a solution method. For example, for most adults, “What is 365 divided by 12?” is a routine problem because they already know the procedure for long division. Nonroutine problems are so unfamiliar to the problem solver that the problem solver does not know a solution method. For example, figuring out the best way to set up a funding campaign for a nonprofit charity is a nonroutine problem for most volunteers. Technically, routine problems do not meet the definition of problem because the problem solver has a goal but knows how to achieve it. Much research on problem solving has focused on routine problems, although most interesting problems in life are nonroutine.

Another customary distinction is between well-defined and ill-defined problems. Well-defined problems have a clearly specified given state, goal state, and legal operators. Examples include arithmetic computation problems or games such as checkers or tic-tac-toe. Ill-defined problems have a poorly specified given state, goal state, or legal operators, or a combination of poorly defined features. Examples include solving the problem of global warming or finding a life partner. Although, ill-defined problems are more challenging, much research in problem solving has focused on well-defined problems.

Cognitive Processes in Problem Solving

The process of problem solving can be broken down into two main phases: problem representation , in which the problem solver builds a mental representation of the problem situation, and problem solution , in which the problem solver works to produce a solution. The major subprocess in problem representation is representing , which involves building a situation model —that is, a mental representation of the situation described in the problem. The major subprocesses in problem solution are planning , which involves devising a plan for how to solve the problem; executing , which involves carrying out the plan; and monitoring , which involves evaluating and adjusting one’s problem solving.

For example, given an arithmetic word problem such as “Alice has three marbles. Sarah has two more marbles than Alice. How many marbles does Sarah have?” the process of representing involves building a situation model in which Alice has a set of marbles, there is set of marbles for the difference between the two girls, and Sarah has a set of marbles that consists of Alice’s marbles and the difference set. In the planning process, the problem solver sets a goal of adding 3 and 2. In the executing process, the problem solver carries out the computation, yielding an answer of 5. In the monitoring process, the problem solver looks over what was done and concludes that 5 is a reasonable answer. In most complex problem-solving episodes, the four cognitive processes may not occur in linear order, but rather may interact with one another. Although some research focuses mainly on the execution process, problem solvers may tend to have more difficulty with the processes of representing, planning, and monitoring.

Knowledge for Problem Solving

An important theme in problem-solving research is that problem-solving proficiency on any task depends on the learner’s knowledge (Anderson et al., 2001 ; Mayer, 1992 ). Five kinds of knowledge are as follows:

Facts —factual knowledge about the characteristics of elements in the world, such as “Sacramento is the capital of California” Concepts —conceptual knowledge, including categories, schemas, or models, such as knowing the difference between plants and animals or knowing how a battery works Procedures —procedural knowledge of step-by-step processes, such as how to carry out long-division computations Strategies —strategic knowledge of general methods such as breaking a problem into parts or thinking of a related problem Beliefs —attitudinal knowledge about how one’s cognitive processing works such as thinking, “I’m good at this”

Although some research focuses mainly on the role of facts and procedures in problem solving, complex problem solving also depends on the problem solver’s concepts, strategies, and beliefs (Mayer, 1992 ).

Historical Approaches to Problem Solving

Psychological research on problem solving began in the early 1900s, as an outgrowth of mental philosophy (Humphrey, 1963 ; Mandler & Mandler, 1964 ). Throughout the 20th century four theoretical approaches developed: early conceptions, associationism, Gestalt psychology, and information processing.

Early Conceptions

The start of psychology as a science can be set at 1879—the year Wilhelm Wundt opened the first world’s psychology laboratory in Leipzig, Germany, and sought to train the world’s first cohort of experimental psychologists. Instead of relying solely on philosophical speculations about how the human mind works, Wundt sought to apply the methods of experimental science to issues addressed in mental philosophy. His theoretical approach became structuralism —the analysis of consciousness into its basic elements.

Wundt’s main contribution to the study of problem solving, however, was to call for its banishment. According to Wundt, complex cognitive processing was too complicated to be studied by experimental methods, so “nothing can be discovered in such experiments” (Wundt, 1911/1973 ). Despite his admonishments, however, a group of his former students began studying thinking mainly in Wurzburg, Germany. Using the method of introspection, subjects were asked to describe their thought process as they solved word association problems, such as finding the superordinate of “newspaper” (e.g., an answer is “publication”). Although the Wurzburg group—as they came to be called—did not produce a new theoretical approach, they found empirical evidence that challenged some of the key assumptions of mental philosophy. For example, Aristotle had proclaimed that all thinking involves mental imagery, but the Wurzburg group was able to find empirical evidence for imageless thought .

Associationism

The first major theoretical approach to take hold in the scientific study of problem solving was associationism —the idea that the cognitive representations in the mind consist of ideas and links between them and that cognitive processing in the mind involves following a chain of associations from one idea to the next (Mandler & Mandler, 1964 ; Mayer, 1992 ). For example, in a classic study, E. L. Thorndike ( 1911 ) placed a hungry cat in what he called a puzzle box—a wooden crate in which pulling a loop of string that hung from overhead would open a trap door to allow the cat to escape to a bowl of food outside the crate. Thorndike placed the cat in the puzzle box once a day for several weeks. On the first day, the cat engaged in many extraneous behaviors such as pouncing against the wall, pushing its paws through the slats, and meowing, but on successive days the number of extraneous behaviors tended to decrease. Overall, the time required to get out of the puzzle box decreased over the course of the experiment, indicating the cat was learning how to escape.

Thorndike’s explanation for how the cat learned to solve the puzzle box problem is based on an associationist view: The cat begins with a habit family hierarchy —a set of potential responses (e.g., pouncing, thrusting, meowing, etc.) all associated with the same stimulus (i.e., being hungry and confined) and ordered in terms of strength of association. When placed in the puzzle box, the cat executes its strongest response (e.g., perhaps pouncing against the wall), but when it fails, the strength of the association is weakened, and so on for each unsuccessful action. Eventually, the cat gets down to what was initially a weak response—waving its paw in the air—but when that response leads to accidentally pulling the string and getting out, it is strengthened. Over the course of many trials, the ineffective responses become weak and the successful response becomes strong. Thorndike refers to this process as the law of effect : Responses that lead to dissatisfaction become less associated with the situation and responses that lead to satisfaction become more associated with the situation. According to Thorndike’s associationist view, solving a problem is simply a matter of trial and error and accidental success. A major challenge to assocationist theory concerns the nature of transfer—that is, where does a problem solver find a creative solution that has never been performed before? Associationist conceptions of cognition can be seen in current research, including neural networks, connectionist models, and parallel distributed processing models (Rogers & McClelland, 2004 ).

Gestalt Psychology

The Gestalt approach to problem solving developed in the 1930s and 1940s as a counterbalance to the associationist approach. According to the Gestalt approach, cognitive representations consist of coherent structures (rather than individual associations) and the cognitive process of problem solving involves building a coherent structure (rather than strengthening and weakening of associations). For example, in a classic study, Kohler ( 1925 ) placed a hungry ape in a play yard that contained several empty shipping crates and a banana attached overhead but out of reach. Based on observing the ape in this situation, Kohler noted that the ape did not randomly try responses until one worked—as suggested by Thorndike’s associationist view. Instead, the ape stood under the banana, looked up at it, looked at the crates, and then in a flash of insight stacked the crates under the bananas as a ladder, and walked up the steps in order to reach the banana.

According to Kohler, the ape experienced a sudden visual reorganization in which the elements in the situation fit together in a way to solve the problem; that is, the crates could become a ladder that reduces the distance to the banana. Kohler referred to the underlying mechanism as insight —literally seeing into the structure of the situation. A major challenge of Gestalt theory is its lack of precision; for example, naming a process (i.e., insight) is not the same as explaining how it works. Gestalt conceptions can be seen in modern research on mental models and schemas (Gentner & Stevens, 1983 ).

Information Processing

The information processing approach to problem solving developed in the 1960s and 1970s and was based on the influence of the computer metaphor—the idea that humans are processors of information (Mayer, 2009 ). According to the information processing approach, problem solving involves a series of mental computations—each of which consists of applying a process to a mental representation (such as comparing two elements to determine whether they differ).

In their classic book, Human Problem Solving , Newell and Simon ( 1972 ) proposed that problem solving involved a problem space and search heuristics . A problem space is a mental representation of the initial state of the problem, the goal state of the problem, and all possible intervening states (based on applying allowable operators). Search heuristics are strategies for moving through the problem space from the given to the goal state. Newell and Simon focused on means-ends analysis , in which the problem solver continually sets goals and finds moves to accomplish goals.

Newell and Simon used computer simulation as a research method to test their conception of human problem solving. First, they asked human problem solvers to think aloud as they solved various problems such as logic problems, chess, and cryptarithmetic problems. Then, based on an information processing analysis, Newell and Simon created computer programs that solved these problems. In comparing the solution behavior of humans and computers, they found high similarity, suggesting that the computer programs were solving problems using the same thought processes as humans.

An important advantage of the information processing approach is that problem solving can be described with great clarity—as a computer program. An important limitation of the information processing approach is that it is most useful for describing problem solving for well-defined problems rather than ill-defined problems. The information processing conception of cognition lives on as a keystone of today’s cognitive science (Mayer, 2009 ).

Classic Issues in Problem Solving

Three classic issues in research on problem solving concern the nature of transfer (suggested by the associationist approach), the nature of insight (suggested by the Gestalt approach), and the role of problem-solving heuristics (suggested by the information processing approach).

Transfer refers to the effects of prior learning on new learning (or new problem solving). Positive transfer occurs when learning A helps someone learn B. Negative transfer occurs when learning A hinders someone from learning B. Neutral transfer occurs when learning A has no effect on learning B. Positive transfer is a central goal of education, but research shows that people often do not transfer what they learned to solving problems in new contexts (Mayer, 1992 ; Singley & Anderson, 1989 ).

Three conceptions of the mechanisms underlying transfer are specific transfer , general transfer , and specific transfer of general principles . Specific transfer refers to the idea that learning A will help someone learn B only if A and B have specific elements in common. For example, learning Spanish may help someone learn Latin because some of the vocabulary words are similar and the verb conjugation rules are similar. General transfer refers to the idea that learning A can help someone learn B even they have nothing specifically in common but A helps improve the learner’s mind in general. For example, learning Latin may help people learn “proper habits of mind” so they are better able to learn completely unrelated subjects as well. Specific transfer of general principles is the idea that learning A will help someone learn B if the same general principle or solution method is required for both even if the specific elements are different.

In a classic study, Thorndike and Woodworth ( 1901 ) found that students who learned Latin did not subsequently learn bookkeeping any better than students who had not learned Latin. They interpreted this finding as evidence for specific transfer—learning A did not transfer to learning B because A and B did not have specific elements in common. Modern research on problem-solving transfer continues to show that people often do not demonstrate general transfer (Mayer, 1992 ). However, it is possible to teach people a general strategy for solving a problem, so that when they see a new problem in a different context they are able to apply the strategy to the new problem (Judd, 1908 ; Mayer, 2008 )—so there is also research support for the idea of specific transfer of general principles.

Insight refers to a change in a problem solver’s mind from not knowing how to solve a problem to knowing how to solve it (Mayer, 1995 ; Metcalfe & Wiebe, 1987 ). In short, where does the idea for a creative solution come from? A central goal of problem-solving research is to determine the mechanisms underlying insight.

The search for insight has led to five major (but not mutually exclusive) explanatory mechanisms—insight as completing a schema, insight as suddenly reorganizing visual information, insight as reformulation of a problem, insight as removing mental blocks, and insight as finding a problem analog (Mayer, 1995 ). Completing a schema is exemplified in a study by Selz (Fridja & de Groot, 1982 ), in which people were asked to think aloud as they solved word association problems such as “What is the superordinate for newspaper?” To solve the problem, people sometimes thought of a coordinate, such as “magazine,” and then searched for a superordinate category that subsumed both terms, such as “publication.” According to Selz, finding a solution involved building a schema that consisted of a superordinate and two subordinate categories.

Reorganizing visual information is reflected in Kohler’s ( 1925 ) study described in a previous section in which a hungry ape figured out how to stack boxes as a ladder to reach a banana hanging above. According to Kohler, the ape looked around the yard and found the solution in a flash of insight by mentally seeing how the parts could be rearranged to accomplish the goal.

Reformulating a problem is reflected in a classic study by Duncker ( 1945 ) in which people are asked to think aloud as they solve the tumor problem—how can you destroy a tumor in a patient without destroying surrounding healthy tissue by using rays that at sufficient intensity will destroy any tissue in their path? In analyzing the thinking-aloud protocols—that is, transcripts of what the problem solvers said—Duncker concluded that people reformulated the goal in various ways (e.g., avoid contact with healthy tissue, immunize healthy tissue, have ray be weak in healthy tissue) until they hit upon a productive formulation that led to the solution (i.e., concentrating many weak rays on the tumor).

Removing mental blocks is reflected in classic studies by Duncker ( 1945 ) in which solving a problem involved thinking of a novel use for an object, and by Luchins ( 1942 ) in which solving a problem involved not using a procedure that had worked well on previous problems. Finding a problem analog is reflected in classic research by Wertheimer ( 1959 ) in which learning to find the area of a parallelogram is supported by the insight that one could cut off the triangle on one side and place it on the other side to form a rectangle—so a parallelogram is really a rectangle in disguise. The search for insight along each of these five lines continues in current problem-solving research.

Heuristics are problem-solving strategies, that is, general approaches to how to solve problems. Newell and Simon ( 1972 ) suggested three general problem-solving heuristics for moving from a given state to a goal state: random trial and error , hill climbing , and means-ends analysis . Random trial and error involves randomly selecting a legal move and applying it to create a new problem state, and repeating that process until the goal state is reached. Random trial and error may work for simple problems but is not efficient for complex ones. Hill climbing involves selecting the legal move that moves the problem solver closer to the goal state. Hill climbing will not work for problems in which the problem solver must take a move that temporarily moves away from the goal as is required in many problems.

Means-ends analysis involves creating goals and seeking moves that can accomplish the goal. If a goal cannot be directly accomplished, a subgoal is created to remove one or more obstacles. Newell and Simon ( 1972 ) successfully used means-ends analysis as the search heuristic in a computer program aimed at general problem solving, that is, solving a diverse collection of problems. However, people may also use specific heuristics that are designed to work for specific problem-solving situations (Gigerenzer, Todd, & ABC Research Group, 1999 ; Kahneman & Tversky, 1984 ).

Current and Future Issues in Problem Solving

Eight current issues in problem solving involve decision making, intelligence and creativity, teaching of thinking skills, expert problem solving, analogical reasoning, mathematical and scientific problem solving, everyday thinking, and the cognitive neuroscience of problem solving.

Decision Making

Decision making refers to the cognitive processing involved in choosing between two or more alternatives (Baron, 2000 ; Markman & Medin, 2002 ). For example, a decision-making task may involve choosing between getting $240 for sure or having a 25% change of getting $1000. According to economic theories such as expected value theory, people should chose the second option, which is worth $250 (i.e., .25 x $1000) rather than the first option, which is worth $240 (1.00 x $240), but psychological research shows that most people prefer the first option (Kahneman & Tversky, 1984 ).

Research on decision making has generated three classes of theories (Markman & Medin, 2002 ): descriptive theories, such as prospect theory (Kahneman & Tversky), which are based on the ideas that people prefer to overweight the cost of a loss and tend to overestimate small probabilities; heuristic theories, which are based on the idea that people use a collection of short-cut strategies such as the availability heuristic (Gigerenzer et al., 1999 ; Kahneman & Tversky, 2000 ); and constructive theories, such as mental accounting (Kahneman & Tversky, 2000 ), in which people build a narrative to justify their choices to themselves. Future research is needed to examine decision making in more realistic settings.

Intelligence and Creativity

Although researchers do not have complete consensus on the definition of intelligence (Sternberg, 1990 ), it is reasonable to view intelligence as the ability to learn or adapt to new situations. Fluid intelligence refers to the potential to solve problems without any relevant knowledge, whereas crystallized intelligence refers to the potential to solve problems based on relevant prior knowledge (Sternberg & Gregorenko, 2003 ). As people gain more experience in a field, their problem-solving performance depends more on crystallized intelligence (i.e., domain knowledge) than on fluid intelligence (i.e., general ability) (Sternberg & Gregorenko, 2003 ). The ability to monitor and manage one’s cognitive processing during problem solving—which can be called metacognition —is an important aspect of intelligence (Sternberg, 1990 ). Research is needed to pinpoint the knowledge that is needed to support intelligent performance on problem-solving tasks.

Creativity refers to the ability to generate ideas that are original (i.e., other people do not think of the same idea) and functional (i.e., the idea works; Sternberg, 1999 ). Creativity is often measured using tests of divergent thinking —that is, generating as many solutions as possible for a problem (Guilford, 1967 ). For example, the uses test asks people to list as many uses as they can think of for a brick. Creativity is different from intelligence, and it is at the heart of creative problem solving—generating a novel solution to a problem that the problem solver has never seen before. An important research question concerns whether creative problem solving depends on specific knowledge or creativity ability in general.

Teaching of Thinking Skills

How can people learn to be better problem solvers? Mayer ( 2008 ) proposes four questions concerning teaching of thinking skills:

What to teach —Successful programs attempt to teach small component skills (such as how to generate and evaluate hypotheses) rather than improve the mind as a single monolithic skill (Covington, Crutchfield, Davies, & Olton, 1974 ). How to teach —Successful programs focus on modeling the process of problem solving rather than solely reinforcing the product of problem solving (Bloom & Broder, 1950 ). Where to teach —Successful programs teach problem-solving skills within the specific context they will be used rather than within a general course on how to solve problems (Nickerson, 1999 ). When to teach —Successful programs teaching higher order skills early rather than waiting until lower order skills are completely mastered (Tharp & Gallimore, 1988 ).

Overall, research on teaching of thinking skills points to the domain specificity of problem solving; that is, successful problem solving depends on the problem solver having domain knowledge that is relevant to the problem-solving task.

Expert Problem Solving

Research on expertise is concerned with differences between how experts and novices solve problems (Ericsson, Feltovich, & Hoffman, 2006 ). Expertise can be defined in terms of time (e.g., 10 years of concentrated experience in a field), performance (e.g., earning a perfect score on an assessment), or recognition (e.g., receiving a Nobel Prize or becoming Grand Master in chess). For example, in classic research conducted in the 1940s, de Groot ( 1965 ) found that chess experts did not have better general memory than chess novices, but they did have better domain-specific memory for the arrangement of chess pieces on the board. Chase and Simon ( 1973 ) replicated this result in a better controlled experiment. An explanation is that experts have developed schemas that allow them to chunk collections of pieces into a single configuration.

In another landmark study, Larkin et al. ( 1980 ) compared how experts (e.g., physics professors) and novices (e.g., first-year physics students) solved textbook physics problems about motion. Experts tended to work forward from the given information to the goal, whereas novices tended to work backward from the goal to the givens using a means-ends analysis strategy. Experts tended to store their knowledge in an integrated way, whereas novices tended to store their knowledge in isolated fragments. In another study, Chi, Feltovich, and Glaser ( 1981 ) found that experts tended to focus on the underlying physics concepts (such as conservation of energy), whereas novices tended to focus on the surface features of the problem (such as inclined planes or springs). Overall, research on expertise is useful in pinpointing what experts know that is different from what novices know. An important theme is that experts rely on domain-specific knowledge rather than solely general cognitive ability.

Analogical Reasoning

Analogical reasoning occurs when people solve one problem by using their knowledge about another problem (Holyoak, 2005 ). For example, suppose a problem solver learns how to solve a problem in one context using one solution method and then is given a problem in another context that requires the same solution method. In this case, the problem solver must recognize that the new problem has structural similarity to the old problem (i.e., it may be solved by the same method), even though they do not have surface similarity (i.e., the cover stories are different). Three steps in analogical reasoning are recognizing —seeing that a new problem is similar to a previously solved problem; abstracting —finding the general method used to solve the old problem; and mapping —using that general method to solve the new problem.

Research on analogical reasoning shows that people often do not recognize that a new problem can be solved by the same method as a previously solved problem (Holyoak, 2005 ). However, research also shows that successful analogical transfer to a new problem is more likely when the problem solver has experience with two old problems that have the same underlying structural features (i.e., they are solved by the same principle) but different surface features (i.e., they have different cover stories) (Holyoak, 2005 ). This finding is consistent with the idea of specific transfer of general principles as described in the section on “Transfer.”

Mathematical and Scientific Problem Solving

Research on mathematical problem solving suggests that five kinds of knowledge are needed to solve arithmetic word problems (Mayer, 2008 ):

Factual knowledge —knowledge about the characteristics of problem elements, such as knowing that there are 100 cents in a dollar Schematic knowledge —knowledge of problem types, such as being able to recognize time-rate-distance problems Strategic knowledge —knowledge of general methods, such as how to break a problem into parts Procedural knowledge —knowledge of processes, such as how to carry our arithmetic operations Attitudinal knowledge —beliefs about one’s mathematical problem-solving ability, such as thinking, “I am good at this”

People generally possess adequate procedural knowledge but may have difficulty in solving mathematics problems because they lack factual, schematic, strategic, or attitudinal knowledge (Mayer, 2008 ). Research is needed to pinpoint the role of domain knowledge in mathematical problem solving.

Research on scientific problem solving shows that people harbor misconceptions, such as believing that a force is needed to keep an object in motion (McCloskey, 1983 ). Learning to solve science problems involves conceptual change, in which the problem solver comes to recognize that previous conceptions are wrong (Mayer, 2008 ). Students can be taught to engage in scientific reasoning such as hypothesis testing through direct instruction in how to control for variables (Chen & Klahr, 1999 ). A central theme of research on scientific problem solving concerns the role of domain knowledge.

Everyday Thinking

Everyday thinking refers to problem solving in the context of one’s life outside of school. For example, children who are street vendors tend to use different procedures for solving arithmetic problems when they are working on the streets than when they are in school (Nunes, Schlieman, & Carraher, 1993 ). This line of research highlights the role of situated cognition —the idea that thinking always is shaped by the physical and social context in which it occurs (Robbins & Aydede, 2009 ). Research is needed to determine how people solve problems in authentic contexts.

Cognitive Neuroscience of Problem Solving

The cognitive neuroscience of problem solving is concerned with the brain activity that occurs during problem solving. For example, using fMRI brain imaging methodology, Goel ( 2005 ) found that people used the language areas of the brain to solve logical reasoning problems presented in sentences (e.g., “All dogs are pets…”) and used the spatial areas of the brain to solve logical reasoning problems presented in abstract letters (e.g., “All D are P…”). Cognitive neuroscience holds the potential to make unique contributions to the study of problem solving.

Problem solving has always been a topic at the fringe of cognitive psychology—too complicated to study intensively but too important to completely ignore. Problem solving—especially in realistic environments—is messy in comparison to studying elementary processes in cognition. The field remains fragmented in the sense that topics such as decision making, reasoning, intelligence, expertise, mathematical problem solving, everyday thinking, and the like are considered to be separate topics, each with its own separate literature. Yet some recurring themes are the role of domain-specific knowledge in problem solving and the advantages of studying problem solving in authentic contexts.

Future Directions

Some important issues for future research include the three classic issues examined in this chapter—the nature of problem-solving transfer (i.e., How are people able to use what they know about previous problem solving to help them in new problem solving?), the nature of insight (e.g., What is the mechanism by which a creative solution is constructed?), and heuristics (e.g., What are some teachable strategies for problem solving?). In addition, future research in problem solving should continue to pinpoint the role of domain-specific knowledge in problem solving, the nature of cognitive ability in problem solving, how to help people develop proficiency in solving problems, and how to provide aids for problem solving.

Anderson L. W. , Krathwohl D. R. , Airasian P. W. , Cruikshank K. A. , Mayer R. E. , Pintrich P. R. , Raths, J., & Wittrock M. C. ( 2001 ). A taxonomy for learning, teaching, and assessing: A revision of Bloom’s taxonomy of educational objectives. New York : Longman.

Baron J. ( 2000 ). Thinking and deciding (3rd ed.). New York : Cambridge University Press.

Google Scholar

Google Preview

Bloom B. S. , & Broder B. J. ( 1950 ). Problem-solving processes of college students: An exploratory investigation. Chicago : University of Chicago Press.

Chase W. G. , & Simon H. A. ( 1973 ). Perception in chess.   Cognitive Psychology, 4, 55–81.

Chen Z. , & Klahr D. ( 1999 ). All other things being equal: Acquisition and transfer of the control of variable strategy . Child Development, 70, 1098–1120.

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

Covington M. V. , Crutchfield R. S. , Davies L. B. , & Olton R. M. ( 1974 ). The productive thinking program. Columbus, OH : Merrill.

de Groot A. D. ( 1965 ). Thought and choice in chess. The Hague, The Netherlands : Mouton.

Duncker K. ( 1945 ). On problem solving.   Psychological Monographs, 58 (3) (Whole No. 270).

Ericsson K. A. , Feltovich P. J. , & Hoffman R. R. (Eds.). ( 2006 ). The Cambridge handbook of expertise and expert performance. New York : Cambridge University Press.

Fridja N. H. , & de Groot A. D. ( 1982 ). Otto Selz: His contribution to psychology. The Hague, The Netherlands : Mouton.

Gentner D. , & Stevens A. L. (Eds.). ( 1983 ). Mental models. Hillsdale, NJ : Erlbaum.

Gigerenzer G. , Todd P. M. , & ABC Research Group (Eds.). ( 1999 ). Simple heuristics that make us smart. Oxford, England : Oxford University Press.

Goel V. ( 2005 ). Cognitive neuroscience of deductive reasoning. In K. J. Holyoak & R. G. Morrison (Eds.), The Cambridge handbook of thinking and reasoning (pp. 475–492). New York : Cambridge University Press.

Guilford J. P. ( 1967 ). The nature of human intelligence. New York : McGraw-Hill.

Holyoak K. J. ( 2005 ). Analogy. In K. J. Holyoak & R. G. Morrison (Eds.), The Cambridge handbook of thinking and reasoning (pp. 117–142). New York : Cambridge University Press.

Humphrey G. ( 1963 ). Thinking: An introduction to experimental psychology. New York : Wiley.

Judd C. H. ( 1908 ). The relation of special training and general intelligence. Educational Review, 36, 28–42.

Kahneman D. , & Tversky A. ( 1984 ). Choices, values, and frames. American Psychologist, 39, 341–350.

Kahneman D. , & Tversky A. (Eds.). ( 2000 ). Choices, values, and frames. New York : Cambridge University Press.

Kohler W. ( 1925 ). The mentality of apes. New York : Liveright.

Larkin J. H. , McDermott J. , Simon D. P. , & Simon H. A. ( 1980 ). Expert and novice performance in solving physics problems. Science, 208, 1335–1342.

Luchins A. ( 1942 ). Mechanization in problem solving.   Psychological Monographs, 54 (6) (Whole No. 248).

Mandler J. M. , & Mandler G. ( 1964 ). Thinking from associationism to Gestalt. New York : Wiley.

Markman A. B. , & Medin D. L. ( 2002 ). Decision making. In D. Medin (Ed.), Stevens’ handbook of experimental psychology, Vol. 2. Memory and cognitive processes (2nd ed., pp. 413–466). New York : Wiley.

Mayer R. E. ( 1992 ). Thinking, problem solving, cognition (2nd ed). New York : Freeman.

Mayer R. E. ( 1995 ). The search for insight: Grappling with Gestalt psychology’s unanswered questions. In R. J. Sternberg & J. E. Davidson (Eds.), The nature of insight (pp. 3–32). Cambridge, MA : MIT Press.

Mayer R. E. ( 2008 ). Learning and instruction. Upper Saddle River, NJ : Merrill Prentice Hall.

Mayer R. E. ( 2009 ). Information processing. In T. L. Good (Ed.), 21st century education: A reference handbook (pp. 168–174). Thousand Oaks, CA : Sage.

Mayer R. E. , & Wittrock M. C. ( 2006 ). Problem solving. In P. A. Alexander & P. H. Winne (Eds.), Handbook of educational psychology (2nd ed., pp. 287–304). Mahwah, NJ : Erlbaum.

McCloskey M. ( 1983 ). Intuitive physics.   Scientific American, 248 (4), 122–130.

Metcalfe J. , & Wiebe D. ( 1987 ). Intuition in insight and non-insight problem solving. Memory and Cognition, 15, 238–246.

Newell A. , & Simon H. A. ( 1972 ). Human problem solving. Englewood Cliffs, NJ : Prentice-Hall.

Nickerson R. S. ( 1999 ). Enhancing creativity. In R. J. Sternberg (Ed.), Handbook of creativity (pp. 392–430). New York : Cambridge University Press.

Nunes T. , Schliemann A. D. , & Carraher D. W , ( 1993 ). Street mathematics and school mathematics. Cambridge, England : Cambridge University Press.

Robbins P. , & Aydede M. (Eds.). ( 2009 ). The Cambridge handbook of situated cognition. New York : Cambridge University Press.

Rogers T. T. , & McClelland J. L. ( 2004 ). Semantic cognition: A parallel distributed processing approach. Cambridge, MA : MIT Press.

Singley M. K. , & Anderson J. R. ( 1989 ). The transfer of cognitive skill. Cambridge, MA : Harvard University Press.

Sternberg R. J. ( 1990 ). Metaphors of mind: Conceptions of the nature of intelligence. New York : Cambridge University Press.

Sternberg R. J. ( 1999 ). Handbook of creativity. New York : Cambridge University Press.

Sternberg R. J. , & Gregorenko E. L. (Eds.). ( 2003 ). The psychology of abilities, competencies, and expertise. New York : Cambridge University Press.

Tharp R. G. , & Gallimore R. ( 1988 ). Rousing minds to life: Teaching, learning, and schooling in social context. New York : Cambridge University Press.

Thorndike E. L. ( 1911 ). Animal intelligence. New York: Hafner.

Thorndike E. L. , & Woodworth R. S. ( 1901 ). The influence of improvement in one mental function upon the efficiency of other functions. Psychological Review, 8, 247–261.

Wertheimer M. ( 1959 ). Productive thinking. New York : Harper and Collins.

Wundt W. ( 1973 ). An introduction to experimental psychology. New York : Arno Press. (Original work published in 1911).

Further Reading

Baron, J. ( 2008 ). Thinking and deciding (4th ed). New York: Cambridge University Press.

Duncker, K. ( 1945 ). On problem solving. Psychological Monographs , 58(3) (Whole No. 270).

Holyoak, K. J. , & Morrison, R. G. ( 2005 ). The Cambridge handbook of thinking and reasoning . New York: Cambridge University Press.

Mayer, R. E. , & Wittrock, M. C. ( 2006 ). Problem solving. In P. A. Alexander & P. H. Winne (Eds.), Handbook of educational psychology (2nd ed., pp. 287–304). Mahwah, NJ: Erlbaum.

Sternberg, R. J. , & Ben-Zeev, T. ( 2001 ). Complex cognition: The psychology of human thought . New York: Oxford University Press.

Weisberg, R. W. ( 2006 ). Creativity . New York: Wiley.

• About Oxford Academic
• Publish journals with us
• University press partners
• What we publish
• New features  
• Open access
• Institutional account management
• Rights and permissions
• Get help with access
• Accessibility
• Advertising
• Media enquiries
• Oxford University Press
• Oxford Languages
• University of Oxford

Oxford University Press is a department of the University of Oxford. It furthers the University's objective of excellence in research, scholarship, and education by publishing worldwide

• Copyright © 2024 Oxford University Press
• Cookie settings
• Cookie policy
• Privacy policy
• Legal notice

This Feature Is Available To Subscribers Only

Sign In or Create an Account

This PDF is available to Subscribers Only

For full access to this pdf, sign in to an existing account, or purchase an annual subscription.

What Is Problem Solving?

You will often see beach clean-up drives being publicized in coastal cities. There are already dustbins available on the beaches,…

You will often see beach clean-up drives being publicized in coastal cities. There are already dustbins available on the beaches, so why do people need to organize these drives? It’s evident that despite advertising and posting anti-littering messages, some of us don’t follow the rules.

Temporary food stalls and shops make it even more difficult to keep the beaches clean. Since people can’t ask the shopkeepers to relocate or prevent every single person from littering, the clean-up drive is needed.  This is an ideal example of problem-solving psychology in humans. ( 230-fifth.com ) So, what is problem-solving? Let’s find out.

What Is Problem-Solving?

At its simplest, the meaning of problem-solving is the process of defining a problem, determining its cause, and implementing a solution. The definition of problem-solving is rooted in the fact that as humans, we exert control over our environment through solutions. We move forward in life when we solve problems and make decisions. 

We can better define the problem-solving process through a series of important steps.

Identify The Problem: 

This step isn’t as simple as it sounds. Most times, we mistakenly identify the consequences of a problem rather than the problem itself. It’s important that we’re careful to identify the actual problem and not just its symptoms. 

Define The Problem: 

Once the problem has been identified correctly, you should define it. This step can help clarify what needs to be addressed and for what purpose.

Form A Strategy: 

Develop a strategy to solve your problem. Defining an approach will provide direction and clarity on the next steps. 

Organize The Information:  

Organizing information systematically will help you determine whether something is missing. The more information you have, the easier it’ll become for you to arrive at a solution.  

Allocate Resources:  

We may not always be armed with the necessary resources to solve a problem. Before you commit to implementing a solution for a problem, you should determine the availability of different resources—money, time and other costs.

Track Progress: 

The true meaning of problem-solving is to work towards an objective. If you measure your progress, you can evaluate whether you’re on track. You could revise your strategies if you don’t notice the desired level of progress. 

Evaluate The Results:  

After you spot a solution, evaluate the results to determine whether it’s the best possible solution. For example, you can evaluate the success of a fitness routine after several weeks of exercise.

Meaning Of Problem-Solving Skill

Now that we’ve established the definition of problem-solving psychology in humans, let’s look at how we utilize our problem-solving skills.  These skills help you determine the source of a problem and how to effectively determine the solution. Problem-solving skills aren’t innate and can be mastered over time. Here are some important skills that are beneficial for finding solutions.

Communication

Communication is a critical skill when you have to work in teams.  If you and your colleagues have to work on a project together, you’ll have to collaborate with each other. In case of differences of opinion, you should be able to listen attentively and respond respectfully in order to successfully arrive at a solution.

As a problem-solver, you need to be able to research and identify underlying causes. You should never treat a problem lightly. In-depth study is imperative because often people identify only the symptoms and not the actual problem.

Once you have researched and identified the factors causing a problem, start working towards developing solutions. Your analytical skills can help you differentiate between effective and ineffective solutions.

Decision-Making

You’ll have to make a decision after you’ve identified the source and methods of solving a problem. If you’ve done your research and applied your analytical skills effectively, it’ll become easier for you to take a call or a decision.

Organizations really value decisive problem-solvers. Harappa Education’s   Defining Problems course will guide you on the path to developing a problem-solving mindset. Learn how to identify the different types of problems using the Types of Problems framework. Additionally, the SMART framework, which is a five-point tool, will teach you to create specific and actionable objectives to address problem statements and arrive at solutions. 

Explore topics & skills such as Problem Solving Skills , PICK Chart , How to Solve Problems & Barriers to Problem Solving from our Harappa Diaries blog section and develop your skills.

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

Gain essential management and leadership skills

Busy schedule? No problem. Learn anytime, anywhere. 

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

Join today and save on an annual membership!

Sign-up to our newsletter

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

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Latest Updates

Better Public Speaking

How to Build Confidence in Others

Mind Tools Store

About Mind Tools Content

Discover something new today

How to create psychological safety at work.

Speaking up without fear

How to Guides

Pain Points Podcast - Presentations Pt 1

How do you get better at presenting?

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

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

Recommended for you

Communications planning.

Getting the Right Message Across in the Right Way

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

Problems: Definition, Types, and Evidence

• Reference work entry
• pp 2690–2693
• Cite this reference work entry

• Norbert M. Seel 2  

2173 Accesses

1 Citations

Problem solving

A distinction can be made between “task” and “problem.” Generally, a task is a well-defined piece of work that is usually imposed by another person and may be burdensome. A problem is generally considered to be a task, a situation, or person which is difficult to deal with or control due to complexity and intransparency. In everyday language, a problem is a question proposed for solution, a matter stated for examination or proof. In each case, a problem is considered to be a matter which is difficult to solve or settle, a doubtful case, or a complex task involving doubt and uncertainty.

Theoretical Background

The nature of human problem solving has been studied by psychologists over the past hundred years. Beginning with the early experimental work of the Gestalt psychologists in Germany, and continuing through the 1960s and early 1970s, research on problem solving typically operated with relatively simple laboratory problems, such as Duncker’s...

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

• Available as PDF
• Read on any device
• Instant download
• Own it forever
• Available as EPUB and PDF
• Durable hardcover edition
• Dispatched in 3 to 5 business days
• Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Berry, D. C., & Broadbent, D. E. (1995). Implicit learning in the control of complex systems: A reconsideration of some of the earlier claims. In P. A. Frensch & J. Funke (Eds.), Complex problem solving: The European perspective (pp. 131–150). Hillsdale: Lawrence Erlbaum.

Google Scholar  

Broadbent, D. E. (1977). Levels, hierarchies, and the locus of control. Quarterly Journal of Experimental Psychology, 29 , 181–201.

Article   Google Scholar  

Dörner, D. (1976). Problemlösen als Informationsverarbeitung . Stuttgart: Kohlhammer (Problem solving as information processing).

Dörner, D., Kreuzig, H. W., Reither, F., & Stäudel, T. (1983). Lohhausen. Vom Umgang mit Unbestimmtheit und Komplexität [Lohhausen. The concern with uncertainty and complexity] . Bern: Huber.

Dörner, D. (1989). Die Logik des Misslingens . Hamburg: Rowohlt.

Funke, J. (1992). Wissen über dynamische Systeme: Erwerb, Repräsentation und Anwendung . Berlin: Springer.

Book   Google Scholar  

Funke, J., & Frensch, P. (1995). Complex problem solving research in North America and Europe: An integrative review. Foreign Psychology, 5 , 42–47.

Jonassen, D. H. (1997). Instructional design models for well-structured and ill-structured problem-solving learning outcomes. Educational Technology Research and Development, 45 (1), 65–94.

Newell, A., & Simon, H. A. (1972). Human problem solving . Englewood Cliffs: Prentice Hall.

Newell, A., Shaw, J. C., & Simon, H. A. (1959). A general problem-solving program for a computer. Computers and Automation, 8 (7), 10–16.

Download references

Author information

Authors and affiliations.

Department of Education, University of Freiburg, Rempartstr. 11, 3. OG, Freiburg, 79098, Germany

Prof. Norbert M. Seel ( Faculty of Economics and Behavioral Sciences )

You can also search for this author in PubMed   Google Scholar

Corresponding author

Correspondence to Norbert M. Seel .

Editor information

Editors and affiliations.

Faculty of Economics and Behavioral Sciences, Department of Education, University of Freiburg, 79085, Freiburg, Germany

Norbert M. Seel

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Springer Science+Business Media, LLC

About this entry

Cite this entry.

Seel, N.M. (2012). Problems: Definition, Types, and Evidence. In: Seel, N.M. (eds) Encyclopedia of the Sciences of Learning. Springer, Boston, MA. https://doi.org/10.1007/978-1-4419-1428-6_914

Download citation

DOI : https://doi.org/10.1007/978-1-4419-1428-6_914

Publisher Name : Springer, Boston, MA

Print ISBN : 978-1-4419-1427-9

Online ISBN : 978-1-4419-1428-6

eBook Packages : Humanities, Social Sciences and Law

Share this entry

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

• Publish with us

Policies and ethics

• Find a journal
• Track your research

• SUGGESTED TOPICS
• The Magazine
• Newsletters
• Managing Yourself
• Managing Teams
• Work-life Balance
• The Big Idea
• Data & Visuals
• Reading Lists
• Case Selections
• HBR Learning
• Topic Feeds
• Account Settings
• Email Preferences

Share Podcast

A Better Framework for Solving Tough Problems

Start with trust and end with speed.

• Apple Podcasts

When it comes to solving complicated problems, the default for many organizational leaders is to take their time to work through the issues at hand. Unfortunately, that often leads to patchwork solutions or problems not truly getting resolved.

But Anne Morriss offers a different framework. In this episode, she outlines a five-step process for solving any problem and explains why starting with trust and ending with speed is so important for effective change leadership. As she says, “Let’s get into dialogue with the people who are also impacted by the problem before we start running down the path of solving it.”

Morriss is an entrepreneur and leadership coach. She’s also the coauthor of the book, Move Fast and Fix Things: The Trusted Leader’s Guide to Solving Hard Problems .

Key episode topics include: strategy, decision making and problem solving, strategy execution, managing people, collaboration and teams, trustworthiness, organizational culture, change leadership, problem solving, leadership.

HBR On Strategy curates the best case studies and conversations with the world’s top business and management experts, to help you unlock new ways of doing business. New episodes every week.

• Listen to the full HBR IdeaCast episode: How to Solve Tough Problems Better and Faster (2023)
• Find more episodes of HBR IdeaCast
• Discover 100 years of Harvard Business Review articles, case studies, podcasts, and more at HBR.org .

HANNAH BATES: Welcome to HBR On Strategy , case studies and conversations with the world’s top business and management experts, hand-selected to help you unlock new ways of doing business.

When it comes to solving complicated problems, many leaders only focus on the most apparent issues. Unfortunately that often leads to patchwork or partial solutions. But Anne Morriss offers a different framework that aims to truly tackle big problems by first leaning into trust and then focusing on speed.

Morriss is an entrepreneur and leadership coach. She’s also the co-author of the book, Move Fast and Fix Things: The Trusted Leader’s Guide to Solving Hard Problems . In this episode, she outlines a five-step process for solving any problem. Some, she says, can be solved in a week, while others take much longer. She also explains why starting with trust and ending with speed is so important for effective change leadership.

This episode originally aired on HBR IdeaCast in October 2023. Here it is.

CURT NICKISCH: Welcome to the HBR IdeaCast from Harvard Business Review. I’m Curt Nickisch.

Problems can be intimidating. Sure, some problems are fun to dig into. You roll up your sleeves, you just take care of them; but others, well, they’re complicated. Sometimes it’s hard to wrap your brain around a problem, much less fix it.

And that’s especially true for leaders in organizations where problems are often layered and complex. They sometimes demand technical, financial, or interpersonal knowledge to fix. And whether it’s avoidance on the leaders’ part or just the perception that a problem is systemic or even intractable, problems find a way to endure, to keep going, to keep being a problem that everyone tries to work around or just puts up with.

But today’s guest says that just compounds it and makes the problem harder to fix. Instead, she says, speed and momentum are key to overcoming a problem.

Anne Morriss is an entrepreneur, leadership coach and founder of the Leadership Consortium and with Harvard Business School Professor Francis Frei, she wrote the new book, Move Fast and Fix Things: The Trusted Leaders Guide to Solving Hard Problems . Anne, welcome back to the show.

ANNE MORRISS: Curt, thank you so much for having me.

CURT NICKISCH: So, to generate momentum at an organization, you say that you really need speed and trust. We’ll get into those essential ingredients some more, but why are those two essential?

ANNE MORRISS: Yeah. Well, the essential pattern that we observed was that the most effective change leaders out there were building trust and speed, and it didn’t seem to be a well-known observation. We all know the phrase, “Move fast and break things,” but the people who were really getting it right were moving fast and fixing things, and that was really our jumping off point. So when we dug into the pattern, what we observed was they were building trust first and then speed. This foundation of trust was what allowed them to fix more things and break fewer.

CURT NICKISCH: Trust sounds like a slow thing, right? If you talk about building trust, that is something that takes interactions, it takes communication, it takes experiences. Does that run counter to the speed idea?

ANNE MORRISS: Yeah. Well, this issue of trust is something we’ve been looking at for over a decade. One of the headlines in our research is it’s actually something we’re building and rebuilding and breaking all the time. And so instead of being this precious, almost farbege egg, it’s this thing that is constantly in motion and this thing that we can really impact when we’re deliberate about our choices and have some self-awareness around where it’s breaking down and how it’s breaking down.

CURT NICKISCH: You said break trust in there, which is intriguing, right? That you may have to break trust to build trust. Can you explain that a little?

ANNE MORRISS:  Yeah, well, I’ll clarify. It’s not that you have to break it in order to build it. It’s just that we all do it some of the time. Most of us are trusted most of the time. Most of your listeners I imagine are trusted most of the time, but all of us have a pattern where we break trust or where we don’t build as much as could be possible.

CURT NICKISCH: I want to talk about speed, this other essential ingredient that’s so intriguing, right? Because you think about solving hard problems as something that just takes a lot of time and thinking and coordination and planning and designing. Explain what you mean by it? And also, just  how we maybe approach problems wrong by taking them on too slowly?

ANNE MORRISS: Well, Curt, no one has ever said to us, “I wish I had taken longer and done less.” We hear the opposite all the time, by the way. So what we really set out to do was to create a playbook that anyone can use to take less time to do more of the things that are going to make your teams and organizations stronger.

And the way we set up the book is okay, it’s really a five step process. Speed is the last step. It’s the payoff for the hard work you’re going to do to figure out your problem, build or rebuild trust, expand the team in thoughtful and strategic ways, and then tell a real and compelling story about the change you’re leading.

Only then do you get to go fast, but that’s an essential part of the process, and we find that either people under emphasize it or speed has gotten a bad name in this world of moving fast and breaking things. And part of our mission for sure was to rehabilitate speed’s reputation because it is an essential part of the change leader’s equation. It can be the difference between good intentions and getting anything done at all.

CURT NICKISCH: You know, the fact that nobody ever tells you, “I wish we had done less and taken more time.” I think we all feel that, right? Sometimes we do something and then realize, “Oh, that wasn’t that hard and why did it take me so long to do it? And I wish I’d done this a long time ago.” Is it ever possible to solve a problem too quickly?

ANNE MORRISS: Absolutely. And we see that all the time too. What we push people to do in those scenarios is really take a look at the underlying issue because in most cases, the solution is not to take your foot off the accelerator per se and slow down. The solution is to get into the underlying problem. So if it’s burnout or a strategic disconnect between what you’re building and the marketplace you’re serving, what we find is the anxiety that people attach to speed or the frustration people attach to speed is often misplaced.

CURT NICKISCH: What is a good timeline to think about solving a problem then? Because if we by default take too long or else jump ahead and we don’t fix it right, what’s a good target time to have in your mind for how long solving a problem should take?

ANNE MORRISS: Yeah. Well, we’re playful in the book and talking about the idea that many problems can be solved in a week. We set the book up five chapters. They’re titled Monday, Tuesday, Wednesday, Thursday, Friday, and we’re definitely having fun with that. And yet, if you count the hours in a week, there are a lot of them. Many of our problems, if you were to spend a focused 40 hours of effort on a problem, you’re going to get pretty far.

But our main message is, listen, of course it’s going to depend on the nature of the problem, and you’re going to take weeks and maybe even some cases months to get to the other side. What we don’t want you to do is take years, which tends to be our default timeline for solving hard problems.

CURT NICKISCH: So you say to start with identifying the problem that’s holding you back, seems kind of obvious. But where do companies go right and wrong with this first step of just identifying the problem that’s holding you back?

ANNE MORRISS: And our goal is that all of these are going to feel obvious in retrospect. The problem is we skip over a lot of these steps and this is why we wanted to underline them. So this one is really rooted in our observation and I think the pattern of our species that we tend to be overconfident in the quality of our thoughts, particularly when it comes to diagnosing problems.

And so we want to invite you to start in a very humble and curious place, which tends not to be our default mode when we’re showing up for work. We convince ourselves that we’re being paid for our judgment. That’s exactly what gets reinforced everywhere. And so we tend to counterintuitively, given what we just talked about, we tend to move too quickly through the diagnostic phase.

CURT NICKISCH: “I know what to do, that’s why you hired me.”

ANNE MORRISS: Exactly. “I know what to do. That’s why you hired me. I’ve seen this before. I have a plan. Follow me.” We get rewarded for the expression of confidence and clarity. And so what we’re inviting people to do here is actually pause and really lean into what are the root causes of the problem you’re seeing? What are some alternative explanations? Let’s get into dialogue with the people who are also impacted by the problem before we start running down the path of solving it.

CURT NICKISCH: So what do you recommend for this step, for getting to the root of the problem? What are questions you should ask? What’s the right thought process? What do you do on Monday of the week?

ANNE MORRISS: In our experience of doing this work, people tend to undervalue the power of conversation, particularly with other people in the organization. So we will often advocate putting together a team of problem solvers, make it a temporary team, really pull in people who have a particular perspective on the problem and create the space, make it as psychologically safe as you can for people to really, as Chris Argyris so beautifully articulated, discuss the undiscussable.

And so the conditions for that are going to look different in every organization depending on the problem, but if you can get a space where smart people who have direct experience of a problem are in a room and talking honestly with each other, you can make an extraordinary amount of progress, certainly in a day.

CURT NICKISCH: Yeah, that gets back to the trust piece.

ANNE MORRISS: Definitely.

CURT NICKISCH: How do you like to start that meeting, or how do you like to talk about it? I’m just curious what somebody on that team might hear in that meeting, just to get the sense that it’s psychologically safe, you can discuss the undiscussable and you’re also focusing on the identification part. What’s key to communicate there?

ANNE MORRISS: Yeah. Well, we sometimes encourage people to do a little bit of data gathering before those conversations. So the power of a quick anonymous survey around whatever problem you’re solving, but also be really thoughtful about the questions you’re going to ask in the moment. So a little bit of preparation can go a long way and a little bit of thoughtfulness about the power dynamic. So who’s going to walk in there with license to speak and who’s going to hold back? So being thoughtful about the agenda, about the questions you’re asking about the room, about the facilitation, and then courage is a very infectious emotion.

So if you can early on create the conditions for people to show up bravely in that conversation, then the chance that you’re going to get good information and that you’re going to walk out of that room with new insight in the problem that you didn’t have when you walked in is extraordinarily high.

CURT NICKISCH: Now, in those discussions, you may have people who have different perspectives on what the problem really is. They also bear different costs of addressing the problem or solving it. You talked about the power dynamic, but there’s also an unfairness dynamic of who’s going to actually have to do the work to take care of it, and I wonder how you create a culture in that meeting where it’s the most productive?

ANNE MORRISS: For sure, the burden of work is not going to be equitably distributed around the room. But I would say, Curt, the dynamic that we see most often is that people are deeply relieved that hard problems are being addressed. So it really can create, and more often than not in our experience, it does create this beautiful flywheel of action, creativity, optimism. Often when problems haven’t been addressed, there is a fair amount of anxiety in the organization, frustration, stagnation. And so credible movement towards action and progress is often the best antidote. So even if the plan isn’t super clear yet, if it’s credible, given who’s in the room and their decision rights and mandate, if there’s real momentum coming out of that to make progress, then that tends to be deeply energizing to people.

CURT NICKISCH: I wonder if there’s an organization that you’ve worked with that you could talk about how this rolled out and how this took shape?

ANNE MORRISS: When we started working with Uber, that was wrestling with some very public issues of culture and trust with a range of stakeholders internally, the organization, also external, that work really started with a campaign of listening and really trying to understand where trust was breaking down from the perspective of these stakeholders?

So whether it was female employees or regulators or riders who had safety concerns getting into the car with a stranger. This work, it starts with an honest internal dialogue, but often the problem has threads that go external. And so bringing that same commitment to curiosity and humility and dialogue to anyone who’s impacted by the problem is the fastest way to surface what’s really going on.

CURT NICKISCH: There’s a step in this process that you lay out and that’s communicating powerfully as a leader. So we’ve heard about listening and trust building, but now you’re talking about powerful communication. How do you do this and why is it maybe this step in the process rather than the first thing you do or the last thing you do?

ANNE MORRISS: So in our process, again, it’s the days of the week. On Monday you figured out the problem. Tuesday you really got into the sandbox in figuring out what a good enough plan is for building trust. Wednesday, step three, you made it better. You created an even better plan, bringing in new perspectives. Thursday, this fourth step is the day we’re saying you got to go get buy-in. You got to bring other people along. And again, this is a step where we see people often underinvest in the power and payoff of really executing it well.

CURT NICKISCH: How does that go wrong?

ANNE MORRISS: Yeah, people don’t know the why. Human behavior and the change in human behavior really depends on a strong why. It’s not just a selfish, “What’s in it for me?” Although that’s helpful, but where are we going? I may be invested in a status quo and I need to understand, okay, if you’re going to ask me to change, if you’re going to invite me into this uncomfortable place of doing things differently, why am I here? Help me understand it and articulate the way forward and language that not only I can understand, but also that’s going to be motivating to me.

CURT NICKISCH: And who on my team was part of this process and all that kind of stuff?

ANNE MORRISS: Oh, yeah. I may have some really important questions that may be in the way of my buy-in and commitment to this plan. So certainly creating a space where those questions can be addressed is essential. But what we found is that there is an architecture of a great change story, and it starts with honoring the past, honoring the starting place. Sometimes we’re so excited about the change and animated about the change that what has happened before or what is even happening in the present tense is low on our list of priorities.

Or we want to label it bad, because that’s the way we’ve thought about the change, but really pausing and honoring what came before you and all the reasonable decisions that led up to it, I think can be really helpful to getting people emotionally where you want them to be willing to be guided by you. Going back to Uber, when Dara Khosrowshahi came in.

CURT NICKISCH: This is the new CEO.

ANNE MORRISS: The new CEO.

CURT NICKISCH: Replaced Travis Kalanick, the founder and first CEO, yeah.

ANNE MORRISS: Yeah, and had his first all-hands meeting. One of his key messages, and this is a quote, was that he was going to retain the edge that had made Uber, “A force of nature.” And in that meeting, the crowd went wild because this is also a company that had been beaten up publicly for months and months and months, and it was a really powerful choice. And his predecessor, Travis was in the room, and he also honored Travis’ incredible work and investment in bringing the company to the place where it was.

And I would use words like grace to also describe those choices, but there’s also an incredible strategic value to naming the starting place for everybody in the room because in most cases, most people in that room played a role in getting to that starting place, and you’re acknowledging that.

CURT NICKISCH: You can call it grace. Somebody else might call it diplomatic or strategic. But yeah, I guess like it or not, it’s helpful to call out and honor the complexity of the way things have been done and also the change that’s happening.

ANNE MORRISS: Yeah, and the value. Sometimes honoring the past is also owning what didn’t work or what wasn’t working for stakeholders or segments of the employee team, and we see that around culture change. Sometimes you’ve got to acknowledge that it was not an equitable environment, but whatever the worker, everyone in that room is bringing that pass with them. So again, making it discussable and using it as the jumping off place is where we advise people to start.

Then you’ve earned the right to talk about the change mandate, which we suggest using clear and compelling language about the why. “This is what happened, this is where we are, this is the good and the bad of it, and here’s the case for change.”

And then the last part, which is to describe a rigorous and optimistic way forward. It’s a simple past, present, future arc, which will be familiar to human beings. We love stories as human beings. It’s among the most powerful currency we have to make sense of the world.

CURT NICKISCH: Yeah. Chronological is a pretty powerful order.

ANNE MORRISS: Right. But again, the change leaders we see really get it right, are investing an incredible amount of time into the storytelling part of their job. Ursula Burns, the Head of Xerox is famous for the months and years she spent on the road just telling the story of Xerox’s change, its pivot into services to everyone who would listen, and that was a huge part of her success.

CURT NICKISCH: So Friday or your fifth step, you end with empowering teams and removing roadblocks. That seems obvious, but it’s critical. Can you dig into that a little bit?

ANNE MORRISS: Yeah. Friday is the fun day. Friday’s the release of energy into the system. Again, you’ve now earned the right to go fast. You have a plan, you’re pretty confident it’s going to work. You’ve told the story of change the organization, and now you get to sprint. So this is about really executing with urgency, and it’s about a lot of the tactics of speed is where we focus in the book. So the tactics of empowerment, making tough strategic trade-offs so that your priorities are clear and clearly communicated, creating mechanisms to fast-track progress. At Etsy, CEO Josh Silverman, he labeled these projects ambulances. It’s an unfortunate metaphor, but it’s super memorable. These are the products that get to speed out in front of the other ones because the stakes are high and the clock is sticking.

CURT NICKISCH: You pull over and let it go by.

ANNE MORRISS: Yeah, exactly. And so we have to agree as an organization on how to do something like that. And so we see lots of great examples both in young organizations and big complex biotech companies with lots of regulatory guardrails have still found ways to do this gracefully.

And I think we end with this idea of conflict debt, which is a term we really love. Leanne Davey, who’s a team scholar and researcher, and anyone in a tech company will recognize the idea of tech debt, which is this weight the organization drags around until they resolve it. Conflict debt is a beautiful metaphor because it is this weight that we drag around and slows us down until we decide to clean it up and fix it. The organizations that are really getting speed right have figured out either formally or informally, how to create an environment where conflict and disagreements can be gracefully resolved.

CURT NICKISCH: Well, let’s talk about this speed more, right? Because I think this is one of those places that maybe people go wrong or take too long, and then you lose the awareness of the problem, you lose that urgency. And then that also just makes it less effective, right? It’s not just about getting the problem solved as quickly as possible. It’s also just speed in some ways helps solve the problem.

ANNE MORRISS: Oh, yeah. It really is the difference between imagining the change you want to lead and really being able to bring it to life. Speed is the thing that unlocks your ability to lead change. It needs a foundation, and that’s what Monday through Thursday is all about, steps one through four, but the finish line is executing with urgency, and it’s that urgency that releases the system’s energy, that communicates your priorities, that creates the conditions for your team to make progress.

CURT NICKISCH: Moving fast is something that entrepreneurs and tech companies certainly understand, but there’s also this awareness that with big companies, the bigger the organization, the harder it is to turn the aircraft carrier around, right? Is speed relative when you get at those levels, or do you think this is something that any company should be able to apply equally?

ANNE MORRISS: We think this applies to any company. The culture really lives at the level of team. So we believe you can make a tremendous amount of progress even within your circle of control as a team leader. I want to bring some humility to this and careful of words like universal, but we do think there’s some universal truths here around the value of speed, and then some of the byproducts like keeping fantastic people. Your best people want to solve problems, they want to execute, they want to make progress and speed, and the ability to do that is going to be a variable in their own equation of whether they stay or they go somewhere else where they can have an impact.

CURT NICKISCH: Right. They want to accomplish something before they go or before they retire or finish something out. And if you’re able to just bring more things on the horizon and have it not feel like it’s going to be another two years to do something meaningful.

ANNE MORRISS: People – I mean, they want to make stuff happen and they want to be around the energy and the vitality of making things happen, which again, is also a super infectious phenomenon. One of the most important jobs of a leader, we believe, is to set the metabolic pace of their teams and organizations. And so what we really dig into on Friday is, well, what does that look like to speed something up? What are the tactics of that?

CURT NICKISCH: I wonder if that universal truth, that a body in motion stays in motion applies to organizations, right? If an organization in motion stays in motion, there is something to that.

ANNE MORRISS: Absolutely.

CURT NICKISCH: Do you have a favorite client story to share, just where you saw speed just become a bit of a flywheel or just a positive reinforcement loop for more positive change at the organization?

ANNE MORRISS: Yeah. We work with a fair number of organizations that are on fire. We do a fair amount of firefighting, but we also less dramatically do a lot of fire prevention. So we’re brought into organizations that are working well and want to get better, looking out on the horizon. That work is super gratifying, and there is always a component of, well, how do we speed this up?

What I love about that work is there’s often already a high foundation of trust, and so it’s, well, how do we maintain that foundation but move this flywheel, as you said, even faster? And it’s really energizing because often there’s a lot of pent-up energy that… There’s a lot of loyalty to the organization, but often it’s also frustration and pent-up energy. And so when that gets released, when good people get the opportunity to sprint for the first time in a little while, it’s incredibly energizing, not just for us, but for the whole organization.

CURT NICKISCH: Anne, this is great. I think finding a way to solve problems better but also faster is going to be really helpful. So thanks for coming on the show to talk about it.

ANNE MORRISS:  Oh, Curt, it was such a pleasure. This is my favorite conversation. I’m delighted to have it anytime.

HANNAH BATES: That was entrepreneur, leadership coach, and author Anne Morriss – in conversation with Curt Nickisch on HBR IdeaCast.

We’ll be back next Wednesday with another hand-picked conversation about business strategy from Harvard Business Review. If you found this episode helpful, share it with your friends and colleagues, and follow our show on Apple Podcasts, Spotify, or wherever you get your podcasts. While you’re there, be sure to leave us a review.

When you’re ready for more podcasts, articles, case studies, books, and videos with the world’s top business and management experts, you’ll find it all at HBR.org.

This episode was produced by Mary Dooe, Anne Saini, and me, Hannah Bates. Ian Fox is our editor. Special thanks to Rob Eckhardt, Maureen Hoch, Erica Truxler, Ramsey Khabbaz, Nicole Smith, Anne Bartholomew, and you – our listener. See you next week.

• Subscribe On:

Latest in this series

This article is about strategy.

• Decision making and problem solving
• Strategy execution
• Leadership and managing people
• Collaboration and teams
• Trustworthiness
• Organizational culture

Partner Center

Product Thinking: Definition, Process, and Practicing Tools

10 min read

Product thinking is all about putting yourself in the other person’s (user) shoes. What do they want or need? Do they like certain colors? What makes them happy? How could you make their life easier?

Only by adopting a product-thinking mindset and following it as a process can you get to know your users better.

In this article, we cover the basics of product thinking: What it is, how to adopt it, and how to bring it to life to drive product-led growth . Let’s get started.

• Product thinking is the process of identifying problems and coming up with solutions by placing the user in the center. This practice also invites you to think of your business goals and current technology limitations.
• It’s crucial to install a product-thinking mindset in your business to influence design thinking. It also allows you to create user-centric designs, foster agile iteration, promote scalability, and enable continuous product learning.
• The process of product thinking starts by defining the problem. Then, you need to identify market opportunities, correlate them with business goals, and ideate possible solutions.
• To leverage product thinking in product development , you can:
• Conduct user research to understand their needs, through feedback surveys , interviews, and social listening.
• Identify and assess market opportunities, by researching market gaps and trends to tailor profitable products.
• Decide solutions and start building, start by developing an MVP to test early and iterate based on feedback.
• Undertake strategic planning and allocation of resources, and align them with business goals.
• Collect data for analytics, such as behavioral and sentiment data, to improve the product.
• Continuously iterate your product based on findings, by regularly refining the product based on user feedback.
• Use these problem space tools to practice a product thinking mindset:
• 5W1H. Ask who, what, when, where, why, and how to identify problems.
• The Mom Test . Conduct unbiased interviews to gain genuine user insights.
• Jobs-to-be-done framework. Identify and address user tasks and goals through interviews and surveys.
• Check out these solution space tools for product thinking:
• User stories . Share your user needs and desired outcomes in a structured story.
• Problem-solving methods. Explore approaches like minimizing, maximizing, transforming, combining, modifying, and substituting features.
• Value proposition canvas. Align your solution with customer values and needs by mapping out customer profiles and creating product value .
• Add native-feel product interventions and track their performance in the same place with Userpilot. Iterate and make changes as you go to drive product-led growth. Get a demo .

Try Userpilot and Take Your Product-Led Growth to the Next Level

• 14 Day Trial
• No Credit Card Required

What is product thinking?

Product thinking is the continuous process of identifying customer problems and finding solutions that make sense to them and the business. All, by having a strong understanding of your current technology limitations.

Why do product thinking skills matter?

Product thinking skills are important because they influence the product team’s decisions. Strong product thinking skills lead to:

• User-centric designs. When you adopt a product-thinking mindset, you can build experiences (UX) that serve user needs. This transforms product growth into product-led growth .
• Agile iteration and continuous discovery. For the user to have the last word, you need to test your product with real people, make changes based on their feedback, and test again. A product thinking approach supports (and understands) the need for multiple iterations.
• Scalability and sustainable product growth. Product thinking brings the user, the business, and the technology together. This means your developers also need to work alongside other departments. When teams work together and not in silos, you can better prepare for potential future scenarios.
• Continuous product learning. The more you test your existing solution, the more you get to know how your users interact with and what they value about your product. This form of continuous learning is a competitive advantage and can lead to sustained product-led growth.

What is the product thinking process?

Providing a good user experience will inevitably lead to higher retention, but you might not always have the money or software infrastructure to make user ideas come to life. This is why you need to establish an internal product thinking process.

Here’s what a product thinking process can look like:

• Define problems. Run user persona surveys or implement a jobs-to-be-done template to spot your current issues. Determine exactly what’s causing your users and your business to struggle, e.g., low conversion rates despite a large and steady organic traffic base.
• Identify opportunities. Then, measure the size of the opportunity, potential ROI, market opportunity, and possible market share gain. For instance, imagine your average order value (AOV) per customer is $70, and have a monthly traffic of 10,000 people. If you can take your conversion rate from 2% to 7%, you could increase your monthly income by $35,000.
• Correlate with business goals. Once you’ve calculated the opportunity size, determine how relevant this problem is to your business. Using the previous example, we can all agree the problem is critical to the business. Not knowing why customers aren’t converting could cause you to leave at least $35,000 on the table every month.
• Find a solution. Use solution space frameworks to present potential solutions and let the product managers and developers decide what to do based on your budget and current infrastructure. Build prototypes to test ideas and hypotheses and launch a beta version to collect more feedback. Keep iterating until you find the right solution.

How to leverage product thinking in product development?

When you make product thinking part of product development, you build more user-centric products. You can do this by following these six generic proven models:

1. Conduct user research to understand their needs

Product thinking is all about putting the user at the center. So, launch feedback surveys, conduct interviews or focus groups, do social listening, or build a voice of the customer map to define their needs.

The goal of user research is to define exactly what they need from a product like yours. You can also determine what day-to-day life needs your product can potentially solve.

Here’s an example of a user research survey that you can build using Userpilot:

2. Identify and assess market opportunities

As mentioned above, you must research market opportunities and correlate them with the benefits for your business. Running a product market fit analysis and conducting market research allow you to build products that solve user problems and make a profit.

The better you can identify gaps, trends, and areas of opportunity within your target market, the more tailored products you’ll be able to develop—and the more profit you’ll make.

3. Decide solutions and start building

Ideate and find problem solutions alongside your users. Conduct concept testing before settling on a solution. Once you find a problem solution fit, build an MVP with minimum viable features for users to interact with.

Test early and often so designers can get feedback they can build into the product. Continuous testing and editing of your product based on real user insights is one way to ensure your solution’s success.

4. Undertake strategic planning and allocation of resources

Your business resources are limited, use them efficiently. Achieve proper resource allocation through strategic planning and defining a product roadmap that outlines your product vision. Make sure this roadmap is linked to bigger business goals.

For example, if your designers are working on a new feature, take that into account before assigning them more work. Proper resource allocation leads to better results and a more stable business.

5. Collect data for analytics

Test your product before, during, and after development to collect user behavioral and sentiment data. You can use a tool like Userpilot to collect event-tracking data, user behavior tracking , and survey analytics of in-app interventions. Analyze the results and make plans to iterate on the same product idea until you get favorable results.

6. Continuously iterate your product based on findings

Lastly, and throughout the product lifecycle, iterate on your product based on an analysis of user feedback .

The faster you can act upon user feedback and improve your product, the closer you get to increased customer satisfaction.

For example, using NPS response tags in Userpilot, you can quickly identify common issues among your NPS detractors and set guidelines to build better products.

Problem space tools to practice product thinking mindset

Here are problem space tools to dive deep into your business and users’ problems and make product thinking come to life:

1. The 5W1H approach to identify the underlying problems

This tool invites you to ask questions that dig into your tangible issues to identify the real or hidden problems.

Imagine your problem is that you’re the CEO of a content marketing agency with a low client retention rate using this tool.

• What is the problem? The agency has a great sales team, so it’s easy to close deals, but the client-facing team is disorganized and late.
• Who is experiencing the problem? Clients. They’re not feeling satisfied with the service, so they churn fast.
• Where does the problem happen? At the editing stage. Editors are scheduled to edit the pieces after the client meeting. The work is usually late.
• Why is this problem happening? Because the project managers have too many responsibilities.
• When does the problem usually occur? At the end of the three-month mark.
• How to approach this problem? Hire more project managers or allow writers and editors to set deadlines for themselves.

2. The Mom Test to collect insights

The Mom Test is a problem space tool for having conversations and asking questions to gain genuine user insights.

Ask questions about past behaviors, specific cases, concrete details, unbiased questions, general user behavior, and recent experience. For example:

• What motivated you to start using [product/service]?
• What goals or objectives are you trying to achieve by using [product/service]?
• Can you tell me about the last time you [performed X action]?
• How many apps do you use daily to achieve [X goal]?

3. The jobs-to-be-done framework to determine user needs

The JTBD framework proposes that people are willing to purchase a license or a product if it allows them to complete a certain job.

JTBD in product management implies that users can view jobs as activities or as progress, i.e., your product/service can help them perform certain tasks or improve their lives.

To identify the problem space using this framework, you can conduct micro surveys or interviews. Analyze the answers, create a job map, and determine which jobs you’ll address with your product.

Solution space tools to practice product thinking

After you’ve identified the problem, it’s time to think of ways to solve it. These solution space tools propose different problem-solving techniques that place the user at the center.

1. Create user stories

User stories are a powerful way of identifying and communicating customer needs and requirements. The idea is to write a paragraph that tells a story about who the user is and what they want. The product team is the one to determine how to solve the problem based on other testing methods.

Every user story should contain three elements: Persona, action, and outcome.

For example, as a project manager , I want to be able to assign deadlines to tasks in bulk so that I can reduce mistakes and use my time in strategic allocation planning.

2. Leverage problem-solving methods

This solution space tool invites you to think of different ways to solve a problem based on your several existing solutions. For example:

• Minimize your offer by reducing the scope, e.g., YouTube vs. Coursera.
• Maximize your product by adding more functionality to an existing solution, e.g., your phone’s note app vs. Notion.
• Transform your tool by offering multiple separate solutions, e.g., Uber and Uber Eats.
• Combine two or more existing solutions into one, e.g., WhatsApp (messaging, calling, video calling). This is only recommended for products getting to advanced growth stages instead of first-release ones.
• Modify or rearrange your tool by revamping and improving a current product, e.g., your phone reminders into Doist.
• Substitute one part of a current solution, e.g., Readers (you could do this from your phone or laptop).

3. Use value proposition canvas

A value proposition canvas is a tool for positioning a product/service around the customer’s values and needs.

The canvas is usually divided into two parts: the customer profile and the value map.

The customer profile includes the different jobs they want to address and their pains and gains. The value map, on the other hand, focuses on how the business can create value for the customer.

Embracing product thinking leads to better product management and more satisfied users. Do this by implementing and following the product thinking process.

You can also use problem and solution space tools to identify the root cause of your users’ struggles and ideate creative ways to solve them.

If you want to leverage product-led growth, try Userpilot. Here, you’ll be able to conduct user research, add in-app interventions, and keep track of your user feedback, all in one place. Get a demo .

Leave a comment Cancel reply

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

Get The Insights!

The fastest way to learn about Product Growth,Management & Trends.

The coolest way to learn about Product Growth, Management & Trends. Delivered fresh to your inbox, weekly.

The fastest way to learn about Product Growth, Management & Trends.

You might also be interested in ...

Explained: Importance of critical thinking, problem-solving skills in curriculum

F uture careers are no longer about domain expertise or technical skills. Rather, critical thinking and problem-solving skills in employees are on the wish list of every big organization today. Even curriculums and pedagogies across the globe and within India are now requiring skilled workers who are able to think critically and are analytical.

The reason for this shift in perspective is very simple.

These skills provide a staunch foundation for comprehensive learning that extends beyond books or the four walls of the classroom. In a nutshell, critical thinking and problem-solving skills are a part of '21st Century Skills' that can help unlock valuable learning for life.

Over the years, the education system has been moving away from the system of rote and other conventional teaching and learning parameters.

They are aligning their curriculums to the changing scenario which is becoming more tech-driven and demands a fusion of critical skills, life skills, values, and domain expertise. There's no set formula for success.

Rather, there's a defined need for humans to be more creative, innovative, adaptive, agile, risk-taking, and have a problem-solving mindset.

In today's scenario, critical thinking and problem-solving skills have become more important because they open the human mind to multiple possibilities, solutions, and a mindset that is interdisciplinary in nature.

Therefore, many schools and educational institutions are deploying AI and immersive learning experiences via gaming, and AR-VR technologies to give a more realistic and hands-on learning experience to their students that hone these abilities and help them overcome any doubt or fear.

ADVANTAGES OF CRITICAL THINKING AND PROBLEM-SOLVING IN CURRICULUM

Ability to relate to the real world:  Instead of theoretical knowledge, critical thinking, and problem-solving skills encourage students to look at their immediate and extended environment through a spirit of questioning, curiosity, and learning. When the curriculum presents students with real-world problems, the learning is immense.

Confidence, agility & collaboration : Critical thinking and problem-solving skills boost self-belief and confidence as students examine, re-examine, and sometimes fail or succeed while attempting to do something.

They are able to understand where they may have gone wrong, attempt new approaches, ask their peers for feedback and even seek their opinion, work together as a team, and learn to face any challenge by responding to it.

Willingness to try new things: When problem-solving skills and critical thinking are encouraged by teachers, they set a robust foundation for young learners to experiment, think out of the box, and be more innovative and creative besides looking for new ways to upskill.

It's important to understand that merely introducing these skills into the curriculum is not enough. Schools and educational institutions must have upskilling workshops and conduct special training for teachers so as to ensure that they are skilled and familiarized with new teaching and learning techniques and new-age concepts that can be used in the classrooms via assignments and projects.

Critical thinking and problem-solving skills are two of the most sought-after skills. Hence, schools should emphasise the upskilling of students as a part of the academic curriculum.

The article is authored by Dr Tassos Anastasiades, Principal- IB, Genesis Global School, Noida. 

Watch Live TV in English

Watch Live TV in Hindi

Follow Polygon online:

• Follow Polygon on Facebook
• Follow Polygon on Youtube
• Follow Polygon on Instagram

Site search

• Dragon’s Dogma 2
• Ghost of Tsushima
• Zelda: Tears of the Kingdom
• Baldur’s Gate 3
• GTA 5 cheats
• PlayStation
• Dungeons & Dragons
• Magic: The Gathering
• Board Games
• All Tabletop
• All Entertainment
• What to Watch
• What to Play
• Buyer’s Guides
• Really Bad Chess
• All Puzzles

Filed under:

• Entertainment

The 3-body problem is real, and it’s really unsolvable

Oh god don’t make me explain math

Share this story

• Share this on Facebook
• Share this on Reddit
• Share All sharing options

Share All sharing options for: The 3-body problem is real, and it’s really unsolvable

Everybody seems to be talking about 3 Body Problem , the new Netflix series based on Cixin Liu’s Remembrance of Earth’s Past book trilogy . Fewer people are talking about the two series’ namesake: The unsolvable physics problem of the same name.

This makes sense, because it’s confusing . In physics, the three-body problem attempts to find a way to predict the movements of three objects whose gravity interacts with each of the others — like three stars that are close together in space. Sounds simple enough, right? Yet I myself recently pulled up the Wikipedia article on the three-body problem and closed the tab in the same manner that a person might stagger away from a bright light. Apparently the Earth, sun, and moon are a three-body system? Are you telling me we don’t know how the moon moves ? Scientists have published multiple solutions for the three-body problem? Are you telling me Cixin Liu’s books are out of date?

All I’d wanted to know was why the problem was considered unsolvable, and now memories of my one semester of high school physics were swimming before my eyes like so many glowing doom numbers. However, despite my pains, I have readied several ways that we non-physicists can be confident that the three-body problem is, in fact, unsolvable.

Reason 1: This is a special definition of ‘unsolvable’

The three-body problem is extra confusing, because scientists are seemingly constantly finding new solutions to the three-body problem! They just don’t mean a one-solution-for-all solution. Such a formula does exist for a two-body system, and apparently Isaac Newton figured it out in 1687 . But systems with more than two bodies are, according to physicists, too chaotic (i.e., not in the sense of a child’s messy bedroom, but in the sense of “chaos theory”) to be corralled by a single solution.

When physicists say they have a new solution to the three-body problem, they mean that they’ve found a specific solution for three-body systems that have certain theoretical parameters. Don’t ask me to explain those parameters, because they’re all things like “the three masses are collinear at each instant” or “a zero angular momentum solution with three equal masses moving around a figure-eight shape.” But basically: By narrowing the focus of the problem to certain arrangements of three-body systems, physicists have been able to derive formulas that predict the movements of some of them, like in our solar system. The mass of the Earth and the sun create a “ restricted three-body problem ,” where a less-big body (in this case, the moon) moves under the influence of two massive ones (the Earth and the sun).

What physicists mean when they say the three-body problem has no solution is simply that there isn’t a one-formula-fits-all solution to every way that the gravity of three objects might cause those objects to move — which is exactly what Three-Body Problem bases its whole premise on.

Reason 2: 3 Body Problem picked an unsolved three-body system on purpose

Henri Poincaré’s research into a general solution to the three-body problem formed the basis of what would become known as chaos theory (you might know it from its co-starring role in Jurassic Park ). And 3 Body Problem itself isn’t about any old three-body system. It’s specifically about an extremely chaotic three-body system, the exact kind of arrangement of bodies that Poincaré was focused on when he showed that the problem is “unsolvable.”

[ Ed. note: The rest of this section includes some spoilers for 3 Body Problem .]

In both Liu’s books and Netflix’s 3 Body Problem , humanity faces an invasion by aliens (called Trisolarans in the English translation of the books, and San-Ti in the TV series) whose home solar system features three suns in a chaotic three-body relationship. It is a world where, unlike ours, the heavens are fundamentally unpredictable. Periods of icy cold give way to searing heat that give way to swings in gravity that turn into temporary reprieves that can never be trusted. The unpredictable nature of the San-Ti environment is the source of every detail of their physicality, their philosophy, and their desire to claim Earth for their own.

In other words, 3 Body Problem ’s three-body problem is unsolvable because Liu wanted to write a story with an unsolvable three-body system, so he chose one of the three-body systems for which we have not discovered a solution, and might never.

Reason 3: Scientists are still working on the three-body problem

Perhaps the best reason I can give you to believe that the three-body problem is real, and is really unsolvable, is that some scientists published a whole set of new solutions for specific three-body systems very recently .

If physicists are still working on the three-body problem, we can safely assume that it has not been solved. Scientists, after all, are the real experts. And I am definitely not.

The next level of puzzles.

Take a break from your day by playing a puzzle or two! We’ve got SpellTower, Typeshift, crosswords, and more.

Sign up for the newsletter Patch Notes

A weekly roundup of the best things from Polygon

Just one more thing!

Please check your email to find a confirmation email, and follow the steps to confirm your humanity.

Oops. Something went wrong. Please enter a valid email and try again.

Loading comments...

What time does Modern Warfare 3 season 4 release?

Polygon’s most anticipated, least expected, 2024 summer preview

Read this or you’ll miss it!

• The 2024 summer preview

Can Lev Grossman do for King Arthur what he did for Harry Potter?

Kill is the brutal thriller that action buffs shouldn’t overlook this summer

When will Furiosa come to streaming?

Dune 2, The Fall Guy, Netflix’s Atlas, and every movie new to streaming this week