problem solving strategies reddit

How it works

For Business

Join Mind Tools

Self-Assessment • 20 min read

How Good Is Your Problem Solving?

Use a systematic approach..

By the Mind Tools Content Team

Good problem solving skills are fundamentally important if you're going to be successful in your career.

But problems are something that we don't particularly like.

They're time-consuming.

They muscle their way into already packed schedules.

They force us to think about an uncertain future.

And they never seem to go away!

That's why, when faced with problems, most of us try to eliminate them as quickly as possible. But have you ever chosen the easiest or most obvious solution – and then realized that you have entirely missed a much better solution? Or have you found yourself fixing just the symptoms of a problem, only for the situation to get much worse?

To be an effective problem-solver, you need to be systematic and logical in your approach. This quiz helps you assess your current approach to problem solving. By improving this, you'll make better overall decisions. And as you increase your confidence with solving problems, you'll be less likely to rush to the first solution – which may not necessarily be the best one.

Once you've completed the quiz, we'll direct you to tools and resources that can help you make the most of your problem-solving skills.

How Good Are You at Solving Problems?

Instructions.

For each statement, click the button in the column that best describes you. Please answer questions as you actually are (rather than how you think you should be), and don't worry if some questions seem to score in the 'wrong direction'. When you are finished, please click the 'Calculate My Total' button at the bottom of the test.

Answering these questions should have helped you recognize the key steps associated with effective problem solving.

This quiz is based on Dr Min Basadur's Simplexity Thinking problem-solving model. This eight-step process follows the circular pattern shown below, within which current problems are solved and new problems are identified on an ongoing basis. This assessment has not been validated and is intended for illustrative purposes only.

Below, we outline the tools and strategies you can use for each stage of the problem-solving process. Enjoy exploring these stages!

Step 1: Find the Problem (Questions 7, 12)

Some problems are very obvious, however others are not so easily identified. As part of an effective problem-solving process, you need to look actively for problems – even when things seem to be running fine. Proactive problem solving helps you avoid emergencies and allows you to be calm and in control when issues arise.

These techniques can help you do this:

PEST Analysis helps you pick up changes to your environment that you should be paying attention to. Make sure too that you're watching changes in customer needs and market dynamics, and that you're monitoring trends that are relevant to your industry.

Risk Analysis helps you identify significant business risks.

Failure Modes and Effects Analysis helps you identify possible points of failure in your business process, so that you can fix these before problems arise.

After Action Reviews help you scan recent performance to identify things that can be done better in the future.

Where you have several problems to solve, our articles on Prioritization and Pareto Analysis help you think about which ones you should focus on first.

Step 2: Find the Facts (Questions 10, 14)

After identifying a potential problem, you need information. What factors contribute to the problem? Who is involved with it? What solutions have been tried before? What do others think about the problem?

If you move forward to find a solution too quickly, you risk relying on imperfect information that's based on assumptions and limited perspectives, so make sure that you research the problem thoroughly.

Step 3: Define the Problem (Questions 3, 9)

Now that you understand the problem, define it clearly and completely. Writing a clear problem definition forces you to establish specific boundaries for the problem. This keeps the scope from growing too large, and it helps you stay focused on the main issues.

A great tool to use at this stage is CATWOE . With this process, you analyze potential problems by looking at them from six perspectives, those of its Customers; Actors (people within the organization); the Transformation, or business process; the World-view, or top-down view of what's going on; the Owner; and the wider organizational Environment. By looking at a situation from these perspectives, you can open your mind and come to a much sharper and more comprehensive definition of the problem.

Cause and Effect Analysis is another good tool to use here, as it helps you think about the many different factors that can contribute to a problem. This helps you separate the symptoms of a problem from its fundamental causes.

Step 4: Find Ideas (Questions 4, 13)

With a clear problem definition, start generating ideas for a solution. The key here is to be flexible in the way you approach a problem. You want to be able to see it from as many perspectives as possible. Looking for patterns or common elements in different parts of the problem can sometimes help. You can also use metaphors and analogies to help analyze the problem, discover similarities to other issues, and think of solutions based on those similarities.

Traditional brainstorming and reverse brainstorming are very useful here. By taking the time to generate a range of creative solutions to the problem, you'll significantly increase the likelihood that you'll find the best possible solution, not just a semi-adequate one. Where appropriate, involve people with different viewpoints to expand the volume of ideas generated.

Tip: Don't evaluate your ideas until step 5. If you do, this will limit your creativity at too early a stage.

Step 5: Select and Evaluate (Questions 6, 15)

After finding ideas, you'll have many options that must be evaluated. It's tempting at this stage to charge in and start discarding ideas immediately. However, if you do this without first determining the criteria for a good solution, you risk rejecting an alternative that has real potential.

Decide what elements are needed for a realistic and practical solution, and think about the criteria you'll use to choose between potential solutions.

Paired Comparison Analysis , Decision Matrix Analysis and Risk Analysis are useful techniques here, as are many of the specialist resources available within our Decision-Making section . Enjoy exploring these!

Step 6: Plan (Questions 1, 16)

You might think that choosing a solution is the end of a problem-solving process. In fact, it's simply the start of the next phase in problem solving: implementation. This involves lots of planning and preparation. If you haven't already developed a full Risk Analysis in the evaluation phase, do so now. It's important to know what to be prepared for as you begin to roll out your proposed solution.

The type of planning that you need to do depends on the size of the implementation project that you need to set up. For small projects, all you'll often need are Action Plans that outline who will do what, when, and how. Larger projects need more sophisticated approaches – you'll find out more about these in the article What is Project Management? And for projects that affect many other people, you'll need to think about Change Management as well.

Here, it can be useful to conduct an Impact Analysis to help you identify potential resistance as well as alert you to problems you may not have anticipated. Force Field Analysis will also help you uncover the various pressures for and against your proposed solution. Once you've done the detailed planning, it can also be useful at this stage to make a final Go/No-Go Decision , making sure that it's actually worth going ahead with the selected option.

Step 7: Sell the Idea (Questions 5, 8)

As part of the planning process, you must convince other stakeholders that your solution is the best one. You'll likely meet with resistance, so before you try to “sell” your idea, make sure you've considered all the consequences.

As you begin communicating your plan, listen to what people say, and make changes as necessary. The better the overall solution meets everyone's needs, the greater its positive impact will be! For more tips on selling your idea, read our article on Creating a Value Proposition and use our Sell Your Idea Skillbook.

Step 8: Act (Questions 2, 11)

Finally, once you've convinced your key stakeholders that your proposed solution is worth running with, you can move on to the implementation stage. This is the exciting and rewarding part of problem solving, which makes the whole process seem worthwhile.

This action stage is an end, but it's also a beginning: once you've completed your implementation, it's time to move into the next cycle of problem solving by returning to the scanning stage. By doing this, you'll continue improving your organization as you move into the future.

Problem solving is an exceptionally important workplace skill.

Being a competent and confident problem solver will create many opportunities for you. By using a well-developed model like Simplexity Thinking for solving problems, you can approach the process systematically, and be comfortable that the decisions you make are solid.

Given the unpredictable nature of problems, it's very reassuring to know that, by following a structured plan, you've done everything you can to resolve the problem to the best of your ability.

This assessment has not been validated and is intended for illustrative purposes only. It is just one of many Mind Tool quizzes that can help you to evaluate your abilities in a wide range of important career skills.

If you want to reproduce this quiz, you can purchase downloadable copies in our Store .

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Problem Solving

4 Logical Fallacies

Avoid Common Types of Faulty Reasoning

Add comment

Comments (2)

Afkar Hashmi

😇 This tool is very useful for me.

over 1 year

Very impactful

Team Management

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

Sign-up to our newsletter

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

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Newest Releases

SWOT Analysis

How to Build a Strong Culture in a Distributed Team

Mind Tools Store

About Mind Tools Content

Discover something new today

Top tips for delegating.

Delegate work to your team members effectively with these top tips

Ten Dos and Don'ts of Change Conversations

Tips for tackling discussions about change

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

Rumors in the workplace.

Managing and Preventing Them

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

Decision Making

Member Podcast

• 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

Transform your enterprise with the scalable mindsets, skills, & behavior change that drive performance.

Explore how BetterUp connects to your core business systems.

We pair AI with the latest in human-centered coaching to drive powerful, lasting learning and behavior change.

Build leaders that accelerate team performance and engagement.

Unlock performance potential at scale with AI-powered curated growth journeys.

Build resilience, well-being and agility to drive performance across your entire enterprise.

Transform your business, starting with your sales leaders.

Unlock business impact from the top with executive coaching.

Foster a culture of inclusion and belonging.

Accelerate the performance and potential of your agencies and employees.

See how innovative organizations use BetterUp to build a thriving workforce.

Discover how BetterUp measurably impacts key business outcomes for organizations like yours.

A demo is the first step to transforming your business. Meet with us to develop a plan for attaining your goals.

• What is coaching?

Learn how 1:1 coaching works, who its for, and if it's right for you.

Accelerate your personal and professional growth with the expert guidance of a BetterUp Coach.

Types of Coaching

Navigate career transitions, accelerate your professional growth, and achieve your career goals with expert coaching.

Enhance your communication skills for better personal and professional relationships, with tailored coaching that focuses on your needs.

Find balance, resilience, and well-being in all areas of your life with holistic coaching designed to empower you.

Discover your perfect match : Take our 5-minute assessment and let us pair you with one of our top Coaches tailored just for you.

Research, expert insights, and resources to develop courageous leaders within your organization.

Best practices, research, and tools to fuel individual and business growth.

View on-demand BetterUp events and learn about upcoming live discussions.

The latest insights and ideas for building a high-performing workplace.

• BetterUp Briefing

The online magazine that helps you understand tomorrow's workforce trends, today.

Innovative research featured in peer-reviewed journals, press, and more.

Founded in 2022 to deepen the understanding of the intersection of well-being, purpose, and performance

We're on a mission to help everyone live with clarity, purpose, and passion.

Join us and create impactful change.

Read the buzz about BetterUp.

Meet the leadership that's passionate about empowering your workforce.

For Business

For Individuals

10 Problem-solving strategies to turn challenges on their head

Jump to section

What is an example of problem-solving?

What are the 5 steps to problem-solving, 10 effective problem-solving strategies, what skills do efficient problem solvers have, how to improve your problem-solving skills.

Problems come in all shapes and sizes — from workplace conflict to budget cuts.

Creative problem-solving is one of the most in-demand skills in all roles and industries. It can boost an organization’s human capital and give it a competitive edge. 

Problem-solving strategies are ways of approaching problems that can help you look beyond the obvious answers and find the best solution to your problem . 

Let’s take a look at a five-step problem-solving process and how to combine it with proven problem-solving strategies. This will give you the tools and skills to solve even your most complex problems.

Good problem-solving is an essential part of the decision-making process . To see what a problem-solving process might look like in real life, let’s take a common problem for SaaS brands — decreasing customer churn rates.

To solve this problem, the company must first identify it. In this case, the problem is that the churn rate is too high. 

Next, they need to identify the root causes of the problem. This could be anything from their customer service experience to their email marketing campaigns. If there are several problems, they will need a separate problem-solving process for each one. 

Let’s say the problem is with email marketing — they’re not nurturing existing customers. Now that they’ve identified the problem, they can start using problem-solving strategies to look for solutions. 

This might look like coming up with special offers, discounts, or bonuses for existing customers. They need to find ways to remind them to use their products and services while providing added value. This will encourage customers to keep paying their monthly subscriptions.

They might also want to add incentives, such as access to a premium service at no extra cost after 12 months of membership. They could publish blog posts that help their customers solve common problems and share them as an email newsletter.

The company should set targets and a time frame in which to achieve them. This will allow leaders to measure progress and identify which actions yield the best results.

Perhaps you’ve got a problem you need to tackle. Or maybe you want to be prepared the next time one arises. Either way, it’s a good idea to get familiar with the five steps of problem-solving. 

Use this step-by-step problem-solving method with the strategies in the following section to find possible solutions to your problem.

1. Identify the problem

The first step is to know which problem you need to solve. Then, you need to find the root cause of the problem. 

The best course of action is to gather as much data as possible, speak to the people involved, and separate facts from opinions. 

Once this is done, formulate a statement that describes the problem. Use rational persuasion to make sure your team agrees .

2. Break the problem down 

Identifying the problem allows you to see which steps need to be taken to solve it. 

First, break the problem down into achievable blocks. Then, use strategic planning to set a time frame in which to solve the problem and establish a timeline for the completion of each stage.

3. Generate potential solutions

At this stage, the aim isn’t to evaluate possible solutions but to generate as many ideas as possible. 

Encourage your team to use creative thinking and be patient — the best solution may not be the first or most obvious one.

Use one or more of the different strategies in the following section to help come up with solutions — the more creative, the better.

4. Evaluate the possible solutions

Once you’ve generated potential solutions, narrow them down to a shortlist. Then, evaluate the options on your shortlist. 

There are usually many factors to consider. So when evaluating a solution, ask yourself the following questions:

• Will my team be on board with the proposition?
• Does the solution align with organizational goals ?
• Is the solution likely to achieve the desired outcomes?
• Is the solution realistic and possible with current resources and constraints?
• Will the solution solve the problem without causing additional unintended problems?

5. Implement and monitor the solutions

Once you’ve identified your solution and got buy-in from your team, it’s time to implement it. 

But the work doesn’t stop there. You need to monitor your solution to see whether it actually solves your problem. 

Request regular feedback from the team members involved and have a monitoring and evaluation plan in place to measure progress.

If the solution doesn’t achieve your desired results, start this step-by-step process again.

There are many different ways to approach problem-solving. Each is suitable for different types of problems. 

The most appropriate problem-solving techniques will depend on your specific problem. You may need to experiment with several strategies before you find a workable solution.

Here are 10 effective problem-solving strategies for you to try:

• Use a solution that worked before
• Brainstorming
• Work backward
• Use the Kipling method
• Draw the problem
• Use trial and error
• Sleep on it
• Get advice from your peers
• Use the Pareto principle
• Add successful solutions to your toolkit

Let’s break each of these down.

1. Use a solution that worked before

