problem solving meaning management

.css-s5s6ko{margin-right:42px;color:#F5F4F3;}@media (max-width: 1120px){.css-s5s6ko{margin-right:12px;}} AI that works. Coming June 5, Asana redefines work management—again. .css-1ixh9fn{display:inline-block;}@media (max-width: 480px){.css-1ixh9fn{display:block;margin-top:12px;}} .css-1uaoevr-heading-6{font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-1uaoevr-heading-6:hover{color:#F5F4F3;} .css-ora5nu-heading-6{display:-webkit-box;display:-webkit-flex;display:-ms-flexbox;display:flex;-webkit-align-items:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:start;-ms-flex-pack:start;-webkit-justify-content:flex-start;justify-content:flex-start;color:#0D0E10;-webkit-transition:all 0.3s;transition:all 0.3s;position:relative;font-size:16px;line-height:28px;padding:0;font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-ora5nu-heading-6:hover{border-bottom:0;color:#CD4848;}.css-ora5nu-heading-6:hover path{fill:#CD4848;}.css-ora5nu-heading-6:hover div{border-color:#CD4848;}.css-ora5nu-heading-6:hover div:before{border-left-color:#CD4848;}.css-ora5nu-heading-6:active{border-bottom:0;background-color:#EBE8E8;color:#0D0E10;}.css-ora5nu-heading-6:active path{fill:#0D0E10;}.css-ora5nu-heading-6:active div{border-color:#0D0E10;}.css-ora5nu-heading-6:active div:before{border-left-color:#0D0E10;}.css-ora5nu-heading-6:hover{color:#F5F4F3;} Get early access .css-1k6cidy{width:11px;height:11px;margin-left:8px;}.css-1k6cidy path{fill:currentColor;}

• Product overview
• All features
• App integrations

CAPABILITIES

• project icon Project management
• Project views
• Custom fields
• Status updates
• goal icon Goals and reporting
• Reporting dashboards
• workflow icon Workflows and automation
• portfolio icon Resource management
• Time tracking
• my-task icon Admin and security
• Admin console
• asana-intelligence icon Asana Intelligence
• list icon Personal
• premium icon Starter
• briefcase icon Advanced
• Goal management
• Organizational planning
• Campaign management
• Creative production
• Marketing strategic planning
• Request tracking
• Resource planning
• Project intake
• View all uses arrow-right icon
• Project plans
• Team goals & objectives
• Team continuity
• Meeting agenda
• View all templates arrow-right icon
• Work management resources Discover best practices, watch webinars, get insights
• What's new Learn about the latest and greatest from Asana
• Customer stories See how the world's best organizations drive work innovation with Asana
• Help Center Get lots of tips, tricks, and advice to get the most from Asana
• Asana Academy Sign up for interactive courses and webinars to learn Asana
• Developers Learn more about building apps on the Asana platform
• Community programs Connect with and learn from Asana customers around the world
• Events Find out about upcoming events near you
• Partners Learn more about our partner programs
• Support Need help? Contact the Asana support team
• Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Featured Reads

• Business strategy |
• Problem management: 8 steps to better p ...

Problem management: 8 steps to better problem solving

Problem management is an 8 step framework most commonly used by IT teams. You can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Solving the root cause prevents recurrence and creates a repeatable solution to use on similar errors in the future.

In an IT department, errors and mishaps are part of the job. You can't always control these problems, but you can control how you respond to them with problem management. Problem management helps you solve larger problems and reduce the risk that they’ll happen again by identifying all connected problems, solving them, and planning for the future.

What is problem management?

Problem management is an 8 step framework most commonly used by IT teams. Your team can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Problem management is a process—used mostly by IT teams—to identify, react, and respond to issues. It’s not for every problem, but it’s a useful response when multiple major incidents occur that cause large work interruptions. Unlike problem solving, problem management goes beyond the initial incident to discover and dissect the root causes, preventing future incidents with permanent solutions.

The goals of problem management are to:

Prevent problems before they start.

Solve for repetitive errors.

Lessen each incident’s impact. 

Problem management vs. incident management 

Example: Someone leaves their unprotected laptop in a coffee shop, causing a security breach. The security team can use incident management to solve for this one, isolated event. In this case, the team could manually shut down the accounts connected to that laptop. If this continues to happen, IT would use problem management to solve the root of this issue—perhaps installing more security features on each company laptop so that if employees lose them, no one else can access the information.

Problem management vs. problem solving

While similar in name, problem management differs slightly from problem-solving. Problem management focuses on every aspect of the incident—identifying the root cause of the problem, solving it, and prevention. Problem solving is, as the name implies, focused solely on the solution step. 

Example: You’re launching a new password management system when it crashes—again. You don’t know if anything leaked, but you know it could contain confidential information. Plus, it’s happened before. You start the problem management process to ensure it doesn’t happen again. In that process, you’ll use problem solving as a step to fix the issue. In this case, perhaps securing confidential information before you try to launch a new software.

Problem management vs. change management 

Change management targets large transitions within your workplace, good and bad. These inevitable changes aren’t always negative, so you can’t always apply problem management as a solution. That’s where change management comes in—a framework that helps you adjust to any new scenario.

Example: Your company is transitioning to a new cloud platform. The transition happens incident-free—meaning you won’t need problem management—but you can ease the transition by implementing some change management best practices. Preparing and training team members in the new software is a good place to start.

Problem management vs. project management

Project management is the framework for larger collections of work. It’s the overarching method for how you work on any project, hit goals, and get results. You can use project management to help you with problem management, but they are not the same thing. Problem management and project management work together to solve issues as part of your problem management process.

Example: During problem management, you uncover a backend security issue that needs to be addressed—employees are using storage software with outdated security measures. To solve this, you create a project and outline the tasks from start to finish. In this case, you might need to alert senior executives, get approval to remove the software, and alert employees. You create a project schedule with a defined timeline and assign the tasks to relevant teams. In this process, you identified a desired outcome—remove the unsafe software—and solved it. That’s project management.

The 8 steps of problem management

It’s easy to get upset when problems occur. In fact, it’s totally normal. But an emotional response is not always the best response when faced with new incidents. Having a reliable system—such as problem management—removes the temptation to respond emotionally. Proactive project management gives your team a framework for problem solving. It’s an iterative process —the more you use it, the more likely you are to have fewer problems, faster response times, and better outputs. 

1. Identify the problem

During problem identification, you’re looking at the present—what’s happening right now? Here, you’ll define what the incident is and its scale. Is this a small, quick-fix, or a full overhaul? Consider using problem framing to define, prioritize, and understand the obstacles involved with these more complex problems. 

2. Diagnose the cause

Use problem analysis or root cause analysis to strategically look at the cause of a problem. Follow the trail of issues all the way back to its beginnings.

To diagnose the underlying cause, you’ll want to answer:

What factors or conditions led to the incident?

Do you see related incidents? Could those be coming from the same source?

Did someone miss a step? Are processes responsible for this problem?

3. Organize and prioritize

Now it’s time to build out your framework. Use an IT project plan to organize information in a space where everyone can make and see updates in real time. The easiest way to do this is with a project management tool where you can input ‌tasks, assign deadlines, and add dependencies to ensure nothing gets missed. To better organize your process, define:

What needs to be done? 

Who’s responsible for each aspect? If no one is, can we assign someone? 

When does each piece need to be completed?

What is the final number of incidents related to this problem?

Are any of these tasks dependent on another one? Do you need to set up dependencies ?

What are your highest priorities? How do they affect our larger business goals ? 

How should you plan for this in the future?

4. Create a workaround

If the incident has stopped work or altered it, you might need to create a workaround. This is not always necessary, but temporary workarounds can keep work on track and avoid backlog while you go through the problem management steps. When these workarounds are especially effective, you can make them permanent processes.

5. Update your known error database

Every time an incident occurs, create a known error record and add it to your known error database (KEDB). Recording incidents helps you catch recurrences and logs the solution, so you know how to solve similar errors in the future. 

6. Pause for change management (if necessary)

Larger, high-impact problems might require change management. For example, if you realize the problem’s root cause is a lack of staff, you might dedicate team members to help. You can use change management to help them transition their responsibilities, see how these new roles fit in with the entire team, and determine how they will collaborate moving forward.

7. Solve the problem

This is the fun part—you get to resolve problems. At this stage, you should know exactly what you’re dealing with and the steps you need to take. But remember—with problem management, it’s not enough to solve the current problem. You’ll want to take any steps to prevent this from happening again in the future. That could mean hiring a new role to cover gaps in workflows , investing in new softwares and tools, or training staff on best practices to prevent these types of incidents.

Read: Turn your team into skilled problem solvers with these problem-solving strategies

8. Reflect on the process

The problem management process has the added benefit of recording the process in its entirety, so you can review it in the future. Once you’ve solved the problem, take the time to review each step and reflect on the lessons learned during this process. Make note of who was involved, what you needed, and any opportunities to improve your response to the next incident. After you go through the problem management process a few times and understand the basic steps, stakeholders, workload, and resources you need, create a template to make the kickoff process easier in the future.

5 benefits of problem management

Problem management helps you discover every piece of the problem—from the current scenario down to its root cause. Not only does this have an immediate positive impact on the current issue at hand, it also promotes collaboration and helps to build a better product overall. 

Here are five other ways ‌problem management can benefit your team:

Avoids repeat incidents. When you manage the entire incident from start to finish, you will address the foundational problems that caused it. This leads to fewer repeat incidents.

Boosts cross-functional collaboration. Problem management is a collaborative process. One incident might require collaboration from IT, the security team, and legal. Depending on the level of the problem, it might trickle all the way back down to the product or service team, where core changes need to be made.

Creates a better user experience. It’s simple—the fewer incidents you have, the better your customer’s experience will be. Reducing incidents means fewer delays, downtime, and frustrations for your users, and a higher rate of customer satisfaction.

Improves response time. As you develop a flow and framework with a project management process, you’ll be better equipped to handle future incidents—even if they’re different scenarios.

Organizes problem solving. Problem management provides a structured, thoughtful approach to solving problems. This reduces impulsive responses and helps you keep a better problem record of incidents and solutions.

Problem management leads to better, faster solutions

IT teams will always have to deal with incidents, but they don’t have to be bogged down by them. That’s because problem management works. Whether you employ a full problem management team or choose to apply these practices to your current IT infrastructure, problem management—especially when combined with a project management tool—saves you time and effort down the road.

With IT project plans, we’ve made it easier than ever to track your problem management work in a shared tool. Try our free IT project template to see your work come together, effortlessly.

Related resources

Grant management: A nonprofit’s guide

How Asana uses work management to optimize resource planning

How Asana uses work management for organizational planning

Solve your tech overload with an intelligent transformation

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

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

What Is Problem Solving?

Definition and importance.

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

Problem-Solving Steps

The problem-solving process typically includes the following steps:

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

Defining the Problem

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

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

Generating Solutions

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

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

Evaluating and Selecting Solutions

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

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

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

Implementing and Monitoring the Solution

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

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

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

Problem-Solving Techniques

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

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

Brainstorming

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

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

When brainstorming, remember to:

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

Root Cause Analysis

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

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

SWOT Analysis

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

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

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

Mind Mapping

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

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

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

Examples of Problem Solving in Various Contexts

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

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

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

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

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

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

• Project Management

Home » Free Resources » »

What Is Problem Solving in Project Management? Here’s Everything You Need to Know

• Written by Contributing Writer
• Updated on August 4, 2023

In project management , problem-solving is a crucial and necessary skill. Whether you have failed to consider every possible factor impacting a project, a problem arises through no fault of your own, or conditions change that create issues, problems must be addressed promptly to keep projects on track.

In this article, we will define problem-solving and how it impacts projects, provide real-world examples of problem-solving, and give you a structured, step-by-step process to solve problems. We’ll also show you how earning a project management certification can help you gain practical experience in problem-solving methods.

What Is Problem-Solving?

Problem-solving is a process to identify roadblocks or defects that arise during a project. A structured system to define problems, identify root causes, brainstorm and test solutions, and monitor results can affect change to improve performance and overcome challenges.

Effective problem-solving enables teams to deal with uncertainties or gaps in planning to minimize the impact on outcomes.

The Importance of Problem-Solving in Project Management

During a project and operation, problems can arise at any time. You may find that your planning before launching a product, for example, did not consider all the factors that impact results. You may find that you were too optimistic about project timelines, performance, or workforce. Or, as many of us discovered over the past few years, supply chain disruption may make even the best project plans obsolete.

Regardless, your job is identifying, solving, and overcoming these problems. Project managers must be skilled in leading team members through a structured approach to resolving problems.

Proactive problem-solving requires careful consideration of all the variables in a project, including preparation to:

• Achieve project objectives
• Address obstacles before they arise
• Manage project risks and contingency plans
• Manage communication and collaboration
• Provide a framework for time and cost management
• Provide a pathway for continuous improvement

Also Read: 10 Tips on How to Increase Productivity in the Workplace

Problem-Solving Steps in Project Management

While the process you choose to solve problems may vary, here is a seven-step framework many project managers use. This problem-solving method combines primary and secondary problem-solving steps.

#1. Define the Problem

• Gather data and information from key stakeholders, team members, and project documentation. Include any relevant reporting or data analysis
• Itemized key details, such as a description of the problem, timelines, outcomes, and impact
• Frame the issue as a problem statement

A good example of a problem statement might be: An unexpected demand spike has exceeded our current production capacity. How can we still meet customer deadlines for delivery?

#2. Analyze Root Causes

• Break down issues into smaller components to diagnose bottlenecks or problems
• Identify the organizational, mechanical, environmental, or operational factors that contribute
• Distinguish between one-time issues vs. systematic, ongoing areas that need improvement

When analyzing root causes, it’s common to find multiple factors contributing to a problem. As such, it is essential to prioritize issues that have the most significant impact on outcomes.

#3. Brainstorm Potential Solutions

• Holding specific sessions focused on brainstorming ideas to resolve root causes
• Build on ideas or suggest combinations or iterations
• Categorize solutions by types, such as process or input changes, adding additional resources, outsourcing, etc.)

In brainstorming, you should refrain from immediately analyzing suggestions to keep ideas coming.

#4. Evaluate Potential Solutions

• Reframe the problem and concern for team members, providing a framework for evaluation such as cost, timing, and feasibility
• With ideas in hand, it is time to evaluate potential solutions. Project managers often employ strategies such as weighted scoring models to rank ideas.
• Consider the pros and cons in relation to project objectives

As you narrow the list, getting additional insight from subject matter experts to evaluate real-world viability is helpful. For example, if you are proposing a process change in operating a machine, get feedback from skilled operators before implementing changes.

#5. Decide on a Plan of Action

• Make a decision on which course of action you want to pursue and make sure the solution aligns with your organizational goals
• Create an action plan to implement the changes, including key milestones
• Assign project ownership, deadlines, resources, and budgets

Defining what outcomes you need to achieve to declare success is also essential. Are you looking for incremental change or significant improvements, and what timeline are you establishing for measurement?

#6. Implement the Action Plan

• Communicate the plan with key stakeholders
• Provide any training associated with the changes
• Allocate resources necessary for implementation

As part of the action plan, you will also want to detail the measures and monitoring you will put in place to assess process outcomes.

#7. Monitor and Track Results

• Track solution performance against the action plan and key milestones
• Solicit feedback from the project team on problem-solving effectiveness
• Ensure the solution resolves the root cause, creating the desired results without negatively impacting other areas of the operation

