the problem to solve

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

Problem-Solving Strategies and Obstacles

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

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

JGI / Jamie Grill / Getty Images

• Application
• Improvement

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

What Is Problem-Solving?

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

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

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

The problem-solving process involves:

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

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

Problem-Solving Mental Processes

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

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

Problem-Solving Strategies

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

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

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

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

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

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

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

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

Trial and Error

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

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

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

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

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

How to Apply Problem-Solving Strategies in Real Life

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

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

Obstacles to Problem-Solving

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

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

How to Improve Your Problem-Solving Skills

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

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

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

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

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

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

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

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

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

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

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

National Alliance on Mental Illness. Warning signs and symptoms .

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

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

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

How it works

For Business

Join Mind Tools

Article • 7 min read

What Is Problem Solving?

By the Mind Tools Content Team

We all spend a lot of our time solving problems, both at work and in our personal lives.

Some problems are small, and we can quickly sort them out ourselves. But others are complex challenges that take collaboration, creativity, and a considerable amount of effort to solve.

At work, the types of problems we face depend largely on the organizations we're in and the jobs we do. A manager in a cleaning company, for example, might spend their day untangling staffing issues, resolving client complaints, and sorting out problems with equipment and supplies. An aircraft designer, on the other hand, might be grappling with a problem about aerodynamics, or trying to work out why a new safety feature isn't working. Meanwhile, a politician might be exploring solutions to racial injustice or climate change.

But whatever issues we face, there are some common ways to tackle them effectively. And we can all boost our confidence and ability to succeed by building a strong set of problem-solving skills.

Mind Tools offers a large collection of resources to help you do just that!

How Well Do You Solve Problems?

Start by taking an honest look at your existing skills. What's your current approach to solving problems, and how well is it working? Our quiz, How Good Is Your Problem Solving? lets you analyze your abilities, and signposts ways to address any areas of weakness.

Define Every Problem

The first step in solving a problem is understanding what that problem actually is. You need to be sure that you're dealing with the real problem – not its symptoms. For example, if performance in your department is substandard, you might think that the problem lies with the individuals submitting work. However, if you look a bit deeper, the real issue might be a general lack of training, or an unreasonable workload across the team.

Tools like 5 Whys , Appreciation and Root Cause Analysis get you asking the right questions, and help you to work through the layers of a problem to uncover what's really going on.

However, defining a problem doesn't mean deciding how to solve it straightaway. It's important to look at the issue from a variety of perspectives. If you commit yourself too early, you can end up with a short-sighted solution. The CATWOE checklist provides a powerful reminder to look at many elements that may contribute to the problem, keeping you open to a variety of possible solutions.

Understanding Complexity

As you define your problem, you'll often discover just how complicated it is. There are likely several interrelated issues involved. That's why it's important to have ways to visualize, simplify and make sense of this tangled mess!

Affinity Diagrams are great for organizing many different pieces of information into common themes, and for understanding the relationships between them.

Another popular tool is the Cause-and-Effect Diagram . To generate viable solutions, you need a solid understanding of what's causing the problem.

When your problem occurs within a business process, creating a Flow Chart , Swim Lane Diagram or a Systems Diagram will help you to see how various activities and inputs fit together. This may well highlight a missing element or bottleneck that's causing your problem.

Quite often, what seems to be a single problem turns out to be a whole series of problems. The Drill Down technique prompts you to split your problem into smaller, more manageable parts.

General Problem-Solving Tools

When you understand the problem in front of you, you’re ready to start solving it. With your definition to guide you, you can generate several possible solutions, choose the best one, then put it into action. That's the four-step approach at the heart of good problem solving.

There are various problem-solving styles to use. For example:

• Constructive Controversy is a way of widening perspectives and energizing discussions.
• Inductive Reasoning makes the most of people’s experiences and know-how, and can speed up solution finding.
• Means-End Analysis can bring extra clarity to your thinking, and kick-start the process of implementing solutions.

Specific Problem-Solving Systems

Some particularly complicated or important problems call for a more comprehensive process. Again, Mind Tools has a range of approaches to try, including:

• Simplex , which involves an eight-stage process: problem finding, fact finding, defining the problem, idea finding, selecting and evaluating, planning, selling the idea, and acting. These steps build upon the basic, four-step process described above, and they create a cycle of problem finding and solving that will continually improve your organization.
• Appreciative Inquiry , which is a uniquely positive way of solving problems by examining what's working well in the areas surrounding them.
• Soft Systems Methodology , which takes you through four stages to uncover more details about what's creating your problem, and then define actions that will improve the situation.

Further Problem-Solving Strategies

Good problem solving requires a number of other skills – all of which are covered by Mind Tools.

For example, we have a large section of resources to improve your Creativity , so that you come up with a range of possible solutions.

By strengthening your Decision Making , you'll be better at evaluating the options, selecting the best ones, then choosing how to implement them.

And our Project Management collection has valuable advice for strengthening the whole problem-solving process. The resources there will help you to make effective changes – and then keep them working long term.

Problems are an inescapable part of life, both in and out of work. So we can all benefit from having strong problem-solving skills.

It's important to understand your current approach to problem solving, and to know where and how to improve.

Define every problem you encounter – and understand its complexity, rather than trying to solve it too soon.

There's a range of general problem-solving approaches, helping you to generate possible answers, choose the best ones, and then implement your solution.

Some complicated or serious problems require more specific problem-solving systems, especially when they relate to business processes.

By boosting your creativity, decision-making and project-management skills, you’ll become even better at solving all the problems you face.

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Book Insights

The Back of the Napkin: Solving Problems and Selling Ideas With Pictures

Infographic

Creative Problem Solving Infographic

Infographic Transcript

Add comment

Comments (0)

Be the first to comment!

Team Management

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

Sign-up to our newsletter

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

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Newest Releases

Connecting Remote and Hybrid Workers to Organizational Mission

Pain Points Podcast - Building Trust

Mind Tools Store

About Mind Tools Content

Discover something new today

Toxic leadership test.

Use this exercise to assess if a manager or leader is showing signs of toxic behaviour. No separate facilitator guidance is necessary.

Pain Points Podcast - Receiving Feedback

Accepting What Others Say About You

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

Designing future-state customer journeys.

Planning the Ideal Experience for Your Customers

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

Introduction to Problem Solving Skills

What is problem solving and why is it important.

The ability to solve problems is a basic life skill and is essential to our day-to-day lives, at home, at school, and at work. We solve problems every day without really thinking about how we solve them. For example: it’s raining and you need to go to the store. What do you do? There are lots of possible solutions. Take your umbrella and walk. If you don't want to get wet, you can drive, or take the bus. You might decide to call a friend for a ride, or you might decide to go to the store another day. There is no right way to solve this problem and different people will solve it differently.

Problem solving is the process of identifying a problem, developing possible solution paths, and taking the appropriate course of action.

Why is problem solving important? Good problem solving skills empower you not only in your personal life but are critical in your professional life. In the current fast-changing global economy, employers often identify everyday problem solving as crucial to the success of their organizations. For employees, problem solving can be used to develop practical and creative solutions, and to show independence and initiative to employers.

Throughout this case study you will be asked to jot down your thoughts in idea logs. These idea logs are used for reflection on concepts and for answering short questions. When you click on the "Next" button, your responses will be saved for that page. If you happen to close the webpage, you will lose your work on the page you were on, but previous pages will be saved. At the end of the case study, click on the "Finish and Export to PDF" button to acknowledge completion of the case study and receive a PDF document of your idea logs.

What Does Problem Solving Look Like?

The ability to solve problems is a skill, and just like any other skill, the more you practice, the better you get. So how exactly do you practice problem solving? Learning about different problem solving strategies and when to use them will give you a good start. Problem solving is a process. Most strategies provide steps that help you identify the problem and choose the best solution. There are two basic types of strategies: algorithmic and heuristic.

Algorithmic strategies are traditional step-by-step guides to solving problems. They are great for solving math problems (in algebra: multiply and divide, then add or subtract) or for helping us remember the correct order of things (a mnemonic such as “Spring Forward, Fall Back” to remember which way the clock changes for daylight saving time, or “Righty Tighty, Lefty Loosey” to remember what direction to turn bolts and screws). Algorithms are best when there is a single path to the correct solution.

But what do you do when there is no single solution for your problem? Heuristic methods are general guides used to identify possible solutions. A popular one that is easy to remember is IDEAL [ Bransford & Stein, 1993 ] :

