methods of administrative problem solving

Become A Certified World Class Assistant in 2024

Problem Solving for Administrative and Executive Assistants

• May 24, 2024

Problem-solving is a critical skill that we use on a daily basis, whether it’s dealing with a small issue like a printer jam or tackling a larger problem such as a major business crisis. While there are many methods people use to solve problems, such as mind mapping or brainstorming, having a structured process can be especially helpful when facing more complex issues.

By following a series of steps in a logical order, you can increase your chances of finding the right solution and successfully resolving the problem. In this blog, we’ll outline a few steps to problem-solving and provide tips and best practices for each stage of the process.

Stage I: Recognition

Recognition is about being aware and cognizant that a problem exists. This can also be something like an administrative process you use that no longer works. Here are the steps to take in this stage:

1. Identify the Problem or Issue

Being open to the possibility that a problem exists is the first step. Sometimes we may be so used to a certain way of doing things that we don’t realize there’s a better solution out there. It’s important to be vigilant and observant, noting any inefficiencies or recurring issues that could indicate a deeper problem.

2. Clearly State the Problem or Issue

Clearly stating the problem in a way that is specific and measurable helps everyone involved understand the issue more clearly. For example, instead of saying, “The office is always in chaos,” you could state, “There is a lack of a standardized procedure for managing incoming and outgoing correspondence, resulting in lost documents and delayed responses.”

3. Gather as Much Background Information as Possible

Gathering comprehensive background information is essential to understand the problem fully. This includes:

• Talking to Others : Engage with colleagues and stakeholders who may have experienced the problem. Their insights can provide valuable context.
• Researching Online : Look for similar issues and how they have been resolved in other organizations.
• Reviewing Data and Documents : Examine relevant data, reports, and documents to gather evidence and pinpoint patterns or trends.

4. List Negative Effects

Documenting the negative effects of the problem can help illustrate its impact and urgency. This might include:

• Decreased Productivity : Highlight how the problem slows down processes or creates bottlenecks.
• Employee Morale : Note any frustration or dissatisfaction among staff due to the issue.
• Financial Costs : Calculate any direct or indirect financial impacts, such as increased operational costs or lost revenue.

5. Assemble Relevant Information

Once you’ve gathered background information and identified negative effects, it’s time to assemble all relevant information in a structured format. This could include:

• Data and Statistics : Compile quantitative data that supports the existence and impact of the problem.
• Stakeholder Feedback : Summarize qualitative feedback from discussions and interviews.
• Document Analysis : Include key points from reviewed documents and reports.

6. Write Five to Ten Possible Solutions

Brainstorming a list of potential solutions without evaluating them yet ensures a broad range of options. Encourage creative thinking and consider various approaches, even unconventional ones. For example:

• Implementing New Software : Consider technology solutions that could automate or streamline problematic processes.
• Training and Development : Identify if additional training for staff could mitigate the problem.
• Process Redesign : Think about redesigning workflows or procedures to eliminate inefficiencies.

By thoroughly recognizing and defining the problem, gathering comprehensive background information, and brainstorming potential solutions, you’ll be well-prepared to move on to the next stage of the problem-solving process.

Stage II: Identify the Solution

Brainstorming a list of possible solutions is a crucial step. At this stage, focus on generating as many ideas as possible without evaluating them yet. This ensures a broad range of options to consider later. Once you have a comprehensive list, it’s time to analyze each potential solution by considering its positive and negative outcomes. Here’s how to approach this:

7. List the Positive or Negative Outcomes of Each Possible Solution

Evaluate the positive outcomes:

• Effectiveness : How well does this solution address the root cause of the problem?
• Efficiency : Will this solution streamline processes and save time or resources?
• Employee Morale : Could this solution improve team satisfaction and morale?
• Cost Savings : Will implementing this solution reduce costs in the long run?

Evaluate the negative outcomes:

• Implementation Challenges : What are the potential difficulties in implementing this solution?
• Cost : What are the initial costs associated with this solution? Is it financially viable?
• Time : How long will it take to implement this solution? Is it a short-term or long-term fix?
• Resistance to Change : Are there potential hurdles in getting buy-in from stakeholders or employees?

8. Select the Best One

After listing and evaluating the potential solutions, it’s time to select the one that seems to have the most potential for success and addresses the root cause of the problem. Follow these steps:

Narrow down options by eliminating solutions that have more negative outcomes or are not feasible within your current constraints. Prioritize solutions that address the core issues effectively and have manageable implementation challenges.

Criteria for selection should include:

• Alignment with Goals : Ensure the solution aligns with organizational goals and objectives.
• Feasibility : Consider if the solution is practical and can be realistically implemented with the available resources.
• Impact : Choose a solution that will have a significant positive impact on resolving the problem.
• Stakeholder Support : Opt for a solution that has or can gain the support of key stakeholders and team members.

Utilize decision-making frameworks like the Eisenhower Matrix, which helps in prioritizing tasks based on urgency and importance. Tools like SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) can provide a structured way to evaluate the options.

Make a decision on the best solution after thorough discussion and consensus among the decision-makers. Document the rationale behind the chosen solution to ensure transparency and accountability.

By systematically evaluating the positive and negative outcomes of each potential solution and selecting the one that best addresses the root cause, you increase the likelihood of effectively resolving the problem. This structured approach helps in making informed decisions that are aligned with organizational goals and resources.

Stage III: Implementation

9. consider how you will present this information.

Effectively communicating  the chosen solution is crucial to its successful implementation. First, determine who needs to know about the solution, including team members, managers, stakeholders, or external partners. Next, decide on the best format for communication based on the audience and the complexity of the solution. This could be a verbal presentation, a written report, an email, or a detailed document. Use clear and concise language to explain the solution, avoiding jargon or overly technical terms unless necessary. Ensure the message is structured logically, covering the problem, the solution, and the expected outcomes. Consider the best timing for delivering the message, ensuring it does not coincide with busy periods or other major announcements that might overshadow it.

10. Implement Your Idea

Once the solution has been communicated, it’s time to put it into action. Develop a detailed action plan outlining the steps needed to implement the solution, and assign specific tasks and responsibilities to team members to ensure clarity and accountability. If the solution involves changing existing processes or systems, ensure these changes are well-documented and communicated to everyone involved. Provide necessary training or resources to help team members adapt to the new processes. Set up a system to monitor the progress of the implementation, which could include regular check-ins, progress reports, or using project management tools like Trello, Asana, or Monday.com.

11. Evaluate the Outcome

After implementing the solution, it’s essential to evaluate its effectiveness. Define clear metrics or KPIs (Key Performance Indicators) to measure the success of the solution, such as improved productivity, reduced costs, or higher employee satisfaction. Collect feedback from those affected by the solution to gain insights into its effectiveness and any issues that might have arisen. Compare the actual outcomes with the expected outcomes, identifying any discrepancies and analyzing the reasons behind them.

12. Adjust as Necessary and Try Again

If the solution has not been fully effective, adjustments may be necessary. Identify any issues or barriers that prevented the solution from being successful and modify the solution based on the feedback and analysis. This might involve tweaking the approach, changing certain processes, or addressing any unforeseen challenges. Implement the adjusted solution and monitor its progress again.

13. If Necessary, Try a Different Solution

If the initial solution and adjustments still do not resolve the problem, it might be necessary to try a different solution. Revisit the list of potential solutions generated in Stage II and select another promising option. Follow the implementation steps for the new solution, ensuring thorough communication, monitoring, and evaluation. Remember that problem-solving is an iterative process, and continuous improvement and learning from each attempt are key to finding the right solution.

Problem-solving is an ongoing and dynamic process that requires a structured approach. By recognizing the problem, identifying viable solutions, and carefully implementing them, you can effectively tackle various challenges in the workplace. Following these steps ensures a thorough and systematic approach to resolving issues, leading to better outcomes and continuous improvement.

Embrace these methods in your daily work to enhance your problem-solving skills. Stay proactive, keep learning, and leverage Office Dynamics’ resources to excel in your role. Explore our training programs and professional development resources to further refine your abilities and stay ahead in your career.

Like this article? Share it!

Read similar posts.

• Admin Assistant Training , Problem Solving

Company Information

• Office Dynamics International
• 5575 South Durango Dr. Suite 106 Las Vegas, NV 89113
• 800-STAR-139
• 8 a.m. – 5:00 p.m. Pacific Time

Site Navigation

Stay connected.

• Submit a Contact Form
• View Upcoming Assistant Events
• Receive Webinar Updates
• Monday Motivators

RECOMMENDed training

• Conference for Administrative Excellence
• Digital Efficiency for Administrative Excellence
• Executive Support Series™
• Star Achievement Series®
• World Class Assistant™

QUICK FIND ASSISTANT & EXECUTIVE RESOURCES

© office dynamics international 2024.

Privacy Policy | Terms of Use

Privacy Overview

Join our administrative community.

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

Learn Creative Problem Solving Techniques to Stimulate Innovation in Your Organization

By Kate Eby | October 20, 2017 (updated August 27, 2021)

• Share on Facebook
• Share on LinkedIn

Link copied

In today’s competitive business landscape, organizations need processes in place to make strong, well-informed, and innovative decisions. Problem solving - in particular creative problem solving (CPS) - is a key skill in learning how to accurately identify problems and their causes, generate potential solutions, and evaluate all the possibilities to arrive at a strong corrective course of action. Every team in any organization, regardless of department or industry, needs to be effective, creative, and quick when solving problems. 

In this article, we’ll discuss traditional and creative problem solving, and define the steps, best practices, and common barriers associated. After that, we’ll provide helpful methods and tools to identify the cause(s) of problematic situations, so you can get to the root of the issue and start to generate solutions. Then, we offer nearly 20 creative problem solving techniques to implement at your organization, or even in your personal life. Along the way, experts weigh in on the importance of problem solving, and offer tips and tricks. 

What Is Problem Solving and Decision Making?

Problem solving is the process of working through every aspect of an issue or challenge to reach a solution. Decision making is choosing one of multiple proposed solutions  — therefore, this process also includes defining and evaluating all potential options. Decision making is often one step of the problem solving process, but the two concepts are distinct. 

Collective problem solving is problem solving that includes many different parties and bridges the knowledge of different groups. Collective problem solving is common in business problem solving because workplace decisions typically affect more than one person. 

Problem solving, especially in business, is a complicated science. Not only are business conflicts multifaceted, but they often involve different personalities, levels of authority, and group dynamics. In recent years, however, there has been a rise in psychology-driven problem solving techniques, especially for the workplace. In fact, the psychology of how people solve problems is now studied formally in academic disciplines such as psychology and cognitive science.

Joe Carella is the Assistant Dean for Executive Education at the University of Arizona . Joe has over 20 years of experience in helping executives and corporations in managing change and developing successful business strategies. His doctoral research and executive education engagements have seen him focus on corporate strategy, decision making and business performance with a variety of corporate clients including Hershey’s, Chevron, Fender Musical Instruments Corporation, Intel, DP World, Essilor, BBVA Compass Bank.

He explains some of the basic psychology behind problem solving: “When our brain is engaged in the process of solving problems, it is engaged in a series of steps where it processes and organizes the information it receives while developing new knowledge it uses in future steps. Creativity is embedded in this process by incorporating diverse inputs and/or new ways of organizing the information received.”

Laura MacLeod is a Professor of Social Group Work at City University of New York, and the creator of From The Inside Out Project® , a program that coaches managers in team leadership for a variety of workplaces. She has a background in social work and over two decades of experience as a union worker, and currently leads talks on conflict resolution, problem solving, and listening skills at conferences across the country. 

MacLeod thinks of problem solving as an integral practice of successful organizations. “Problem solving is a collaborative process — all voices are heard and connected, and resolution is reached by the group,” she says. “Problems and conflicts occur in all groups and teams in the workplace, but if leaders involve everyone in working through, they will foster cohesion, engagement, and buy in. Everybody wins.”

10 tips that will make you more productive.

Uncover the top three factors that are killing your productivity and 10 tips to help you overcome them.

Download the free e-book to overcome my productivity killers

Project Management Guide

Your one-stop shop for everything project management

Ready to get more out of your project management efforts? Visit our comprehensive project management guide for tips, best practices, and free resources to manage your work more effectively.

View the guide

What Is the First Step in Solving a Problem?

Although problem solving techniques vary procedurally, experts agree that the first step in solving a problem is defining the problem. Without a clear articulation of the problem at stake, it is impossible to analyze all the key factors and actors, generate possible solutions, and then evaluate them to pick the best option. 

Dr. Elliott Jaffa is a behavioral and management psychologist with over 25 years of problem solving training and management experience. “Start with defining the problem you want to solve,” he says, “And then define where you want to be, what you want to come away with.” He emphasizes these are the first steps in creating an actionable, clear solution. 

Bryan Mattimore is Co-Founder of Growth Engine, an 18-year old innovation agency based in Norwalk, CT. Bryan has facilitated over 1,000 ideation sessions and managed over 200 successful innovation projects leading to over $3 billion in new sales. His newest book is 21 Days to a Big Idea . When asked about the first critical component to successful problem solving, Mattimore says, “Defining the challenge correctly, or ‘solving the right problem’ … The three creative techniques we use to help our clients ‘identify the right problem to be solved’ are questioning assumptions, 20 questions, and problem redefinition. A good example of this was a new product challenge from a client to help them ‘invent a new iron. We got them to redefine the challenge as first: a) inventing new anti-wrinkle devices, and then b) inventing new garment care devices.”