You should refine results or start the process over again to increase performance. For example, you may address the root cause but find a need for secondary problem-solving in project management, focusing on other factors.

These problem-solving steps are used repeatedly in lean management and Six Sigma strategies for continuous improvement.

Also Read: 5 Project Management Steps You Need to Know

How Project Management Tools Can Help You in Problem-Solving

Project management software can guide teams through problem-solving, acting as a central repository to provide visibility into the stages of a project.

The best project management software will include the following:

• Issue tracking to capture problems as they arise
• Chat and real-time collaboration for discussion and brainstorming
• Templates for analysis, such as fishbone diagrams
• Action plans, assigning tasks, ownership, and accountability
• Dashboards for updates to monitor solutions
• Reporting on open issues, mitigation, and resolution

Examples of Problem-Solving

Here are some examples of the problem-solving process demonstrating how team members can work through the process to achieve results.

Sign-ups for a New Software Solution Were Well Below First-Month Targets

After analyzing the data, a project team identifies the root cause as inefficient onboarding and account configurations. They then brainstorm solutions. Ideas include re-architecting the software, simplifying onboarding steps, improving the initial training and onboarding process, or applying additional resources to guide customers through the configuration process.

After weighing alternatives, the company invests in streamlining onboarding and developing software to automate configuration.

A Project Was at Risk of Missing a Hard Deadline Due to Supplier Delays

In this case, you already know the root cause: Your supplier cannot deliver the necessary components to complete the project on time. Brainstorming solutions include finding alternative sources for components, considering project redesigns to use different (available) components, negotiating price reductions with customers due to late delivery, or adjusting the scope to complete projects without this component.

After evaluating potential solutions, the project manager might negotiate rush delivery with the original vendor. While this might be more expensive, it enables the business to meet customer deadlines. At the same time, project schedules might be adjusted to account for later-than-expected part delivery.

A Construction Project Is Falling Behind Due to Inclement Weather

Despite months of planning, a major construction project has fallen behind schedule due to bad weather, preventing concrete and masonry work. The problem-solving team brainstorms the problem and evaluates solutions, such as constructing temporary protection from the elements, heating concrete to accelerate curing, and bringing on additional crews once the weather clears.

The project team might decide to focus on tasks not impacted by weather earlier in the process than expected to postpone exterior work until the weather clears.

Also Read: Understanding KPIs in Project Management

Improve Your Problem-Solving and Project Management Skills

This project management course delivered by Simpliearn, in collaboration wiht the University of Massachusetts, can boost your career journey as a project manager. This 24-week online bootcamp aligns with Project Management Institute (PMI) practices, the Project Management Professional (PMP®) certification, and IASSC-Lean Six Sigma.

This program teaches skills such as:

• Agile management
• Customer experience design
• Design thinking
• Digital transformation
• Lean Six Sigma Green Belt

You might also like to read:

5 Essential Project Management Steps You Need to Know

Project Management Frameworks and Methodologies Explained

13 Key Project Management Principles and How to Use Them

Project Management Phases: A Full Breakdown

How To Develop a Great Project Management Plan in 2023

Leave a Comment Cancel Reply

Your email address will not be published. Required fields are marked *

Recommended Articles

What is Project Resource Management? Everything You Need to Know

If you’re asking, “What is project resource management,” and want to learn the tools, techniques, and best practices involved, our comprehensive guide covers everything you need.

Best Apps for Project Management You Should Know in 2024

Every project needs a manager, especially in today’s fast-paced digital world. And every project manager needs tools to manage projects. Learn about some of the best project management apps you can choose from today in this blog.

20 Best Practices in Project Management [2024 Guide]

Explore our guide to the top best practices in project management. Strengthen your foundation and take your career to new heights.

How to Measure Project Success? A 2024 Guide

One person’s definition of success can vary wildly from another’s. That’s why project managers need definitive ways to measure project success. This article will share tips, best practices, and methods to determine whether you are hitting the mark.

Remote Project Management: How to Manage Remote Teams Effectively

Remote working became a harsh reality during the COVID-19 pandemic. Yet, many employers and their employees adapted to it quickly and still prefer it, making remote project management an essential skill for professionals.

What are Project Management Skills? Here are Top Skills You should Know in 2024

Here are the top project management skills you will need to master project management in 2024. This article will help you get started with both hard and soft skills.

Project Management Bootcamp

Learning Format

Online Bootcamp

Program benefits.

• 25 in-demand tools covered
• Aligned with PMI-PMP® and IASSC-Lean Six Sigma
• Masterclasses from top faculty of UMass Amherst
• UMass Amherst Alumni Association membership

How it works

For Business

Join Mind Tools

Article • 7 min read

What Is Problem Solving?

Find a solution to any problem you face.

By the Mind Tools Content Team

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

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

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

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

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

How Well Do You Solve Problems?

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

Define Every Problem

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

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

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

Understanding Complexity

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

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

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

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

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

General Problem-Solving Tools

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

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

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

Specific Problem-Solving Systems

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

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

Further Problem-Solving Strategies

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

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

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

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

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

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

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

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

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

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

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Action learning sets.

Solving Problems by Doing and Discussing

Cause and Effect Analysis

Identifying the Likely Causes of Problems

Add comment

Comments (0)

Be the first to comment!

Get 30% off your first year of Mind Tools

Great teams begin with empowered leaders. Our tools and resources offer the support to let you flourish into leadership. Join today!

Sign-up to our newsletter

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

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Latest Updates

The Presentation Planning Checklist

Mind Tools Store

About Mind Tools Content

Discover something new today

Managing your boss.

Developing an Effective Working Relationship

Negotiating With Confrontational Customers

Advice on how to reach a successful outcome when faced with a confrontational customer.

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

Risk impact/probability charts.

Learning to Prioritize Risks

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

Table of Contents

The problem-solving process, how to solve problems: 5 steps, train to solve problems with lean today, what is problem solving steps, techniques, & best practices explained.

Problem solving is the art of identifying problems and implementing the best possible solutions. Revisiting your problem-solving skills may be the missing piece to leveraging the performance of your business, achieving Lean success, or unlocking your professional potential. 

Ask any colleague if they’re an effective problem-solver and their likely answer will be, “Of course! I solve problems every day.” 

Problem solving is part of most job descriptions, sure. But not everyone can do it consistently. 

Problem solving is the process of defining a problem, identifying its root cause, prioritizing and selecting potential solutions, and implementing the chosen solution.

There’s no one-size-fits-all problem-solving process. Often, it’s a unique methodology that aligns your short- and long-term objectives with the resources at your disposal. Nonetheless, many paradigms center problem solving as a pathway for achieving one’s goals faster and smarter. 

One example is the Six Sigma framework , which emphasizes eliminating errors and refining the customer experience, thereby improving business outcomes. Developed originally by Motorola, the Six Sigma process identifies problems from the perspective of customer satisfaction and improving product delivery. 

Lean management, a similar method, is about streamlining company processes over time so they become “leaner” while producing better outcomes. 

Trendy business management lingo aside, both of these frameworks teach us that investing in your problem solving process for personal and professional arenas will bring better productivity.

1. Precisely Identify Problems

As obvious as it seems, identifying the problem is the first step in the problem-solving process. Pinpointing a problem at the beginning of the process will guide your research, collaboration, and solutions in the right direction. 

At this stage, your task is to identify the scope and substance of the problem. Ask yourself a series of questions: 

• What’s the problem? 
• How many subsets of issues are underneath this problem? 
• What subject areas, departments of work, or functions of business can best define this problem? 

Although some problems are naturally large in scope, precision is key. Write out the problems as statements in planning sheets . Should information or feedback during a later step alter the scope of your problem, revise the statements. 

Framing the problem at this stage will help you stay focused if distractions come up in later stages. Furthermore, how you frame a problem will aid your search for a solution. A strategy of building Lean success, for instance, will emphasize identifying and improving upon inefficient systems. 

2. Collect Information and Plan 

The second step is to collect information and plan the brainstorming process. This is another foundational step to road mapping your problem-solving process. Data, after all, is useful in identifying the scope and substance of your problems. 

Collecting information on the exact details of the problem, however, is done to narrow the brainstorming portion to help you evaluate the outcomes later. Don’t overwhelm yourself with unnecessary information — use the problem statements that you identified in step one as a north star in your research process. 

This stage should also include some planning. Ask yourself:

• What parties will ultimately decide a solution? 
• Whose voices and ideas should be heard in the brainstorming process? 
• What resources are at your disposal for implementing a solution? 

Establish a plan and timeline for steps 3-5. 

3. Brainstorm Solutions

Brainstorming solutions is the bread and butter of the problem-solving process. At this stage, focus on generating creative ideas. As long as the solution directly addresses the problem statements and achieves your goals, don’t immediately rule it out. 

Moreover, solutions are rarely a one-step answer and are more like a roadmap with a set of actions. As you brainstorm ideas, map out these solutions visually and include any relevant factors such as costs involved, action steps, and involved parties. 

With Lean success in mind, stay focused on solutions that minimize waste and improve the flow of business ecosystems. 

Become a Quality Management Professional

• 10% Growth In Jobs Of Quality Managers Profiles By 2025
• 11% Revenue Growth For Organisations Improving Quality

Certified Lean Six Sigma Green Belt

• 4 hands-on projects to perfect the skills learnt
• 4 simulation test papers for self-assessment

Lean Six Sigma Expert

• IASSC® Lean Six Sigma Green Belt and Black Belt certification
• 13 Projects, 12 Simulation exams, 18 Case Studies & 114 PDUs

Here's what learners are saying regarding our programs:

Xueting Liu

Mechanical engineer student at sargents pty. ltd. ,.

A great training and proper exercise with step-by-step guide! I'll give a rating of 10 out of 10 for this training.

Abdus Salam

I have completed the Lean Six Sigma Expert Master’s Program from Simplilearn. And after the course, I could take up new projects and perform better. My average pay rate for a research position increased by 21%.

4. Decide and Implement

The most critical stage is selecting a solution. Easier said than done. Consider the criteria that has arisen in previous steps as you decide on a solution that meets your needs. 

Once you select a course of action, implement it. 

Practicing due diligence in earlier stages of the process will ensure that your chosen course of action has been evaluated from all angles. Often, efficient implementation requires us to act correctly and successfully the first time, rather than being hurried and sloppy. Further compilations will create more problems, bringing you back to step 1. 

5. Evaluate

Exercise humility and evaluate your solution honestly. Did you achieve the results you hoped for? What would you do differently next time? 

As some experts note, formulating feedback channels into your evaluation helps solidify future success. A framework like Lean success, for example, will use certain key performance indicators (KPIs) like quality, delivery success, reducing errors, and more. Establish metrics aligned with company goals to assess your solutions.

Master skills like measurement system analysis, lean principles, hypothesis testing, process analysis and DFSS tools with our Lean Six Sigma Green Belt Training Course . Sign-up today!

Become a quality expert with Simplilearn’s Lean Six Sigma Green Belt . This Lean Six Sigma certification program will help you gain key skills to excel in digital transformation projects while improving quality and ultimate business results.

In this course, you will learn about two critical operations management methodologies – Lean practices and Six Sigma to accelerate business improvement.

Our Quality Management Courses Duration And Fees

Explore our top Quality Management Courses and take the first step towards career success

Get Free Certifications with free video courses

Quality Management

Lean Management

Project Management

Learn from industry experts with free masterclasses, digital marketing.

SEO vs. PPC: Which Digital Marketing Career Path Fits You Best in 2024?

The Top 10 AI Tools You Need to Master Marketing in 2024

Unlock Digital Marketing Career Success Secrets for 2024 with Purdue University

Recommended Reads

Introduction to Machine Learning: A Beginner's Guide

Webinar Wrap-up: Mastering Problem Solving: Career Tips for Digital Transformation Jobs

An Ultimate Guide That Helps You to Develop and Improve Problem Solving in Programming

Free eBook: 21 Resources to Find the Data You Need

ITIL Problem Workaround: A Leader’s Guide to Manage Problems

Your One-Stop Solution to Understand Coin Change Problem

Get Affiliated Certifications with Live Class programs

• PMP, PMI, PMBOK, CAPM, PgMP, PfMP, ACP, PBA, RMP, SP, and OPM3 are registered marks of the Project Management Institute, Inc.

How to master the seven-step problem-solving process

In this episode of the McKinsey Podcast , Simon London speaks with Charles Conn, CEO of venture-capital firm Oxford Sciences Innovation, and McKinsey senior partner Hugo Sarrazin about the complexities of different problem-solving strategies.

Podcast transcript

Simon London: Hello, and welcome to this episode of the McKinsey Podcast , with me, Simon London. What’s the number-one skill you need to succeed professionally? Salesmanship, perhaps? Or a facility with statistics? Or maybe the ability to communicate crisply and clearly? Many would argue that at the very top of the list comes problem solving: that is, the ability to think through and come up with an optimal course of action to address any complex challenge—in business, in public policy, or indeed in life.

Looked at this way, it’s no surprise that McKinsey takes problem solving very seriously, testing for it during the recruiting process and then honing it, in McKinsey consultants, through immersion in a structured seven-step method. To discuss the art of problem solving, I sat down in California with McKinsey senior partner Hugo Sarrazin and also with Charles Conn. Charles is a former McKinsey partner, entrepreneur, executive, and coauthor of the book Bulletproof Problem Solving: The One Skill That Changes Everything [John Wiley & Sons, 2018].

Charles and Hugo, welcome to the podcast. Thank you for being here.

Hugo Sarrazin: Our pleasure.

Charles Conn: It’s terrific to be here.

Simon London: Problem solving is a really interesting piece of terminology. It could mean so many different things. I have a son who’s a teenage climber. They talk about solving problems. Climbing is problem solving. Charles, when you talk about problem solving, what are you talking about?

Charles Conn: For me, problem solving is the answer to the question “What should I do?” It’s interesting when there’s uncertainty and complexity, and when it’s meaningful because there are consequences. Your son’s climbing is a perfect example. There are consequences, and it’s complicated, and there’s uncertainty—can he make that grab? I think we can apply that same frame almost at any level. You can think about questions like “What town would I like to live in?” or “Should I put solar panels on my roof?”

You might think that’s a funny thing to apply problem solving to, but in my mind it’s not fundamentally different from business problem solving, which answers the question “What should my strategy be?” Or problem solving at the policy level: “How do we combat climate change?” “Should I support the local school bond?” I think these are all part and parcel of the same type of question, “What should I do?”

I’m a big fan of structured problem solving. By following steps, we can more clearly understand what problem it is we’re solving, what are the components of the problem that we’re solving, which components are the most important ones for us to pay attention to, which analytic techniques we should apply to those, and how we can synthesize what we’ve learned back into a compelling story. That’s all it is, at its heart.

I think sometimes when people think about seven steps, they assume that there’s a rigidity to this. That’s not it at all. It’s actually to give you the scope for creativity, which often doesn’t exist when your problem solving is muddled.

Simon London: You were just talking about the seven-step process. That’s what’s written down in the book, but it’s a very McKinsey process as well. Without getting too deep into the weeds, let’s go through the steps, one by one. You were just talking about problem definition as being a particularly important thing to get right first. That’s the first step. Hugo, tell us about that.

Hugo Sarrazin: It is surprising how often people jump past this step and make a bunch of assumptions. The most powerful thing is to step back and ask the basic questions—“What are we trying to solve? What are the constraints that exist? What are the dependencies?” Let’s make those explicit and really push the thinking and defining. At McKinsey, we spend an enormous amount of time in writing that little statement, and the statement, if you’re a logic purist, is great. You debate. “Is it an ‘or’? Is it an ‘and’? What’s the action verb?” Because all these specific words help you get to the heart of what matters.

