Exploring the Elements: Analysis & Problem Solving

Analysis & problem solving are necessary to navigate everyday life, especially in a world of echo-chambers and #fakenews . through analysis, we seek to fully understand issues and uncover potential solutions. so keep reading for insights into how these skills can be developed…, what is analysis & problem solving and why is it important .

Analysis and Problem Solving is the ability to critically evaluate data and use judgement to work through issues. It involves spotting connections between data. And essentially, involves seeing and actioning solutions effectively.

Firstly, Analysis is about being objective. And looking for evidence to support the conclusions we reach. Ultimately to improve judgement. And good analysis helps us to keep in check important cognitive shortcuts that can often impair our judgements– our biases.

We all have biases. When left unmanaged, biases are very problematic. One common bias, the Halo Effect , leads us to amplify the positive aspects of people. For example, thinking because a person is attractive, they’ll automatically be a good person. By building an analytical mindset, we can manage our biases, make better decisions and effectively solve problems.

The goal is to problem-solve on the basis of objective evidence, not sentiment. Emotions and biases cloud our judgement. So it’s essential to probe the evidence, determine what’s fact from fiction. Good analysis helps us to do this.

When starting out

management analysis and problem solving

At the outset of your career, you’re likely to be given tasks or problems to solve. A good determinant of how successful you’ll be in problem solving or delivering tasks is your ability to conduct strong analysis.

Naturally, over time, the problems you’ll deal with will become increasingly complex. So, it’s good to get in the habit of conducting thorough, evidence-based analysis early on.

First, focus on identifying relevant information. Is there data, facts, evidence available to help you analyse? Be careful too, it’s easy to waste time with interesting yet ultimately irrelevant data.

During this time, you’ll be getting to grips with the role, workplace and your colleagues. So you’ll have all sorts of information to handle. This makes it even more important to focus on what really matters to the task at hand.

Ask questions for a better understanding of what you’re trying to solve. Seek others’ views and opinions. This is important for ensuring others trust and engage with you. But your priority should be on building a picture of problems, built of evidence and data.

Test assumptions to decipher and challenge the myths. In a world of fake news, critical thinking is integral to analysis and problem solving. Sometimes can be as simple as reviewing problems again after a break. Ask yourself:  what am I assuming here? What is really going? W hat might I have missed before?

Exercise lateral thinking. Think outside the box and to look at problems from different perspectives. For example, if you’re a product designer it’s effective to interact with product from the perspective of users, suppliers and distributors.

Beware of  overconfidence . Both your own and that of others. Don’t just expect your managers or seniors to be correct, examine the source of data. Also, get a handle on the different types of biases that hinder  analysis . Think about which biases you might be prone to.

Essentially, it’s about having your research hat on. So stay alert and conduct qualitative and quantitative analysis as appropriate. Try testing yourself to build your capacity for spotting trends and patterns in complex problems. Logical or abstract reasoning tests can be a great one to start with.

Analysis and Problem Solving on your way up

management analysis and problem solving

So as you gain more experience in dealing with analysis, you’ll become better at problem-solving. Often the more senior your role is means the more responsibility you have, thus more potential problems.

With experience, you’ll start to more routinely tune-in to the workplace. Y ou’ll be aware of issues brewing beneath the surface, like office politics. And you will analyse and navigate underlying issues like this when problem-solving.

By its very nature, you’re dealing with more data, more information, more stakeholders and more pressure. So your ability to analyse despite additional distractions is truly put to the test. However, you may now have the opportunity to delegate tasks.

And if the option of help is there – grab it with both hands! The variety of information you’re dealing with grows with increasing responsibility. It’s easy to think you can continue to effectively analyse as you once did with a more focused workload, but don’t be fooled. We all have limits. We have to prioritise our attention. Pick what and when we analyse.

As you take more of a lead on problems, help others to think critically. Point out the evidence, data or facts underpinning your judgements. And ask them to critically evaluate them too.

More and more, leaders will want to see depth in your analysis and evidence that your ideas are future-proofed. They’ll ask to see the business case for any recommendations you make. So prioritise building strong rationale in business cases and focus on testing assumptions and iterating your solutions. Build prototypes or minimal viable products (MVPs) to truly stress test your ideas or judgements.

Develop a process for problem solving. Try to implement systems to seek, analyse, formulate solutions and evaluate outcomes. Building loops like this can help create habits and make analysis more seamless.

You could use tools to appraise data quickly. Or you can work with specialists in evaluating big data. In the future we’ll be using more tools to analyse complex and diverse data. So get ahead of the curb, by building you capacity for interpreting data now.

Leading in Analysis and Problem Solving

Photo by rawpixel on Unsplash

No matter what career stage you’re at, there will be problems to solve. This is especially the case when you’re in a position of leadership. A good leader is both demonstrator and facilitator of strong analysis and problem-solving skills.

At this stage you’ll likely be responsible for the management of a team and the big picture of the organisation.  Ultimately, you’ll need to lead by example and set the tone for your team when problem-solving.

Leaders are expected to be decisive. And good decisions are made by harnessing the power of an analytical mindset to collect and decipher data and information. No knee-jerk reactions, but thoughtful and strategic responses. Here are some pointers on how you can do this:

Use patterns and trends to uncover longer term opportunities and draw potential conclusions. This could relate to commercial thinking when looking for financially beneficial opportunities.

Recognise and respond strategically to the pressures faced by your people. Engage with your team and look at how you can improve processes, wellbeing and overall productivity.

Consistently build and review your awareness of new technologies shaping the way things might be done in the future. Stay in the know and beware of the fads. It’s about choosing what is best to pursue.

Increase your awareness and use of Systems Thinking . Identify the links between different tasks and functions. Then evaluate on the basis of seeing things in a system, rather than treating issues in isolation.

Say what you think. Share your thought-process openly. Be a thought-leader, create an open space for sharing thoughts and your team will contribute. This ultimately increases potential collaboration, empowers the team and teases out team-working issues.

From analysing the situation to solving it

management analysis and problem solving

Whatever walk of life or occupation, your chances of success will improve along with your capacity for analysis and problem solving. Whether you’re just starting out or you’ve been around for a while, these skills are needed at every stage.

And analysis is important in our interpersonal interactions, as it is for regular tasks. There are always instances where you might need to read between the lines of what someone is saying. And to identify what’s really going on, beneath the conversation’s surface.

Additionally, the more hands-on experience we have with problems, the better we’ll be at finding solutions. So maybe we should schedule some time for ‘brain-training’ exercises like Sudoku? Although there isn’t any conclusive evidence to suggest games like Sudoku substantially improve our problem-solving abilities, the regular exposure to problems tests us and builds confidence.

So if you’re looking to build up your analysis and problem solving skills, set up a  spotlight  on the  WiseAmigo app . Doing this will help you stay on track with your development, and get inspired along the way.

And once you’ve nailed Analysis and Problem Solving, you’ll be in a better place to think strategically, commercially and manage conflict better too.

“Analysis is the art of creation through destruction.”  

― p.s. baber, cassie draws the universe..

Normal 0 false false false EN-US JA X-NONE

Development is a journey and the  WiseAmigo  app is here to help you along the way. Join the WiseAmigo community,  create a Spotlight , discover more insightful content and reflect on your assertiveness journey today.

management analysis and problem solving

Privacy Preference Center

Privacy preferences.

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

Problem management: 8 steps to better problem solving

Alicia Raeburn contributor headshot

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. 

[product ui] Incident log example (lists)

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

management analysis and problem solving

Business impact analysis: 4 steps to prepare for anything

management analysis and problem solving

The beginner’s guide to business process management (BPM)

management analysis and problem solving

Project portfolio management 101

management analysis and problem solving

Marketing campaign management: 7 steps for success

Simplilearn

  • 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

What Is Problem Solving

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

Agile vs Waterfall Project Management

Agile vs. Waterfall Project Management: A Comparative Guide

Want to compare agile vs. waterfall project management? Read our guide for insights into both methodologies’ characteristics, benefits, and challenges.

Project Management Process

A Project Management Process Primer

What are the five phases of a project management process? Our guide discusses each phase with examples and offers tips for aspiring project managers.

Risk Management Process

Why Study Project Management? Top 5 Reasons

There are many excellent reasons for professionals in any industry to study project management. This article outlines why, so read on.

What is Project Design in Project Management

What is Project Design in Project Management?

Explore the fundamentals of project design in project management. Learn how this critical phase sets the stage for project success.

What is Risk Management

What is Risk Management? A Definitive Guide