What Are Problem Solving Skills?

To understand the necessary skills in problem solving, you should first understand the types of thinking often associated with strong decision making. Most problem solving techniques look for a balance between the following binaries:

• Convergent vs. Divergent Thinking: Convergent thinking is bringing together disparate information or ideas to determine a single best answer or solution. This thinking style values logic, speed, and accuracy, and leaves no chance for ambiguity. Divergent thinking is focused on generating new ideas to identify and evaluate multiple possible solutions, often uniting ideas in unexpected combinations. Divergent thinking is characterized by creativity, complexity, curiosity, flexibility, originality, and risk-taking.
• Pragmatics vs. Semantics: Pragmatics refer to the logic of the problem at hand, and semantics is how you interpret the problem to solve it. Both are important to yield the best possible solution.
• Mathematical vs. Personal Problem Solving: Mathematical problem solving involves logic (usually leading to a single correct answer), and is useful for problems that involve numbers or require an objective, clear-cut solution. However, many workplace problems also require personal problem solving, which includes interpersonal, collaborative, and emotional intuition and skills. 

The following basic methods are fundamental problem solving concepts. Implement them to help balance the above thinking models.

• Reproductive Thinking: Reproductive thinking uses past experience to solve a problem. However, be careful not to rely too heavily on past solutions, and to evaluate current problems individually, with their own factors and parameters. 
• Idea Generation: The process of generating many possible courses of action to identify a solution. This is most commonly a team exercise because putting everyone’s ideas on the table will yield the greatest number of potential solutions. 

However, many of the most critical problem solving skills are “soft” skills: personal and interpersonal understanding, intuitiveness, and strong listening. 

Mattimore expands on this idea: “The seven key skills to be an effective creative problem solver that I detail in my book Idea Stormers: How to Lead and Inspire Creative Breakthroughs are: 1) curiosity 2) openness 3) a willingness to embrace ambiguity 4) the ability to identify and transfer principles across categories and disciplines 5) the desire to search for integrity in ideas, 6) the ability to trust and exercise “knowingness” and 7) the ability to envision new worlds (think Dr. Seuss, Star Wars, Hunger Games, Harry Potter, etc.).”

“As an individual contributor to problem solving it is important to exercise our curiosity, questioning, and visioning abilities,” advises Carella. “As a facilitator it is essential to allow for diverse ideas to emerge, be able to synthesize and ‘translate’ other people’s thinking, and build an extensive network of available resources.”

MacLeod says the following interpersonal skills are necessary to effectively facilitate group problem solving: “The abilities to invite participation (hear all voices, encourage silent members), not take sides, manage dynamics between the monopolizer, the scapegoat, and the bully, and deal with conflict (not avoiding it or shutting down).” 

Furthermore, Jaffa explains that the skills of a strong problem solver aren’t measurable. The best way to become a creative problem solver, he says, is to do regular creative exercises that keep you sharp and force you to think outside the box. Carella echoes this sentiment: “Neuroscience tells us that creativity comes from creating novel neural paths. Allow a few minutes each day to exercise your brain with novel techniques and brain ‘tricks’ – read something new, drive to work via a different route, count backwards, smell a new fragrance, etc.”

What Is Creative Problem Solving? History, Evolution, and Core Principles

Creative problem solving (CPS) is a method of problem solving in which you approach a problem or challenge in an imaginative, innovative way. The goal of CPS is to come up with innovative solutions, make a decision, and take action quickly. Sidney Parnes and Alex Osborn are credited with developing the creative problem solving process in the 1950s. The concept was further studied and developed at SUNY Buffalo State and the Creative Education Foundation. 

The core principles of CPS include the following:

• Balance divergent and convergent thinking
• Ask problems as questions
• Defer or suspend judgement
• Focus on “Yes, and…” rather than “No, but…”

According to Carella, “Creative problem solving is the mental process used for generating innovative and imaginative ideas as a solution to a problem or a challenge. Creative problem solving techniques can be pursued by individuals or groups.”

When asked to define CPS, Jaffa explains that it is, by nature, difficult to create boundaries for. “Creative problem solving is not cut and dry,” he says, “If you ask 100 different people the definition of creative problem solving, you’ll get 100 different responses - it’s a non-entity.”

Business presents a unique need for creative problem solving. Especially in today’s competitive landscape, organizations need to iterate quickly, innovate with intention, and constantly be at the cutting-edge of creativity and new ideas to succeed. Developing CPS skills among your workforce not only enables you to make faster, stronger in-the-moment decisions, but also inspires a culture of collaborative work and knowledge sharing. When people work together to generate multiple novel ideas and evaluate solutions, they are also more likely to arrive at an effective decision, which will improve business processes and reduce waste over time. In fact, CPS is so important that some companies now list creative problem solving skills as a job criteria.

MacLeod reiterates the vitality of creative problem solving in the workplace. “Problem solving is crucial for all groups and teams,” she says. “Leaders need to know how to guide the process, hear all voices and involve all members - it’s not easy.”

“This mental process [of CPS] is especially helpful in work environments where individuals and teams continuously struggle with new problems and challenges posed by their continuously changing environment,” adds Carella. 

Problem Solving Best Practices

By nature, creative problem solving does not have a clear-cut set of do’s and don’ts. Rather, creating a culture of strong creative problem solvers requires flexibility, adaptation, and interpersonal skills. However, there are a several best practices that you should incorporate:

• Use a Systematic Approach: Regardless of the technique you use, choose a systematic method that satisfies your workplace conditions and constraints (time, resources, budget, etc.). Although you want to preserve creativity and openness to new ideas, maintaining a structured approach to the process will help you stay organized and focused. 
• View Problems as Opportunities: Rather than focusing on the negatives or giving up when you encounter barriers, treat problems as opportunities to enact positive change on the situation. In fact, some experts even recommend defining problems as opportunities, to remain proactive and positive.
• Change Perspective: Remember that there are multiple ways to solve any problem. If you feel stuck, changing perspective can help generate fresh ideas. A perspective change might entail seeking advice of a mentor or expert, understanding the context of a situation, or taking a break and returning to the problem later. “A sterile or familiar environment can stifle new thinking and new perspectives,” says Carella. “Make sure you get out to draw inspiration from spaces and people out of your usual reach.”
• Break Down Silos: To invite the greatest possible number of perspectives to any problem, encourage teams to work cross-departmentally. This not only combines diverse expertise, but also creates a more trusting and collaborative environment, which is essential to effective CPS. According to Carella, “Big challenges are always best tackled by a group of people rather than left to a single individual. Make sure you create a space where the team can concentrate and convene.”
• Employ Strong Leadership or a Facilitator: Some companies choose to hire an external facilitator that teaches problem solving techniques, best practices, and practicums to stimulate creative problem solving. But, internal managers and staff can also oversee these activities. Regardless of whether the facilitator is internal or external, choose a strong leader who will value others’ ideas and make space for creative solutions.  Mattimore has specific advice regarding the role of a facilitator: “When facilitating, get the group to name a promising idea (it will crystalize the idea and make it more memorable), and facilitate deeper rather than broader. Push for not only ideas, but how an idea might specifically work, some of its possible benefits, who and when would be interested in an idea, etc. This fleshing-out process with a group will generate fewer ideas, but at the end of the day will yield more useful concepts that might be profitably pursued.” Additionally, Carella says that “Executives and managers don’t necessarily have to be creative problem solvers, but need to make sure that their teams are equipped with the right tools and resources to make this happen. Also they need to be able to foster an environment where failing fast is accepted and celebrated.”
• Evaluate Your Current Processes: This practice can help you unlock bottlenecks, and also identify gaps in your data and information management, both of which are common roots of business problems.

MacLeod offers the following additional advice, “Always get the facts. Don’t jump too quickly to a solution – working through [problems] takes time and patience.”

Mattimore also stresses that how you introduce creative problem solving is important. “Do not start by introducing a new company-wide innovation process,” he says. “Instead, encourage smaller teams to pursue specific creative projects, and then build a process from the ground up by emulating these smaller teams’ successful approaches. We say: ‘You don’t innovate by changing the culture, you change the culture by innovating.’”

Barriers to Effective Problem Solving

Learning how to effectively solve problems is difficult and takes time and continual adaptation. There are several common barriers to successful CPS, including:

• Confirmation Bias: The tendency to only search for or interpret information that confirms a person’s existing ideas. People misinterpret or disregard data that doesn’t align with their beliefs.
• Mental Set: People’s inclination to solve problems using the same tactics they have used to solve problems in the past. While this can sometimes be a useful strategy (see Analogical Thinking in a later section), it often limits inventiveness and creativity.
• Functional Fixedness: This is another form of narrow thinking, where people become “stuck” thinking in a certain way and are unable to be flexible or change perspective.
• Unnecessary Constraints: When people are overwhelmed with a problem, they can invent and impose additional limits on solution avenues. To avoid doing this, maintain a structured, level-headed approach to evaluating causes, effects, and potential solutions.
• Groupthink: Be wary of the tendency for group members to agree with each other — this might be out of conflict avoidance, path of least resistance, or fear of speaking up. While this agreeableness might make meetings run smoothly, it can actually stunt creativity and idea generation, therefore limiting the success of your chosen solution.
• Irrelevant Information: The tendency to pile on multiple problems and factors that may not even be related to the challenge at hand. This can cloud the team’s ability to find direct, targeted solutions.
• Paradigm Blindness: This is found in people who are unwilling to adapt or change their worldview, outlook on a particular problem, or typical way of processing information. This can erode the effectiveness of problem solving techniques because they are not aware of the narrowness of their thinking, and therefore cannot think or act outside of their comfort zone.

According to Jaffa, the primary barrier of effective problem solving is rigidity. “The most common things people say are, ‘We’ve never done it before,’ or ‘We’ve always done it this way.’” While these feelings are natural, Jaffa explains that this rigid thinking actually precludes teams from identifying creative, inventive solutions that result in the greatest benefit.

“The biggest barrier to creative problem solving is a lack of awareness – and commitment to – training employees in state-of-the-art creative problem-solving techniques,” Mattimore explains. “We teach our clients how to use ideation techniques (as many as two-dozen different creative thinking techniques) to help them generate more and better ideas. Ideation techniques use specific and customized stimuli, or ‘thought triggers’ to inspire new thinking and new ideas.” 

MacLeod adds that ineffective or rushed leadership is another common culprit. “We're always in a rush to fix quickly,” she says. “Sometimes leaders just solve problems themselves, making unilateral decisions to save time. But the investment is well worth it — leaders will have less on their plates if they can teach and eventually trust the team to resolve. Teams feel empowered and engagement and investment increases.”

Strategies for Problem Cause Identification

As discussed, most experts agree that the first and most crucial step in problem solving is defining the problem. Once you’ve done this, however, it may not be appropriate to move straight to the solution phase. Rather, it is often helpful to identify the cause(s) of the problem: This will better inform your solution planning and execution, and help ensure that you don’t fall victim to the same challenges in the future. 

Below are some of the most common strategies for identifying the cause of a problem:

• Root Cause Analysis: This method helps identify the most critical cause of a problem. A factor is considered a root cause if removing it prevents the problem from recurring. Performing a root cause analysis is a 12 step process that includes: define the problem, gather data on the factors contributing to the problem, group the factors based on shared characteristics, and create a cause-and-effect timeline to determine the root cause. After that, you identify and evaluate corrective actions to eliminate the root cause.

‌ Download Fishbone Diagram Template - Excel

Download 5 Whys Template   Excel  |  Word  |  PDF   

Problem Solving Techniques and Strategies

In this section, we’ll explain several traditional and creative problem solving methods that you can use to identify challenges, create actionable goals, and resolve problems as they arise. Although there is often procedural and objective crossover among techniques, they are grouped by theme so you can identify which method works best for your organization.

Divergent Creative Problem Solving Techniques

Brainstorming: One of the most common methods of divergent thinking, brainstorming works best in an open group setting where everyone is encouraged to share their creative ideas. The goal is to generate as many ideas as possible – you analyze, critique, and evaluate the ideas only after the brainstorming session is complete. To learn more specific brainstorming techniques, read this article . 

Mind Mapping: This is a visual thinking tool where you graphically depict concepts and their relation to one another. You can use mind mapping to structure the information you have, analyze and synthesize it, and generate solutions and new ideas from there. The goal of a mind map is to simplify complicated problems so you can more clearly identify solutions.

Appreciative Inquiry (AI): The basic assumption of AI is that “an organization is a mystery to be embraced.” Using this principle, AI takes a positive, inquisitive approach to identifying the problem, analyzing the causes, and presenting possible solutions. The five principles of AI emphasize dialogue, deliberate language and outlook, and social bonding. 

Lateral Thinking: This is an indirect problem solving approach centered on the momentum of idea generation. As opposed to critical thinking, where people value ideas based on their truth and the absence of errors, lateral thinking values the “movement value” of new ideas: This means that you reward team members for producing a large volume of new ideas rapidly. With this approach, you’ll generate many new ideas before approving or rejecting any.

Problem Solving Techniques to Change Perspective