Want to subscribe to The McKinsey Podcast ?

Simon London: So this is a concise problem statement.

Hugo Sarrazin: Yeah. It’s not like “Can we grow in Japan?” That’s interesting, but it is “What, specifically, are we trying to uncover in the growth of a product in Japan? Or a segment in Japan? Or a channel in Japan?” When you spend an enormous amount of time, in the first meeting of the different stakeholders, debating this and having different people put forward what they think the problem definition is, you realize that people have completely different views of why they’re here. That, to me, is the most important step.

Charles Conn: I would agree with that. For me, the problem context is critical. When we understand “What are the forces acting upon your decision maker? How quickly is the answer needed? With what precision is the answer needed? Are there areas that are off limits or areas where we would particularly like to find our solution? Is the decision maker open to exploring other areas?” then you not only become more efficient, and move toward what we call the critical path in problem solving, but you also make it so much more likely that you’re not going to waste your time or your decision maker’s time.

How often do especially bright young people run off with half of the idea about what the problem is and start collecting data and start building models—only to discover that they’ve really gone off half-cocked.

Hugo Sarrazin: Yeah.

Charles Conn: And in the wrong direction.

Simon London: OK. So step one—and there is a real art and a structure to it—is define the problem. Step two, Charles?

Charles Conn: My favorite step is step two, which is to use logic trees to disaggregate the problem. Every problem we’re solving has some complexity and some uncertainty in it. The only way that we can really get our team working on the problem is to take the problem apart into logical pieces.

What we find, of course, is that the way to disaggregate the problem often gives you an insight into the answer to the problem quite quickly. I love to do two or three different cuts at it, each one giving a bit of a different insight into what might be going wrong. By doing sensible disaggregations, using logic trees, we can figure out which parts of the problem we should be looking at, and we can assign those different parts to team members.

Simon London: What’s a good example of a logic tree on a sort of ratable problem?

Charles Conn: Maybe the easiest one is the classic profit tree. Almost in every business that I would take a look at, I would start with a profit or return-on-assets tree. In its simplest form, you have the components of revenue, which are price and quantity, and the components of cost, which are cost and quantity. Each of those can be broken out. Cost can be broken into variable cost and fixed cost. The components of price can be broken into what your pricing scheme is. That simple tree often provides insight into what’s going on in a business or what the difference is between that business and the competitors.

If we add the leg, which is “What’s the asset base or investment element?”—so profit divided by assets—then we can ask the question “Is the business using its investments sensibly?” whether that’s in stores or in manufacturing or in transportation assets. I hope we can see just how simple this is, even though we’re describing it in words.

When I went to work with Gordon Moore at the Moore Foundation, the problem that he asked us to look at was “How can we save Pacific salmon?” Now, that sounds like an impossible question, but it was amenable to precisely the same type of disaggregation and allowed us to organize what became a 15-year effort to improve the likelihood of good outcomes for Pacific salmon.

Simon London: Now, is there a danger that your logic tree can be impossibly large? This, I think, brings us onto the third step in the process, which is that you have to prioritize.

Charles Conn: Absolutely. The third step, which we also emphasize, along with good problem definition, is rigorous prioritization—we ask the questions “How important is this lever or this branch of the tree in the overall outcome that we seek to achieve? How much can I move that lever?” Obviously, we try and focus our efforts on ones that have a big impact on the problem and the ones that we have the ability to change. With salmon, ocean conditions turned out to be a big lever, but not one that we could adjust. We focused our attention on fish habitats and fish-harvesting practices, which were big levers that we could affect.

People spend a lot of time arguing about branches that are either not important or that none of us can change. We see it in the public square. When we deal with questions at the policy level—“Should you support the death penalty?” “How do we affect climate change?” “How can we uncover the causes and address homelessness?”—it’s even more important that we’re focusing on levers that are big and movable.

Would you like to learn more about our Strategy & Corporate Finance Practice ?

Simon London: Let’s move swiftly on to step four. You’ve defined your problem, you disaggregate it, you prioritize where you want to analyze—what you want to really look at hard. Then you got to the work plan. Now, what does that mean in practice?

Hugo Sarrazin: Depending on what you’ve prioritized, there are many things you could do. It could be breaking the work among the team members so that people have a clear piece of the work to do. It could be defining the specific analyses that need to get done and executed, and being clear on time lines. There’s always a level-one answer, there’s a level-two answer, there’s a level-three answer. Without being too flippant, I can solve any problem during a good dinner with wine. It won’t have a whole lot of backing.

Simon London: Not going to have a lot of depth to it.

Hugo Sarrazin: No, but it may be useful as a starting point. If the stakes are not that high, that could be OK. If it’s really high stakes, you may need level three and have the whole model validated in three different ways. You need to find a work plan that reflects the level of precision, the time frame you have, and the stakeholders you need to bring along in the exercise.

Charles Conn: I love the way you’ve described that, because, again, some people think of problem solving as a linear thing, but of course what’s critical is that it’s iterative. As you say, you can solve the problem in one day or even one hour.

Charles Conn: We encourage our teams everywhere to do that. We call it the one-day answer or the one-hour answer. In work planning, we’re always iterating. Every time you see a 50-page work plan that stretches out to three months, you know it’s wrong. It will be outmoded very quickly by that learning process that you described. Iterative problem solving is a critical part of this. Sometimes, people think work planning sounds dull, but it isn’t. It’s how we know what’s expected of us and when we need to deliver it and how we’re progressing toward the answer. It’s also the place where we can deal with biases. Bias is a feature of every human decision-making process. If we design our team interactions intelligently, we can avoid the worst sort of biases.

Simon London: Here we’re talking about cognitive biases primarily, right? It’s not that I’m biased against you because of your accent or something. These are the cognitive biases that behavioral sciences have shown we all carry around, things like anchoring, overoptimism—these kinds of things.

Both: Yeah.

Charles Conn: Availability bias is the one that I’m always alert to. You think you’ve seen the problem before, and therefore what’s available is your previous conception of it—and we have to be most careful about that. In any human setting, we also have to be careful about biases that are based on hierarchies, sometimes called sunflower bias. I’m sure, Hugo, with your teams, you make sure that the youngest team members speak first. Not the oldest team members, because it’s easy for people to look at who’s senior and alter their own creative approaches.

Hugo Sarrazin: It’s helpful, at that moment—if someone is asserting a point of view—to ask the question “This was true in what context?” You’re trying to apply something that worked in one context to a different one. That can be deadly if the context has changed, and that’s why organizations struggle to change. You promote all these people because they did something that worked well in the past, and then there’s a disruption in the industry, and they keep doing what got them promoted even though the context has changed.

Simon London: Right. Right.

Hugo Sarrazin: So it’s the same thing in problem solving.

Charles Conn: And it’s why diversity in our teams is so important. It’s one of the best things about the world that we’re in now. We’re likely to have people from different socioeconomic, ethnic, and national backgrounds, each of whom sees problems from a slightly different perspective. It is therefore much more likely that the team will uncover a truly creative and clever approach to problem solving.

Simon London: Let’s move on to step five. You’ve done your work plan. Now you’ve actually got to do the analysis. The thing that strikes me here is that the range of tools that we have at our disposal now, of course, is just huge, particularly with advances in computation, advanced analytics. There’s so many things that you can apply here. Just talk about the analysis stage. How do you pick the right tools?

Charles Conn: For me, the most important thing is that we start with simple heuristics and explanatory statistics before we go off and use the big-gun tools. We need to understand the shape and scope of our problem before we start applying these massive and complex analytical approaches.

Simon London: Would you agree with that?

Hugo Sarrazin: I agree. I think there are so many wonderful heuristics. You need to start there before you go deep into the modeling exercise. There’s an interesting dynamic that’s happening, though. In some cases, for some types of problems, it is even better to set yourself up to maximize your learning. Your problem-solving methodology is test and learn, test and learn, test and learn, and iterate. That is a heuristic in itself, the A/B testing that is used in many parts of the world. So that’s a problem-solving methodology. It’s nothing different. It just uses technology and feedback loops in a fast way. The other one is exploratory data analysis. When you’re dealing with a large-scale problem, and there’s so much data, I can get to the heuristics that Charles was talking about through very clever visualization of data.

You test with your data. You need to set up an environment to do so, but don’t get caught up in neural-network modeling immediately. You’re testing, you’re checking—“Is the data right? Is it sound? Does it make sense?”—before you launch too far.

Simon London: You do hear these ideas—that if you have a big enough data set and enough algorithms, they’re going to find things that you just wouldn’t have spotted, find solutions that maybe you wouldn’t have thought of. Does machine learning sort of revolutionize the problem-solving process? Or are these actually just other tools in the toolbox for structured problem solving?

Charles Conn: It can be revolutionary. There are some areas in which the pattern recognition of large data sets and good algorithms can help us see things that we otherwise couldn’t see. But I do think it’s terribly important we don’t think that this particular technique is a substitute for superb problem solving, starting with good problem definition. Many people use machine learning without understanding algorithms that themselves can have biases built into them. Just as 20 years ago, when we were doing statistical analysis, we knew that we needed good model definition, we still need a good understanding of our algorithms and really good problem definition before we launch off into big data sets and unknown algorithms.

Simon London: Step six. You’ve done your analysis.

Charles Conn: I take six and seven together, and this is the place where young problem solvers often make a mistake. They’ve got their analysis, and they assume that’s the answer, and of course it isn’t the answer. The ability to synthesize the pieces that came out of the analysis and begin to weave those into a story that helps people answer the question “What should I do?” This is back to where we started. If we can’t synthesize, and we can’t tell a story, then our decision maker can’t find the answer to “What should I do?”

Simon London: But, again, these final steps are about motivating people to action, right?

Charles Conn: Yeah.

Simon London: I am slightly torn about the nomenclature of problem solving because it’s on paper, right? Until you motivate people to action, you actually haven’t solved anything.

Charles Conn: I love this question because I think decision-making theory, without a bias to action, is a waste of time. Everything in how I approach this is to help people take action that makes the world better.

Simon London: Hence, these are absolutely critical steps. If you don’t do this well, you’ve just got a bunch of analysis.

Charles Conn: We end up in exactly the same place where we started, which is people speaking across each other, past each other in the public square, rather than actually working together, shoulder to shoulder, to crack these important problems.

Simon London: In the real world, we have a lot of uncertainty—arguably, increasing uncertainty. How do good problem solvers deal with that?

Hugo Sarrazin: At every step of the process. In the problem definition, when you’re defining the context, you need to understand those sources of uncertainty and whether they’re important or not important. It becomes important in the definition of the tree.

You need to think carefully about the branches of the tree that are more certain and less certain as you define them. They don’t have equal weight just because they’ve got equal space on the page. Then, when you’re prioritizing, your prioritization approach may put more emphasis on things that have low probability but huge impact—or, vice versa, may put a lot of priority on things that are very likely and, hopefully, have a reasonable impact. You can introduce that along the way. When you come back to the synthesis, you just need to be nuanced about what you’re understanding, the likelihood.

Often, people lack humility in the way they make their recommendations: “This is the answer.” They’re very precise, and I think we would all be well-served to say, “This is a likely answer under the following sets of conditions” and then make the level of uncertainty clearer, if that is appropriate. It doesn’t mean you’re always in the gray zone; it doesn’t mean you don’t have a point of view. It just means that you can be explicit about the certainty of your answer when you make that recommendation.

Simon London: So it sounds like there is an underlying principle: “Acknowledge and embrace the uncertainty. Don’t pretend that it isn’t there. Be very clear about what the uncertainties are up front, and then build that into every step of the process.”

Hugo Sarrazin: Every step of the process.

Simon London: Yeah. We have just walked through a particular structured methodology for problem solving. But, of course, this is not the only structured methodology for problem solving. One that is also very well-known is design thinking, which comes at things very differently. So, Hugo, I know you have worked with a lot of designers. Just give us a very quick summary. Design thinking—what is it, and how does it relate?

Hugo Sarrazin: It starts with an incredible amount of empathy for the user and uses that to define the problem. It does pause and go out in the wild and spend an enormous amount of time seeing how people interact with objects, seeing the experience they’re getting, seeing the pain points or joy—and uses that to infer and define the problem.

Simon London: Problem definition, but out in the world.

Hugo Sarrazin: With an enormous amount of empathy. There’s a huge emphasis on empathy. Traditional, more classic problem solving is you define the problem based on an understanding of the situation. This one almost presupposes that we don’t know the problem until we go see it. The second thing is you need to come up with multiple scenarios or answers or ideas or concepts, and there’s a lot of divergent thinking initially. That’s slightly different, versus the prioritization, but not for long. Eventually, you need to kind of say, “OK, I’m going to converge again.” Then you go and you bring things back to the customer and get feedback and iterate. Then you rinse and repeat, rinse and repeat. There’s a lot of tactile building, along the way, of prototypes and things like that. It’s very iterative.

Simon London: So, Charles, are these complements or are these alternatives?

Charles Conn: I think they’re entirely complementary, and I think Hugo’s description is perfect. When we do problem definition well in classic problem solving, we are demonstrating the kind of empathy, at the very beginning of our problem, that design thinking asks us to approach. When we ideate—and that’s very similar to the disaggregation, prioritization, and work-planning steps—we do precisely the same thing, and often we use contrasting teams, so that we do have divergent thinking. The best teams allow divergent thinking to bump them off whatever their initial biases in problem solving are. For me, design thinking gives us a constant reminder of creativity, empathy, and the tactile nature of problem solving, but it’s absolutely complementary, not alternative.

Simon London: I think, in a world of cross-functional teams, an interesting question is do people with design-thinking backgrounds really work well together with classical problem solvers? How do you make that chemistry happen?

Hugo Sarrazin: Yeah, it is not easy when people have spent an enormous amount of time seeped in design thinking or user-centric design, whichever word you want to use. If the person who’s applying classic problem-solving methodology is very rigid and mechanical in the way they’re doing it, there could be an enormous amount of tension. If there’s not clarity in the role and not clarity in the process, I think having the two together can be, sometimes, problematic.

The second thing that happens often is that the artifacts the two methodologies try to gravitate toward can be different. Classic problem solving often gravitates toward a model; design thinking migrates toward a prototype. Rather than writing a big deck with all my supporting evidence, they’ll bring an example, a thing, and that feels different. Then you spend your time differently to achieve those two end products, so that’s another source of friction.

Now, I still think it can be an incredibly powerful thing to have the two—if there are the right people with the right mind-set, if there is a team that is explicit about the roles, if we’re clear about the kind of outcomes we are attempting to bring forward. There’s an enormous amount of collaborativeness and respect.

Simon London: But they have to respect each other’s methodology and be prepared to flex, maybe, a little bit, in how this process is going to work.

Hugo Sarrazin: Absolutely.

Simon London: The other area where, it strikes me, there could be a little bit of a different sort of friction is this whole concept of the day-one answer, which is what we were just talking about in classical problem solving. Now, you know that this is probably not going to be your final answer, but that’s how you begin to structure the problem. Whereas I would imagine your design thinkers—no, they’re going off to do their ethnographic research and get out into the field, potentially for a long time, before they come back with at least an initial hypothesis.

Want better strategies? Become a bulletproof problem solver