• I dentify the problem
• D efine the context of the problem
• E xplore possible strategies
• A ct on best solution

IDEAL is just one problem solving strategy. Building a toolbox of problem solving strategies will improve your problem solving skills. With practice, you will be able to recognize and use multiple strategies to solve complex problems.

Watch the video

What is the best way to get a peanut out of a tube that cannot be moved? Watch a chimpanzee solve this problem in the video below [ Geert Stienissen, 2010 ].

[PDF transcript]

Describe the series of steps you think the chimpanzee used to solve this problem.

• [Page 2: What does Problem Solving Look Like?] Describe the series of steps you think the chimpanzee used to solve this problem.

Think of an everyday problem you've encountered recently and describe your steps for solving it.

• [Page 2: What does Problem Solving Look Like?] Think of an everyday problem you've encountered recently and describe your steps for solving it.

Developing Problem Solving Processes

Problem solving is a process that uses steps to solve problems. But what does that really mean? Let's break it down and start building our toolbox of problem solving strategies.

What is the first step of solving any problem? The first step is to recognize that there is a problem and identify the right cause of the problem. This may sound obvious, but similar problems can arise from different events, and the real issue may not always be apparent. To really solve the problem, it's important to find out what started it all. This is called identifying the root cause .

Example: You and your classmates have been working long hours on a project in the school's workshop. The next afternoon, you try to use your student ID card to access the workshop, but discover that your magnetic strip has been demagnetized. Since the card was a couple of years old, you chalk it up to wear and tear and get a new ID card. Later that same week you learn that several of your classmates had the same problem! After a little investigation, you discover that a strong magnet was stored underneath a workbench in the workshop. The magnet was the root cause of the demagnetized student ID cards.

The best way to identify the root cause of the problem is to ask questions and gather information. If you have a vague problem, investigating facts is more productive than guessing a solution. Ask yourself questions about the problem. What do you know about the problem? What do you not know? When was the last time it worked correctly? What has changed since then? Can you diagram the process into separate steps? Where in the process is the problem occurring? Be curious, ask questions, gather facts, and make logical deductions rather than assumptions.

Watch Adam Savage from Mythbusters, describe his problem solving process [ ForaTv, 2010 ]. As you watch this section of the video, try to identify the questions he asks and the different strategies he uses.

Adam Savage shared many of his problem solving processes. List the ones you think are the five most important. Your list may be different from other people in your class—that's ok!

• [Page 3: Developing Problem Solving Processes] Adam Savage shared many of his problem solving processes. List the ones you think are the five most important.

“The ability to ask the right question is more than half the battle of finding the answer.” — Thomas J. Watson , founder of IBM

Voices From the Field: Solving Problems

In manufacturing facilities and machine shops, everyone on the floor is expected to know how to identify problems and find solutions. Today's employers look for the following skills in new employees: to analyze a problem logically, formulate a solution, and effectively communicate with others.

In this video, industry professionals share their own problem solving processes, the problem solving expectations of their employees, and an example of how a problem was solved.

Meet the Partners:

• Taconic High School in Pittsfield, Massachusetts, is a comprehensive, fully accredited high school with special programs in Health Technology, Manufacturing Technology, and Work-Based Learning.
• Berkshire Community College in Pittsfield, Massachusetts, prepares its students with applied manufacturing technical skills, providing hands-on experience at industrial laboratories and manufacturing facilities, and instructing them in current technologies.
• H.C. Starck in Newton, Massachusetts, specializes in processing and manufacturing technology metals, such as tungsten, niobium, and tantalum. In almost 100 years of experience, they hold over 900 patents, and continue to innovate and develop new products.
• Nypro Healthcare in Devens, Massachusetts, specializes in precision injection-molded healthcare products. They are committed to good manufacturing processes including lean manufacturing and process validation.

Making Decisions

Now that you have a couple problem solving strategies in your toolbox, let's practice. In this exercise, you are given a scenario and you will be asked to decide what steps you would take to identify and solve the problem.

Scenario: You are a new employee and have just finished your training. As your first project, you have been assigned the milling of several additional components for a regular customer. Together, you and your trainer, Bill, set up for the first run. Checking your paperwork, you gather the tools and materials on the list. As you are mounting the materials on the table, you notice that you didn't grab everything and hurriedly grab a few more items from one of the bins. Once the material is secured on the CNC table, you load tools into the tool carousel in the order listed on the tool list and set the fixture offsets.

Bill tells you that since this is a rerun of a job several weeks ago, the CAD/CAM model has already been converted to CNC G-code. Bill helps you download the code to the CNC machine. He gives you the go-ahead and leaves to check on another employee. You decide to start your first run.

What problems did you observe in the video?

• [Page 5: Making Decisions] What problems did you observe in the video?
• What do you do next?
• Try to fix it yourself.
• Ask your trainer for help.

As you are cleaning up, you think about what happened and wonder why it happened. You try to create a mental picture of what happened. You are not exactly sure what the end mill hit, but it looked like it might have hit the dowel pin. You wonder if you grabbed the correct dowel pins from the bins earlier.

You can think of two possible next steps. You can recheck the dowel pin length to make sure it is the correct length, or do a dry run using the CNC single step or single block function with the spindle empty to determine what actually happened.

• Check the dowel pins.
• Use the single step/single block function to determine what happened.

You notice that your trainer, Bill, is still on the floor and decide to ask him for help. You describe the problem to him. Bill asks if you know what the end mill ran into. You explain that you are not sure but you think it was the dowel pin. Bill reminds you that it is important to understand what happened so you can fix the correct problem. He suggests that you start all over again and begin with a dry run using the single step/single block function, with the spindle empty, to determine what it hit. Or, since it happened at the end, he mentions that you can also check the G-code to make sure the Z-axis is raised before returning to the home position.

• Run the single step/single block function.
• Edit the G-code to raise the Z-axis.

You finish cleaning up and check the CNC for any damage. Luckily, everything looks good. You check your paperwork and gather the components and materials again. You look at the dowel pins you used earlier, and discover that they are not the right length. As you go to grab the correct dowel pins, you have to search though several bins. For the first time, you are aware of the mess - it looks like the dowel pins and other items have not been put into the correctly labeled bins. You spend 30 minutes straightening up the bins and looking for the correct dowel pins.

Finally finding them, you finish setting up. You load tools into the tool carousel in the order listed on the tool list and set the fixture offsets. Just to make sure, you use the CNC single step/single block function, to do a dry run of the part. Everything looks good! You are ready to create your first part. The first component is done, and, as you admire your success, you notice that the part feels hotter than it should.

You wonder why? You go over the steps of the process to mentally figure out what could be causing the residual heat. You wonder if there is a problem with the CNC's coolant system or if the problem is in the G-code.

• Look at the G-code.

After thinking about the problem, you decide that maybe there's something wrong with the setup. First, you clean up the damaged materials and remove the broken tool. You check the CNC machine carefully for any damage. Luckily, everything looks good. It is time to start over again from the beginning.

You again check your paperwork and gather the tools and materials on the setup sheet. After securing the new materials, you use the CNC single step/single block function with the spindle empty, to do a dry run of the part. You watch carefully to see if you can figure out what happened. It looks to you like the spindle barely misses hitting the dowel pin. You determine that the end mill was broken when it hit the dowel pin while returning to the start position.

After conducting a dry run using the single step/single block function, you determine that the end mill was damaged when it hit the dowel pin on its return to the home position. You discuss your options with Bill. Together, you decide the best thing to do would be to edit the G-code and raise the Z-axis before returning to home. You open the CNC control program and edit the G-code. Just to make sure, you use the CNC single step/single block function, to do another dry run of the part. You are ready to create your first part. It works. You first part is completed. Only four more to go.

As you are cleaning up, you notice that the components are hotter than you expect and the end mill looks more worn than it should be. It dawns on you that while you were milling the component, the coolant didn't turn on. You wonder if it is a software problem in the G-code or hardware problem with the CNC machine.

It's the end of the day and you decide to finish the rest of the components in the morning.

• You decide to look at the G-code in the morning.
• You leave a note on the machine, just in case.

You decide that the best thing to do would be to edit the G-code and raise the Z-axis of the spindle before it returns to home. You open the CNC control program and edit the G-code.