Constructive Controversy: This is a structured approach to group decision making to preserve critical thinking and disagreement while maintaining order. After defining the problem and presenting multiple courses of action, the group divides into small advocacy teams who research, analyze, and refute a particular option. Once each advocacy team has presented its best-case scenario, the group has a discussion (advocacy teams still defend their presented idea). Arguing and playing devil’s advocate is encouraged to reach an understanding of the pros and cons of each option. Next, advocacy teams abandon their cause and evaluate the options openly until they reach a consensus. All team members formally commit to the decision, regardless of whether they advocated for it at the beginning. You can learn more about the goals and steps in constructive controversy here . 

Carella is a fan of this approach. “Create constructive controversy by having two teams argue the pros and cons of a certain idea,” he says. “It forces unconscious biases to surface and gives space for new ideas to formulate.”

Abstraction: In this method, you apply the problem to a fictional model of the current situation. Mapping an issue to an abstract situation can shed extraneous or irrelevant factors, and reveal places where you are overlooking obvious solutions or becoming bogged down by circumstances. 

Analogical Thinking: Also called analogical reasoning , this method relies on an analogy: using information from one problem to solve another problem (these separate problems are called domains). It can be difficult for teams to create analogies among unrelated problems, but it is a strong technique to help you identify repeated issues, zoom out and change perspective, and prevent the problems from occurring in the future. .

CATWOE: This framework ensures that you evaluate the perspectives of those whom your decision will impact. The factors and questions to consider include (which combine to make the acronym CATWOE):

• Customers: Who is on the receiving end of your decisions? What problem do they currently have, and how will they react to your proposed solution?
• Actors: Who is acting to bring your solution to fruition? How will they respond and be affected by your decision?
• Transformation Process: What processes will you employ to transform your current situation and meet your goals? What are the inputs and outputs?
• World View: What is the larger context of your proposed solution? What is the larger, big-picture problem you are addressing?
• Owner: Who actually owns the process? How might they influence your proposed solution (positively or negatively), and how can you influence them to help you?
• Environmental Constraints: What are the limits (environmental, resource- and budget-wise, ethical, legal, etc.) on your ideas? How will you revise or work around these constraints?

Complex Problem Solving

Soft Systems Methodology (SSM): For extremely complex problems, SSM can help you identify how factors interact, and determine the best course of action. SSM was borne out of organizational process modeling and general systems theory, which hold that everything is part of a greater, interconnected system: This idea works well for “hard” problems (where logic and a single correct answer are prioritized), and less so for “soft” problems (i.e., human problems where factors such as personality, emotions, and hierarchy come into play). Therefore, SSM defines a seven step process for problem solving: 

• Begin with the problem or problematic situation 
• Express the problem or situation and build a rich picture of the themes of the problem 
• Identify the root causes of the problem (most commonly with CATWOE)
• Build conceptual models of human activity surrounding the problem or situation
• Compare models with real-world happenings
• Identify changes to the situation that are both feasible and desirable
• Take action to implement changes and improve the problematic situation

SSM can be used for any complex soft problem, and is also a useful tool in change management . 

Failure Mode and Effects Analysis (FMEA): This method helps teams anticipate potential problems and take steps to mitigate them. Use FMEA when you are designing (redesigning) a complex function, process, product, or service. First, identify the failure modes, which are the possible ways that a project could fail. Then, perform an effects analysis to understand the consequences of each of the potential downfalls. This exercise is useful for internalizing the severity of each potential failure and its effects so you can make adjustments or safeties in your plan. 

‌ Download FMEA Template  

Problem Solving Based on Data or Logic (Heuristic Methods)

TRIZ: A Russian-developed problem solving technique that values logic, analysis, and forecasting over intuition or soft reasoning. TRIZ (translated to “theory of inventive problem solving” or TIPS in English) is a systematic approach to defining and identifying an inventive solution to difficult problems. The method offers several strategies for arriving at an inventive solution, including a contradictions matrix to assess trade-offs among solutions, a Su-Field analysis which uses formulas to describe a system by its structure, and ARIZ (algorithm of inventive problem solving) which uses algorithms to find inventive solutions. 

Inductive Reasoning: A logical method that uses evidence to conclude that a certain answer is probable (this is opposed to deductive reasoning, where the answer is assumed to be true). Inductive reasoning uses a limited number of observations to make useful, logical conclusions (for example, the Scientific Method is an extreme example of inductive reasoning). However, this method doesn’t always map well to human problems in the workplace — in these instances, managers should employ intuitive inductive reasoning , which allows for more automatic, implicit conclusions so that work can progress. This, of course, retains the principle that these intuitive conclusions are not necessarily the one and only correct answer. 

Process-Oriented Problem Solving Methods

Plan Do Check Act (PDCA): This is an iterative management technique used to ensure continual improvement of products or processes. First, teams plan (establish objectives to meet desired end results), then do (implement the plan, new processes, or produce the output), then check (compare expected with actual results), and finally act (define how the organization will act in the future, based on the performance and knowledge gained in the previous three steps). 

Means-End Analysis (MEA): The MEA strategy is to reduce the difference between the current (problematic) state and the goal state. To do so, teams compile information on the multiple factors that contribute to the disparity between the current and goal states. Then they try to change or eliminate the factors one by one, beginning with the factor responsible for the greatest difference in current and goal state. By systematically tackling the multiple factors that cause disparity between the problem and desired outcome, teams can better focus energy and control each step of the process. 

Hurson’s Productive Thinking Model: This technique was developed by Tim Hurson, and is detailed in his 2007 book Think Better: An Innovator’s Guide to Productive Thinking . The model outlines six steps that are meant to give structure while maintaining creativity and critical thinking: 1) Ask “What is going on?” 2) Ask “What is success?” 3) Ask “What is the question?” 4) Generate answers 5) Forge the solution 6) Align resources. 

Control Influence Accept (CIA): The basic premise of CIA is that how you respond to problems determines how successful you will be in overcoming them. Therefore, this model is both a problem solving technique and stress-management tool that ensures you aren’t responding to problems in a reactive and unproductive way. The steps in CIA include:

• Control: Identify the aspects of the problem that are within your control.
• Influence: Identify the aspects of the problem that you cannot control, but that you can influence.
• Accept: Identify the aspects of the problem that you can neither control nor influence, and react based on this composite information. 

GROW Model: This is a straightforward problem solving method for goal setting that clearly defines your goals and current situation, and then asks you to define the potential solutions and be realistic about your chosen course of action. The steps break down as follows:

• Goal: What do you want?
• Reality: Where are you now?
• Options: What could you do?
• Will: What will you do?

OODA Loop: This acronym stands for observe, orient, decide, and act. This approach is a decision-making cycle that values agility and flexibility over raw human force. It is framed as a loop because of the understanding that any team will continually encounter problems or opponents to success and have to overcome them.

There are also many un-named creative problem solving techniques that follow a sequenced series of steps. While the exact steps vary slightly, they all follow a similar trajectory and aim to accomplish similar goals of problem, cause, and goal identification, idea generation, and active solution implementation.

MacLeod offers her own problem solving procedure, which echoes the above steps:

“1. Recognize the Problem: State what you see. Sometimes the problem is covert. 2. Identify: Get the facts — What exactly happened? What is the issue? 3. and 4. Explore and Connect: Dig deeper and encourage group members to relate their similar experiences. Now you're getting more into the feelings and background [of the situation], not just the facts.  5. Possible Solutions: Consider and brainstorm ideas for resolution. 6. Implement: Choose a solution and try it out — this could be role play and/or a discussion of how the solution would be put in place.  7. Evaluate: Revisit to see if the solution was successful or not.”

Many of these problem solving techniques can be used in concert with one another, or multiple can be appropriate for any given problem. It’s less about facilitating a perfect CPS session, and more about encouraging team members to continually think outside the box and push beyond personal boundaries that inhibit their innovative thinking. So, try out several methods, find those that resonate best with your team, and continue adopting new techniques and adapting your processes along the way. 

Improve Problem Solving with Work Management in Smartsheet

Empower your people to go above and beyond with a flexible platform designed to match the needs of your team — and adapt as those needs change. 

The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed. 

When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time.  Try Smartsheet for free, today.

Discover why over 90% of Fortune 100 companies trust Smartsheet to get work done.

Effective Problem-Solving Techniques in Business

Problem solving is an increasingly important soft skill for those in business. The Future of Jobs Survey by the World Economic Forum drives this point home. According to this report, complex problem solving is identified as one of the top 15 skills that will be sought by employers in 2025, along with other soft skills such as analytical thinking, creativity and leadership.

Dr. Amy David , clinical associate professor of management for supply chain and operations management, spoke about business problem-solving methods and how the Purdue University Online MBA program prepares students to be business decision-makers.

Why Are Problem-Solving Skills Essential in Leadership Roles?

Every business will face challenges at some point. Those that are successful will have people in place who can identify and solve problems before the damage is done.

“The business world is constantly changing, and companies need to be able to adapt well in order to produce good results and meet the needs of their customers,” David says. “They also need to keep in mind the triple bottom line of ‘people, profit and planet.’ And these priorities are constantly evolving.”

To that end, David says people in management or leadership need to be able to handle new situations, something that may be outside the scope of their everyday work.

“The name of the game these days is change—and the speed of change—and that means solving new problems on a daily basis,” she says.

The pace of information and technology has also empowered the customer in a new way that provides challenges—or opportunities—for businesses to respond.

“Our customers have a lot more information and a lot more power,” she says. “If you think about somebody having an unhappy experience and tweeting about it, that’s very different from maybe 15 years ago. Back then, if you had a bad experience with a product, you might grumble about it to one or two people.”

David says that this reality changes how quickly organizations need to react and respond to their customers. And taking prompt and decisive action requires solid problem-solving skills.

What Are Some of the Most Effective Problem-Solving Methods?

David says there are a few things to consider when encountering a challenge in business.

“When faced with a problem, are we talking about something that is broad and affects a lot of people? Or is it something that affects a select few? Depending on the issue and situation, you’ll need to use different types of problem-solving strategies,” she says.

Using Techniques

There are a number of techniques that businesses use to problem solve. These can include:

• Five Whys : This approach is helpful when the problem at hand is clear but the underlying causes are less so. By asking “Why?” five times, the final answer should get at the potential root of the problem and perhaps yield a solution.
• Gap Analysis : Companies use gap analyses to compare current performance with expected or desired performance, which will help a company determine how to use its resources differently or adjust expectations.
• Gemba Walk : The name, which is derived from a Japanese word meaning “the real place,” refers to a commonly used technique that allows managers to see what works (and what doesn’t) from the ground up. This is an opportunity for managers to focus on the fundamental elements of the process, identify where the value stream is and determine areas that could use improvement.
• Porter’s Five Forces : Developed by Harvard Business School professor Michael E. Porter, applying the Five Forces is a way for companies to identify competitors for their business or services, and determine how the organization can adjust to stay ahead of the game.
• Six Thinking Hats : In his book of the same name, Dr. Edward de Bono details this method that encourages parallel thinking and attempting to solve a problem by trying on different “thinking hats.” Each color hat signifies a different approach that can be utilized in the problem-solving process, ranging from logic to feelings to creativity and beyond. This method allows organizations to view problems from different angles and perspectives.
• SWOT Analysis : This common strategic planning and management tool helps businesses identify strengths, weaknesses, opportunities and threats (SWOT).

“We have a lot of these different tools,” David says. “Which one to use when is going to be dependent on the problem itself, the level of the stakeholders, the number of different stakeholder groups and so on.”

Each of the techniques outlined above uses the same core steps of problem solving:

• Identify and define the problem
• Consider possible solutions
• Evaluate options
• Choose the best solution
• Implement the solution
• Evaluate the outcome

Data drives a lot of daily decisions in business and beyond. Analytics have also been deployed to problem solve.

“We have specific classes around storytelling with data and how you convince your audience to understand what the data is,” David says. “Your audience has to trust the data, and only then can you use it for real decision-making.”

Data can be a powerful tool for identifying larger trends and making informed decisions when it’s clearly understood and communicated. It’s also vital for performance monitoring and optimization.

How Is Problem Solving Prioritized in Purdue’s Online MBA?

The courses in the Purdue Online MBA program teach problem-solving methods to students, keeping them up to date with the latest techniques and allowing them to apply their knowledge to business-related scenarios.

“I can give you a model or a tool, but most of the time, a real-world situation is going to be a lot messier and more valuable than what we’ve seen in a textbook,” David says. “Asking students to take what they know and apply it to a case where there’s not one single correct answer is a big part of the learning experience.”

Make Your Own Decision to Further Your Career

An online MBA from Purdue University can help advance your career by teaching you problem-solving skills, decision-making strategies and more. Reach out today to learn more about earning an online MBA with Purdue University .

More Blog Posts

Purdue + Microsoft = Data Powerhouse

August 17, 2024

Linking the Chain

July 29, 2024

Failing Forward

July 28, 2024

What does commercialization mean?

July 27, 2024

Living Big: Kylie Broton’s MBA Adventure

July 15, 2024

Which degree should you choose? How the MBT stacks up against the MBA

July 12, 2024

From IT Professional to Business Analytics Leader

Triple Master

May 28, 2024

Becoming Irreplacable

May 27, 2024