If you’re asking, “What is risk management?” you’re in the right place! Explore our guide to understand its role, strategies, and how it shapes successful projects.

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

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.

Want better strategies? Become a bulletproof problem solver

Strategy to beat the odds

firo13_frth

Five routes to more innovative problem solving

35 problem-solving techniques and methods for solving complex problems

Problem solving workshop

Design your next session with SessionLab

Join the 150,000+ facilitators 
using SessionLab.

Recommended Articles

How to become a great workshop facilitator, workshop design 101: how to craft a successful agenda design.

  • 47 useful online tools for workshop planning and meeting facilitation
  • A step-by-step guide to planning a workshop

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!

management analysis and problem solving

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!

management analysis and problem solving

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! 

' src=

thank you very much for these excellent techniques

' src=

Certainly wonderful article, very detailed. Shared!

Leave a Comment Cancel reply

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

management analysis and problem solving

Facilitation skills can be applied in a variety of contexts, such as meetings, events, or in the classroom. Arguably, the setting in which facilitation skills shine the most is the design and running of workshops.  Workshops are dedicated spaces for interaction and learning. They are generally very hands-on, including activities such as simulations or games designed to practice specific skills. Leading workshops is an exciting, rewarding experience! In this piece we will go through some of the essential elements of workshop facilitation: What are workshops? Workshops are a time set aside for a group of people to learn new skills, come up with the best ideas, and solve problems together.…

A notebook and a computer

So, you’ve decided to convene a workshop, a special time set aside to work with a team on a certain topic or project. You are looking for brilliant ideas, new solutions and, of course, great participation. To begin the process that will get you to workshop success, you’ll need three ingredients: participants willing to join, someone to facilitate and guide them through the process (aka, you) and a detailed agenda or schedule of the activities you’ve planned. In this article we will focus on that last point: what makes a good agenda design? Having a good agenda is essential to ensure your workshops are well prepared and you can lead…

management analysis and problem solving

What are facilitation skills and how to improve them?

Facilitation skills are the abilities you need in order to master working with a group. In essence, facilitation is about being aware of what happens when people get together to achieve a common goal, and directing their focus and attention in ways that serve the group itself.  When we work together at our best, we can achieve a lot more than anything we might attempt alone. Working with others is not always easy: teamwork is fraught with risks and pitfalls, but skilled facilitation can help navigate them with confidence. With the right approach, facilitation can be a workplace superpower.  Whatever your position, career path, or life story, you probably have…

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Sign up for free

Cart

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

How to Solve Problems

  • Laura Amico

management analysis and problem solving

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

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

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

Partner Center

  • Business Essentials
  • Leadership & Management
  • Credential of Leadership, Impact, and Management in Business (CLIMB)
  • Entrepreneurship & Innovation
  • *New* Digital Transformation
  • Finance & Accounting
  • Business in Society
  • For Organizations
  • Support Portal
  • Media Coverage
  • Founding Donors
  • Leadership Team

management analysis and problem solving

  • Harvard Business School →
  • HBS Online →
  • Business Insights →

Business Insights

Harvard Business School Online's Business Insights Blog provides the career insights you need to achieve your goals and gain confidence in your business skills.

  • Career Development
  • Communication
  • Decision-Making
  • Earning Your MBA
  • Negotiation
  • News & Events
  • Productivity
  • Staff Spotlight
  • Student Profiles
  • Work-Life Balance
  • Alternative Investments
  • Business Analytics
  • Business Strategy
  • Business and Climate Change
  • Design Thinking and Innovation
  • Digital Marketing Strategy
  • Disruptive Strategy
  • Economics for Managers
  • Entrepreneurship Essentials
  • Financial Accounting
  • Global Business
  • Launching Tech Ventures
  • Leadership Principles
  • Leadership, Ethics, and Corporate Accountability
  • Leading with Finance
  • Management Essentials
  • Negotiation Mastery
  • Organizational Leadership
  • Power and Influence for Positive Impact
  • Strategy Execution
  • Sustainable Business Strategy
  • Sustainable Investing
  • Winning with Digital Platforms

Why Problem-Solving Skills Are Essential for Leaders in Any Industry

Business man leading team in problem-solving exercise with white board

  • 17 Jan 2023

Any organization offering a product or service is in the business of solving problems.

Whether providing medical care to address health issues or quick convenience to those hungry for dinner, a business’s purpose is to satisfy customer needs .

In addition to solving customers’ problems, you’ll undoubtedly encounter challenges within your organization as it evolves to meet customer needs. You’re likely to experience growing pains in the form of missed targets, unattained goals, and team disagreements.

Yet, the ubiquity of problems doesn’t have to be discouraging; with the right frameworks and tools, you can build the skills to solve consumers' and your organization’s most challenging issues.

Here’s a primer on problem-solving in business, why it’s important, the skills you need, and how to build them.

Access your free e-book today.

What Is Problem-Solving in Business?

Problem-solving is the process of systematically removing barriers that prevent you or others from reaching goals.

Your business removes obstacles in customers’ lives through its products or services, just as you can remove obstacles that keep your team from achieving business goals.

Design Thinking

Design thinking , as described by Harvard Business School Dean Srikant Datar in the online course Design Thinking and Innovation , is a human-centered , solutions-based approach to problem-solving and innovation. Originally created for product design, design thinking’s use case has evolved . It’s now used to solve internal business problems, too.

The design thinking process has four stages :

4 Stages of Design Thinking

  • Clarify: Clarify a problem through research and feedback from those impacted.
  • Ideate: Armed with new insights, generate as many solutions as possible.
  • Develop: Combine and cull your ideas into a short list of viable, feasible, and desirable options before building prototypes (if making physical products) and creating a plan of action (if solving an intangible problem).
  • Implement: Execute the strongest idea, ensuring clear communication with all stakeholders about its potential value and deliberate reasoning.

Using this framework, you can generate innovative ideas that wouldn’t have surfaced otherwise.

Creative Problem-Solving

Another, less structured approach to challenges is creative problem-solving , which employs a series of exercises to explore open-ended solutions and develop new perspectives. This is especially useful when a problem’s root cause has yet to be defined.

You can use creative problem-solving tools in design thinking’s “ideate” stage, which include:

  • Brainstorming: Instruct everyone to develop as many ideas as possible in an allotted time frame without passing judgment.
  • Divergent thinking exercises: Rather than arriving at the same conclusion (convergent thinking), instruct everyone to come up with a unique idea for a given prompt (divergent thinking). This type of exercise helps avoid the tendency to agree with others’ ideas without considering alternatives.
  • Alternate worlds: Ask your team to consider how various personas would manage the problem. For instance, how would a pilot approach it? What about a young child? What about a seasoned engineer?

It can be tempting to fall back on how problems have been solved before, especially if they worked well. However, if you’re striving for innovation, relying on existing systems can stunt your company’s growth.

Related: How to Be a More Creative Problem-Solver at Work: 8 Tips

Why Is Problem-Solving Important for Leaders?

While obstacles’ specifics vary between industries, strong problem-solving skills are crucial for leaders in any field.

Whether building a new product or dealing with internal issues, you’re bound to come up against challenges. Having frameworks and tools at your disposal when they arise can turn issues into opportunities.

As a leader, it’s rarely your responsibility to solve a problem single-handedly, so it’s crucial to know how to empower employees to work together to find the best solution.

Your job is to guide them through each step of the framework and set the parameters and prompts within which they can be creative. Then, you can develop a list of ideas together, test the best ones, and implement the chosen solution.

Related: 5 Design Thinking Skills for Business Professionals

4 Problem-Solving Skills All Leaders Need

1. problem framing.

One key skill for any leader is framing problems in a way that makes sense for their organization. Problem framing is defined in Design Thinking and Innovation as determining the scope, context, and perspective of the problem you’re trying to solve.

“Before you begin to generate solutions for your problem, you must always think hard about how you’re going to frame that problem,” Datar says in the course.

For instance, imagine you work for a company that sells children’s sneakers, and sales have plummeted. When framing the problem, consider:

  • What is the children’s sneaker market like right now?
  • Should we improve the quality of our sneakers?
  • Should we assess all children’s footwear?
  • Is this a marketing issue for children’s sneakers specifically?
  • Is this a bigger issue that impacts how we should market or produce all footwear?

While there’s no one right way to frame a problem, how you do can impact the solutions you generate. It’s imperative to accurately frame problems to align with organizational priorities and ensure your team generates useful ideas for your firm.

To solve a problem, you need to empathize with those impacted by it. Empathy is the ability to understand others’ emotions and experiences. While many believe empathy is a fixed trait, it’s a skill you can strengthen through practice.