Hugo Sarrazin: That is a great callout, and that’s another difference. Designers typically will like to soak into the situation and avoid converging too quickly. There’s optionality and exploring different options. There’s a strong belief that keeps the solution space wide enough that you can come up with more radical ideas. If there’s a large design team or many designers on the team, and you come on Friday and say, “What’s our week-one answer?” they’re going to struggle. They’re not going to be comfortable, naturally, to give that answer. It doesn’t mean they don’t have an answer; it’s just not where they are in their thinking process.

Simon London: I think we are, sadly, out of time for today. But Charles and Hugo, thank you so much.

Charles Conn: It was a pleasure to be here, Simon.

Hugo Sarrazin: It was a pleasure. Thank you.

Simon London: And thanks, as always, to you, our listeners, for tuning into this episode of the McKinsey Podcast . If you want to learn more about problem solving, you can find the book, Bulletproof Problem Solving: The One Skill That Changes Everything , online or order it through your local bookstore. To learn more about McKinsey, you can of course find us at McKinsey.com.

Charles Conn is CEO of Oxford Sciences Innovation and an alumnus of McKinsey’s Sydney office. Hugo Sarrazin is a senior partner in the Silicon Valley office, where Simon London, a member of McKinsey Publishing, is also based.

Explore a career with us

Related articles.

Strategy to beat the odds

Five routes to more innovative problem solving

• Coaching Skills Training
• Coaching TIPS²™
• Continuous Improvement Coaching
• Courageous Conversations Workshop
• Executive Coaching Program
• Feedback 360
• Safety Coaching
• Sales Coaching Training Program
• Free Consultation
• Applied Strategic Thinking®
• Strategic Leadership Course
• Strategic Teaming
• Strategy Development Processes and Services
• Communication Training for Managers
• Conflict and Collaboration
• Confronting Racism Workshop
• Delegation & Accountability
• Diversity, Equity, and Inclusion Workshop
• Flexible Leadership
• Leading Change
• Leading Groups to Solutions
• Leading Innovation
• Mid-Level Management Training
• Qualities of Leadership
• Bottom Line Leadership
• Customized Leadership Development Programs
• Leadership Development Program Design
• Mini-MBA & Operational Finance
• Problem Solving and Decision Making in the Workplace
• Transition to Leadership
• Virtual Leadership
• High-Performance Teamwork
• Leadership Team Alignment Workshop
• Orienteering
• Corporate Outdoor Training and Team Building
• Retreats for Teams
• Innovation Skills Training
• Personal Impact Workshop
• Supervisor Training Programs
• Customization of CMOE’s Learning Library
• Full Curriculum Development and Design
• Learning & Development Advisory Services
• Bottom Line Leadership Training
• Consulting Services
• Leadership Retreats
• Learning and Development Consulting Services
• Needs Analysis and Organization Assessments
• Transformation & Change Solutions
• Facilitator Training Workshop
• Empathic Leadership
• Supervisor Development Series
• All Courses
• Digital Learning
• Books and Publications
• Assessments and Surveys
• Clients Served
• History and Experience
• Meet the CMOE Team
• Testimonials
• Articles & Tools
• Scenario Templates
• Certified Partners
• Event Resources
• Industry Insights
• Resource Library
• Video Library
• News and Events
• Professional Accreditation and Continuing Education Units
• Surveys & Assessments
• Problem Solving in Business
• 360-Degree Leadership Assessment
• Adaptive Communication
• Adaptive Leadership
• Authentic Leadership Style
• Boundary Spanning Leadership
• Business Change Strategies
• Business-Strategy Principles
• Capacity Building
• Cascading Strategy
• Change Management
• Coaching Framework
• Coaching in the Workplace
• Coaching Leadership Style
• Collaborative Coaching
• Competency Assessment
• Conflict Resolution in the Workplace
• Core Competence
• Corporate Strategic Planning
• Crisis Leadership
• Critical Success Factors
• DEI in the Workplace
• Directive Leader
• Empathetic Leadership Definition
• Horizontal Leadership
• Inclusive Leadership
• Innovation Strategy
• Leadership Assessment
• Leadership Competency Framework
• Leadership Model
• Management Succession Planning
• Operational Excellence
• Organizational Alignment
• Participative Leadership Style
• Performance Deficiency Coaching
• Persuasive Leadership Style
• Servant Leadership Style
• Strategic Agility
• Strategic Alignment
• Strategic Audit
• Strategic Framework
• Strategic Initiatives: Examples and Development
• Strategic Management
• Strategic Mindset Competency
• Strategic Thinking
• Strategy Committee
• Strategy Issues
• Strategy Maps
• Supportive Leadership Style: Definition and Qualities
• Team Building Interventions
• Team Environment
• Team Performance Assessment
• Teamwork Atmosphere
• Total Employee Involvement
• Training Needs Analysis (TNA) Definition
• Transformational Leadership
• Visionary Leadership Style

What Is Problem Solving in Business?

Problem-solving in business is defined as implementing processes that reduce or remove obstacles that are preventing you or others from accomplishing operational and strategic business goals.

In business, a problem is a situation that creates a gap between the desired and actual outcomes. In addition, a true problem typically does not have an immediately obvious resolution.

Business problem-solving works best when it is approached through a consistent system in which individuals:

• Identify and define the problem
• Prioritize the problem based on size, potential impact, and urgency
• Complete a root-cause analysis
• Develop a variety of possible solutions
• Evaluate possible solutions and decide which is most effective
• Plan and implement the solution

Why Is Problem-Solving Important in Business?

Understanding the importance of problem-solving skills in the workplace will help you develop as a leader. Problem-solving skills will help you resolve critical issues and conflicts that you come across. Problem-solving is a valued skill in the workplace because it allows you to:

• Apply a standard problem-solving system to all challenges
• Find the root causes of problems
• Quickly deal with short-term business interruptions
• Form plans to deal with long-term problems and improve the organization
• See challenges as opportunities
• Keep your cool during challenges

How Do You Solve Business Problems Effectively?

There are many different problem-solving strategies, but most can be broken into general steps. Here is a six-step method for business problem solving:

1) Identify the Details of the Problem: Gather enough information to accurately define the problem. This can include data on procedures being used, employee actions, relevant workplace rules, and so on. Write down the specific outcome that is needed, but don’t assume what the solution should be.

• Use the Five Whys: When assessing a problem, a common strategy is to ask “why” five times. First, ask why the problem occurred. Then, take the answer and ask “why” again, and so on. The intention is to help you get down to the root cause of the problem so you can directly target that core issue with your solution.

2) Creatively Brainstorm Solutions:   State every solution you can think of. Write them down. Seek input from those who possess in-depth knowledge of or experience with the problem you’re trying to solve. These insights will provide you with valuable perspectives you can transform into tangible and impactful solutions.

3) Evaluate Solutions and Make a Decision:   Assess the feasibility of each solution. Is the deadline realistic? Are there readily available resources you can leverage to successfully implement the solution? What is the return on investment of each solution? If necessary, come up with alternative solutions or adjust the initial ones you brainstormed in step 2.

4) Make a Decision: Finally, make a firm decision on one solution. This final solution should clearly address the root cause of the problem.

• Perform a SWOT Analysis: You can use a SWOT analysis to help you decide on the best solution. A SWOT analysis involves identifying the strengths, weaknesses, opportunities, and threats linked to a specific decision. With this framework, your team can assess a decision from various angles, thereby gaining a holistic view of it.

5) Take Action:   Write up a detailed plan. This involves developing a comprehensive roadmap that outlines the steps required to implement your solution. The steps should specify milestones, deadlines, roles, and how to obtain the necessary approvals. To ensure accountability, your entire team should have access to this action plan. Each team member should be able to track and share their progress with the group.

6) Gather and Share Feedback: Problem-solving is not a “set it and forget it” process. It’s a dynamic journey that necessitates ongoing attention, deliberation, and refinement to achieve optimal results. Thus, periodic feedback is critical in validating whether the chosen solution creates the desired impact. It allows key stakeholders to check in and make any necessary changes.

What Are Problem-Solving Skills?

Problem-solving skills are specific procedures that can be used to complete one or more of the six general steps of problem-solving (discussed above). Here are five important examples:

Using Emotional Intelligence: You’ll solve problems more calmly when you learn to recognize your own emotional patterns and to empathize with and guide the emotions of others. Avoid knee-jerk responses and making assumptions.

Researching Problems: An effective solution requires an accurate description of the problem. Define simple problems using quick research methods such as asking, “What? Where? When? and How much?.” Difficult problems require more in-depth research, such as data exploration, surveys, and interviews.

Creative Brainstorming: When brainstorming with a group, encourage idea creation by listening attentively to everyone, and recognizing everyone’s unique contributions.

Logical Reasoning: Develop standard logical steps for analyzing possible solutions to problems. Study and apply ideas about logical fallacies, deductive reasoning, and other areas of analytical thought.

Decisiveness: Use an agreed-upon system for choosing a solution, which can include assigning pros and cons to solutions, identifying mandatory results, getting feedback about solutions, choosing the decision-maker(s), and finishing or repeating the process.

How Can You Improve Your Problem-Solving Skills?

Learning how to solve business problems takes time and effort. Though some people appear to have been born with superior problem-solving skills, great problem-solvers usually have taken the time to refine their abilities. You can develop high-level skills for solving problems too, through the following methods:

Ask and Listen: Don’t expect to solve every problem alone. Ask for advice, and listen to it carefully.

Practice Curiosity: Any time you’re involved in solving a problem, practice researching and defining the problem just a little longer than you would naturally.

Break Down Problems: Whenever possible, break large problems into their smallest units. Then, search for solutions to one unit at a time.

Don’t Label Yourself Negatively: Don’t allow a problem to mean something negative about you personally. Separate yourself from it. Look at it objectively and be part of the solution.

Enhance Your Problem-Solving Skills with CMOE

Problem-solving skills in business are not developed overnight. Developing then takes ongoing practice and the right guidance to get right. We encourage you to leverage CMOE’s Problem-Solving and Decision Making in the Workplace workshop to further develop your skills. We’ll help you identify new ways to solve problems methodically so you can create greater impact.

Clients We’ve Worked With

Contact form.

Need More Information? Please fill out the following form and we will be in contact with you with more information.

" * " indicates required fields

As Featured In:

The Better Business Bureau has determined that CMOE meets accreditation standards. These standards verify that CMOE’s product quality and competence enhance customer trust and confidence.

©2024 Center for Management & Organization Effectiveness. All rights reserved.

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

Overview of the Problem-Solving Mental Process

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

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

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

Frequently Asked Questions

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

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

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

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

The following steps include developing strategies and organizing knowledge.

1. Identifying the Problem

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

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

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

2. Defining the Problem

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

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

3. Forming a Strategy

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

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

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

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

4. Organizing Information

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

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

5. Allocating Resources

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

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

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

6. Monitoring Progress

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

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

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

7. Evaluating the Results

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

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

A Word From Verywell​

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

Get Advice From The Verywell Mind Podcast

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

Follow Now : Apple Podcasts / Spotify / Google Podcasts

You can become a better problem solving by:

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

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

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

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

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

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

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

35 problem-solving techniques and methods for solving complex problems

Design your next session with SessionLab

Join the 150,000+ facilitators 
using SessionLab.

Recommended Articles

A step-by-step guide to planning a workshop, how to create an unforgettable training session in 8 simple steps, 47 useful online tools for workshop planning and meeting facilitation.

All teams and organizations encounter challenges as they grow. There are problems that might occur for teams when it comes to miscommunication or resolving business-critical issues . You may face challenges around growth , design , user engagement, and even team culture and happiness. In short, problem-solving techniques should be part of every team’s skillset.

Problem-solving methods are primarily designed to help a group or team through a process of first identifying problems and challenges , ideating possible solutions , and then evaluating the most suitable .

Finding effective solutions to complex problems isn’t easy, but by using the right process and techniques, you can help your team be more efficient in the process.

So how do you develop strategies that are engaging, and empower your team to solve problems effectively?

In this blog post, we share a series of problem-solving tools you can use in your next workshop or team meeting. You’ll also find some tips for facilitating the process and how to enable others to solve complex problems.

Let’s get started! 

How do you identify problems?

How do you identify the right solution.

• Tips for more effective problem-solving

Complete problem-solving methods

• Problem-solving techniques to identify and analyze problems
• Problem-solving techniques for developing solutions

Problem-solving warm-up activities

Closing activities for a problem-solving process.

Before you can move towards finding the right solution for a given problem, you first need to identify and define the problem you wish to solve. 

Here, you want to clearly articulate what the problem is and allow your group to do the same. Remember that everyone in a group is likely to have differing perspectives and alignment is necessary in order to help the group move forward. 

Identifying a problem accurately also requires that all members of a group are able to contribute their views in an open and safe manner. It can be scary for people to stand up and contribute, especially if the problems or challenges are emotive or personal in nature. Be sure to try and create a psychologically safe space for these kinds of discussions.

Remember that problem analysis and further discussion are also important. Not taking the time to fully analyze and discuss a challenge can result in the development of solutions that are not fit for purpose or do not address the underlying issue.

Successfully identifying and then analyzing a problem means facilitating a group through activities designed to help them clearly and honestly articulate their thoughts and produce usable insight.

With this data, you might then produce a problem statement that clearly describes the problem you wish to be addressed and also state the goal of any process you undertake to tackle this issue.  

Finding solutions is the end goal of any process. Complex organizational challenges can only be solved with an appropriate solution but discovering them requires using the right problem-solving tool.

After you’ve explored a problem and discussed ideas, you need to help a team discuss and choose the right solution. Consensus tools and methods such as those below help a group explore possible solutions before then voting for the best. They’re a great way to tap into the collective intelligence of the group for great results!

Remember that the process is often iterative. Great problem solvers often roadtest a viable solution in a measured way to see what works too. While you might not get the right solution on your first try, the methods below help teams land on the most likely to succeed solution while also holding space for improvement.

Every effective problem solving process begins with an agenda . A well-structured workshop is one of the best methods for successfully guiding a group from exploring a problem to implementing a solution.

In SessionLab, it’s easy to go from an idea to a complete agenda . Start by dragging and dropping your core problem solving activities into place . Add timings, breaks and necessary materials before sharing your agenda with your colleagues.

The resulting agenda will be your guide to an effective and productive problem solving session that will also help you stay organized on the day!

Tips for more effective problem solving

Problem-solving activities are only one part of the puzzle. While a great method can help unlock your team’s ability to solve problems, without a thoughtful approach and strong facilitation the solutions may not be fit for purpose.

Let’s take a look at some problem-solving tips you can apply to any process to help it be a success!

Clearly define the problem

Jumping straight to solutions can be tempting, though without first clearly articulating a problem, the solution might not be the right one. Many of the problem-solving activities below include sections where the problem is explored and clearly defined before moving on.

This is a vital part of the problem-solving process and taking the time to fully define an issue can save time and effort later. A clear definition helps identify irrelevant information and it also ensures that your team sets off on the right track.

Don’t jump to conclusions

It’s easy for groups to exhibit cognitive bias or have preconceived ideas about both problems and potential solutions. Be sure to back up any problem statements or potential solutions with facts, research, and adequate forethought.

The best techniques ask participants to be methodical and challenge preconceived notions. Make sure you give the group enough time and space to collect relevant information and consider the problem in a new way. By approaching the process with a clear, rational mindset, you’ll often find that better solutions are more forthcoming.  

Try different approaches  

Problems come in all shapes and sizes and so too should the methods you use to solve them. If you find that one approach isn’t yielding results and your team isn’t finding different solutions, try mixing it up. You’ll be surprised at how using a new creative activity can unblock your team and generate great solutions.