MSF students explore M&A in inaugural case competition

May 14, 2024

Is the GMAT required for a master’s in finance?

May 6, 2024

Establishing Contact: Marketing Students Network with Chicago Professionals

May 3, 2024

Up for the Challenge

April 25, 2024

AI in the Classroom: Balancing Automation with Student-Centric Learning

The State of Supply Chain Sustainability

April 17, 2024

Find Your Right Fit

Making the Connection

April 16, 2024

Unlocking Opportunities: Future Leaders network at EDGE Conference for supply chain management

April 14, 2024

The Pursuit of Growth

April 1, 2024

Hacking for Good

March 28, 2024

What Is Collective Genius? How Collaboration Drives Innovation

March 25, 2024

Thriving in the Virtual Classroom

March 24, 2024

Doing Good with Data

February 29, 2024

Trading Insights: Finance student lessons from a NYC networking trip

February 20, 2024

Bridging the gap between business and psychology

January 26, 2024

You've been accepted!

January 12, 2024

What Is Operations Management?

January 3, 2024

What Is Data Mining?

Storytelling With Data: Why Data Visualization Is Important

January 1, 2024

What Can You Do With an MBA With a Specialization in Leadership, Negotiation and Change Management?

December 20, 2023

Paving Your Path

December 15, 2023

Supply Chain Risks and Mitigation Strategies

December 12, 2023

Earning a Graduate Degree Without Drowning in Debt

December 8, 2023

How the Purdue Online MBA Program Works

December 4, 2023

From Newbie to Networker

December 1, 2023

Achieving Success

November 28, 2023

A Step Towards Crafting Success

Future of HR Talent Competition 2022

The Edge to Success

Improving Diversity for an Industry Giant

November 21, 2023

Leveling Up

November 20, 2023

5 Reasons Entrepreneurs Should Consider an MBA for Success

November 17, 2023

The Right Fit

3 Steps to Choosing the Right Specialization for Your Online MBA

November 10, 2023

Solving Human Challenges

November 9, 2023

Experiential Learning: Exploring Learning Through Experience

November 3, 2023

3 Advantages of Earning an MBA Online

September 28, 2023

If you would like to receive more information about pursuing a business master’s at the Mitchell E. Daniels, Jr. School of Business, please fill out the form and a program specialist will be in touch!

Connect With Us

• 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
• Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Featured Reads

• Collaboration |
• Turn your team into skilled problem sol ...

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

Picture this, you're handling your daily tasks at work and your boss calls you in and says, "We have a problem." 

Unfortunately, we don't live in a world in which problems are instantly resolved with the snap of our fingers. Knowing how to effectively solve problems is an important professional skill to hone. If you have a problem that needs to be solved, what is the right process to use to ensure you get the most effective solution?

In this article we'll break down the problem-solving process and how you can find the most effective solutions for complex problems.

What is problem solving? 

Problem solving is the process of finding a resolution for a specific issue or conflict. There are many possible solutions for solving a problem, which is why it's important to go through a problem-solving process to find the best solution. You could use a flathead screwdriver to unscrew a Phillips head screw, but there is a better tool for the situation. Utilizing common problem-solving techniques helps you find the best solution to fit the needs of the specific situation, much like using the right tools.

Decision-making tools for agile businesses

In this ebook, learn how to equip employees to make better decisions—so your business can pivot, adapt, and tackle challenges more effectively than your competition.

4 steps to better problem solving

While it might be tempting to dive into a problem head first, take the time to move step by step. Here’s how you can effectively break down the problem-solving process with your team:

1. Identify the problem that needs to be solved

One of the easiest ways to identify a problem is to ask questions. A good place to start is to ask journalistic questions, like:

Who : Who is involved with this problem? Who caused the problem? Who is most affected by this issue?

What: What is happening? What is the extent of the issue? What does this problem prevent from moving forward?

Where: Where did this problem take place? Does this problem affect anything else in the immediate area? 

When: When did this problem happen? When does this problem take effect? Is this an urgent issue that needs to be solved within a certain timeframe?

Why: Why is it happening? Why does it impact workflows?

How: How did this problem occur? How is it affecting workflows and team members from being productive?

Asking journalistic questions can help you define a strong problem statement so you can highlight the current situation objectively, and create a plan around that situation.

Here’s an example of how a design team uses journalistic questions to identify their problem:

Overarching problem: Design requests are being missed

Who: Design team, digital marketing team, web development team

What: Design requests are forgotten, lost, or being created ad hoc.

Where: Email requests, design request spreadsheet

When: Missed requests on January 20th, January 31st, February 4th, February 6th

How : Email request was lost in inbox and the intake spreadsheet was not updated correctly. The digital marketing team had to delay launching ads for a few days while design requests were bottlenecked. Designers had to work extra hours to ensure all requests were completed.

In this example, there are many different aspects of this problem that can be solved. Using journalistic questions can help you identify different issues and who you should involve in the process.

2. Brainstorm multiple solutions

If at all possible, bring in a facilitator who doesn't have a major stake in the solution. Bringing an individual who has little-to-no stake in the matter can help keep your team on track and encourage good problem-solving skills.

Here are a few brainstorming techniques to encourage creative thinking:

Brainstorm alone before hand: Before you come together as a group, provide some context to your team on what exactly the issue is that you're brainstorming. This will give time for you and your teammates to have some ideas ready by the time you meet.

Say yes to everything (at first): When you first start brainstorming, don't say no to any ideas just yet—try to get as many ideas down as possible. Having as many ideas as possible ensures that you’ll get a variety of solutions. Save the trimming for the next step of the strategy. 

Talk to team members one-on-one: Some people may be less comfortable sharing their ideas in a group setting. Discuss the issue with team members individually and encourage them to share their opinions without restrictions—you might find some more detailed insights than originally anticipated.

Break out of your routine: If you're used to brainstorming in a conference room or over Zoom calls, do something a little different! Take your brainstorming meeting to a coffee shop or have your Zoom call while you're taking a walk. Getting out of your routine can force your brain out of its usual rut and increase critical thinking.

3. Define the solution

After you brainstorm with team members to get their unique perspectives on a scenario, it's time to look at the different strategies and decide which option is the best solution for the problem at hand. When defining the solution, consider these main two questions: What is the desired outcome of this solution and who stands to benefit from this solution? 

Set a deadline for when this decision needs to be made and update stakeholders accordingly. Sometimes there's too many people who need to make a decision. Use your best judgement based on the limitations provided to do great things fast.

4. Implement the solution

To implement your solution, start by working with the individuals who are as closest to the problem. This can help those most affected by the problem get unblocked. Then move farther out to those who are less affected, and so on and so forth. Some solutions are simple enough that you don’t need to work through multiple teams.

After you prioritize implementation with the right teams, assign out the ongoing work that needs to be completed by the rest of the team. This can prevent people from becoming overburdened during the implementation plan . Once your solution is in place, schedule check-ins to see how the solution is working and course-correct if necessary.

Implement common problem-solving strategies

There are a few ways to go about identifying problems (and solutions). Here are some strategies you can try, as well as common ways to apply them:

Trial and error

Trial and error problem solving doesn't usually require a whole team of people to solve. To use trial and error problem solving, identify the cause of the problem, and then rapidly test possible solutions to see if anything changes. 

This problem-solving method is often used in tech support teams through troubleshooting.

The 5 whys problem-solving method helps get to the root cause of an issue. You start by asking once, “Why did this issue happen?” After answering the first why, ask again, “Why did that happen?” You'll do this five times until you can attribute the problem to a root cause. 

This technique can help you dig in and find the human error that caused something to go wrong. More importantly, it also helps you and your team develop an actionable plan so that you can prevent the issue from happening again.

Here’s an example:

Problem: The email marketing campaign was accidentally sent to the wrong audience.

“Why did this happen?” Because the audience name was not updated in our email platform.

“Why were the audience names not changed?” Because the audience segment was not renamed after editing. 

“Why was the audience segment not renamed?” Because everybody has an individual way of creating an audience segment.

“Why does everybody have an individual way of creating an audience segment?” Because there is no standardized process for creating audience segments. 

“Why is there no standardized process for creating audience segments?” Because the team hasn't decided on a way to standardize the process as the team introduced new members. 

In this example, we can see a few areas that could be optimized to prevent this mistake from happening again. When working through these questions, make sure that everyone who was involved in the situation is present so that you can co-create next steps to avoid the same problem. 

A SWOT analysis

A SWOT analysis can help you highlight the strengths and weaknesses of a specific solution. SWOT stands for:

Strength: Why is this specific solution a good fit for this problem? 

Weaknesses: What are the weak points of this solution? Is there anything that you can do to strengthen those weaknesses?

Opportunities: What other benefits could arise from implementing this solution?

Threats: Is there anything about this decision that can detrimentally impact your team?

As you identify specific solutions, you can highlight the different strengths, weaknesses, opportunities, and threats of each solution. 

This particular problem-solving strategy is good to use when you're narrowing down the answers and need to compare and contrast the differences between different solutions. 

Even more successful problem solving

After you’ve worked through a tough problem, don't forget to celebrate how far you've come. Not only is this important for your team of problem solvers to see their work in action, but this can also help you become a more efficient, effective , and flexible team. The more problems you tackle together, the more you’ll achieve. 

Looking for a tool to help solve problems on your team? Track project implementation with a work management tool like Asana .

Related resources

10 tips to improve nonverbal communication

Scaling clinical trial management software with PM solutions

How to build your critical thinking skills in 7 steps (with examples)

4 ways to establish roles and responsibilities for team success

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

How to Solve Problems

• Laura Amico

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

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

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

Partner Center

The Art of Effective Problem Solving: A Step-by-Step Guide

Author: Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

Whether we realise it or not, problem solving skills are an important part of our daily lives. From resolving a minor annoyance at home to tackling complex business challenges at work, our ability to solve problems has a significant impact on our success and happiness. However, not everyone is naturally gifted at problem-solving, and even those who are can always improve their skills. In this blog post, we will go over the art of effective problem-solving step by step.

You will learn how to define a problem, gather information, assess alternatives, and implement a solution, all while honing your critical thinking and creative problem-solving skills. Whether you’re a seasoned problem solver or just getting started, this guide will arm you with the knowledge and tools you need to face any challenge with confidence. So let’s get started!

Problem Solving Methodologies

Individuals and organisations can use a variety of problem-solving methodologies to address complex challenges. 8D and A3 problem solving techniques are two popular methodologies in the Lean Six Sigma framework.

Methodology of 8D (Eight Discipline) Problem Solving:

The 8D problem solving methodology is a systematic, team-based approach to problem solving. It is a method that guides a team through eight distinct steps to solve a problem in a systematic and comprehensive manner.

The 8D process consists of the following steps:

• Form a team: Assemble a group of people who have the necessary expertise to work on the problem.
• Define the issue: Clearly identify and define the problem, including the root cause and the customer impact.
• Create a temporary containment plan: Put in place a plan to lessen the impact of the problem until a permanent solution can be found.
• Identify the root cause: To identify the underlying causes of the problem, use root cause analysis techniques such as Fishbone diagrams and Pareto charts.
• Create and test long-term corrective actions: Create and test a long-term solution to eliminate the root cause of the problem.
• Implement and validate the permanent solution: Implement and validate the permanent solution’s effectiveness.
• Prevent recurrence: Put in place measures to keep the problem from recurring.
• Recognize and reward the team: Recognize and reward the team for its efforts.

Download the 8D Problem Solving Template

A3 Problem Solving Method:

The A3 problem solving technique is a visual, team-based problem-solving approach that is frequently used in Lean Six Sigma projects. The A3 report is a one-page document that clearly and concisely outlines the problem, root cause analysis, and proposed solution.

The A3 problem-solving procedure consists of the following steps:

• Determine the issue: Define the issue clearly, including its impact on the customer.
• Perform root cause analysis: Identify the underlying causes of the problem using root cause analysis techniques.
• Create and implement a solution: Create and implement a solution that addresses the problem’s root cause.
• Monitor and improve the solution: Keep an eye on the solution’s effectiveness and make any necessary changes.

Subsequently, in the Lean Six Sigma framework, the 8D and A3 problem solving methodologies are two popular approaches to problem solving. Both methodologies provide a structured, team-based problem-solving approach that guides individuals through a comprehensive and systematic process of identifying, analysing, and resolving problems in an effective and efficient manner.

Step 1 – Define the Problem

The definition of the problem is the first step in effective problem solving. This may appear to be a simple task, but it is actually quite difficult. This is because problems are frequently complex and multi-layered, making it easy to confuse symptoms with the underlying cause. To avoid this pitfall, it is critical to thoroughly understand the problem.

To begin, ask yourself some clarifying questions:

• What exactly is the issue?
• What are the problem’s symptoms or consequences?
• Who or what is impacted by the issue?
• When and where does the issue arise?

Answering these questions will assist you in determining the scope of the problem. However, simply describing the problem is not always sufficient; you must also identify the root cause. The root cause is the underlying cause of the problem and is usually the key to resolving it permanently.

Try asking “why” questions to find the root cause:

• What causes the problem?
• Why does it continue?
• Why does it have the effects that it does?

By repeatedly asking “ why ,” you’ll eventually get to the bottom of the problem. This is an important step in the problem-solving process because it ensures that you’re dealing with the root cause rather than just the symptoms.

