problem solving meaning management

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

• 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
• AI Essentials for Business
• Alternative Investments
• Business Analytics
• Business Strategy
• Business and Climate Change
• Creating Brand Value
• 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 Change and Organizational Renewal
• 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

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

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

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 .

About the Author

• Project Management

Home » Free Resources » »

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

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

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

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

What Is Problem-Solving?

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

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

The Importance of Problem-Solving in Project Management

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

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

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

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

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

Problem-Solving Steps in Project Management

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

#1. Define the Problem

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

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

#2. Analyze Root Causes

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

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

#3. Brainstorm Potential Solutions

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

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

#4. Evaluate Potential Solutions

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

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

#5. Decide on a Plan of Action

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

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

#6. Implement the Action Plan

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

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

#7. Monitor and Track Results

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

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

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

Also Read: 5 Project Management Steps You Need to Know

How Project Management Tools Can Help You in Problem-Solving

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

The best project management software will include the following:

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

Examples of Problem-Solving

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

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

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

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

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

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

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

A Construction Project Is Falling Behind Due to Inclement Weather

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

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

Also Read: Understanding KPIs in Project Management

Improve Your Problem-Solving and Project Management Skills

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

This program teaches skills such as:

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

You might also like to read:

5 Essential Project Management Steps You Need to Know

Project Management Frameworks and Methodologies Explained

13 Key Project Management Principles and How to Use Them

Project Management Phases: A Full Breakdown

How To Develop a Great Project Management Plan in 2023

Leave a Comment Cancel Reply

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

Recommended Articles

Project Management Tips: What is a Feasibility Study?

What is a feasibility study? The short answer is that it can prevent project failures. This guide explores its fundamentals, applications, and best practices.

Design for Six Sigma: Methodology, Tools, and More

Learn the basics of Design for Six Sigma with our detailed guide. From methodology to tools, discover how DFSS helps create high-quality products and processes from the ground up.

Demystifying Project Management Documentation

This article explores project management documentation, its uses, importance, types, tools, and best practices.

Exploring the Role of a Scrum Master in Project Management

This article covers a Scrum master’s role in project management, including what they are, what they do, roles and responsibilities, skills, and how to become one.

13 Project Management Principles and How to Use Them

Master the core principles of project management. Discover essential insights for effective project leadership and success.

12 Best Project Management Books You Must Read in 2024

Whether you’re an official project manager or someone who manages projects at work, it’s always helpful to learn some of the tools and techniques available. Check out this list of the best project management books for professionals at all experience levels.

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

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

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

What Is Problem Solving?

Definition and importance.

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

Problem-Solving Steps

The problem-solving process typically includes the following steps:

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

Defining the Problem

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

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

Generating Solutions

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

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

Evaluating and Selecting Solutions

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

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

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

Implementing and Monitoring the Solution

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

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

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

Problem-Solving Techniques

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

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

Brainstorming

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

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

When brainstorming, remember to:

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

Root Cause Analysis

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

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

SWOT Analysis

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

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

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

Mind Mapping

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

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

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

Examples of Problem Solving in Various Contexts

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

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

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

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

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

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

What Is Problem-Solving? How to Use Problem-Solving Skills to Resolve Issues

Great businesses don’t exist to simply grow and make money. Instead, they solve the world’s problems , from tiny issues to giant dilemmas. Problem-solving is essentially the main function of organizations. An effective organization will have systems and processes in place to reach their goals and solve problems. If a company has team members and leaders who have poor problem-solving skills, that means they’re ineffective at one of the core functions of a business.

What Is Problem-Solving?

What is the general process of problem-solving, 1. define the problem, 2. brainstorm possible solutions, 3. research several options.

After you’ve come up with several possible alternative solutions, pick two or three that seem the most promising using your analytical skills. Then you’ll need to buckle down and do some research to see which one to pursue. Conduct your research using primary and secondary resources.

4. Select a Solution

In order to make the most objective decision:

5. Develop an Action Plan

When the right choice is made, and the solution is placed into the overall strategy, start developing an action plan . Lay out the “who,” “what,” “when,” “why,” and “how.” Visualize exactly what success looks like with this new plan. When working through the problem-solving process, write all the details down. This helps leaders construct action items and delegate them accordingly. Never leave this part of the process empty-handed. Your team needs a clear picture of expectations so they can properly implement the solution. And if everything works, you can use this problem-solving model in the future.

The Best Problem-Solving Strategies and Tools

One of the best ways to discover the root cause of a problem is by utilizing the 5 Whys method. This strategy was developed by Sakichi Toyoda, founder of Toyota Industries. It’s as simple as it sounds. When a problem occurs, ask why it happened five times. In theory, the last answer should get to the heart of the issue.

First Principles Thinking

When one engages in first principles thinking , they end up questioning what everyone just assumes to be true. It effectively removes those assumptions , breaking things down into their most basic elements that are probably true. It’s all about getting to that core foundation of truth and building out from there. Problem-solving skills should always include first principles thinking.

Steve Jobs’ Problem-Solving Method

What to do when a problem feels too big to solve.

Tackling a problem that feels too big to solve requires a can-do, positive mindset. In order to improve your problem-solving, you’ll need to take remember these steps. Imagine what is possible instead of focusing on what seems impossible. As you do so, you’ll become skilled in solving all sorts of problems while also improving your decision-making.

40 problem-solving techniques and processes

All teams and organizations encounter challenges. Approaching those challenges without a structured problem solving process can end up making things worse.

Proven problem solving techniques such as those outlined below can guide your group through a process of identifying problems and challenges , ideating on possible solutions , and then evaluating and implementing the most suitable .

In this post, you'll find problem-solving tools you can use to develop effective solutions. You'll also find some tips for facilitating the problem solving process and solving complex problems.

Design your next session with SessionLab

Join the 150,000+ facilitators 
using SessionLab.

Recommended Articles

A step-by-step guide to planning a workshop, 54 great online tools for workshops and meetings, how to create an unforgettable training session in 8 simple steps.

• 18 Free Facilitation Resources We Think You’ll Love

What is problem solving?

Problem solving is a process of finding and implementing a solution to a challenge or obstacle. In most contexts, this means going through a problem solving process that begins with identifying the issue, exploring its root causes, ideating and refining possible solutions before implementing and measuring the impact of that solution.

For simple or small problems, it can be tempting to skip straight to implementing what you believe is the right solution. The danger with this approach is that without exploring the true causes of the issue, it might just occur again or your chosen solution may cause other issues.

Particularly in the world of work, good problem solving means using data to back up each step of the process, bringing in new perspectives and effectively measuring the impact of your solution.

Effective problem solving can help ensure that your team or organization is well positioned to overcome challenges, be resilient to change and create innovation. In my experience, problem solving is a combination of skillset, mindset and process, and it’s especially vital for leaders to cultivate this skill.

What is the seven step problem solving process?

A problem solving process is a step-by-step framework from going from discovering a problem all the way through to implementing a solution.

With practice, this framework can become intuitive, and innovative companies tend to have a consistent and ongoing ability to discover and tackle challenges when they come up.

You might see everything from a four step problem solving process through to seven steps. While all these processes cover roughly the same ground, I’ve found a seven step problem solving process is helpful for making all key steps legible.

We’ll outline that process here and then follow with techniques you can use to explore and work on that step of the problem solving process with a group.

The seven-step problem solving process is:

1. Problem identification 

The first stage of any problem solving process is to identify the problem(s) you need to solve. This often looks like using group discussions and activities to help a group surface and effectively articulate the challenges they’re facing and wish to resolve.

Be sure to align with your team on the exact definition and nature of the problem you’re solving. An effective process is one where everyone is pulling in the same direction – ensure clarity and alignment now to help avoid misunderstandings later.

2. Problem analysis and refinement