It might seem obvious, but if you’ve faced similar problems in the past, look back to what worked then. See if any of the solutions could apply to your current situation and, if so, replicate them.

2. Brainstorming

The more people you enlist to help solve the problem, the more potential solutions you can come up with.

Use different brainstorming techniques to workshop potential solutions with your team. They’ll likely bring something you haven’t thought of to the table.

3. Work backward

Working backward is a way to reverse engineer your problem. Imagine your problem has been solved, and make that the starting point.

Then, retrace your steps back to where you are now. This can help you see which course of action may be most effective.

4. Use the Kipling method

This is a method that poses six questions based on Rudyard Kipling’s poem, “ I Keep Six Honest Serving Men .” 

• What is the problem?
• Why is the problem important?
• When did the problem arise, and when does it need to be solved?
• How did the problem happen?
• Where is the problem occurring?
• Who does the problem affect?

Answering these questions can help you identify possible solutions.

5. Draw the problem

Sometimes it can be difficult to visualize all the components and moving parts of a problem and its solution. Drawing a diagram can help.

This technique is particularly helpful for solving process-related problems. For example, a product development team might want to decrease the time they take to fix bugs and create new iterations. Drawing the processes involved can help you see where improvements can be made.

6. Use trial-and-error

A trial-and-error approach can be useful when you have several possible solutions and want to test them to see which one works best.

7. Sleep on it

Finding the best solution to a problem is a process. Remember to take breaks and get enough rest . Sometimes, a walk around the block can bring inspiration, but you should sleep on it if possible.

A good night’s sleep helps us find creative solutions to problems. This is because when you sleep, your brain sorts through the day’s events and stores them as memories. This enables you to process your ideas at a subconscious level. 

If possible, give yourself a few days to develop and analyze possible solutions. You may find you have greater clarity after sleeping on it. Your mind will also be fresh, so you’ll be able to make better decisions.

8. Get advice from your peers

Getting input from a group of people can help you find solutions you may not have thought of on your own. 

For solo entrepreneurs or freelancers, this might look like hiring a coach or mentor or joining a mastermind group. 

For leaders , it might be consulting other members of the leadership team or working with a business coach .

It’s important to recognize you might not have all the skills, experience, or knowledge necessary to find a solution alone. 

9. Use the Pareto principle

The Pareto principle — also known as the 80/20 rule — can help you identify possible root causes and potential solutions for your problems.

Although it’s not a mathematical law, it’s a principle found throughout many aspects of business and life. For example, 20% of the sales reps in a company might close 80% of the sales. 

You may be able to narrow down the causes of your problem by applying the Pareto principle. This can also help you identify the most appropriate solutions.

10. Add successful solutions to your toolkit

Every situation is different, and the same solutions might not always work. But by keeping a record of successful problem-solving strategies, you can build up a solutions toolkit. 

These solutions may be applicable to future problems. Even if not, they may save you some of the time and work needed to come up with a new solution.

Improving problem-solving skills is essential for professional development — both yours and your team’s. Here are some of the key skills of effective problem solvers:

• Critical thinking and analytical skills
• Communication skills , including active listening
• Decision-making
• Planning and prioritization
• Emotional intelligence , including empathy and emotional regulation
• Time management
• Data analysis
• Research skills
• Project management

And they see problems as opportunities. Everyone is born with problem-solving skills. But accessing these abilities depends on how we view problems. Effective problem-solvers see problems as opportunities to learn and improve.

Ready to work on your problem-solving abilities? Get started with these seven tips.

1. Build your problem-solving skills

One of the best ways to improve your problem-solving skills is to learn from experts. Consider enrolling in organizational training , shadowing a mentor , or working with a coach .

2. Practice

Practice using your new problem-solving skills by applying them to smaller problems you might encounter in your daily life. 

Alternatively, imagine problematic scenarios that might arise at work and use problem-solving strategies to find hypothetical solutions.

3. Don’t try to find a solution right away

Often, the first solution you think of to solve a problem isn’t the most appropriate or effective.

Instead of thinking on the spot, give yourself time and use one or more of the problem-solving strategies above to activate your creative thinking. 

4. Ask for feedback

Receiving feedback is always important for learning and growth. Your perception of your problem-solving skills may be different from that of your colleagues. They can provide insights that help you improve. 

5. Learn new approaches and methodologies

There are entire books written about problem-solving methodologies if you want to take a deep dive into the subject. 

We recommend starting with “ Fixed — How to Perfect the Fine Art of Problem Solving ” by Amy E. Herman. 

6. Experiment

Tried-and-tested problem-solving techniques can be useful. However, they don’t teach you how to innovate and develop your own problem-solving approaches. 

Sometimes, an unconventional approach can lead to the development of a brilliant new idea or strategy. So don’t be afraid to suggest your most “out there” ideas.

7. Analyze the success of your competitors

Do you have competitors who have already solved the problem you’re facing? Look at what they did, and work backward to solve your own problem. 

For example, Netflix started in the 1990s as a DVD mail-rental company. Its main competitor at the time was Blockbuster. 

But when streaming became the norm in the early 2000s, both companies faced a crisis. Netflix innovated, unveiling its streaming service in 2007. 

If Blockbuster had followed Netflix’s example, it might have survived. Instead, it declared bankruptcy in 2010.

Use problem-solving strategies to uplevel your business

When facing a problem, it’s worth taking the time to find the right solution. 

Otherwise, we risk either running away from our problems or headlong into solutions. When we do this, we might miss out on other, better options.

Use the problem-solving strategies outlined above to find innovative solutions to your business’ most perplexing problems.

If you’re ready to take problem-solving to the next level, request a demo with BetterUp . Our expert coaches specialize in helping teams develop and implement strategies that work.

Boost your productivity

Maximize your time and productivity with strategies from our expert coaches.

Elizabeth Perry, ACC

Elizabeth Perry is a Coach Community Manager at BetterUp. She uses strategic engagement strategies to cultivate a learning community across a global network of Coaches through in-person and virtual experiences, technology-enabled platforms, and strategic coaching industry partnerships. With over 3 years of coaching experience and a certification in transformative leadership and life coaching from Sofia University, Elizabeth leverages transpersonal psychology expertise to help coaches and clients gain awareness of their behavioral and thought patterns, discover their purpose and passions, and elevate their potential. She is a lifelong student of psychology, personal growth, and human potential as well as an ICF-certified ACC transpersonal life and leadership Coach.

8 creative solutions to your most challenging problems

5 problem-solving questions to prepare you for your next interview, what are metacognitive skills examples in everyday life, 31 examples of problem solving performance review phrases, what is lateral thinking 7 techniques to encourage creative ideas, learn what process mapping is and how to create one (+ examples), leadership activities that encourage employee engagement, how much do distractions cost 8 effects of lack of focus, can dreams help you solve problems 6 ways to try, similar articles, the pareto principle: how the 80/20 rule can help you do more with less, thinking outside the box: 8 ways to become a creative problem solver, experimentation brings innovation: create an experimental workplace, effective problem statements have these 5 components, contingency planning: 4 steps to prepare for the unexpected, stay connected with betterup, get our newsletter, event invites, plus product insights and research..

3100 E 5th Street, Suite 350 Austin, TX 78702

• Platform Overview
• Integrations
• Powered by AI
• BetterUp Lead
• BetterUp Manage™
• BetterUp Care™
• Sales Performance
• Diversity & Inclusion
• Case Studies
• Why BetterUp?
• About Coaching
• Find your Coach
• Career Coaching
• Communication Coaching
• Life Coaching
• News and Press
• Leadership Team
• Become a BetterUp Coach
• BetterUp Labs
• Center for Purpose & Performance
• Leadership Training
• Business Coaching
• Contact Support
• Contact Sales
• Privacy Policy
• Acceptable Use Policy
• Trust & Security
• Cookie Preferences

• Book a Demo

Struggling to overcome challenges in your life? We all face problems, big and small, on a regular basis.

So how do you tackle them effectively? What are some key problem-solving strategies and skills that can guide you?

Effective problem-solving requires breaking issues down logically, generating solutions creatively, weighing choices critically, and adapting plans flexibly based on outcomes. Useful strategies range from leveraging past solutions that have worked to visualizing problems through diagrams. Core skills include analytical abilities, innovative thinking, and collaboration.

Want to improve your problem-solving skills? Keep reading to find out 17 effective problem-solving strategies, key skills, common obstacles to watch for, and tips on improving your overall problem-solving skills.

Key Takeaways:

• Effective problem-solving requires breaking down issues logically, generating multiple solutions creatively, weighing choices critically, and adapting plans based on outcomes.
• Useful problem-solving strategies range from leveraging past solutions to brainstorming with groups to visualizing problems through diagrams and models.
• Core skills include analytical abilities, innovative thinking, decision-making, and team collaboration to solve problems.
• Common obstacles include fear of failure, information gaps, fixed mindsets, confirmation bias, and groupthink.
• Boosting problem-solving skills involves learning from experts, actively practicing, soliciting feedback, and analyzing others’ success.
• Onethread’s project management capabilities align with effective problem-solving tenets – facilitating structured solutions, tracking progress, and capturing lessons learned.

What Is Problem-Solving?

Problem-solving is the process of understanding an issue, situation, or challenge that needs to be addressed and then systematically working through possible solutions to arrive at the best outcome.

It involves critical thinking, analysis, logic, creativity, research, planning, reflection, and patience in order to overcome obstacles and find effective answers to complex questions or problems.

The ultimate goal is to implement the chosen solution successfully.

What Are Problem-Solving Strategies?

Problem-solving strategies are like frameworks or methodologies that help us solve tricky puzzles or problems we face in the workplace, at home, or with friends.

Imagine you have a big jigsaw puzzle. One strategy might be to start with the corner pieces. Another could be looking for pieces with the same colors. 

Just like in puzzles, in real life, we use different plans or steps to find solutions to problems. These strategies help us think clearly, make good choices, and find the best answers without getting too stressed or giving up.

Why Is It Important To Know Different Problem-Solving Strategies?

Knowing different problem-solving strategies is important because different types of problems often require different approaches to solve them effectively. Having a variety of strategies to choose from allows you to select the best method for the specific problem you are trying to solve.

This improves your ability to analyze issues thoroughly, develop solutions creatively, and tackle problems from multiple angles. Knowing multiple strategies also aids in overcoming roadblocks if your initial approach is not working.

Here are some reasons why you need to know different problem-solving strategies:

• Different Problems Require Different Tools: Just like you can’t use a hammer to fix everything, some problems need specific strategies to solve them.
• Improves Creativity: Knowing various strategies helps you think outside the box and come up with creative solutions.
• Saves Time: With the right strategy, you can solve problems faster instead of trying things that don’t work.
• Reduces Stress: When you know how to tackle a problem, it feels less scary and you feel more confident.
• Better Outcomes: Using the right strategy can lead to better solutions, making things work out better in the end.
• Learning and Growth: Each time you solve a problem, you learn something new, which makes you smarter and better at solving future problems.

Knowing different ways to solve problems helps you tackle anything that comes your way, making life a bit easier and more fun!

17 Effective Problem-Solving Strategies

Effective problem-solving strategies include breaking the problem into smaller parts, brainstorming multiple solutions, evaluating the pros and cons of each, and choosing the most viable option. 

Critical thinking and creativity are essential in developing innovative solutions. Collaboration with others can also provide diverse perspectives and ideas. 

By applying these strategies, you can tackle complex issues more effectively.

Now, consider a challenge you’re dealing with. Which strategy could help you find a solution? Here we will discuss key problem strategies in detail.

1. Use a Past Solution That Worked

This strategy involves looking back at previous similar problems you have faced and the solutions that were effective in solving them.

It is useful when you are facing a problem that is very similar to something you have already solved. The main benefit is that you don’t have to come up with a brand new solution – you already know the method that worked before will likely work again.

However, the limitation is that the current problem may have some unique aspects or differences that mean your old solution is not fully applicable.

The ideal process is to thoroughly analyze the new challenge, identify the key similarities and differences versus the past case, adapt the old solution as needed to align with the current context, and then pilot it carefully before full implementation.

An example is using the same negotiation tactics from purchasing your previous home when putting in an offer on a new house. Key terms would be adjusted but overall it can save significant time versus developing a brand new strategy.

2. Brainstorm Solutions

This involves gathering a group of people together to generate as many potential solutions to a problem as possible.

It is effective when you need creative ideas to solve a complex or challenging issue. By getting input from multiple people with diverse perspectives, you increase the likelihood of finding an innovative solution.

The main limitation is that brainstorming sessions can sometimes turn into unproductive gripe sessions or discussions rather than focusing on productive ideation —so they need to be properly facilitated.

The key to an effective brainstorming session is setting some basic ground rules upfront and having an experienced facilitator guide the discussion. Rules often include encouraging wild ideas, avoiding criticism of ideas during the ideation phase, and building on others’ ideas.

For instance, a struggling startup might hold a session where ideas for turnaround plans are generated and then formalized with financials and metrics.

3. Work Backward from the Solution

This technique involves envisioning that the problem has already been solved and then working step-by-step backward toward the current state.

This strategy is particularly helpful for long-term, multi-step problems. By starting from the imagined solution and identifying all the steps required to reach it, you can systematically determine the actions needed. It lets you tackle a big hairy problem through smaller, reversible steps.

A limitation is that this approach may not be possible if you cannot accurately envision the solution state to start with.

The approach helps drive logical systematic thinking for complex problem-solving, but should still be combined with creative brainstorming of alternative scenarios and solutions.

An example is planning for an event – you would imagine the successful event occurring, then determine the tasks needed the week before, two weeks before, etc. all the way back to the present.

4. Use the Kipling Method

This method, named after author Rudyard Kipling, provides a framework for thoroughly analyzing a problem before jumping into solutions.

It consists of answering six fundamental questions: What, Where, When, How, Who, and Why about the challenge. Clearly defining these core elements of the problem sets the stage for generating targeted solutions.

The Kipling method enables a deep understanding of problem parameters and root causes before solution identification. By jumping to brainstorm solutions too early, critical information can be missed or the problem is loosely defined, reducing solution quality.