Once you have a firm grasp on the issue, it is time to divide it into smaller, more manageable chunks. This makes tackling the problem easier and reduces the risk of becoming overwhelmed. For example, if you’re attempting to solve a complex business problem, you might divide it into smaller components like market research, product development, and sales strategies.

To summarise step 1, defining the problem is an important first step in effective problem-solving. You will be able to identify the root cause and break it down into manageable parts if you take the time to thoroughly understand the problem. This will prepare you for the next step in the problem-solving process, which is gathering information and brainstorming ideas.

Step 2 – Gather Information and Brainstorm Ideas

Gathering information and brainstorming ideas is the next step in effective problem solving. This entails researching the problem and relevant information, collaborating with others, and coming up with a variety of potential solutions. This increases your chances of finding the best solution to the problem.

Begin by researching the problem and relevant information. This could include reading articles, conducting surveys, or consulting with experts. The goal is to collect as much information as possible in order to better understand the problem and possible solutions.

Next, work with others to gather a variety of perspectives. Brainstorming with others can be an excellent way to come up with new and creative ideas. Encourage everyone to share their thoughts and ideas when working in a group, and make an effort to actively listen to what others have to say. Be open to new and unconventional ideas and resist the urge to dismiss them too quickly.

Finally, use brainstorming to generate a wide range of potential solutions. This is the place where you can let your imagination run wild. At this stage, don’t worry about the feasibility or practicality of the solutions; instead, focus on generating as many ideas as possible. Write down everything that comes to mind, no matter how ridiculous or unusual it may appear. This can be done individually or in groups.

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the next step in the problem-solving process, which we’ll go over in greater detail in the following section.

Step 3 – Evaluate Options and Choose the Best Solution

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the third step in effective problem solving, and it entails weighing the advantages and disadvantages of each solution, considering their feasibility and practicability, and selecting the solution that is most likely to solve the problem effectively.

To begin, weigh the advantages and disadvantages of each solution. This will assist you in determining the potential outcomes of each solution and deciding which is the best option. For example, a quick and easy solution may not be the most effective in the long run, whereas a more complex and time-consuming solution may be more effective in solving the problem in the long run.

Consider each solution’s feasibility and practicability. Consider the following:

• Can the solution be implemented within the available resources, time, and budget?
• What are the possible barriers to implementing the solution?
• Is the solution feasible in today’s political, economic, and social environment?

You’ll be able to tell which solutions are likely to succeed and which aren’t by assessing their feasibility and practicability.

Finally, choose the solution that is most likely to effectively solve the problem. This solution should be based on the criteria you’ve established, such as the advantages and disadvantages of each solution, their feasibility and practicability, and your overall goals.

It is critical to remember that there is no one-size-fits-all solution to problems. What is effective for one person or situation may not be effective for another. This is why it is critical to consider a wide range of solutions and evaluate each one based on its ability to effectively solve the problem.

Step 4 – Implement and Monitor the Solution

When you’ve decided on the best solution, it’s time to put it into action. The fourth and final step in effective problem solving is to put the solution into action, monitor its progress, and make any necessary adjustments.

To begin, implement the solution. This may entail delegating tasks, developing a strategy, and allocating resources. Ascertain that everyone involved understands their role and responsibilities in the solution’s implementation.

Next, keep an eye on the solution’s progress. This may entail scheduling regular check-ins, tracking metrics, and soliciting feedback from others. You will be able to identify any potential roadblocks and make any necessary adjustments in a timely manner if you monitor the progress of the solution.

Finally, make any necessary modifications to the solution. This could entail changing the solution, altering the plan of action, or delegating different tasks. Be willing to make changes if they will improve the solution or help it solve the problem more effectively.

It’s important to remember that problem solving is an iterative process, and there may be times when you need to start from scratch. This is especially true if the initial solution does not effectively solve the problem. In these situations, it’s critical to be adaptable and flexible and to keep trying new solutions until you find the one that works best.

To summarise, effective problem solving is a critical skill that can assist individuals and organisations in overcoming challenges and achieving their objectives. Effective problem solving consists of four key steps: defining the problem, generating potential solutions, evaluating alternatives and selecting the best solution, and implementing the solution.

You can increase your chances of success in problem solving by following these steps and considering factors such as the pros and cons of each solution, their feasibility and practicability, and making any necessary adjustments. Furthermore, keep in mind that problem solving is an iterative process, and there may be times when you need to go back to the beginning and restart. Maintain your adaptability and try new solutions until you find the one that works best for you.

• Novick, L.R. and Bassok, M., 2005.  Problem Solving . Cambridge University Press.

Was this helpful?

Daniel Croft

Hi im Daniel continuous improvement manager with a Black Belt in Lean Six Sigma and over 10 years of real-world experience across a range sectors, I have a passion for optimizing processes and creating a culture of efficiency. I wanted to create Learn Lean Siigma to be a platform dedicated to Lean Six Sigma and process improvement insights and provide all the guides, tools, techniques and templates I looked for in one place as someone new to the world of Lean Six Sigma and Continuous improvement.

What is SMED: (Single-Minute Exchange of Die)

Histogram Basics

Free lean six sigma templates.

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

Understanding Process Performance: Pp and Ppk

Understand Process Performance (Pp) and Process Performance Index (Ppk) to assess and improve manufacturing processes.…

LIFO or FIFO for Stock Management?

Choosing between LIFO and FIFO for stock management depends on factors like product nature, market…

Are There Any Official Standards for Six Sigma?

Are there any official standards for Six Sigma? While Six Sigma is a well-defined methodology…

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

• Get started

How to Improve Your Problem-Solving Skills as a Chief Administrative Officer

Improve your problem-solving skills as a Chief Administrative Officer with these tips and techniques. Boost your leadership abilities today.

As a Chief Administrative Officer, your role is crucial in ensuring smooth operations within your organization. A key aspect of your role is problem-solving, which involves identifying, analyzing, and resolving issues that may arise. In order to be an effective problem solver, you need to adopt a problem-solving mindset, enhance your critical thinking and analytical skills, and hone effective communication and collaboration practices. This article will guide you through the steps you can take to improve your problem-solving skills as a Chief Administrative Officer.

Understanding the Role of a Chief Administrative Officer

As a Chief Administrative Officer, you are responsible for overseeing the administrative functions of your organization. Your role is integral to ensuring the smooth running of your organization, as you are tasked with developing and implementing policies and procedures that contribute to the overall success of the organization.

One of the key responsibilities of a Chief Administrative Officer is managing budgets. You will have to work closely with other members of the organization to ensure that funds are allocated appropriately and that the organization remains financially stable. You will also be responsible for handling staffing, which includes hiring, training, and managing employees. Analyzing data is another important aspect of your role, as you will need to be able to make informed decisions based on the information that you gather.

Key Responsibilities and Challenges

In addition to managing budgets, handling staffing, and analyzing data, you will also be responsible for negotiating contracts, dealing with legal issues, and overseeing other administrative tasks. With so many responsibilities, it is important to be able to identify and address problems that arise quickly.

One of the biggest challenges that you will face as a Chief Administrative Officer is managing the expectations of various stakeholders. You will need to work closely with other members of the organization, as well as external stakeholders, to ensure that everyone's needs are being met. This can be a difficult task, as different stakeholders may have conflicting priorities and goals.

The Importance of Problem-Solving Skills in Administration

Effective problem-solving skills are crucial in Administration because they allow you to quickly and efficiently identify issues, analyze the root cause, and develop solutions. By doing so, you can help your organization to be more efficient, productive, and successful.

As a Chief Administrative Officer, you will need to be able to think critically and creatively in order to solve complex problems. You will need to be able to work collaboratively with other members of the organization, as well as external stakeholders, to develop solutions that are effective and sustainable.

Ultimately, the success of your organization will depend on your ability to effectively manage the administrative functions of the organization. By developing your problem-solving skills and staying focused on the key responsibilities of your role, you can help your organization to achieve its goals and thrive in a competitive environment.

Developing a Problem-Solving Mindset

A problem-solving mindset involves cultivating a growth mindset, being curious, open to new ideas, and practicing patience and persistence. All of these are essential traits for effective problem-solving.

Problem-solving is a critical skill that is necessary for success in both personal and professional life. Whether you are working on a complex project at work or trying to solve a problem in your personal life, having a problem-solving mindset can make all the difference.

Embracing a Growth Mindset

Having a growth mindset means believing that your skills and abilities can be developed and improved with hard work, dedication, and a willingness to learn. A growth mindset opens up possibilities and encourages innovative solutions that may have seemed impossible previously.

When you embrace a growth mindset, you are more likely to take risks and try new things. You are not afraid of failure because you understand that failure is an opportunity to learn and grow. This mindset allows you to approach problems with a positive attitude and a willingness to find solutions.

Cultivating Curiosity and Openness to New Ideas

Cultivating curiosity means questioning assumptions and being open to new and innovative ideas. Having an open mind is key to problem-solving as it allows you to explore different solutions and perspectives.

When you are curious, you are more likely to ask questions and seek out information. This can lead to new insights and ideas that may not have been considered before. Being open to new ideas means that you are willing to consider different perspectives and approaches, which can lead to more creative and effective solutions.

Practicing Patience and Persistence

Problem-solving can be a challenging and time-consuming process that requires patience and persistence. When faced with a problem, break it down into manageable steps and take time to evaluate each one thoroughly. Be patient and persistent in your efforts to find a solution.

It is important to remember that problem-solving is not always a linear process. You may encounter setbacks and obstacles along the way, but it is important to stay focused and continue working towards a solution. With patience and persistence, you can overcome even the most challenging problems.

In conclusion, developing a problem-solving mindset is essential for success in both personal and professional life. By embracing a growth mindset, cultivating curiosity and openness to new ideas, and practicing patience and persistence, you can become an effective problem solver who is capable of finding innovative solutions to even the most complex problems.

Enhancing Critical Thinking and Analytical Skills

Critical thinking and analytical skills are essential for effective problem-solving. The ability to ask the right questions, break down complex problems, and evaluate possible solutions are all key components of critical thinking and analytical skills.

Developing critical thinking and analytical skills takes time and effort, but it is a valuable skill set that can be applied in all areas of life. Here are some additional tips to enhance your critical thinking and analytical skills:

Asking the Right Questions

Asking the right questions is essential to identifying the root cause of a problem. Be sure to ask open-ended questions that encourage exploration and discovery. It is also important to consider the context of the problem and the different perspectives of those involved.

For example, if you are trying to solve a problem at work, consider the perspectives of your colleagues, supervisors, and customers. By understanding their viewpoints, you can gain a better understanding of the problem and potential solutions.

Breaking Down Complex Problems

Breaking down complex problems into smaller manageable steps allows you to analyze each component and identify solutions for each. This process can also help to identify interdependencies between the different components of the problem.

One technique to break down complex problems is to use a mind map. A mind map is a visual tool that helps you organize your thoughts and ideas. Start with the main problem in the center of the map and then branch out to the different components of the problem. This can help you see the big picture and identify potential solutions.

Evaluating Possible Solutions

Once you have identified potential solutions, it is important to evaluate and compare them. Consider the advantages and disadvantages of each solution and weigh the potential outcomes. This will help you select the best option to implement.

Another technique to evaluate possible solutions is to use a decision matrix. A decision matrix is a chart that helps you compare different options based on a set of criteria. List the criteria that are important for the decision and then rate each option on a scale of 1-5 for each criterion. Add up the scores for each option to determine the best solution.

By using these techniques to enhance your critical thinking and analytical skills, you can become a more effective problem solver and make better decisions in all areas of your life.

Effective Communication and Collaboration

Effective communication and collaboration are crucial in any organization. They are the foundation of problem-solving and can lead to the creation of innovative solutions that benefit everyone. When communication is clear and teams are strong, the exchange of ideas becomes easier, and constructive solutions can arise.

Active Listening and Empathy

Active listening and empathy are essential components of effective communication. Active listening requires paying attention to the speaker and understanding their perspective. Empathy facilitates understanding and allows for the development of collaborative solutions. By actively listening and showing empathy, you can build stronger relationships with your colleagues, which can lead to better problem-solving and more productive teamwork.

For example, imagine you are working on a project with a colleague who has a different opinion than you. By actively listening to their perspective and showing empathy, you can better understand their point of view. This can lead to a more productive discussion, where you can find a solution that works for both of you.

Clear and Concise Communication

Clear and concise communication is essential in ensuring that everyone is on the same page when tackling problems. Clear communication ensures that everyone understands what is expected, and concise communication ensures that everyone stays focused on primary goals. When communication is not clear, misunderstandings can occur, leading to confusion and frustration.

For example, imagine you are working on a project where there are multiple tasks to complete. If the communication is not clear, some team members may not understand which tasks they are responsible for, leading to delays and confusion. However, if the communication is clear and concise, everyone will know what is expected of them, and the project can move forward smoothly.

Building a Strong Team

Building a strong team requires understanding the strengths and weaknesses of individuals and managing them accordingly. Encourage teamwork and promote open communication to foster a culture of collaboration that supports problem-solving effectively.

For example, imagine you are the manager of a team working on a project. By understanding the strengths and weaknesses of each team member, you can assign tasks that play to their strengths. This can lead to a more productive team, where everyone is working towards a common goal.

