Identify Goal
Define Problem
Define Problem
Gather Data
Define Causes
Identify Options
Clarify Problem
Generate Ideas
Evaluate Options
Generate Ideas
Choose the Best Solution
Implement Solution
Select Solution
Take Action
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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 .
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!
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:
Download the 8D Problem Solving Template
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:
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.
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:
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:
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.
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.
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:
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.
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.
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.
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.
Understand Process Performance (Pp) and Process Performance Index (Ppk) to assess and improve manufacturing processes.…
Choosing between LIFO and FIFO for stock management depends on factors like product nature, market…
Are there any official standards for Six Sigma? While Six Sigma is a well-defined methodology…
In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…
When it comes to business, knowing the value you’re getting for your money is crucial,…
In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…
August 17, 2023 by MindManager Blog
Whether you run a business, manage a team, or work in an industry where change is the norm, it may feel like something is always going wrong. Thankfully, becoming proficient in the problem solving process can alleviate a great deal of the stress that business issues can create.
Understanding the right way to solve problems not only takes the guesswork out of how to deal with difficult, unexpected, or complex situations, it can lead to more effective long-term solutions.
In this article, we’ll walk you through the 5 steps of problem solving, and help you explore a few examples of problem solving scenarios where you can see the problem solving process in action before putting it to work.
When something isn’t working, it’s important to understand what’s at the root of the problem so you can fix it and prevent it from happening again. That’s why resolving difficult or complex issues works best when you apply proven business problem solving tools and techniques – from soft skills, to software.
The problem solving process typically includes:
While skills like active listening, collaboration, and leadership play an important role in problem solving, tools like visual mapping software make it easier to define and share problem solving objectives, play out various solutions, and even put the best fit to work.
Before you can take your first step toward solving a problem, you need to have a clear idea of what the issue is and the outcome you want to achieve by resolving it.
For example, if your company currently manufactures 50 widgets a day, but you’ve started processing orders for 75 widgets a day, you could simply say you have a production deficit.
However, the problem solving process will prove far more valuable if you define the start and end point by clarifying that production is running short by 25 widgets a day, and you need to increase daily production by 50%.
Once you know where you’re at and where you need to end up, these five steps will take you from Point A to Point B:
In practice, you might not hit a home-run with every solution you execute. But the beauty of a repeatable process like problem solving is that you can carry out steps 4 and 5 again by drawing from the brainstorm options you documented during step 2.
The best way to get a sense of how the problem solving process works before you try it for yourself is to work through some simple scenarios.
Here are three examples of how you can apply business problem solving techniques to common workplace challenges.
Building on our original manufacturing example, you determine that your company is consistently short producing 25 widgets a day and needs to increase daily production by 50%.
Since you’d like to gather data and input from both your manufacturing and sales order departments, you schedule a brainstorming session to discover the root cause of the shortage.
After examining four key production areas – machines, materials, methods, and management – you determine the cause of the problem: the material used to manufacture your widgets can only be fed into your equipment once the machinery warms up to a specific temperature for the day.
Your team comes up with three possible solutions.
After weighing the expense of the first two solutions, and conducting some online research, you decide that switching to a comparable but less expensive material that can be worked at a lower temperature is your best option.
You implement your plan, monitor your widget quality and output over the following week, and declare your solution a success when daily production increases by 100%.
Business training is booming and you’ve had to onboard new staff over the past month. Now you learn that several clients have expressed concern about the quality of your recent training sessions.
After speaking with both clients and staff, you discover there are actually two distinct factors contributing to your quality problem:
You could look for a new conference room or re-schedule upcoming training sessions until after your new equipment arrives. But your team collaboratively determines that the best way to mitigate both issues at once is by temporarily renting the high-quality sound and visual system they need.
Using benchmarks that include several weeks of feedback from session attendees, and random session spot-checks you conduct personally, you conclude the solution has worked.
You’ve invested heavily in product marketing, but still can’t meet your sales goals. Specifically, you missed your revenue target by 30% last year and would like to meet that same target this year.
After collecting and examining reams of information from your sales and accounting departments, you sit down with your marketing team to figure out what’s hindering your success in the marketplace.
Determining that your product isn’t competitively priced, you map out two viable solutions.
Since you’re in a hurry for results, you decide to immediately reduce the price of your product and market it accordingly.
When revenue figures for the following quarter show sales have declined even further – and marketing surveys show potential customers are doubting the quality of your product – you revert back to your original pricing, revisit your problem solving process, and implement the market analysis solution instead.
With the valuable information you gain, you finally arrive at just the right product price for your target market and sales begin to pick up. Although you miss your revenue target again this year, you meet it by the second quarter of the following year.
Kickstart your collaborative brainstorming sessions and try MindManager for free today !
MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster.
MindManager® helps individuals, teams, and enterprises bring greater clarity and structure to plans, projects, and processes. It provides visual productivity tools and mind mapping software to help take you and your organization to where you want to be.
Lean Six Sigma Training Certification
September 23rd, 2024
Here’s a fact…
Organizations that are great at solving problems are about 3.5 times more likely to grow their income faster than other companies!
But what’s so crucial about problem-solving that makes such a big impact?
Problem-solving is about finding and fixing issues that stop a company from reaching its goals.
Being good at solving problems is important for businesses to do well and for people to move up in their careers.
Companies that are great at solving problems can:
For people, getting better at solving problems can help them:
Traditional problem-solving approaches often relied on linear thinking and standardized processes . While these methods still have their place, contemporary problem-solving techniques have evolved to meet the demands of our complex, interconnected business world.
Modern problem-solving techniques emphasize:
Adapting to fast-paced, digital environments requires a blend of traditional wisdom and innovative approaches. For instance, while the core principles of Six Sigma remain relevant, we now apply them in conjunction with agile methodologies and digital tools to solve problems more efficiently.
To excel in problem-solving, professionals need to develop a diverse skill set:
By honing these skills and applying the right problem-solving techniques, you can tackle even the most challenging business issues with confidence.
Ready to enhance your problem-solving skills? Get started with our Lean Six Sigma Green Belt training covers essential techniques like Root Cause Analysis and Process Mapping. Enroll now to boost your analytical and creative problem-solving abilities.
Whether you’re troubleshooting a manufacturing issue or optimizing a business process , the fundamental problem-solving procedure remains the same. Let me walk you through the key problem-solving steps that I’ve successfully implemented across various industries.
The first and most crucial step in any problem-solving technique is accurately identifying and defining the problem . In my experience, many organizations rush to solutions without fully understanding the root cause of their issues . To avoid this pitfall, I recommend using these root-cause analysis techniques:
Once you’ve identified the root cause, it’s essential to frame a clear problem statement. This statement should be specific, measurable, and actionable.
For example, instead of saying “Customer satisfaction is low”, a better problem statement would be “Customer satisfaction scores have decreased by 15% in the past quarter, primarily due to longer response times in our customer service department”.
After defining the problem, the next step in the problem-solving procedure is to collect and analyze relevant data . In my work with companies like GE and HP, I’ve found that data-driven decision-making is crucial for effective problem-solving. Here are some data collection methods and analytical tools I frequently use:
With a clear understanding of the problem and relevant data in hand, it’s time to generate potential solutions. This is where creative problem-solving techniques come into play. I often employ a mix of individual and group ideation techniques, such as:
Once you have a list of potential solutions, it’s crucial to evaluate them systematically. In my workshops, I teach various decision-making frameworks , including:
It’s also essential to conduct a thorough risk assessment of each potential solution. This helps in identifying and mitigating any potential negative consequences before implementation.
The final step in the problem-solving process is implementation and monitoring. This involves:
From optimizing manufacturing processes to streamlining business operations, I’ve learned that having a diverse toolkit of problem-solving techniques is crucial for success. In this section, I’ll share some of the most effective individual problem-solving techniques I’ve used and taught in my workshops worldwide.
A few years ago, I worked with a large electronics manufacturer facing significant inventory management challenges . Here’s how we applied multiple techniques to solve their problem:
The result? The company reduced excess inventory by 40% within six months, leading to significant cost savings and improved cash flow.
I’ve seen firsthand how team-based problem-solving techniques can unlock innovative solutions and drive transformative change.
Want to master advanced problem-solving methods for complex organizational challenges? Our Lean Six Sigma Black Belt program delves deep into statistical tools and leadership techniques.
What I’ve learned is that while the core principles of problem-solving remain consistent, their application can vary significantly depending on the industry context. Let’s talk about some industry-specific problem-solving techniques that I’ve found particularly effective in my consulting work.
I worked with a large manufacturing company that was struggling with efficiency and quality issues. Here’s how we applied multiple techniques to solve their problems:
The result? A 40% reduction in defect rates, a 25% improvement in overall equipment effectiveness, and a successful transition into Industry 4.0 practices.
By understanding and applying these industry-specific problem-solving techniques, you can tackle the unique challenges in your field more effectively. Remember, the key is to adapt these methods to your specific context and combine them when necessary for optimal results.
I’ve witnessed firsthand the dramatic shift toward remote and digital work environments. This transition has brought new challenges to the problem-solving landscape and opened up exciting opportunities for innovation.
Tips for Effective Remote Problem-Solving
By adapting our problem-solving techniques to remote and digital environments, we can overcome the challenges and harness the unique advantages of virtual collaboration . In my experience, remote problem-solving can lead to more diverse perspectives and innovative solutions when done right.
Looking to implement effective problem-solving strategies across your entire organization? Our Lean Six Sigma Champion Leadership program equips executives with the skills to drive continuous improvement and foster a culture of problem-solving.
The emergence of new technologies has revolutionized how we approach challenges, offering unprecedented opportunities for efficiency and innovation.
Emerging Technologies in Problem-Solving
These emerging technologies are not just tools; they’re reshaping the very nature of problem-solving in business. As a Six Sigma practitioner, I’ve found that integrating these technologies with traditional problem-solving methods can lead to breakthrough solutions.
For instance, in a recent project with a semiconductor manufacturer, we combined Six Sigma’s DMAIC methodology with AI-driven predictive modeling . This hybrid approach allowed us to not only solve current yield issues but also predict and prevent future problems, resulting in a sustained 20% improvement in overall yield.
As we look to the future, the key to effective problem-solving will be the ability to seamlessly blend human expertise with these advanced technologies. The most successful problem solvers will be those who can harness the power of AI, VR, and big data while still applying critical thinking and creativity.
I can confidently say that problem-solving is not just a skill—it’s a mindset that can be continuously developed and refined . Cultivating strong problem-solving skills can transform careers and drive organizational success.
Let’s look at strategies for developing and improving your problem-solving abilities , drawing from my experiences training thousands of professionals worldwide.
Challenge : Put Your Skills to the Test
I challenge you to take on a problem in your workplace using a technique you’ve never tried before. Perhaps use the “ 5 Whys ” to dig into a recurring issue, or apply the SCAMPER method to innovate a product or process. Share your experience in the comments —I’d love to hear about your results!
Tips for Improving Problem-Solving Skills
Remember, becoming an expert problem solver is a journey, not a destination. As the business landscape evolves, so too must our problem-solving techniques.
By committing to continuous improvement and embracing new challenges, you’ll not only solve the problems of today but be prepared for the challenges of tomorrow.
We’ve covered a wide range of problem-solving techniques, from the analytical rigor of Six Sigma to the creative approaches of design thinking.
We’ve explored how these methods can be applied across various industries and adapted for remote environments. We’ve also looked at emerging trends, showing how AI and big data are reshaping the landscape of problem-solving.
Key takeaways:
Remember, the most effective problem solvers are those who can adapt their approach to the unique challenges they face. Whether you’re troubleshooting a manufacturing issue, optimizing a business process , or tackling a global supply chain challenge, the techniques we’ve discussed provide a robust toolkit for success.
As you move forward in your career, I encourage you to implement these problem-solving techniques in your daily work. Start with small challenges and gradually apply these methods to more complex problems. Share your learnings with your team and create a culture of continuous improvement in your organization.
The ability to solve problems effectively is more than just a skill—it’s a competitive advantage in today’s rapidly changing business landscape. By honing your problem-solving abilities , you’re not just preparing for the challenges of today, but positioning yourself as a leader for the challenges of tomorrow.
Remember, every problem is an opportunity in disguise. Happy problem-solving!
SixSigma.us offers both Live Virtual classes as well as Online Self-Paced training. Most option includes access to the same great Master Black Belt instructors that teach our World Class in-person sessions. Sign-up today!
Virtual Classroom Training Programs Self-Paced Online Training Programs
" * " indicates required fields
Posted on May 29, 2019
Constant disruption has become a hallmark of the modern workforce and organisations want problem solving skills to combat this. Employers need people who can respond to change – be that evolving technology, new competitors, different models for doing business, or any of the other transformations that have taken place in recent years.
In addition, problem solving techniques encompass many of the other top skills employers seek . For example, LinkedIn’s list of the most in-demand soft skills of 2019 includes creativity, collaboration and adaptability, all of which fall under the problem-solving umbrella.
Despite its importance, many employees misunderstand what the problem solving method really involves.
Effective problem solving doesn’t mean going away and coming up with an answer immediately. In fact, this isn’t good problem solving at all, because you’ll be running with the first solution that comes into your mind, which often isn’t the best.
Instead, you should look at problem solving more as a process with several steps involved that will help you reach the best outcome. Those steps are:
Let’s look at each step in a little more detail.
The first step to solving a problem is defining what the problem actually is – sounds simple, right? Well no. An effective problem solver will take the thoughts of everyone involved into account, but different people might have different ideas on what the root cause of the issue really is. It’s up to you to actively listen to everyone without bringing any of your own preconceived notions to the conversation. Learning to differentiate facts from opinion is an essential part of this process.
An effective problem solver will take the opinions of everyone involved into account
The same can be said of data. Depending on what the problem is, there will be varying amounts of information available that will help you work out what’s gone wrong. There should be at least some data involved in any problem, and it’s up to you to gather as much as possible and analyse it objectively.
Once you’ve identified what the real issue is, it’s time to think of solutions. Brainstorming as many solutions as possible will help you arrive at the best answer because you’ll be considering all potential options and scenarios. You should take everyone’s thoughts into account when you’re brainstorming these ideas, as well as all the insights you’ve gleaned from your data analysis. It also helps to seek input from others at this stage, as they may come up with solutions you haven’t thought of.
Depending on the type of problem, it can be useful to think of both short-term and long-term solutions, as some of your options may take a while to implement.
Each option will have pros and cons, and it’s important you list all of these, as well as how each solution could impact key stakeholders. Once you’ve narrowed down your options to three or four, it’s often a good idea to go to other employees for feedback just in case you’ve missed something. You should also work out how each option ties in with the broader goals of the business.
There may be a way to merge two options together in order to satisfy more people.
Only now should you choose which solution you’re going to go with. What you decide should be whatever solves the problem most effectively while also taking the interests of everyone involved into account. There may be a way to merge two options together in order to satisfy more people.
At this point you might be thinking it’s time to sit back and relax – problem solved, right? There are actually two more steps involved if you want your problem solving method to be truly effective. The first is to create an implementation plan. After all, if you don’t carry out your solution effectively, you’re not really solving the problem at all.
Create an implementation plan on how you will put your solution into practice. One problem solving technique that many use here is to introduce a testing and feedback phase just to make sure the option you’ve selected really is the most viable. You’ll also want to include any changes to your solution that may occur in your implementation plan, as well as how you’ll monitor compliance and success.
There’s one last step to consider as part of the problem solving methodology, and that’s communicating your solution . Without this crucial part of the process, how is anyone going to know what you’ve decided? Make sure you communicate your decision to all the people who might be impacted by it. Not everyone is going to be 100 per cent happy with it, so when you communicate you must give them context. Explain exactly why you’ve made that decision and how the pros mean it’s better than any of the other options you came up with.
Employers are increasingly seeking soft skills, but unfortunately, while you can show that you’ve got a degree in a subject, it’s much harder to prove you’ve got proficiency in things like problem solving skills. But this is changing thanks to Deakin’s micro-credentials. These are university-level micro-credentials that provide an authoritative and third-party assessment of your capabilities in a range of areas, including problem solving. Reach out today for more information .
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 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:
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.
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
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.
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.”
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
Related articles.
Home Blog others What is Problem Solving? Process, Techniques, Examples
Whether tackling a technical issue at work or finding our way around a roadblock unnoticed by Google Maps, problem-solving is a daily occurrence for most people. But how prepared are you to overcome life's challenges? Do you rely on a structured process to ensure successful outcomes, or do you navigate through problems impulsively?
Here's the crux: the strength of your problem-solving skills significantly impacts the ease and success of your life, both professionally and personally. Practical problem-solving is a valuable career and life skill. You're in the right place if you're eager to enhance your problem-solving abilities efficiently.
In this blog post, I will delve into what is problem solving the steps, techniques, and exercises of the problem-solving process. Whether seeking to troubleshoot technical issues or navigate life's complexities, mastering organized problem-solving can elevate your capabilities and lead to more favorable outcomes.
First, let me help you understand what is problem solving. Problem-solving is a comprehensive process involving identifying issues, prioritizing based on urgency and severity, analyzing root causes, gathering pertinent Information, devising and assessing solutions, making informed decisions, and planning and executing implementation strategies.
This skill set also encompasses critical thinking, effective communication, active listening, creativity, research, data analysis, risk assessment, continuous learning, and decision-making abilities. Effective problem-solving strategies mitigate potential losses or damages and enhance self-confidence and reputation. Problem-solving is essential in personal and professional contexts as it allows individuals and teams to navigate obstacles, make informed decisions, and drive progress.
Importance:
Now that we have a clear understanding of the problem solving definition as to what is problem solving let us now navigate the problem solving process. Effective problem-solving is a valuable skill sought after by employers in various fields. Here's a breakdown of a common problem-solving process, presented in a pointwise manner:
The first step in the problem-solving process is clearly defining the issue. This involves gathering relevant Information, observing patterns or trends, and understanding the impact of the problem on stakeholders.
Once the problem is identified, it's essential to analyze its root causes and contributing factors. This may involve conducting research, gathering data, and exploring different perspectives to comprehensively understand the situation.
With a clear understanding of the problem solving methods, brainstorming potential solutions is the next step. Encouraging creativity and considering various alternatives can lead to innovative ideas. Evaluating each solution based on feasibility, effectiveness, and alignment with goals and values is crucial.
After generating a list of potential solutions, it's essential to carefully evaluate each option. This involves weighing the pros and cons, considering potential risks and benefits, and assessing the likelihood of success. Consulting with relevant stakeholders or experts can provide valuable insights during this stage.
Based on the evaluation, one or more solutions are the most viable options. It's essential to prioritize solutions that address the root cause of the problem and have the most significant potential for long-term success. Communicating the chosen solution effectively to stakeholders is crucial for garnering support and buy-in.
Once a solution is selected, it's time to put it into action. This involves developing a detailed action plan, allocating resources, and assigning responsibilities. Effective communication, coordination, and monitoring are essential during the implementation phase to ensure smooth execution and timely resolution of the problem.
After implementing the solution, it's essential to monitor its progress and evaluate its effectiveness over time. This may involve collecting feedback, analyzing performance metrics, and making adjustments as needed. Continuous monitoring and review allow for ongoing improvement and refinement of the problem-solving process.
Here's a breakdown of the 5 problem-solving steps for your understanding:
Example: Let's say customer complaints about slow website loading times have increased.
Example: Potential solutions for slow website loading times could include optimizing images, upgrading server capacity, or implementing a content delivery network (CDN).
Example: Upgrading server capacity might be a very effective solution, but it could be expensive. Optimizing images is a more feasible solution that could yield significant improvement.
Example: The website optimization plan might involve tasks like image resizing, code minification, and implementing caching mechanisms.
Example: After website optimization, monitor website loading times and customer feedback to see if the issue has been resolved. If not, repeat the process, considering new solutions based on the learnings from this attempt.
Remember, problem-solving is an iterative process. Be prepared to adapt your approach as you gather more Information and evaluate the effectiveness of your solutions.
Creative problem solving requires careful consideration at each stage. Here are vital things to focus on:
Let us look at problem solving example scenarios in a typical workplace: , example 1: project deadline challenge .
By following these examples of problem-solving skills, you can effectively tackle challenges and achieve successful outcomes. Also, explore KnowledgeHut’ s best online courses for further skill enhancement.
Effective problem-solving techniques are essential for tackling challenges and achieving desired outcomes. Here are some problem solving tools and techniques commonly used in problem-solving:
By incorporating these problem-solving techniques in the workplace, you can approach problems systematically, generate creative solutions, and develop a well-rounded plan for achieving success.
Conquering challenges is a key to professional success, and practical problem-solving equips you to do just that. By following a structured approach, you can transform from a bystander to a solution-oriented individual. This involves gathering Information to clearly define the problem and identify its root cause. Analyzing the situation from various angles and brainstorming freely unlock creative solutions. Evaluating potential solutions ensures you choose the one that aligns with your goals and is feasible to implement. Clear communication and a well-defined plan are crucial for successful execution. Finally, reflecting on the outcome allows you to learn and continuously improve your problem-solving skills, making you an invaluable asset in any environment.
The best method involves identifying the problem, brainstorming solutions, evaluating options, implementing the chosen solution, and assessing outcomes for improvement.
The principles include defining the problem, generating alternatives, evaluating options, implementing solutions, and reviewing outcomes for continuous improvement.
Different types include analytical problem-solving, creative problem-solving, critical thinking, decision-making, and systematic problem-solving.
The significant elements include understanding the problem, devising a plan, executing the plan, and evaluating the results.
The skills encompass critical thinking, decision-making, and analytical reasoning. These abilities aid in identifying, analyzing, and resolving problems effectively.
Abhresh is specialized as a corporate trainer, He has a decade of experience in technical training blended with virtual webinars and instructor-led session created courses, tutorials, and articles for organizations. He is also the founder of Nikasio.com, which offers multiple services in technical training, project consulting, content development, etc.
Avail your free 1:1 mentorship session.
Something went wrong
Share this article, download a pdf version., subscribe to our newsletter, 10 effective problem-solving methods and tools for manufacturers.
Downloaded on: September 18, 2024
• April 30, 2024
Variability of demand, quality management, equipment maintenance, and integration of new technologies : problems are frequent and inevitable, and manufacturers face challenges very often. Acknowledging this reality enables teams to remain vigilant, quickly identify and resolve these difficulties, and constantly improve processes and products alike.
Why focus on problem-solving? In the Lean philosophy , a problem isn't just a problem; it's also, and above all, an opportunity to do better. Rather than hiding or ignoring what's not working, the idea is to face up to it, to find structured methods for optimizing efficiency and quality. For this, there are a number of possible solutions and tools available.
What are the different stages of problem-solving? Which methods and tools are most effective in production environments? And how do you use them?
This article provides all the answers and problem-solving tips.
Tired of scrolling? Download a PDF version for easier offline reading and sharing with coworkers.
To better understand each of these steps, let's take the example of a factory manufacturing automotive components, faced with a sudden rise in the number of defective parts.
The first step is to recognize that a problem exists. This involves observing the symptoms and identifying the gaps between the current state and the desired goal.
The 5 Ws and H tool enables you to identify the problem by collecting factual information on incidents.
After identification, you need to precisely define the problem. This involves determining its scope (using the Four A’s method, for example), representing it clearly, and understanding its impact on operations.
This step aims to analyze the factors contributing to the problem in order to identify its root cause. This is a critical process requiring in-depth examination to avoid treating symptoms alone.
Once the root cause has been identified, it's time to focus on finding solutions. This phase encourages creative problem-solving and innovation from the whole team. They have to explore existing ideas and generate new ones.
Before implementing a solution on a large scale, it is essential to test it in a controlled environment. This enables you to assess its effectiveness in real-life situations and adjust the action plan.
Once you’ve found the best solution, it must be standardized and integrated into the organization's procedures. Documenting the process helps prevent the problem from recurring and facilitates employee training .
1. 8d (eight disciplines problem solving).
8D is a quality approach to solving complex problems requiring in-depth analysis and lasting corrective action.
The method comprises eight steps:
Use case in the manufacturing industry
Problem: Recurrent failure of a major piece of equipment, leading to costly production stoppages.
8D would enable a multi-disciplinary team to systematically identify, analyze, and eliminate the root cause of the failure while implementing sustainable corrective actions.
Also known as the Deming wheel, this systematic, iterative model comprises four stages or cycles: Plan, Do, Check, Act.
The PDCA method helps companies test changes under controlled conditions, evaluate the results, and then implement improvements progressively to optimize production and ensure consistent product quality.
Problem: Variation in the quality of the finished product, which does not always meet standards.
PDCA would address this problem by planning improvements, testing them, evaluating their effectiveness, and adjusting the production process to stabilize product quality.
This Six Sigma method is highly effective in optimizing production processes, reducing variation, and eliminating defects by focusing on data and statistical analysis.
It involves clearly defining the problem (Define), measuring (Measure), and analyzing process data to identify root causes (Analyze), then implementing improvements (Improve) and controlling processes to ensure sustainable quality gains (Control).
Problem: High scrap and rework rates on an assembly line.
DMAIC would be used to specify the problem, measure performance, analyze data to find the cause, implement improvements, and control the process to reduce defects.
This fast, effective method inspired by Lean Management, consists in identifying, analyzing and solving problems directly on the shop floor. It is particularly well suited to fast-paced production environments where immediate detection and resolution are necessary to maintain production continuity and efficiency.
Problem: Frequent safety incidents in the workplace.
QRQC would enable rapid reaction to identify and resolve the causes of such incidents immediately, thereby reducing their frequency and improving overall safety.
The Four A’s method is a structured approach that is designed to systematically address and solve problems within an organization.
It is used where problems need to be solved quickly and efficiently while ensuring that lessons learned are integrated into standard practices.
Problem: Missed delivery deadlines due to production bottlenecks.
The Four A’s method would help to quickly detect bottlenecks, analyze their causes, find and implement effective solutions, and then integrate these changes into regular operations to improve on-time delivery.
The choice of problem-solving method depends on several factors:
Now it's time for the problem-solving tools! These will help structure the process and keep it moving in the right direction.
This problem-solving technique, created by Toyota founder Sakichi Toyoda, involves asking the question "Why?" five times until the root cause of a given problem is revealed. It's a simple but powerful tool for finding root causes.
A factory has a problem with late delivery of finished products:
Also known as the "fishbone diagram" or "5M", this tool developed by Kaoru Ishikawa helps to systematically visualize all the potential causes of a specific problem, as well as the contributing factors.
Causes are divided into 5 main categories.
A factory encounters a problem with a drop in product quality:
This evolution of the Ishikawa diagram focuses on not five, but seven major problem areas: Manpower, Method, Materials, Environment, Equipment, Management, Measurement.
A factory is experiencing machine failure problems:
The Pareto or 80/20 principle is very useful for focusing on the problems that will have the greatest impact once solved, and for making informed decisions.
In a factory producing electronic components, 80% of production defects stem from just 20% of the manufacturing processes.
By analyzing production data, the company could discover that the majority of defects are linked to errors in the soldering and PCB inspection stages. These two stages, although representing a small part of the total manufacturing process, are crucial and require special attention to reduce the overall number of defects.
This tool helps gather comprehensive information on a problem by answering these key questions: Who, What, Where, When, Why, and How. Thus, it provides an in-depth understanding of the situation.
There is a delay in production at a furniture manufacturing plant:
Other tools can also be useful for structuring problem-solving methods:
Integrate problem-solving into daily routines.
Instead of seeing problem-solving as a separate activity, integrate it into daily routines. For example, set up SIM meetings to discuss ongoing problems as a group and monitor progress on solutions.
Adopt a Daily Management System (DMS) like UTrakk to quickly identify problems, track corrective actions, facilitate collaboration between teams, and document solutions in a centralized repository.
Define Lean KPIs that measure the effectiveness of the problem-solving process (average time to solve the problem, problem recurrence rate, and impact of solutions on business performance).
To understand problems, you need to go where value is created. Encourage managers to go on the shop floor to directly observe processes, interact with operators, and identify possible improvements.
Form teams with members from different departments to tackle complex problem-solving. Integrating different angles, perspectives, and expertise broadens the point of view on the subject, enriches the analysis, and generates more creative ideas.
In addition to basic training, use mentoring and coaching to develop problem-solving skills . Experienced employees can guide less experienced ones, sharing their know-how.
When a problem is solved, conduct a post-mortem to discuss what went well, what didn't, and how processes can be improved.
Tracking and evaluating each solution implemented allows you to adjust strategies as needed, learn from past experiences, and foster continuous improvement .
Using organized methods and analytical tools to tackle challenges is essential for manufacturers seeking to improve operational efficiency and product quality. UTrakk DMS is the perfect solution for this structured approach to daily problem-solving. With its multiple functionalities – rituals, actions, dashboards, and more – this Daily Management System can adapt to any problem-solving method to optimize every step of the process. Once a solution is standardized, it can be documented in UTrakk’s Knowledge Center to ensure compliance and prevent recurrence.
Adopting these problem-solving techniques not only enables manufacturers to respond effectively to today's challenges, but it also lays the foundations for continuous improvement, ensuring their competitiveness in an ever-changing industrial environment .
What are the key problem-solving methods for manufacturers.
The key problem-solving methods for manufacturers include Lean manufacturing, Six Sigma, and the PDCA (Plan-Do-Check-Act) cycle. These methodologies focus on eliminating waste, optimizing processes, and implementing continuous improvement to enhance operational efficiency.
Manufacturers can effectively implement Lean principles by identifying and eliminating waste, optimizing workflows, and improving overall efficiency through techniques like Kanban and 5S. Training employees and involving them in the continuous improvement process are also critical steps.
Six Sigma is important in manufacturing because it provides a data-driven approach for reducing defects and variability in processes. This methodology helps in improving product quality and operational efficiency by following the DMAIC (Define-Measure-Analyze-Improve-Control) framework.
Technology plays a crucial role in enhancing problem-solving in manufacturing. Digital twins, augmented reality, and collaborative robotics are technologies that help improve precision, efficiency, and safety, facilitating better decision-making and process optimization.
Continuous improvement practices offer several benefits, including increased operational efficiency, reduced waste and costs, and improved employee engagement and customer satisfaction. These practices encourage a proactive approach to addressing inefficiencies and fostering innovation.
In addition to providing the UTrakk solution, Proaction International supports you in implementing the best problem-solving methods and helps you achieve operational excellence.
Writer and editorial manager for about 15 years, Adeline is passionate about human behavior and communication dynamics. At Proaction International, she covers topics ranging from Industry 5.0 to operational excellence, with a focus on leadership development. This expertise enables her to offer insights and advice on employee engagement and continuous improvement of managerial skills.
Kefor maximizes its performance by optimizing manager skills, le goupe maurice: motivate and retain talents by focusing on the leadership development of managers.
© 2023 Proaction International Inc. All rights reserved. Terms of Use | Privacy Notice | Cookie Notice
What’s life without its challenges? All of us will at some point encounter professional and personal hurdles. That might mean resolving a conflict with coworkers or making a big life decision. With effective problem solving skills, you’ll find tricky situations easier to navigate, and welcome challenges as opportunities to learn, grow and thrive.
In this guide, we dive into the importance of problem solving skills and look at examples that show how relevant they are to different areas of your life. We cover how to find creative solutions and implement them, as well as ways to refine your skills in communication and critical thinking. Ready to start solving problems? Read on.
Before we cover strategies for improving problem solving skills, it’s important to first have a clear understanding of the problem solving process. Here are the steps in solving a problem:
There’s more to problem solving than coming up with a quick fix. Effective problem solving requires wide range of skills and abilities, such as:
Problem solving skills in the workplace are invaluable, whether you need them for managing a team, dealing with clients or juggling deadlines. To get a better understanding of how you might use these skills in real-life scenarios, here are some problem solving examples that are common in the workplace.
Analytical thinking is something that comes naturally to some, while others have to work a little harder. It involves being able to look at problem solving from a logical perspective, breaking down the issues into manageable parts.
Quality control: in a manufacturing facility, analytical thinking helps identify the causes of product defects in order to pinpoint solutions.
Market research: marketing teams rely on analytical thinking to examine consumer data, identify market trends and make informed decisions on ad campaigns.
Critical thinkers are able to approach problems objectively, looking at different viewpoints without rushing to a decision. Critical thinking is an important aspect of problem solving, helping to uncover biases and assumptions and weigh up the quality of the information before making any decisions.
Making decisions is often the hardest part of problem solving. How do you know which solution is the right one? It involves evaluating information, considering potential outcomes and choosing the most suitable option. Effective problem solving relies on making well-informed decisions.
Research skills are pivotal when it comes to problem solving, to ensure you have all the information you need to make an informed decision. These skills involve searching for relevant data, critically evaluating information sources, and drawing meaningful conclusions.
A little creative flair goes a long way. By thinking outside the box, you can approach problems from different angles. Creative thinking involves combining existing knowledge, experiences and perspectives in new and innovative ways to come up with inventive solutions.
It’s not always easy to work with other people, but collaboration is a key element in problem solving, allowing you to make use of different perspectives and areas of expertise to find solutions.
Being able to mediate conflicts is a great skill to have. It involves facilitating open communication, understanding different perspectives and finding solutions that work for everyone. Conflict resolution is essential for managing any differences in opinion that arise.
Risk management is essential across many workplaces. It involves analysing potential threats and opportunities, evaluating their impact and implementing strategies to minimise negative consequences. Risk management is closely tied to problem solving, as it addresses potential obstacles and challenges that may arise during the problem solving process.
Effective communication is a skill that will get you far in all areas of life. When it comes to problem solving, communication plays an important role in facilitating collaboration, sharing insights and ensuring that all stakeholders have the same expectations.
Ready to improve your problem solving skills? In this section we explore strategies and techniques that will give you a head start in developing better problem solving skills.
Developing a problem solving mindset will help you tackle challenges effectively . Start by accepting problems as opportunities for growth and learning, rather than as obstacles or setbacks. This will allow you to approach every challenge with a can-do attitude.
Patience is also essential, because it will allow you to work through the problem and its various solutions mindfully. Persistence is also important, so you can keep adapting your approach until you find the right solution.
Finally, don’t forget to ask questions. What do you need to know? What assumptions are you making? What can you learn from previous attempts? Approach problem solving as an opportunity to acquire new skills . Stay curious, seek out solutions, explore new possibilities and remain open to different problem solving approaches.
There’s no point trying to solve a problem you don’t understand. To analyse a problem effectively, you need to be able to define it. This allows you to break it down into smaller parts, making it easier to find causes and potential solutions. Start with a well-defined problem statement that is precise and specific. This will help you focus your efforts on the core issue, so you don’t waste time and resources on the wrong concerns.
Critical thinking and creativity are both important when it comes to looking at the problem objectively and thinking outside the box. Critical thinking encourages you to question assumptions, recognise biases and seek evidence to support your conclusions. Creative thinking allows you to look at the problem from different angles to reveal new insights and opportunities.
Research and decision-making skills are pivotal in problem solving as they enable you to gather relevant information, analyse options and choose the best course of action. Research provides the information and data needed, and ensures that you have a comprehensive understanding of the problem and its context. Effective decision-making is about selecting the solution that best addresses the problem.
Being able to work with others is one of the most important skills to have at work. Collaboration skills enable everyone to work effectively as a team, share their perspectives and collectively find solutions.
Once you’ve overcome a challenge, take the time to look back with a critical eye. How effective was the outcome? Could you have tweaked anything in your process? Learning from past experiences is important when it comes to problem solving. It involves reflecting on both successes and failures to gain insights, refine strategies and make more informed decisions in the future.
Problem-solving tools and resources are a great help when it comes to navigating complex challenges. These tools offer structured approaches, methodologies and resources that can streamline the process.
Practice makes perfect! Using your skills in real life allows you to refine them, adapt to new challenges and build confidence in your problem solving capabilities. Make sure to try out these skills whenever you can.
Effectively showcasing your problem solving skills on your resumé is a great way to demonstrate your ability to address challenges and add value to a workplace. We'll explore how to demonstrate problem solving skills on your resumé, so you stand out from the crowd.
A resumé summary is your introduction to potential employers and provides an opportunity to succinctly showcase your skills. The resumé summary is often the first section employers read. It offers a snapshot of your qualifications and sets the tone for the rest of your resumé.
Your resumé summary should be customised for different job applications, ensuring that you highlight the specific problem solving skills relevant to the position you’re applying for.
Example 1: Project manager with a proven track record of solving complex operational challenges. Skilled in identifying root causes, developing innovative solutions and leading teams to successful project completion.
Example 2: Detail-oriented data analyst with strong problem solving skills. Proficient in data-driven decision-making, quantitative analysis and using statistical tools to solve business problems.
The experience section of your resumé presents the perfect opportunity to demonstrate your problem solving skills in action.
The skills section of your resumé should showcase your top abilities, including problem solving skills. Here are some tips for including these skills.
Including a dedicated section for projects or case studies in your resumé allows you to provide specific examples of your problem solving skills in action. It goes beyond simply listing skills, to demonstrate how you are able to apply those skills to real-world challenges.
Example – Data Analysis
Case Study: Market Expansion Strategy
A well-crafted cover letter is your first impression on any potential employer. Integrating problem solving skills can support your job application by showcasing your ability to address challenges and contribute effectively to their team. Here’s a quick run-down on what to include:
Problem solving skills are essential in all areas of life, enabling you to overcome challenges, make informed decisions, settle conflicts and drive innovation. We've explored the significance of problem solving skills and how to improve, demonstrate and leverage them effectively. It’s an ever-evolving skill set that can be refined over time.
By actively incorporating problem solving skills into your day-to-day, you can become a more effective problem solver at work and in your personal life as well.
Common problem solving techniques include brainstorming, root cause analysis, SWOT analysis, decision matrices, the scientific method and the PDCA (Plan-Do-Check-Act) cycle. These techniques offer structured approaches to identify, analyse and address problems effectively.
Improving critical thinking involves practising skills such as analysis, evaluation and problem solving. It helps to engage in activities like reading, solving puzzles, debating and self-reflection.
Common obstacles to problem solving include biases, lack of information or resources, and resistance to change. Recognising and addressing these obstacles is essential for effective problem solving.
To overcome resistance to change, it's essential to communicate the benefits of the proposed solution clearly, involve stakeholders in the decision-making process, address concerns and monitor the implementation's progress to demonstrate its effectiveness.
Problem solving skills are highly valuable in a career as they enable you to navigate challenges, make informed decisions, adapt to change and contribute to innovation and efficiency. These skills enhance your professional effectiveness and can lead to career advancement and increased job satisfaction.
Explore related topics, subscribe to career advice.
The first step to solving a problem is to define the problem precisely. It is the heart of problem-solving.
Root cause analysis is the second important element of problem-solving in quality management. The reason is if you don't know what the problem is, you can never solve the exact problem that is hurting the quality.
Manufacturers have a variety of problem-solving tools at hand. However, they need to know when to use which tool in a manner that is appropriate for the situation. In this article, we discuss 7 tools including:
The model introduced by Ishikawa (also known as the fishbone diagram) is considered one of the most robust methods for conducting root cause analysis. This model uses the assessment of the 6Ms as a methodology for identifying the true or most probable root cause to determine corrective and preventive actions. The 6Ms include:
Related Training: Fishbone Diagramming
The Pareto Chart is a series of bars whose heights reflect the frequency or impact of problems. On the Chart, bars are arranged in descending order of height from left to right, which means the categories represented by the tall bars on the left are relatively more frequent than those on the right.
Related Training: EFFECTIVE INVESTIGATIONS AND CORRECTIVE ACTIONS (CAPA) Establishing and resolving the root causes of deviations, problems and failures
This model uses the 5 Why by asking why 5 times to find the root cause of the problem. It generally takes five iterations of the questioning process to arrive at the root cause of the problem and that's why this model got its name as 5 Whys. But it is perfectly fine for a facilitator to ask less or more questions depending on the needs.
Related training: Accident/Incident Investigation and Root Cause Analysis
Process | Failure | Effect | S | Causes | O | D | RPN |
---|---|---|---|---|---|---|---|
FMEA is a technique used to identify process and product problems before they occur. It focuses on how and when a system will fail, not if it will fail. In this model, each failure mode is assessed for:
A combination of the three scores produces a risk priority number (RPN). The RPN is then provided a ranking system to prioritize which problem must gain more attention first.
Related Training: Failure Mode Effects Analysis
A scatter diagram also known as a scatter plot is a graph in which the values of two variables are plotted along two axes, the pattern of the resulting points revealing any correlation present.
To use scatter plots in root cause analysis, an independent variable or suspected cause is plotted on the x-axis and the dependent variable (the effect) is plotted on the y-axis. If the pattern reflects a clear curve or line, it means they are correlated. If required, more sophisticated correlation analyses can be continued.
Related Training: Excel Charting Basics - Produce Professional-Looking Excel Charts
Also known as KJ Diagram, this model is used to represent the structure of big and complex factors that impact a problem or a situation. It divides these factors into small classifications according to their similarity to assist in identifying the major causes of the problem.
The Fault Tree Analysis uses Boolean logic to arrive at the cause of a problem. It begins with a defined problem and works backward to identify what factors contributed to the problem using a graphical representation called the Fault Tree. It takes a top-down approach starting with the problem and evaluating the factors that caused the problem.
Finding the root cause isn't an easy because there is not always one root cause. You may have to repeat your experiment several times to arrive at it to eliminate the encountered problem. Using a scientific approach to solving problem works. So, its important to learn the several problem-solving tools and techniques at your fingertips so you can use the ones appropriate for different situations.
P&PC, SPC/6Sigma, Failure Investigation, Root Cause Analysis, PDCA, DMAIC, A3 This webinar will define what are the US FDA's expectation for Production and Process Control / Product Realization, the use of statistical tehniques, 6 sigma, SPC, for establishing, controlling , and verifying the acceptability of process capability and product characteristics, product acceptance or validation and other studies. Non-conformance, OOS, deviations Failure Investigations, and Root Cause Analysis, PDCA, DMAIC, and similar project drivers to improvement, A# and similar dash boards.
Accident/Incident Investigation and Root Cause Analysis If a major workplace injury or illness occurred, what would you do? How would you properly investigate it? What could be done to prevent it from happening again? A properly executed accident/incident investigation drives to the root causes of the workplace accident to prevent a repeat occurrence. A good accident/incident investigation process includes identifying the investigation team, establishing/reviewing written procedures, identifying root causes and tracking of all safety hazards found to completion.
Root Cause Analysis - The Heart of Corrective Action This presentation will explain the importance of root cause analysis and how it fits into an effective corrective and preventive action system. It will cover where else in your quality management system root cause analysis can be used and will give examples of some of the techniques for doing an effective root cause analysis. Attendees will learn how root cause analysis can be used in process control.
Addressing Non-Conformances using Root Cause Analysis (RCA) RCA assumes that systems and events are interrelated. An action in one area triggers an action in another, and another, and so on. By tracing back these actions, you can discover where the issue started and how it grew into the problem you're now facing.
Risk Management Under ISO 14971 ISO 14971:2019 is the definitive standard for risk management for medical devices and IVDs. The standard lays out a comprehensive approach to managing risks in the life sciences. The course will discuss practical approaches to complying with the standard.
Introduction to Root Cause Investigation for CAPA If you have reoccurring problems showing up in your quality systems, your CAPA system is not effective and you have not performed an in-depth root cause analysis to be able to detect through proper problem solving tools and quality data sources, the true root cause of your problem. Unless you can get to the true root cause of a failure, nonconformity, defect or other undesirable situation, your CAPA system will not be successful.
Root Cause Analysis and CAPA Controls for a Compliant Quality System In this CAPA webinar, learn various regulations governing Corrective and Preventive Actions (CAPA) and how organization should collect information, analyze information, identify, investigate product and quality problems, and take appropriate and effective corrective and/or preventive action to prevent their recurrence.
How to Design and Implement a Dynamic Control Plan This webinar training will discuss how to design a dynamic control plan that combines FMEA and the control plan by extending the FMEA to encompass the elements of the control plan and create a living document that helps to drive continual improvement.
An Easy to Implement Integrated Risk Management Approach Compliant with ISO 14971 This integrated risk management training for medical devices will discuss how to incorporate risk management as per ISO 14971 guidelines in all phases of medical device development. It will highlight the documentation needed to support the decisions made as part of the risk management process.
The Use and Mis-use of FMEA in Medical Device Risk Management The presentation will discuss the proper use of FMEA in risk management and how to recognize and avoid the traps associated with this tool in order to have a more efficient risk management process. Most medical device manufacturers use FMEA as a part of their risk management system. Most medical device manufacturers use FMEA as a part of their risk management system.
Root Cause Analysis for CAPA Management (Shutting Down the Alligator Farm) Emphasis will be placed on realizing system interactions and cultural environment that often lies at the root of the problem and prevents true root cause analysis. This webinar will benefit any organization that wants to improve the effectiveness of their CAPA and failure investigation processes.
Root Cause Analysis for Corrective and Preventive Action (CAPA) The Quality Systems Regulation (21 CFR 820) and the Quality Management Standard for Medical Devices (ISO 13485:2003), require medical device companies to establish and maintain procedures for implementing corrective and preventive action (CAPA) as an integral part of the quality system.
Strategies for an Effective Root Cause Analysis and CAPA Program This webinar will provide valuable assistance to all regulated companies, a CAPA program is a requirement across the Medical Device, Diagnostic, Pharmaceutical, and Biologics fields. This session will discuss the importance, requirements, and elements of a root cause-based CAPA program, as well as detailing the most effective ways to determine root cause and describing the uses of CAPA data.
This piece of content and any of its enclosures, attachments or appendices, references are created to provide solely for information purpose. ComplianceOnline has made all effort to provide accurate information concerning the subject matter covered. This content is created from interpretation, and understanding of relevant and applicable information and it is not all inclusive. It can be best used in conjunction with your professional judgment and discretion.
However, this piece of content and any other ancillary items disseminated in connection with same are not necessarily prepared by a person licensed to practice law in a particular jurisdiction. This piece of content is not a substitute for the advice of an attorney. If you require legal or other expert advice, you should seek the services of a competent attorney or other professional.
ComplianceOnline necessarily is not, cannot and will not be liable for any claims, damages, or regulatory legal proceedings initiated as a consequence of you using whole or any part of the content present in this document. If any action, claim for damages, or regulatory proceedings is commenced against ComplianceOnline as a consequence of your use of this document, then and in that event, you agree to indemnify ComplianceOnline for such claims, and for any attorney's fees expended by ComplianceOnline in connection with defense of same.
Format attachments.
You'll find several kinds of fields in your grant application forms - check boxes, dates, data entry fields, and attachments. This page provides guidance on attachments: documents that are prepared outside the grant application using whatever editing software you desire (e.g., Microsoft Word), converted to PDF format, and then added or uploaded to your application. We require PDF format to preserve document formatting and a consistent reading experience for reviewers and staff.
We have very specific attachment formatting requirements. Failure to follow these requirements may lead to application errors upon submission or withdrawal of your application from funding consideration.
A PDF that has fillable fields, electronic signatures, text boxes or images inserted, becomes layered with each of these elements representing a layer. The existence of these layers interferes with the handling of the documents in eRA systems. Consequently, PDF documents included in applications, progress reports, and other information collected in eRA Commons must be flattened. A flattened PDF is simply one in which all the layers are merged together into a single flat layer. Many simple PDFs are already flattened - all the information is contained in a single layer. Uploading a PDF that isn’t flattened may result in an eRA Commons error message. You will need to replace your PDF with a flattened version to complete the submission process.
Adherence to font size, type density, line spacing, and text color requirements is necessary to ensure readability and fairness. Although font requirements apply to all attachments, they are most important and most heavily scrutinized in attachments with page limits.
Text in your attachments must follow these minimum requirements:
Legibility is of paramount importance. Applications that include PDF attachments that do not conform to the minimum requirements listed above may be withdrawn from consideration.
IMAGES
VIDEO
COMMENTS
The problem-solving process typically includes the following steps: Identify the issue: Recognize the problem that needs to be solved. Analyze the situation: Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present. Generate potential solutions: Brainstorm a list of possible ...
Problem-solving tools refer to strategies that can help determine the cause of a problem and identify the best solutions available. The first step in addressing an issue at work is to outline your objectives. Once you establish the cause, you can isolate variables that can help contribute to a potential solution.
18. Open Space Technology. Open Space Technology is a method for large groups to create a problem-solving agenda around a central theme. It works best when your group is comprised of subject-matter experts and experienced individuals with a sufficient stake in the problem.
Finding a suitable solution for issues can be accomplished by following the basic four-step problem-solving process and methodology outlined below. Step. Characteristics. 1. Define the problem. Differentiate fact from opinion. Specify underlying causes. Consult each faction involved for information. State the problem specifically.
7. Solution evaluation. 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.
In insight problem-solving, the cognitive processes that help you solve a problem happen outside your conscious awareness. 4. Working backward. Working backward is a problem-solving approach often ...
The 7 steps to problem-solving. When it comes to problem-solving there are seven key steps that you should follow: define the problem, disaggregate, prioritize problem branches, create an analysis plan, conduct analysis, synthesis, and communication. 1. Define the problem. Problem-solving begins with a clear understanding of the issue at hand.
Creative problem solving (CPS) is actually a formal process formulated by Sidney Parnes and Alex Faickney Osborn, who is thought of as the father of traditional brainstorming (and the "O" in famous advertising agency BBDO).. Their creative problem solving process emphasizes several things, namely:. Separate ideation from evaluation.When you brainstorm creative ideas, have a separate time for ...
7. Work backward. Sometimes the best way to solve a problem is to work backward to solve it. This can be helpful if you need to recreate specific events to locate the root cause of a problem. For example, a car manufacturer may want to produce a vehicle that is better than their competitor's newest model.
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.".
Problem solving software is the best way to take advantage of multiple problem solving tools in one platform. While some software programs are geared toward specific industries or processes - like manufacturing or customer relationship management, for example - others, like MindManager , are purpose-built to work across multiple trades ...
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.
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.
The problem solving process typically includes: Pinpointing what's broken by gathering data and consulting with team members. Figuring out why it's not working by mapping out and troubleshooting the problem. Deciding on the most effective way to fix it by brainstorming and then implementing a solution. While skills like active listening ...
Problem solving techniques helps find and fix issues that hinder a company's growth. It helps businesses to do well and people to move up. ... For example, instead of saying "Customer satisfaction is low", a better problem statement would be "Customer satisfaction scores have decreased by 15% in the past quarter, primarily due to longer ...
Instead, you should look at problem solving more as a process with several steps involved that will help you reach the best outcome. Those steps are: Define the problem. List all the possible solutions. Evaluate the options. Select the best solution. Create an implementation plan. Communicate your solution.
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.
Brainstorm options to solve the problem. Select an option. Create an implementation plan. Execute the plan and monitor the results. Evaluate the solution. Read more: Effective Problem Solving Steps in the Workplace. 2. Collaborative. This approach involves including multiple people in the problem-solving process.
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 ...
Problem-solving is a comprehensive process involving identifying issues, prioritizing based on urgency and severity, analyzing root causes, gathering pertinent Information, devising and assessing solutions, making informed decisions, and planning and executing implementation strategies.
Identify the problem. The first step is to recognize that a problem exists. This involves observing the symptoms and identifying the gaps between the current state and the desired goal. The 5 Ws and H tool enables you to identify the problem by collecting factual information on incidents. Example.
Example 1: Project manager with a proven track record of solving complex operational challenges. Skilled in identifying root causes, developing innovative solutions and leading teams to successful project completion. Example 2: Detail-oriented data analyst with strong problem solving skills.
The first step to solving a problem is to define the problem precisely. It is the heart of problem-solving. Root cause analysis is the second important element of problem-solving in quality management. The reason is if you don't know what the problem is, you can never solve the exact problem that is hurting the quality.
Below are some practical activities to implement that can foster creative problem-solving skills in students. Why Early Development of Creative Problem-Solving Skills Matters. Instilling creative problem-solving skills from a young age can have lasting benefits that extend well beyond the classroom. Here are some of the key advantages: 1.
You'll find several kinds of fields in your grant application forms - check boxes, dates, data entry fields, and attachments. This page provides guidance on attachments: documents that are prepared outside the grant application using whatever editing software you desire (e.g., Microsoft Word), converted to PDF format, and then added or uploaded to your application.