Don’t take it personally 

Depending on the nature of your team or organizational problems, it’s easy for conversations to get heated. While it’s good for participants to be engaged in the discussions, ensure that emotions don’t run too high and that blame isn’t thrown around while finding solutions.

You’re all in it together, and even if your team or area is seeing problems, that isn’t necessarily a disparagement of you personally. Using facilitation skills to manage group dynamics is one effective method of helping conversations be more constructive.

Get the right people in the room

Your problem-solving method is often only as effective as the group using it. Getting the right people on the job and managing the number of people present is important too!

If the group is too small, you may not get enough different perspectives to effectively solve a problem. If the group is too large, you can go round and round during the ideation stages.

Creating the right group makeup is also important in ensuring you have the necessary expertise and skillset to both identify and follow up on potential solutions. Carefully consider who to include at each stage to help ensure your problem-solving method is followed and positioned for success.

Document everything

The best solutions can take refinement, iteration, and reflection to come out. Get into a habit of documenting your process in order to keep all the learnings from the session and to allow ideas to mature and develop. Many of the methods below involve the creation of documents or shared resources. Be sure to keep and share these so everyone can benefit from the work done!

Bring a facilitator 

Facilitation is all about making group processes easier. With a subject as potentially emotive and important as problem-solving, having an impartial third party in the form of a facilitator can make all the difference in finding great solutions and keeping the process moving. Consider bringing a facilitator to your problem-solving session to get better results and generate meaningful solutions!

Develop your problem-solving skills

It takes time and practice to be an effective problem solver. While some roles or participants might more naturally gravitate towards problem-solving, it can take development and planning to help everyone create better solutions.

You might develop a training program, run a problem-solving workshop or simply ask your team to practice using the techniques below. Check out our post on problem-solving skills to see how you and your group can develop the right mental process and be more resilient to issues too!

Design a great agenda

Workshops are a great format for solving problems. With the right approach, you can focus a group and help them find the solutions to their own problems. But designing a process can be time-consuming and finding the right activities can be difficult.

Check out our workshop planning guide to level-up your agenda design and start running more effective workshops. Need inspiration? Check out templates designed by expert facilitators to help you kickstart your process!

In this section, we’ll look at in-depth problem-solving methods that provide a complete end-to-end process for developing effective solutions. These will help guide your team from the discovery and definition of a problem through to delivering the right solution.

If you’re looking for an all-encompassing method or problem-solving model, these processes are a great place to start. They’ll ask your team to challenge preconceived ideas and adopt a mindset for solving problems more effectively.

• Six Thinking Hats
• Lightning Decision Jam
• Problem Definition Process
• Discovery & Action Dialogue

Design Sprint 2.0

• Open Space Technology

1. Six Thinking Hats

Individual approaches to solving a problem can be very different based on what team or role an individual holds. It can be easy for existing biases or perspectives to find their way into the mix, or for internal politics to direct a conversation.

Six Thinking Hats is a classic method for identifying the problems that need to be solved and enables your team to consider them from different angles, whether that is by focusing on facts and data, creative solutions, or by considering why a particular solution might not work.

Like all problem-solving frameworks, Six Thinking Hats is effective at helping teams remove roadblocks from a conversation or discussion and come to terms with all the aspects necessary to solve complex problems.

2. Lightning Decision Jam

Featured courtesy of Jonathan Courtney of AJ&Smart Berlin, Lightning Decision Jam is one of those strategies that should be in every facilitation toolbox. Exploring problems and finding solutions is often creative in nature, though as with any creative process, there is the potential to lose focus and get lost.

Unstructured discussions might get you there in the end, but it’s much more effective to use a method that creates a clear process and team focus.

In Lightning Decision Jam, participants are invited to begin by writing challenges, concerns, or mistakes on post-its without discussing them before then being invited by the moderator to present them to the group.

From there, the team vote on which problems to solve and are guided through steps that will allow them to reframe those problems, create solutions and then decide what to execute on. 

By deciding the problems that need to be solved as a team before moving on, this group process is great for ensuring the whole team is aligned and can take ownership over the next stages. 

Lightning Decision Jam (LDJ)   #action   #decision making   #problem solving   #issue analysis   #innovation   #design   #remote-friendly   The problem with anything that requires creative thinking is that it’s easy to get lost—lose focus and fall into the trap of having useless, open-ended, unstructured discussions. Here’s the most effective solution I’ve found: Replace all open, unstructured discussion with a clear process. What to use this exercise for: Anything which requires a group of people to make decisions, solve problems or discuss challenges. It’s always good to frame an LDJ session with a broad topic, here are some examples: The conversion flow of our checkout Our internal design process How we organise events Keeping up with our competition Improving sales flow

3. Problem Definition Process

While problems can be complex, the problem-solving methods you use to identify and solve those problems can often be simple in design. 

By taking the time to truly identify and define a problem before asking the group to reframe the challenge as an opportunity, this method is a great way to enable change.

Begin by identifying a focus question and exploring the ways in which it manifests before splitting into five teams who will each consider the problem using a different method: escape, reversal, exaggeration, distortion or wishful. Teams develop a problem objective and create ideas in line with their method before then feeding them back to the group.

This method is great for enabling in-depth discussions while also creating space for finding creative solutions too!

Problem Definition   #problem solving   #idea generation   #creativity   #online   #remote-friendly   A problem solving technique to define a problem, challenge or opportunity and to generate ideas.

4. The 5 Whys 

Sometimes, a group needs to go further with their strategies and analyze the root cause at the heart of organizational issues. An RCA or root cause analysis is the process of identifying what is at the heart of business problems or recurring challenges. 

The 5 Whys is a simple and effective method of helping a group go find the root cause of any problem or challenge and conduct analysis that will deliver results. 

By beginning with the creation of a problem statement and going through five stages to refine it, The 5 Whys provides everything you need to truly discover the cause of an issue.

The 5 Whys   #hyperisland   #innovation   This simple and powerful method is useful for getting to the core of a problem or challenge. As the title suggests, the group defines a problems, then asks the question “why” five times, often using the resulting explanation as a starting point for creative problem solving.

5. World Cafe

World Cafe is a simple but powerful facilitation technique to help bigger groups to focus their energy and attention on solving complex problems.

World Cafe enables this approach by creating a relaxed atmosphere where participants are able to self-organize and explore topics relevant and important to them which are themed around a central problem-solving purpose. Create the right atmosphere by modeling your space after a cafe and after guiding the group through the method, let them take the lead!

Making problem-solving a part of your organization’s culture in the long term can be a difficult undertaking. More approachable formats like World Cafe can be especially effective in bringing people unfamiliar with workshops into the fold. 

World Cafe   #hyperisland   #innovation   #issue analysis   World Café is a simple yet powerful method, originated by Juanita Brown, for enabling meaningful conversations driven completely by participants and the topics that are relevant and important to them. Facilitators create a cafe-style space and provide simple guidelines. Participants then self-organize and explore a set of relevant topics or questions for conversation.

6. Discovery & Action Dialogue (DAD)

One of the best approaches is to create a safe space for a group to share and discover practices and behaviors that can help them find their own solutions.

With DAD, you can help a group choose which problems they wish to solve and which approaches they will take to do so. It’s great at helping remove resistance to change and can help get buy-in at every level too!

This process of enabling frontline ownership is great in ensuring follow-through and is one of the methods you will want in your toolbox as a facilitator.

Discovery & Action Dialogue (DAD)   #idea generation   #liberating structures   #action   #issue analysis   #remote-friendly   DADs make it easy for a group or community to discover practices and behaviors that enable some individuals (without access to special resources and facing the same constraints) to find better solutions than their peers to common problems. These are called positive deviant (PD) behaviors and practices. DADs make it possible for people in the group, unit, or community to discover by themselves these PD practices. DADs also create favorable conditions for stimulating participants’ creativity in spaces where they can feel safe to invent new and more effective practices. Resistance to change evaporates as participants are unleashed to choose freely which practices they will adopt or try and which problems they will tackle. DADs make it possible to achieve frontline ownership of solutions.

7. Design Sprint 2.0

Want to see how a team can solve big problems and move forward with prototyping and testing solutions in a few days? The Design Sprint 2.0 template from Jake Knapp, author of Sprint, is a complete agenda for a with proven results.

Developing the right agenda can involve difficult but necessary planning. Ensuring all the correct steps are followed can also be stressful or time-consuming depending on your level of experience.

Use this complete 4-day workshop template if you are finding there is no obvious solution to your challenge and want to focus your team around a specific problem that might require a shortcut to launching a minimum viable product or waiting for the organization-wide implementation of a solution.

8. Open space technology

Open space technology- developed by Harrison Owen – creates a space where large groups are invited to take ownership of their problem solving and lead individual sessions. Open space technology is a great format when you have a great deal of expertise and insight in the room and want to allow for different takes and approaches on a particular theme or problem you need to be solved.

Start by bringing your participants together to align around a central theme and focus their efforts. Explain the ground rules to help guide the problem-solving process and then invite members to identify any issue connecting to the central theme that they are interested in and are prepared to take responsibility for.

Once participants have decided on their approach to the core theme, they write their issue on a piece of paper, announce it to the group, pick a session time and place, and post the paper on the wall. As the wall fills up with sessions, the group is then invited to join the sessions that interest them the most and which they can contribute to, then you’re ready to begin!

Everyone joins the problem-solving group they’ve signed up to, record the discussion and if appropriate, findings can then be shared with the rest of the group afterward.

Open Space Technology   #action plan   #idea generation   #problem solving   #issue analysis   #large group   #online   #remote-friendly   Open Space is a methodology for large groups to create their agenda discerning important topics for discussion, suitable for conferences, community gatherings and whole system facilitation

Techniques to identify and analyze problems

Using a problem-solving method to help a team identify and analyze a problem can be a quick and effective addition to any workshop or meeting.

While further actions are always necessary, you can generate momentum and alignment easily, and these activities are a great place to get started.

We’ve put together this list of techniques to help you and your team with problem identification, analysis, and discussion that sets the foundation for developing effective solutions.

Let’s take a look!

• The Creativity Dice
• Fishbone Analysis
• Problem Tree
• SWOT Analysis
• Agreement-Certainty Matrix
• The Journalistic Six
• LEGO Challenge
• What, So What, Now What?
• Journalists

Individual and group perspectives are incredibly important, but what happens if people are set in their minds and need a change of perspective in order to approach a problem more effectively?

Flip It is a method we love because it is both simple to understand and run, and allows groups to understand how their perspectives and biases are formed. 

Participants in Flip It are first invited to consider concerns, issues, or problems from a perspective of fear and write them on a flip chart. Then, the group is asked to consider those same issues from a perspective of hope and flip their understanding.  

No problem and solution is free from existing bias and by changing perspectives with Flip It, you can then develop a problem solving model quickly and effectively.

Flip It!   #gamestorming   #problem solving   #action   Often, a change in a problem or situation comes simply from a change in our perspectives. Flip It! is a quick game designed to show players that perspectives are made, not born.

10. The Creativity Dice

One of the most useful problem solving skills you can teach your team is of approaching challenges with creativity, flexibility, and openness. Games like The Creativity Dice allow teams to overcome the potential hurdle of too much linear thinking and approach the process with a sense of fun and speed. 

In The Creativity Dice, participants are organized around a topic and roll a dice to determine what they will work on for a period of 3 minutes at a time. They might roll a 3 and work on investigating factual information on the chosen topic. They might roll a 1 and work on identifying the specific goals, standards, or criteria for the session.

Encouraging rapid work and iteration while asking participants to be flexible are great skills to cultivate. Having a stage for idea incubation in this game is also important. Moments of pause can help ensure the ideas that are put forward are the most suitable. 

The Creativity Dice   #creativity   #problem solving   #thiagi   #issue analysis   Too much linear thinking is hazardous to creative problem solving. To be creative, you should approach the problem (or the opportunity) from different points of view. You should leave a thought hanging in mid-air and move to another. This skipping around prevents premature closure and lets your brain incubate one line of thought while you consciously pursue another.

11. Fishbone Analysis

Organizational or team challenges are rarely simple, and it’s important to remember that one problem can be an indication of something that goes deeper and may require further consideration to be solved.

Fishbone Analysis helps groups to dig deeper and understand the origins of a problem. It’s a great example of a root cause analysis method that is simple for everyone on a team to get their head around. 

Participants in this activity are asked to annotate a diagram of a fish, first adding the problem or issue to be worked on at the head of a fish before then brainstorming the root causes of the problem and adding them as bones on the fish. 

Using abstractions such as a diagram of a fish can really help a team break out of their regular thinking and develop a creative approach.

Fishbone Analysis   #problem solving   ##root cause analysis   #decision making   #online facilitation   A process to help identify and understand the origins of problems, issues or observations.

12. Problem Tree 

Encouraging visual thinking can be an essential part of many strategies. By simply reframing and clarifying problems, a group can move towards developing a problem solving model that works for them. 

In Problem Tree, groups are asked to first brainstorm a list of problems – these can be design problems, team problems or larger business problems – and then organize them into a hierarchy. The hierarchy could be from most important to least important or abstract to practical, though the key thing with problem solving games that involve this aspect is that your group has some way of managing and sorting all the issues that are raised.

Once you have a list of problems that need to be solved and have organized them accordingly, you’re then well-positioned for the next problem solving steps.

Problem tree   #define intentions   #create   #design   #issue analysis   A problem tree is a tool to clarify the hierarchy of problems addressed by the team within a design project; it represents high level problems or related sublevel problems.

13. SWOT Analysis

Chances are you’ve heard of the SWOT Analysis before. This problem-solving method focuses on identifying strengths, weaknesses, opportunities, and threats is a tried and tested method for both individuals and teams.

Start by creating a desired end state or outcome and bare this in mind – any process solving model is made more effective by knowing what you are moving towards. Create a quadrant made up of the four categories of a SWOT analysis and ask participants to generate ideas based on each of those quadrants.

Once you have those ideas assembled in their quadrants, cluster them together based on their affinity with other ideas. These clusters are then used to facilitate group conversations and move things forward. 

SWOT analysis   #gamestorming   #problem solving   #action   #meeting facilitation   The SWOT Analysis is a long-standing technique of looking at what we have, with respect to the desired end state, as well as what we could improve on. It gives us an opportunity to gauge approaching opportunities and dangers, and assess the seriousness of the conditions that affect our future. When we understand those conditions, we can influence what comes next.

14. Agreement-Certainty Matrix

Not every problem-solving approach is right for every challenge, and deciding on the right method for the challenge at hand is a key part of being an effective team.

The Agreement Certainty matrix helps teams align on the nature of the challenges facing them. By sorting problems from simple to chaotic, your team can understand what methods are suitable for each problem and what they can do to ensure effective results. 

If you are already using Liberating Structures techniques as part of your problem-solving strategy, the Agreement-Certainty Matrix can be an invaluable addition to your process. We’ve found it particularly if you are having issues with recurring problems in your organization and want to go deeper in understanding the root cause. 