Furthermore, promoting open communication can help build trust among team members. When team members feel comfortable sharing their thoughts and ideas, they are more likely to work together effectively, leading to better problem-solving and more successful projects.

Improving problem-solving skills as a Chief Administrative Officer requires cultivating a problem-solving mindset, enhancing critical thinking and analytical skills, and practicing effective communication and collaboration. By actively working on these areas you can ensure you are well equipped to tackle any challenge that may arise within your organization.

Ready to build an advisory board?

• Q1. What is the role of a Chief Administrative Officer? A1. As a Chief Administrative Officer, your role is to oversee the administrative functions of your organization, develop and implement policies and procedures, manage budgets, handle staffing, analyze data, negotiate contracts, and deal with legal issues.
• Q2. Why is problem-solving essential for a Chief Administrative Officer? A2. Effective problem-solving skills are crucial for a Chief Administrative Officer as it allows them to quickly and efficiently identify issues, analyze the root cause, and develop solutions, making the organization more efficient, productive, and successful.
• Q3. How can one develop a problem-solving mindset? A3. Developing a problem-solving mindset requires cultivating a growth mindset, being curious, open to new ideas, and being patient and persistent.
• Q4. What are the tips for enhancing critical thinking and analytical skills? A4. The tips for enhancing critical thinking and analytical skills are asking the right questions, breaking down complex problems, and evaluating possible solutions.
• Q5. Why is effective communication and collaboration important for an organization? A5. Effective communication and collaboration are important for an organization because they are the foundation of problem-solving and can lead to the creation of innovative solutions that benefit everyone. Clear and concise communication ensures that everyone understands what is expected, and teamwork promotes open communication that supports effective problem-solving.

Build your advisory board today

See how easy we've made it to build an advisory board

See what boards you're qualified for

See what you qualify for with our 2-minute assessment

Similar Articles

How to Improve Your Conflict Resolution Skills as a VP of Risk Management

How to Improve Your Active Listening Skills as a VP of Marketing

How to Improve Your Leadership Skills as a Chief Human Resources Officer

How to Improve Your Problem-Solving Skills as a Chief Digital Officer

How to Improve Your Problem Solving Skills as a VP of Data

How to Improve Your Emotional Intelligence Skills as a VP of Administration

How to Improve Your Project Management Skills as a Chief Compliance Officer

How to Improve Your Critical Thinking Skills as a Chief Financial Officer

How to Improve Your Presentation Skills as a VP of Administration

How to Improve Your Teamwork Skills as a VP of Sustainability

How to Improve Your Problem Solving Skills as a Chief Data Officer

How to Improve Your Active Listening Skills as a Chief Innovation Officer

How to Improve Your Decision Making Skills as a VP of Corporate Communications

How to Improve Your Networking Skills as a Chief Human Resources Officer

How to Improve Your Project Management Skills as a VP of Innovation

Start an advisory board.

Join an advisory board

• Problem management techniques
• Get Problem management kit

Everything you need to know about effective problem management

• Try ServiceDesk Plus now
• Start my free trial

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

IT Problem management techniques

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

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

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

Brainstorming

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

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

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

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

Kepner-Tregoe method

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

The method follows four processes:

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

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

Define the problem

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

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

Failed backup on server

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

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

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

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

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

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

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

Describe the problem

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

The questions below help describe four parts of any problem:

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

Each of these questions demands two types of answers:

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

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

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

Establish possible causes

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

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

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

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

Test the most probable cause

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

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

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

Verify the true cause

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

Ishikawa analysis, or fishbone diagram analysis

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

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

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

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

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

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

Pareto analysis

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

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

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

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

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

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

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

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

Five whys technique

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

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

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

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

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

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

Other techniques

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

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

Reactive vs Proactive problem management

Problem management best practices

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

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

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

Problem management feature checklist

IT incident management handbook

•   Live Demo
•   Compare
•   Get quote

Administrative Skills Aren’t Just for Admin Jobs—Here’s What Everyone Needs to Know (Plus a List of Examples)

As you look for jobs—particularly admin jobs such as executive assistant or office manager—you may see that employers are looking for administrative skills. And for good reason: Businesses can’t run without them. “Focusing on administrative skills can transform average companies and employees into exceptional ones,” says Muse career coach Neely Raffellini .

But what are administrative skills? Who really needs them? (Short answer: everyone.) How do you improve yours? And how do you show employers that you have them in a job search?

What Are Administrative Skills and Why Are They Important at Work?

Administrative skills are the abilities you need to perform tasks that keep any type of business running. They “are the foundational tools that help you complete your job responsibilities,” says Muse career coach Anne Kelly . In other words, administrative skills allow you to do the tasks that support you in getting your work done. For example, scheduling meetings, writing emails, and maintaining office supply levels are all administrative skills.

Administrative positions rely primarily on administrative skills, of course, but every job requires the use of administrative skills in some capacity. For example, in order to complete their design work, a graphic designer may need to communicate with clients, schedule a meeting with stakeholders, use project management software, plan how they’re going to allot their time in a given week, and organize multiple versions of a design on their computer. If you’re trying to identify when you use administrative skills in your own job, think of those tasks you need to do, not necessarily the ones you want to do, Kelly says.

Administrative skills are helpful not only for getting your individual job done well, but also for ensuring your team and organization’s success as a whole. They “create a structure so that the company and its employees can function,” Raffellini says. “The system they create helps everything (and everyone!) perform at the highest level.”

Examples of Administrative Skills

Any skill that helps support your own work or the operation of your company could be an administrative skill, but here are some of the most common categories of administrative skills—and examples that fall under each category.

Communication Skills

Communication skills are all of the abilities that help you share information with others, both inside and outside of your company. They ensure everyone (yourself included) has the knowledge they need to do their job, is informed of any changes, can give and receive feedback, and is able to complete a number of other vital professional functions. Administrative communication skills can be used in verbal, nonverbal, written, and visual forms of communication and are needed in virtually every job.

Here are a few examples:

• The ability to give and receive feedback
• Active listening
• Answering and directing calls
• Body language awareness
• Cold calling
• Communication method choice
• Customer service
• Editing and proofreading
• Empathetic listening
• Note taking

Read More: Your Communication Skills Matter for Every Job—Here’s How to Use, Improve, and Show Off Yours

Organizational Skills

Organizational skills help you arrange your physical and digital space as well as your time, resources, and mental bandwidth, so that you can complete tasks as efficiently as possible. If you’re an administrative assistant, for example, you may need to organize office supplies, files, phone and email messages, or travel plans.

Some example of administrative organizational skills are:

• Attention to detail
• Allocation of meeting spaces
• Digital organization
• Event planning
• Office organization
• Project management
• Reimbursement and expense processing
• Supply inventory
• Time management
• Travel planning, scheduling, and booking

Read More: Your Guide to Organizational Skills on the Job—and During the Job Hunt

Time Management Skills

Time management skills are a subset of organizational skills, but they’re especially important. Time management skills help you plan your time, be more efficient, and accomplish everything you need to at work. They also ensure that everyone on a team or in an office is respecting the time of others.

Some examples of administrative time management skills are:

• Calendar management
• Deadline management
• Goal setting
• Pre-planning
• Prioritization
• Roadmap creation
• Schedule coordination
• Task management
• Time estimation

Read More: These Time Management Skills Can Make You a Better Employee—and Improve Your Work-Life Balance

Technical Skills

Technical skills are the knowledge and ability to perform specific tasks, especially those that require computers or other equipment or software. Even if you’re not in what you’d consider a “tech” role or working for a tech company, these skills are vital. Administrative technical skills help employees communicate; track progress, data, and information; troubleshoot minor issues; create presentations; and maintain efficiency, to name just a few. During the COVID-19 pandemic, technical skills became even more important since most work had to be completed online using various collaboration and other tools.

A few examples of technical administrative skills are:

• Communication software: Slack, Zoom, Microsoft Teams, Google Meet
• Database searching and updating
• Google Suite: Docs, Drive, Forms, Gmail, Sheets, Slides
• Microsoft365: Excel, OneDrive, OneNote, PowerPoint, Word
• Project management software: Airtable, Asana, Jira, Monday, Trello
• Use of office equipment (for example, operating a printer, scanner, or fax machine)
• Scheduling software: Google Calendar, iCalendar, Microsoft Outlook

Read More: What Are Technical Skills and How Should You Include Them On Your Resume? (Plus a List of Examples)

Problem-Solving

No matter what your job is, you’ll come up against unexpected hurdles and challenges. Problem-solving skills help you figure out what to do next. For example, if you’re an executive assistant whose manager is suddenly going to miss an important meeting because of a flight delay, you might brainstorm solutions, analyze the possible options, and make a decision about how to proceed. And it's important to be able to handle challenges without always going to your manager—though you do want to recognize when you need help solving a problem.

• Adaptability
• Brainstorming
• Conflict resolution
• Critical thinking
• Decision making
• Forecasting
• Resource allocation

Read More: How to Improve Your Problem-Solving Skills (and Show Them Off in Your Job Hunt)

How to Improve Your Administrative Skills

Any skill can be improved, and administrative skills are no exception. Here are a few tips for improving yours:

• Identify your weak points. Ask yourself questions to figure out which skills you need to improve: What tasks give you the most difficulty? What parts of your work have gotten the most negative feedback from past managers and coworkers? Where have you dropped the ball? Think through these answers and identify common themes. You can also ask for feedback from a willing colleague.
• Ask for help: Is there someone you know well in your network or personal life who excels at the skill set you want to improve? See if they’re willing to help you out, but be clear in what you’re asking for. Would you like them to look over a few emails you’ve written and give feedback? Do you want to know how they prioritize their tasks? A specific ask is more likely to get a response.
• Look for online resources and classes: There are plenty of online resources for improving administrative skills. If you’re struggling with a specific technology, there may be a tutorial from the company that makes it or a tutorial on YouTube. Sites like LinkedIn Learning and Coursera might have online classes that can help you hone your skills. Resources like The Muse have advice articles that will teach you about using and improving specific skills—for example Google Sheets or inbox organization .
• Practice: Improving almost any skill requires that you actually use that skill, so find ways to practice in low-stakes situations. Can you practice different communication techniques with friends? Can you hone your time management skills by scheduling your chores and leisure activities on a weekend in different ways?

How to Show Off Your Administrative Skills in a Job Hunt

Now that you know what administrative skills you have or need to have, here’s how to show them off to potential employers.

1. Choose the Right Skills to Highlight

Closely read the job description of any opening you apply to and note which administrative skills are mentioned explicitly either in the requirements or the job duties. These are the skills employers will be looking for and they’re the ones you should highlight. For basic administrative skills, make sure you’re not taking up valuable resume space by listing qualifications the employer didn’t ask for, even if you think you’ll need them. For example, technical skills like typing, using Microsoft Office, and emailing don’t need to be in your application materials unless they’re mentioned in the job description.

2. Work Them Into Your Resume and Cover Letter

Employers are interested in the results of your skills more than the fact that you have them, Raffellini says. “The best way to showcase administrative skills is by providing specific examples” on your resume and cover letter . For example, think of times you’ve made a difference. Have you saved time or money? Created a new process or system? Solved a big issue? Under your work experience on your resume, write strong, quantified bullet points that show how you’ve used your skills to make things better for your employers and list any hard skills again in your skills section . You can bring up skills that are especially crucial in a cover letter by giving a more detailed example of how you’ve successfully used them. 

3. Demonstrate Them at Every Opportunity

Beyond your application materials, show off your administrative skills at every step of the hiring process. For example, follow instructions for submitting your application, Kelly says. Write professional emails , answer the phone politely, and practice with any tech you’ll use in a video interview beforehand. Any part of the interview process that might resemble your day-to-day job duties is a chance to show potential employers what you can do.

• 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

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

• Articles Automation Career Cloud Containers Kubernetes Linux Programming Security

Sysadmin careers: The 5 steps of problem solving

%t min read | by David Both (Sudoer alumni)

Photo by  Robin Schreiner  from  Pexels

In the previous article, 4 problem-solving strategies for sysadmins , we looked at methods of reasoning about problems that relate to computer hardware and software. We saw that problem-solving approaches like MAPs and other symptom-fix methods have significant limitations. It is also clear that proprietary, closed software systems do not lend themselves to reasoned approaches, while open systems like Linux and open source software, in general, are intimately knowable and thus tractable to reason and logic.

One of the best things that my mentors helped me with was the formulation of a defined reasoning process that I could always use for solving problems of nearly any type. That process, the algorithm, is very closely related to the scientific method and is what we will cover in this article.

During the research for my book,  The Linux Philosophy for SysAdmins , I discovered a short article titled,  How the Scientific Method Works , that describes the scientific method using a diagram very much like the one I have created for my "five steps of problem-solving."

Solving problems of any kind is art, science, and—some would say—perhaps a bit of magic, too. Solving technical problems, such as those that occur with computers, requires a good deal of specialized knowledge as well. Any approach to solving problems of any nature —including problems with Linux—must include more than just a list of symptoms and the steps necessary to fix or circumvent the problems that caused the symptoms. This so-called "symptom-fix" approach looks good on paper to many managers, but it really sucks in practice. The best way to approach problem-solving is with a large base of knowledge of the subject and a strong methodology.