While editing the G-code to raise the Z-axis, you notice that the coolant is turned off at the beginning of the code and at the end of the code. The coolant command error caught your attention because your coworker, Mark, mentioned having a similar issue during lunch. You change the coolant command to turn the mist on.

• You decide to talk with your supervisor.
• You discuss what happened with a coworker over lunch.

As you reflect on the residual heat problem, you think about the machining process and the factors that could have caused the issue. You try to think of anything and everything that could be causing the issue. Are you using the correct tool for the specified material? Are you using the specified material? Is it running at the correct speed? Is there enough coolant? Are there chips getting in the way?

Wait, was the coolant turned on? As you replay what happened in your mind, you wonder why the coolant wasn't turned on. You decide to look at the G-code to find out what is going on.

From the milling machine computer, you open the CNC G-code. You notice that there are no coolant commands. You add them in and on the next run, the coolant mist turns on and the residual heat issues is gone. Now, its on to creating the rest of the parts.

Have you ever used brainstorming to solve a problem? Chances are, you've probably have, even if you didn't realize it.

You notice that your trainer, Bill, is on the floor and decide to ask him for help. You describe the problem with the end mill breaking, and how you discovered that items are not being returned to the correctly labeled bins. You think this caused you to grab the incorrect length dowel pins on your first run. You have sorted the bins and hope that the mess problem is fixed. You then go on to tell Bill about the residual heat issue with the completed part.

Together, you go to the milling machine. Bill shows you how to check the oil and coolant levels. Everything looks good at the machine level. Next, on the CNC computer, you open the CNC G-code. While looking at the code, Bill points out that there are no coolant commands. Bill adds them in and when you rerun the program, it works.

Bill is glad you mentioned the problem to him. You are the third worker to mention G-code issues over the last week. You noticed the coolant problems in your G-code, John noticed a Z-axis issue in his G-code, and Sam had issues with both the Z-axis and the coolant. Chances are, there is a bigger problem and Bill will need to investigate the root cause .

Talking with Bill, you discuss the best way to fix the problem. Bill suggests editing the G-code to raise the Z-axis of the spindle before it returns to its home position. You open the CNC control program and edit the G-code. Following the setup sheet, you re-setup the job and use the CNC single step/single block function, to do another dry run of the part. Everything looks good, so you run the job again and create the first part. It works. Since you need four of each component, you move on to creating the rest of them before cleaning up and leaving for the day.

It's a new day and you have new components to create. As you are setting up, you go in search of some short dowel pins. You discover that the bins are a mess and components have not been put away in the correctly labeled bins. You wonder if this was the cause of yesterday's problem. As you reorganize the bins and straighten up the mess, you decide to mention the mess issue to Bill in your afternoon meeting.

You describe the bin mess and using the incorrect length dowels to Bill. He is glad you mentioned the problem to him. You are not the first person to mention similar issues with tools and parts not being put away correctly. Chances are there is a bigger safety issue here that needs to be addressed in the next staff meeting.

In any workplace, following proper safety and cleanup procedures is always important. This is especially crucial in manufacturing where people are constantly working with heavy, costly and sometimes dangerous equipment. When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost, and save money.

You now know that the end mill was damaged when it hit the dowel pin. It seems to you that the easiest thing to do would be to edit the G-code and raise the Z-axis position of the spindle before it returns to the home position. You open the CNC control program and edit the G-code, raising the Z-axis. Starting over, you follow the setup sheet and re-setup the job. This time, you use the CNC single step/single block function, to do another dry run of the part. Everything looks good, so you run the job again and create the first part.

At the end of the day, you are reviewing your progress with your trainer, Bill. After you describe the day's events, he reminds you to always think about safety and the importance of following work procedures. He decides to bring the issue up in the next morning meeting as a reminder to everyone.

In any workplace, following proper procedures (especially those that involve safety) is always important. This is especially crucial in manufacturing where people are constantly working with heavy, costly, and sometimes dangerous equipment. When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost, and save money. One tool to improve communication is the morning meeting or huddle.

The next morning, you check the G-code to determine what is wrong with the coolant. You notice that the coolant is turned off at the beginning of the code and also at the end of the code. This is strange. You change the G-code to turn the coolant on at the beginning of the run and off at the end. This works and you create the rest of the parts.

Throughout the day, you keep wondering what caused the G-code error. At lunch, you mention the G-code error to your coworker, John. John is not surprised. He said that he encountered a similar problem earlier this week. You decide to talk with your supervisor the next time you see him.

You are in luck. You see your supervisor by the door getting ready to leave. You hurry over to talk with him. You start off by telling him about how you asked Bill for help. Then you tell him there was a problem and the end mill was damaged. You describe the coolant problem in the G-code. Oh, and by the way, John has seen a similar problem before.

Your supervisor doesn't seem overly concerned, errors happen. He tells you "Good job, I am glad you were able to fix the issue." You are not sure whether your supervisor understood your explanation of what happened or that it had happened before.

The challenge of communicating in the workplace is learning how to share your ideas and concerns. If you need to tell your supervisor that something is not going well, it is important to remember that timing, preparation, and attitude are extremely important.

It is the end of your shift, but you want to let the next shift know that the coolant didn't turn on. You do not see your trainer or supervisor around. You decide to leave a note for the next shift so they are aware of the possible coolant problem. You write a sticky note and leave it on the monitor of the CNC control system.

How effective do you think this solution was? Did it address the problem?

In this scenario, you discovered several problems with the G-code that need to be addressed. When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring and avoid injury to personnel. The challenge of communicating in the workplace is learning how and when to share your ideas and concerns. If you need to tell your co-workers or supervisor that there is a problem, it is important to remember that timing and the method of communication are extremely important.

You are able to fix the coolant problem in the G-code. While you are glad that the problem is fixed, you are worried about why it happened in the first place. It is important to remember that if a problem keeps reappearing, you may not be fixing the right problem. You may only be addressing the symptoms.

You decide to talk to your trainer. Bill is glad you mentioned the problem to him. You are the third worker to mention G-code issues over the last week. You noticed the coolant problems in your G-code, John noticed a Z-axis issue in his G-code, and Sam had issues with both the Z-axis and the coolant. Chances are, there is a bigger problem and Bill will need to investigate the root cause .

Over lunch, you ask your coworkers about the G-code problem and what may be causing the error. Several people mention having similar problems but do not know the cause.

You have now talked to three coworkers who have all experienced similar coolant G-code problems. You make a list of who had the problem, when they had the problem, and what each person told you.

When you see your supervisor later that afternoon, you are ready to talk with him. You describe the problem you had with your component and the damaged bit. You then go on to tell him about talking with Bill and discovering the G-code issue. You show him your notes on your coworkers' coolant issues, and explain that you think there might be a bigger problem.

You supervisor thanks you for your initiative in identifying this problem. It sounds like there is a bigger problem and he will need to investigate the root cause. He decides to call a team huddle to discuss the issue, gather more information, and talk with the team about the importance of communication.

Root Cause Analysis

Root cause analysis ( RCA ) is a method of problem solving that identifies the underlying causes of an issue. Root cause analysis helps people answer the question of why the problem occurred in the first place. RCA uses clear cut steps in its associated tools, like the "5 Whys Analysis" and the "Cause and Effect Diagram," to identify the origin of the problem, so that you can:

• Determine what happened.
• Determine why it happened.
• Fix the problem so it won’t happen again.

RCA works under the idea that systems and events are connected. An action in one area triggers an action in another, and another, and so on. By tracing back these actions, you can discover where the problem started and how it developed into the problem you're now facing. Root cause analysis can prevent problems from recurring, reduce injury to personnel, reduce rework and scrap, and ultimately, reduce cost and save money. There are many different RCA techniques available to determine the root cause of a problem. These are just a few:

• Root Cause Analysis Tools
• 5 Whys Analysis
• Fishbone or Cause and Effect Diagram
• Pareto Analysis

How Huddles Work

Communication is a vital part of any setting where people work together. Effective communication helps employees and managers form efficient teams. It builds trusts between employees and management, and reduces unnecessary competition because each employee knows how their part fits in the larger goal.

One tool that management can use to promote communication in the workplace is the huddle . Just like football players on the field, a huddle is a short meeting where everyone is standing in a circle. A daily team huddle ensures that team members are aware of changes to the schedule, reiterated problems and safety issues, and how their work impacts one another. When done right, huddles create collaboration, communication, and accountability to results. Impromptu huddles can be used to gather information on a specific issue and get each team member's input.

