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.
Drive clarity and impact at scale by connecting work and workflows to company-wide goals.
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.
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:
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.
Read: How to use problem framing to solve team inefficienciesWhen you and your team are brainstorming different possible solutions, it's important to consider who the problem affects. Go back to the journalistic questions you’re asking: Who is involved in this problem? Make sure these individuals (often referred to as project stakeholders) are involved in the decision making process.
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.
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.
Read: RACI chartTo 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.
Read: What is 8D? A template for efficient problem-solvingIn 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.
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 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.
Read: Understanding the iterative process, with examplesThe 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.
Read: Ask “5 Whys” to get to the root of any problemA 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.
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.
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.