The process of problem analysis means ensuring that the problem you are seeking to solve is  the   right problem . Choosing the right problem to solve means you are on the right path to creating the right solution.

At this stage, you may look deeper at the problem you identified to try and discover the root cause at the level of people or process. You may also spend some time sourcing data, consulting relevant parties and creating and refining a problem statement.

Problem refinement means adjusting scope or focus of the problem you will be aiming to solve based on what comes up during your analysis. As you analyze data sources, you might discover that the root cause means you need to adjust your problem statement. Alternatively, you might find that your original problem statement is too big to be meaningful approached within your current project.

Remember that the goal of any problem refinement is to help set the stage for effective solution development and deployment. Set the right focus and get buy-in from your team here and you’ll be well positioned to move forward with confidence.

3. Solution generation

Once your group has nailed down the particulars of the problem you wish to solve, you want to encourage a free flow of ideas connecting to solving that problem. This can take the form of problem solving games that encourage creative thinking or techniquess designed to produce working prototypes of possible solutions. 

The key to ensuring the success of this stage of the problem solving process is to encourage quick, creative thinking and create an open space where all ideas are considered. The best solutions can often come from unlikely places and by using problem solving techniques that celebrate invention, you might come up with solution gold. 

4. Solution development

No solution is perfect right out of the gate. It’s important to discuss and develop the solutions your group has come up with over the course of following the previous problem solving steps in order to arrive at the best possible solution. Problem solving games used in this stage involve lots of critical thinking, measuring potential effort and impact, and looking at possible solutions analytically. 

During this stage, you will often ask your team to iterate and improve upon your front-running solutions and develop them further. Remember that problem solving strategies always benefit from a multitude of voices and opinions, and not to let ego get involved when it comes to choosing which solutions to develop and take further.

Finding the best solution is the goal of all problem solving workshops and here is the place to ensure that your solution is well thought out, sufficiently robust and fit for purpose. 

5. Decision making and planning

Nearly there! Once you’ve got a set of possible, you’ll need to make a decision on which to implement. This can be a consensus-based group decision or it might be for a leader or major stakeholder to decide. You’ll find a set of effective decision making methods below.

Once your group has reached consensus and selected a solution, there are some additional actions that also need to be decided upon. You’ll want to work on allocating ownership of the project, figure out who will do what, how the success of the solution will be measured and decide the next course of action.

Set clear accountabilities, actions, timeframes, and follow-ups for your chosen solution. Make these decisions and set clear next-steps in the problem solving workshop so that everyone is aligned and you can move forward effectively as a group. 

Ensuring that you plan for the roll-out of a solution is one of the most important problem solving steps. Without adequate planning or oversight, it can prove impossible to measure success or iterate further if the problem was not solved. 

6. Solution implementation 

This is what we were waiting for! All problem solving processes have the end goal of implementing an effective and impactful solution that your group has confidence in.

Project management and communication skills are key here – your solution may need to adjust when out in the wild or you might discover new challenges along the way. For some solutions, you might also implement a test with a small group and monitor results before rolling it out to an entire company.

You should have a clear owner for your solution who will oversee the plans you made together and help ensure they’re put into place. This person will often coordinate the implementation team and set-up processes to measure the efficacy of your solution too.

7. Solution evaluation 

So you and your team developed a great solution to a problem and have a gut feeling it’s been solved. Work done, right? Wrong. All problem solving strategies benefit from evaluation, consideration, and feedback.

You might find that the solution does not work for everyone, might create new problems, or is potentially so successful that you will want to roll it out to larger teams or as part of other initiatives. 

None of that is possible without taking the time to evaluate the success of the solution you developed in your problem solving model and adjust if necessary.

Remember that the problem solving process is often iterative and it can be common to not solve complex issues on the first try. Even when this is the case, you and your team will have generated learning that will be important for future problem solving workshops or in other parts of the organization. 

It’s also worth underlining how important record keeping is throughout the problem solving process. If a solution didn’t work, you need to have the data and records to see why that was the case. If you go back to the drawing board, notes from the previous workshop can help save time.

What does an effective problem solving process look like?

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

The format of a workshop ensures that you can get buy-in from your group, encourage free-thinking and solution exploration before making a decision on what to implement following the session.

This Design Sprint 2.0 template is an effective problem solving process from top agency AJ&Smart. It’s a great format for the entire problem solving process, with four-days of workshops designed to surface issues, explore solutions and even test a solution.

Check it for an example of how you might structure and run a problem solving process and feel free to copy and adjust it your needs!

For a shorter process you can run in a single afternoon, this remote problem solving agenda will guide you effectively in just a couple of hours.

Whatever the length of your workshop, by using 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!

Complete problem-solving methods

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

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.

The Six Thinking Hats   #creative thinking   #meeting facilitation   #problem solving   #issue resolution   #idea generation   #conflict resolution   The Six Thinking Hats are used by individuals and groups to separate out conflicting styles of thinking. They enable and encourage a group of people to think constructively together in exploring and implementing change, rather than using argument to fight over who is right and who is wrong.

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   It doesn’t matter where you work and what your job role is, if you work with other people together as a team, you will always encounter the same challenges: Unclear goals and miscommunication that cause busy work and overtime Unstructured meetings that leave attendants tired, confused and without clear outcomes. Frustration builds up because internal challenges to productivity are not addressed Sudden changes in priorities lead to a loss of focus and momentum Muddled compromise takes the place of clear decision- making, leaving everybody to come up with their own interpretation. In short, a lack of structure leads to a waste of time and effort, projects that drag on for too long and frustrated, burnt out teams. AJ&Smart has worked with some of the most innovative, productive companies in the world. What sets their teams apart from others is not better tools, bigger talent or more beautiful offices. The secret sauce to becoming a more productive, more creative and happier team is simple: Replace all open discussion or brainstorming with a structured process that leads to more ideas, clearer decisions and better outcomes. When a good process provides guardrails and a clear path to follow, it becomes easier to come up with ideas, make decisions and solve problems. This is why AJ&Smart created Lightning Decision Jam (LDJ). It’s a simple and short, but powerful group exercise that can be run either in-person, in the same room, or remotely with distributed teams.

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.

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.

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.

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.

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.

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!

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.

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.

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.

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.

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.

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.

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.

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.

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!

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

Now you have the context and background of the problem you are trying to solving, now comes the time to start ideating and thinking about how you’ll solve the issue.

Here, you’ll want to encourage creative, free thinking and speed. Get as many ideas out as possible and explore different perspectives so you have the raw material for the next step.

Looking at a problem from a new angle can be one of the most effective ways of creating an effective solution. TRIZ is a problem-solving tool that asks the group to consider what they must not do in order to solve a challenge.

By reversing the discussion, new topics and taboo subjects often emerge, allowing the group to think more deeply and create ideas that confront the status quo in a safe and meaningful way. If you’re working on a problem that you’ve tried to solve before, TRIZ is a great problem-solving method to help your team get unblocked.

Making Space with TRIZ   #issue analysis   #liberating structures   #issue resolution   You can clear space for innovation by helping a group let go of what it knows (but rarely admits) limits its success and by inviting creative destruction. TRIZ makes it possible to challenge sacred cows safely and encourages heretical thinking. The question “What must we stop doing to make progress on our deepest purpose?” induces seriously fun yet very courageous conversations. Since laughter often erupts, issues that are otherwise taboo get a chance to be aired and confronted. With creative destruction come opportunities for renewal as local action and innovation rush in to fill the vacuum. Whoosh!

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.

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.

Idea and Concept Development

Brainstorming without structure can quickly become chaotic or frustrating. In a problem-solving context, having an ideation framework to follow can help ensure your team is both creative and disciplined.

In this method, you’ll find an idea generation process that encourages your group to brainstorm effectively before developing their ideas and begin clustering them together. By using concepts such as Yes and…, more is more and postponing judgement, you can create the ideal conditions for brainstorming with ease.