The five steps of problem-solving

There are five basic steps that are involved in the problem-solving process, as shown in Figure 1. This algorithm is very similar to that of the scientific method but is specifically intended for solving technical problems.

You probably already follow these steps when you troubleshoot a problem but do not even realize it. These steps are universal and apply to solving most any type of problem, not just problems with computers or Linux. I used these steps for years with various types of problems without realizing it. Having them codified for me made me much more effective at solving problems because, when I became stuck, I could review the steps I had taken, verify where I was in the process, and restart at any appropriate step.

You may have heard a couple of other terms applied to problem-solving in the past. The first three steps of this process are also known as problem determination, that is, finding the root cause of the problem. The last two steps are problem resolution, which is actually fixing the problem.

The next sections cover each of these five steps in more detail.

Knowledge of the subject in which you are attempting to solve a problem is the first step. All of the articles I have seen about the scientific method seem to assume this as a prerequisite. However, the acquisition of knowledge is an ongoing process, driven by curiosity and augmented by the knowledge gained from using the scientific method to explore and learn more through experimentation. You must be knowledgeable about Linux at the very least, and furthermore, you must be knowledgeable about the other factors that can interact with and affect Linux. Hardware, the network, and even environmental factors like temperature, humidity, and the electrical environment in which the Linux system operates can affect it.

Knowledge can be gained by reading books and web sites about Linux and those other topics. You can attend classes, seminars, and conferences. You can also set up a number of physical or virtual Linux computers in a networked environment. And, of course, there is much to learn through interaction with other knowledgeable people. You learn when you resolve a problem or discover a new cause for a particular type of problem, even when an attempt to fix a problem results in a temporary failure.

Classes are also valuable in providing us with new information. My personal preference is to play—uh, experiment—with Linux or a particular piece such as networking, name services, DHCP, Chrony, and more. Then I take a class or two to help me internalize the knowledge I have gained.

Remember, "without knowledge, resistance is futile," to paraphrase the Borg. Knowledge is power.

Observation

The second step in solving the problem is to observe its symptoms. It is important to take note of all of the problem symptoms, but also to observe what is working properly. This is not the time to try to fix the problem; merely observe. Another important part of observation is to ask yourself questions about what you see and what you do not see. Aside from the questions you need to ask that are specific to the problem, there are some general questions to ask:

• Is this problem caused by hardware, Linux, application software, or perhaps by lack of user knowledge or training?
• Is this problem similar to others I have seen?
• Is there an error message?
• Are there any log entries pertaining to the problem?
• What was taking place on the computer just before the error occurred?
• What did I expect to happen if the error had not occurred?
• Has anything about the system hardware or software changed recently?

Other questions will reveal themselves as you work to answer these. The important thing to remember here is not these specific questions, but rather to gather as much information as possible. This increases the knowledge you have about this specific problem instance and aids in finding the solution.

As you gather data, never assume that the information obtained from someone else is correct. Observe everything yourself. This can be a major problem if you are working with someone who is at a remote location. Careful questioning is essential, and tools that allow remote access to the system in question are extremely helpful when attempting to confirm the information that you are given.

Tip: When questioning a person at a remote site, never ask leading questions; they will try to be helpful by answering with what they think you want to hear.

At other times the answers you receive will depend upon how much or how little knowledge the person has of Linux and computers in general. When a person knows—or thinks they know—about computers, the answers you receive may contain assumptions that can be difficult to disprove. Rather than ask. "Did you check…," it is better to have the other person actually perform the task required to check the item. And rather than telling the person what they should see, simply have the user explain or describe to you what they do see. Again, remote access to the machine can allow you to confirm the information you are given.

The best problem solvers are those who never take anything for granted. They never assume that the information they have is 100% accurate or complete. When the information you have seems to contradict itself or the symptoms, start over from the beginning as if you have no information at all.

In almost all of the jobs I have had in the computer business, we have always tried to help each other out, and this was true when I was at IBM. I have always been very good at fixing things, and there were times when I would show up to support another CE who was having a particularly difficult time finding the source of a problem. The first thing I would do is assess the situation. I would ask the primary CE what they had done so far to locate the problem. After that, I would start over from the beginning. I always wanted to see the results myself. Many times that paid off because I would observe something that others had missed. In one very strange incident, I fixed a large computer by sitting on it.

This took place while I was an IBM CE in Lima, Ohio, in about 1976. Two of us were installing an IBM System/3, which was smaller than an IBM mainframe, like a 360 or 370, but still large enough to need a room of its own, high voltage power, and significant air cooling.

We had assembled the main CPU and had started to attach the IBM 1403 line printer controller when we ran into the problem. The printer controller was contained in a slightly lower than desktop-height unit to the left of the CPU. That nice large work surface is just the right height to sit on.

We had just bolted the printer controller to the frame of the CPU and were doing one of the very many checks built into the installation instructions. We connected the leads of an Ohm meter between the frame of the CPU and a specific terminal on the power supply of the printer controller. The result was supposed to be an open circuit, that is, infinite resistance, which would indicate that the hot leads of the power supply were not shorted to the frame. In this case, there was a short—zero resistance—which was bad.

There would not have been a spectacular display of noise and fireworks like you see on TV, but it would have been a problem as it would prevent the computer from powering up. Best to catch this while it was still being assembled rather than later. After an hour of trying to find the problem, we were unable to do so. We called the support center for the System/3 in Boca Raton, Florida, and were guided through several further problem determination steps that were unsuccessful.

A bit frustrated, I sat on the printer control unit. Out of the corner of my eye, I saw the needle on the Ohm meter swing to indicate an open circuit. I mentioned this to the other CE and to Vern in Boca Raton, who would later be one of my own mentors when I went down there for a few years as a Course Development Representative (CSR).

We removed the top, where I had perched, from the controller, and with a bit of luck, found that one of the bolts holding the top to the frame of the printer controller had come loose and fallen into the power supply and caused the short. When I sat on the top of the controller, the frame moved just enough to cause the bolt to no longer make the contact required to produce the short. Removing that loose bolt from the power supply fixed the problem.

Vern, who was responsible for the System/3 support at that time, made some changes to the instructions to cover this problem in case it happened again. He also worked with the manufacturing people to ensure that it did not happen again, putting in place a check to ensure that the bolt was properly tightened during the build process.

The thing to remember is to really observe what is going on in all parts of the system. Pay attention to everything, and don't ignore the slightest clue. Sometimes watching  top ,  htop ,  glances , or one of the other utilities used to monitor the internal functioning of the kernel or the network can provide a momentary glimpse of something—a clue—that gets us started in the right direction.

And sometimes it takes just a bit of luck, like sitting on the printer control unit.

Use reasoning skills to take the information from your observations of the symptoms, your knowledge to determine a probable cause for the problem. We discussed the different types of reasoning in some detail in my previous article  Sysadmin careers:  4 problem-solving strategies . The process of reasoning through your observations of the problem, your knowledge, and your past experience is where art and science combine to produce inspiration, intuition, or some other mystical mental insight into the root cause of the problem.

In some cases, this is a fairly easy process. You can see an error code and look up its meaning from the sources available to you. Or perhaps you observe a symptom that is familiar, and you know what steps might resolve it. You can then apply the vast knowledge you have gained by reading about Linux and the documentation provided with Linux to reason your way to the cause of the problem.

In other cases, it can be a very difficult and lengthy part of the problem determination process. These are the types of cases that can be the most difficult—symptoms you have never seen or a problem that is not resolved by any of the methods you have used. It is these difficult ones that require more work and especially more reasoning applied to them.

It helps to remember that the symptom is not the problem. The problem causes the symptom. You want to discover the true problem, not just the symptom.

Now is the time to perform the appropriate repair action. This is usually the simple part. The hard part is what came before—figuring out what to do. After you know the cause of the problem, it is easy to determine the correct repair action to take. The specific action you take will depend upon the cause(s) of the problem.

Remember, we are fixing the root cause, not just trying to get rid of or cover up the symptom.

Make only one change at a time. If there are several actions that can be taken that might correct the cause of a problem, only make the one change or take the one action that is most likely to resolve the root cause. The selection of the corrective action with the highest probability of fixing the problem is what you are trying to do here. Whether it is your own experience telling you which action to take, or the experiences of others, move down the list from highest to lowest probability, one action at a time. Test the results after each action.

After taking some overt repair action, the repair should be tested. This usually means performing the task that failed in the first place, but it could also be a single, simple command that illustrates the problem.

We make a single change, taking one potential corrective action, and then testing the results of that action. This is the only way we can be certain which corrective action fixed the problem. If we were to take several corrective actions and then test one time, there is no way to know which action was responsible for fixing the problem. This is especially important if we want to walk back those ineffective changes we made after finding the solution.

If the repair action has not been successful, you should begin the procedure over again. If there are additional corrective actions you can take, return to that step and continue doing so until you have run out of possibilities or have learned with to a certainty that you are on the wrong track.

Be sure to check the original observed symptoms when testing. It is possible that they have changed due to the action you have taken, and you need to be aware of this in order to make informed decisions during the next iteration of the process. Even if the problem has not been resolved, the altered symptom could be very valuable in determining how to proceed.

As you work through a problem, it will be necessary to iterate through at least some of the steps. If, for example, performing a given corrective action does not resolve the problem, you may need to try another action that has also been known to resolve the problem in the past. Figure 1 shows that you may need to iterate to any previous step in order to continue. It may be necessary to go back to the observation step and gather more information about the problem. I have also found that sometimes it was a good idea to go back to the knowledge step and gather more basic knowledge. This includes reading or rereading manuals and man pages, using search engines, whatever is necessary to gain the knowledge required to continue past the point where I was blocked.

Be flexible, and don't hesitate to step back and start over if nothing else produces some forward progress.

Concluding thoughts

In this article, we have looked at one way to approach fixing problems that applies to many non-technical things as well as to computer hardware and software. What we have discussed here is one algorithm for problem-solving that can be used with the reasoning methodologies we explored in the first article. The flexibility of this particular combination is extremely powerful.

I am not telling you that you "should" use this method. However, if you go all Zen and analyze your own method for solving problems, you will very likely find that it is already very close to the algorithm I describe here. I suggest that you do take the time to analyze your own methods. I think you will find it a productive use of time that will be quite enlightening.

Skills You Need website,  Critical Thinking Skills

Wikipedia,  Reason

Butte College,  Deductive, Inductive, and Abductive Reasoning

Harris, William,  How the Scientific Method Works

Both, David,  The Linux Philosophy for SysAdmins , Ch23.

[ Want to test your sysadmin skills? Take a skills assessment today. ]

David Both is an open source software and GNU/Linux advocate, trainer, writer, and speaker who lives in Raleigh, NC. He is a strong proponent of and evangelist for the "Linux Philosophy." David has been in the IT industry for over 50 years. More about me

Try Red Hat Enterprise Linux

Download it at no charge from the red hat developer program., related content.

26 Expert-Backed Problem Solving Examples – Interview Answers

Published: February 13, 2023

Interview Questions and Answers

Actionable advice from real experts:

Biron Clark

Former Recruiter

Contributor

Dr. Kyle Elliott

Career Coach

Hayley Jukes

Editor-in-Chief

Biron Clark , Former Recruiter

Kyle Elliott , Career Coach

Hayley Jukes , Editor

As a recruiter , I know employers like to hire people who can solve problems and work well under pressure.

 A job rarely goes 100% according to plan, so hiring managers are more likely to hire you if you seem like you can handle unexpected challenges while staying calm and logical.

But how do they measure this?

Hiring managers will ask you interview questions about your problem-solving skills, and they might also look for examples of problem-solving on your resume and cover letter. 

In this article, I’m going to share a list of problem-solving examples and sample interview answers to questions like, “Give an example of a time you used logic to solve a problem?” and “Describe a time when you had to solve a problem without managerial input. How did you handle it, and what was the result?”

• Problem-solving involves identifying, prioritizing, analyzing, and solving problems using a variety of skills like critical thinking, creativity, decision making, and communication.
• Describe the Situation, Task, Action, and Result ( STAR method ) when discussing your problem-solving experiences.
• Tailor your interview answer with the specific skills and qualifications outlined in the job description.
• Provide numerical data or metrics to demonstrate the tangible impact of your problem-solving efforts.

What are Problem Solving Skills? 

Problem-solving is the ability to identify a problem, prioritize based on gravity and urgency, analyze the root cause, gather relevant information, develop and evaluate viable solutions, decide on the most effective and logical solution, and plan and execute implementation. 

Problem-solving encompasses other skills that can be showcased in an interview response and your resume. Problem-solving skills examples include:

• Critical thinking
• Analytical skills
• Decision making
• Research skills
• Technical skills
• Communication skills
• Adaptability and flexibility

Why is Problem Solving Important in the Workplace?

Problem-solving is essential in the workplace because it directly impacts productivity and efficiency. Whenever you encounter a problem, tackling it head-on prevents minor issues from escalating into bigger ones that could disrupt the entire workflow. 

Beyond maintaining smooth operations, your ability to solve problems fosters innovation. It encourages you to think creatively, finding better ways to achieve goals, which keeps the business competitive and pushes the boundaries of what you can achieve. 

Effective problem-solving also contributes to a healthier work environment; it reduces stress by providing clear strategies for overcoming obstacles and builds confidence within teams. 