When confronted with a problem, consider whom it impacts. Returning to the children’s sneaker example, think of who’s affected:

  • Your organization’s employees, because sales are down
  • The customers who typically buy your sneakers
  • The children who typically wear your sneakers

Empathy is required to get to the problem’s root and consider each group’s perspective. Assuming someone’s perspective often isn’t accurate, so the best way to get that information is by collecting user feedback.

For instance, if you asked customers who typically buy your children’s sneakers why they’ve stopped, they could say, “A new brand of children’s sneakers came onto the market that have soles with more traction. I want my child to be as safe as possible, so I bought those instead.”

When someone shares their feelings and experiences, you have an opportunity to empathize with them. This can yield solutions to their problem that directly address its root and shows you care. In this case, you may design a new line of children’s sneakers with extremely grippy soles for added safety, knowing that’s what your customers care most about.

Related: 3 Effective Methods for Assessing Customer Needs

3. Breaking Cognitive Fixedness

Cognitive fixedness is a state of mind in which you examine situations through the lens of past experiences. This locks you into one mindset rather than allowing you to consider alternative possibilities.

For instance, your cognitive fixedness may make you think rubber is the only material for sneaker treads. What else could you use? Is there a grippier alternative you haven’t considered?

Problem-solving is all about overcoming cognitive fixedness. You not only need to foster this skill in yourself but among your team.

4. Creating a Psychologically Safe Environment

As a leader, it’s your job to create an environment conducive to problem-solving. In a psychologically safe environment, all team members feel comfortable bringing ideas to the table, which are likely influenced by their personal opinions and experiences.

If employees are penalized for “bad” ideas or chastised for questioning long-held procedures and systems, innovation has no place to take root.

By employing the design thinking framework and creative problem-solving exercises, you can foster a setting in which your team feels comfortable sharing ideas and new, innovative solutions can grow.

Design Thinking and Innovation | Uncover creative solutions to your business problems | Learn More

How to Build Problem-Solving Skills

The most obvious answer to how to build your problem-solving skills is perhaps the most intimidating: You must practice.

Again and again, you’ll encounter challenges, use creative problem-solving tools and design thinking frameworks, and assess results to learn what to do differently next time.

While most of your practice will occur within your organization, you can learn in a lower-stakes setting by taking an online course, such as Design Thinking and Innovation . Datar guides you through each tool and framework, presenting real-world business examples to help you envision how you would approach the same types of problems in your organization.

Are you interested in uncovering innovative solutions for your organization’s business problems? Explore Design Thinking and Innovation —one of our online entrepreneurship and innovation courses —to learn how to leverage proven frameworks and tools to solve challenges. Not sure which course is right for you? Download our free flowchart .

management analysis and problem solving

About the Author

Book cover

Strategic Performance Management pp 93–108 Cite as

Problem-Solving and Performance Management Tools

  • Marc Helmold   ORCID: orcid.org/0000-0001-9759-9002 2  
  • First Online: 29 April 2022

1800 Accesses

Part of the Management for Professionals book series (MANAGPROF)

Problem-solving consists of using generic or ad hoc methods in an orderly manner to find solutions to problems. Some of the problem-solving techniques developed and used in philosophy, artificial intelligence, computer science, engineering, mathematics, medicine, and societies in general are related to mental problem-solving techniques studied in psychology and cognitive sciences (Helmold, 2021). The term problem-solving has a slightly different meaning depending on the discipline. For instance, it is a mental process in psychology and a computerized process in computer science. There are two different types of problems: ill-defined and well-defined; different approaches are used for each. Well-defined problems have specific end goals and clearly expected solutions, while ill-defined problems do not. Well-defined problems allow for more initial planning than ill-defined problems. Solving problems sometimes involves dealing with pragmatics, the way that context contributes to meaning, and semantics, the interpretation of the problem. The ability to understand what the end goal of the problem is, and what rules could be applied, represents the key to solving the problem. Sometimes the problem requires abstract thinking or coming up with a creative solution.

The quality, not the longevity, of one’s life is what is important. Martin Luther King

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

Buying options

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

Tax calculation will be finalised at checkout

Purchases are for personal use only

Bayer. (2021). www.bayer.com

Kepner-Tregoe. (2020). Kepner-Tregoe - Consulting Services - Leadership Development - Business Training. www.kepner-tregoe.com

Download references

Author information

Authors and affiliations.

IU University of Applied Sciences, Berlin, Germany

Marc Helmold

You can also search for this author in PubMed   Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to Springer Nature Switzerland AG

About this chapter

Cite this chapter.

Helmold, M. (2022). Problem-Solving and Performance Management Tools. In: Strategic Performance Management. Management for Professionals. Springer, Cham. https://doi.org/10.1007/978-3-030-98725-1_6

Download citation

DOI : https://doi.org/10.1007/978-3-030-98725-1_6

Published : 29 April 2022

Publisher Name : Springer, Cham

Print ISBN : 978-3-030-98724-4

Online ISBN : 978-3-030-98725-1

eBook Packages : Business and Management Business and Management (R0)

Share this chapter

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

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

Provided by the Springer Nature SharedIt content-sharing initiative

  • Publish with us

Policies and ethics

  • Find a journal
  • Track your research
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Additional menu

MindManager Blog

Nine essential problem solving tools: The ultimate guide to finding a solution

October 26, 2023 by MindManager Blog

Problem solving may unfold differently depending on the industry, or even the department you work in. However, most agree that before you can fix any issue, you need to be clear on what it is, why it’s happening, and what your ideal long-term solution will achieve.

Understanding both the nature and the cause of a problem is the only way to figure out which actions will help you resolve it.

Given that most problem-solving processes are part inspiration and part perspiration, you’ll be more successful if you can reach for a problem solving tool that facilitates collaboration, encourages creative thinking, and makes it easier to implement the fix you devise.

The problem solving tools include three unique categories: problem solving diagrams, problem solving mind maps, and problem solving software solutions.

They include:

  • Fishbone diagrams
  • Strategy maps
  • Mental maps
  • Concept maps
  • Layered process audit software
  • Charting software
  • MindManager

In this article, we’ve put together a roundup of versatile problem solving tools and software to help you and your team map out and repair workplace issues as efficiently as possible.

Let’s get started!

Problem solving diagrams

Mapping your way out of a problem is the simplest way to see where you are, and where you need to end up.

Not only do visual problem maps let you plot the most efficient route from Point A (dysfunctional situation) to Point B (flawless process), problem mapping diagrams make it easier to see:

  • The root cause of a dilemma.
  • The steps, resources, and personnel associated with each possible solution.
  • The least time-consuming, most cost-effective options.

A visual problem solving process help to solidify understanding. Furthermore, it’s a great way for you and your team to transform abstract ideas into a practical, reconstructive plan.

Here are three examples of common problem mapping diagrams you can try with your team:

1. Fishbone diagrams

Fishbone diagrams are a common problem solving tool so-named because, once complete, they resemble the skeleton of a fish.

With the possible root causes of an issue (the ribs) branching off from either side of a spine line attached to the head (the problem), dynamic fishbone diagrams let you:

  • Lay out a related set of possible reasons for an existing problem
  • Investigate each possibility by breaking it out into sub-causes
  • See how contributing factors relate to one another

MindManager Fishbone Diagram 1

Fishbone diagrams are also known as cause and effect or Ishikawa diagrams.

2. Flowcharts

A flowchart is an easy-to-understand diagram with a variety of applications. But you can use it to outline and examine how the steps of a flawed process connect.

Flowchart | MindManager

Made up of a few simple symbols linked with arrows indicating workflow direction, flowcharts clearly illustrate what happens at each stage of a process – and how each event impacts other events and decisions.

3. Strategy maps

Frequently used as a strategic planning tool, strategy maps also work well as problem mapping diagrams. Based on a hierarchal system, thoughts and ideas can be arranged on a single page to flesh out a potential resolution.

Strategy Toolkit MindManager 2018

Once you’ve got a few tactics you feel are worth exploring as possible ways to overcome a challenge, a strategy map will help you establish the best route to your problem-solving goal.

Problem solving mind maps

Problem solving mind maps are especially valuable in visualization. Because they facilitate the brainstorming process that plays a key role in both root cause analysis and the identification of potential solutions, they help make problems more solvable.

Mind maps are diagrams that represent your thinking. Since many people struggle taking or working with hand-written or typed notes, mind maps were designed to let you lay out and structure your thoughts visually so you can play with ideas, concepts, and solutions the same way your brain does.