Idea & Concept Development   #hyperisland   #innovation   #idea generation   Ideation and Concept Development is a process for groups to work creatively and collaboratively to generate creative ideas. It’s a general approach that can be adapted and customized to suit many different scenarios. It includes basic principles for idea generation and several steps for groups to work with. It also includes steps for idea selection and development.

Problem-solving techniques for developing and refining 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 develop and refine your ideas in order to bring them closer to a solution that actually solves the problem.

Use these problem-solving techniques when you want to help your team think through their ideas and refine them as part of your problem solving process.

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.

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

Ensuring that everyone in a group is able to contribute to a discussion is vital during any problem solving process. Not only does this ensure all bases are covered, but its then easier to get buy-in and accountability when people have been able to contribute to the process.

1-2-4-All is a tried and tested facilitation technique where participants are asked to first brainstorm on a topic on their own. Next, they discuss and share ideas in a pair before moving into a small group. Those groups are then asked to present the best idea from their discussion to the rest of the team.

This method can be used in many different contexts effectively, though I find it particularly shines in the idea development stage of the process. Giving each participant time to concretize their ideas and develop them in progressively larger groups can create a great space for both innovation and psychological safety.

1-2-4-All   #idea generation   #liberating structures   #issue analysis   With this facilitation technique you can immediately include everyone regardless of how large the group is. You can generate better ideas and more of them faster than ever before. You can tap the know-how and imagination that is distributed widely in places not known in advance. Open, generative conversation unfolds. Ideas and solutions are sifted in rapid fashion. Most importantly, participants own the ideas, so follow-up and implementation is simplified. No buy-in strategies needed! Simple and elegant!

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.

Problem-solving techniques for making decisions and planning

After your group is happy with the possible solutions you’ve developed, now comes the time to choose which to implement. There’s more than one way to make a decision and the best option is often dependant on the needs and set-up of your group.

Sometimes, it’s the case that you’ll want to vote as a group on what is likely to be the most impactful solution. Other times, it might be down to a decision maker or major stakeholder to make the final decision. Whatever your process, here’s some techniques you can use to help you make a decision during your problem solving process.

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.

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.

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.

Straddling the gap between decision making and planning, MoSCoW is a simple and effective method that allows a group team to easily prioritize a set of possible options.

Use this method in a problem solving process by collecting and summarizing all your possible solutions and then categorize them into 4 sections: “Must have”, “Should have”, “Could have”, or “Would like but won‘t get”.

This method is particularly useful when its less about choosing one possible solution and more about prioritorizing which to do first and which may not fit in the scope of your project. In my experience, complex challenges often require multiple small fixes, and this method can be a great way to move from a pile of things you’d all like to do to a structured plan.

MoSCoW   #define intentions   #create   #design   #action   #remote-friendly   MoSCoW is a method that allows the team to prioritize the different features that they will work on. Features are then categorized into “Must have”, “Should have”, “Could have”, or “Would like but won‘t get”. To be used at the beginning of a timeslot (for example during Sprint planning) and when planning is needed.

When it comes to managing the rollout of a solution, clarity and accountability are key factors in ensuring the success of the project. The RAACI chart is a simple but effective model for setting roles and responsibilities as part of a planning session.

Start by listing each person involved in the project and put them into the following groups in order to make it clear who is responsible for what during the rollout of your solution.

• Responsibility  (Which person and/or team will be taking action?)
• Authority  (At what “point” must the responsible person check in before going further?)
• Accountability  (Who must the responsible person check in with?)
• Consultation  (Who must be consulted by the responsible person before decisions are made?)
• Information  (Who must be informed of decisions, once made?)

Ensure this information is easily accessible and use it to inform who does what and who is looped into discussions and kept up to date.

RAACI   #roles and responsibility   #teamwork   #project management   Clarifying roles and responsibilities, levels of autonomy/latitude in decision making, and levels of engagement among diverse stakeholders.

Problem-solving warm-up activities

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

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.

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.

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.

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.

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.

Closing activities for a problem-solving process

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

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.

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.

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.

Tips for 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.

Create psychologically safe spaces for discussion

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 tough for people to stand up and contribute if the problems or challenges are emotive or personal in nature. Try and create a psychologically safe space for these kinds of discussions and where possible, create regular opportunities for challenges to be brought up organically.

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!

Save time and effort creating an effective problem solving process

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

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

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

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

Over to you

The problem-solving process can often be as complicated and multifaceted as the problems they are set-up to solve. With the right problem-solving techniques and a mix of 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! 

James Smart is Head of Content at SessionLab. He’s also a creative facilitator who has run workshops and designed courses for establishments like the National Centre for Writing, UK. He especially enjoys working with young people and empowering others in their creative practice.

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

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

Leave a Comment Cancel reply

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

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

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

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

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Sign up for free

How to master the seven-step problem-solving process

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

Podcast transcript

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

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

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

Hugo Sarrazin: Our pleasure.

Charles Conn: It’s terrific to be here.

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

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

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

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

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

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

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

Want to subscribe to The McKinsey Podcast ?

Simon London: So this is a concise problem statement.

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

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

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

Hugo Sarrazin: Yeah.

Charles Conn: And in the wrong direction.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Both: Yeah.

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

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

Simon London: Right. Right.

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

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

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

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

Simon London: Would you agree with that?

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

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

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

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

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

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

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

Charles Conn: Yeah.

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

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

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

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

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

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

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

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

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

Hugo Sarrazin: Every step of the process.

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

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

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

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

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

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

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

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

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

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

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

Hugo Sarrazin: Absolutely.

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

Want better strategies? Become a bulletproof problem solver

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

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

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

Hugo Sarrazin: It was a pleasure. Thank you.

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

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

Explore a career with us

Related articles.

Strategy to beat the odds

Five routes to more innovative problem solving

• Coaching Skills Training
• Coaching TIPS²™
• Continuous Improvement Coaching
• Courageous Conversations Workshop
• Executive Coaching Program
• Feedback 360
• Safety Coaching
• Sales Coaching Training Program
• Free Consultation
• Applied Strategic Thinking®
• Strategic Leadership Course
• Strategic Teaming
• Strategy Development Processes and Services
• Communication Training for Managers
• Conflict and Collaboration
• Confronting Racism Workshop
• Delegation & Accountability
• Diversity, Equity, and Inclusion Workshop
• Flexible Leadership
• Leading Change
• Leading Groups to Solutions
• Leading Innovation
• Mid-Level Management Training
• Qualities of Leadership
• Bottom Line Leadership
• Customized Leadership Development Programs
• Leadership Development Program Design
• Mini-MBA & Operational Finance
• Problem Solving and Decision Making in the Workplace
• Transition to Leadership
• Virtual Leadership
• High-Performance Teamwork
• Leadership Team Alignment Workshop
• Orienteering
• Corporate Outdoor Training and Team Building
• Retreats for Teams
• Innovation Skills Training
• Personal Impact Workshop
• Supervisor Training Programs
• Customization of CMOE’s Learning Library
• Full Curriculum Development and Design
• Learning & Development Advisory Services
• Bottom Line Leadership Training
• Consulting Services
• Leadership Retreats
• Learning and Development Consulting Services
• Needs Analysis and Organization Assessments
• Transformation & Change Solutions
• Facilitator Training Workshop
• Empathic Leadership
• Supervisor Development Series
• All Courses
• Digital Learning
• Books and Publications
• Assessments and Surveys
• Clients Served
• History and Experience
• Meet the CMOE Team
• Testimonials
• Articles & Tools
• Scenario Templates
• Certified Partners
• Event Resources
• Industry Insights
• Resource Library
• Video Library
• News and Events
• Professional Accreditation and Continuing Education Units
• Surveys & Assessments

Managers Must Be Effective Problem-Solvers