Answering the six fundamental questions illuminates all angles of the issue. This takes time but pays dividends in generating optimal solutions later tuned precisely to the true underlying problem.

The limitation is that meticulously working through numerous questions before addressing solutions can slow progress.

The best approach blends structured problem decomposition techniques like the Kipling method with spurring innovative solution ideation from a diverse team. 

An example is using this technique after a technical process failure – the team would systematically detail What failed, Where/When did it fail, How it failed (sequence of events), Who was involved, and Why it likely failed before exploring preventative solutions.

5. Try Different Solutions Until One Works (Trial and Error)

This technique involves attempting various potential solutions sequentially until finding one that successfully solves the problem.

Trial and error works best when facing a concrete, bounded challenge with clear solution criteria and a small number of discrete options to try. By methodically testing solutions, you can determine the faulty component.

A limitation is that it can be time-intensive if the working solution set is large.

The key is limiting the variable set first. For technical problems, this boundary is inherent and each element can be iteratively tested. But for business issues, artificial constraints may be required – setting decision rules upfront to reduce options before testing.

Furthermore, hypothesis-driven experimentation is far superior to blind trial and error – have logic for why Option A may outperform Option B.

Examples include fixing printer jams by testing different paper tray and cable configurations or resolving website errors by tweaking CSS/HTML line-by-line until the code functions properly.

6. Use Proven Formulas or Frameworks (Heuristics)

Heuristics refers to applying existing problem-solving formulas or frameworks rather than addressing issues completely from scratch.

This allows leveraging established best practices rather than reinventing the wheel each time.

It is effective when facing recurrent, common challenges where proven structured approaches exist.

However, heuristics may force-fit solutions to non-standard problems.

For example, a cost-benefit analysis can be used instead of custom weighting schemes to analyze potential process improvements.

Onethread allows teams to define, save, and replicate configurable project templates so proven workflows can be reliably applied across problems with some consistency rather than fully custom one-off approaches each time.

Try One thread

Experience One thread full potential, with all its features unlocked. Sign up now to start your 14-day free trial!

7. Trust Your Instincts (Insight Problem-Solving)

Insight is a problem-solving technique that involves waiting patiently for an unexpected “aha moment” when the solution pops into your mind.

It works well for personal challenges that require intuitive realizations over calculated logic. The unconscious mind makes connections leading to flashes of insight when relaxing or doing mundane tasks unrelated to the actual problem.

Benefits include out-of-the-box creative solutions. However, the limitations are that insights can’t be forced and may never come at all if too complex. Critical analysis is still required after initial insights.

A real-life example would be a writer struggling with how to end a novel. Despite extensive brainstorming, they feel stuck. Eventually while gardening one day, a perfect unexpected plot twist sparks an ideal conclusion. However, once written they still carefully review if the ending flows logically from the rest of the story.

8. Reverse Engineer the Problem

This approach involves deconstructing a problem in reverse sequential order from the current undesirable outcome back to the initial root causes.

By mapping the chain of events backward, you can identify the origin of where things went wrong and establish the critical junctures for solving it moving ahead. Reverse engineering provides diagnostic clarity on multi-step problems.

However, the limitation is that it focuses heavily on autopsying the past versus innovating improved future solutions.

An example is tracing back from a server outage, through the cascade of infrastructure failures that led to it finally terminating at the initial script error that triggered the crisis. This root cause would then inform the preventative measure.

9. Break Down Obstacles Between Current and Goal State (Means-End Analysis)

This technique defines the current problem state and the desired end goal state, then systematically identifies obstacles in the way of getting from one to the other.

By mapping the barriers or gaps, you can then develop solutions to address each one. This methodically connects the problem to solutions.

A limitation is that some obstacles may be unknown upfront and only emerge later.

For example, you can list down all the steps required for a new product launch – current state through production, marketing, sales, distribution, etc. to full launch (goal state) – to highlight where resource constraints or other blocks exist so they can be addressed.

Onethread allows dividing big-picture projects into discrete, manageable phases, milestones, and tasks to simplify execution just as problems can be decomposed into more achievable components. Features like dependency mapping further reinforce interconnections.

Using Onethread’s issues and subtasks feature, messy problems can be decomposed into manageable chunks.

10. Ask “Why” Five Times to Identify the Root Cause (The 5 Whys)

This technique involves asking “Why did this problem occur?” and then responding with an answer that is again met with asking “Why?” This process repeats five times until the root cause is revealed.

Continually asking why digs deeper from surface symptoms to underlying systemic issues.

It is effective for getting to the source of problems originating from human error or process breakdowns.

However, some complex issues may have multiple tangled root causes not solvable through this approach alone.

An example is a retail store experiencing a sudden decline in customers. Successively asking why five times may trace an initial drop to parking challenges, stemming from a city construction project – the true starting point to address.

11. Evaluate Strengths, Weaknesses, Opportunities, and Threats (SWOT Analysis)

This involves analyzing a problem or proposed solution by categorizing internal and external factors into a 2×2 matrix: Strengths, Weaknesses as the internal rows; Opportunities and Threats as the external columns.

Systematically identifying these elements provides balanced insight to evaluate options and risks. It is impactful when evaluating alternative solutions or developing strategy amid complexity or uncertainty.

The key benefit of SWOT analysis is enabling multi-dimensional thinking when rationally evaluating options. Rather than getting anchored on just the upsides or the existing way of operating, it urges a systematic assessment through four different lenses:

• Internal Strengths: Our core competencies/advantages able to deliver success
• Internal Weaknesses: Gaps/vulnerabilities we need to manage
• External Opportunities: Ways we can differentiate/drive additional value
• External Threats: Risks we must navigate or mitigate

Multiperspective analysis provides the needed holistic view of the balanced risk vs. reward equation for strategic decision making amid uncertainty.

However, SWOT can feel restrictive if not tailored and evolved for different issue types.

Teams should view SWOT analysis as a starting point, augmenting it further for distinct scenarios.

An example is performing a SWOT analysis on whether a small business should expand into a new market – evaluating internal capabilities to execute vs. risks in the external competitive and demand environment to inform the growth decision with eyes wide open.

12. Compare Current vs Expected Performance (Gap Analysis)

This technique involves comparing the current state of performance, output, or results to the desired or expected levels to highlight shortfalls.

By quantifying the gaps, you can identify problem areas and prioritize address solutions.

Gap analysis is based on the simple principle – “you can’t improve what you don’t measure.” It enables facts-driven problem diagnosis by highlighting delta to goals, not just vague dissatisfaction that something seems wrong. And measurement immediately suggests improvement opportunities – address the biggest gaps first.

This data orientation also supports ROI analysis on fixing issues – the return from closing larger gaps outweighs narrowly targeting smaller performance deficiencies.

However, the approach is only effective if robust standards and metrics exist as the benchmark to evaluate against. Organizations should invest upfront in establishing performance frameworks.

Furthermore, while numbers are invaluable, the human context behind problems should not be ignored – quantitative versus qualitative gap assessment is optimally blended.

For example, if usage declines are noted during software gap analysis, this could be used as a signal to improve user experience through design.

13. Observe Processes from the Frontline (Gemba Walk)

A Gemba walk involves going to the actual place where work is done, directly observing the process, engaging with employees, and finding areas for improvement.

By experiencing firsthand rather than solely reviewing abstract reports, practical problems and ideas emerge.

The limitation is Gemba walks provide anecdotes not statistically significant data. It complements but does not replace comprehensive performance measurement.

An example is a factory manager inspecting the production line to spot jam areas based on direct reality rather than relying on throughput dashboards alone back in her office. Frontline insights prove invaluable.

14. Analyze Competitive Forces (Porter’s Five Forces)

This involves assessing the marketplace around a problem or business situation via five key factors: competitors, new entrants, substitute offerings, suppliers, and customer power.

Evaluating these forces illuminates risks and opportunities for strategy development and issue resolution. It is effective for understanding dynamic external threats and opportunities when operating in a contested space.

However, over-indexing on only external factors can overlook the internal capabilities needed to execute solutions.

A startup CEO, for example, may analyze market entry barriers, whitespace opportunities, and disruption risks across these five forces to shape new product rollout strategies and marketing approaches.

15. Think from Different Perspectives (Six Thinking Hats)

The Six Thinking Hats is a technique developed by Edward de Bono that encourages people to think about a problem from six different perspectives, each represented by a colored “thinking hat.”

The key benefit of this strategy is that it pushes team members to move outside their usual thinking style and consider new angles. This brings more diverse ideas and solutions to the table.

It works best for complex problems that require innovative solutions and when a team is stuck in an unproductive debate. The structured framework keeps the conversation flowing in a positive direction.

Limitations are that it requires training on the method itself and may feel unnatural at first. Team dynamics can also influence success – some members may dominate certain “hats” while others remain quiet.

A real-life example is a software company debating whether to build a new feature. The white hat focuses on facts, red on gut feelings, black on potential risks, yellow on benefits, green on new ideas, and blue on process. This exposes more balanced perspectives before deciding.

Onethread centralizes diverse stakeholder communication onto one platform, ensuring all voices are incorporated when evaluating project tradeoffs, just as problem-solving should consider multifaceted solutions.

16. Visualize the Problem (Draw it Out)

Drawing out a problem involves creating visual representations like diagrams, flowcharts, and maps to work through challenging issues.

This strategy is helpful when dealing with complex situations with lots of interconnected components. The visuals simplify the complexity so you can thoroughly understand the problem and all its nuances.

Key benefits are that it allows more stakeholders to get on the same page regarding root causes and it sparks new creative solutions as connections are made visually.

However, simple problems with few variables don’t require extensive diagrams. Additionally, some challenges are so multidimensional that fully capturing every aspect is difficult.

A real-life example would be mapping out all the possible causes leading to decreased client satisfaction at a law firm. An intricate fishbone diagram with branches for issues like service delivery, technology, facilities, culture, and vendor partnerships allows the team to trace problems back to their origins and brainstorm targeted fixes.

17. Follow a Step-by-Step Procedure (Algorithms)

An algorithm is a predefined step-by-step process that is guaranteed to produce the correct solution if implemented properly.

Using algorithms is effective when facing problems that have clear, binary right and wrong answers. Algorithms work for mathematical calculations, computer code, manufacturing assembly lines, and scientific experiments.

Key benefits are consistency, accuracy, and efficiency. However, they require extensive upfront development and only apply to scenarios with strict parameters. Additionally, human error can lead to mistakes.

For example, crew members of fast food chains like McDonald’s follow specific algorithms for food prep – from grill times to ingredient amounts in sandwiches, to order fulfillment procedures. This ensures uniform quality and service across all locations. However, if a step is missed, errors occur.

The Problem-Solving Process

The problem-solving process typically includes defining the issue, analyzing details, creating solutions, weighing choices, acting, and reviewing results.

In the above, we have discussed several problem-solving strategies. For every problem-solving strategy, you have to follow these processes. Here’s a detailed step-by-step process of effective problem-solving:

Step 1: Identify the Problem

The problem-solving process starts with identifying the problem. This step involves understanding the issue’s nature, its scope, and its impact. Once the problem is clearly defined, it sets the foundation for finding effective solutions.

Identifying the problem is crucial. It means figuring out exactly what needs fixing. This involves looking at the situation closely, understanding what’s wrong, and knowing how it affects things. It’s about asking the right questions to get a clear picture of the issue. 

This step is important because it guides the rest of the problem-solving process. Without a clear understanding of the problem, finding a solution is much harder. It’s like diagnosing an illness before treating it. Once the problem is identified accurately, you can move on to exploring possible solutions and deciding on the best course of action.

Step 2: Break Down the Problem

Breaking down the problem is a key step in the problem-solving process. It involves dividing the main issue into smaller, more manageable parts. This makes it easier to understand and tackle each component one by one.

After identifying the problem, the next step is to break it down. This means splitting the big issue into smaller pieces. It’s like solving a puzzle by handling one piece at a time. 

By doing this, you can focus on each part without feeling overwhelmed. It also helps in identifying the root causes of the problem. Breaking down the problem allows for a clearer analysis and makes finding solutions more straightforward. 

Each smaller problem can be addressed individually, leading to an effective resolution of the overall issue. This approach not only simplifies complex problems but also aids in developing a systematic plan to solve them.

Step 3: Come up with potential solutions

Coming up with potential solutions is the third step in the problem-solving process. It involves brainstorming various options to address the problem, considering creativity and feasibility to find the best approach.

After breaking down the problem, it’s time to think of ways to solve it. This stage is about brainstorming different solutions. You look at the smaller issues you’ve identified and start thinking of ways to fix them. This is where creativity comes in. 

You want to come up with as many ideas as possible, no matter how out-of-the-box they seem. It’s important to consider all options and evaluate their pros and cons. This process allows you to gather a range of possible solutions. 

Later, you can narrow these down to the most practical and effective ones. This step is crucial because it sets the stage for deciding on the best solution to implement. It’s about being open-minded and innovative to tackle the problem effectively.

Step 4: Analyze the possible solutions

Analyzing the possible solutions is the fourth step in the problem-solving process. It involves evaluating each proposed solution’s advantages and disadvantages to determine the most effective and feasible option.

After coming up with potential solutions, the next step is to analyze them. This means looking closely at each idea to see how well it solves the problem. You weigh the pros and cons of every solution.

Consider factors like cost, time, resources, and potential outcomes. This analysis helps in understanding the implications of each option. It’s about being critical and objective, ensuring that the chosen solution is not only effective but also practical.

This step is vital because it guides you towards making an informed decision. It involves comparing the solutions against each other and selecting the one that best addresses the problem.

By thoroughly analyzing the options, you can move forward with confidence, knowing you’ve chosen the best path to solve the issue.

Step 5: Implement and Monitor the Solutions

Implementing and monitoring the solutions is the final step in the problem-solving process. It involves putting the chosen solution into action and observing its effectiveness, making adjustments as necessary.

Once you’ve selected the best solution, it’s time to put it into practice. This step is about action. You implement the chosen solution and then keep an eye on how it works. Monitoring is crucial because it tells you if the solution is solving the problem as expected. 

If things don’t go as planned, you may need to make some changes. This could mean tweaking the current solution or trying a different one. The goal is to ensure the problem is fully resolved. 