Agreement-Certainty Matrix   #issue analysis   #liberating structures   #problem solving   You can help individuals or groups avoid the frequent mistake of trying to solve a problem with methods that are not adapted to the nature of their challenge. The combination of two questions makes it possible to easily sort challenges into four categories: simple, complicated, complex , and chaotic .  A problem is simple when it can be solved reliably with practices that are easy to duplicate.  It is complicated when experts are required to devise a sophisticated solution that will yield the desired results predictably.  A problem is complex when there are several valid ways to proceed but outcomes are not predictable in detail.  Chaotic is when the context is too turbulent to identify a path forward.  A loose analogy may be used to describe these differences: simple is like following a recipe, complicated like sending a rocket to the moon, complex like raising a child, and chaotic is like the game “Pin the Tail on the Donkey.”  The Liberating Structures Matching Matrix in Chapter 5 can be used as the first step to clarify the nature of a challenge and avoid the mismatches between problems and solutions that are frequently at the root of chronic, recurring problems.

Organizing and charting a team’s progress can be important in ensuring its success. SQUID (Sequential Question and Insight Diagram) is a great model that allows a team to effectively switch between giving questions and answers and develop the skills they need to stay on track throughout the process. 

Begin with two different colored sticky notes – one for questions and one for answers – and with your central topic (the head of the squid) on the board. Ask the group to first come up with a series of questions connected to their best guess of how to approach the topic. Ask the group to come up with answers to those questions, fix them to the board and connect them with a line. After some discussion, go back to question mode by responding to the generated answers or other points on the board.

It’s rewarding to see a diagram grow throughout the exercise, and a completed SQUID can provide a visual resource for future effort and as an example for other teams.

SQUID   #gamestorming   #project planning   #issue analysis   #problem solving   When exploring an information space, it’s important for a group to know where they are at any given time. By using SQUID, a group charts out the territory as they go and can navigate accordingly. SQUID stands for Sequential Question and Insight Diagram.

16. Speed Boat

To continue with our nautical theme, Speed Boat is a short and sweet activity that can help a team quickly identify what employees, clients or service users might have a problem with and analyze what might be standing in the way of achieving a solution.

Methods that allow for a group to make observations, have insights and obtain those eureka moments quickly are invaluable when trying to solve complex problems.

In Speed Boat, the approach is to first consider what anchors and challenges might be holding an organization (or boat) back. Bonus points if you are able to identify any sharks in the water and develop ideas that can also deal with competitors!   

Speed Boat   #gamestorming   #problem solving   #action   Speedboat is a short and sweet way to identify what your employees or clients don’t like about your product/service or what’s standing in the way of a desired goal.

17. The Journalistic Six

Some of the most effective ways of solving problems is by encouraging teams to be more inclusive and diverse in their thinking.

Based on the six key questions journalism students are taught to answer in articles and news stories, The Journalistic Six helps create teams to see the whole picture. By using who, what, when, where, why, and how to facilitate the conversation and encourage creative thinking, your team can make sure that the problem identification and problem analysis stages of the are covered exhaustively and thoughtfully. Reporter’s notebook and dictaphone optional.

The Journalistic Six – Who What When Where Why How   #idea generation   #issue analysis   #problem solving   #online   #creative thinking   #remote-friendly   A questioning method for generating, explaining, investigating ideas.

18. LEGO Challenge

Now for an activity that is a little out of the (toy) box. LEGO Serious Play is a facilitation methodology that can be used to improve creative thinking and problem-solving skills. 

The LEGO Challenge includes giving each member of the team an assignment that is hidden from the rest of the group while they create a structure without speaking.

What the LEGO challenge brings to the table is a fun working example of working with stakeholders who might not be on the same page to solve problems. Also, it’s LEGO! Who doesn’t love LEGO! 

LEGO Challenge   #hyperisland   #team   A team-building activity in which groups must work together to build a structure out of LEGO, but each individual has a secret “assignment” which makes the collaborative process more challenging. It emphasizes group communication, leadership dynamics, conflict, cooperation, patience and problem solving strategy.

19. What, So What, Now What?

If not carefully managed, the problem identification and problem analysis stages of the problem-solving process can actually create more problems and misunderstandings.

The What, So What, Now What? problem-solving activity is designed to help collect insights and move forward while also eliminating the possibility of disagreement when it comes to identifying, clarifying, and analyzing organizational or work problems. 

Facilitation is all about bringing groups together so that might work on a shared goal and the best problem-solving strategies ensure that teams are aligned in purpose, if not initially in opinion or insight.

Throughout the three steps of this game, you give everyone on a team to reflect on a problem by asking what happened, why it is important, and what actions should then be taken. 

This can be a great activity for bringing our individual perceptions about a problem or challenge and contextualizing it in a larger group setting. This is one of the most important problem-solving skills you can bring to your organization.

W³ – What, So What, Now What?   #issue analysis   #innovation   #liberating structures   You can help groups reflect on a shared experience in a way that builds understanding and spurs coordinated action while avoiding unproductive conflict. It is possible for every voice to be heard while simultaneously sifting for insights and shaping new direction. Progressing in stages makes this practical—from collecting facts about What Happened to making sense of these facts with So What and finally to what actions logically follow with Now What . The shared progression eliminates most of the misunderstandings that otherwise fuel disagreements about what to do. Voila!

20. Journalists  

Problem analysis can be one of the most important and decisive stages of all problem-solving tools. Sometimes, a team can become bogged down in the details and are unable to move forward.

Journalists is an activity that can avoid a group from getting stuck in the problem identification or problem analysis stages of the process.

In Journalists, the group is invited to draft the front page of a fictional newspaper and figure out what stories deserve to be on the cover and what headlines those stories will have. By reframing how your problems and challenges are approached, you can help a team move productively through the process and be better prepared for the steps to follow.

Journalists   #vision   #big picture   #issue analysis   #remote-friendly   This is an exercise to use when the group gets stuck in details and struggles to see the big picture. Also good for defining a vision.

Problem-solving techniques for developing solutions 

The success of any problem-solving process can be measured by the solutions it produces. After you’ve defined the issue, explored existing ideas, and ideated, it’s time to narrow down to the correct solution.

Use these problem-solving techniques when you want to help your team find consensus, compare possible solutions, and move towards taking action on a particular problem.

• Improved Solutions
• Four-Step Sketch
• 15% Solutions
• How-Now-Wow matrix
• Impact Effort Matrix

21. Mindspin  

Brainstorming is part of the bread and butter of the problem-solving process and all problem-solving strategies benefit from getting ideas out and challenging a team to generate solutions quickly. 

With Mindspin, participants are encouraged not only to generate ideas but to do so under time constraints and by slamming down cards and passing them on. By doing multiple rounds, your team can begin with a free generation of possible solutions before moving on to developing those solutions and encouraging further ideation. 

This is one of our favorite problem-solving activities and can be great for keeping the energy up throughout the workshop. Remember the importance of helping people become engaged in the process – energizing problem-solving techniques like Mindspin can help ensure your team stays engaged and happy, even when the problems they’re coming together to solve are complex. 

MindSpin   #teampedia   #idea generation   #problem solving   #action   A fast and loud method to enhance brainstorming within a team. Since this activity has more than round ideas that are repetitive can be ruled out leaving more creative and innovative answers to the challenge.

22. Improved Solutions

After a team has successfully identified a problem and come up with a few solutions, it can be tempting to call the work of the problem-solving process complete. That said, the first solution is not necessarily the best, and by including a further review and reflection activity into your problem-solving model, you can ensure your group reaches the best possible result. 

One of a number of problem-solving games from Thiagi Group, Improved Solutions helps you go the extra mile and develop suggested solutions with close consideration and peer review. By supporting the discussion of several problems at once and by shifting team roles throughout, this problem-solving technique is a dynamic way of finding the best solution. 

Improved Solutions   #creativity   #thiagi   #problem solving   #action   #team   You can improve any solution by objectively reviewing its strengths and weaknesses and making suitable adjustments. In this creativity framegame, you improve the solutions to several problems. To maintain objective detachment, you deal with a different problem during each of six rounds and assume different roles (problem owner, consultant, basher, booster, enhancer, and evaluator) during each round. At the conclusion of the activity, each player ends up with two solutions to her problem.

23. Four Step Sketch

Creative thinking and visual ideation does not need to be confined to the opening stages of your problem-solving strategies. Exercises that include sketching and prototyping on paper can be effective at the solution finding and development stage of the process, and can be great for keeping a team engaged. 

By going from simple notes to a crazy 8s round that involves rapidly sketching 8 variations on their ideas before then producing a final solution sketch, the group is able to iterate quickly and visually. Problem-solving techniques like Four-Step Sketch are great if you have a group of different thinkers and want to change things up from a more textual or discussion-based approach.

Four-Step Sketch   #design sprint   #innovation   #idea generation   #remote-friendly   The four-step sketch is an exercise that helps people to create well-formed concepts through a structured process that includes: Review key information Start design work on paper,  Consider multiple variations , Create a detailed solution . This exercise is preceded by a set of other activities allowing the group to clarify the challenge they want to solve. See how the Four Step Sketch exercise fits into a Design Sprint

24. 15% Solutions

Some problems are simpler than others and with the right problem-solving activities, you can empower people to take immediate actions that can help create organizational change. 

Part of the liberating structures toolkit, 15% solutions is a problem-solving technique that focuses on finding and implementing solutions quickly. A process of iterating and making small changes quickly can help generate momentum and an appetite for solving complex problems.

Problem-solving strategies can live and die on whether people are onboard. Getting some quick wins is a great way of getting people behind the process.   

It can be extremely empowering for a team to realize that problem-solving techniques can be deployed quickly and easily and delineate between things they can positively impact and those things they cannot change. 

15% Solutions   #action   #liberating structures   #remote-friendly   You can reveal the actions, however small, that everyone can do immediately. At a minimum, these will create momentum, and that may make a BIG difference.  15% Solutions show that there is no reason to wait around, feel powerless, or fearful. They help people pick it up a level. They get individuals and the group to focus on what is within their discretion instead of what they cannot change.  With a very simple question, you can flip the conversation to what can be done and find solutions to big problems that are often distributed widely in places not known in advance. Shifting a few grains of sand may trigger a landslide and change the whole landscape.

25. How-Now-Wow Matrix

The problem-solving process is often creative, as complex problems usually require a change of thinking and creative response in order to find the best solutions. While it’s common for the first stages to encourage creative thinking, groups can often gravitate to familiar solutions when it comes to the end of the process. 

When selecting solutions, you don’t want to lose your creative energy! The How-Now-Wow Matrix from Gamestorming is a great problem-solving activity that enables a group to stay creative and think out of the box when it comes to selecting the right solution for a given problem.

Problem-solving techniques that encourage creative thinking and the ideation and selection of new solutions can be the most effective in organisational change. Give the How-Now-Wow Matrix a go, and not just for how pleasant it is to say out loud. 

How-Now-Wow Matrix   #gamestorming   #idea generation   #remote-friendly   When people want to develop new ideas, they most often think out of the box in the brainstorming or divergent phase. However, when it comes to convergence, people often end up picking ideas that are most familiar to them. This is called a ‘creative paradox’ or a ‘creadox’. The How-Now-Wow matrix is an idea selection tool that breaks the creadox by forcing people to weigh each idea on 2 parameters.

26. Impact and Effort Matrix

All problem-solving techniques hope to not only find solutions to a given problem or challenge but to find the best solution. When it comes to finding a solution, groups are invited to put on their decision-making hats and really think about how a proposed idea would work in practice. 

The Impact and Effort Matrix is one of the problem-solving techniques that fall into this camp, empowering participants to first generate ideas and then categorize them into a 2×2 matrix based on impact and effort.

Activities that invite critical thinking while remaining simple are invaluable. Use the Impact and Effort Matrix to move from ideation and towards evaluating potential solutions before then committing to them. 

Impact and Effort Matrix   #gamestorming   #decision making   #action   #remote-friendly   In this decision-making exercise, possible actions are mapped based on two factors: effort required to implement and potential impact. Categorizing ideas along these lines is a useful technique in decision making, as it obliges contributors to balance and evaluate suggested actions before committing to them.

27. Dotmocracy

If you’ve followed each of the problem-solving steps with your group successfully, you should move towards the end of your process with heaps of possible solutions developed with a specific problem in mind. But how do you help a group go from ideation to putting a solution into action? 

Dotmocracy – or Dot Voting -is a tried and tested method of helping a team in the problem-solving process make decisions and put actions in place with a degree of oversight and consensus. 

One of the problem-solving techniques that should be in every facilitator’s toolbox, Dot Voting is fast and effective and can help identify the most popular and best solutions and help bring a group to a decision effectively. 

Dotmocracy   #action   #decision making   #group prioritization   #hyperisland   #remote-friendly   Dotmocracy is a simple method for group prioritization or decision-making. It is not an activity on its own, but a method to use in processes where prioritization or decision-making is the aim. The method supports a group to quickly see which options are most popular or relevant. The options or ideas are written on post-its and stuck up on a wall for the whole group to see. Each person votes for the options they think are the strongest, and that information is used to inform a decision.

All facilitators know that warm-ups and icebreakers are useful for any workshop or group process. Problem-solving workshops are no different.

Use these problem-solving techniques to warm up a group and prepare them for the rest of the process. Activating your group by tapping into some of the top problem-solving skills can be one of the best ways to see great outcomes from your session.

• Check-in/Check-out
• Doodling Together
• Show and Tell
• Constellations
• Draw a Tree

28. Check-in / Check-out

Solid processes are planned from beginning to end, and the best facilitators know that setting the tone and establishing a safe, open environment can be integral to a successful problem-solving process.

Check-in / Check-out is a great way to begin and/or bookend a problem-solving workshop. Checking in to a session emphasizes that everyone will be seen, heard, and expected to contribute. 

If you are running a series of meetings, setting a consistent pattern of checking in and checking out can really help your team get into a groove. We recommend this opening-closing activity for small to medium-sized groups though it can work with large groups if they’re disciplined!

Check-in / Check-out   #team   #opening   #closing   #hyperisland   #remote-friendly   Either checking-in or checking-out is a simple way for a team to open or close a process, symbolically and in a collaborative way. Checking-in/out invites each member in a group to be present, seen and heard, and to express a reflection or a feeling. Checking-in emphasizes presence, focus and group commitment; checking-out emphasizes reflection and symbolic closure.

29. Doodling Together  

Thinking creatively and not being afraid to make suggestions are important problem-solving skills for any group or team, and warming up by encouraging these behaviors is a great way to start. 

Doodling Together is one of our favorite creative ice breaker games – it’s quick, effective, and fun and can make all following problem-solving steps easier by encouraging a group to collaborate visually. By passing cards and adding additional items as they go, the workshop group gets into a groove of co-creation and idea development that is crucial to finding solutions to problems. 

Doodling Together   #collaboration   #creativity   #teamwork   #fun   #team   #visual methods   #energiser   #icebreaker   #remote-friendly   Create wild, weird and often funny postcards together & establish a group’s creative confidence.

30. Show and Tell

You might remember some version of Show and Tell from being a kid in school and it’s a great problem-solving activity to kick off a session.

Asking participants to prepare a little something before a workshop by bringing an object for show and tell can help them warm up before the session has even begun! Games that include a physical object can also help encourage early engagement before moving onto more big-picture thinking.

By asking your participants to tell stories about why they chose to bring a particular item to the group, you can help teams see things from new perspectives and see both differences and similarities in the way they approach a topic. Great groundwork for approaching a problem-solving process as a team! 

Show and Tell   #gamestorming   #action   #opening   #meeting facilitation   Show and Tell taps into the power of metaphors to reveal players’ underlying assumptions and associations around a topic The aim of the game is to get a deeper understanding of stakeholders’ perspectives on anything—a new project, an organizational restructuring, a shift in the company’s vision or team dynamic.

31. Constellations