The most important thing to remember about huddles is that they are short, lasting no more than 10 minutes, and their purpose is to communicate and identify. In essence, a huddle’s purpose is to identify priorities, communicate essential information, and discover roadblocks to productivity.

Who uses huddles? Many industries and companies use daily huddles. At first thought, most people probably think of hospitals and their daily patient update meetings, but lots of managers use daily meetings to engage their employees. Here are a few examples:

• Brian Scudamore, CEO of 1-800-Got-Junk? , uses the daily huddle as an operational tool to take the pulse of his employees and as a motivational tool. Watch a morning huddle meeting .
• Fusion OEM, an outsourced manufacturing and production company. What do employees take away from the daily huddle meeting .
• Biz-Group, a performance consulting group. Tips for a successful huddle .

Brainstorming

One tool that can be useful in problem solving is brainstorming . Brainstorming is a creativity technique designed to generate a large number of ideas for the solution to a problem. The method was first popularized in 1953 by Alex Faickney Osborn in the book Applied Imagination . The goal is to come up with as many ideas as you can in a fixed amount of time. Although brainstorming is best done in a group, it can be done individually. Like most problem solving techniques, brainstorming is a process.

• Define a clear objective.
• Have an agreed a time limit.
• During the brainstorming session, write down everything that comes to mind, even if the idea sounds crazy.
• If one idea leads to another, write down that idea too.
• Combine and refine ideas into categories of solutions.
• Assess and analyze each idea as a potential solution.

When used during problem solving, brainstorming can offer companies new ways of encouraging staff to think creatively and improve production. Brainstorming relies on team members' diverse experiences, adding to the richness of ideas explored. This means that you often find better solutions to the problems. Team members often welcome the opportunity to contribute ideas and can provide buy-in for the solution chosen—after all, they are more likely to be committed to an approach if they were involved in its development. What's more, because brainstorming is fun, it helps team members bond.

• Watch Peggy Morgan Collins, a marketing executive at Power Curve Communications discuss How to Stimulate Effective Brainstorming .
• Watch Kim Obbink, CEO of Filter Digital, a digital content company, and her team share their top five rules for How to Effectively Generate Ideas .

Importance of Good Communication and Problem Description

Communication is one of the most frequent activities we engage in on a day-to-day basis. At some point, we have all felt that we did not effectively communicate an idea as we would have liked. The key to effective communication is preparation. Rather than attempting to haphazardly improvise something, take a few minutes and think about what you want say and how you will say it. If necessary, write yourself a note with the key points or ideas in the order you want to discuss them. The notes can act as a reminder or guide when you talk to your supervisor.

Tips for clear communication of an issue:

• Provide a clear summary of your problem. Start at the beginning, give relevant facts, timelines, and examples.
• Avoid including your opinion or personal attacks in your explanation.
• Avoid using words like "always" or "never," which can give the impression that you are exaggerating the problem.
• If this is an ongoing problem and you have collected documentation, give it to your supervisor once you have finished describing the problem.
• Remember to listen to what's said in return; communication is a two-way process.

Not all communication is spoken. Body language is nonverbal communication that includes your posture, your hands and whether you make eye contact. These gestures can be subtle or overt, but most importantly they communicate meaning beyond what is said. When having a conversation, pay attention to how you stand. A stiff position with arms crossed over your chest may imply that you are being defensive even if your words state otherwise. Shoving your hands in your pockets when speaking could imply that you have something to hide. Be wary of using too many hand gestures because this could distract listeners from your message.

The challenge of communicating in the workplace is learning how and when to share your ideas or concerns. If you need to tell your supervisor or co-worker about something that is not going well, keep in mind that good timing and good attitude will go a long way toward helping your case.

Like all skills, effective communication needs to be practiced. Toastmasters International is perhaps the best known public speaking organization in the world. Toastmasters is open to anyone who wish to improve their speaking skills and is willing to put in the time and effort to do so. To learn more, visit Toastmasters International .

Methods of Communication

Communication of problems and issues in any workplace is important, particularly when safety is involved. It is therefore crucial in manufacturing where people are constantly working with heavy, costly, and sometimes dangerous equipment. As issues and problems arise, they need to be addressed in an efficient and timely manner. Effective communication is an important skill because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost and save money.

There are many different ways to communicate: in person, by phone, via email, or written. There is no single method that fits all communication needs, each one has its time and place.

In person: In the workplace, face-to-face meetings should be utilized whenever possible. Being able to see the person you need to speak to face-to-face gives you instant feedback and helps you gauge their response through their body language. Be careful of getting sidetracked in conversation when you need to communicate a problem.

Email: Email has become the communication standard for most businesses. It can be accessed from almost anywhere and is great for things that don’t require an immediate response. Email is a great way to communicate non-urgent items to large amounts of people or just your team members. One thing to remember is that most people's inboxes are flooded with emails every day and unless they are hyper vigilant about checking everything, important items could be missed. For issues that are urgent, especially those around safety, email is not always be the best solution.

Phone: Phone calls are more personal and direct than email. They allow us to communicate in real time with another person, no matter where they are. Not only can talking prevent miscommunication, it promotes a two-way dialogue. You don’t have to worry about your words being altered or the message arriving on time. However, mobile phone use and the workplace don't always mix. In particular, using mobile phones in a manufacturing setting can lead to a variety of problems, cause distractions, and lead to serious injury.

Written: Written communication is appropriate when detailed instructions are required, when something needs to be documented, or when the person is too far away to easily speak with over the phone or in person.

There is no "right" way to communicate, but you should be aware of how and when to use the appropriate form of communication for your situation. When deciding the best way to communicate with a co-worker or manager, put yourself in their shoes, and think about how you would want to learn about the issue. Also, consider what information you would need to know to better understand the issue. Use your good judgment of the situation and be considerate of your listener's viewpoint.

Did you notice any other potential problems in the previous exercise?

• [Page 6:] Did you notice any other potential problems in the previous exercise?

Summary of Strategies

In this exercise, you were given a scenario in which there was a problem with a component you were creating on a CNC machine. You were then asked how you wanted to proceed. Depending on your path through this exercise, you might have found an easy solution and fixed it yourself, asked for help and worked with your trainer, or discovered an ongoing G-code problem that was bigger than you initially thought.

When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost, and save money. Although, each path in this exercise ended with a description of a problem solving tool for your toolbox, the first step is always to identify the problem and define the context in which it happened.

There are several strategies that can be used to identify the root cause of a problem. Root cause analysis (RCA) is a method of problem solving that helps people answer the question of why the problem occurred. RCA uses a specific set of steps, with associated tools like the “5 Why Analysis" or the “Cause and Effect Diagram,” to identify the origin of the problem, so that you can:

Once the underlying cause is identified and the scope of the issue defined, the next step is to explore possible strategies to fix the problem.

If you are not sure how to fix the problem, it is okay to ask for help. Problem solving is a process and a skill that is learned with practice. It is important to remember that everyone makes mistakes and that no one knows everything. Life is about learning. It is okay to ask for help when you don’t have the answer. When you collaborate to solve problems you improve workplace communication and accelerates finding solutions as similar problems arise.

One tool that can be useful for generating possible solutions is brainstorming . Brainstorming is a technique designed to generate a large number of ideas for the solution to a problem. The method was first popularized in 1953 by Alex Faickney Osborn in the book Applied Imagination. The goal is to come up with as many ideas as you can, in a fixed amount of time. Although brainstorming is best done in a group, it can be done individually.

Depending on your path through the exercise, you may have discovered that a couple of your coworkers had experienced similar problems. This should have been an indicator that there was a larger problem that needed to be addressed.

In any workplace, communication of problems and issues (especially those that involve safety) is always important. This is especially crucial in manufacturing where people are constantly working with heavy, costly, and sometimes dangerous equipment. When issues and problems arise, it is important that they be addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost and save money.

One strategy for improving communication is the huddle . Just like football players on the field, a huddle is a short meeting with everyone standing in a circle. A daily team huddle is a great way to ensure that team members are aware of changes to the schedule, any problems or safety issues are identified and that team members are aware of how their work impacts one another. When done right, huddles create collaboration, communication, and accountability to results. Impromptu huddles can be used to gather information on a specific issue and get each team member's input.

To learn more about different problem solving strategies, choose an option below. These strategies accompany the outcomes of different decision paths in the problem solving exercise.