This step is critical because it involves real-world application. It’s not just about planning; it’s about doing and adjusting based on results. By effectively implementing and monitoring the solutions, you can achieve the desired outcome and solve the problem successfully.

Why This Process is Important

Following a defined process to solve problems is important because it provides a systematic, structured approach instead of a haphazard one. Having clear steps guides logical thinking, analysis, and decision-making to increase effectiveness. Key reasons it helps are:

• Clear Direction: This process gives you a clear path to follow, which can make solving problems less overwhelming.
• Better Solutions: Thoughtful analysis of root causes, iterative testing of solutions, and learning orientation lead to addressing the heart of issues rather than just symptoms.
• Saves Time and Energy: Instead of guessing or trying random things, this process helps you find a solution more efficiently.
• Improves Skills: The more you use this process, the better you get at solving problems. It’s like practicing a sport. The more you practice, the better you play.
• Maximizes collaboration: Involving various stakeholders in the process enables broader inputs. Their communication and coordination are streamlined through organized brainstorming and evaluation.
• Provides consistency: Standard methodology across problems enables building institutional problem-solving capabilities over time. Patterns emerge on effective techniques to apply to different situations.

The problem-solving process is a powerful tool that can help us tackle any challenge we face. By following these steps, we can find solutions that work and learn important skills along the way.

Key Skills for Efficient Problem Solving

Efficient problem-solving requires breaking down issues logically, evaluating options, and implementing practical solutions.

Key skills include critical thinking to understand root causes, creativity to brainstorm innovative ideas, communication abilities to collaborate with others, and decision-making to select the best way forward. Staying adaptable, reflecting on outcomes, and applying lessons learned are also essential.

With practice, these capacities will lead to increased personal and team effectiveness in systematically addressing any problem.

 Let’s explore the powers you need to become a problem-solving hero!

Critical Thinking and Analytical Skills

Critical thinking and analytical skills are vital for efficient problem-solving as they enable individuals to objectively evaluate information, identify key issues, and generate effective solutions. 

These skills facilitate a deeper understanding of problems, leading to logical, well-reasoned decisions. By systematically breaking down complex issues and considering various perspectives, individuals can develop more innovative and practical solutions, enhancing their problem-solving effectiveness.

Communication Skills

Effective communication skills are essential for efficient problem-solving as they facilitate clear sharing of information, ensuring all team members understand the problem and proposed solutions. 

These skills enable individuals to articulate issues, listen actively, and collaborate effectively, fostering a productive environment where diverse ideas can be exchanged and refined. By enhancing mutual understanding, communication skills contribute significantly to identifying and implementing the most viable solutions.

Decision-Making

Strong decision-making skills are crucial for efficient problem-solving, as they enable individuals to choose the best course of action from multiple alternatives. 

These skills involve evaluating the potential outcomes of different solutions, considering the risks and benefits, and making informed choices. Effective decision-making leads to the implementation of solutions that are likely to resolve problems effectively, ensuring resources are used efficiently and goals are achieved.

Planning and Prioritization

Planning and prioritization are key for efficient problem-solving, ensuring resources are allocated effectively to address the most critical issues first. This approach helps in organizing tasks according to their urgency and impact, streamlining efforts towards achieving the desired outcome efficiently.

Emotional Intelligence

Emotional intelligence enhances problem-solving by allowing individuals to manage emotions, understand others, and navigate social complexities. It fosters a positive, collaborative environment, essential for generating creative solutions and making informed, empathetic decisions.

Leadership skills drive efficient problem-solving by inspiring and guiding teams toward common goals. Effective leaders motivate their teams, foster innovation, and navigate challenges, ensuring collective efforts are focused and productive in addressing problems.

Time Management

Time management is crucial in problem-solving, enabling individuals to allocate appropriate time to each task. By efficiently managing time, one can ensure that critical problems are addressed promptly without neglecting other responsibilities.

Data Analysis

Data analysis skills are essential for problem-solving, as they enable individuals to sift through data, identify trends, and extract actionable insights. This analytical approach supports evidence-based decision-making, leading to more accurate and effective solutions.

Research Skills

Research skills are vital for efficient problem-solving, allowing individuals to gather relevant information, explore various solutions, and understand the problem’s context. This thorough exploration aids in developing well-informed, innovative solutions.

Becoming a great problem solver takes practice, but with these skills, you’re on your way to becoming a problem-solving hero. 

How to Improve Your Problem-Solving Skills?

Improving your problem-solving skills can make you a master at overcoming challenges. Learn from experts, practice regularly, welcome feedback, try new methods, experiment, and study others’ success to become better.

Learning from Experts

Improving problem-solving skills by learning from experts involves seeking mentorship, attending workshops, and studying case studies. Experts provide insights and techniques that refine your approach, enhancing your ability to tackle complex problems effectively.

To enhance your problem-solving skills, learning from experts can be incredibly beneficial. Engaging with mentors, participating in specialized workshops, and analyzing case studies from seasoned professionals can offer valuable perspectives and strategies. 

Experts share their experiences, mistakes, and successes, providing practical knowledge that can be applied to your own problem-solving process. This exposure not only broadens your understanding but also introduces you to diverse methods and approaches, enabling you to tackle challenges more efficiently and creatively.

Improving problem-solving skills through practice involves tackling a variety of challenges regularly. This hands-on approach helps in refining techniques and strategies, making you more adept at identifying and solving problems efficiently.

One of the most effective ways to enhance your problem-solving skills is through consistent practice. By engaging with different types of problems on a regular basis, you develop a deeper understanding of various strategies and how they can be applied. 

This hands-on experience allows you to experiment with different approaches, learn from mistakes, and build confidence in your ability to tackle challenges.

Regular practice not only sharpens your analytical and critical thinking skills but also encourages adaptability and innovation, key components of effective problem-solving.

Openness to Feedback

Being open to feedback is like unlocking a secret level in a game. It helps you boost your problem-solving skills. Improving problem-solving skills through openness to feedback involves actively seeking and constructively responding to critiques. 

This receptivity enables you to refine your strategies and approaches based on insights from others, leading to more effective solutions. 

Learning New Approaches and Methodologies

Learning new approaches and methodologies is like adding new tools to your toolbox. It makes you a smarter problem-solver. Enhancing problem-solving skills by learning new approaches and methodologies involves staying updated with the latest trends and techniques in your field. 

This continuous learning expands your toolkit, enabling innovative solutions and a fresh perspective on challenges.

Experimentation

Experimentation is like being a scientist of your own problems. It’s a powerful way to improve your problem-solving skills. Boosting problem-solving skills through experimentation means trying out different solutions to see what works best. This trial-and-error approach fosters creativity and can lead to unique solutions that wouldn’t have been considered otherwise.

Analyzing Competitors’ Success

Analyzing competitors’ success is like being a detective. It’s a smart way to boost your problem-solving skills. Improving problem-solving skills by analyzing competitors’ success involves studying their strategies and outcomes. Understanding what worked for them can provide valuable insights and inspire effective solutions for your own challenges. 

Challenges in Problem-Solving

Facing obstacles when solving problems is common. Recognizing these barriers, like fear of failure or lack of information, helps us find ways around them for better solutions.

Fear of Failure

Fear of failure is like a big, scary monster that stops us from solving problems. It’s a challenge many face. Because being afraid of making mistakes can make us too scared to try new solutions. 

How can we overcome this? First, understand that it’s okay to fail. Failure is not the opposite of success; it’s part of learning. Every time we fail, we discover one more way not to solve a problem, getting us closer to the right solution. Treat each attempt like an experiment. It’s not about failing; it’s about testing and learning.

Lack of Information

Lack of information is like trying to solve a puzzle with missing pieces. It’s a big challenge in problem-solving. Because without all the necessary details, finding a solution is much harder. 

How can we fix this? Start by gathering as much information as you can. Ask questions, do research, or talk to experts. Think of yourself as a detective looking for clues. The more information you collect, the clearer the picture becomes. Then, use what you’ve learned to think of solutions. 

Fixed Mindset

A fixed mindset is like being stuck in quicksand; it makes solving problems harder. It means thinking you can’t improve or learn new ways to solve issues. 

How can we change this? First, believe that you can grow and learn from challenges. Think of your brain as a muscle that gets stronger every time you use it. When you face a problem, instead of saying “I can’t do this,” try thinking, “I can’t do this yet.” Look for lessons in every challenge and celebrate small wins. 

Everyone starts somewhere, and mistakes are just steps on the path to getting better. By shifting to a growth mindset, you’ll see problems as opportunities to grow. Keep trying, keep learning, and your problem-solving skills will soar!

Jumping to Conclusions

Jumping to conclusions is like trying to finish a race before it starts. It’s a challenge in problem-solving. That means making a decision too quickly without looking at all the facts. 

How can we avoid this? First, take a deep breath and slow down. Think about the problem like a puzzle. You need to see all the pieces before you know where they go. Ask questions, gather information, and consider different possibilities. Don’t choose the first solution that comes to mind. Instead, compare a few options. 

Feeling Overwhelmed

Feeling overwhelmed is like being buried under a mountain of puzzles. It’s a big challenge in problem-solving. When we’re overwhelmed, everything seems too hard to handle. 

How can we deal with this? Start by taking a step back. Breathe deeply and focus on one thing at a time. Break the big problem into smaller pieces, like sorting puzzle pieces by color. Tackle each small piece one by one. It’s also okay to ask for help. Sometimes, talking to someone else can give you a new perspective. 

Confirmation Bias

Confirmation bias is like wearing glasses that only let you see what you want to see. It’s a challenge in problem-solving. Because it makes us focus only on information that agrees with what we already believe, ignoring anything that doesn’t. 

How can we overcome this? First, be aware that you might be doing it. It’s like checking if your glasses are on right. Then, purposely look for information that challenges your views. It’s like trying on a different pair of glasses to see a new perspective. Ask questions and listen to answers, even if they don’t fit what you thought before.

Groupthink is like everyone in a group deciding to wear the same outfit without asking why. It’s a challenge in problem-solving. It means making decisions just because everyone else agrees, without really thinking it through. 

How can we avoid this? First, encourage everyone in the group to share their ideas, even if they’re different. It’s like inviting everyone to show their unique style of clothes. 

Listen to all opinions and discuss them. It’s okay to disagree; it helps us think of better solutions. Also, sometimes, ask someone outside the group for their thoughts. They might see something everyone in the group missed.

Overcoming obstacles in problem-solving requires patience, openness, and a willingness to learn from mistakes. By recognizing these barriers, we can develop strategies to navigate around them, leading to more effective and creative solutions.

What are the most common problem-solving techniques?

The most common techniques include brainstorming, the 5 Whys, mind mapping, SWOT analysis, and using algorithms or heuristics. Each approach has its strengths, suitable for different types of problems.

What’s the best problem-solving strategy for every situation?

There’s no one-size-fits-all strategy. The best approach depends on the problem’s complexity, available resources, and time constraints. Combining multiple techniques often yields the best results.

How can I improve my problem-solving skills?

Improve your problem-solving skills by practicing regularly, learning from experts, staying open to feedback, and continuously updating your knowledge on new approaches and methodologies.

Are there any tools or resources to help with problem-solving?

Yes, tools like mind mapping software, online courses on critical thinking, and books on problem-solving techniques can be very helpful. Joining forums or groups focused on problem-solving can also provide support and insights.

What are some common mistakes people make when solving problems?

Common mistakes include jumping to conclusions without fully understanding the problem, ignoring valuable feedback, sticking to familiar solutions without considering alternatives, and not breaking down complex problems into manageable parts.

Final Words

Mastering problem-solving strategies equips us with the tools to tackle challenges across all areas of life. By understanding and applying these techniques, embracing a growth mindset, and learning from both successes and obstacles, we can transform problems into opportunities for growth. Continuously improving these skills ensures we’re prepared to face and solve future challenges more effectively.

Let's Get Started with Onethread

Onethread empowers you to plan, organise, and track projects with ease, ensuring you meet deadlines, allocate resources efficiently, and keep progress transparent.

By subscribing you agree to our  Privacy Policy .

Giving modern marketing teams superpowers with short links that stand out.

• Live Product Demo

© Copyright 2023 Onethread, Inc

How to Solve Coding Problems with a Simple Four Step Method

I had fifteen minutes left, and I knew I was going to fail.

I had spent two months studying for my first technical interview.

I thought I was prepared, but as the interview came to a close, it hit me: I had no idea how to solve coding problems.

Of all the tutorials I had taken when I was learning to code, not one of them had included an approach to solving coding problems.

I had to find a method for problem-solving—my career as a developer depended on it.

I immediately began researching methods. And I found one. In fact, what I uncovered was an invaluable strategy. It was a time-tested four-step method that was somehow under the radar in the developer ecosystem.

In this article, I’ll go over this four-step problem-solving method that you can use to start confidently solving coding problems.

Solving coding problems is not only part of the developer job interview process—it’s what a developer does all day. After all, writing code is problem-solving.

A method for solving problems

This method is from the book How to Solve It by George Pólya. It originally came out in 1945 and has sold over one million copies.

His problem-solving method has been used and taught by many programmers, from computer science professors (see Udacity’s Intro to CS course taught by professor David Evans) to modern web development teachers like Colt Steele.

Let’s walk through solving a simple coding problem using the four-step problem-solving method. This allows us to see the method in action as we learn it. We'll use JavaScript as our language of choice. Here’s the problem:

Create a function that adds together two numbers and returns that value. There are four steps to the problem-solving method:

• Understand the problem.
• Devise a plan.
• Carry out the plan.

Let’s get started with step one.

Step 1: Understand the problem.

When given a coding problem in an interview, it’s tempting to rush into coding. This is hard to avoid, especially if you have a time limit.

However, try to resist this urge. Make sure you actually understand the problem before you get started with solving it.

Read through the problem. If you’re in an interview, you could read through the problem out loud if that helps you slow down.

As you read through the problem, clarify any part of it you do not understand. If you’re in an interview, you can do this by asking your interviewer questions about the problem description. If you’re on your own, think through and/or Google parts of the question you might not understand.