By starting with a single notion that branches out into greater detail, problem solving mind maps make it easy to:

  • Explain unfamiliar problems or processes in less time
  • Share and elaborate on novel ideas
  • Achieve better group comprehension that can lead to more effective solutions

Mind maps are a valuable problem solving tool because they’re geared toward bringing out the flexible thinking that creative solutions require. Here are three types of problem solving mind maps you can use to facilitate the brainstorming process.

4. Mental maps

A mental map helps you get your thoughts about what might be causing a workplace issue out of your head and onto a shared digital space.

Mental Map | MindManager Blog

Because mental maps mirror the way our brains take in and analyze new information, using them to describe your theories visually will help you and your team work through and test those thought models.

5. Idea maps

Mental Map | MindManager Blog

Idea maps let you take advantage of a wide assortment of colors and images to lay down and organize your scattered thought process. Idea maps are ideal brainstorming tools because they allow you to present and explore ideas about the best way to solve a problem collaboratively, and with a shared sense of enthusiasm for outside-the-box thinking.

6. Concept maps

Concept maps are one of the best ways to shape your thoughts around a potential solution because they let you create interlinked, visual representations of intricate concepts.

Concept Map | MindManager Blog

By laying out your suggested problem-solving process digitally – and using lines to form and define relationship connections – your group will be able to see how each piece of the solution puzzle connects with another.

Problem solving software solutions

Problem solving software is the best way to take advantage of multiple problem solving tools in one platform. While some software programs are geared toward specific industries or processes – like manufacturing or customer relationship management, for example – others, like MindManager , are purpose-built to work across multiple trades, departments, and teams.

Here are three problem-solving software examples.

7. Layered process audit software

Layered process audits (LPAs) help companies oversee production processes and keep an eye on the cost and quality of the goods they create. Dedicated LPA software makes problem solving easier for manufacturers because it helps them see where costly leaks are occurring and allows all levels of management to get involved in repairing those leaks.

8. Charting software

Charting software comes in all shapes and sizes to fit a variety of business sectors. Pareto charts, for example, combine bar charts with line graphs so companies can compare different problems or contributing factors to determine their frequency, cost, and significance. Charting software is often used in marketing, where a variety of bar charts and X-Y axis diagrams make it possible to display and examine competitor profiles, customer segmentation, and sales trends.

9. MindManager

No matter where you work, or what your problem-solving role looks like, MindManager is a problem solving software that will make your team more productive in figuring out why a process, plan, or project isn’t working the way it should.

Once you know why an obstruction, shortfall, or difficulty exists, you can use MindManager’s wide range of brainstorming and problem mapping diagrams to:

  • Find the most promising way to correct the situation
  • Activate your chosen solution, and
  • Conduct regular checks to make sure your repair work is sustainable

MindManager is the ultimate problem solving software.

Not only is it versatile enough to use as your go-to system for puzzling out all types of workplace problems, MindManager’s built-in forecasting tools, timeline charts, and warning indicators let you plan, implement, and monitor your solutions.

By allowing your group to work together more effectively to break down problems, uncover solutions, and rebuild processes and workflows, MindManager’s versatile collection of problem solving tools will help make everyone on your team a more efficient problem solver.

Download a free trial today to get started!

Ready to take the next step?

MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster.

management analysis and problem solving

Why choose MindManager?

MindManager® helps individuals, teams, and enterprises bring greater clarity and structure to plans, projects, and processes. It provides visual productivity tools and mind mapping software to help take you and your organization to where you want to be.

Explore MindManager

business analyst mentor

The 5 Steps in Problem Analysis

problem analysis

One technique that is extremely useful to gain a better understanding of the problems before determining a solution is problem analysis .

Problem analysis is the process of understanding real-world problems and user’s needs and proposing solutions to meet those needs. The goal of problem analysis is to gain a better understanding of the problem being solved before developing a solution.

There are five useful steps that can be taken to gain a better understanding of the problem before developing a solution.

  • Gain agreement on the problem definition
  • Understand the root-causes – the problem behind the problem
  • Identify the stakeholders and the users
  • Define the solution boundary
  • Identify the constraints to be imposed on the solution

Table of Contents

Gain agreement on the problem definition.

The first step is to gain agreement on the definition of the problem to be solved. One of the simplest ways to gain agreement is to simply write the problem down and see whether everyone agrees.

Business Problem Statement Template

Opens in a new tab.

A helpful and standardised format to write the problem definition is as follows:

  • The problem of – Describe the problem
  • Affects – Identify stakeholders affected by the problem
  • The results of which – Describe the impact of this problem on stakeholders and business activity
  • Benefits of – Indicate the proposed solution and list a few key benefits

Example Business Problem Statement

There are many problems statement examples that can be found in different business domains and during the discovery when the business analyst is conducting analysis. An example business problem statement is as follows:

The problem of  having to manually maintain an accurate single source of truth for finance product data across the business, affects the finance department. The results of which has the impact of not having to have duplicate data, having to do workarounds and difficulty of maintaining finance product data across the business and key channels. A successful solution would  have the benefit of providing a single source of truth for finance product data that can be used across the business and channels and provide an audit trail of changes, stewardship and maintain data standards and best practices.

Understand the Root Causes Problem Behind the Problem

You can use a variety of techniques to gain an understanding of the real problem and its real causes. One such popular technique is root cause analysis, which is a systematic way of uncovering the root or underlying cause of an identified problem or a symptom of a problem.

Root cause analysis helps prevents the development of solutions that are focussed on symptoms alone .

To help identify the root cause, or the problem behind the problem, ask the people directly involved.

problem analysis fish bone diagram

The primary goal of the technique is to determine the root cause of a defect or problem by repeating the question “Why?” . Each answer forms the basis of the next question. The “five” in the name derives from an anecdotal observation on the number of iterations needed to resolve the problem .

Identify the Stakeholders and the Users

Effectively solving any complex problem typically involves satisfying the needs of a diverse group of stakeholders. Stakeholders typically have varying perspectives on the problem and various needs that must be addressed by the solution. So, involving stakeholders will help you to determine the root causes to problems.

Define the Solution Boundary

Once the problem statement is agreed to and the users and stakeholders are identified, we can turn our attention of defining a solution that can be deployed to address the problem.

Identify the Constraints  Imposed on Solution

We must consider the constraints that will be imposed on the solution. Each constraint has the potential to severely restrict our ability to deliver a solution as we envision it.

Some example solution constraints and considerations could be:-

  • Economic – what financial or budgetary constraints are applicable?
  • Environmental – are there environmental or regulatory constraints?
  • Technical  – are we restricted in our choice of technologies?
  • Political – are there internal or external political issues that affect potential solutions?

Conclusion – Problem Analysis

Try the five useful steps for problem solving when your next trying to gain a better understanding of the problem domain on your business analysis project or need to do problem analysis in software engineering.

The problem statement format can be used in businesses and across industries. 

requirements discovery checklist pack business analysis templates

Jerry Nicholas

Jerry continues to maintain the site to help aspiring and junior business analysts and taps into the network of experienced professionals to accelerate the professional development of all business analysts. He is a Principal Business Analyst who has over twenty years experience gained in a range of client sizes and sectors including investment banking, retail banking, retail, telecoms and public sector. Jerry has mentored and coached business analyst throughout his career. He is a member of British Computer Society (MBCS), International Institute of Business Analysis (IIBA), Business Agility Institute, Project Management Institute (PMI), Disciplined Agile Consortium and Business Architecture Guild. He has contributed and is acknowledged in the book: Choose Your WoW - A Disciplined Agile Delivery Handbook for Optimising Your Way of Working (WoW).

Recent Posts

Introduction to Train the Trainer for a Business Analyst

No matter the industry, modern professionals need to continuously improve themselves and work on up skilling and re-skilling to maintain satisfactory success within their field. This is particularly...

CliftonStrengths for a Business Analyst | Be You

Today, the job of a business analyst is probably more challenging than ever. The already intricate landscape of modern business analysis has recently gone through various shifts, mainly due to the...

  • Artificial Intelligence
  • Generative AI
  • Business Operations
  • Cloud Computing
  • Data Center
  • Data Management
  • Emerging Technology
  • Enterprise Applications
  • IT Leadership
  • Digital Transformation
  • IT Strategy
  • IT Management
  • Diversity and Inclusion
  • IT Operations
  • Project Management
  • Software Development
  • Vendors and Providers
  • United States
  • Middle East
  • Italia (Italy)
  • Netherlands
  • United Kingdom
  • New Zealand
  • Data Analytics & AI
  • Newsletters
  • Foundry Careers
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Copyright Notice
  • Member Preferences
  • About AdChoices
  • Your California Privacy Rights