• View Problem Solving Strategies Select a strategy below... Root Cause Analysis How Huddles Work Brainstorming Importance of Good Problem Description Methods of Communication

Communication is one of the most frequent activities we engage in on a day-to-day basis. At some point, we have all felt that we did not effectively communicate an idea as we would have liked. The key to effective communication is preparation. Rather than attempting to haphazardly improvise something, take a few minutes and think about what you want say and how you will say it. If necessary, write yourself a note with the key points or ideas in the order you want to discuss them. The notes can act as a reminder or guide during your meeting.

• Provide a clear summary of the problem. Start at the beginning, give relevant facts, timelines, and examples.

In person: In the workplace, face-to-face meetings should be utilized whenever possible. Being able to see the person you need to speak to face-to-face gives you instant feedback and helps you gauge their response in their body language. Be careful of getting sidetracked in conversation when you need to communicate a problem.

There is no "right" way to communicate, but you should be aware of how and when to use the appropriate form of communication for the situation. When deciding the best way to communicate with a co-worker or manager, put yourself in their shoes, and think about how you would want to learn about the issue. Also, consider what information you would need to know to better understand the issue. Use your good judgment of the situation and be considerate of your listener's viewpoint.

"Never try to solve all the problems at once — make them line up for you one-by-one.” — Richard Sloma

Problem Solving: An Important Job Skill

Problem solving improves efficiency and communication on the shop floor. It increases a company's efficiency and profitability, so it's one of the top skills employers look for when hiring new employees. Recent industry surveys show that employers consider soft skills, such as problem solving, as critical to their business’s success.

The 2011 survey, "Boiling Point? The skills gap in U.S. manufacturing ," polled over a thousand manufacturing executives who reported that the number one skill deficiency among their current employees is problem solving, which makes it difficult for their companies to adapt to the changing needs of the industry.

In this video, industry professionals discuss their expectations and present tips for new employees joining the manufacturing workforce.

Quick Summary

• [Quick Summary: Question1] What are two things you learned in this case study?
• What question(s) do you still have about the case study?
• [Quick Summary: Question2] What question(s) do you still have about the case study?
• Is there anything you would like to learn more about with respect to this case study?
• [Quick Summary: Question3] Is there anything you would like to learn more about with respect to this case study?

• 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

How to Solve Problems

• Laura Amico

To bring the best ideas forward, teams must build psychological safety.

Teams today aren’t just asked to execute tasks: They’re called upon to solve problems. You’d think that many brains working together would mean better solutions, but the reality is that too often problem-solving teams fall victim to inefficiency, conflict, and cautious conclusions. The two charts below will help your team think about how to collaborate better and come up with the best solutions for the thorniest challenges.

• Laura Amico is a former senior editor at Harvard Business Review.

Partner Center

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? (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)

• Class Notes

Digital Exclusives

• Blog Network
• School News
• Alumni Spotlight

Breaking Gender Barriers in the Board Room

How Ellen Stafford-Sigg WG88 influenced the leadership of Deloitte over 35 years

Using GenAI as a Collaborative Teammate

The technology can fill critical gaps and build trust.

A Wharton Legend Wows the Crowd at Impact Tour NYC

Emeritus finance professor Jeremy Siegel brought the audience back to the classroom before fielding questions from Dean Erika James.

Inside the 52nd Iditarod

Race CEO Rob Urbach WG91 talks livestream logistics, remote rescues, and building a dog-brand empire.

A Family Affair

How Hannah and Malick Diop WG09 collaborated with a famous relative to disrupt the beauty and entertainment industries

Alumni Book Roundup: Winter 2024

Aviation adventures, tales for children, and remembering a baseball legend

Insights from the World Economic Forum in Davos

An insider shares his decades-long experience with the annual meeting of international leaders in the Swiss Alps

How to Develop Talent in a GenAI World

Leveraging artificial intelligence to recruit and train future leaders

Insights From a Gig-Economy Executive

Taskrabbit CEO Ania Smith WG02 reflects on the digital platform’s growth, navigating global change, and the importance of resilience.

5 Questions to Ask Before Joining a Nonprofit Board

Make sure the board aligns with your passions and skills

Don’t Leave Your Job — Refresh It

Professor Samir Nurmohamed offers guidance for finding new opportunities within your current role

A Moment for Community and Opportunity

Pam Perskie W97, the new president of the Wharton Club of New York, reflects on the strength and impact of the alumni network

40 Years of Wharton’s Business Economics and Public Policy Department

Faculty and alumni reflect on how the first program of its kind has evolved

Black and African MBA Events Celebrate Milestone Anniversaries

The Whitney M. Young Jr. Memorial Conference turns 50 this year, while the Wharton Africa Business Forum marks its 30th

When to Speak Up in Meetings

Professor Michael Parke’s recent paper shows how employees can harness the power of “strategic silence”

A Veteran’s Lessons in Leadership

Daniel Moore WG00’s non-traditional journey from Air Force Captain to real estate CEO

The Eight Fundamentals of Problem Solving

As business leaders we are consequently required to solve problems. But what are the very fundamentals of problem solving?

Read on to find out.

1. Define the Real Problem

This is the biggie. Ensure that you are solving the right problem. Toyota is justifiably famous for its problem-solving savvy in perfecting its production methods. According to Toyota, the key to their method is to spend relatively more time defining the problem and relatively less time on figuring out the solution.

2. Solve the Root Cause of the Problem

Don’t treat the symptoms; solve the root cause of the problem. There are numerous methods to determine root causes—cause mapping, fishbone diagrams, etc. For me, the easiest and most effective is to use the “Five Whys.” Ask a question and to each answer ask. “Why?” again. Doing this for five times should get you to the root cause of the problem.

3. Use a Hypothesis

As happens on the “CSI” television shows, you should make a best guess as to the solution to the problem at the very beginning of your process—define the initial hypothesis. Then test this initial hypothesis by digging deep to determine whether the hypothesis is right or wrong and adjusting the hypothesis as the facts dictate.

4. Get the Facts

Dig deep and get the facts to truly understand the nature of the problem and the possible solutions. Do the analysis to let the facts do the talking instead of gut instinct. As Wharton’s own Peter Cappelli says: “I tell my MBA students that whenever you are going with your gut, you are doing something wrong. In most cases, you can actually figure it out. So you should sit down and figure it out.”

5. Keep the solution simple

Any solution to a problem has to be implemented by your team. So keep it simple. Be able to explain the solution clearly and precisely in 30 seconds. Limit the action items to solve the problem to three. Go for the solution that solves 80 percent of the problem but that is 100 percent implementable by the team—rather than a 100 percent solution that is unlikely to ever be properly implemented.

6. Do not re-invent the wheel

Plagiarism can be good. If someone has a clever idea or way to solve your problem, by all means legally use it. The “not invented here” syndrome is just sheer arrogance.

7. Gain momentum in problem solving

In situations where you have multiple problems to solve (e.g., business turnarounds) pluck the low-hanging but important fruit first. Solve the easy problems. This gives you momentum, shows progress and gives your team confidence.

8. Consider time

With any solution, ensure that you do first what needs to be done first. Also, ensure that the solution can be implemented in a reasonable period of time. Solutions that take longer than a few months will likely fail. The momentum will die out or top management will move on to another “critical issue.”

Everyday Advice for Business Leader Sanity

Simple to-do tips that are easy to execute in a how-to world drowning in advice.

7 Ways Your Smartphone May Be Killing Your Business

Today’s smartphones enable business leaders to constantly be in contact with the office and access the Internet or the cloud for needed information on the fly. Unfortunately, it is exactly this constant contact and easy access that often overwhelm the positives and make these devices harmful to the leaders’ businesses and lives.

9 Keys to Driving Cultural Change

The hardest part of a business transformation is changing the culture—the mindset and instincts of the people in the company. So, what are the keys to driving cultural change?

The Inside Story of How Creative Business Gets Done

Leadership consultant Roz Courtney translates the story behind an iconic Robin Williams cover photo to lessons in creativity valuable to any business executive.

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

What Factors Actually Impact a Developer’s Decision to Accept an Offer?

Game Central

Decision-Making

Can't solve a problem find the problem under the problem, not all problems are created equal. four common types and their antidotes..

Posted June 24, 2023 | Reviewed by Lybi Ma

• Problems are problems only because they are situations in our lives that we are struggling to solve.
• The four common sources of problems are lack of skill, emotional triggering, indecisiveness, and your story.
• The key to solving problems are knowing the undelying cause and taking active steps to address them.