This first step is vital as we often don’t take the time to fully understand the problem. When you don’t fully understand the problem, you’ll have a much harder time solving it.

To help you better understand the problem, ask yourself:

What are the inputs?

What kinds of inputs will go into this problem? In this example, the inputs are the arguments that our function will take.

Just from reading the problem description so far, we know that the inputs will be numbers. But to be more specific about what the inputs will be, we can ask:

Will the inputs always be just two numbers? What should happen if our function receives as input three numbers?

Here we could ask the interviewer for clarification, or look at the problem description further.

The coding problem might have a note saying, “You should only ever expect two inputs into the function.” If so, you know how to proceed. You can get more specific, as you’ll likely realize that you need to ask more questions on what kinds of inputs you might be receiving.

Will the inputs always be numbers? What should our function do if we receive the inputs “a” and “b”? Clarify whether or not our function will always take in numbers.

Optionally, you could write down possible inputs in a code comment to get a sense of what they’ll look like:

//inputs: 2, 4

What are the outputs?

What will this function return? In this case, the output will be one number that is the result of the two number inputs. Make sure you understand what your outputs will be.

Create some examples.

Once you have a grasp of the problem and know the possible inputs and outputs, you can start working on some concrete examples.

Examples can also be used as sanity checks to test your eventual problem. Most code challenge editors that you’ll work in (whether it’s in an interview or just using a site like Codewars or HackerRank) have examples or test cases already written for you. Even so, writing out your own examples can help you cement your understanding of the problem.

Start with a simple example or two of possible inputs and outputs. Let's return to our addition function.

Let’s call our function “add.”

What’s an example input? Example input might be:

// add(2, 3)

What is the output to this? To write the example output, we can write:

// add(2, 3) ---> 5

This indicates that our function will take in an input of 2 and 3 and return 5 as its output.

Create complex examples.

By walking through more complex examples, you can take the time to look for edge cases you might need to account for.

For example, what should we do if our inputs are strings instead of numbers? What if we have as input two strings, for example, add('a', 'b')?

Your interviewer might possibly tell you to return an error message if there are any inputs that are not numbers. If so, you can add a code comment to handle this case if it helps you remember you need to do this.

Your interviewer might also tell you to assume that your inputs will always be numbers, in which case you don’t need to write any extra code to handle this particular input edge case.

If you don’t have an interviewer and you’re just solving this problem, the problem might say what happens when you enter invalid inputs.

For example, some problems will say, “If there are zero inputs, return undefined.” For cases like this, you can optionally write a comment.

// check if there are no inputs.

// If no inputs, return undefined.

For our purposes, we’ll assume that our inputs will always be numbers. But generally, it’s good to think about edge cases.

Computer science professor Evans says to write what developers call defensive code. Think about what could go wrong and how your code could defend against possible errors.  

Before we move on to step 2, let’s summarize step 1, understand the problem:

-Read through the problem.

-What are the inputs?

-What are the outputs?

Create simple examples, then create more complex ones.

2. Devise a plan for solving the problem.

Next, devise a plan for how you’ll solve the problem. As you devise a plan, write it out in pseudocode.

Pseudocode is a plain language description of the steps in an algorithm. In other words, your pseudocode is your step-by-step plan for how to solve the problem.

Write out the steps you need to take to solve the problem. For a more complicated problem, you’d have more steps. For this problem, you could write:

// Create a sum variable.

Add the first input to the second input using the addition operator .

// Store value of both inputs into sum variable.

// Return as output the sum variable. Now you have your step-by-step plan to solve the problem. For more complex problems, professor Evans notes, “Consider systematically how a human solves the problem.” That is, forget about how your code might solve the problem for a moment, and think about how you would solve it as a human. This can help you see the steps more clearly.

3. Carry out the plan (Solve the problem!)

The next step in the problem-solving strategy is to solve the problem. Using your pseudocode as your guide, write out your actual code.

Professor Evans suggests focusing on a simple, mechanical solution. The easier and simpler your solution is, the more likely you can program it correctly.

Taking our pseudocode, we could now write this:

Professor Evans adds, remember not to prematurely optimize. That is, you might be tempted to start saying, “Wait, I’m doing this and it’s going to be inefficient code!”

First, just get out your simple, mechanical solution.

What if you can’t solve the entire problem? What if there's a part of it you still don't know how to solve?

Colt Steele gives great advice here: If you can’t solve part of the problem, ignore that hard part that’s tripping you up. Instead, focus on everything else that you can start writing.

Temporarily ignore that difficult part of the problem you don’t quite understand and write out the other parts. Once this is done, come back to the harder part.

This allows you to get at least some of the problem finished. And often, you’ll realize how to tackle that harder part of the problem once you come back to it.

Step 4: Look back over what you've done.

Once your solution is working, take the time to reflect on it and figure out how to make improvements. This might be the time you refactor your solution into a more efficient one.

As you look at your work, here are some questions Colt Steele suggests you ask yourself to figure out how you can improve your solution:

• Can you derive the result differently? What other approaches are there that are viable?
• Can you understand it at a glance? Does it make sense?
• Can you use the result or method for some other problem?
• Can you improve the performance of your solution?
• Can you think of other ways to refactor?
• How have other people solved this problem?

One way we might refactor our problem to make our code more concise: removing our variable and using an implicit return:

With step 4, your problem might never feel finished. Even great developers still write code that they later look at and want to change. These are guiding questions that can help you.

If you still have time in an interview, you can go through this step and make your solution better. If you are coding on your own, take the time to go over these steps.

When I’m practicing coding on my own, I almost always look at the solutions out there that are more elegant or effective than what I’ve come up with.

Wrapping Up

In this post, we’ve gone over the four-step problem-solving strategy for solving coding problems.

Let's review them here:

• Step 1: understand the problem.
• Step 2: create a step-by-step plan for how you’ll solve it .
• Step 3: carry out the plan and write the actual code.
• Step 4: look back and possibly refactor your solution if it could be better.

Practicing this problem-solving method has immensely helped me in my technical interviews and in my job as a developer. If you don't feel confident when it comes to solving coding problems, just remember that problem-solving is a skill that anyone can get better at with time and practice.

If you enjoyed this post, join my coding club , where we tackle coding challenges together every Sunday and support each other as we learn new technologies.

If you have feedback or questions on this post, feel free to tweet me @madisonkanna ..

Read more posts .

If you read this far, thank the author to show them you care. Say Thanks

Learn to code for free. freeCodeCamp's open source curriculum has helped more than 40,000 people get jobs as developers. Get started

My experience with Solve, McKinsey’s assessment game.

August 21, 2020 Ana, a former architect and current fellow in Rio de Janeiro , and Carl, a former engineer and current digital associate in Brussels , joined McKinsey earlier this year. We sat down with them virtually to learn about their experiences with Solve .

How did you hear about Solve?

Ana - I heard about the game at a recruiting event. The recruiters and the consultants I met explained the game would give us a chance to show our problem-solving skills. I was curious about the experience, so I watched the video and browsed the interviewing  page. It was my first time hearing of such a test for recruiting, so I was intrigued and nervous as I don’t play videogames.

Carl - I first heard about it when I received the interview instructions. I was quite surprised and excited about this unusual approach. Like Ana, I had a look at the guide on the McKinsey website  which put me at ease.

What was your experience with Solve?

Ana - I was nervous at first. I got so in my head that the instructions didn’t sink in. Then I tried to relax, understand what I had to do, and go with the flow of the game. It was super intuitive, so my anxiety was immediately eased. I really enjoyed learning what I had to do and what strategies to change. As the phases went on, I understood more of what I had to do and found better ways to accomplish my main task.

Carl - After the first five minutes of playing the game, I felt completely drawn into the story and virtual world. In a way, I forgot I was doing an assessment. It was quite fun to play.

Did anything surprise you?

Ana - I was really surprised at how fast I learned how to play the game and evolved my strategy with each new phase. It was easy for me to test out what I thought was the right approach, and shift my strategy when I saw that it was needed.

Carl - By playing the game and trying to find an optimal solution, I realized why McKinsey uses it as part of the assessment process. The game is about understanding a complex situation, determining influencing factors and dynamics, testing a few hypotheses and eventually developing an approach to solve for the game objective. This is precisely what we do every day at McKinsey with our clients.

How did you prepare?

Ana - As there is no preparation required, I made sure I had a good night’s rest prior to playing. During the game I was given guidance for how to manage time and could track my progress.

Carl - I didn’t prepare beforehand as there isn’t a way or need to study or practice. This alleviated some of the normal stress of interviewing for a new role. Once I was in the game, I created some generic steps to structure my approach and set time limits on each step. Of course, these were mainly self-imposed guidelines as I didn’t really know what to expect, but it ended up working well.

What advice would you give someone who is going to play McKinsey’s assessment game?

Ana - You don’t need to prepare or be familiar with video games to do well. When I was told this by a McKinsey recruiter, I didn’t believe them, but now I can reassure people first hand. There is no need to stress – just go into it with an open mind and willingness to try.

Also, take your time. Understand what is in front of you and list what is asked of you – not what you think you should be doing. The format will allow you to showcase how you approach problems, so just try your best.

Carl -Take your time to understand and reflect on the objective. For instance, should you go for quick wins or for long-term solutions and what are the influencing factors. Only then can you prioritize your actions and test the hypotheses to quickly reach a good solution.

Want more interviewing tips and tricks? Read more stories from our colleagues.

Learn more about interviewing at McKinsey

More about Ana

Ana graduated with a bachelor’s degree in architecture and urbanism from the Pontifícia Universidade Católica do Rio de Janeiro, Brazil. After graduating, she worked at a small architecture firm for a year before joining the City Hall of Niterói, as an architect in the Department of Environment, Water Resources and Sustainability.

As a fellow at McKinsey, Ana has been working with retail banking clients.

More about Carl

Carl earned a bachelor’s degree in engineering (mechanics) from KULeuven. He went on to earn a Master’s degree in Engineering (robotics & mechatronics) from KULeuven and TUMunchen. He started his career as a product engineer at Audi. Prior to joining McKinsey, Carl was a consultant focused on digital operations at PwC.

As a digital associate at McKinsey, Carl works on digital transformations in a variety of industries.

Never miss another post

DEV Community

Posted on Apr 10, 2019

Algorithm Problem Solving Strategies

Algorithm puzzles are an unfortunately common way to weed out candidates in the application process. However, when you aren't stressing over the job search, they're actually a lot of fun, like crossword puzzles for coders.

Solving them presents unique challenges that you won't encounter when spinning up Yet Another Crud App and exposes you to concepts that you might not already be familiar with. Practicing algorithm challenges will improve your broader problem solving abilities, as well as cement a problem solving process that is more generically useful.

Much like other types of puzzles, there are strategies that give you an early foothold into the problem and a way to break it down into smaller, more approachable chunks. With an actual puzzle, you might sort the pieces into coherent groups of similar colors or features, find look for obvious matches and grow outwards. With minesweeper, you might start with a random click, and then move around the exposed edges, marking off obvious mines and exposes obvious clear areas, only clicking randomly once more when you've exhausted all possibilities.

While there are strategies for approaching similar kinds of algorithms, I would recommend that you start with a broader problem solving strategy that you embrace as a general habit, and not just when you're grinding LeetCode as interview prep.

Be Strategic, Think First

Rather than diving in, approach the problem in stages:

• Analyze the problem
• Restate the problem
• Write out examples of input and output
• Break the problem into its component parts
• Outline a solution in psuedo-code
• Step through your example data with your psuedo-code
• Test your solution against your examples