Our Network

  • Computerworld
  • Network World

Sarah K. White

What is root cause analysis? A proactive approach to change management

Root cause analysis (RCA) focuses on fostering a proactive approach to solving problems before they happen and eliminating the potential for flaws to reoccur in the future.

Tree roots

Root cause analysis definition

Root cause analysis (RCA) is a problem-solving process that focuses on identifying the root cause of issues or errors with the goal of preventing them from reoccurring in the future. RCA is typically part of service management methodologies and frameworks, such as ITIL , TQM , and Kanban , that focus on continuous process improvement . This type of analysis can help identify flaws in IT processes, potential security breaches, and faults in business processes.

When a problem is identified and removed, it is considered a “root cause” if it prevents the problem from reoccurring. If, however, a problem is removed and it impacts the event’s outcome, but not in the way intended, then it is a “causal factor.” RCA is typically used to find the root cause of software or infrastructure problems to improve the quality and efficiency of processes, and thereby to save time and money. Every potential cause in a given process is identified and analyzed to ensure the organization is treating the disease, rather than just the symptoms.

Reactive vs. proactive problem management

Reactive management and proactive management are the two main approaches organizations take to repairing issues and solving problems. With reactive management, problems are fixed soon after they occur, often called “putting out fires.” The goal is to act quickly to resolve issues and alleviate any effects of a problem as soon as possible.

Proactive management, on the other hand, aims to prevent problems from reoccurring. It is focused less on quickly solving problems and instead on analyzing them to find ways to prevent them from happening again. That’s where root cause analysis comes in. Its methodology is best suited to support proactive problem management’s goal of identifying and fixing underlying issues, rather than just reacting to problems as they happen.

Root cause analysis steps

While there’s no strict rulebook on how to conduct a root cause analysis, certain guidelines can help ensure your root cause analysis process is effective. The four main steps that most professionals agree are essential for RCA to be successful include the following:

  • Identification and description: Organizations must first identify the failures, errors, or events that triggered the problem in question and then establish event descriptions to explain what happened.
  • Chronology: After identifying these issues, organizations must then create a sequential timeline of events to better visualize the root cause and any contributing causal factors. Here, it’s important to establish the nature of the event, the impact it had, and where and when the problem occurred.
  • Differentiation: Once the sequence of events is established, data involved with a particular issue can be matched to historical data from past analysis to identify the root cause, causal factors, and non-causal factors.
  • Causal graphing: Those investigating the problem should be able to establish key events that explain how the problem occurred and convert that data into a causal graph.

Root cause analysis takes a systematic approach to identifying problems and requires the effort of full teams to properly perform the analysis. Those tasked with the analysis typically work backwards to determine what happened, why it happened, and how to reduce the chances of it happening again. They can trace triggered actions to find the root cause that started the chain reaction of errors in a process to remedy it. These steps help guide the process and give organizations a framework for how to successfully complete a root cause analysis.

Root cause analysis methods

RCA is already baked into several IT frameworks and methodologies as a step for change, problem, or risk management. It’s been established as a proven, effective way to support continuous process and quality improvement. But if you are conducting a root cause analysis outside of a separate process management framework, organizations typically employ the following methods to ensure a successful RCA:

  • Form a team to conduct the RCA and evaluate processes and procedures in the organization that have flaws. This team should be built by bringing together employees who work in relevant business areas or who work directly with the broken processes.
  • Once the analysis begins, it can take upwards of two months to complete. Each step of the process is given equal weight whether it’s defining and understanding the problem, identifying possible causes, analyzing the effects of the problem, or determining potential solutions.
  • Teams should meet at least once per week, if not more often, with meetings being kept to no longer than two hours with a loose agenda. The meetings are intended to be relatively creative, so you want to avoid bogging people down with too much structure.
  • Team members should be assigned specific roles or tasks so everyone has a clear understanding of what they should be investigating.
  • Upon finding a potential solution, it’s crucial to follow up to make sure that the solution is effective and that it’s implemented successfully.

Root cause analysis tools

You don’t need much to conduct a root cause analysis, but there are several tools that are helpful and commonly used to help make the process easier. Commonly used tools to perform an effective root cause analysis include:  

  • Fishbone diagrams: A fishbone diagram is mapped out in the shape of a fishbone, allowing you to group causes into sub-categories to be analyzed.
  • Failure mode and effects analysis (FMEA): FMEA is a technique that can be used to map out a system or process and identify the failures within it. It can be used not only to identify flaws but also to map out how often they happen, what actions have already been taken, and what actions have been effective in remedying the issue.
  • Pareto charts: A Pareto chart is a simple bar chart that maps out related events and problems in order of how often they occur. This helps identify which problems are more significant than others and where to focus process improvement efforts.
  • Scatter diagrams: A scatter diagram plots data on a chart with an x and y axis. This is another useful tool for mapping out problems to understand their impact and significance.
  • Fault tree analysis: A fault tree analysis uses Boolean logic to identify the cause of problems or flaws. They are mapped out on a diagram that looks like a tree, where every potential cause is included as its own “branch.”
  • 5 whys analysis: With 5 whys analysis, you will ask the question “why” five times too delve deeper into a problem to develop a clearer picture of its root cause.

Root cause analysis training

While RCA is a part of other frameworks and methodologies, there are training programs and courses designed to focus on helping people better understand how to perform the analysis. If you want to get more training on RCA, here are a handful of programs designed to help:

  • Workhub Root Cause Analysis training
  • Udemy Root Cause Analysis course
  • Pink Elephant Problem Management: Root Cause Analysis Specialist certification course
  • NSF Root cause analysis CAPA training and certification
  • Coursera Root Cause Analysis course
  • ASQ root cause analysis course
  • Lean Six Sigma Root cause analysis online training

Related content

How strategic partnerships are the key to ai-driven innovation, unleashing the power of banks’ data with generative ai, the generative ai revolution is transforming how banks work, sap names philipp herzig as chief artificial intelligence officer, from our editors straight to your inbox.

Sarah K. White

Sarah White is a senior writer for CIO.com, covering IT careers, hiring & staffing, and diversity.

More from this author

Black tech pipeline connects black it pros to dei-committed employers, how built unites black it pros and builds equity, women it leaders on their climb to the top, top 10 countries attracting international tech talent, most popular authors.

management analysis and problem solving

Show me more

Adp’s cloud transformation pays dividends.

Image

Why Tomago Aluminium reversed course on its cloud journey

Image

Microsoft invests €3.2 billion in AI and in the cloud Germany

Image

CIO Leadership Live UK with Graham OSullivan, CIO, OneFamily

Image

CIO Leadership Live Canada with Lekan Olawoye, Founder, BPTN

Image

CIO Leadership Live Australia with Brett Reedman, Chief Information Officer, Catholic Healthcare

Image

CIO Leadership Live UK with Graham O'Sullivan, CIO, OneFamily

Image

The Workplace Changes Companies Aren’t Prepared For

Image

Sponsored Links

  • Want to justify your IT investments faster? IDC reports on how to measure business impact.
  • Read this IDC spotlight to learn what commonly prevents value realization – and how to solve it
  • Experience the comprehensive solution that provides end-to-end visibility across applications, infrastructure, and network layers. Plus improve your IT operations and enhance overall business performance. Sign up for a Free Trial and explore the benefits

loading

How it works

For Business

Join Mind Tools

Article • 4 min read

Means-End Analysis

Identifying the steps needed to solve a problem.

By the Mind Tools Content Team

management analysis and problem solving

Means-End Analysis is a simple tool that helps you to identify the practical steps needed to solve a problem or to reach a desired state.

In this article we'll explore Means-End Analysis, and we'll look at how you can apply it.

About the Tool

Means-End Analysis is essentially an early form of Gap Analysis . It was created by researchers Allen Newell and Herbert Simon in the late 1950s, and it was then published their 1972 book, "Human Problem Solving."

Newell and Simon were creating an effective problem-solving program for early computers, and Means-End Analysis was a direct result of this research. They named the tool "Means-End" because it helps you define the means needed to reach a desired end.

Means-End Analysis might seem quite simplistic at first glance. However, when you begin using it, you'll find that it's a practical and useful method for solving simple problems.

How to Use the Tool

Step 1: define your initial state (problem).

Start by defining the problem you're trying to solve. It might help to write the problem down on a piece of paper, or even draw out a diagram.

It's important to you make sure you're trying to solve the right problem, and not just a symptom of a deeper issue. If you're struggling to do this, you can use tools such as Root Cause Analysis , Cause and Effect Analysis , CATWOE , and the 5 Whys to help define your problem, and to make sure that you're addressing the real issue.