One of a manager’s most important responsibilities is to solve problems.  Finding the answers to difficult questions that are sometimes a source of great perplexity and distress for the organization often falls to an organization’s leaders.

Here’s the deal:

A company’s success depends on managerial problem-solvers . Issues arrive in all sizes, ranging from daily nuisances to organizational crises.

Managers who have the ability to systematically think through the facts, diagnose the situation, and find an accurate and workable solution will help the business thrive and prosper.

Effective problem-solvers are able to guide teams towards the achievement of goals by eliminating frustration, confusion, and misunderstandings before they become unmanageable.

They build cooperation and collaboration between individuals, eliminate the need for rework, and foster continuous improvement.

The best managers can often sense problems with keen insight.

They may notice a deviation from standard team performance , such as a missed deadline or an unmet sales goal—and when the team’s plans go off the rails, these managers automatically begin the problem-solving process.

1. Identify and Define the Problem

Alert managers constantly watch for signals, symptoms, and signs that problems may exist. Once they see a potential issue, they think through whether this is a problem they can solve and whether it will make a critical impact on the team or organization.

Once the problem has been defined as a priority, they create a clear, quantitative problem statement and describe the situation in specific, objective terms without making assumptions or jumping to conclusions.

2. Analyze the Problem

The best problem-solvers analyze patterns and ask questions about what, who, when, where, and how much the problem has affected the business.

They are able to isolate and define the root cause of the issue so that once it’s been resolved, it’s unlikely to recur.

3. Develop Solutions

While problems sometimes come with easy answers, managerial problem-solving cannot be impulsive, risking the mistake of making snap decisions.

Instead, they use techniques like brainstorming ideas, creating prioritized lists, and evaluating the time, cost, and technology involved to assess the situation and design a long-term solution.

4. Plan and Act

Once the best solution has been identified, a good manager develops a solid implementation plan. This plan should include steps that will be taken to move forward, as well as contingency plans that will help the manager handle potential roadblocks.

He or she must also secure the commitment of others, mobilize them to act, and hold them accountable for their responsibilities.

The managerial problem-solving process is a never-ending cycle of planning, doing, checking, and acting, while also monitoring the situation and the outcomes. As needed, managers make adjustments to their plans so that the team can continue to move towards the solution that will lead them to better business results .

Recommended For You:

Leadership development workshops, get exclusive content delivered straight to your inbox.

When you subscribe to our blog and become a CMOE Insider.

And the best part?

It's 100% free.

As Featured In:

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

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

What Are Problem-Solving Skills? Definition and Examples

• Share on Twitter Share on Twitter
• Share on Facebook Share on Facebook
• Share on LinkedIn Share on LinkedIn

Forage puts students first. Our blog articles are written independently by our editorial team. They have not been paid for or sponsored by our partners. See our full  editorial guidelines .

Why do employers hire employees? To help them solve problems. Whether you’re a financial analyst deciding where to invest your firm’s money, or a marketer trying to figure out which channel to direct your efforts, companies hire people to help them find solutions. Problem-solving is an essential and marketable soft skill in the workplace. 

So, how can you improve your problem-solving and show employers you have this valuable skill? In this guide, we’ll cover:

Problem-Solving Skills Definition

Why are problem-solving skills important, problem-solving skills examples, how to include problem-solving skills in a job application, how to improve problem-solving skills, problem-solving: the bottom line.

Problem-solving skills are the ability to identify problems, brainstorm and analyze answers, and implement the best solutions. An employee with good problem-solving skills is both a self-starter and a collaborative teammate; they are proactive in understanding the root of a problem and work with others to consider a wide range of solutions before deciding how to move forward. 

Examples of using problem-solving skills in the workplace include:

• Researching patterns to understand why revenue decreased last quarter
• Experimenting with a new marketing channel to increase website sign-ups
• Brainstorming content types to share with potential customers
• Testing calls to action to see which ones drive the most product sales
• Implementing a new workflow to automate a team process and increase productivity

Problem-solving skills are the most sought-after soft skill of 2022. In fact, 86% of employers look for problem-solving skills on student resumes, according to the National Association of Colleges and Employers Job Outlook 2022 survey . 

It’s unsurprising why employers are looking for this skill: companies will always need people to help them find solutions to their problems. Someone proactive and successful at problem-solving is valuable to any team.

“Employers are looking for employees who can make decisions independently, especially with the prevalence of remote/hybrid work and the need to communicate asynchronously,” Eric Mochnacz, senior HR consultant at Red Clover, says. “Employers want to see individuals who can make well-informed decisions that mitigate risk, and they can do so without suffering from analysis paralysis.”

Showcase new skills

Build the confidence and practical skills that employers are looking for with Forage’s free job simulations.

Problem-solving includes three main parts: identifying the problem, analyzing possible solutions, and deciding on the best course of action.

>>MORE: Discover the right career for you based on your skills with a career aptitude test .

Research is the first step of problem-solving because it helps you understand the context of a problem. Researching a problem enables you to learn why the problem is happening. For example, is revenue down because of a new sales tactic? Or because of seasonality? Is there a problem with who the sales team is reaching out to? 

Research broadens your scope to all possible reasons why the problem could be happening. Then once you figure it out, it helps you narrow your scope to start solving it. 

Analysis is the next step of problem-solving. Now that you’ve identified the problem, analytical skills help you look at what potential solutions there might be.

“The goal of analysis isn’t to solve a problem, actually — it’s to better understand it because that’s where the real solution will be found,” Gretchen Skalka, owner of Career Insights Consulting, says. “Looking at a problem through the lens of impartiality is the only way to get a true understanding of it from all angles.”

Decision-Making

Once you’ve figured out where the problem is coming from and what solutions are, it’s time to decide on the best way to go forth. Decision-making skills help you determine what resources are available, what a feasible action plan entails, and what solution is likely to lead to success.

On a Resume

Employers looking for problem-solving skills might include the word “problem-solving” or other synonyms like “ critical thinking ” or “analytical skills” in the job description.

“I would add ‘buzzwords’ you can find from the job descriptions or LinkedIn endorsements section to filter into your resume to comply with the ATS,” Matthew Warzel, CPRW resume writer, advises. Warzel recommends including these skills on your resume but warns to “leave the soft skills as adjectives in the summary section. That is the only place soft skills should be mentioned.”

On the other hand, you can list hard skills separately in a skills section on your resume .

Forage Resume Writing Masterclass

Learn how to showcase your skills and craft an award-winning resume with this free masterclass from Forage.

Avg. Time: 5 to 6 hours

Skills you’ll build: Resume writing, professional brand, professional summary, narrative, transferable skills, industry keywords, illustrating your impact, standing out

In a Cover Letter or an Interview

Explaining your problem-solving skills in an interview can seem daunting. You’re required to expand on your process — how you identified a problem, analyzed potential solutions, and made a choice. As long as you can explain your approach, it’s okay if that solution didn’t come from a professional work experience.

“Young professionals shortchange themselves by thinking only paid-for solutions matter to employers,” Skalka says. “People at the genesis of their careers don’t have a wealth of professional experience to pull from, but they do have relevant experience to share.”

Aaron Case, career counselor and CPRW at Resume Genius, agrees and encourages early professionals to share this skill. “If you don’t have any relevant work experience yet, you can still highlight your problem-solving skills in your cover letter,” he says. “Just showcase examples of problems you solved while completing your degree, working at internships, or volunteering. You can even pull examples from completely unrelated part-time jobs, as long as you make it clear how your problem-solving ability transfers to your new line of work.”

Learn How to Identify Problems

Problem-solving doesn’t just require finding solutions to problems that are already there. It’s also about being proactive when something isn’t working as you hoped it would. Practice questioning and getting curious about processes and activities in your everyday life. What could you improve? What would you do if you had more resources for this process? If you had fewer? Challenge yourself to challenge the world around you.

Think Digitally