As a therapist, most of my day is spent helping clients solve a problem: With their emotions— anxiety or depression —with their relationships—their boss, partner, kids. What I’m always most curious about is not the problem itself but where they are getting stuck solving it on their own. Different schools of therapy each have their approaches and solutions: Psychodynamic approaches may focus on unraveling the past and its wounds, while cognitive-behavioral will focus on how what you think and do affects your emotions. But we can also think about the problem-solving process on a more everyday level. Here, in my experience, are the four most common ways clients get stuck solving their problems and their antidotes:

1: You don’t have the skills to do what you want to do

In his seminal book, The Teaching and Learning of Psychotherapy , the psychiatrist Rudolf Ekstein said that all problems could be broken down into two camps: Learning problems and problems about learning. Learning problems are problems caused by a lack of skill. You never diapered a baby, written a resume, or mowed a lawn. Once someone shows you how to do it, you then practice, develop the skill, and the problem is solved.

But many common behavioral and relationship problems that we often associate with personality entail learning new skills—how to destress, control your temper or drinking, eat healthily, or even communicate effectively and compromise, manage conflict or anxiety; the list goes on.

Antidote: You need information, training, practice, and support. Watch a YouTube video, take a class, hire a teacher, join a support group, and or get therapy.

2: You get emotionally triggered

This is Ekstein’s second category: Problems about learning. Here you have a baseline of skills—for example, you know how to be a good parent—but under particular stressful situations, or when certain situations trigger you, these skills go out the window—my teenage daughter gives that pouty defiant look with her hands on her hips, and I go crazy. We all do this based on wounds from our past: Your boss doesn’t say good morning to you, and you think she’s angry with you; your partner doesn’t return your phone call, and you assume something terrible has happened to him; you're angry with your partner but rather than speaking up, you shut down and sweep it under the rug. For some, the triggers are very specific, the teenage daughter’s look, but for many, they're more generalized—it's not just your partner you avoid confronting, but you're anxious about any sign of a potential conflict and go out of your way to avoid it.

Antidote: When emotions hijack the brain, that rational brain shuts down; we literally can’t think straight, go down rabbit holes of irrational fears, or our anger goes zero to 60. The antidote is in two parts: Part one is first aid—realizing we are getting upset and having tools to calm ourselves down—going for a walk, deep breathing, writing down how we feel, and or talking to a friend.

Part two is taking action to solve the problem: Having a non-emotional conversation with the daughter about arguments, anger, or attitude; taking baby steps towards talking to your partner so you can become more comfortable with confrontation rather than continuing to avoid it; stepping away from those little-kid feelings of being in trouble and stepping up and being the adult that you are.

3: You're afraid of making a wrong decision

You don’t solve the problem because you are not decisive, and you’re not decisive because you constantly are fretting about making the right decision. Often, this is more complicated than it needs to be: You have to figure out what you should do versus what you want to do; then you need to figure out how others may react and what will make them happy—a tall order. This fear of making a mistake can be paralyzing for many; often, they are highly self-critical or perfectionistic .

Antidote: This too is rooted in anxiety, the notion that bad choices invariably lead to terrible consequences that can’t be repaired. Like feeling overwhelmed, this is usually tied to wounds from the past, and like most anxiety-based situations, the antidote to moving forward despite how you feel. Because anxiety makes everything feel important, you want to learn to prioritize your decisions—what to eat for lunch does not require the same caution as deciding what house to buy or college to attend; rather than obsessing and overthinking, you want to take acceptable risks—making decisions that seem a bit impulsive—to find out that what your anxious brain is telling you will happen, doesn’t. And even if you decide in hindsight that you made a mistake, realize that few mistakes in life can’t be repaired.

4: You’re holding onto your story

I’m a loser; I don’t deserve to be happy; others can’t be trusted; men are self-centered; I need to constantly look around corners or bad things will sneak up on me.

The story we tell ourselves about ourselves and the world limits our ability to deal with the world and its problems. If you believe you’re a loser or don’t deserve to be happy, you don’t try and take what you get; if others can’t be trusted, you don’t get close to anyone; if you have to be hypervigilant and always look around corners, you’re constantly anxious, living in the future rather than the present. Problems aren’t solved because your range of options and ability to think creatively are limited.

Antidote: The story is exactly that, a story, a fiction that someone helped to plant within you. It is like old software in a computer that no longer works. Time to upgrade, change the story, or act despite it to again find out what you think is true is not.

One way of viewing problems is that they tell us what we need to learn. Where do you get stuck solving your problems? What skills do you need to develop? What risks do you need to learn to take?

Bob Taibbi, L.C.S.W., has 49 years of clinical experience. He is the author of 13 books and over 300 articles and provides training nationally and internationally.

• Find a Therapist
• Find a Treatment Center
• Find a Psychiatrist
• Find a Support Group
• Find Teletherapy
• United States
• Brooklyn, NY
• Chicago, IL
• Houston, TX
• Los Angeles, CA
• New York, NY
• Portland, OR
• San Diego, CA
• San Francisco, CA
• Seattle, WA
• Washington, DC
• Asperger's
• Bipolar Disorder
• Chronic Pain
• Eating Disorders
• Passive Aggression
• Personality
• Goal Setting
• Positive Psychology
• Stopping Smoking
• Low Sexual Desire
• Relationships
• Child Development
• Therapy Center NEW
• Diagnosis Dictionary
• Types of Therapy

Understanding what emotional intelligence looks like and the steps needed to improve it could light a path to a more emotionally adept world.

• Coronavirus Disease 2019
• Affective Forecasting
• Neuroscience

Pave the Way for Self-regulation and Problem-solving With Social-emotional Learning

Posted: April 3, 2024

Problem-solving is a social-emotional learning (SEL) skill children need for lifelong success. Effective problem-solving skills support children's ability to self-regulate, focus on tasks, think flexibly and creatively, work with others, and generate multiple ways to solve problems. When young children develop and build these skills, it positively impacts their interactions with others, grows their capacity to manage challenges, and boosts a sense of competence.

A group of school-age children are stacking plastic blocks with an educator.

The foundation for effective social problem-solving is grounded in self-regulation, or the ability to regulate emotions when interacting with others. It is easier to focus on one's feelings and the feelings and perspectives of others and to work cooperatively toward solutions when a child can self-regulate and calm down. Children develop self-regulation skills over time, with practice and with adult guidance. Equally important is how an adult models emotion regulation and co-regulation. 

"Caregivers play a key role in cultivating the development of emotion regulation through co-regulation, or the processes by which they provide external support or scaffolding as children navigate their emotional experiences" (Paley & Hajal, 2022, p. 1).

When adults model calm and self-regulated approaches to problem-solving, it shows children how to approach problems constructively. For example, an educator says, "I'm going to take a breath and calm down so I can think better." This model helps children see and hear a strategy to support self-regulation.

Problem-solving skills help children resolve conflicts and interact with others as partners and collaborators. Developing problem-solving skills helps children learn and grow empathy for others, stand up for themselves, and build resilience and competence to work through challenges in their world. 

Eight strategies to support problem-solving 

• Teach about emotions and use feeling words throughout the day. When children have more words to express themselves and their feelings, it is easier to address and talk about challenges when they arise. 
• Recognize and acknowledge children's feelings throughout the day. For example, when children enter the classroom during circle time, mealtime, and outside time, ask them how they feel. Always acknowledge children's feelings, both comfortable and uncomfortable, to support an understanding that all feelings are OK to experience.  
• Differentiate between feelings and behaviors. By differentiating feelings from behaviors, educators contribute to children’s understanding that all feelings are OK, but not all behaviors are OK. For example, an educator says, "It looks like you may be feeling mad because you want the red blocks, and Nila is playing with them. It's OK to feel mad but not OK to knock over your friend’s blocks."
• Support children's efforts to calm down. When children are self-regulated, they can think more clearly. For example, practice taking a breath with children as a self-regulation technique during calm moments. Then, when challenges arise, children have a strategy they have practiced many times and can use to calm down before problem-solving begins.  
• Encourage children's efforts to voice the problem and their feelings after they are calm. For example, when a challenge arises, encourage children to use the phrase, "The problem is_______, and I feel______." This process sets the stage to begin problem-solving.
• Acknowledge children's efforts to think about varied ways to solve problems. For example, an educator says, "It looks like you and Nila are trying to work out how to share the blocks. What do you think might work so you can both play with them? Do you have some other ideas about how you could share?"
• Champion children's efforts as they problem-solve. For example, "You and Nila thought about two ways you could share. One way is to divide the red blocks so you can each build, and the other is to build a tower together. Great thinking, friends!"
• Create opportunities for activities and play that offer problem-solving practice. For example, when children play together in the block area, it provides opportunities to negotiate plans for play and role-play, build perspective, talk about feelings, and share. The skills children learn during play, along with adult support, enhance children’s ability to solve more complex and challenging social problems and conflicts when they occur in and out of the early learning setting.