Step 2: Visualize Your Goal State

Next, picture the ideal state you'd like to be in. This is the outcome you'd like to see, once the problem is solved.

Again, it might be helpful to write this out on paper.

Step 3: List the Differences Between States

Now, look at the differences between your initial state and your goal state. And then explore the obstacles that are stopping you from reaching this state. Make a list of these differences and obstacles.

If the obstacles seem overwhelmingly large, consider using Drill Down to break them down into easy-to-understand chunks.

Step 4: Create Sub-Goals

Once you have a list of the differences and obstacles that you need to overcome, you need to create sub-goals that will help you address each of these.

Think of these sub-goals as steps that will ultimately lead you to your desired goal state – look at each obstacle you've listed, and then create the plans you need to overcome them.

Step 5: Take Action

The last step is to take action on your analysis.

If you're dealing with a simple problem, you'll be able to identify all of the actions that you need to take to solve your problem quickly. ( Action Plans are useful here.)

However, if you're solving a difficult problem, or planning a new project, you'll likely have to do further analysis and planning. The Simplex Process is useful for solving complex problems, while our project management section will help you plan more complex projects.

Means-End Analysis is a simple problem-solving tool that you can use to solve well-defined problems, and to kick-start the planning stage of a new project.

To use the tool, first look at your initial state (the state you're in right now). Then, picture your desired goal state – this is the state you want to be in once you've solved the problem or completed the project.

Next, make a list of the obstacles that are standing in the way of your goal state, and create sub-goals that will guide you in overcoming all those obstacles.

Finally, take action on your analysis.

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

How to build expert power.

Developing and promoting your expertise

Porter's Generic Strategies

Choosing Your Route to Success

Add comment

Comments (0)

Be the first to comment!

management analysis and problem solving

Enhance your in-demand workplace skills

Top skills - leadership, management, communication and more - are available to develop using the 3,000+ resources available from Mind Tools.

Join Mind Tools 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

Most Popular

Mind Tools Store

About Mind Tools Content

Discover something new today

Recommended for you.

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

IT professionals checking servers

Problem management is the discipline of proactively and reactively identifying IT issues and solutions to minimize any impact on an IT team’s ability to deliver services to end users.

Issues within IT services are called incidents and problems, which differ based on their frequency, impact, and solutions. In general, multiple recurring incidents are considered problems that are likely to continue if left unaddressed.

IT services include a complex system of interdependent applications, software, hardware, IT infrastructure and other technologies. Service disruptions can disrupt an organization’s goal of continual service improvement and create serious reputational and financial issues for an organization, so their IT teams need to prioritize solving problems efficiently and effectively.

Proactive problem management is an important component of an organization’s approach. It is necessary to identify incidents and known problems and solve errors before they cascade into even larger ones.

Thankfully, organizations can utilize automation to help better manage the impact of incidents and problems, delivering improved services and more resilient applications to maximize uptime. This can lead to reduced costs and improved decision-making. 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.

Organizations that are starting or improving a robust problem management process must also manage organizational change . 1   (link resides outside ibm.com) Robust problem management not only addresses incidents in an organization’s tech stack, but it also compels that organization to explore better ways to address incidents across their operations. Effective problem management requires rigorous categorization and prioritization, which subsequently allow the business to address its most pertinent problems. Ideally, an organization will focus on solving major incidents and major problems first and then transition to other incidents and problems that have a less pronounced impact on the business.

IBM Instana Observability gives everyone across the enterprise user-friendly access to the data they want with the context they need to deliver rapid issue prevention and remediation.

Sign up for the IBM newsletter

Problem management is intended to prevent the incident from reoccurring by addressing the root cause. It is related to incident management in that if the incident has occurred several times, it should be diagnosed and investigated as a problem or known error.

Incident management without problem management only addresses symptoms and not the underlying cause, leading to similar incidents occurring in the future. Effective problem management identifies a permanent solution to problems, decreasing the number of incidents an organization will have to manage in the future.

Ultimately, problem management seeks to understand the problem lifecycle, identify the root cause of the problem and fix the conditions 2 (link resides outside ibm.com) that led to its creation.

A problem management team can either engage in reactive or proactive problem management, depending on what incidents they observed 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 first must occur before organizations can apply reactive problem management.

Proactive problem management involves more investigative work on why a problem is happening and building a solution to prevent it from happening again. This type of problem management is more concerned with identifying the root cause, so the team can deploy a lasting solution that helps to avoid future problems.

Effective problem management is an important component of 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. The goal of any organization’s ITSM strategy is to enable and maintain optimal deployment, operation and management of every single IT resource. Problem management is a core component of ITSM.

Organizations often utilize several native and open-source strategies for accomplishing ITSM, especially using the Information Technology Infrastructure Library (ITIL).

ITIL is the most widely adopted best-practices guidance framework for implementing and documenting ITSM. ITIL problem management uses ITIL processes to minimize the foundational work that needs to go into addressing any one problem. Many problems that organizations face such as server outages and cyber security issues have happened before to other organizations and can often have standardized responses. Therefore, ITSM approaches often incorporate ITIL to minimize the required amount of custom work to solve IT problems.

Most problem management approaches follow a similar pattern of assessment, logging, analysis, and solution. Each component is necessary to ultimately solve the problem.

  • Problem detection: Automated systems or IT professionals identify recurring incidents that could be classified as a problem.
  • Problem assessment: This involves the identification and categorization of an incident as a problem record or as an unrelated issue that is unlikely to occur again.
  • Problem logging:  This involves the IT team logging the identified problem and tracking each occurrence. Problem management teams that encounter a problem log it, often via a self-service platform, to create a problem record, which is the comprehensive accounting for the problem, any related incidents, where and how the problem occurred, the root cause analysis and the solution. That creates a known error record that is entered in the known error database (KEDB). Advanced organizations will often combine their problem-management and knowledge-management approaches.
  • Root cause analysis: The organization studies the underlying issues behind these problems and develops a roadmap to create a long-term solution.
  • Solve the problem: When an IT team understands the problem and its root cause, it can address the problem (also known as problem control). This can involve a quick or protracted response depending on the severity or complexity of the problem.
  • Error control: Finally, an organization that successfully diagnoses 3 (link resides outside ibm.com) and solves the problem through a work-around or a permanent resolution conducts error control for that problem.

Problem management requires a well-thought-out approach to ensure a team is allocating resources as efficiently as possible. Fortunately, problem management teams can utilize several levers to successfully address problems effectively and efficiently, getting to the root cause and creating solutions that can stop the problem from happening again.

The Pareto principle, also known as the Pareto 80:20 rule, states that about 80% of problems arise from 20% of the causes. Put another way, an overwhelming majority of problems stem from a few major causes. Therefore, problem solving for those 20% of issues will efficiently solve many of the organization’s problems. 

Problem management teams ask why something happened five times to help get to the root cause of any problem. Addressing user experience is a good example of the five whys in action.

  • Why #1: Users report substandard experience because of long load times.
  • Why #2: The website takes too long to load because of slow or overloaded servers.
  • Why #3: Inefficient code causes the server to run slowly.
  • Why #4: Poorly written database queries fetch unnecessary data leading to inefficient code.
  • Why #5: Overly complicated queries with multiple nested subqueries, which ultimately contribute to the long load time.

Therefore, DevOps can solve the user experience problem by simplifying the query structure.

Root cause analysis (RCA) is the quality management process by which an organization searches for the root of a problem, issue or incident after it occurs. Organizations need to find the root cause of any problem to effectively solve the problem.

This is a tool (link resides outside ibm.com) for identifying the potential causes of a specific problem. It places the problem or effect at the “head” of the fish while using the “bones” to list potential causes organized by categories. It is like the five whys approach, but it adds more structure to the potential causes part of the cause analysis.

The goal of problem management is to minimize downtime, increase efficiency and improve service delivery. Below are some of the more impactful benefits of problem management.

  • Enhanced security: Identifying the underlying cause of incidents is an important part of cyber risk management . Organizations that merely patch or resolve individual incidents without exploring their root cause may never discover 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 catastrophic problems for the organization.
  • Increased customer satisfaction: Customers have certain expectations about their services and are unhappy whenever they don’t receive the services that they expected or paid for. Organizations that cannot deliver service reliably risk losing customers and will struggle to recruit new ones. Customers can tolerate occasional disruptions to service, like the inability to access a website or application due to a traffic overload or a chatbot malfunctioning. However, they will have less tolerance for sustained downtime or potential risks to cyber-criminal activity. Incidents that cascade into larger problems are likely to create unhappy customers. By prioritizing problem identification and problem resolution, organizations can minimize downtime and create happier customers.
  • Improved knowledge management: Long-standing organizations have likely encountered many types of tech incidents and problems throughout their history. Organizations that prioritize knowledge management , the process of identifying, organizing, storing and disseminating information in a knowledge base within an organization, 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.
  • Increased productivity and employee satisfaction: Organizations have two options when pursuing problem management: reactive problem management or proactive problem management. IT employees join organizations to work on large problems and make meaningful differences. They do not want to repeatedly fix the same recurring problems without having the chance to work on higher-level opportunities. Organizations need sophisticated problem management to improve their IT operations and to keep employees happy and engaged.

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

Optimize software usage and cost

{In one or two sentences, introduce to the learn topic resources (optional).}

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 that need remedying. 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 ensuring your observability strategy can keep up with the dynamic complexity of today’s environments, and tomorrow’s. From mobile to mainframe, Instana supports over 250 technologies and growing.

1  Problem Management: A Practical Guide (link resides outside ibm.com), Jim Bolton III and Buff Scott III, 2016 

2  What is root cause analysis? A proactive approach to change management (link resides outside ibm.com), CIO, 6, May 2022

3  Problem Management: Frequently Asked Questions (link resides outside ibm.com), University of Minnesota

management analysis and problem solving

  • Problem management techniques
  • Get Problem management kit

Problem management

Everything you need to know about effective problem management

  • Try ServiceDesk Plus now
  • Start my free trial

For this section, we will dive into the various techniques employed to find the root cause of a problem in an IT environment.

IT Problem management techniques

The problem management process can be mandated with a good service desk tool, but the techniques used for investigation and diagnosis should vary according to the organization. It's recommended that investigation techniques are flexible based on the organization's needs rather than being overly prescriptive.

Since problems can appear in any shape or size, it's impossible to stick to one technique to find a solution every time; instead, using a combination of techniques will yield the best results. A simple LAN connectivity problem might be solved with a quick brainstorming session, but a network or VoIP issue might need a deeper look.

Here are several techniques you can practice in your organization's problem management process.

Brainstorming

Brainstorming techniques  for problem solving

By establishing a dialogue between departments, you gain various perspectives and new information, generating many potential solutions.

To have a productive brainstorming session, you need a moderator. The moderator handles the following:

  • Driving the direction of the meeting
  • Documenting the insights obtained
  • Highlighting the measures to be taken
  • Tracking the discussed deliverable
  • Preventing a time-consuming session

Brainstorming sessions are more productive when collaborative problem-solving techniques, such as Ishikawa analysis and the five whys method, are used. These techniques will be discussed later in this section.

Kepner-Tregoe method

Kepner tregoe problem solving method

The Kepner-Tregoe (K-T) method is a problem-solving and decision-making technique used in many fields due to its step-by-step approach for logically solving a problem. It's well-suited for solving complex problems in both proactive and reactive problem management.

The method follows four processes:

  • Situation appraisal: Assessment and clarification of the scenario
  • Problem analysis: Connecting cause with effect
  • Decision analysis: Weighing the alternate options
  • Potential problem analysis: Anticipating the future

However, problem analysis is the only part that concerns IT problem management, and it consists of five steps.

Define the problem

Identifying what the problem truly is can be a problem in itself. Since problem management is inherently a collaborative effort, having a comprehensive definition of the problem eliminates preconceived notions that any participating member might have, saving a considerable amount of time.

For example, if an organization's automatic data backup on a server has failed, the problem can be defined as:

Failed backup on server

This definition indeed describes the deviation from the normal situation, but it demands more questions and information. A good model of a definition should be unambiguous and easily understood.

To remove ambiguity, the above definition can be updated to:

Data backup on November 15 failed on server #34-C

This definition provides more clarity, and spares employees from redundant questions. Nevertheless, this definition can be further improved. Suppose the cause of the data backup failure can be attributed to an event such as the application of a new patch; then the initial problem analysis would undoubtedly lead to this event.

To save time and effort, let's update the definition to:

Data backup on November 15 failed on server #34-C after application of patch 3.124 by engineer Noah

This detailed definition leaves no room for redundant questions, and provides a good amount of information on where the problem could lie. These extra minutes spent on the initial definition save valuable time and effort, provide a logical sense of direction to analysis, and remove any preconceived notions about the problem.

Describe the problem

The next step is to lay out a detailed description of the problem. The K-T method provides the questions that need to be asked on any problem to help identify the possible causes.

The questions below help describe four parts of any problem:

  • What is the problem?
  • Where did the problem occur?
  • When did the problem occur?
  • To what extent did the problem occur?

Each of these questions demands two types of answers:

IS: As in, "What is the problem?" or "Where is the problem?"

COULD BE but IS NOT: As in, "Where could the problem be but is not?"

This exercise helps compare and highlight the what, where, when, and how the deviation from normal performance in business processes is happening.

Establish possible causes

The comparison between normal performance and deviated performance made in the previous step helps in shortlisting the possible causes of the problem. Making a table with all the information in one place can be helpful to make the comparison.

New possible causes become evident when the information is assembled together. For our example problem, the root cause can be narrowed down to:

Procedural error caused by the inadequate transfer of knowledge by the Level 3 engineers.

Whatever the problem, a sound analysis for possible causes can be done based on relevant comparison.

Test the most probable cause

The penultimate step is to short-list the probable causes and test them before proceeding to the conclusion. Each probable cause should follow this question:

If _______ is the root cause of this problem, does it explain what the problem IS and what the problem COULD BE but IS NOT?

Again, it's beneficial to populate all the information into a table.

Verify the true cause

The final step is to eliminate all the improbable causes and provide evidence to the most probable causes. With this verification, it's time to propose a solution to the problem. Without evidence of the possible root cause, the solution should not be attempted.

Ishikawa analysis, or fishbone diagram analysis

Fishbone analysis

Ishikawa analysis uses the fishbone framework to enumerate the cause and effects of a problem, and can be used in conjunction with brainstorming sessions and the five whys method. The simplicity in executing RCA using an Ishikawa diagram shouldn't deceive you of its prowess to handle complex problems.

To start the analysis, define the problem and use it as the head of the fishbone. Draw the spine and add the categories that the problem could be originating from as ribs to the fishbone.

Generally, it's easiest to start the categories with the four dimensions of service management: partners, processes, people, and technology. However, these categories can be anything relevant to your problem, environment, organization, or industry.

Once these categories form the ribs of the fishbone, start attaching possible causes to each category. Each possible cause can also branch out to detail the reason for that occurrence. This could lead to a complex diagram of four to five levels of causes and effects, subsequently drilling down to the root cause of the problem.

Ishikawa diagaram

It's recommended to split up dense ribs into additional ribs as required. Alternatively, merging empty ribs with other suitable ribs keeps the fishbone clean and easy to read. Additionally, you should ensure the ribs are populated with causes, not just symptoms of the problem.

This analysis is again a collaborative effort, and requires a moderator to direct the brainstorming sessions in an effective way. Every participant has the opportunity to engage, providing a comprehensive view of the problem.

Pareto analysis

Pareto analysis

The Pareto principle is an observation that approximately 80 percent of effects come from approximately 20 percent of causes. This observation applies to a wide range of subjects, including problem management.

When trying to reduce the number of incidents occurring in an organization, it's highly efficient to apply Pareto analysis before jumping into solving the problems. Pareto analysis prioritizes the causes of incidents, and helps in managing problems based on their impact and probability.

This analysis is carried out by generating a Pareto chart from a Pareto table. A Pareto table consists of the cumulative count of classification of all problems. A Pareto chart is a bar graph showing the cumulative percentage of the frequency of various classification of problems.

To create a Pareto chart, follow the steps given below:

  • Collect problem ticket data from your service desk tool.
  • Remodel the data into categories based on various attributes.
  • Create a Pareto table to find the frequency of problems in each classification over a period of time.
  • Compute the frequency of problem occurrences in each category.
  • Generate the cumulative frequency percentage in decreasing order.
  • Plot the data on a graph to create a Pareto chart.

The most important step is to remodel the data into a countable set of classifications and attributes.

Pareto chart analysis

This chart helps identify the problems that should be solved first to significantly reduce service disruption. This analysis complements the Ishikawa and Kepner-Tregoe methods by providing a way to prioritize the category of problems, while the other methods analyze the root cause.

It's important to remember that the 80/20 rule suggests likely causes, and may be incorrect at times.

Five whys technique

5 whys example

Five whys is a straightforward technique for RCA. It defines a problem statement, then repeatedly asks why until the underlying root cause of the problem is discovered. The number of whys doesn't need to be limited to five, but can be based on the problem and the situation.

The five whys technique complements many other problem-solving techniques like the Ishikawa method, Pareto analysis, and the K-T method.

Using the previous example of the data backup failure in a server, let's apply the five whys technique.

The above iterative process reveals the absence of a standardized format, which has led to the problem of data backup failure.

For our purposes, the example above is a simple execution of the method. In a real scenario, the next question depends on the answer to the previous question, so it's imperative to collaborate with stakeholders who have elaborate knowledge of the domain the problem resides in.

By adopting parts of the K-T method along with the five whys technique, such as providing evidence to each answer before validating it with a return question, you can ensure precise analysis during problem-solving sessions.

5 whys to solve problems

Other techniques

Apart from the five major techniques, there are still numerous others, each with their own unique strengths. Overall, problem investigation is carried out using a combination of techniques suitable for the situation. Some other techniques that are prevalent in the problem management community are chronological testing, fault tree analysis, the fault isolation method, hypothesis testing, and pain value analysis. It's worth taking the time to learn many techniques as your organization's problem management process matures.

You have made it so far! In our penultimate part of the six-part series, you will learn about the best practices of problem management that can help you jump past any hurdles during your problem management journey.

Reactive vs Proactive problem management

Problem management best practices

Assess your incident response readiness to kick-start your problem management journey

The zeroth step in the journey towards proactive problem management is establishing a robust incident management process in your IT environment. Discover how Zoho, our parent company, handles the spectrum of incidents thrown at it year over year and assess your incident management readiness at an enterprise scale.

Download a free copy of our incident management handbook and a best practice checklist to review your problem management solution.

Problem management sofware feature checklist

Problem management feature checklist

major incident procedure

IT incident management handbook

  •   Live Demo
  •   Compare
  •   Get quote

IMAGES

  1. The 5 Steps of Problem Solving

    management analysis and problem solving

  2. Problem Solving Infographic 10 Steps Concept Vector Image

    management analysis and problem solving

  3. 5 step problem solving method

    management analysis and problem solving

  4. Six Sigma Problem Solving Process

    management analysis and problem solving

  5. An Overview Of 9 Step Problem Solving Model

    management analysis and problem solving

  6. Problem Solving Cycle

    management analysis and problem solving

VIDEO

  1. Principles of Management

  2. PRINCIPLES OF MANAGEMENT DETAILED EXPLANATION PART 5

  3. Nodal Analysis Problem Solving

  4. Risk Management Analysis of HSBC bank

  5. Risk Management Analysis of Nestle

  6. MANAGEMENT CONCEPTS&PRINCIPLES I MANAGEMENT CONCEPTS I PART 2

COMMENTS

  1. What is Problem Solving? Steps, Process & Techniques

    1. Define the problem Diagnose the situation so that your focus is on the problem, not just its symptoms. Helpful problem-solving techniques include using flowcharts to identify the expected steps of a process and cause-and-effect diagrams to define and analyze root causes. The sections below help explain key problem-solving steps.

  2. Analysis and Problem Solving

    Analysis and Problem Solving is the ability to critically evaluate data and use judgement to work through issues. It involves spotting connections between data. And essentially, involves seeing and actioning solutions effectively. Firstly, Analysis is about being objective. And looking for evidence to support the conclusions we reach.

  3. 7 Problem-Solving Skills That Can Help You Be a More ...

    1. Analysis As a manager, you'll solve each problem by assessing the situation first. Then, you'll use analytical skills to distinguish between ineffective and effective solutions. 2. Communication Effective communication plays a significant role in problem-solving, particularly when others are involved.

  4. Problem management: 8 steps to better problem solving

    November 27th, 2022 6 min read Jump to section What is problem management? The 8 steps of problem management 5 benefits of problem management Problem management leads to better, faster solutions View Templates Summary Problem management is an 8 step framework most commonly used by IT teams.

  5. What Is Problem Solving in Project Management? Here's Everything You

    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.

  6. How to master the seven-step problem-solving process

    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.

  7. PDF Problem Solving in Organizations

    An indispensable guide enabling business and management students to develop their professional competences in real organizational settings, this new and fully updated edition of Problem Solving in Organizations equips the reader with the necessary toolkit to apply the theory outlined in this book to practical business problems.

  8. 35 problem-solving techniques and methods for solving ...

    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.

  9. Decision making and problem solving

    Competing Through Manufacturing. Decision making and problem solving Magazine Article. Steven C. Wheelwright. Robert H. Hayes. The past several years have witnessed a growing awareness among ...

  10. How to Solve Problems

    How to Solve Problems. To bring the best ideas forward, teams must build psychological safety. Teams today aren't just asked to execute tasks: They're called upon to solve problems. You'd ...

  11. Why Problem-Solving Skills Are Essential for Leaders

    4 Problem-Solving Skills All Leaders Need. 1. Problem Framing. One key skill for any leader is framing problems in a way that makes sense for their organization. Problem framing is defined in Design Thinking and Innovation as determining the scope, context, and perspective of the problem you're trying to solve.

  12. Problem-Solving and Performance Management Tools

    Problem-solving consists of using generic or ad hoc methods in an orderly manner to find solutions to problems. Some of the problem-solving techniques developed and used in philosophy, artificial intelligence, computer science, engineering, mathematics, medicine, and societies in general are related to mental problem-solving techniques studied in psychology and cognitive sciences (Helmold, 2021).

  13. 9 essential problem solving tools: the ultimate guide

    Problem solving diagrams Mapping your way out of a problem is the simplest way to see where you are, and where you need to end up. Not only do visual problem maps let you plot the most efficient route from Point A (dysfunctional situation) to Point B (flawless process), problem mapping diagrams make it easier to see: The root cause of a dilemma.

  14. Problem Analysis In HR: 5 Problem-Solving Techniques

    Problem analysis in HR is the process of identifying, evaluating, and proposing possible solutions to HR-related issues within an organization.

  15. Managerial Problem Solving and Decision Making

    According to Galli and Hudson (2020), problem solving and decision making are inseparable concepts in that both problem-solving and decision-making each require an evaluation of the...

  16. The 5 Steps In Problem Analysis

    A helpful and standardised format to write the problem definition is as follows: The problem of - Describe the problem. Affects - Identify stakeholders affected by the problem. The results of which - Describe the impact of this problem on stakeholders and business activity. Benefits of - Indicate the proposed solution and list a few key ...

  17. What is root cause analysis? A proactive approach to change management

    Root cause analysis (RCA) is a problem-solving process that focuses on identifying the root cause of issues or errors with the goal of preventing them from reoccurring in the future.

  18. Means-End Analysis

    The Simplex Process is useful for solving complex problems, while our project management section will help you plan more complex projects. Key Points. Means-End Analysis is a simple problem-solving tool that you can use to solve well-defined problems, and to kick-start the planning stage of a new project. To use the tool, first look at your ...

  19. What Is Problem Analysis? (With Processes and Useful Types)

    Problem analysis is a series of steps for identifying problems, analyzing them, and developing solutions to address them. It's an inquiry or investigation into the causes of an error, failure, or unexpected incident.

  20. The Importance of Data Analysis in Problem Solving

    These problems will be because of various reasons — businesses, the environment, the stakeholders, and sometimes purely due to people's psychology. To solve those problems, data analysis is very important. Data crunching, business analysis and finding unique insights is a very essential part of management analysis and decision making.

  21. Problem Management

    Problem management is the discipline of proactively and reactively identifying IT issues and solutions to minimize any impact on an IT team's ability to deliver services to end users. ... problem solving for those 20% of issues will efficiently solve many of the organization's problems. ... Root cause analysis (RCA) is the quality ...

  22. 5 techniques for IT problem management

    Problem analysis: Connecting cause with effect; Decision analysis: Weighing the alternate options; Potential problem analysis: Anticipating the future; However, problem analysis is the only part that concerns IT problem management, and it consists of five steps. Define the problem. Identifying what the problem truly is can be a problem in itself.

  23. The difference between Problem Management and Problem Solving

    The "Problem Management" journey often starts with some ITIL training and maybe we even buy consulting assistance. Then, we define a theoretically problem management process description, which ...

  24. Get A Job Ghana on Instagram: "We are seeking a highly motivated and

    13 likes, 0 comments - getajobghana on November 20, 2023: "We are seeking a highly motivated and experienced Sales Manager to join our growing cement manufa..."