Who doesn’t love stars? Constellations is a great warm-up activity for any workshop as it gets people up off their feet, energized, and ready to engage in new ways with established topics. It’s also great for showing existing beliefs, biases, and patterns that can come into play as part of your session.

Using warm-up games that help build trust and connection while also allowing for non-verbal responses can be great for easing people into the problem-solving process and encouraging engagement from everyone in the group. Constellations is great in large spaces that allow for movement and is definitely a practical exercise to allow the group to see patterns that are otherwise invisible. 

Constellations   #trust   #connection   #opening   #coaching   #patterns   #system   Individuals express their response to a statement or idea by standing closer or further from a central object. Used with teams to reveal system, hidden patterns, perspectives.

32. Draw a Tree

Problem-solving games that help raise group awareness through a central, unifying metaphor can be effective ways to warm-up a group in any problem-solving model.

Draw a Tree is a simple warm-up activity you can use in any group and which can provide a quick jolt of energy. Start by asking your participants to draw a tree in just 45 seconds – they can choose whether it will be abstract or realistic. 

Once the timer is up, ask the group how many people included the roots of the tree and use this as a means to discuss how we can ignore important parts of any system simply because they are not visible.

All problem-solving strategies are made more effective by thinking of problems critically and by exposing things that may not normally come to light. Warm-up games like Draw a Tree are great in that they quickly demonstrate some key problem-solving skills in an accessible and effective way.

Draw a Tree   #thiagi   #opening   #perspectives   #remote-friendly   With this game you can raise awarness about being more mindful, and aware of the environment we live in.

Each step of the problem-solving workshop benefits from an intelligent deployment of activities, games, and techniques. Bringing your session to an effective close helps ensure that solutions are followed through on and that you also celebrate what has been achieved.

Here are some problem-solving activities you can use to effectively close a workshop or meeting and ensure the great work you’ve done can continue afterward.

• One Breath Feedback
• Who What When Matrix
• Response Cards

How do I conclude a problem-solving process?

All good things must come to an end. With the bulk of the work done, it can be tempting to conclude your workshop swiftly and without a moment to debrief and align. This can be problematic in that it doesn’t allow your team to fully process the results or reflect on the process.

At the end of an effective session, your team will have gone through a process that, while productive, can be exhausting. It’s important to give your group a moment to take a breath, ensure that they are clear on future actions, and provide short feedback before leaving the space. 

The primary purpose of any problem-solving method is to generate solutions and then implement them. Be sure to take the opportunity to ensure everyone is aligned and ready to effectively implement the solutions you produced in the workshop.

Remember that every process can be improved and by giving a short moment to collect feedback in the session, you can further refine your problem-solving methods and see further success in the future too.

33. One Breath Feedback

Maintaining attention and focus during the closing stages of a problem-solving workshop can be tricky and so being concise when giving feedback can be important. It’s easy to incur “death by feedback” should some team members go on for too long sharing their perspectives in a quick feedback round. 

One Breath Feedback is a great closing activity for workshops. You give everyone an opportunity to provide feedback on what they’ve done but only in the space of a single breath. This keeps feedback short and to the point and means that everyone is encouraged to provide the most important piece of feedback to them. 

One breath feedback   #closing   #feedback   #action   This is a feedback round in just one breath that excels in maintaining attention: each participants is able to speak during just one breath … for most people that’s around 20 to 25 seconds … unless of course you’ve been a deep sea diver in which case you’ll be able to do it for longer.

34. Who What When Matrix 

Matrices feature as part of many effective problem-solving strategies and with good reason. They are easily recognizable, simple to use, and generate results.

The Who What When Matrix is a great tool to use when closing your problem-solving session by attributing a who, what and when to the actions and solutions you have decided upon. The resulting matrix is a simple, easy-to-follow way of ensuring your team can move forward. 

Great solutions can’t be enacted without action and ownership. Your problem-solving process should include a stage for allocating tasks to individuals or teams and creating a realistic timeframe for those solutions to be implemented or checked out. Use this method to keep the solution implementation process clear and simple for all involved. 

Who/What/When Matrix   #gamestorming   #action   #project planning   With Who/What/When matrix, you can connect people with clear actions they have defined and have committed to.

35. Response cards

Group discussion can comprise the bulk of most problem-solving activities and by the end of the process, you might find that your team is talked out! 

Providing a means for your team to give feedback with short written notes can ensure everyone is head and can contribute without the need to stand up and talk. Depending on the needs of the group, giving an alternative can help ensure everyone can contribute to your problem-solving model in the way that makes the most sense for them.

Response Cards is a great way to close a workshop if you are looking for a gentle warm-down and want to get some swift discussion around some of the feedback that is raised. 

Response Cards   #debriefing   #closing   #structured sharing   #questions and answers   #thiagi   #action   It can be hard to involve everyone during a closing of a session. Some might stay in the background or get unheard because of louder participants. However, with the use of Response Cards, everyone will be involved in providing feedback or clarify questions at the end of a session.

Save time and effort discovering the right solutions

A structured problem solving process is a surefire way of solving tough problems, discovering creative solutions and driving organizational change. But how can you design for successful outcomes?

With SessionLab, it’s easy to design engaging workshops that deliver results. Drag, drop and reorder blocks  to build your agenda. When you make changes or update your agenda, your session  timing   adjusts automatically , saving you time on manual adjustments.

Collaborating with stakeholders or clients? Share your agenda with a single click and collaborate in real-time. No more sending documents back and forth over email.

Explore  how to use SessionLab  to design effective problem solving workshops or  watch this five minute video  to see the planner in action!

Over to you

The problem-solving process can often be as complicated and multifaceted as the problems they are set-up to solve. With the right problem-solving techniques and a mix of creative exercises designed to guide discussion and generate purposeful ideas, we hope we’ve given you the tools to find the best solutions as simply and easily as possible.

Is there a problem-solving technique that you are missing here? Do you have a favorite activity or method you use when facilitating? Let us know in the comments below, we’d love to hear from you! 

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

Your list of techniques for problem solving can be helpfully extended by adding TRIZ to the list of techniques. TRIZ has 40 problem solving techniques derived from methods inventros and patent holders used to get new patents. About 10-12 are general approaches. many organization sponsor classes in TRIZ that are used to solve business problems or general organiztational problems. You can take a look at TRIZ and dwonload a free internet booklet to see if you feel it shound be included per your selection process.

Leave a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Going from a mere idea to a workshop that delivers results for your clients can feel like a daunting task. In this piece, we will shine a light on all the work behind the scenes and help you learn how to plan a workshop from start to finish. On a good day, facilitation can feel like effortless magic, but that is mostly the result of backstage work, foresight, and a lot of careful planning. Read on to learn a step-by-step approach to breaking the process of planning a workshop into small, manageable chunks.  The flow starts with the first meeting with a client to define the purposes of a workshop.…

How does learning work? A clever 9-year-old once told me: “I know I am learning something new when I am surprised.” The science of adult learning tells us that, in order to learn new skills (which, unsurprisingly, is harder for adults to do than kids) grown-ups need to first get into a specific headspace.  In a business, this approach is often employed in a training session where employees learn new skills or work on professional development. But how do you ensure your training is effective? In this guide, we'll explore how to create an effective training session plan and run engaging training sessions. As team leader, project manager, or consultant,…

Effective online tools are a necessity for smooth and engaging virtual workshops and meetings. But how do you choose the right ones? Do you sometimes feel that the good old pen and paper or MS Office toolkit and email leaves you struggling to stay on top of managing and delivering your workshop? Fortunately, there are plenty of online tools to make your life easier when you need to facilitate a meeting and lead workshops. In this post, we’ll share our favorite online tools you can use to make your job as a facilitator easier. In fact, there are plenty of free online workshop tools and meeting facilitation software you can…

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Sign up for free

ITSM for high-velocity teams

What is problem management.

Problem management is the process of identifying and managing the causes of incidents on an IT service. It is a core component of ITSM frameworks.

The closer you get to real incident experts, the less you actually hear the question: “What caused the incident?”  Sure, you’ll hear it plenty from executives, and customers, and the press. But the experts know better. Because the answer to “what caused the incident” is often dry and non-helpful: a rewritten config file, a corrupted database entry.

But what were the contributing causes behind the thing that caused the incident? What were the factors that led up to the incident? How is it possible that a config file could be rewritten? What conditions create a corrupted database entry? These are the questions you hear experts ask. And they’re at the heart of problem management.

Problem management isn’t just about finding and fixing incidents, but identifying and understanding the underlying causes of an incident as well as identifying the best method to eliminate that root cause. Moreover, pinpointing the cause has no value to an organization if it’s a cut-off process completed by a siloed team, so problem management should be constant and widely practiced across multiple teams, including IT, security, and software developers. An incident may be over once the service is up and running again, but until the underlying causes and contributing factors are addressed, the problem remains.

The relationship between problem management and other key ITIL processes

Problem management works alongside incident management and other ITIL practices to form an overall ITSM strategy.

Problem management vs. incident management

ITIL defines a problem as a cause, or potential cause, of one or more incidents. The behaviors behind effective incident management and effective problem management are often similar and overlapping, but there are still key differences. For example, rolling back a recently deploy may get the service operating again and end the incident, but the underlying problem remains.

That said, we believe that problem management and incident management practices are becoming increasingly intertwined. During the times between incidents, IT teams can focus their efforts on problem investigations that lead to improvements and better service quality. This is how problem management becomes the most valuable to the organization.

Problem management and change management

Change management is the process of planning, tracking, and releasing changes without service disruption or downtime. 

When a change does cause disruption or downtime, that change is analyzed during incident and problem management processes.

Problem management and knowledge management

Knowledge management creates a repository of solutions and documentation for common procedures and even incident workarounds. When used together, a healthy knowledge management practice can enable faster incident resolution and fewer incidents altogether.

Problem management and service request management

Service request management is the practice of processing a request from a user for something to be provided, such as access to applications, software enhancements, and information. It can sometimes be difficult to distinguish a service request from an incident. In fact, the two were not distinguished and both lumped into the category “incidents” until the release of ITIL V3 in 2007. ITIL now defines an incident as ‘an unplanned interruption to an IT service or reduction in the quality of an IT service.’ It defines a service request as “a formal request from a user for something to be provided – for example, a request for information or advice; to reset a password; or to install a workstation for a new user.”

What are the benefits of problem management?

Done right, problem management unleashes many benefits for the business.

Decrease time to resolution

Teams that unlock the problems behind today’s incident will be better prepared to attack incidents in the future. By codifying best practices around problem analysis, teams will be able to more quickly respond and take action during the next service disruption.

Avoid costly incidents

Avoiding incidents will save time, money, and lots of pain. According to Gartner , many organizations report downtime costing more than $300,000 per hour. For some web-based services, that number can be dramatically higher. 

Increase productivity

Stop responding to incidents so frequently and return resources and time to teams who could be shipping new value to customers.

Empower your team to find and learn from underlying causes

When organizations effectively practice problem management, teams continually investigate, learn from incidents, and ship valuable updates. Unfortunately, many enterprises create a siloed problem management team that is too far removed from day-to-day operations to eliminate the most pressing problems.

Promote continuous service improvement 

Problem management prevents incidents and also delivers value. For instance, fixing an incident causing low level performance also ships valuable service quality improvements.

Increase customer satisfaction

Better problem management leads to fewer incidents, and happier customers. Alternatively, customer patience wears thin when they notice the same incident happening multiple times. Decreasing the occurrence of repeat incidents builds customer trust.

The problem management process

At Atlassian, we advocate bringing the problem and incident management processes closer together.

When problem management is a heavy, siloed, and separate process, companies can end up creating a dumping ground of problems. This backlog is where problem issues go to die in some teams. It’s best to get problems in front of the teams that can handle and do valuable investigations.

That all being said, it’s good to understand the main steps that contribute to a problem management process. Such as:

• Problem detection  - Proactively find problems so they can be fixed, or identify workarounds before future incidents happen.
• Categorization and prioritization - Track and assess known problems to keep teams organized and working on the most relevant and high-value problems.
• Investigation and diagnosis - Identify the underlying contributing causes of the problem and the best course of action for remediation.
• Create a known error record  - In ITIL, a known error is “a problem that has a documented root cause and a workaround.” Recording this information leads to less downtime if the problem triggers an incident. This is typically stored in a document called a known error database.
• Create a workaround, if necessary - A workaround is a temporary solution for reducing the impact of problems and keeping them from becoming incidents. These aren’t ideal, but they can limit business impact and avoid a customer-facing incident if the problem can’t be easily identified and eliminated.
• Resolve and close the problem - A closed problem is one that has been eliminated and can no longer cause another incident.

Problem management best practices and tips

Like we mentioned earlier, the most effective problem management teams we’ve seen blend problem management and incident management.

Setting problem management as a separate practice creates a challenge where the problem team becomes a bottleneck or focuses on the wrong things, like problems from external vendors that they have no control over. Root causes are often not investigated until long after the incident has happened. 

In many cases, your team may benefit from integrating incident management and problem management practices. This is a proactive approach that allows you to understand what led to the incident at the same time you work to resolve it. For example, resolving an incident in software requires identifying poor code (the cause), and then developing replacement code to avoid further incidents (the fix).

Weaving problem and incident together means when teams aren’t in response mode they can look to problems that are most impacting service and performance quality and get ahead, to prevent future incidents. 

Problem management tips

Avoid relying on reactive, root-cause analysis.

There is rarely just one root cause behind an incident or problem. The best teams holistically consider all potential contributing factors and practice blameless analysis .

Encourage an open environment where problems are shared

Problem and incident analysis should be an open conversation where team members are encouraged to share the facts without fear of punishment or retribution.

Focus on critical services

Prioritize addressing the problems affecting the services that deliver the most value to the organization.

Ask questions and use the ‘5 whys’

Many teams find success using the “5 Whys” technique Taiichi Ohno, the architect of the Toyota Production System. Check out the Atlassian Team Playbook play to learn more.

Spread the knowledge

Open teams share knowledge and insights that their colleagues and adjacent teams can learn from.

Become a learning organization

Effective problem management isn’t something with an end date. Even the best-performing organizations have incidents. The truly world class teams are the ones who constantly iterate on their process, improve it, and lessen the impact of problems on their colleagues and customers.

Track follow-up

It’s important to develop a clear and standardized way to stay on top of follow-up actions. Since you should always be practicing problem management, it’s important to use ITSM software that will enable your team to prioritize tasks, track progress, and help associate incident issues with problems.

Incidents are often described as an unplanned investment in the future reliability of your service. An effective problem management delivers valuable service improvements, while identifying and eliminating the driving forces behind incidents.  

Want to learn about problem management in Jira Service Management?

Atlassian's guide to agile ways of working with ITIL 4

ITIL 4 is here—and it’s more agile than ever. Learn tips to bring agility and collaboration into ITSM with Atlassian.

What is IT change management? Definition, benefits and types

IT Change Management minimizes risk while making changes to systems and services. Learn about the change management process, its importance, best practices

Published: 10 April 2024 Contributor: Camilo Quiroz-Vázquez

Problem management is the process of identifying, managing and finding solutions for the root causes of incidents on an IT service. Problem management is a critical aspect of IT service management (ITSM).

The problem management process is both proactive and reactive and improves an IT team’s ability to find the root cause of issues while offering continuous service delivery to users. Crucially, problem management goes beyond identifying issues and delivering a quick fix; successful problem management operates on a comprehensive understanding of all underlying factors that contribute to incidents and solutions that address the root cause.