(If you're familiar with this approach, skip down to Algorithm Patterns)

Analyze the Problem

You may have had a flash of insight when you first saw the problem. This is typically your mind connecting to some prior experience. Hold on to that insight! However, you should still spend some time looking at the problem, particularly for ways that your insight differs from the actual question.

Any well written puzzle has the components needed to answer the problem contained in a sentence or two. However just because you read the problem doesn't mean you understand the problem. And if you don't understand the problem, you will stumble about aimlessly, or solve what you assumed the problem was.

Look for key words which determine the shape of the challenge.

Identify the input. Identify the desired output. Identify critical keywords and phrases.

For example, LeetCode #26

Given a [sorted] [array] nums, [remove the duplicates] [in-place] such that each element appear only once and [return the new length]. Do not allocate extra space for another array, you must do this by modifying the input array in-place with [O(1) extra memory].

• an array. So we know we're probably going to do some kind of iteration.
• an array of numbers. That's more implied rather than specifically stated and doesn't really matter as much as we can use the same set of conditionals.
• length of altered array
• side effect: a modified array

Critical Words and Phrases:

• sorted: repeated elements will be next to each other
• remove...duplicates
• in-place: the array itself must be destructively modified. This constraint dictates what array methods we may use.
• O(1) extra memory: we are limited to O(1) space complexity, allowing us to define variables, but not create a copy of the array.

Restate the Problem

Now, in our own words, rephrase this so it is meaningful to ourselves. If you are in an interviewing situation, you may restate it back to the interviewer, both to set it in your own mind, and to make sure that you heard and understood them correctly.

Given a sorted array of numbers, passed by reference, destructively modify the original array in-place by removing duplicate, so that each value only appears once. Return the length of the modified array.

Write out Example Inputs and Expected Outputs

All we are doing is mapping inputs to outputs. The challenge is figuring out how to get from A to B, however first we need to establish what A and B are . Even if you are given test cases, write your own. Looking at something doesn't create nearly as much understanding as doing it for yourself.

This is also a great time to explore your understanding of the problem and look for quirks that might trip up a naive solution. That includes edge cases like empty inputs, an array filled with duplicates of the same value, a massive data set, etc. We don't need to worry about anything outside of the constraints of the problem

Write out at least 3 examples:

Given the inputs, do you have enough information to map to the result? If you don't, take a step back and continue examining the problem before continuing. If you are interviewing, feel free to ask for clarification.

Look for a simple and consistent process that you can apply regardless of the value to reach the outcome. If you end up with a convoluted series of steps and exceptions, you've likely gone too far and passed over a simpler solution.

Break the Problem into Small Parts

Starting with the simplest possible example, simply the problem down to an essential puzzle and build upon that. In this case, that is an array of three elements, two duplicated, e.g. [1, 1, 2] . Reducing the problem to such a small case makes it more approachable and clarifies the the first step you need to take. Your task from there is to develop a procedure which solves that simple case and holds true for all other cases in the problem set.

So we know we need to do a couple things:

• Iterate through an array
• Keep track of where in the array we are
• Check adjacent values for equality
• Destructively remove any duplicate values after the first occurrence
• Get the final array length and return it

This is a relatively simple example problem, however there is a gotcha lurking in it: lots of iteration methods don't play nicely with removing elements from the array while you're iterating through the array, because the index values change. You may end up skipping a duplicate because the pointer incremented over it.

This gotcha indicates that we'll want to use an approach that gives us explicit control of iteration.

In a more involved problem, we might consider some or all of these components into helper functions, allowing us to write a clear and succinct solution, as well as test the validity of each of our sub-parts separately.

Psuedocode the Solution

If we've clearly grasped the problem, identified the core tasks and hopefully spotted the flaws in our own assumptions and any gotchas, we write out a human-legible description of what our approach will be. Hopefully once we've done that we can cleanly transform it into working code.

How you write pseudocode is up to you. Your notation doesn't need to be perfectly spelled and grammatically correct. It can be a gestural combination of code and words meant to convey meaning. Your pseudocode will provide a meaningful roadmap that you can refer back to if you find yourself lost deep in the particulars of implementation, so make sure that you record enough to be useful later.

If you're interviewing, this is a great opportunity to walk the interviewer through your intent. And if you're running out of time, you will at least have something on the board that demonstrates your problem solving approach.

Recommendations:

• start with a function signature: removeDuplicates :: (Array) -> number
• if whiteboarding, leave plenty of space to write your actual code
• if using an IDE, write comments and keep them separate from your code so you can reference back later on.
• write it as a series of steps and use bullet points

Since we're looking for duplicates, that means we need to perform a comparison. We can look ahead of our current position in the array, or we can look behind.

We start by exiting if our array is only 0 or 1 elements in size, partly because these cases satisfy the conditions of the problem: there are no duplicates possible, and partly because they'll break our code if we try and compare the first value with a second that doesn't exist.

We also establish our iteration exit condition, and because we'll be using a look-ahead, we make sure to stop before we reach the last element.

Because we don't move our pointer position until after we've dealt with any duplicates, we should be clear of the shifting indices issue.

Step Through the Sample Data

Take a moment and mentally run some of the sample data through our pseudocode:

Are we missing anything?

There may be an issue with the last example: [1, 1, 1, 1, 1] . What happens if we remove all of the duplicates, and then try and move on to the next element in our array without checking to see if there are any?

We'll want to make sure that our end condition catches any changes in the array length.

Time for rubber to meet the road. This is where you have all of the assumptions you didn't even know you made come back to haunt you. The better you were able to plan, the fewer there will be.

Personally I like to put in my return values first. That way I'm clear on what my goal is, and I've also captured the first case of empty or single element arrays.

Yup, we're going with a standard for-loop. I prefer not to use them if there's more appropriate or cleaner syntax, but for this particular problem, we need the ability to control our iteration.

And that works out of the box, except for:

Turns out the existence check I snuck in the while loop resolves to falsy if the array value is 0 . Thanks JavaScript! So let's just rework that real quick and do a look behind instead of look ahead, which actually cleans the code up a tad as well:

And that passes. It's a memory efficient solution, we've only defined 1 variable besides the array reference. And it is of average speed, which we could improve upon.

But mostly it was a simple example of a process:

• Write examples
• Break into small problems
• Outline in pseudocode
• Step through pseudocode with examples

Algorithm Patterns

Aside from specific data structures and algorithms which have known and fairly standardized approaches, algorithm challenges tend to fall into categories that suggest similar solution approaches. Learning these approaches gives you a foothold into the problem.

Multiple Pointers

When we first learn to iterate through a collection, typically an array, we do so with a single pointer with an index going from the lowest value to the highest. This works for some operations and is simple to consider and code. However for problems involving comparing multiple elements, particularly ones where their position in the collection is important, finding corresponding value with a single pointer requires iterating through the array at least once for each value, an O(n 2) operation.

If instead we use multiple multiple points we can potentially reduce the computation down to an O(n) operation.

There are two common strategies: Two Pointer and Sliding Window

Two Pointer

Why not start at both ends and work your way in? Or start at a value or pair of values and expand outwards. This is a great approach for finding the largest sequence in a collection.

Because you are handling two points, you will need to define a rule to ensure that they do not cross over each other.

Sliding Window

Instead of placing two points at the outer bounds, we can march through our array sequentially moving two pointers in parallel. The width of our window may grow or shrink according to the problem set, but it continues to progress across the collection, capturing a snapshot of whatever sequence best fits the desired outcome.

Divide and Conquer

Divide and Conquer often involves a recursive approach: applying the same rule to divide a collection until you've broken it down into the smallest components and identify the answer.

Binary Search and Merge Sort are both excellent examples of recursive subdivision leading to a solution.

O(1) Lookup: Object/Dictionary/Hash

Hashed Key:Value stores, called Objects, Dictionaries or Hashes depending upon your coding language, are incredibly useful tools for storing information when counting frequency, checking for duplicates or the complement of an answer. As there

You may store the value, or you may store the value that you are looking for instead. For example, when looking for zero-sum pairs in an array, we can save the complement rather than the value itself.

Fundamentals of Algorithmic Problem Solving (video) Algorithmic Problem Solving for Programmers Top 10 Algorithms in Interview Questions Improving your Algorithms and Data Structure Skills

Top comments (3)

Templates let you quickly answer FAQs or store snippets for re-use.

• Location New York, NY
• Education Cooper Union BFA, NYU MFA - Visual Art
• Joined Jan 21, 2021

This is a great break down of how to approach solving algorithm problems. I really appreciated the step by step explanations and concrete examples. Thanks!

• Location Kazakhstan, Shymkent
• Work Middle Software developer
• Joined Feb 18, 2021

Thanks! It is a great tutor how to start solve the problem! And don't worry if someone said about typo in the words. The context is important! I will keep your strategic as main for myself

• Joined Feb 13, 2020

I did not finish the reading yet but just want to point that in several places you have a typo in the word Pseudocode . Do a search using the word "psuedo" and you will find it in 3 places.

Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink .

Hide child comments as well

For further actions, you may consider blocking this person and/or reporting abuse

An interesting Mule app to create complex MUnits

Alex Martinez - Apr 16

Insights from the Leading EDJE Round Table Discussion on AI: Bridging the Gap Between Virtual and Physical Spaces

Julie Yakunich - Apr 16

vishal.codes - Apr 16

#2 Variáveis - Entendendo o JavaScript

João Pedro V - Apr 16

We're a place where coders share, stay up-to-date and grow their careers.

McKinsey Solve

• Fundamentals
• How it works
• Skills tested
• How to prepare
• A guide to the McKinsey Problem Solving Game

MCC is here to help

McKinsey’s Solve assessment has been making candidates sweat ever since it was initially trialled at the firm’s London office back in 2017 - and things have gotten even more difficult since a new version launched in Spring 2023, adding the Redrock case study.

More recently, in Summer 2023, we have seen a new iteration of that Redrock case, as we continue to interview test takers to keep you updated. This replaces the case study about optimising wolf pack populations across Redrock Island with one about boosting the overall plant biodiversity on the same island.

Since its initial roll-out, the Solve assessment has definitely been the most idiosyncratic, but also the most advanced, of the screening tests used by the MBB firms.

It can be hard to understand how an ecology-themed video game can tell McKinsey whether you’ll make a good management consultant, let alone know how to prepare yourself to do well in that game. When you consider that McKinsey are potentially cutting 70%+ of the applicant pool based on this single test, you can hardly blame applicants for being worried.

Matters are definitely not helped by the dearth of reliable, up-to-date information about what could very well be - with a top-tier consulting job on the line - the most important test you will take over your entire career. This was already true with the version of Solve that had been around for a few years, let alone the new iterations.

What information is available online is then often contradictory. For a long time, there was huge disagreement as to whether it is actually possible to meaningfully prepare for the Solve assessment - before you’ve even considered how to go about that preparation. There is also a lot of confusion and inaccuracy around the new Redrock case - largely as it is such a recent addition, and individual test takers tend to misremember details.

Luckily, we at MCC have been interviewing test takers both before and after the Redrock case rollout and have been following up to see which strategies and approaches actually work to push individuals through to interview.

Here, we’ll explain that it is indeed possible to prepare effectively for both versions of Solve and give you some ideas for how you can get started. Understanding how the Solve assessment works, what it tests you for and how is critical for all but the most hurried preparations.

This article makes for a great introduction to the Solve assessment. However, if you are going to be facing this aptitude test yourself and want full information and advice for preparation, then you should ideally get our full PDF guide:

Master the Solve Assessment

What is the mckinsey solve assessment.

In simple terms, the McKinsey Solve assessment is a set of ecology-themed video games. In these games, you must do things like build food chains, protect endangered species, manage predator and prey populations, boost biodiversity and potentially diagnose diseases within animal populations or identify natural disasters.

Usually, you will be given around 70 minutes to complete two separate games, spending about the same amount of time on each.

Until recently, these games had uniformly been Ecosystem Building and Plant Defence. However, since Spring 2023, McKinsey has been rolling out a new version across certain geographies. This replaces the Plant Defence game with the new Redrock case study. Some other games have also been run as tests.

We’ll run through a little more on all these games below to give you an idea of what you’ll be up against for both versions and possible new iterations.

An important aspect that we'll cover in more detail here is that the Solve games don't only score you on your answers (your "product score"), but also on the method you use to arrive at them (your "process score") - considerably impacting optimal strategy.

In the past, candidates had to show up to a McKinsey office and take what was then the Digital Assessment or PSG on a company computer. However, candidates are now able to take the re-branded Solve assessment at home on their own computers.

Test takers are allowed to leverage any assistance they like (you aren’t spied on through your webcam as you would be with some other online tests), and it is common to have a calculator or even another computer there to make use of.

Certainly, we strongly advise every candidate to have at least a pen, paper and calculator on their desk when they take the Solve assessment.

Common Question: Is the Solve assessment the same thing as the PSG?

In short, yes - “Solve” is just the newer name for the McKinsey Problem Solving Game.

We want to clear up any potential confusion right at the beginning. You will hear this same screening test called a few different things in different places. The Solve moniker itself is a relatively recent re-branding by McKinsey. Previously, the same test was known as either the Problem Solving Game (usually abbreviated to PSG) or the Digital Assessment. You will also often see that same test referred to as the Imbellus test or game, after the firm that created the first version.

You will still see all these names used across various sites and forums - and even within some older articles and blog posts here on MyConsultingCoach. McKinsey has also been a little inconsistent on what they call their own assessment internally. Candidates can often become confused when trying to do their research, but you can rest assured that all these names refer to the same screening test - though, of course, folk might be referring to either the legacy or Redrock versions.

How and why does McKinsey use the Solve assessment?

It’s useful to understand where the Solve assessment fits into McKinsey’s overall selection process and why they have felt the need to include it.

Let’s dive right in…

How is the Solve Assessment used by McKinsey?

McKinsey's own account of how the Solve assessment is used in selection can be seen in the following video:

Whilst some offices initially stuck with the old PST, the legacy Solve assessment was soon rolled out globally and given universally to candidates for roles at pretty well every level of the hierarchy. Certainly, if you are a recent grad from a Bachelor’s, MBA, PhD or similar, or a standard experienced hired, you can expect to be asked to complete the Solve assessment.

Likewise, the new Redrock case study versions seem to be in the process of being rolled out globally - though at this point it seems you might be given either (especially as McKinsey has been having significant technical problems with this new online case study) and so should be ready for both.

At present, it seems that only those applying for very senior positions, or perhaps those with particularly strong referrals and/or connections, are allowed to skip the test. Even this will be office-dependent.

As noted above, one of the advantages of the Solve assessment is that it can be given to all of McKinsey’s hires. Thus, you can expect to be run into the same games whether you are applying as a generalist consultant or to a specialist consulting role - with McKinsey Digital , for example.

The takeaway here is that, if you are applying to McKinsey for any kind of consulting role, you should be fully prepared to sit the Solve Assessment!

Where does the Solve assessment fit into the recruitment process?

You can expect to receive an invitation to take the Solve assessment shortly after submitting your resume.

It seems that an initial screen of resumes is made, but that most individuals who apply are invited to take the Solve assessment.

Any initial screen is not used to make a significant cut of the candidate pool, but likely serves mostly to weed out fraudulent applications from fake individuals (such as those wishing to access the Solve assessment more than once so they can practice...) and perhaps to eliminate a few individuals who are clearly far from having the required academic or professional background, or have made a total mess of their resumes.

Your email invitation will generally give you either one or two weeks to complete the test, though our clients have seen some variation here - with one individual being given as little as three days.

Certainly, you should plan to be ready to sit the Solve assessment within one week of submitting your resume!

Once you have completed the test, McKinsey explain on their site that they look at both your test scores and resume (in more detail this time) to determine who will be invited to live case interviews. This will only be around 30% of the candidates who applied - possibly even fewer.

One thing to note here is that you shouldn’t expect a good resume to make up for bad test scores and vice versa. We have spoken to excellent candidates whose academic and professional achievements were not enough to make up for poor Solve performance. Similarly, we don’t know of anyone invited to interview who hadn’t put together an excellent resume.

Blunty, you need great Solve scores and a great resume to be advanced to interview.

Your first port of call to craft the best possible resume and land your invitation to interview is our excellent free consulting resume guide .

Why does this test exist?

As with Bain, BCG and other major management consulting firms, McKinsey receives far far more applications for each position than they can ever hope to interview. Compounding this issue is that case interviews are expensive and inconvenient for firms like McKinsey to conduct. Having a consultant spend a day interviewing just a few candidates means disrupting a whole engagement and potentially having to fly that consultant back to their home office from wherever their current project was located. This problem is even worse for second-round interviews given by partners.

Thus, McKinsey need to cut down their applicant pool as far as possible, so as to shrink the number of case interviews they need to give without losing the candidates they actually want to hire. Of course, they want to accomplish this as cheaply and conveniently as possible.

The Problem Solving Test (invariably shortened to PST) had been used by McKinsey for many years. However, it had a number of problems that were becoming more pronounced over time, and it was fundamentally in need of replacement. Some of these were deficiencies with the test itself, though many were more concerned with how the test fitted with the changing nature of the consulting industry.

The Solve assessment was originally developed and iterated by the specialist firm Imbellus ( now owned by gaming giant Roblox ) to replace the long-standing PST in this screening role and offers solutions to those problems with its predecessor.

We could easily write a whole article on what McKinsey aimed to gain from the change, but the following few points cover most of the main ideas:

• New Challenges: Previously, candidates were largely coming out of MBAs or similar business-focussed backgrounds and the PST’s quickfire business questions were thus perfectly sufficient to select for non-technical generalist consulting roles. However, as consulting projects increasingly call for a greater diversity and depth of expertise, McKinsey cannot assume the most useful talent – especially for technical roles – is going to come with pre-existing business expertise. A non-business aptitude test was therefore required.
• Fairness and the Modern Context: The covid pandemic necessitated at-home aptitude testing. However, even aside from this, online testing dramatically reduces the amount of travel required of candidates. This allows McKinsey to cast a wider net, providing more opportunities to those living away from hub cities, whilst also hugely reducing the carbon footprint associated with the McKinsey selection process.
• Gaming the System: More pragmatically, the Solve assessment is a much harder test to “game” than was the PST, where highly effective prep resources were available and readily allowed a bad candidate with good preparation to do better than a good candidate. The fact that game parameters change for every individual test taker further cuts down the risk of candidates benefitting from shared information. The recent move towards the Redrock version then also helps McKinsey stay ahead of those developing prep resources for the legacy Solve assessment.
• Cost Cutting: A major advantage of scrapping the old pen-and-paper PST is that the formidable task of thinning down McKinsey’s applicant pool can be largely automated. No test rooms and invigilation staff need to be organised and no human effort is required to devise, transport, catalogue and mark papers.

Impress your interviewer

There has been a bit of variation in the games included in the Solve assessment/PSG over the years and what specific form those games take. Imbellus and McKinsey had experimented with whole new configurations as well as making smaller, iterative tweaks over time. That being said, the new 2023 Redrock case studies (seemingly added by McKinsey themselves without Imbellus) are by far the largest change to Solve since that assessment's genesis back in 2017.

Given that innovation seems to continue (especially with the lengthy feedback forms some candidates are being asked to fill in after sitting the newest iteration), there is always the chance you might be the first to receive something new.

However, our surveys of, and interviews with, those taking the Solve assessment - both before and after recent changes - mean we can give you a good idea of what to expect if you are presented with either the legacy or one of the Redrock versions of Solve.

We provide much more detailed explanation of each of the games in our Solve Assessment PDF Guide - including guidance on optimal scenarios to maximise your performance. Here, though, we can give a quick overview of each scenario:

Ecosystem Building

In this scenario, you are asked to assemble a self-sustaining ecosystem in either an aquatic, alpine or jungle environment (though do not be surprised if environments are added, as this should be relatively easy to do without changing the underlying mechanics).

The game requires you to select a location for your ecosystem. Several different options are given, all with different prevailing conditions. You then have to select a number of different plant and animal species to populate a functioning food chain within that location.

In previous versions of the game, you would have had to fit as many different species as possible into a functioning food chain. However, newer iterations of the Solve assessment require a fixed number of eight or, more recently, seven species to be selected.

Species selection isn’t a free-for-all. You must ensure that all the species you select are compatible with one another - that the predator species you select are able to eat the prey you have selected for them etc. All the species must also be able to survive in the conditions prevailing at the location you have selected.

So far, this sounds pretty easy. However, the complexity arises from the strict rules around the manner and order in which the different species eat one another. We run through these in detail in our guide, with tips for getting your food chain right. However, the upshot is that you are going to have to spend some significant time checking your initial food chain - and then likely iterating it and replacing one or more species when it turns out that the food chain does not adhere to the eating rules.

Once you have decided on your food chain, you simply submit it and are moved on to the next game. In the past, test takers were apparently shown whether their solution was correct or not, but this is no longer the case.

Test takers generally report that this game is the easier of the two, whether it is paired with the Plant Defence game in the legacy Solve or the Redrock case study in the new version. Candidates will not usually struggle to assemble a functioning ecosystem and do not find themselves under enormous time pressure. Thus, we can assume that process scores will be the main differentiator between individuals for this component of the Solve assessment.

For ideas on how to optimise your process score for this game, you can see our PDF Solve guide .

Plant Defence

As mentioned, this game has been replaced with the Redrock case study in the new newer version of the Solve assessment, rolled out from Spring 2023 and further iterated in Summer 2023. However, you might still be asked to sit the legacy version, with this game, when applying to certain offices - so you should be ready for it!

This scenario tasks you with protecting an endangered plant species from invasive species trying to destroy it.

The game set-up is much like a traditional board game, with play taking place over a square area of terrain divided into a grid of the order of 10x10 squares.

Your plant is located in a square near the middle of the grid and groups of invaders - shown as rats, foxes or similar - enter from the edges of the grid before making a beeline towards your plant.

Your job then is to eliminate the invaders before they get to your plant. You do this by placing defences along their path. These can be terrain features, such as mountains or forests, that either force the invaders to slow down their advance or change their path to move around an obstacle. To actually destroy the invaders though, you use animal defenders, like snakes or eagles, that are able to deplete the groups of invaders as they pass by their area of influence.

Complication here comes from a few features of the game. In particular:

• You are restricted in terms of both the numbers of different kinds of defenders you can use and where you are allowed to place them. Thus, you might only have a couple of mountains to place and only be allowed to place these in squares adjacent to existing mountains.
• The main complication is the fact that gameplay is not dynamic but rather proceeds in quite a restricted turnwise manner. By this, we mean that you cannot place or move around your defences continuously as the invaders advance inwards. Rather, turns alternate between you and invaders and you are expected to plan your use of defences in blocks of five turns at once, with only minimal allowance for you to make changes on the fly as the game develops.

The plant defence game is split into three mini-games. Each mini-game is further split into three blocks of five turns. On the final turn, the game does not stop, but continues to run, with the invaders in effect taking more and more turns whilst you are not able to place any more defences or change anything about your set-up.

More and more groups of invaders pour in, and your plant will eventually be destroyed. The test with this “endgame” is simply how many turns your defences can stand up to the surge of invaders before they are overwhelmed.

As opposed to the Ecosystem Building scenario, there are stark differences in immediate candidate performance - and thus product score - in this game. Some test takers’ defences will barely make it to the end of the standard 15 turns, whilst others will survive 50+ turns of endgame before they are overwhelmed.

In this context, as opposed to the Ecosystem Building game typically preceding it, it seems likely that product score will be the primary differentiator between candidates.

We have a full discussion of strategies to optimise your defence placement - and thus boost your product score - in our Solve guide .

Redrock Case Study

This is the replacement for the Plant Defence game in the newest iteration of Solve.

One important point to note is that, where the Solve assessment contains this case study, you have a strict, separate time limit of 35 minutes for each half of the assessment. You cannot finish one game early and use the extra time in the other, as you could in the legacy Solve assessment.

McKinsey has had significant issues with this case study, with test takers noting several major problems. In particular:

• Glitches/crashes - Whilst the newest, Summer 2023 version seems to have done a lot to address this issue, many test takers have had the Redrock case crash on them. Usually, this is just momentary and the assessment returns to where it was in a second or two. If this happens to you, try to just keep calm and carry on. However, there are reports online of some candidates having the whole Solve assessment crash and being locked out as a result. If this happens, contact HR.
• Poor interface - Even where there are no explicit glitches, users note that several aspects of the interface are difficult to use and/or finicky, and that they generally seem poorly designed compared to the older Ecosystem Building game preceding it. For example, test takers have noted that navigation is difficult or unclear and the drag and drop feature for data points is temperamental - all of this costing precious time.
• Confusing language - Related to the above is that the English used is often rather convoluted and sometimes poorly phrased. This can be challenging even for native English speakers but is even worse for those sitting Solve in their second language. It can make the initial instructions difficult to understand - compounding the previous interface problem. It can also make questions difficult, requiring a few readings to comprehend.
• Insufficient time - Clearly, McKinsey intended for Redrock to be time pressured. Whilst the newest, Summer 2023 iteration of the Redrock case seems slightly more forgiving in this regard, time is still so scarce that many candidates don't get through all the questions. This is plainly sub-optimal for McKinsey - as well as being stressful and disheartening for candidates. We would expect further changes to be made to address this issue in future.

McKinsey are clearly aware of these issues, as even those sitting the new version of Redrock have been asked to complete substantial feedback surveys. Do note, then, that this raises the likelihood of further changes to the Redrock case study in the near term - meaning you should always be ready to tackle something new.

For the time being, though, we can take you through the fundamentals of the current version of the Redrock case study. For more detail, see our freshly updated PDF Guide .

The Scenario

Whilst changes to the details are likely in future, the current Redrock case study is set on the Island of Redrock. This island is a nature reserve with populations of various species, including wolves, elk and several varieties of plant.

In the original Redrock case, it is explained that the island's wolves are split into four packs, associated with four geographical locales. These packs predate the elk and depend upon them for food, such that there is a dynamic relationship between the population numbers of both species. Your job is to ensure ecological balance by optimising the numbers of wolves in the four packs, such that both wolves and elk can sustainably coexist.

In the newer iteration of the case, first observed in Summer 2023, you are asked to assess which, if any, of three possible strategies can successfully boost the island's plant biodiversity by a certain specified percentage. Plants here are segmented into grasses, trees and shrubs.

The Questions

The Redrock case study's questions were initially split into three sections, but a fourth was added later. These sections break down as follows:

• Investigation - Here, you have access to the full description of the case, with all the data on the various animal populations. Your task is to efficiently extract all the most salient data points and drag-and-drop them to your "Research Journal" workspace area. This is important, as you subsequently lose access to all the information you don't save at this stage.
• Analysis - You must answer three numerical questions using information you saved in the Investigation section. This can include you dragging and dropping values to and from an in-game calculator.
• Report - Formerly the final section, you must complete a pre-written report on the wolf populations or plant biodiversity levels, including calculating numerical values to fill in gaps and using an in-game interface to make a chart to illustrate your findings. You will leverage information saved in the Investigation section, as well as answers calculated in the Analysis section.
• Case Questions - This section adds a further ten individual case questions. These are wolf-themed, so are thematically similar to the original Redrock case, but are slightly incongruous with the newer, plant-themed version of Redrock. In both instances, though, these questions are entirely separable from the main case preceding them, not relying on any information from the previous sections. The ten questions are highly quantitative and extremely time pressured. Few test takers finish them before being timed out.

This is a very brief summary - more detail is available in our PDF Guide .

Other Games - Disease and Disaster Identification

There have been accounts of some test takers being given a third game as part of their Solve assessment. At time of writing, these third games have always been clearly introduced as non-scored beta tests for Imbellus to try out potential new additions to the assessment. However, the fact that these have been tested means that there is presumably a good chance we’ll see them as scored additions in future.

Notably, these alternative scenarios are generally variations on a fairly consistent theme and tend to share a good deal of the character of the Ecosystem Building game. Usually, candidates will be given a whole slew of information on how an animal population has changed over time. They will then have to wade through that information to figure out either which kind of natural disaster or which disease has been damaging that population - the commonality with the Ecosystem Building game being in the challenge of dealing with large volumes of information and figuring out which small fraction of it is actually relevant.

Join thousands of other candidates cracking cases like pros

What does the solve assessment test for.

Whilst information on the Solve assessment can be hard to come by, Imbellus and McKinsey have at least been explicit on what traits the test was designed to look for. These are:

• Critical Thinking : making judgements based on the objective analysis of information
• Decision Making : choosing the best course of action, especially under time pressure or with incomplete information
• Metacognition : deploying appropriate strategies to tackle problems efficiently
• Situational Awareness : the ability to interpret and subsequently predict an environment
• Systems Thinking : understanding the complex causal relationships between the elements of a system

Equally important to understanding the raw facts of the particular skillset being sought out, though, is understanding the very idiosyncratic ways in which the Solve assessment tests for these traits.

Let's dive deeper:

Process Scores

Perhaps the key difference between the Solve assessment and any other test you’ve taken before is Imbellus’s innovation around “process scores”.

To explain, when you work through each of the games, the software examines the solutions you generate to the various problems you are faced with. How well you do here is measured by your “product score”.

However, scoring does not end there. Rather, Solve's software also constantly monitors and assesses the method you used to arrive at that solution. The quality of the method you used is then captured in your “process score”.

To make things more concrete here, if you are playing the Ecosystem Building game, you will not only be judged on whether the ecosystem you put together is self-sustaining. You will also be judged on the way you have worked in figuring out that ecosystem - presumably, on how efficient and organised you were. The program tracks all your mouse clicks and other actions and will thus be able to capture things like how you navigate around the various groups of species, how you place the different options you select, whether you change your mind before you submit the solution and so on.

You can find more detail on these advanced aspects of the Solve assessment and the innovative work behind it in the presentation by Imbellus founder Rebecca Kantar in the first section of the following video:

Compared to other tests, this is far more like the level of assessment you face from an essay-based exam, where the full progression of your argument towards a conclusion is marked - or a maths exam, where you are scored on your working as well as the final answer (with, of course, the major advantage that there is no highly qualified person required to mark papers).

Clearly, the upshot of all this is that you will want to be very careful how you approach the Solve assessment. You should generally try to think before you act and to show yourself in a very rational, rigorous, ordered light.

We have some advice to help look after your process scores in our PDF Guide to the McKinsey Solve Assessment .

A Different Test for Every Candidate

Another remarkable and seriously innovative aspect of the Solve assessment is that no two candidates receive exactly the same test.

Imbellus automatically varies the parameters of their games to be different for each individual test taker, so that each will be given a meaningfully different game to everyone else’s.

Within a game, this might mean a different terrain setting, having a different number of species or different types of species to work with or more or fewer restrictions on which species will eat which others.

Consequently, even if your buddy takes the assessment for the same level role at the same office just the day before you do, whatever specific strategy they used in their games might very well not work for you.

This is an intentional feature designed to prevent test takers from sharing information with one another and thus advantaging some over others. At the extreme, this feature would also be a robust obstacle to any kind of serious cheating.

To manage to give every candidate a different test and still be able to generate a reliable ranking of those candidates across a fundamental skillset, without that test being very lengthy, is a considerable achievement from Imbellus. At high level, this would seem to be approximately equivalent to reliably extracting a faint signal from a very noisy background on the first attempt almost every time.

(Note that we are yet to confirm to what extent and how this also happens with the new Redrock case studies, but it seems to be set up to allow for easy changes to be made to the numerical values describing the case, so we assume there will be similar, widespread of variation.)

Preparation for the McKinsey Solve assessment

Understanding what the Solve assessment tests for immediately begs the question as to whether it is possible to usefully prepare and, if so, what that preparation should look like.

Is it Really Possible to Prepare for the McKinsey Solve Assessment?

In short, yes you can - and you should!

As noted previously, there has been a lot of disagreement over whether it is really possible to prep for the Solve assessment in a way that actually makes a difference.

Especially for the legacy version, there has been a widespread idea that the Solve assessment functions as something like an IQ test, so that preparation beyond very basic familiarisation to ensure you don’t panic on test day will not do anything to reliably boost your scores (nobody is going to build up to scoring an IQ of 200 just by doing practice tests, for example).

This rationale says that the best you can do is familiarise yourself with what you are up against to calm your nerves and avoid misunderstanding instructions on test day. However, this school of thought says there will be minimal benefit from practice and/or skill building.

The utility of preparation has become a clearer with the addition of the Redrock case study to the new version of Solve. Its heavily quantitative nature, strong time pressure and structure closely resembling a traditional business case make for a clearer route to improvement.

However, as we explain in more detail in our PDF guide to the Solve assessment, the idea that any aspect of either version of Solve can't be prepared for has been based on some fundamental misunderstandings about what kind of cognitive traits are being tested. Briefly put, the five key skills the Solve assessment explicitly examines are what are known as higher-order thinking skills.

Crucially, these are abilities that can be meaningfully built over time.

McKinsey and Imbellus have generally advised that you shouldn’t prepare. However, this is not the same as saying that there is no benefit in doing so. McKinsey benefits from ensuring as even a playing field as possible. To have the Solve test rank candidates based purely on their pre-existing ability, they would ideally wish for a completely unprepared population.

How to prep

We discuss how to prep for the Solve assessment in full detail in our PDF guide . Here, though, we can give you a few initial pointers to get you started. In particular, there are some great ways to simulate different games as well as build up the skills the Solve assessment tests for.

Playing video games is great prep for the legacy Solve assessment in particular, but remains highly relevant to the new Redrock version.

Contrary to what McKinsey and Imbellus have said - and pretty unfortunately for those of us with other hobbies - test takers have consistently said that they reckoned the Problem Solving Game, and now the Solve assessment, favours those with strong video gaming experience.

If you listened when your parents told you video games were a waste of time and really don’t have any experience, then putting in some hours on pretty much anything will be useful. However, the closer the games you play are to the Solve scenarios, the better. We give some great recommendations on specific games and what to look for more generally in our Solve guide - including one free-to-play game that our clients have found hugely useful as prep for the plant defence game!

PST-Style Questions

The inclusion of the Redrock case studies in the new version of Solve really represents a return to something like a modernised PST. Along with the similar new BCG Casey assessment, this seems to be the direction of travel for consulting recruitment in general.

Luckily, this means that you can leverage the wealth of existing PST-style resources to your advantage in preparation.

Our PST article - which links to some free PST questions and our full PST prep resources - is a great place to start. However, better than old-fashioned PDF question sets are the digital PST-style questions embedded in our Case Academy course . Conducted online with a strict timer running, these are a much closer approximation of the Solve assessment itself. These questions are indeed a subset of our Case Academy course, but are also available separately in our Course Exercises package .

Quick Mathematics With a Calculator and/or Excel

Again, specifically for the Redrock assessment, you will be expected to solve math problems very quickly. The conceptual level of mathematics required is not particularly high, but you need to know what you are doing and get through it fast using a calculator nand/or Excel, if you are already comfortable with that program.

Our article on consulting math is a great place to start to understand what is expected of you throughout the recruiting process, with our consulting math package (a subset of our Case Academy course) providing more in-depth lessons and practice material.

Learn to Solve Case Studies

With the Redrock case studies clearly being ecology-themed analogues to standard business case studies, it's pretty obvious that getting good at case studies will be useful.

However, the Solve assessment as a whole is developed and calibrated to be predictive of case interview performance, so you can expect that improving your case solving ability will indirectly bring up your performance across the board.

Of course, this overlaps with your prep for McKinsey's case interviews. For more on how to get started there, see the final section of this article.

Learning About Optimal Strategies for the Games

The first thing to do is to familiarise yourself with the common game scenarios from the Solve assessment and how you can best approach them to help boost your chances of success.

Now, one thing to understand is that, since the parameters for the games change for each test taker, there might not be a single definitive optimal strategy for every single possible iteration of a particular game. As such, you shouldn’t rely on just memorising one approach and hoping it matches up to what you get on test day.

Instead, it is far better to understand why a strategy is sensible in some circumstances and when it might be better to do something else instead if the version of the game you personally receive necessitates a different approach.

In this article, we have given you a useful overview of the games currently included in the Solve assessment. However, a full discussion with suggested strategies is provided in our comprehensive Solve guide .

With the limited space available here, this is only a very brief sketch of a subset of the ways you can prep.

As noted, what will help with all of these and more is reading the extensive prep guidance in our full PDF guide to the Solve assessment...

The MCC Solve Assessment Guide

Preparing for the Solve assessment doesn’t have to be a matter of stumbling around on your own. This article is a good introduction. From here, though our new, updated PDF guide to the McKinsey Solve assessment is your first stop to optimise your Solve preparation.

This guide is based on our own survey work and interviews with real test takers, as well as iterative follow-ups on how the advice in previous editions worked out in reality.

Does it make sense to invest in a guide?

Short answer: yes. If you just think about the financials, a job at McKinsey is worth millions in the long run. If you factor in experience, personal growth and exit opportunities, the investment is a no-brainer.

How our guide can help you ace the test

Don't expect some magic tricks to game the system (because you can't), but rather an in-depth analysis of key areas crucial to boost your scores. This helps you to:

As noted, the guide is based on interviews with real recent test takers and covers the current games in detail. Being familiar with the game rules, mechanics and potential strategies in advance will massively reduce the amount of new information you have to assimilate from scratch on test day, allowing you to focus on the actual problems at hand.

Despite the innovative environment, the Solve assessment tests candidates for the same skills evaluated in case interviews, albeit on a more abstract level. Our guide breaks these skills down and provides a clear route to develop them. You also benefit from the cumulative experience of our clients, as we have followed up to see which prep methods and game strategies were genuinely helpful.

A clear plan of how to prepare is instrumental for success. Our guide includes a detailed, flexible preparation strategy, leveraging a whole host of diverse prep activities to help you practice and build your skills as effectively as possible. Importantly, our guide helps you prioritise the most effective aspects of preparation to optimise for whatever timeframe you have to work in.

Overall, the MyConsultingCoach Solve guide is designed to be no-nonsense and straight to the point. It tells you what you need to know up front and - for those of you in a hurry - crucial sections are clearly marked to read first to help you prep ASAP.

For those of you starting early with more time to spare, there is also a fully detailed, more nuanced discussion of what the test is looking for and how you can design a more long-term prep to build up the skills you need - and how this can fit into your wider case interview prep.

Importantly, there is no fluff to bulk out the page count. The market is awash with guides at huge page counts, stuffed full of irrelevant material to boost overall document length. By contrast, we realise your time is better spent actually preparing than ploughing through a novel.