References: 

Paley, B., & Hajal, N. J. (2022). Conceptualizing emotion regulation and coregulation as family-level phenomena. Clinical Child and Family Psychology Review ,  25 (1), 19-43.

Social Media

• X (Twitter)
• Degrees & Programs
• College Directory

Information for

• Faculty & Staff
• Visitors & Public

• Share full article

Advertisement

Subscriber-only Newsletter

If A.I. Takes All Our Jobs, Will It Also Take Our Purpose?

By Peter Coy

Opinion Writer

What would life be like if artificial intelligence solved all your problems? You wouldn’t have to work anymore. You could get any luxury you wanted by raising an eyebrow. Feelings of pleasure would wash over you constantly. Death would become almost optional because you could take on digital form and keep going for a billion years.

It sounds awful to me.

We human beings dislike our problems, naturally, but if we had no problems to solve, what meaning would life have? How long would we be happy sitting on top of our big rock candy mountains? For me, one long weekend would about do it. A billion years of perfect happiness would be perfect misery.

Nick Bostrom, a philosophy professor at Oxford, wrestles with this question in a fascinating book that was published on March 27, “Deep Utopia: Life and Meaning in a Solved World.” Solved here means solved the way the game of tic-tac-toe has been solved: If you move first, there is no reason you should ever lose.

A lot has changed in A.I. in the 10 years since Bostrom’s last book on the topic, “Superintelligence: Paths, Dangers, Strategies.” A.I. is folding proteins, generating art and blowing minds. The idea that it will change the world has gone from a nerdy obsession to conventional wisdom.

What we still don’t know is how A.I. will change the world. It could enslave or kill us all. But for “Deep Utopia,” Bostrom smartly chose to imagine the opposite: That A.I. does exactly what we ask it to do.

It’s not a pretty picture. “Basically,” he writes, “we’re unfit to inhabit a perfect world.”

People could still “work” at “jobs” in “offices” even if A.I. becomes able to do everything better than people can — a scenario examined by the economist Pascual Restrepo of Boston University in one of my newsletters last month. But the jobs will really be more like harmless hobbies, Bostrom writes.

Fine, you might say, people can fulfill themselves in other ways, such as shopping or gardening or child care. Bostrom punctures that balloon as well. One reason people find satisfaction in such activities is that they pride themselves on being good at them — knowing how to find the right throw pillow or grow gardenias or dry a child’s tears.

But A.I. will be able to do all of those things better than you can, Bostrom says. “It is quite conceivable that, at technological maturity, you would in fact be slightly harming your child whenever you indulged in some D.I.Y. parenting,” he writes.

I predict that prediction will infuriate a lot of people. I’m appalled by it myself. Bostrom, though, is not aiming to please. He clearly prides himself on following trends in A.I. to their logical conclusions, even when that’s discomfiting. He’s a jokey, quirky polymath who has a doctorate in philosophy but has also studied computational neuroscience, mathematical logic, astrophysics and general relativity.

Although he says we’re not cut out for perfection, Bostrom does explore ways that life in utopia could be made bearable after all. For instance, we could ask the computers to give us absorbing challenges. He cites a science fiction novel, “Permutation City” by Greg Egan, about a man who has achieved immortality. To avoid boredom, he programs himself to be seized, at random intervals, by fresh passions. At the moment of the novel it’s making table legs, of which he has manufactured 162,329.

That feels more like hell than heaven. Another vision of the future, even more repulsing, is that we become aimless blobs, perhaps hooked up to electrodes for jolts of pleasure.

Bostrom asks us to suspend judgment, though. Maybe we’d like it. “The question before us here is a very different one: not how interesting a future is to look at , but how good it is to live in .”

Bostrom told me on Friday that he sees the book as an exploration of the A.I. future, not a conclusion about it. “It’s going to be ultimately a very deep question what we choose,” he said. There is, he said, “a hunger for people to think about these questions.”

He likened the book to a particle accelerator that smashes atoms together to study their parts, such as quarks. In “Deep Utopia,” he said, he smashed values into one another to study their composition.

Toward the end of the book, a professor named Bostrom who very much resembles the author promises to reveal the secret of life. Just as he gets to that point in the lecture, the dean tells him to wrap up because the venue has been booked only until 6.

“Well,” the Bostrom character says, “I guess that’s that.”

The Readers Write

On China’s domination of green technology exports : I’m of the opinion that the planet does not care who is making what. What matters to the planet is total emissions and use of resources. If someone can make them most efficiently on the South Pole, that’s what’s better for our planet.

Mato Egredzija Zagreb, Croatia

Treasury Secretary Janet Yellen’s trip to China comes across as typical U.S. arrogance of telling people what they should be doing. How would she feel if the Chinese finance minister visited Washington, D.C., and told her that Americans should be saving more money for retirement and children’s education?

Patrick Yuen Riverside, Conn.

Quote of the Day

“There ain’t any answer, there ain’t going to be any answer, there never has been any answer, that’s the answer.”

— Gertrude Stein, “Brewsie and Willie” (1946)

Peter Coy is a writer for the Opinion section of The Times, covering economics and business. Email him at [email protected] . @ petercoy

• Environment

This Kind of Fracking Can Help Solve Our Climate Problems

The us government aims to make geothermal energy a viable clean power source., oliver milman.

• Share on Facebook
• Share on Twitter

A surge tank on the injection well return line at the Blundell Geothermal Power Plant near Milford, Utah. Jon G. Fuller / ZUMA

This story was originally published by the Guardian and is reproduced here as part of the  Climate Desk   collaboration.

A limitless supply of heat exists beneath our feet within the Earth’s crust, but harnessing it at scale has proved challenging. Now, a combination of new techniques, government support and the pressing need to secure continuous clean power in an era of climate crisis means that geothermal energy is finally having its moment in the US.

Until recently, geothermal has only been viable where the Earth’s inner heat simmers near the surface, such as at hot springs or geysers where hot water or steam can be easily drawn to drive turbines and generate electricity.

While this has allowed a limited number of places,  like Iceland , to use geothermal as a main source of heating and electricity, it has only been a niche presence in the US, providing  less than 1 percent of the nation’s electricity . But this could change dramatically, offering the promise of endless, 24/7 clean energy that can fill in the gaps of intermittent solar and wind generation in the electricity grid.

“Geothermal has been used for over 100 years, limited to certain geographic locations—but that is now changing,” said Amanda Kolker, the geothermal laboratory program manager at the National Renewable Energy Laboratory (NREL).

“As we penetrate the grid with renewables that are not available all the time, we need to find a base load, which is currently taken up by gas. There aren’t really many options for zero-emissions base load power, which is why geothermal is entering the picture.”

Geothermal capacity could increase 20-fold by 2050, generating 10 percent of the US’s electricity, according to  a recent road map released by the US Department of Energy . Joe Biden’s administration has also funded new projects aimed at pushing forward the next generation of geothermal that aim to make the energy source available anywhere on America’s landmass, not just easy-to-reach hot springs.

“The US can lead the clean-energy future with continued innovation on next-generation technologies, from harnessing the power of the sun to the heat beneath our feet, and cracking the code to deploy them at scale,” said Jennifer Granholm, the US energy secretary, who added that she saw “enormous potential” in geothermal.

Expanding the geothermal footprint to the entire US will take time, as well as plenty of money—the department of energy estimates as much as $250 billion will be needed for projects to become widespread across the country, providing a major source of clean power.

But advocates of geothermal say that such growth is within reach, because of a wave of geothermal technologies as well as government support. In February, the Biden administration  announced $74 million for up to seven pilot projects to develop enhanced geothermal systems that, the government said, hold the potential for powering 65 million American homes.