“Employers in the modern workplace value digital problem-solving skills, like being able to find a technology solution to a traditional issue,” Case says. “For example, when I first started working as a marketing writer, my department didn’t have the budget to hire a professional voice actor for marketing video voiceovers. But I found a perfect solution to the problem with an AI voiceover service that cost a fraction of the price of an actor.”

Being comfortable with new technology — even ones you haven’t used before — is a valuable skill in an increasingly hybrid and remote world. Don’t be afraid to research new and innovative technologies to help automate processes or find a more efficient technological solution.

Collaborate

Problem-solving isn’t done in a silo, and it shouldn’t be. Use your collaboration skills to gather multiple perspectives, help eliminate bias, and listen to alternative solutions. Ask others where they think the problem is coming from and what solutions would help them with your workflow. From there, try to compromise on a solution that can benefit everyone.

If we’ve learned anything from the past few years, it’s that the world of work is constantly changing — which means it’s crucial to know how to adapt . Be comfortable narrowing down a solution, then changing your direction when a colleague provides a new piece of information. Challenge yourself to get out of your comfort zone, whether with your personal routine or trying a new system at work.

Put Yourself in the Middle of Tough Moments

Just like adapting requires you to challenge your routine and tradition, good problem-solving requires you to put yourself in challenging situations — especially ones where you don’t have relevant experience or expertise to find a solution. Because you won’t know how to tackle the problem, you’ll learn new problem-solving skills and how to navigate new challenges. Ask your manager or a peer if you can help them work on a complicated problem, and be proactive about asking them questions along the way.

Career Aptitude Test

What careers are right for you based on your skills? Take this quiz to find out. It’s completely free — you’ll just need to sign up to get your results!

Step 1 of 3

Companies always need people to help them find solutions — especially proactive employees who have practical analytical skills and can collaborate to decide the best way to move forward. Whether or not you have experience solving problems in a professional workplace, illustrate your problem-solving skills by describing your research, analysis, and decision-making process — and make it clear that you’re the solution to the employer’s current problems. 

Image Credit: Christina Morillo / Pexels 

Related Posts

6 negotiation skills to level up your work life, how to build conflict resolution skills: case studies and examples, what is github uses and getting started, upskill with forage.

Build career skills recruiters are looking for.

• Product overview
• All features
• Latest feature release
• App integrations

CAPABILITIES

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

Featured Reads

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

Problem management: 8 steps to better problem solving

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

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

What is problem management?

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

The goals of problem management are to:

Prevent problems before they start.

Solve for repetitive errors.

Lessen each incident’s impact. 

Problem management vs. incident management 

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

Problem management vs. problem solving

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

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

Problem management vs. change management 

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

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

Problem management vs. project management

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

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

The 8 steps of problem management

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

1. Identify the problem

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

2. Diagnose the cause

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

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

What factors or conditions led to the incident?

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

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

3. Organize and prioritize

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

What needs to be done? 

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

When does each piece need to be completed?

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

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

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

How should you plan for this in the future?

4. Create a workaround

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

5. Update your known error database

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

6. Pause for change management (if necessary)

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

7. Solve the problem

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

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

8. Reflect on the process

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

5 benefits of problem management

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

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

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

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

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

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

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

Problem management leads to better, faster solutions

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

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

Related resources

15 creative elevator pitch examples for every scenario

How Asana streamlines strategic planning with work management

How to create a CRM strategy: 6 steps (with examples)

What is management by objectives (MBO)?

The Problem Manager Role: Skills, Responsibilities, and Best Practices

Ever wondered why the same IT issues keep cropping up, disrupting your business operations? How do companies identify and fix these recurring problems for good?

In this article, we'll explore the crucial role of a problem manager , the responsibilities they hold, and the best practices they employ to ensure IT services run smoothly.

What skills are essential for a problem manager? How do they overcome common challenges? And what tools do they rely on? Keep reading to uncover the answers to these questions.

What is Problem Management?

Problem Management is a systematic approach to managing the lifecycle of all problems encountered during IT service delivery. Unlike Incident management, which focuses on restoring services as quickly as possible, Problem Management aims to identify and resolve the root causes of recurring issues and find permanent solutions.

It is a critical aspect of IT Service Management (ITSM) , alongside other essential processes such as Incident Management, Change Management , and Service Request Management . The ITIL (Information Technology Infrastructure Library) framework is widely adopted for guiding ITSM practices, including Problem Management.

Incident Management vs Problem Management: Definition & Differences

Roles and responsibilities of a problem manager.

The Problem Manager's role is to ensure the reliability and continuity of IT services. Their primary responsibility is to address the root causes of recurring incidents, preventing them from recurring and affecting business operations.

Key responsibilities:

Root cause analysis : Conduct thorough investigations to identify the underlying causes of recurring incidents. This involves analyzing incident data, reviewing system logs, and collaborating with technical teams to pinpoint the source of problems.

Coordination and collaboration: Work closely with various teams, including IT support, development, and operations, to gather information, tools, and expertise needed to resolve problems. Effective coordination ensures that all relevant stakeholders are involved in the problem-solving process.

Implementation of solutions: Develop and implement permanent solutions to address identified root causes. This may involve deploying software patches, updating configurations, or redesigning processes to prevent future incidents.

Continuous improvemen t: Monitor the effectiveness of implemented solutions and make necessary adjustments. Continuously seek ways to improve Problem Management processes and reduce the occurrence of incidents.

Root Cause Analysis (RCA), Explained

Skills and qualifications of a problem manager.

A Problem Manager needs a combination of problem-solving abilities, technical and analytical skills, and good communication:

Technical proficiency: A deep understanding of the organization's IT infrastructure is crucial. Problem managers must be familiar with the various components, systems, and technologies used within the organization to diagnose and resolve issues effectively.

Problem-solving abilities: Creativity, critical thinking, and persistence are vital for identifying and resolving complex problems. Problem managers should be able to think outside the box and explore innovative solutions to recurring issues.

Analytical skills: The ability to analyze real-time metrics and data is essential for spotting trends, drawing insights, and identifying root causes. Problem managers should be comfortable working with data and using analytical tools to support their investigations.

Effective communication: Strong communication skills are necessary for relaying information to technical teams, vendors, users, and other stakeholders. Problem managers must be able to explain complex technical issues in a clear manner, ensuring that everyone involved understands the situation and the proposed solutions.

Unlocking Career Progression

Discover the strategies to lifelong learning and evolvement in IT

Proactive Problem Management strategies

Proactive Problem Management involves analyzing data to identify trends or significant problems before they escalate. This preventive approach minimizes the impact of incidents and improves overall service reliability. Problem managers work closely with incident management, Change Management, and other service teams to develop and implement solutions.

Tools and software for Problem Management

Problem managers need a diverse toolkit tailored to address the multifaceted challenges of IT Problem Management. Essential tools include:

Problem Management module: Integrates with other key modules such as incident management and change management to provide a cohesive approach to problem resolution.

Configuration Management Database (CMDB) : Helps understand dependencies and interrelationships between different components within the IT infrastructure.

Known Error Database (KEDB): Facilitates quick resolution by providing information on known errors and their workarounds.

8 Steps to Build a Solid Problem Management Process

Measuring problem management effectiveness.

Key performance metrics for evaluating Problem Management effectiveness include:

Percentage of problems with identified root cause:  Measures the success of diagnosing issues.

Percentage of problems with permanent solution or workaround: Indicates the effectiveness of implementing resolutions.

Proficiency in evaluating risks: Assesses the ability to prioritize fixes based on business impact and urgency.

Problem managers should also calculate the return on investment (ROI) for their work to demonstrate value and prioritize problem fixes according to business needs.

Career development and training for Problem Managers

Problem Management offers a lucrative and rewarding career path . A bachelor's degree in business, computer science, or a related technical field is typically required, along with 2 to 4 years of experience in Problem Management or related roles. Essential skills include business acumen, leadership, and analytical abilities.