If this sounds right for you, you can purchase our PDF Solve guide here:

McKinsey Solve Assessment Guide

• Full guide to both the legacy version of the Solve assessment and the newer Redrock Case Study versions
• In-depth description of the different games and strategies to beat them
• Preparation strategies for the short, medium and long-term prep
• No fluff - straight to the point, with specific tips for those without much time
• Straight to your inbox
• 30 days money-back guarantee, no questions asked. Simply email us and we will refund the full amount.

The Next Step - Case Interviews

So, you pour in the hours to generate an amazing resume and cover letter. You prepare diligently for the Solve assessment, going through our PDF guide and implementing all the suggestions. On test day, you sit down and ace Solve. The result is an invitation to a live McKinsey case interview.

Now the real work begins…

Arduous as application writing and Solve prep might have seemed, preparing for McKinsey case interviews will easily be an order of magnitude more difficult.

Remember that McKinsey tells candidates not to prepare for Solve - but McKinsey explicitly expects applicants to have rigorously prepared for case interviews .

The volume of specific business knowledge and case-solving principles, as well as the sheer complexity of the cases you will be given, mean that there is no way around knuckling down, learning what you need to know and practicing on repeat.

If you want to get through your interviews and actually land that McKinsey offer, you are going to need to take things seriously, put in the time and learn how to properly solve case studies.

Unfortunately, the framework-based approach taught by many older resources is unlikely to cut it for you. These tend to falter when applied to difficult, idiosyncratic cases - precisely the kind of case you can expect from McKinsey!

The method MCC teaches is based specifically on the way McKinsey train incoming consultants. We throw out generic frameworks altogether and show you how to solve cases like a real management consultant on a real engagement.

You can start reading about the MCC method for case cracking here . To step your learning up a notch, you can move on to our Case Academy course .

To put things into practice in some mock interviews with real McKinsey consultants, take a look at our coaching packages .

And, if all this (rightfully) seems pretty daunting and you’d like to have an experienced consultant guide you through your whole prep from start to finish, you can apply for our comprehensive mentoring programme here .

Looking for an all-inclusive, peace of mind program?

Our comprehensive packages.

Get our Solve guide for free if you purchase any of the following packages. Just email us with your order number and we will send the guide straight to your inbox.

Access to our Case Academy and to coaching will help you prepare for Solve and for the following rounds!

The MCC bundle

• All Case Interview Course Videos
• All Case Interview Course Exercises
• All Fit Interview Course Videos
• All case interview self-assessment modules
• Available on all devices
• Premium support for questions
• Lifetime access

Bridge to Consulting

• 5 one-hour sessions with ex-MBB (McKinsey/Bain/BCG) coach of your choice
• Session personalisation (skill level and preparation stage)
• Choice of interview format (Fit, Case or Both)
• AI-powered performance benchmarking, skill-gap assessment and actionable feedback through your Dashboard
• Full Access to Case Academy (Course, Exercises, Self-Assessments, Fit and Math)
• McKinsey Digital Assessment Guide
• All our PST material

Case Interview Course

• 16+ hours of lectures  covering  all aspects of the case interview
• Introduction to the consulting interview
• Case Interview foundations section 
• Problem Driven Approach
• Building blocks 
• Efficiency tools
• Problem driven structure in action
• Roadmap for preparation planning

Account not confirmed

Problem-Solving Strategies

• © 1998
• Arthur Engel 0

Institut für Didaktik der Mathematik, Johann Wolfgang Goethe-Universität Frankfurt am Main, Frankfurt am Main 11, Germany

You can also search for this author in PubMed   Google Scholar

• The most complete training book on the market
• A must-have for instructors wishing to enrich their teaching with interesting non-routine problems
• Provides individuals with a wide array of interesting, challenging problems
• Each chapter starts with typical examples illustrating the central concepts, followed by carefully selected problems and their solutions
• Very few problems have no solutions

Part of the book series: Problem Books in Mathematics (PBM)

57k Accesses

1 Citations

28 Altmetric

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

Access this book

• Available as PDF
• Read on any device
• Instant download
• Own it forever
• Compact, lightweight edition
• Dispatched in 3 to 5 business days
• Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

Table of contents (14 chapters)

Front matter, the invariance principle, coloring proofs, the extremal principle, the box principle, enumerative combinatorics, number theory, inequalities, the induction principle, polynomials, functional equations, further strategies, back matter.

• Problem-solving
• mathematics

About this book

Problem-Solving Strategies is a unique collection of competition problems from over twenty major national and international mathematical competitions for high school students. The discussion of problem solving strategies is extensive. It is written for trainers and participants of contests of all levels up to the highest level: IMO, Tournament of the Towns, and the noncalculus parts of the Putnam Competition. It will appeal to high school teachers conducting a mathematics club who need a range of simple to complex problems and to those instructors wishing to pose a "problem of the week", "problem of the month", and "research problem of the year" to their students, thus bringing a creative atmosphere into their classrooms with continuous discussions of mathematical problems. This volume is a must-have for instructors wishing to enrich their teaching with some interesting non -routine problems and for individuals who are just interested in solving difficult and challenging problems. Each chapter starts with typical examples illustrating the central concepts and is followed by a number of carefully selected problems and their solutions. Most of the solutions are complete, but some merely point to the road leading to the final solution. Very few problems have no solutions. Readers interested in increasing the effectiveness of the book can do so by working on the examples in addition to the problems thereby increasing the number of problems to over 1300. In addition to being a valuable resource of mathematical problems and solution strategies, this volume is the most complete training book on the market.

Authors and Affiliations

Arthur Engel

About the author

Bibliographic information.

Book Title : Problem-Solving Strategies

Authors : Arthur Engel

Series Title : Problem Books in Mathematics

DOI : https://doi.org/10.1007/b97682

Publisher : Springer New York, NY

eBook Packages : Springer Book Archive

Copyright Information : Springer-Verlag New York 1998

Softcover ISBN : 978-0-387-98219-9 Published: 12 December 1997

eBook ISBN : 978-0-387-22641-5 Published: 19 January 2008

Series ISSN : 0941-3502

Series E-ISSN : 2197-8506

Edition Number : 1

Number of Pages : X, 403

Topics : Mathematics, general

• Publish with us

Policies and ethics

• Find a journal
• Track your research