IT operations  (ITOps) involves managing a complex system of interdependent applications, software, hardware, IT infrastructure and other technologies. Ideally, incidents and problems would not occur in the first place, but when they do, it is necessary to solve issues and identify known errors before they cascade into larger ones. Service disruptions prevent organizations from providing continual service improvements and can cause serious reputational and financial issues.

Proactive problem management helps enterprises stop problems before they occur and reduce downtime.  IT automation solutions help manage the impact of incidents by automating incident detection and the workflows that lead to resolution. IT issues can include long load times, inefficient or broken code, or database queries that fetch unnecessary data. Proactively addressing problems leads to reduced costs and improved customer satisfaction.

Effective problem management requires observability into IT systems and rigorous categorization of problems and incidents. By classifying instances that might lead to major incidents, organizations can address issues likely to have the largest business impact. Problem management strategies address incidents across an organization’s tech stack and compel organizations to explore better ways to address incidents across operations.

Learn how both APM and ARM can enable faster decisions and resource application.

Register for the guide to operationalize FinOps

Problem management requires a well-thought-out approach to ensure that teams are allocating resources as efficiently as possible. Problem management teams and other stakeholders use several levers to address problems effectively and efficiently. These levers help teams identify the root cause of the problem and create solutions that can stop the problem from recurring.

Most problem management approaches follow a similar pattern of assessment, logging, analysis and solution.

IT professionals identify recurring incidents that are classified as problems, often by using automation . Automated systems help find anomalies by sifting through large data sets and identifying data points that might be out of the ordinary.

Anomalous data can lead IT team members to the potential causes of incidents. Incident reports and automated notifications are sent to the service desk, which can identify whether the incident is new or if a team has identified and resolved it in the past.

Teams or automated systems identify and categorize incidents as problem records or as unrelated issues likely to occur again. This categorization helps an organization determine whether it can solve a problem immediately or if the problem requires deeper analysis.

Problem management teams log problems, often by using self-service platforms, and create problem records. Problem records consist of comprehensive accounting for the problem, including any related incidents, where and how the problem occurred, the root cause analysis and the solution. This logging system creates a known error record and enters it into the known error database (KEDB). Enterprises should connect their problem-management and knowledge management approaches. Knowledge management creates a library of solutions for known problems.

Organizations study the underlying issues behind identified problems and develop roadmaps leading to long-term solutions. Understanding the root cause allows organizations to prevent the problem from repeating, reducing the long-term impact.

When an IT team understands the problem and its root cause, it can address the problem (also known as problem control) and find a resolution. This can involve a quick or protracted response depending on the severity or complexity of the problem. Quick resolutions are made by finding workarounds that shorten downtimes while IT teams find the root cause.

Problem management can also use templates, such as ones focused on escalation information and problem reviews, to minimize human resources previously dedicated to key problem management tasks.

Error control is another facet of problem control. Error control focuses on finding resolutions to known errors with the goal of removing them from the known error database (KEDB).

The goal of problem management is to minimize downtime, increase efficiency and improve service delivery. Some of the more impactful benefits of problem management include:

Identifying the underlying cause of incidents is an important part of  cyberrisk management . Organizations that merely patch or resolve individual incidents without exploring their root cause might be overlooking significant security issues. Problem management teams can work in coordination with security professionals to understand which incidents and problems result from malicious actors or security flaws, both of which can create major problems for an organization.

Customer retention relies on the consistent delivery of quality services. Sustained downtime and the inability to access applications or websites can drive customers elsewhere. By prioritizing problem identification and problem resolution, organizations can minimize downtime and increase customer satisfaction.

Organizations that prioritize knowledge management, the process of identifying, organizing, storing and disseminating information in a knowledge base, as part of their problem management approach have a better chance of avoiding repeat incidents. By capturing this information in a problem record, organizations can create known error databases so they can avoid future incidents and create permanent solutions.

Implementing problem management strategies helps maintain the efficiency of IT departments and improve employee experience . Problem management prevents employees from having to repeatedly fix and maintain the same issues, allowing them to boost productivity on higher value work.

Problem management and incident management are closely related processes. IT departments perform both functions with the goal of providing continuous service and eradicating issues. The main difference between these two functions lies in the technical definitions of “incident” and “problem.”

•   An incident is a singular event that causes a disruption and hinders a system’s ability to deliver a specific service. 
• Problems are the root cause of that incident. A problem can consist of a single incident or multiple concurring incidents.

The incident management process has its roots in the IT service desk , which provides a single point of contact between IT operations and users, and handles the entire lifecycle of IT service delivery. Incident resolution happens reactively and involves quickly resolving incidents before they disrupt service. Problem management is concerned with finding the underlying cause of each incident and offering a permanent solution to the cause of the problem. IT teams set standards for problem analysis, allowing them to trace the root cause of incidents. The most effective problem management strategies are proactive and can identify the potential cause of a problem before it occurs. 

Efficient problem management strategies involve an emphasis on knowledge management. Knowledge management strategies use organizational experience to resolve issues more quickly or avoid them entirely. Robust documentation of solutions, protocols and common workarounds is a key aspect of knowledge management. IT departments store documentation in a centralized location and ensure that documentation is easily accessible across teams. Knowledge management repositories help IT teams focus on more complex work and the optimization of existing services. They are also an important tool for proactive problem management.

A problem management team can either engage in reactive or proactive problem management, depending on what incidents they observe and what historical data they have. Reactive problem management is concerned with identifying the problem when it occurs and solving it as quickly as possible. The problem must first occur before organizations can apply reactive problem management.

Proactive problem management involves more investigative work on why a problem is occurring and creating a solution to prevent it from happening again. The more proactive an enterprise can be, the more likely it is to avoid large issues, security threats and service interruptions.

The Information Technology Infrastructure Library (ITIL) is a repository of best practices for optimizing IT operations and improving service level functions. The ITIL is an integral part of the configuration management database (CMDB), which is the centralized authority for every component needed to provide and manage IT services. IT teams use the ITIL when implementing IT service management (ITSM).

ITSM is how an organization ensures its IT services work in the way that its users and business need them to work. ITSM strategy aims to enable and maintain optimal deployment, operation and management of IT resources. Problem management is a core component of ITSM. ITIL is the most widely adopted guidance framework for implementing and documenting ITSM.

ITIL problem management uses ITIL processes to minimize the foundational work that addressing any one problem requires. Many problems that organizations face, such as server outages and cybersecurity issues, have happened before to other organizations. Often, standardized responses exist. Therefore, ITSM approaches often incorporate ITIL to minimize the new work needed to solve IT problems. ITSM also encompasses the process of change management.

Change management is the process of managing and implementing organizational change. Change management can occur throughout migrations, digital transformations or organizational mergers. DevOps teams use ITIL to guide them through these changes and measure KPIs and metrics related to the successful implementation of changes to IT systems. Ideally the change management process should be seamless. When it isn’t, problem management strategies can help smooth the transition.

Discover how to achieve proactive IT operations with IBM® Cloud Pak® for AIOps.

Get the context you need to resolve incidents faster with IBM’s observability solution.

Optimize AWS, Azure, Google Cloud, Kubernetes, data centers and more with intelligent automation.

Flexera One with IBM Observability is a comprehensive IT asset management solution to help you maximize your IT investments and mitigate risk.

Learn how artificial intelligence for IT operations (AIOps) uses data and machine learning to improve and automate IT service management.

Predict and prevent performance issues before they impact your business with application performance management.

Incidents are errors or complications in IT service. Those that point to underlying or more complicated issues that require more comprehensive addressing are called problems.

IT operations and AIOps oversee and automate the management, delivery and support of IT services throughout an organization.

ITSM is how an organization ensures its IT services work the way users and the business need them to work.

Automate IT operations tasks, accelerate software delivery, and minimize IT risk with site reliability engineering.

IBM Instana provides real-time observability that everyone and anyone can use. It delivers quick time-to-value while verifying that your observability strategy can keep up with the dynamic complexity of current and future environments. From mobile to mainframe, Instana supports over 250 technologies and growing. 

What can we help you with?

Problem solving

Regular task for project managers.

Problem solving is a basic task for the project management . It is a process for developing and applying a solution for the occurred problems. The probability of the success rises, if a particular method is implemented to the project work. The problem solving can be described in the following steps. First of all it is necessary to determine the actual status or problem definition. The next step is the applying of the solution process. And the last step is the achievement of the wanted actual status.

First, a clear picture of the situation to be changed is necessary. It should be thereby clearly defined, which objective should be achieved. And the question is: “Why this project is to be performed; which objective it serves?” The initial situation, objects, purpose and scenario of the project are to be analyzed to answer this question and to define therefore the project. The initial situation illustrates the project situation. The project purpose places the project in the subordinated context. The object description enables project measurability and transparency of the target tracking. The scenario or project structure plan divides the whole project into work packages to effectively accomplish project objects.

  More Like This

• Project management
• Project manager
• Project management system

Would you like to receive regular info on project management topics?

Key has already been sent, account limit exceeded, project management newsletter, read more about project management on our blog, our project management software inloox helps you to make a success of your project the fast, easy and secure way, other terms.

Instagantt Standalone

Full version of Instagantt. Don't know what Asana is, or don't want to use it with Asana?

Instagantt for Asana

If you need to manage your Asana projects in Instagantt, this is your product.

A Complete Guide to know What is Problem Solving (Updated May 2024)

Everything happening in this world has its problems. This is because no system in this world has 100% efficiency. But this is not a big issue for the people who are prepared to deal with any kind of problem. The field that is heavily affected by the problems in the field of companies and organizations.

This is because a lot of employees are working in different departments under the same name. The problem for one employee or one department can cause issues for others. This is why the employees are given special problem-solving training. Here we will discuss what is problem-solving and some effective steps involved.

What is problem solving?

Problem-solving isa process of solving any kind of problem. This process is acted upon in some steps. These steps start from identifying the problem and determining the cause of the problem. After the problem and its cause are identified, the next step is to select alternatives for the solution and implement the solutions.

All of these steps are collectively known as a problem-solving process.

The basic steps involved in problem-solving.

As the problem-solving process comprises different steps that collectively help in getting id of the problem. So, here we will have a detailed discussion about the steps that are involved in problem-solving.

Defining the problem.

Defining the problem means that you are diagnosing the situation. This helps take the further steps for solving the problem. This is not just as simple as defining the problem. Here you take effective measures to keep track of the situation of the problem. Some of the most effective and easy to implement ways of defining the problem are listed below.

·       Flowcharts of the process and the problem init.

·       Cause and effect diagram.

With the help of these steps, you can easily identify the root causes of the problem. However, for these ways of defining the problem, you must involve the factual information and then compare the expectations to reality. Apart from this, you also need to stay focused on the root cause of the problem as eradicating this will be your main objective here.

To create a successful deduction for problem-solving in this step, you will first need to review different sectors of your system. Then you will have to evaluate things on the base of how something will affect the system.

Generating the alternatives.

Once you have gone through the first step, the next step will be to get the solution for the problem. It is in our psyche that once we think of an idea or solution, then we keep on thinking that it will be effective. But in reality, this will not happen every time and you will waste a lot of time coming up with another effective solution.

So, here the best thing to do is to come up with more than more solutions at a time. For this, you can do the following things.

·       Take ideas from different employees.

·       Mold your original idea according to different aspects of the problem.

·       Think of other than one effective idea.

When you are going with a set of ideas for the backup, you will be very efficient in solving the problem. This is because if one idea fails, you can implement another one and this can be carried on until you have solved the problem.

Evaluating and selecting alternatives.

So, now you know that you have to come up with more than one idea, but how will you know if the ideas are effective or not. For this, you can easily evaluate the ideas that come up in your mind. This will help in filtering out only the best and the most effective ideas. Here is how this works.

·       Will this solution be able to solve the specific problem without causing other problems in the system?

·       Will all the people and stakeholders of the system accept the solution?

·       Is the solution that I have come up with possible and easy to implement?

·       Will the solution and the alternatives be in the constraints of the organization?

When you think of all the ideas and their alternatives, you will be very efficiently filtering out the ideas that do not seem to be working.

Implementing the solutions.

Now you are in the state where you have the ideas, the solutions, and the alternatives of these solutions. The only step left to get the problem solved is to implement the solution. This is also not a very simple step. Here are some things that you must include in this step to increase the efficiency of your solution.

·      Involving others.

One of the best things to do is to involve others in the implementation of your solution. This will not only reduce the stress that you will have to bear. But this will also add other innovative ideas that come in their minds. This can be very helpful in making the solution to the problem better.

·      Testing and expectations of the solution.

When you are implementing or you have implemented the solution, it is very important to keep constantly monitoring the solution and its working. For this, you can test the solutions’ working at different events. Testing the outcomes and comparing when with the expectations will also give you the idea of how well the solution is performing.

·      Feedback system.

When you have implemented the solution, the role that you will play in the future will be lower than the role of other employees. So, you must take feedback after sometime. The feedback system will tell you about the feelings of people about your solution and its working. This will also help in improving the solution.

Some important things to consider in each of the problem-solving steps.

Above in the article, we discussed the significance of each step involved in problem-solving. Here we will discuss some additional things that you must be aware of. This is because they will not only make your problem-solving experience better, but they will also make your problem-solving techniques more efficient.

Knowing your problem in a good way:

If you are thinking about what is problem solving and how important it is to define the problem. Then we will tell you here the importance of defining the problem and some of the best ways to implement it. It is a must for solving any problem that you must know the real cause and the root of the problem.

This is because the smaller problems can be identified and solved easily. But when we are dealing with the problems on the level of different organizations, then it is very important to get rid of the problem from the start. This is because if the problem is not fully identified, then it will never be truly eradicated.

And this will keep on damaging the company in several ways. For the problem identifying methods we mentioned above, the initiative for any of the methods can be taken for different tools. Some of the tools are the 5 W’s, the root cause analysis, and appreciation. This is also very important that you consider each of them carefully from different perspectives.

This is because the cause of the problem could be an unreasonable workload or lack of training but if unidentified, this can be extremely bad.

Knowing about the complexity of the problem.

While you are solving any problem, you must understand that every problem will not have the same scope and the time required for every problem will be different. This is because the complexity of each problem is different. There are a lot of tools and methods to know about the complexity of the problem. Some of them are listed below.

·       Affinity diagrams.

·       Swim Lane diagram.

·       System diagram.

·       Flow charts.

·       Bottleneck method.

After identifying different factors of the problem, you can implement any of these tools and this will tell you about the complexity of the problem. Sometimes a problem that seems to be a single problem is a collection of different smaller problems.

This is the point where the drill-down technique can be very helpful. It will easily and efficiently breakdown the problem into smaller parts.

Process of solving the problem.

So, there can be a case that the problem is very small, and it can easily be dealt with. But inmost of the cases, the problem is not that simple, and it is a collection of several complex problems related to different departments.

In this case, the head of the problem-solving team must take different members from different departments that will help in solving that problem using the tools, tricks methods, and tips we mentioned above.

With the increasing complexities in different organizations, many people are asking what is problem solving. If you are also uncertain about what is problem solving, then this will be the article that will tell you all about what is problem solving.

This is because it will not only tell you about some of the most effective techniques for solving different problems, but the tips, tools, and methods we mentioned here can also be very helpful for everyone in dealing with complex problems.

We offer monthly and yearly subscriptions. Sign up for free, no credit card required.

Based on 10.000+ reviews on

Make a Gantt Chart Online Now

Start managing your projects efficiently & never struggle with complex tools again.

Ready to simplify your project management?