Overcoming common challenges in Problem Management

Problem Management is essential for maintaining the stability of IT services, but it comes with its own set of challenges. Let's dive into some common obstacles and how problem managers can effectively address them.

Lack of data and metrics

Without adequate data, identifying problems and their root causes becomes challenging. Consider a scenario where a company's website experiences intermittent outages. Without detailed logs and performance metrics, pinpointing the exact cause—whether it's a server issue, a network problem, or a software bug—can be nearly impossible.

How to address it: Problem Managers should implement comprehensive monitoring and logging tools. They can analyze trends and detect anomalies by collecting detailed data on system performance, user activity, and error occurrences.

Misalignment with business goals

When Problem Management efforts are not aligned with business objectives, prioritization can suffer. Imagine a situation where a problem manager is focused on resolving a low-impact bug in an internal tool while a critical customer-facing application faces repeated outages. This misalignment can lead to wasted resources and increased customer dissatisfaction.

How to Address It: Problem Managers should regularly communicate with business leaders to understand their priorities and objectives. Regular meetings and reporting can help align the Problem Management team with the broader business strategy.

Lack of leadership support

Without strong support from leadership, Problem Managers may struggle to secure the resources and authority needed to address issues effectively. For instance, if a problem manager identifies that outdated hardware is causing frequent server crashes but doesn't get approval for an upgrade, the problem will persist.

How to address it:  The problem manager must know how to build a compelling case for the importance of their work and highlight the potential business impact of unresolved problems. This includes demonstrating the cost of downtime, the risk to customer satisfaction, and potential compliance issues.

Insufficient skills and resources

Building a strong Problem Management process will require a blend of technical expertise, analytical skills, and sufficient manpower. A team lacking in these areas may find it challenging to diagnose and resolve problems efficiently.

How to address it: Investing in continuous training and development for the Problem Management team is crucial. Providing opportunities for skill enhancement through courses, certifications, and hands-on experience ensures the team remains capable and up-to-date with the latest technologies. Additionally, ensuring adequate staffing levels and access to necessary tools and resources can significantly enhance problem-solving capabilities.

The role of a problem manager is crucial for maintaining reliable IT services. By identifying and resolving root causes of recurring issues, problem managers help prevent future incidents, ensuring smoother operations across the organization.

Key takeaways:

Core responsibilities: Conduct root cause analyses, coordinate with various teams, and implement lasting solutions.

Skills needed: Technical expertise, problem-solving abilities, analytical skills, and effective communication.

Challenges: Lack of data, misalignment with business goals, insufficient support, and limited resources. These can be addressed by improving data collection, clear communication with leadership, and continuous team training.

Problem Management isn't just about fixing issues—it's about creating a proactive culture that anticipates and prevents problems. One way of doing this is by following ITIL's best practices; it can help you align your Problem Management processes with industry standards and organizational goals.

You can dive deeper into ITIL and explore related practices like Incident Management and Change Management to see how they work together to create a more reliable and efficient IT environment.

For those eager to enhance their ITSM knowledge, the ITIL practices offer a great starting point to help you master Problem Management and other essential practices.

Read other articles like this : Problem Management

Read other articles like this:

Evaluate invgate as your itsm solution, 30-day free trial - no credit card needed.

What is problem solving and why is it important

By Wayne Stottler , Kepner-Tregoe

• Problem Solving & Decision Making Over time, developing and refining problem solving skills provides the ability to solve increasingly complex problems Learn More

For over 60 years, Kepner-Tregoe has been helping companies across industries and geographies to develop and mature their problem-solving capabilities through KT’s industry leading approach to training and the implementation of best practice processes. Considering that problem solving is a part of almost every person’s daily life (both at home and in the workplace), it is surprising how often we are asked to explain what problem solving is and why it is important.

Problem solving is at the core of human evolution. It is the methods we use to understand what is happening in our environment, identify things we want to change and then figure out the things that need to be done to create the desired outcome. Problem solving is the source of all new inventions, social and cultural evolution, and the basis for market based economies. It is the basis for continuous improvement, communication and learning.

If this problem-solving thing is so important to daily life, what is it?

Problem-solving is the process of observing what is going on in your environment; identifying things that could be changed or improved; diagnosing why the current state is the way it is and the factors and forces that influence it; developing approaches and alternatives to influence change; making decisions about which alternative to select; taking action to implement the changes; and observing impact of those actions in the environment.

Each step in the problem-solving process employs skills and methods that contribute to the overall effectiveness of influencing change and determine the level of problem complexity that can be addressed. Humans learn how to solve simple problems from a very early age (learning to eat, make coordinated movements and communicate) – and as a person goes through life problem-solving skills are refined, matured and become more sophisticated (enabling them to solve more difficult problems).

Problem-solving is important both to individuals and organizations because it enables us to exert control over our environment.

Fixing things that are broken

Some things wear out and break over time, others are flawed from day-1. Personal and business environments are full of things, activities, interactions and processes that are broken or not operating in the way they are desired to work. Problem-solving gives us a mechanism for identifying these things, figuring out why they are broken and determining a course of action to fix them.

Addressing risk

Humans have learned to identify trends and developed an awareness of cause-and-effect relationships in their environment. These skills not only enable us to fix things when they break but also anticipate what may happen in the future (based on past-experience and current events). Problem-solving can be applied to the anticipated future events and used to enable action in the present to influence the likelihood of the event occurring and/or alter the impact if the event does occur.

Improving performance

Individuals and organizations do not exist in isolation in the environment. There is a complex and ever-changing web of relationships that exist and as a result, the actions of one person will often have either a direct impact on others or an indirect impact by changing the environment dynamics. These interdependencies enable humans to work together to solve more complex problems but they also create a force that requires everyone to continuously improve performance to adapt to improvements by others. Problem-solving helps us understand relationships and implement the changes and improvements needed to compete and survive in a continually changing environment.

Seizing opportunity

Problem solving isn’t just about responding to (and fixing) the environment that exists today. It is also about innovating, creating new things and changing the environment to be more desirable. Problem-solving enables us to identify and exploit opportunities in the environment and exert (some level of) control over the future.

Problem solving skills and the problem-solving process are a critical part of daily life both as individuals and organizations. Developing and refining these skills through training, practice and learning can provide the ability to solve problems more effectively and over time address problems with a greater degree of complexity and difficulty. View KT’s Problem Solving workshop known to be the gold standard for over 60 years.

We are experts in:

For inquiries, details, or a proposal!

Subscribe to the KT Newsletter

What can we help you with?

Problem solving

Regular task for project managers.

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

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

  More Like This

• Project management
• Project manager
• Project management system

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

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

• Roles & Responsibilities
• Get Problem management kit

IT problem management

Everything you need to know about effective problem management

• Try ServiceDesk Plus now
• Start my free trial

What is IT problem management?

Incident management vs. problem management

• Choosing between reactive and proactive problem management approaches

What are the benefits of IT problem management?

It problem management roles and responsibilities, problem identification, problem control, error control.

• The relationship between the ITSM processes and problem management
• Brainstorming
• Kepner-Tregoe method
• Ishikawa analysis, or fishbone diagram analysis
• Pareto analysis
• Five whys technique
• Other techniques
• IT Problem management best practices
• IT Problem management key performance indicators
• The best features for problem management software

The Comprehensive Guide to IT Problem Management is a six-part series that aims to help readers understand the multiple facets of problem management in an IT environment .

This guide delves into the various approaches of problem management, as well as the processes behind them, and provides practical examples to help you properly prepare for your problem management journey.

A problem is the cause or potential cause of multiple incidents. Problems can arise from major incidents affecting many users, or from recurring incidents. Further, problems can be identified in infrastructure diagnostic systems before users are affected.