Examples of Problem-Solving in the Workplace

• Correcting a mistake at work, whether it was made by you or someone else
• Overcoming a delay at work through problem solving and communication
• Resolving an issue with a difficult or upset customer
• Overcoming issues related to a limited budget, and still delivering good work through the use of creative problem solving
• Overcoming a scheduling/staffing shortage in the department to still deliver excellent work
• Troubleshooting and resolving technical issues
• Handling and resolving a conflict with a coworker
• Solving any problems related to money, customer billing, accounting and bookkeeping, etc.
• Taking initiative when another team member overlooked or missed something important
• Taking initiative to meet with your superior to discuss a problem before it became potentially worse
• Solving a safety issue at work or reporting the issue to those who could solve it
• Using problem solving abilities to reduce/eliminate a company expense
• Finding a way to make the company more profitable through new service or product offerings, new pricing ideas, promotion and sale ideas, etc.
• Changing how a process, team, or task is organized to make it more efficient
• Using creative thinking to come up with a solution that the company hasn’t used before
• Performing research to collect data and information to find a new solution to a problem
• Boosting a company or team’s performance by improving some aspect of communication among employees
• Finding a new piece of data that can guide a company’s decisions or strategy better in a certain area

Problem-Solving Examples for Recent Grads/Entry-Level Job Seekers

• Coordinating work between team members in a class project
• Reassigning a missing team member’s work to other group members in a class project
• Adjusting your workflow on a project to accommodate a tight deadline
• Speaking to your professor to get help when you were struggling or unsure about a project
• Asking classmates, peers, or professors for help in an area of struggle
• Talking to your academic advisor to brainstorm solutions to a problem you were facing
• Researching solutions to an academic problem online, via Google or other methods
• Using problem solving and creative thinking to obtain an internship or other work opportunity during school after struggling at first

How To Answer “Tell Us About a Problem You Solved”

When you answer interview questions about problem-solving scenarios, or if you decide to demonstrate your problem-solving skills in a cover letter (which is a good idea any time the job description mentions problem-solving as a necessary skill), I recommend using the STAR method.

STAR stands for:

It’s a simple way of walking the listener or reader through the story in a way that will make sense to them. 

Start by briefly describing the general situation and the task at hand. After this, describe the course of action you chose and why. Ideally, show that you evaluated all the information you could given the time you had, and made a decision based on logic and fact. Finally, describe the positive result you achieved.

Note: Our sample answers below are structured following the STAR formula. Be sure to check them out!

EXPERT ADVICE

Dr. Kyle Elliott , MPA, CHES Tech & Interview Career Coach caffeinatedkyle.com

How can I communicate complex problem-solving experiences clearly and succinctly?

Before answering any interview question, it’s important to understand why the interviewer is asking the question in the first place.

When it comes to questions about your complex problem-solving experiences, for example, the interviewer likely wants to know about your leadership acumen, collaboration abilities, and communication skills, not the problem itself.

Therefore, your answer should be focused on highlighting how you excelled in each of these areas, not diving into the weeds of the problem itself, which is a common mistake less-experienced interviewees often make.

Tailoring Your Answer Based on the Skills Mentioned in the Job Description

As a recruiter, one of the top tips I can give you when responding to the prompt “Tell us about a problem you solved,” is to tailor your answer to the specific skills and qualifications outlined in the job description. 

Once you’ve pinpointed the skills and key competencies the employer is seeking, craft your response to highlight experiences where you successfully utilized or developed those particular abilities. 

For instance, if the job requires strong leadership skills, focus on a problem-solving scenario where you took charge and effectively guided a team toward resolution. 

By aligning your answer with the desired skills outlined in the job description, you demonstrate your suitability for the role and show the employer that you understand their needs.

Amanda Augustine expands on this by saying:

“Showcase the specific skills you used to solve the problem. Did it require critical thinking, analytical abilities, or strong collaboration? Highlight the relevant skills the employer is seeking.”  

Interview Answers to “Tell Me About a Time You Solved a Problem”

Now, let’s look at some sample interview answers to, “Give me an example of a time you used logic to solve a problem,” or “Tell me about a time you solved a problem,” since you’re likely to hear different versions of this interview question in all sorts of industries.

The example interview responses are structured using the STAR method and are categorized into the top 5 key problem-solving skills recruiters look for in a candidate.

1. Analytical Thinking

Situation: In my previous role as a data analyst , our team encountered a significant drop in website traffic.

Task: I was tasked with identifying the root cause of the decrease.

Action: I conducted a thorough analysis of website metrics, including traffic sources, user demographics, and page performance. Through my analysis, I discovered a technical issue with our website’s loading speed, causing users to bounce. 

Result: By optimizing server response time, compressing images, and minimizing redirects, we saw a 20% increase in traffic within two weeks.

2. Critical Thinking

Situation: During a project deadline crunch, our team encountered a major technical issue that threatened to derail our progress.

Task: My task was to assess the situation and devise a solution quickly.

Action: I immediately convened a meeting with the team to brainstorm potential solutions. Instead of panicking, I encouraged everyone to think outside the box and consider unconventional approaches. We analyzed the problem from different angles and weighed the pros and cons of each solution.

Result: By devising a workaround solution, we were able to meet the project deadline, avoiding potential delays that could have cost the company $100,000 in penalties for missing contractual obligations.

3. Decision Making

Situation: As a project manager , I was faced with a dilemma when two key team members had conflicting opinions on the project direction.

Task: My task was to make a decisive choice that would align with the project goals and maintain team cohesion.

Action: I scheduled a meeting with both team members to understand their perspectives in detail. I listened actively, asked probing questions, and encouraged open dialogue. After carefully weighing the pros and cons of each approach, I made a decision that incorporated elements from both viewpoints.

Result: The decision I made not only resolved the immediate conflict but also led to a stronger sense of collaboration within the team. By valuing input from all team members and making a well-informed decision, we were able to achieve our project objectives efficiently.

4. Communication (Teamwork)

Situation: During a cross-functional project, miscommunication between departments was causing delays and misunderstandings.

Task: My task was to improve communication channels and foster better teamwork among team members.

Action: I initiated regular cross-departmental meetings to ensure that everyone was on the same page regarding project goals and timelines. I also implemented a centralized communication platform where team members could share updates, ask questions, and collaborate more effectively.

Result: Streamlining workflows and improving communication channels led to a 30% reduction in project completion time, saving the company $25,000 in operational costs.

5. Persistence 

Situation: During a challenging sales quarter, I encountered numerous rejections and setbacks while trying to close a major client deal.

Task: My task was to persistently pursue the client and overcome obstacles to secure the deal.

Action: I maintained regular communication with the client, addressing their concerns and demonstrating the value proposition of our product. Despite facing multiple rejections, I remained persistent and resilient, adjusting my approach based on feedback and market dynamics.

Result: After months of perseverance, I successfully closed the deal with the client. By closing the major client deal, I exceeded quarterly sales targets by 25%, resulting in a revenue increase of $250,000 for the company.

Tips to Improve Your Problem-Solving Skills

Throughout your career, being able to showcase and effectively communicate your problem-solving skills gives you more leverage in achieving better jobs and earning more money .

So to improve your problem-solving skills, I recommend always analyzing a problem and situation before acting.

 When discussing problem-solving with employers, you never want to sound like you rush or make impulsive decisions. They want to see fact-based or data-based decisions when you solve problems.

Don’t just say you’re good at solving problems. Show it with specifics. How much did you boost efficiency? Did you save the company money? Adding numbers can really make your achievements stand out.

To get better at solving problems, analyze the outcomes of past solutions you came up with. You can recognize what works and what doesn’t.

Think about how you can improve researching and analyzing a situation, how you can get better at communicating, and deciding on the right people in the organization to talk to and “pull in” to help you if needed, etc.

Finally, practice staying calm even in stressful situations. Take a few minutes to walk outside if needed. Step away from your phone and computer to clear your head. A work problem is rarely so urgent that you cannot take five minutes to think (with the possible exception of safety problems), and you’ll get better outcomes if you solve problems by acting logically instead of rushing to react in a panic.

You can use all of the ideas above to describe your problem-solving skills when asked interview questions about the topic. If you say that you do the things above, employers will be impressed when they assess your problem-solving ability.

More Interview Resources

• 3 Answers to “How Do You Handle Stress?”
• How to Answer “How Do You Handle Conflict?” (Interview Question)
• Sample Answers to “Tell Me About a Time You Failed”

About the Author

Biron Clark is a former executive recruiter who has worked individually with hundreds of job seekers, reviewed thousands of resumes and LinkedIn profiles, and recruited for top venture-backed startups and Fortune 500 companies. He has been advising job seekers since 2012 to think differently in their job search and land high-paying, competitive positions. Follow on Twitter and LinkedIn .

Read more articles by Biron Clark

About the Contributor

Kyle Elliott , career coach and mental health advocate, transforms his side hustle into a notable practice, aiding Silicon Valley professionals in maximizing potential. Follow Kyle on LinkedIn .

About the Editor

Hayley Jukes is the Editor-in-Chief at CareerSidekick with five years of experience creating engaging articles, books, and transcripts for diverse platforms and audiences.

Continue Reading

12 Expert-Approved Responses to ‘What Makes You Unique?’ in Job Interviews

15 most common pharmacist interview questions and answers, 15 most common paralegal interview questions and answers, top 30+ funny interview questions and answers, 60 hardest interview questions and answers, 100+ best ice breaker questions to ask candidates, top 20 situational interview questions (& sample answers), 15 most common physical therapist interview questions and answers.

Career Opportunities with Volunteers of America Los Angeles

A great place to work.

Current job opportunities are posted here as they become available.

Case Manager Problem Solving Specialist

VOALA Helping Our Most Vulnerable Change Their Life Stories

Volunteers of America is a non-profit human services organization committed to serving people in need, strengthening families, and building communities. VOALA provides a variety of social services to Los Angeles area communities such as Head Start programs, Upward Bound college prep programs, veterans� services, homeless shelters, low-income housing program as well as drug and alcohol rehabilitation. Learn more at www.voala.org.

JOB SUMMARY AND PURPOSE

The Case Manager (Specialist) � Problem Solving Specialist provides intensive housing crisis response and case management services to eligible clients, meeting participants at least weekly. Using active listening techniques, the Case Manager � Problem Solving Specialist is the primary point of contact to coordinate creative resolutions to a housing crisis � locating both temporary and permanent housing. Located at a VOALA shelter, and working is the field as needed, the Case Manager (Specialist) � Problem Solving Specialist focuses on resolving the housing crisis, but can refer to other resources as needed.

DUTIES AND RESPONSIBILITIES

• As a member of the program case management team, provides information referrals, crisis intervention, and assistance with permanent housing placement for participants
• Assists case managers in conducting the culturally appropriate, comprehensive screenings and assessments to collect functional, environmental, financial, employment, housing, educational, and health information, as appropriate, to develop a Housing Stability Plan
• Meets with participants to learn about family dynamics, and cultural factors that may assist in finding housing inside the participant�s network or family, as a last resort utilizing the resources of the Program to obtain housing, helps participants establish a plan to sustain housing permanently
• Assists in budgeting with participants, to determine what level of assistance (if any) is needed to resolve housing crisis
• Coordinates follow-up services with participants and case management team
• Identifies and locates housing options suitable for homeless participants, including referral to VOALA shelters as appropriate.
• Creates and maintains a housing database linking tenants to apartments
• Communicates with and visits, families, outside service providers and landlords to familiarize them with the program and the unique needs of participants
• Conducts habitability and lead-based paint inspections of housing options as needed
• Works directly (One on One) with landlords on behalf of clients and program
• Develops support systems to meet individual client's housing needs; coordinates and facilitates move-in activities, rental negotiations, and service referrals as needed
• Facilitates the use of community resources to assist both tenants and landlords in the event of problems leading to potential eviction
• Provide service linkages and support systems to ensure identified needs are met, coordinate with outside service providers.
• Continuously works to identify and apply new, creative approaches and solutions for each participant/family
• Additional duties as assigned
• Other duties as required

Qualifications

REQUIREMENTS:

• Must be able to pass a fingerprint clearance, background check, including criminal history, personal references, employment and education verifications
• Bachelor�s Degree in Social Services or related discipline, Or
• Equivalent combination of education and work experience (four years)

EXPERIENCE:

• 2 years of experience as a case manager
• 1 year assisting the homeless find housing
• Experience working with clients with co-morbidities (chronic health, mental health, substance abuse issues, for example)

PREFERRED QUALIFICATIONS:

• 2 years of experience counseling target population
• HMIS navigation
• Bilingual in Spanish

Volunteers of America is an Equal Opportunity/Affirmative Action employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex including sexual orientation and gender identity, national origin, disability, protected Veteran Status, or any other characteristic protected by applicable federal, state, or local law

This employer participates in E-Verify as required by the federal government and will provide the federal government with your Form 1-9 information to confirm that you are authorized to work in the U.S.

If E-Verify cannot confirm that you are authorized to work, this employer is required to give you written instructions and an opportunity to contact Department of Homeland Security (OHS) or Social Security Administration (SSA) so you can begin to resolve the issue before the employer can take any action against you, including terminating your employment.

© 2024 Volunteers of America Los Angeles