Ironically, enhanced geothermal uses similar fracking techniques currently used to extract oil and gas, which must be phased out if the world is to avoid climate disaster. In the geothermal version of fracking, fluid is injected deep underground, causing fractures to open up, with the liquid becoming hot as it circulates. The hot water is then pumped to the surface, where it can generate electricity for the grid.

This, and other new techniques that allow deeper and horizontal drilling, in some cases down to eight miles deep, allows geothermal energy to be drawn from hot rocks found anywhere underground, rather than select spots that have hot water near the surface. This vastly expands the potential of the technology.

“Anywhere in the country, if you drill, it gets hotter and hotter with each mile you go deeper,” said Koenraad Beckers, an NREL thermal sciences researcher.

“In the Western United States, that temperature increases fast. If you drill just one to two miles deep, you have temperatures hot enough for electricity. To get those temperatures in eastern states, you might need to drill miles and miles down, but you can use lower temperatures to directly heat or cool campuses, neighborhoods, and even towns.”

Dozens of new companies are looking to push ahead with geothermal plans, buoyed up by incentives offered by  recent   legislation  passed in the US, although only a few have so far managed to complete full projects in the US, such as Eavor, a Canadian firm that successfully drilled  a three-mile hole in New Mexico  to prove it could access heat in deep, granite rock.

At play for these companies is an inexhaustible energy supply. Just one type of next generation geothermal—called superhot rock energy, where deep drilling reaches temperatures 400 degrees Celsius or hotter—is abundant enough to theoretically fulfill the world’s power requirements. In fact, just 1 percent of the world’s superhot rock potential could provide 63 terawatts of clean firm power , which would meet global electricity demand nearly eight times over.

“While this modeling is preliminary, our findings suggest an enormous opportunity to unlock vast amounts of clean energy beneath our feet,” said Terra Rogers, the director for superhot rock energy at Clean Air Task Force, which produced the modelling tool to measure the potential of this approach .

“Energy security backed by always available zero-carbon energy isn’t a far-off dream.”

The Toad and the Geothermal Plant

Henry Carnell

This Casino Gambled on Geothermal—and Hit the Jackpot

Jessica McKenzie

New Tectonic Source of Geothermal Energy?

Julia Whitty

Hot Promises of Geothermal Energy

Mother Jones

We Recommend

How Trump’s 2024 Campaign Became a Bloody Cage Fight

Michael Sokolove

RFK Jr. Fundraisers Tied to J6ers, QAnoners, Christian Nationalists, and Far-Right Extremists

David Corn and Dan Friedman

Alabama Lawmakers Want Prison for False Reporting Charges. That Could Have Serious Consequences.

Rachel de Leon

This Is How GOP Signature Matching Laws Harm Disabled Voters

Julia Métraux

Democratic Senators Pressured EPA to Ease Rules on Steel Mill Pollution

Lylla Younes

Uganda Cited Dobbs in an Anti-LGBTQ Crackdown. Americans Should Worry Too.

Julianne McShane

José Andrés: IDF Airstrikes Deliberately Targeted Aid Workers, “Systematically, Car by Car”

Arianna Coghill

Florida’s Ballot Measure on Abortion Could Give Democrats a Lifeline

Abby Vesoulis

Sign up for our free newsletter

Subscribe to the Mother Jones Daily to have our top stories delivered directly to your inbox.

By signing up, you agree to our privacy policy and terms of use , and to receive messages from Mother Jones and our partners.

Get our award-winning magazine

Save big on a full year of investigations, ideas, and insights.

Support our journalism

Help Mother Jones ' reporters dig deep with a tax-deductible donation.

Independent. In print. In your mailbox.

Inexpensive, too! Subscribe today and get a full year of Mother Jones for just $14.95.

Bold. Brave. Beautiful.

Award-winning photojournalism. Stunning video. Fearless conversations.

Looking for news you can trust?

We noticed you have an ad blocker on..

Can you pitch in a few bucks to help fund Mother Jones' investigative journalism? We're a nonprofit (so it's tax-deductible), and reader support makes up about two-thirds of our budget.

We noticed you have an ad blocker on. Can you pitch in a few bucks to help fund Mother Jones' investigative journalism?

Don't let an algorithm decide what news you see.

Sign up for the free Mother Jones Daily newsletter and follow the news that matters.

Pointing Fingers at Big Pharma Won't Solve Our Drug Cost Problem

I n his latest outcry against pharmaceuticals , Sen. Bernie Sanders (I.-Vt.) and a group of other senators recently questioned three "Big Pharma" CEOs in an hours-long hearing about the cost of drugs in the U.S. Even the name of the committee -- Health, Education, Labor & Pensions, whose acronym is "HELP" -- drips with irony. The subliminal message was clear: Sanders and his colleagues were there to "help" the American people by addressing the high cost of pharmaceuticals in the U.S. and shed light on the drivers of cost.

Predictably and unfortunately, the hearing did neither in my opinion. What it did do was provide a platform for Sanders to press executives from three of the largest global industry leaders in a showy attempt to place blame.

In order to truly solve the problems plaguing today's healthcare system, policymakers must widen their lens. The issues the hearing sought to address go much deeper than three pharmaceutical CEOs -- and our political leaders would better serve their constituents by working with healthcare stakeholders, not against them. Until policymakers are willing to have the larger conversation about how we got here and the complex factors at play, the American people will continue to shoulder high costs in a failing system with no meaningful "help" from their leaders.

In his prepared remarks for the hearing, Sanders emphasized his goal to "substantially reduce the price of prescription drugs in America." This priority is laudable and would likely be supported by most Americans who are aware of the price of drugs when they fill their prescriptions. But trying to blame pharma alone misses the mark.

While the committee is right that there are deep-seated issues with our current fee-for-service model -- and that often, the majority of the cost burden falls onto everyday Americans -- the narrow focus on three pharmaceutical CEOs stifled the much-needed conversation about the overarching problems with America's fee-for-service model. By honing in on one segment of the healthcare delivery ecosystem, "Big Pharma," the HELP Committee was able to skirt the more difficult questions and shift responsibility onto these CEOs to seemingly snap their fingers and fix everything.

If only it were that simple. Unfortunately, prescription drugs are only a fraction of the total cost of healthcare . Even if we reduced that segment to zero, healthcare costs would likely still be too high for many, and adverse health outcomes wouldn't suddenly be nil. Still, pharmacy benefit managers and other middlemen were not told they may be subjected to a subpoena for this hearing, nor did they have to face the same questioning as pharmaceutical executives , even though they too bear some blame for today's soaring healthcare costs.

The most helpful thing that Sanders and the HELP committee can -- and should -- do is take a broader, constructive approach to the healthcare ecosystem, evaluating how the pieces fit together, understanding how we got here over decades, and outlining what's required to fix the massive issues we face: a system overhaul. Congress and current and prior administrations have played a significant role in getting us here, and they have an important part to play in fixing the current state.

Today's broken fee-for-service system has decoupled payment for services from quality outcomes and incented volume of procedures over prevention. Yet, leaders have failed to find a way to move on from this model. Every healthcare stakeholder is complicit in allowing this broken model and perverse incentives to keep going. And every stakeholder is responsible for breaking this cycle.

Some committee members seemed aware of this reality. Senator Bill Cassidy, MD (R.-La.), used his opening remarks to call on his fellow senators to take a wider, "substantive" look at "insurance benefit design, price transparency, regulatory barriers, intellectual property barriers, and the perverse effect government discount programs have upon prices charged to commercial patients," in addition to the pharmaceutical industry. His apparent understanding of the entire ecosystem -- and the many players who benefit from high prescription costs, which goes far beyond a few pharmaceutical CEOs -- was refreshing. Yet, others appeared to have an overt political agenda and bulldozed right past him.

Repairing the decades-old problems that plague our healthcare industry will take a greater and more unified effort than Big Pharma can accomplish alone. Until policymakers are willing to engage in real collaborative efforts to overhaul decades-old, systemic problems, nothing will change. Pointing fingers at industry leaders is political theater; it is not a serious effort to solve serious problems. Consumers and the country deserve more.

Rita Numerof, PhD, is president of Numerof & Associates, a global healthcare strategy consulting firm, working in all areas of the healthcare industry. She has authored six books, including Bringing Value to Healthcare: Practical Steps for Getting to a Market-Based Model , and is a regular contributor to Forbes , where she writes about the business of healthcare and the need to move to a market-based model.

Editor's note: You can read an opposing perspective on this issue in another op-ed here .