Incidents hinder business productivity, and providing quick solutions helps ensure seamless continuity of business operations. However, when multiple incidents occur at once or the same incident occurs multiple times, it's not feasible to move forward by providing patchwork solutions, or offering the same resolutions over and over again.

IT problem management is a procedural way to ensure minimal incidents emerge from IT infrastructure operations by delving deep into incidents to find the root causes and fixes, and also reduce the severity of the incidents through suitable documentation of existing issues and providing workarounds.

Problem management is a methodical approach to identify the cause of an incident and manage the life cycle of all problems. The goal of IT problem management process is to minimize the impact of incidents and eliminate recurring ones. While there are no hard and fast rules to perform problem management, here are three common phases you can follow in your approach:

These phases will be discussed in detail later in the guide.

Reactive management deals with incidents that are currently affecting users, whereas proactive problem management addresses issues that could potentially surface as incidents in the future should they be left alone.

A sound problem management process has the potential to significantly reduce the influx of incident tickets, saving IT service desk staff significant time and effort. This advantage ripples into other benefits such as reduction in mean time to repair (MTTR) , higher customer satisfaction, a robust known error database , and reduced cost of IT services and issues. Moreover, an organization that practices proactive problem management is likely to find tremendous value from identifying and eliminating issues before they disrupt business processes .

Problem management as an ITSM practice is most useful when used with other ITSM practices in the overall service value chain. Information is exchanged between the various ITSM practices, namely incident management, change management , IT asset management , knowledge management , and continual service improvement. This information exchanged between parties accumulates value as it moves through each ITSM practice, in turn building an ideal ITSM engine in your enterprise .

Before going further, the following definitions will be useful in understanding the context of this guide.

• Workaround : Temporary solutions that restore services and ensure business continuity. A workaround reduces the impact of an incident or problem.
• Root cause analysis (RCA) : The root cause is the problem's underlying issue. RCA is the investigation techniques that help discover the root cause of a problem.
• Known error : Problems that have occurred before and have a workaround or known root causes.
• Known error database (KEDB) : A database created by documenting the known errors using incident management and problem management.

In this guide, we'll examine each facet of problem management in detail, providing all the knowledge you need to get up to speed on how to implement problem management in your enterprise.

There are a few hurdles organizations might encounter in the process of establishing problem management. The organization might not have the resources to allocate for a problem management team, or it may already have an unorthodox way of managing problems and is reluctant to change. Sometimes, it could just be a cost-related denial of request.

Consequently, it's vital to include all stakeholders in the problem management process, and express how it provides value to different facets of the organization. These benefits include:

• Eliminates the faults in an organization's services through suitable documentation.
• Refines the service design by identifying and solving weak points, ensuring the most effective and efficient path for service delivery.
• Increases the first time fix rate on service failures by providing permanent solutions to incidents rather than stopping at workarounds.
• Diminishes the impact of incidents affecting multiple users, or a single user at a crucial time.
• Prevents most of the incidents and problems plaguing an organization over time, boosting user productivity.
• Strengthens the confidence users have in the organization's IT services.
• Decreases the time it takes to recover from failures through systematic maintenance of a KEDB.
• Prevents recurring incidents through one-time fixes, sparing valuable service desk efforts in resolving them.
• Encourages IT services to mature as the organization develops by the learning from the resolved problems.
• Develops IT talent within the organization through technical awareness and valuable insights.

Take the first step in your problem management journey

• Try ServiceDesk Plus

The roles of a problem management team are directly related to the organizational structure that is present. The organization's age, culture, technology, and number of locations worldwide affect the composition of its problem management team. In the case of small IT organizations, the team's responsibilities might all be combined, or in the case of large, multinational corporations, they may be specialized.

Either way, it's up to the convenience and flexibility of the IT team to tailor an arrangement that ensures problems are efficiently addressed in alignment with industry-standard best practices. Being aware of the organization's general strategy is a good starting point to initiate the team formation. Also, it's important to be wary of the resources the organization is ready to expel for the development of a problem management team.

The team's roles and responsibilities should extend, diverge, and mature as the organization's technology grows, otherwise confusions in accountability can arise during service delivery.

The general roles and responsibilities of problem management teams are listed below.

IT Problem management process flow

Just like an organization creates value for its customers, IT service management creates value for its users through best practices , and indirectly aids in creating value for the organization. To create this value, there must be a process with defined inputs and outputs. When an effective service desk is put in place, the streamlined flow of a problem process looks like this:

You can implement problem management processes with any technology you deem the right fit for your organization. The technology put in place should have functionalities that enable the three phases of IT problem management.

The three phases are:

The problem identification phase identifies and records problems in a management tool. A service desk tool associated with multiple practices of service management, including incident management, asset management , the CMDB , and change management , gives organizations an advantage in this phase.

While the service desk staff would normally report problems based on a surge of incidents, a proactive approach to problem management identifies problems by:

• Analyzing incident trends, leveraging network monitoring systems, and utilizing other diagnostic software.
• Detecting risks from incidents that might recur.
• Evaluating information received from partners and suppliers.
• Evaluating information from internal software developers, engineers, and test teams.

Depending on your organization's structure, domain, and culture, there could be even more modes through which problems can be identified. Nevertheless, it's important to have a system in place for problems to be brought in, identified, prioritized, and recorded for further investigation and diagnosis.

Problem management is a collaborative effort, so for results to be effective, multiple departments and stakeholders should be involved in the problem control phase.

Problem control includes activities like prioritization, investigation, analysis, and documenting known errors and workarounds. There are numerous techniques that help in prioritization and analysis of problems. A good rule of thumb to follow is first tackling problems that, when solved, significantly curb the disruption of services in the organization.

Feasibility is another aspect to note when tackling problems. Fixing a problem permanently might require more resources than settling for a workaround. A quick cost-benefit analysis can determine whether you should proceed with a permanent fix or not.

Workarounds are documented in problem records. Generally, if a problem persists longer, implementing a quick workaround is advisable. This workaround can even be a part of incident management resolution; however, the problem management team should review the workaround and refine the resolution if necessary. As you can see, an effective incident workaround can become a permanent solution to some problems.

This phase manages known errors from the KEDB by regularly checking it for possible permanent fixes if they pass the cost-benefit analysis.

Once a problem is analyzed, it's documented as a known error. These known errors are regularly reassessed to account for the impact they create, and to test the effectiveness of workarounds.

Now with a clear understanding of problem management’s role in an IT environment, we will next compare and contrast problem management with its supporting ITSM 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 feature checklist

IT incident management handbook

Frequently asked questions:

1. what is an example of problem management.

Problem management tackles the root cause of recurring incidents. Imagine a ERP system where users frequently report login issues. Problem management would investigate these incidents, analyzing error logs and user access reports. By identifying a common cause, like a software bug, they can implement a permanent fix, preventing a wave of future tickets and improving overall system stability. Some other common examples include: investigating recurring login issues, analyzing application errors, and identifying slow network performance.

2. What are the 3 phases of problem management?

Problem management in ITSM typically follows a three-phase approach:

• Problem detection and identification: This phase involves recognizing recurring incidents and identifying them as a potential underlying problem. This can involve analyzing trends in incident reports, user feedback, or proactive monitoring tools.
• Investigation and diagnosis: Once a problem is identified, the team delves deeper to understand its root cause. This might involve analyzing logs, replicating the issue, or consulting technical expertise.
• Resolution and closure: The final phase focuses on implementing a permanent fix to address the root cause. This could involve developing a workaround, applying a software patch, or recommending hardware upgrades. The problem record is then closed once the fix is verified and the issue is no longer recurring.

3. What is the role of a problem manager in IT?

The role of a problem manager in IT involves ensuring the long-term stability and efficiency of IT services by identifying and addressing the root causes of recurring incidents. This is accomplished through the analysis of data, thorough the investigation of issues, and close collaboration with technical teams to implement permanent solutions.

•   Live Demo
•   Compare
•   Get quote

How it works

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

Explore how BetterUp connects to your core business systems.

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

Build leaders that accelerate team performance and engagement.

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

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

Transform your business, starting with your sales leaders.

Unlock business impact from the top with executive coaching.

Foster a culture of inclusion and belonging.

Accelerate the performance and potential of your agencies and employees.

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

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

Daring Leadership Institute: a groundbreaking partnership that amplifies Brené Brown's empirically based, courage-building curriculum with BetterUp’s human transformation platform.

• What is coaching?

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

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

Types of Coaching

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

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

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

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

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

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

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

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

• BetterUp Briefing

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

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

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

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

Join us and create impactful change.

Read the buzz about BetterUp.

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

For Business

For Individuals

31 examples of problem solving performance review phrases

Jump to section

You're doing great

You should think of improving

Tips to improve

Use these practical examples of phrases, sample comments, and templates for your performance review , 360-degree feedback survey, or manager appraisal.

The following examples not only relate to problem-solving but also conflict management , effective solutions, selecting the best alternatives, decision making , problem identification, analyzing effectively, and generally becoming an effective problem-solving strategist. Start using effective performance review questions to help better guide your workforce's development. 

Problem solving appraisal comments: you're doing great

• You always maintain an effective dialogue with clients when they have technical problems. Being clear and articulate makes sure our customers' faults are attended to promptly.
• You constantly make sure to look beyond the obvious you never stop at the first answer. You’re really good at exploring alternatives. Well done!
• Keeping the supervisors and managers informed of status changes and requests is important. You’re really good at communicating the changes to the projects at all times. Keep it up!
• You stay cool and collected even when things aren’t going according to plan or up in the air. This is a great trait to possess. Well done!
• You’re excellent at giving an honest and logical analysis. Keep it up! Effectively diagnosing complex problems and reaching sustainable solutions is one of your strong points.
• Your ability to ability to make complex systems into simple ones is truly a unique skill to possess. Well done!
• You often identify practical solutions to every roadblock. You’re a real asset to the team! Great job.
• You always listen actively and attentively to make sure you understand what the exact problem is and you come up with solutions in an effective manner.
• You have an amazing ability to clearly explain options and solutions effectively and efficiently. Well done!
• When driving projects, you can shift to other areas comfortably and easily. making sure the project runs smoothly. Great job!

Problem solving performance review phrases: you should think of improving

• You always seem too overwhelmed when faced with multiple problems. Try to think of ways to make problems more manageable so that they can be solved in a timely and effective manner.
• Avoiding conflicts constantly with people is not a good idea as you will only build up personal frustration and nothing will be done to remedy the situation. Try to face people when there are problems and rectify problems when they occur.
• Don’t allow demanding customers to rattle your cage too much. If they become too demanding, take a step back, regulate your emotions , and try to make use of online support tools to help you rectify problems these tools can help a lot!
• It’s necessary that you learn from your past mistakes . You cannot keep making the same mistakes , as this is not beneficial to the company.
• You tend to ask the same questions over and over again. Try to listen more attentively or take notes when colleagues are answering!
• Providing multiple solutions in an indirect and creative approach will allow you to be more effective at problem-solving . if you struggle with this typically through viewing the problem in a new and unusual light.
• You fail to provide staff with the appropriate amount of structure and direction. They must know the direction you wish them to go in to achieve their goals .
• You need to be able to recognize repetitive trends to solve problems promptly.
• You tend to have problems troubleshooting even the most basic of questions. As a problem solver and customer support person, it’s imperative that you can answer these questions easily.
• Read through your training manual and make sure you fully understand it before attempting questions again.

Performance review tips to improve problem solving

• Try to complain less about problems and come up with solutions to the problems more often. Complaining is not beneficial to progression and innovation.
• As a problem solver, it’s important to be able to handle multiple priorities under short deadlines.
• You need to be able to effectively distinguish between the cause and the symptoms of problems to solve them in an efficient and timely manner.
• Try to anticipate problems in advance before they become major roadblocks down the road.
• Try to view obstacles as opportunities to learn and thrive at the challenge of solving the problem.
• Remember to prioritize problems according to their degree of urgency. It's important that you spend the majority of your time on urgent tasks over menial ones.
• When putting plans into place, stick to them and make sure they are completed.
• When solving problems, try to allocate appropriate levels of resources when undertaking new projects. It is important to become as efficient and as effective as possible.
• Try to learn to pace yourself when solving problems to avoid burnout . You’re a great asset to the team and we cannot afford to lose at this point.
• Meeting regularly with your staff to review results is vital to the problem-solving process.
• Staff that has regular check-ins understand what it is that is required of them, what they are currently achieving, and areas they may need to improve. Try to hold one-on-one meetings every week.

Enhance your problem-solving skills

Discover personalized coaching to navigate challenges effectively and boost your performance.

Madeline Miles

Madeline is a writer, communicator, and storyteller who is passionate about using words to help drive positive change. She holds a bachelor's in English Creative Writing and Communication Studies and lives in Denver, Colorado. In her spare time, she's usually somewhere outside (preferably in the mountains) — and enjoys poetry and fiction.

How a performance review template improves the feedback process

25 performance review questions (and how to use them), agile performance management: how to improve an agile team, 53 performance review examples to boost growth, 5 tactics for managing managers effectively — and why it matters, managers have a strong effect on team performance, for better or worse, how stanford executive education embraces vulnerability as a form of resilience, awakening human potential: developing people and driving performance in the new world of work, uk leaders develop future-minded skills with betterup, 10 problem-solving strategies to turn challenges on their head, teamwork skills self-appraisal comments: 40 example phrases, your complete guide to self-assessments (with examples), 30 communication feedback examples, 30 customer service review examples to develop your team, 15 tips for your end-of-year reviews, 37 innovation and creativity appraisal comments, 8 creative solutions to your most challenging problems, stay connected with betterup, get our newsletter, event invites, plus product insights and research..

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

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

ITSM for high-velocity teams

What is problem management.

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

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

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

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

The relationship between problem management and other key ITIL processes

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

Problem management vs. incident management

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

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

Problem management and change management

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

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

Problem management and knowledge management

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

Problem management and service request management

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

What are the benefits of problem management?

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

Decrease time to resolution

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

Avoid costly incidents

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

Increase productivity

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

Empower your team to find and learn from underlying causes

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

Promote continuous service improvement 

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

Increase customer satisfaction

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

The problem management process

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

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

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

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

Problem management best practices and tips

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

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

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

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

Problem management tips

Avoid relying on reactive, root-cause analysis.

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

Encourage an open environment where problems are shared

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

Focus on critical services

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

Ask questions and use the ‘5 whys’

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

Spread the knowledge

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

Become a learning organization

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

Track follow-up

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

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

Want to learn about problem management in Jira Service Management?

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

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

What is IT change management? Definition, benefits and types

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

Instagantt Standalone

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

Instagantt for Asana

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

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

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

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

What is problem solving?

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

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

The basic steps involved in problem-solving.

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

Defining the problem.

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

·       Flowcharts of the process and the problem init.

·       Cause and effect diagram.

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

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

Generating the alternatives.

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

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

·       Take ideas from different employees.

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

·       Think of other than one effective idea.

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

Evaluating and selecting alternatives.

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

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

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

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

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

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

Implementing the solutions.

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

·      Involving others.

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

·      Testing and expectations of the solution.

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

·      Feedback system.

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

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

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

Knowing your problem in a good way:

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

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

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

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

Knowing about the complexity of the problem.

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

·       Affinity diagrams.

·       Swim Lane diagram.

·       System diagram.

·       Flow charts.

·       Bottleneck method.

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

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

Process of solving the problem.

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

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

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

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

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

Based on 10.000+ reviews on

Make a Gantt Chart Online Now

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

Ready to simplify your project management?