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.
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…
You might associate problem-solving with the math exercises that a seven-year-old would do at school. But problem-solving isn’t just about math — it’s a crucial skill that helps everyone make better decisions in everyday life or work.
Problem-solving involves finding effective solutions to address complex challenges, in any context they may arise.
Unfortunately, structured and systematic problem-solving methods aren’t commonly taught. Instead, when solving a problem, PMs tend to rely heavily on intuition. While for simple issues this might work well, solving a complex problem with a straightforward solution is often ineffective and can even create more problems.
In this article, you’ll learn a framework for approaching problem-solving, alongside how you can improve your problem-solving skills.
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.
Problem-solving begins with a clear understanding of the issue at hand. Without a well-defined problem statement, confusion and misunderstandings can hinder progress. It’s crucial to ensure that the problem statement is outcome-focused, specific, measurable whenever possible, and time-bound.
Additionally, aligning the problem definition with relevant stakeholders and decision-makers is essential to ensure efforts are directed towards addressing the actual problem rather than side issues.
Complex issues often require deeper analysis. Instead of tackling the entire problem at once, the next step is to break it down into smaller, more manageable components.
Various types of logic trees (also known as issue trees or decision trees) can be used to break down the problem. At each stage where new branches are created, it’s important for them to be “MECE” – mutually exclusive and collectively exhaustive. This process of breaking down continues until manageable components are identified, allowing for individual examination.
The decomposition of the problem demands looking at the problem from various perspectives. That is why collaboration within a team often yields more valuable results, as diverse viewpoints lead to a richer pool of ideas and solutions.
The next step involves prioritization. Not all branches of the problem tree have the same impact, so it’s important to understand the significance of each and focus attention on the most impactful areas. Prioritizing helps streamline efforts and minimize the time required to solve the problem.
For prioritized components, you may need to conduct in-depth analysis. Before proceeding, a work plan is created for data gathering and analysis. If work is conducted within a team, having a plan provides guidance on what needs to be achieved, who is responsible for which tasks, and the timelines involved.
Data gathering and analysis are central to the problem-solving process. It’s a good practice to set time limits for this phase to prevent excessive time spent on perfecting details. You can employ heuristics and rule-of-thumb reasoning to improve efficiency and direct efforts towards the most impactful work.
After each individual branch component has been researched, the problem isn’t solved yet. The next step is synthesizing the data logically to address the initial question. The synthesis process and the logical relationship between the individual branch results depend on the logic tree used.
The last step is communicating the story and the solution of the problem to the stakeholders and decision-makers. Clear effective communication is necessary to build trust in the solution and facilitates understanding among all parties involved. It ensures that stakeholders grasp the intricacies of the problem and the proposed solution, leading to informed decision-making.
While problem-solving has traditionally been associated with fields like engineering and science, today it has become a fundamental skill for individuals across all professions. In fact, problem-solving consistently ranks as one of the top skills required by employers.
Problem-solving techniques can be applied in diverse contexts:
Despite the variation in domains and contexts, the fundamental approach to solving these questions remains the same. It starts with gaining a clear understanding of the problem, followed by decomposition, conducting analysis of the decomposed branches, and synthesizing it into a result that answers the initial problem.
Let’s now explore some examples where we can apply the problem solving framework.
Problem: In the production of electronic devices, you observe an increasing number of defects. How can you reduce the error rate and improve the quality?
Before delving into analysis, you can deprioritize branches that you already have information for or ones you deem less important. For instance, while transportation delays may occur, the resulting material degradation is likely negligible. For other branches, additional research and data gathering may be necessary.
Once results are obtained, synthesis is crucial to address the core question: How can you decrease the defect rate?
While all factors listed may play a role, their significance varies. Your task is to prioritize effectively. Through data analysis, you may discover that altering the equipment would bring the most substantial positive outcome. However, executing a solution isn’t always straightforward. In prioritizing, you should consider both the potential impact and the level of effort needed for implementation.
By evaluating impact and effort, you can systematically prioritize areas for improvement, focusing on those with high impact and requiring minimal effort to address. This approach ensures efficient allocation of resources towards improvements that offer the greatest return on investment.
Problem : What should be my next job role?
When breaking down this problem, you need to consider various factors that are important for your future happiness in the role. This includes aspects like the company culture, our interest in the work itself, and the lifestyle that you can afford with the role.
However, not all factors carry the same weight for us. To make sense of the results, we can assign a weight factor to each branch. For instance, passion for the job role may have a weight factor of 1, while interest in the industry may have a weight factor of 0.5, because that is less important for you.
By applying these weights to a specific role and summing the values, you can have an estimate of how suitable that role is for you. Moreover, you can compare two roles and make an informed decision based on these weighted indicators.
This framework provides the foundation and guidance needed to effectively solve problems. However, successfully applying this framework requires the following:
Problem-solving requires practice and a certain mindset. The more you practice, the easier it becomes. Here are some strategies to enhance your skills:
Problem-solving extends far beyond mathematics or scientific fields; it’s a critical skill for making informed decisions in every area of life and work. The seven-step framework presented here provides a systematic approach to problem-solving, relevant across various domains.
Now, consider this: What’s one question currently on your mind? Grab a piece of paper and try to apply the problem-solving framework. You might uncover fresh insights you hadn’t considered before.
Featured image source: IconScout
Get your teams on the same page — try LogRocket today.
Recent posts:.
Buyer persona interviews provide valuable insights — assuming you time them right. Learn to find the right length for your interviews.
Customer validation is the step in a customer development process where you validate your solutions against customer needs and expectations.
When PMs, designers, and devs share learnings, good ideas turn into great products. In this blog, I share how you can keep the wheels rolling smoothly in a product trio.
Matt Kowalski, VP of Product at Uplift Labs, talks about how behind every job to be done is an emotional feeling a user is seeking.
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 .
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.
Five steps to ensure that you don’t jump to solutions by Julia Binder and Michael D. Watkins
Research shows that companies devote too little effort to examining problems before trying to solve them. By jumping immediately into problem-solving, teams limit their ability to design innovative solutions.
The authors recommend that companies spend more time up front on problem-framing, a process for understanding and defining a problem. Exploring different frames is like looking at a scene through various camera lenses while adjusting your angle, aperture, and focus. A wide-angle lens gives you a very different photo from that taken with a telephoto lens, and shifting your angle and depth of focus yields distinct images. Effective problem-framing is similar: Looking at a problem from a variety of perspectives helps you uncover new insights and generate fresh ideas.
This article introduces a five-phase approach to problem-framing: In the expand phase, the team identifies all aspects of a problem; in examine, it dives into root causes; in empathize, it considers key stakeholders’ perspectives; in elevate, it puts the problem into a broader context; and in envision, it creates a road map toward the desired outcome.
When business leaders confront complex problems, there’s a powerful impulse to dive right into “solving” mode: You gather a team and then identify potential solutions. That’s fine for challenges you’ve faced before or when proven methods yield good results. But what happens when a new type of problem arises or aspects of a familiar one shift substantially? Or if you’re not exactly sure what the problem is?
Research conducted by us and others shows that leaders and their teams devote too little effort to examining and defining problems before trying to solve them. A study by Paul Nutt of Ohio State University, for example, looked at 350 decision-making processes at medium to large companies and found that more than half failed to achieve desired results, often because perceived time pressure caused people to pay insufficient attention to examining problems from all angles and exploring their complexities. By jumping immediately into problem-solving, teams limit their ability to design innovative and durable solutions.
When we work with organizations and teams, we encourage them to spend more time up front on problem-framing, a process for understanding and defining a problem. Exploring frames is like looking at a scene through various camera lenses while adjusting your angle, aperture, and focus. A wide-angle lens will give you a very different photo from that taken with a telephoto lens, and shifting your angle and depth of focus yields distinct images. Effective problem-framing is similar: Looking at a problem from a variety of perspectives lets you uncover new insights and generate fresh ideas.
As with all essential processes, it helps to have a methodology and a road map. This article introduces the E5 approach to problem-framing—expand, examine, empathize, elevate, and envision—and offers tools that enable leaders to fully explore the problem space.
In the first phase, set aside preconceptions and open your mind. We recommend using a tool called frame-storming, which encourages a comprehensive exploration of an issue and its nuances. It is a neglected precursor to brainstorming, which typically focuses on generating many different answers for an already framed challenge. Frame-storming helps teams identify assumptions and blind spots, mitigating the risk of pursuing inadequate or biased solutions. The goal is to spark innovation and creativity as people dig into—or as Tina Seelig from Stanford puts it, “fall in love with”—the problem.
Begin by assembling a diverse team, encompassing a variety of types of expertise and perspectives. Involving outsiders can be helpful, since they’re often coming to the issue cold. A good way to prompt the team to consider alternative scenarios is by asking “What if…?” and “How might we…?” questions. For example, ask your team, “What if we had access to unlimited resources to tackle this issue?” or “How might better collaboration between departments or teams help us tackle this issue?” The primary objective is to generate many alternative problem frames, allowing for a more holistic understanding of the issue. Within an open, nonjudgmental atmosphere, you deliberately challenge established thinking—what we call “breaking” the frame.
It may be easy to eliminate some possibilities, and that’s exactly what you should do. Rather than make assumptions, generate alternative hypotheses and then test them.
Consider the problem-framing process at a company we’ll call Omega Soundscapes, a midsize producer of high-end headphones. (Omega is a composite of several firms we’ve worked with.) Omega’s sales had declined substantially over the past two quarters, and the leadership team’s initial diagnosis, or reference frame, was that recent price hikes to its flagship product made it too expensive for its target market. Before acting on this assumption, the team convened knowledgeable representatives from sales, marketing, R&D, customer service, and external consultants to do some frame-storming. Team members were asked:
In playing out each of those scenarios, the Omega team generated several problem frames:
Each of the frames presented a unique angle from which to approach the problem of declining sales, setting the stage for the development of diverse potential solutions. At this stage, it may be relatively easy to eliminate some possibilities, and that’s exactly what you should do. Rather than make assumptions, generate alternative hypotheses and then test them.
See more HBR charts in Data & Visuals
If the expand phase is about identifying all the facets of a problem, this one is about diving deep to identify root causes. The team investigates the issue thoroughly, peeling back the layers to understand underlying drivers and systemic contributors.
A useful tool for doing this is the iceberg model, which guides the team through layers of causation: surface-level events, the behavioral patterns that drive them, underlying systematic structures, and established mental models. As you probe ever deeper and document your findings, you begin to home in on the problem’s root causes. As is the case in the expand phase, open discussions and collaborative research are crucial for achieving a comprehensive analysis.
Let’s return to our Omega Soundscapes example and use the iceberg model to delve into the issues surrounding the two quarters of declining sales. Starting with the first layer beneath the surface, the behavioral pattern, the team diligently analyzed customer feedback. It discovered a significant drop in brand loyalty. This finding validated the problem frame of a “shifting brand perception,” prompting further investigation into what might have been causing it.
In this phase, the focus is on the stakeholders—employees, customers, clients, investors, supply chain partners, and other parties—who are most central to and affected by the problem under investigation. The core objective is to understand how they perceive the issue: what they think and feel, how they’re acting, and what they want.
First list all the people who are directly or indirectly relevant to the problem. It may be helpful to create a visual representation of the network of relationships in the ecosystem. Prioritize the stakeholders according to their level of influence on and interest in the problem, and focus on understanding the roles, demographics, behavior patterns, motivations, and goals of the most important ones.
Now create empathy maps for those critical stakeholders. Make a template divided into four sections: Say, Think, Feel, and Do. Conduct interviews or surveys to gather authentic data. How do various users explain the problem? How do they think about the issue, and how do their beliefs inform that thinking? What emotions are they feeling and expressing? How are they behaving? Populate each section of the map with notes based on your observations and interactions. Finally, analyze the completed empathy maps. Look for pain points, inconsistencies, and patterns in stakeholder perspectives.
Returning to the Omega case study, the team identified its ecosystem of stakeholders: customers (both current and potential); retail partners and distributors; the R&D, marketing, and sales teams; suppliers of headphone components; investors and shareholders; and new and existing competitors. They narrowed the list to a few key stakeholders related to the declining-sales problem: customers, retail partners, and investors/shareholders; Omega created empathy maps for representatives from each.
Here’s what the empathy maps showed about what the stakeholders were saying, thinking, feeling, and doing:
Sarah, the customer, complained on social media about the high price of her favorite headphones. Dave, the retailer, expressed concerns about unsold inventory and the challenge of convincing customers to buy the expensive headphones. Alex, the shareholder, brought up Omega’s declining financial performance during its annual investor day.
Sarah thought that Omega was losing touch with its loyal customer base. Dave was considering whether to continue carrying Omega’s products in his store or explore other brands. Alex was contemplating diversifying his portfolio into other consumer-tech companies.
As a longtime supporter of the brand, Sarah felt frustrated and slightly betrayed. Dave was feeling anxious about the drop in sales and the impact on his store’s profitability. Alex was unhappy with the declining stock value.
Sarah was looking for alternatives to the headphones, even though she loves the product’s quality. Dave was scheduling a call with Omega to negotiate pricing and terms. Alex was planning to attend Omega’s next shareholder meeting to find out more information from the leadership team.
When Omega leaders analyzed the data in the maps, they realized that pricing wasn’t the only reason for declining sales. A more profound issue was customers’ dissatisfaction with the perceived price-to-quality ratio, especially when compared with competitors’ offerings. That insight prompted the team to consider enhancing the headphones with additional features, offering more-affordable alternatives, and possibly switching to a service model.
This phase involves exploring how the problem connects to broader organizational issues. It’s like zooming out on a map to understand where a city lies in relation to the whole country or continent. This bird’s-eye view reveals interconnected issues and their implications.
For this analysis, we recommend the four-frame model developed by Lee Bolman and Terrence Deal, which offers distinct lenses through which to view the problem at a higher level. The structural frame helps you explore formal structures (such as hierarchy and reporting relationships); processes (such as workflow); and systems, rules, and policies. This frame examines efficiency, coordination, and alignment of activities.
The human resources frame focuses on people, relationships, and social dynamics. This includes teamwork, leadership, employee motivation, engagement, professional development, and personal growth. In this frame, the organization is seen as a community or a family that recognizes that talent is its most valuable asset. The political frame delves into power dynamics, competing interests, conflicts, coalitions, and negotiations. From this perspective, organizations are arenas where various stakeholders vie for resources and engage in political struggles to influence decisions. It helps you see how power is distributed, used, and contested.
The symbolic frame highlights the importance of symbols, rituals, stories, and shared values in shaping group identity and culture. In it, organizations are depicted as theaters through which its members make meaning.
Using this model, the Omega team generated the following insights in the four frames:
A deeper look into the company’s structure revealed siloing and a lack of coordination between the R&D and marketing departments, which had led to misaligned messaging to customers. It also highlighted a lack of collaboration between the two functions and pointed to the need to communicate with the target market about the product’s features and benefits in a coherent and compelling way.
This frame revealed that the declining sales and price hikes had ramped up pressure on the sales team, damaging morale. The demotivated team was struggling to effectively promote the product, making it harder to recover from declining sales. Omega realized it was lacking adequate support, training, and incentives for the team.
The key insight from this frame was that the finance team’s reluctance to approve promotions in the sales group to maintain margins was exacerbating the morale problem. Omega understood that investing in sales leadership development while still generating profits was crucial for long-term success and that frank discussions about the issue were needed.
This frame highlighted an important misalignment in perception: The company believed that its headphones were of “top quality,” while customers reported in surveys that they were “overpriced.” This divergence raised alarm that branding, marketing, and pricing strategies, which were all predicated on the central corporate value of superior quality, were no longer resonating with customers. Omega realized that it had been paying too little attention to quality assurance and functionality.
In this phase, you transition from framing the problem to actively imagining and designing solutions. This involves synthesizing the insights gained from earlier phases and crafting a shared vision of the desired future state.
Here we recommend using a technique known as backcasting. First, clearly define your desired goal. For example, a team struggling with missed deadlines and declining productivity might aim to achieve on-time completion rates of 98% for its projects and increase its volume of projects by 5% over the next year. Next, reverse engineer the path to achieving your goal. Outline key milestones required over both the short term and the long term. For each one, pinpoint specific interventions, strategies, and initiatives that will propel you closer to your goal. These may encompass changes in processes, policies, technologies, and behaviors. Synthesize the activities into a sequenced, chronological, prioritized road map or action plan, and allocate the resources, including time, budget, and personnel, necessary to implement your plan. Finally, monitor progress toward your goal and be prepared to adjust the plan in response to outcomes, feedback, or changing circumstances. This approach ensures that the team’s efforts in implementing the insights from the previous phases are strategically and purposefully directed toward a concrete destination.
Albert Einstein once said, “If I had one hour to solve a problem, I would spend 55 minutes thinking about the problem and five minutes thinking about the solution.” That philosophy underpins our E5 framework, which provides a structured approach for conscientiously engaging with complex problems before leaping to solutions.
As teams use the methodology, they must understand that problem-framing in today’s intricate business landscape is rarely a linear process. While we’re attempting to provide a structured path, we also recognize the dynamic nature of problems and the need for adaptability. Invariably, as teams begin to implement solutions, new facets of a problem may come to light, unforeseen challenges may arise, or external circumstances may evolve. Your team should be ready to loop back to previous phases—for instance, revisiting the expand phase to reassess the problem’s frame, delving deeper into an overlooked root cause in another examine phase, or gathering fresh insights from stakeholders in a new empathize phase. Ultimately, the E5 framework is intended to foster a culture of continuous improvement and innovation.
Problem-solving: exploring three diverse approaches.
Andrea Eboli is a Business Strategist, Founder & CEO of IGB Consulting . Ph.D. in Consumer Science. Member of Forbes Business Council.
A problem doesn't last a lifetime. But how you deal with it can make it linger for years without resolution. In my studies about the topic, I've identified that, in addition to everything that triggers a specific issue, there's also a mindset dictating the script a person follows when confronted with what needs to be solved. It's as if there's already software installed in us, and this program runs in a consistently similar way to find a solution.
Understanding our profile when it comes to problem-solving and recognizing our mindset can be the first step to avoiding getting stuck in problems without reaching a solution. Here are three of the most common types I see:
You might hear a problem amplifier say something like, "My problems are too big and not easy to solve." Some people have a talent for envisioning problems as even larger and more impactful than they truly are. It's common for them to become emotionally entangled to such a degree with an issue that they struggle to find the calmness needed to initiate a resolution. By magnifying difficulties, they end up getting lost and can no longer discern what the real problem is.
Consider someone facing a temporary setback, such as job loss. If they have an amplifying mindset toward problems, they might start believing they will never secure another job and have stable employment again. In this scenario, the individual may begin to act in a negative and defeatist manner, becoming demotivated and giving up on seeking new opportunities.
You may be a problem amplifier if:
• Your conversations at work, with family or among friends usually revolve around sharing problems.
• You tend to magnify the impact of the problem by crafting a detailed story that resonates with people and elicits empathy, but never proposes a solution.
• You talk about the same problem to more than one person.
• Try to stay focused and be objective.
• Work to control your emotions.
• Resist the urge to seek attention through the problem and avoid victimizing oneself.
Arrogant problem solvers are "Leave it to me, I know how to solve it!" types. And while confidence is usually a good thing, arrogant behavior can lead to mistakes. It's a blind spot. This is because individuals who tend to believe they have all the answers run the risk of not fully assessing the situation. It's common for this profile to have experience in problem-solving and indeed possess knowledge and resources to read a situation more easily, but they still have more to learn.
You may be an arrogant problem solver if:
• You enjoy doing things your way and have difficulty listening to others.
• You dislike criticism and often project yourself as the "owner of the truth."
• You rarely give credit to others.
• Approach a problem with curiosity, openness and fewer certainties.
• Investigate before solving and treat certainties as doubts that need to be proven.
• Learn to listen genuinely.
A classic refrain for natural problem solvers is "I can't sleep with anything unresolved!" Natural problem solvers are not afraid to face challenges. Individuals like this are so resilient that others might think they have no problems or that everything in their lives is easier. They take initiative, make things happen, seek solutions and are creative. In other words, they spare no effort to do what needs to be done. Successful executives in operational areas often have more of a problem-solving profile. People with this profile can solve many issues, but when they can't, the lingering feeling is frustration.
You may be a natural problem solver if:
• You often receive or take on additional tasks.
• You take care of the personal problems of the entire family.
• You organize personal and professional engagement and partnership-building events.
• You are a workaholic—by nature and passion.
• You can sometimes be disorganized, hasty or have difficulty focusing.
• Have a method that structures your actions and increases your resolution capacity.
• Be less self-critical and banish thoughts that you are always in debt or never good enough.
• Practice patience and celebrate smaller wins along the way.
I often say that problem-solving should be a mandatory subject in all business schools worldwide. Regardless of the area or position in the company, professionals are greeted every morning with numerous challenges and problems to solve. Your outlook on life often predisposes you to face the problem in a certain way, which can be beneficial but at the same time very detrimental to your career and the way you handle deliveries and results. Understanding these profiles and seeking out tools can help you have a more prosperous and promising relationship with your challenges.
Forbes Business Council is the foremost growth and networking organization for business owners and leaders. Do I qualify?
Join the 150,000+ facilitators using SessionLab.
A step-by-step guide to planning a workshop, 54 great online tools for workshops and meetings, how to create an unforgettable training session in 8 simple steps.
Effective problem solving is all about using the right process and following a plan tailored to the issue at hand. Recognizing your team or organization has an issue isn’t enough to come up with effective problem solving strategies.
To truly understand a problem and develop appropriate solutions, you will want to follow a solid process, follow the necessary problem solving steps, and bring all of your problem solving skills to the table. We’ll forst look at what problem solving strategies you can employ with your team when looking for a way to approach the process. We’ll then discuss the problem solving skills you need to be more effective at solving problems, complete with an activity from the SessionLab library you can use to develop that skill in your team.
Let’s get to it!
What skills do i need to be an effective problem solver, how can i improve my problem solving skills.
Problem solving strategies are methods of approaching and facilitating the process of problem-solving with a set of techniques , actions, and processes. Different strategies are more effective if you are trying to solve broad problems such as achieving higher growth versus more focused problems like, how do we improve our customer onboarding process?
Broadly, the problem solving steps outlined above should be included in any problem solving strategy though choosing where to focus your time and what approaches should be taken is where they begin to differ. You might find that some strategies ask for the problem identification to be done prior to the session or that everything happens in the course of a one day workshop.
The key similarity is that all good problem solving strategies are structured and designed. Four hours of open discussion is never going to be as productive as a four-hour workshop designed to lead a group through a problem solving process.
Good problem solving strategies are tailored to the team, organization and problem you will be attempting to solve. Here are some example problem solving strategies you can learn from or use to get started.
Often, the first step to solving problems or organizational challenges is bringing a group together effectively. Most teams have the tools, knowledge, and expertise necessary to solve their challenges – they just need some guidance in how to use leverage those skills and a structure and format that allows people to focus their energies.
Facilitated workshops are one of the most effective ways of solving problems of any scale. By designing and planning your workshop carefully, you can tailor the approach and scope to best fit the needs of your team and organization.
Workshops are an effective strategy for solving problems. By using tried and test facilitation techniques and methods, you can design and deliver a workshop that is perfectly suited to the unique variables of your organization. You may only have the capacity for a half-day workshop and so need a problem solving process to match.
By using our session planner tool and importing methods from our library of 700+ facilitation techniques, you can create the right problem solving workshop for your team. It might be that you want to encourage creative thinking or look at things from a new angle to unblock your groups approach to problem solving. By tailoring your workshop design to the purpose, you can help ensure great results.
One of the main benefits of a workshop is the structured approach to problem solving. Not only does this mean that the workshop itself will be successful, but many of the methods and techniques will help your team improve their working processes outside of the workshop.
We believe that workshops are one of the best tools you can use to improve the way your team works together. Start with a problem solving workshop and then see what team building, culture or design workshops can do for your organization!
Great for:
By using design thinking principles and methods, a design sprint is a great way of identifying, prioritizing and prototyping solutions to long term challenges that can help solve major organizational problems with quick action and measurable results.
Some familiarity with design thinking is useful, though not integral, and this strategy can really help a team align if there is some discussion around which problems should be approached first.
The stage-based structure of the design sprint is also very useful for teams new to design thinking. The inspiration phase, where you look to competitors that have solved your problem, and the rapid prototyping and testing phases are great for introducing new concepts that will benefit a team in all their future work.
It can be common for teams to look inward for solutions and so looking to the market for solutions you can iterate on can be very productive. Instilling an agile prototyping and testing mindset can also be great when helping teams move forwards – generating and testing solutions quickly can help save time in the long run and is also pretty exciting!
Organizational challenges and problems are often complicated and large scale in nature. Sometimes, trying to resolve such an issue in one swoop is simply unachievable or overwhelming. Try breaking down such problems into smaller issues that you can work on step by step. You may not be able to solve the problem of churning customers off the bat, but you can work with your team to identify smaller effort but high impact elements and work on those first.
This problem solving strategy can help a team generate momentum, prioritize and get some easy wins. It’s also a great strategy to employ with teams who are just beginning to learn how to approach the problem solving process. If you want some insight into a way to employ this strategy, we recommend looking at our design sprint template below!
Some problems are best solved by introducing a major shift in perspective or by using new methodologies that encourage your team to think differently.
Props and tools such as Methodkit , which uses a card-based toolkit for facilitation, or Lego Serious Play can be great ways to engage your team and find an inclusive, democratic problem solving strategy. Remember that play and creativity are great tools for achieving change and whatever the challenge, engaging your participants can be very effective where other strategies may have failed.
LEGO Serious Play is a problem solving methodology designed to get participants thinking differently by using 3D models and kinesthetic learning styles. By physically building LEGO models based on questions and exercises, participants are encouraged to think outside of the box and create their own responses.
Collaborate LEGO Serious Play exercises are also used to encourage communication and build problem solving skills in a group. By using this problem solving process, you can often help different kinds of learners and personality types contribute and unblock organizational problems with creative thinking.
Problem solving strategies like LEGO Serious Play are super effective at helping a team solve more skills-based problems such as communication between teams or a lack of creative thinking. Some problems are not suited to LEGO Serious Play and require a different problem solving strategy.
Card decks and method kids are great tools for those new to facilitation or for whom facilitation is not the primary role. Card decks such as the emotional culture deck can be used for complete workshops and in many cases, can be used right out of the box. Methodkit has a variety of kits designed for scenarios ranging from personal development through to personas and global challenges so you can find the right deck for your particular needs.
Having an easy to use framework that encourages creativity or a new approach can take some of the friction or planning difficulties out of the workshop process and energize a team in any setting. Simplicity is the key with these methods. By ensuring everyone on your team can get involved and engage with the process as quickly as possible can really contribute to the success of your problem solving strategy.
Looking to peers, experts and external facilitators can be a great way of approaching the problem solving process. Your team may not have the necessary expertise, insights of experience to tackle some issues, or you might simply benefit from a fresh perspective. Some problems may require bringing together an entire team, and coaching managers or team members individually might be the right approach. Remember that not all problems are best resolved in the same manner.
If you’re a solo entrepreneur, peer groups, coaches and mentors can also be invaluable at not only solving specific business problems, but in providing a support network for resolving future challenges. One great approach is to join a Mastermind Group and link up with like-minded individuals and all grow together. Remember that however you approach the sourcing of external advice, do so thoughtfully, respectfully and honestly. Reciprocate where you can and prepare to be surprised by just how kind and helpful your peers can be!
Problem solving in large organizations with lots of skilled team members is one thing, but how about if you work for yourself or in a very small team without the capacity to get the most from a design sprint or LEGO Serious Play session?
A mastermind group – sometimes known as a peer advisory board – is where a group of people come together to support one another in their own goals, challenges, and businesses. Each participant comes to the group with their own purpose and the other members of the group will help them create solutions, brainstorm ideas, and support one another.
Mastermind groups are very effective in creating an energized, supportive atmosphere that can deliver meaningful results. Learning from peers from outside of your organization or industry can really help unlock new ways of thinking and drive growth. Access to the experience and skills of your peers can be invaluable in helping fill the gaps in your own ability, particularly in young companies.
A mastermind group is a great solution for solo entrepreneurs, small teams, or for organizations that feel that external expertise or fresh perspectives will be beneficial for them. It is worth noting that Mastermind groups are often only as good as the participants and what they can bring to the group. Participants need to be committed, engaged and understand how to work in this context.
Receiving advice from a business coach or building a mentor/mentee relationship can be an effective way of resolving certain challenges. The one-to-one format of most coaching and mentor relationships can really help solve the challenges those individuals are having and benefit the organization as a result.
A great mentor can be invaluable when it comes to spotting potential problems before they arise and coming to understand a mentee very well has a host of other business benefits. You might run an internal mentorship program to help develop your team’s problem solving skills and strategies or as part of a large learning and development program. External coaches can also be an important part of your problem solving strategy, filling skills gaps for your management team or helping with specific business issues.
Now we’ve explored the problem solving process and the steps you will want to go through in order to have an effective session, let’s look at the skills you and your team need to be more effective problem solvers.
Problem solving skills are highly sought after, whatever industry or team you work in. Organizations are keen to employ people who are able to approach problems thoughtfully and find strong, realistic solutions. Whether you are a facilitator , a team leader or a developer, being an effective problem solver is a skill you’ll want to develop.
Problem solving skills form a whole suite of techniques and approaches that an individual uses to not only identify problems but to discuss them productively before then developing appropriate solutions.
Here are some of the most important problem solving skills everyone from executives to junior staff members should learn. We’ve also included an activity or exercise from the SessionLab library that can help you and your team develop that skill.
If you’re running a workshop or training session to try and improve problem solving skills in your team, try using these methods to supercharge your process!
Active listening is one of the most important skills anyone who works with people can possess. In short, active listening is a technique used to not only better understand what is being said by an individual, but also to be more aware of the underlying message the speaker is trying to convey. When it comes to problem solving, active listening is integral for understanding the position of every participant and to clarify the challenges, ideas and solutions they bring to the table.
Some active listening skills include:
Active Listening #hyperisland #skills #active listening #remote-friendly This activity supports participants to reflect on a question and generate their own solutions using simple principles of active listening and peer coaching. It’s an excellent introduction to active listening but can also be used with groups that are already familiar with it. Participants work in groups of three and take turns being: “the subject”, the listener, and the observer.
All problem solving models require strong analytical skills, particularly during the beginning of the process and when it comes to analyzing how solutions have performed.
Analytical skills are primarily focused on performing an effective analysis by collecting, studying and parsing data related to a problem or opportunity.
It often involves spotting patterns, being able to see things from different perspectives and using observable facts and data to make suggestions or produce insight.
Analytical skills are also important at every stage of the problem solving process and by having these skills, you can ensure that any ideas or solutions you create or backed up analytically and have been sufficiently thought out.
Nine Whys #innovation #issue analysis #liberating structures With breathtaking simplicity, you can rapidly clarify for individuals and a group what is essentially important in their work. You can quickly reveal when a compelling purpose is missing in a gathering and avoid moving forward without clarity. When a group discovers an unambiguous shared purpose, more freedom and more responsibility are unleashed. You have laid the foundation for spreading and scaling innovations with fidelity.
Trying to solve problems on your own is difficult. Being able to collaborate effectively, with a free exchange of ideas, to delegate and be a productive member of a team is hugely important to all problem solving strategies.
Remember that whatever your role, collaboration is integral, and in a problem solving process, you are all working together to find the best solution for everyone.
Marshmallow challenge with debriefing #teamwork #team #leadership #collaboration In eighteen minutes, teams must build the tallest free-standing structure out of 20 sticks of spaghetti, one yard of tape, one yard of string, and one marshmallow. The marshmallow needs to be on top. The Marshmallow Challenge was developed by Tom Wujec, who has done the activity with hundreds of groups around the world. Visit the Marshmallow Challenge website for more information. This version has an extra debriefing question added with sample questions focusing on roles within the team.
Being an effective communicator means being empathetic, clear and succinct, asking the right questions, and demonstrating active listening skills throughout any discussion or meeting.
In a problem solving setting, you need to communicate well in order to progress through each stage of the process effectively. As a team leader, it may also fall to you to facilitate communication between parties who may not see eye to eye. Effective communication also means helping others to express themselves and be heard in a group.
Bus Trip #feedback #communication #appreciation #closing #thiagi #team This is one of my favourite feedback games. I use Bus Trip at the end of a training session or a meeting, and I use it all the time. The game creates a massive amount of energy with lots of smiles, laughs, and sometimes even a teardrop or two.
Creative problem solving skills can be some of the best tools in your arsenal. Thinking creatively, being able to generate lots of ideas and come up with out of the box solutions is useful at every step of the process.
The kinds of problems you will likely discuss in a problem solving workshop are often difficult to solve, and by approaching things in a fresh, creative manner, you can often create more innovative solutions.
Having practical creative skills is also a boon when it comes to problem solving. If you can help create quality design sketches and prototypes in record time, it can help bring a team to alignment more quickly or provide a base for further iteration.
The paper clip method #sharing #creativity #warm up #idea generation #brainstorming The power of brainstorming. A training for project leaders, creativity training, and to catalyse getting new solutions.
Critical thinking is one of the fundamental problem solving skills you’ll want to develop when working on developing solutions. Critical thinking is the ability to analyze, rationalize and evaluate while being aware of personal bias, outlying factors and remaining open-minded.
Defining and analyzing problems without deploying critical thinking skills can mean you and your team go down the wrong path. Developing solutions to complex issues requires critical thinking too – ensuring your team considers all possibilities and rationally evaluating them.
Agreement-Certainty Matrix #issue analysis #liberating structures #problem solving You can help individuals or groups avoid the frequent mistake of trying to solve a problem with methods that are not adapted to the nature of their challenge. The combination of two questions makes it possible to easily sort challenges into four categories: simple, complicated, complex , and chaotic . A problem is simple when it can be solved reliably with practices that are easy to duplicate. It is complicated when experts are required to devise a sophisticated solution that will yield the desired results predictably. A problem is complex when there are several valid ways to proceed but outcomes are not predictable in detail. Chaotic is when the context is too turbulent to identify a path forward. A loose analogy may be used to describe these differences: simple is like following a recipe, complicated like sending a rocket to the moon, complex like raising a child, and chaotic is like the game “Pin the Tail on the Donkey.” The Liberating Structures Matching Matrix in Chapter 5 can be used as the first step to clarify the nature of a challenge and avoid the mismatches between problems and solutions that are frequently at the root of chronic, recurring problems.
Though it shares lots of space with general analytical skills, data analysis skills are something you want to cultivate in their own right in order to be an effective problem solver.
Being good at data analysis doesn’t just mean being able to find insights from data, but also selecting the appropriate data for a given issue, interpreting it effectively and knowing how to model and present that data. Depending on the problem at hand, it might also include a working knowledge of specific data analysis tools and procedures.
Having a solid grasp of data analysis techniques is useful if you’re leading a problem solving workshop but if you’re not an expert, don’t worry. Bring people into the group who has this skill set and help your team be more effective as a result.
All problems need a solution and all solutions require that someone make the decision to implement them. Without strong decision making skills, teams can become bogged down in discussion and less effective as a result.
Making decisions is a key part of the problem solving process. It’s important to remember that decision making is not restricted to the leadership team. Every staff member makes decisions every day and developing these skills ensures that your team is able to solve problems at any scale. Remember that making decisions does not mean leaping to the first solution but weighing up the options and coming to an informed, well thought out solution to any given problem that works for the whole team.
Lightning Decision Jam (LDJ) #action #decision making #problem solving #issue analysis #innovation #design #remote-friendly The problem with anything that requires creative thinking is that it’s easy to get lost—lose focus and fall into the trap of having useless, open-ended, unstructured discussions. Here’s the most effective solution I’ve found: Replace all open, unstructured discussion with a clear process. What to use this exercise for: Anything which requires a group of people to make decisions, solve problems or discuss challenges. It’s always good to frame an LDJ session with a broad topic, here are some examples: The conversion flow of our checkout Our internal design process How we organise events Keeping up with our competition Improving sales flow
Most complex organizational problems require multiple people to be involved in delivering the solution. Ensuring that the team and organization can depend on you to take the necessary actions and communicate where necessary is key to ensuring problems are solved effectively.
Being dependable also means working to deadlines and to brief. It is often a matter of creating trust in a team so that everyone can depend on one another to complete the agreed actions in the agreed time frame so that the team can move forward together. Being undependable can create problems of friction and can limit the effectiveness of your solutions so be sure to bear this in mind throughout a project.
Team Purpose & Culture #team #hyperisland #culture #remote-friendly This is an essential process designed to help teams define their purpose (why they exist) and their culture (how they work together to achieve that purpose). Defining these two things will help any team to be more focused and aligned. With support of tangible examples from other companies, the team members work as individuals and a group to codify the way they work together. The goal is a visual manifestation of both the purpose and culture that can be put up in the team’s work space.
Emotional intelligence is an important skill for any successful team member, whether communicating internally or with clients or users. In the problem solving process, emotional intelligence means being attuned to how people are feeling and thinking, communicating effectively and being self-aware of what you bring to a room.
There are often differences of opinion when working through problem solving processes, and it can be easy to let things become impassioned or combative. Developing your emotional intelligence means being empathetic to your colleagues and managing your own emotions throughout the problem and solution process. Be kind, be thoughtful and put your points across care and attention.
Being emotionally intelligent is a skill for life and by deploying it at work, you can not only work efficiently but empathetically. Check out the emotional culture workshop template for more!
As we’ve clarified in our facilitation skills post, facilitation is the art of leading people through processes towards agreed-upon objectives in a manner that encourages participation, ownership, and creativity by all those involved. While facilitation is a set of interrelated skills in itself, the broad definition of facilitation can be invaluable when it comes to problem solving. Leading a team through a problem solving process is made more effective if you improve and utilize facilitation skills – whether you’re a manager, team leader or external stakeholder.
The Six Thinking Hats #creative thinking #meeting facilitation #problem solving #issue resolution #idea generation #conflict resolution The Six Thinking Hats are used by individuals and groups to separate out conflicting styles of thinking. They enable and encourage a group of people to think constructively together in exploring and implementing change, rather than using argument to fight over who is right and who is wrong.
Being flexible is a vital skill when it comes to problem solving. This does not mean immediately bowing to pressure or changing your opinion quickly: instead, being flexible is all about seeing things from new perspectives, receiving new information and factoring it into your thought process.
Flexibility is also important when it comes to rolling out solutions. It might be that other organizational projects have greater priority or require the same resources as your chosen solution. Being flexible means understanding needs and challenges across the team and being open to shifting or arranging your own schedule as necessary. Again, this does not mean immediately making way for other projects. It’s about articulating your own needs, understanding the needs of others and being able to come to a meaningful compromise.
The Creativity Dice #creativity #problem solving #thiagi #issue analysis Too much linear thinking is hazardous to creative problem solving. To be creative, you should approach the problem (or the opportunity) from different points of view. You should leave a thought hanging in mid-air and move to another. This skipping around prevents premature closure and lets your brain incubate one line of thought while you consciously pursue another.
Working in any group can lead to unconscious elements of groupthink or situations in which you may not wish to be entirely honest. Disagreeing with the opinions of the executive team or wishing to save the feelings of a coworker can be tricky to navigate, but being honest is absolutely vital when to comes to developing effective solutions and ensuring your voice is heard.
Remember that being honest does not mean being brutally candid. You can deliver your honest feedback and opinions thoughtfully and without creating friction by using other skills such as emotional intelligence.
Explore your Values #hyperisland #skills #values #remote-friendly Your Values is an exercise for participants to explore what their most important values are. It’s done in an intuitive and rapid way to encourage participants to follow their intuitive feeling rather than over-thinking and finding the “correct” values. It is a good exercise to use to initiate reflection and dialogue around personal values.
The problem solving process is multi-faceted and requires different approaches at certain points of the process. Taking initiative to bring problems to the attention of the team, collect data or lead the solution creating process is always valuable. You might even roadtest your own small scale solutions or brainstorm before a session. Taking initiative is particularly effective if you have good deal of knowledge in that area or have ownership of a particular project and want to get things kickstarted.
That said, be sure to remember to honor the process and work in service of the team. If you are asked to own one part of the problem solving process and you don’t complete that task because your initiative leads you to work on something else, that’s not an effective method of solving business challenges.
15% Solutions #action #liberating structures #remote-friendly You can reveal the actions, however small, that everyone can do immediately. At a minimum, these will create momentum, and that may make a BIG difference. 15% Solutions show that there is no reason to wait around, feel powerless, or fearful. They help people pick it up a level. They get individuals and the group to focus on what is within their discretion instead of what they cannot change. With a very simple question, you can flip the conversation to what can be done and find solutions to big problems that are often distributed widely in places not known in advance. Shifting a few grains of sand may trigger a landslide and change the whole landscape.
A particularly useful problem solving skill for product owners or managers is the ability to remain impartial throughout much of the process. In practice, this means treating all points of view and ideas brought forward in a meeting equally and ensuring that your own areas of interest or ownership are not favored over others.
There may be a stage in the process where a decision maker has to weigh the cost and ROI of possible solutions against the company roadmap though even then, ensuring that the decision made is based on merit and not personal opinion.
Empathy map #frame insights #create #design #issue analysis An empathy map is a tool to help a design team to empathize with the people they are designing for. You can make an empathy map for a group of people or for a persona. To be used after doing personas when more insights are needed.
Being a good leader means getting a team aligned, energized and focused around a common goal. In the problem solving process, strong leadership helps ensure that the process is efficient, that any conflicts are resolved and that a team is managed in the direction of success.
It’s common for managers or executives to assume this role in a problem solving workshop, though it’s important that the leader maintains impartiality and does not bulldoze the group in a particular direction. Remember that good leadership means working in service of the purpose and team and ensuring the workshop is a safe space for employees of any level to contribute. Take a look at our leadership games and activities post for more exercises and methods to help improve leadership in your organization.
Leadership Pizza #leadership #team #remote-friendly This leadership development activity offers a self-assessment framework for people to first identify what skills, attributes and attitudes they find important for effective leadership, and then assess their own development and initiate goal setting.
In the context of problem solving, mediation is important in keeping a team engaged, happy and free of conflict. When leading or facilitating a problem solving workshop, you are likely to run into differences of opinion. Depending on the nature of the problem, certain issues may be brought up that are emotive in nature.
Being an effective mediator means helping those people on either side of such a divide are heard, listen to one another and encouraged to find common ground and a resolution. Mediating skills are useful for leaders and managers in many situations and the problem solving process is no different.
Conflict Responses #hyperisland #team #issue resolution A workshop for a team to reflect on past conflicts, and use them to generate guidelines for effective conflict handling. The workshop uses the Thomas-Killman model of conflict responses to frame a reflective discussion. Use it to open up a discussion around conflict with a team.
Solving organizational problems is much more effective when following a process or problem solving model. Planning skills are vital in order to structure, deliver and follow-through on a problem solving workshop and ensure your solutions are intelligently deployed.
Planning skills include the ability to organize tasks and a team, plan and design the process and take into account any potential challenges. Taking the time to plan carefully can save time and frustration later in the process and is valuable for ensuring a team is positioned for success.
3 Action Steps #hyperisland #action #remote-friendly This is a small-scale strategic planning session that helps groups and individuals to take action toward a desired change. It is often used at the end of a workshop or programme. The group discusses and agrees on a vision, then creates some action steps that will lead them towards that vision. The scope of the challenge is also defined, through discussion of the helpful and harmful factors influencing the group.
As organisations grow, the scale and variation of problems they face multiplies. Your team or is likely to face numerous challenges in different areas and so having the skills to analyze and prioritize becomes very important, particularly for those in leadership roles.
A thorough problem solving process is likely to deliver multiple solutions and you may have several different problems you wish to solve simultaneously. Prioritization is the ability to measure the importance, value, and effectiveness of those possible solutions and choose which to enact and in what order. The process of prioritization is integral in ensuring the biggest challenges are addressed with the most impactful solutions.
Impact and Effort Matrix #gamestorming #decision making #action #remote-friendly In this decision-making exercise, possible actions are mapped based on two factors: effort required to implement and potential impact. Categorizing ideas along these lines is a useful technique in decision making, as it obliges contributors to balance and evaluate suggested actions before committing to them.
Some problem solving skills are utilized in a workshop or ideation phases, while others come in useful when it comes to decision making. Overseeing an entire problem solving process and ensuring its success requires strong project management skills.
While project management incorporates many of the other skills listed here, it is important to note the distinction of considering all of the factors of a project and managing them successfully. Being able to negotiate with stakeholders, manage tasks, time and people, consider costs and ROI, and tie everything together is massively helpful when going through the problem solving process.
Working out meaningful solutions to organizational challenges is only one part of the process. Thoughtfully documenting and keeping records of each problem solving step for future consultation is important in ensuring efficiency and meaningful change.
For example, some problems may be lower priority than others but can be revisited in the future. If the team has ideated on solutions and found some are not up to the task, record those so you can rule them out and avoiding repeating work. Keeping records of the process also helps you improve and refine your problem solving model next time around!
Personal Kanban #gamestorming #action #agile #project planning Personal Kanban is a tool for organizing your work to be more efficient and productive. It is based on agile methods and principles.
Conducting research to support both the identification of problems and the development of appropriate solutions is important for an effective process. Knowing where to go to collect research, how to conduct research efficiently, and identifying pieces of research are relevant are all things a good researcher can do well.
In larger groups, not everyone has to demonstrate this ability in order for a problem solving workshop to be effective. That said, having people with research skills involved in the process, particularly if they have existing area knowledge, can help ensure the solutions that are developed with data that supports their intention. Remember that being able to deliver the results of research efficiently and in a way the team can easily understand is also important. The best data in the world is only as effective as how it is delivered and interpreted.
Customer experience map #ideation #concepts #research #design #issue analysis #remote-friendly Customer experience mapping is a method of documenting and visualizing the experience a customer has as they use the product or service. It also maps out their responses to their experiences. To be used when there is a solution (even in a conceptual stage) that can be analyzed.
Managing risk is an often overlooked part of the problem solving process. Solutions are often developed with the intention of reducing exposure to risk or solving issues that create risk but sometimes, great solutions are more experimental in nature and as such, deploying them needs to be carefully considered.
Managing risk means acknowledging that there may be risks associated with more out of the box solutions or trying new things, but that this must be measured against the possible benefits and other organizational factors.
Be informed, get the right data and stakeholders in the room and you can appropriately factor risk into your decision making process.
Decisions, Decisions… #communication #decision making #thiagi #action #issue analysis When it comes to decision-making, why are some of us more prone to take risks while others are risk-averse? One explanation might be the way the decision and options were presented. This exercise, based on Kahneman and Tversky’s classic study , illustrates how the framing effect influences our judgement and our ability to make decisions . The participants are divided into two groups. Both groups are presented with the same problem and two alternative programs for solving them. The two programs both have the same consequences but are presented differently. The debriefing discussion examines how the framing of the program impacted the participant’s decision.
No single person is as good at problem solving as a team. Building an effective team and helping them come together around a common purpose is one of the most important problem solving skills, doubly so for leaders. By bringing a team together and helping them work efficiently, you pave the way for team ownership of a problem and the development of effective solutions.
In a problem solving workshop, it can be tempting to jump right into the deep end, though taking the time to break the ice, energize the team and align them with a game or exercise will pay off over the course of the day.
Remember that you will likely go through the problem solving process multiple times over an organization’s lifespan and building a strong team culture will make future problem solving more effective. It’s also great to work with people you know, trust and have fun with. Working on team building in and out of the problem solving process is a hallmark of successful teams that can work together to solve business problems.
9 Dimensions Team Building Activity #ice breaker #teambuilding #team #remote-friendly 9 Dimensions is a powerful activity designed to build relationships and trust among team members. There are 2 variations of this icebreaker. The first version is for teams who want to get to know each other better. The second version is for teams who want to explore how they are working together as a team.
The problem solving process is designed to lead a team from identifying a problem through to delivering a solution and evaluating its effectiveness. Without effective time management skills or timeboxing of tasks, it can be easy for a team to get bogged down or be inefficient.
By using a problem solving model and carefully designing your workshop, you can allocate time efficiently and trust that the process will deliver the results you need in a good timeframe.
Time management also comes into play when it comes to rolling out solutions, particularly those that are experimental in nature. Having a clear timeframe for implementing and evaluating solutions is vital for ensuring their success and being able to pivot if necessary.
Improving your skills at problem solving is often a career-long pursuit though there are methods you can use to make the learning process more efficient and to supercharge your problem solving skillset.
Remember that the skills you need to be a great problem solver have a large overlap with those skills you need to be effective in any role. Investing time and effort to develop your active listening or critical thinking skills is valuable in any context. Here are 7 ways to improve your problem solving skills.
Remember that your team is an excellent source of skills, wisdom, and techniques and that you should all take advantage of one another where possible. Best practices that one team has for solving problems, conducting research or making decisions should be shared across the organization. If you have in-house staff that have done active listening training or are data analysis pros, have them lead a training session.
Your team is one of your best resources. Create space and internal processes for the sharing of skills so that you can all grow together.
Once you’ve figured out you have a skills gap, the next step is to take action to fill that skills gap. That might be by asking your superior for training or coaching, or liaising with team members with that skill set. You might even attend specialized training for certain skills – active listening or critical thinking, for example, are business-critical skills that are regularly offered as part of a training scheme.
Whatever method you choose, remember that taking action of some description is necessary for growth. Whether that means practicing, getting help, attending training or doing some background reading, taking active steps to improve your skills is the way to go.
Problem solving can be complicated, particularly when attempting to solve large problems for the first time. Using a problem solving process helps give structure to your problem solving efforts and focus on creating outcomes, rather than worrying about the format.
Tools such as the seven-step problem solving process above are effective because not only do they feature steps that will help a team solve problems, they also develop skills along the way. Each step asks for people to engage with the process using different skills and in doing so, helps the team learn and grow together. Group processes of varying complexity and purpose can also be found in the SessionLab library of facilitation techniques . Using a tried and tested process and really help ease the learning curve for both those leading such a process, as well as those undergoing the purpose.
Effective teams make decisions about where they should and shouldn’t expend additional effort. By using a problem solving process, you can focus on the things that matter, rather than stumbling towards a solution haphazardly.
Some skills gaps are more obvious than others. It’s possible that your perception of your active listening skills differs from those of your colleagues.
It’s valuable to create a system where team members can provide feedback in an ordered and friendly manner so they can all learn from one another. Only by identifying areas of improvement can you then work to improve them.
Remember that feedback systems require oversight and consideration so that they don’t turn into a place to complain about colleagues. Design the system intelligently so that you encourage the creation of learning opportunities, rather than encouraging people to list their pet peeves.
While practice might not make perfect, it does make the problem solving process easier. If you are having trouble with critical thinking, don’t shy away from doing it. Get involved where you can and stretch those muscles as regularly as possible.
Problem solving skills come more naturally to some than to others and that’s okay. Take opportunities to get involved and see where you can practice your skills in situations outside of a workshop context. Try collaborating in other circumstances at work or conduct data analysis on your own projects. You can often develop those skills you need for problem solving simply by doing them. Get involved!
Learn from the best. Our library of 700+ facilitation techniques is full of activities and methods that help develop the skills you need to be an effective problem solver. Check out our templates to see how to approach problem solving and other organizational challenges in a structured and intelligent manner.
There is no single approach to improving problem solving skills, but by using the techniques employed by others you can learn from their example and develop processes that have seen proven results.
Using tried and tested exercises that you know well can help deliver results, but you do run the risk of missing out on the learning opportunities offered by new approaches. As with the problem solving process, changing your mindset can remove blockages and be used to develop your problem solving skills.
Most teams have members with mixed skill sets and specialties. Mix people from different teams and share skills and different points of view. Teach your customer support team how to use design thinking methods or help your developers with conflict resolution techniques. Try switching perspectives with facilitation techniques like Flip It! or by using new problem solving methodologies or models. Give design thinking, liberating structures or lego serious play a try if you want to try a new approach. You will find that framing problems in new ways and using existing skills in new contexts can be hugely useful for personal development and improving your skillset. It’s also a lot of fun to try new things. Give it a go!
Encountering business challenges and needing to find appropriate solutions is not unique to your organization. Lots of very smart people have developed methods, theories and approaches to help develop problem solving skills and create effective solutions. Learn from them!
Books like The Art of Thinking Clearly , Think Smarter, or Thinking Fast, Thinking Slow are great places to start, though it’s also worth looking at blogs related to organizations facing similar problems to yours, or browsing for success stories. Seeing how Dropbox massively increased growth and working backward can help you see the skills or approach you might be lacking to solve that same problem. Learning from others by reading their stories or approaches can be time-consuming but ultimately rewarding.
A tired, distracted mind is not in the best position to learn new skills. It can be tempted to burn the candle at both ends and develop problem solving skills outside of work. Absolutely use your time effectively and take opportunities for self-improvement, though remember that rest is hugely important and that without letting your brain rest, you cannot be at your most effective.
Creating distance between yourself and the problem you might be facing can also be useful. By letting an idea sit, you can find that a better one presents itself or you can develop it further. Take regular breaks when working and create a space for downtime. Remember that working smarter is preferable to working harder and that self-care is important for any effective learning or improvement process.
Now we’ve explored some of the key problem solving skills and the problem solving steps necessary for an effective process, you’re ready to begin developing more effective solutions and leading problem solving workshops.
Need more inspiration? Check out our post on problem solving activities you can use when guiding a group towards a great solution in your next workshop or meeting. Have questions? Did you have a great problem solving technique you use with your team? Get in touch in the comments below. We’d love to chat!
James Smart is Head of Content at SessionLab. He’s also a creative facilitator who has run workshops and designed courses for establishments like the National Centre for Writing, UK. He especially enjoys working with young people and empowering others in their creative practice.
Your email address will not be published. Required fields are marked *
Going from a mere idea to a workshop that delivers results for your clients can feel like a daunting task. In this piece, we will shine a light on all the work behind the scenes and help you learn how to plan a workshop from start to finish. On a good day, facilitation can feel like effortless magic, but that is mostly the result of backstage work, foresight, and a lot of careful planning. Read on to learn a step-by-step approach to breaking the process of planning a workshop into small, manageable chunks. The flow starts with the first meeting with a client to define the purposes of a workshop.…
Effective online tools are a necessity for smooth and engaging virtual workshops and meetings. But how do you choose the right ones? Do you sometimes feel that the good old pen and paper or MS Office toolkit and email leaves you struggling to stay on top of managing and delivering your workshop? Fortunately, there are plenty of great workshop tools to make your life easier when you need to facilitate a meeting and lead workshops. In this post, we’ll share our favorite online tools you can use to make your life easier and run better workshops and meetings. In fact, there are plenty of free online workshop tools and meeting…
How does learning work? A clever 9-year-old once told me: “I know I am learning something new when I am surprised.” The science of adult learning tells us that, in order to learn new skills (which, unsurprisingly, is harder for adults to do than kids) grown-ups need to first get into a specific headspace. In a business, this approach is often employed in a training session where employees learn new skills or work on professional development. But how do you ensure your training is effective? In this guide, we'll explore how to create an effective training session plan and run engaging training sessions. As team leader, project manager, or consultant,…
Join the 150,000 facilitators using SessionLab
Sign up for free
Harvard Business School Online's Business Insights Blog provides the career insights you need to achieve your goals and gain confidence in your business skills.
One of the biggest hindrances to innovation is complacency—it can be more comfortable to do what you know than venture into the unknown. Business leaders can overcome this barrier by mobilizing creative team members and providing space to innovate.
There are several tools you can use to encourage creativity in the workplace. Creative problem-solving is one of them, which facilitates the development of innovative solutions to difficult problems.
Here’s an overview of creative problem-solving and why it’s important in business.
Access your free e-book today.
Research is necessary when solving a problem. But there are situations where a problem’s specific cause is difficult to pinpoint. This can occur when there’s not enough time to narrow down the problem’s source or there are differing opinions about its root cause.
In such cases, you can use creative problem-solving , which allows you to explore potential solutions regardless of whether a problem has been defined.
Creative problem-solving is less structured than other innovation processes and encourages exploring open-ended solutions. It also focuses on developing new perspectives and fostering creativity in the workplace . Its benefits include:
Creative problem-solving is traditionally based on the following key principles :
Creative problem-solving uses two primary tools to find solutions: divergence and convergence. Divergence generates ideas in response to a problem, while convergence narrows them down to a shortlist. It balances these two practices and turns ideas into concrete solutions.
By framing problems as questions, you shift from focusing on obstacles to solutions. This provides the freedom to brainstorm potential ideas.
When brainstorming, it can be natural to reject or accept ideas right away. Yet, immediate judgments interfere with the idea generation process. Even ideas that seem implausible can turn into outstanding innovations upon further exploration and development.
Using negative words like "no" discourages creative thinking. Instead, use positive language to build and maintain an environment that fosters the development of creative and innovative ideas.
Whereas creative problem-solving facilitates developing innovative ideas through a less structured workflow, design thinking takes a far more organized approach.
Design thinking is a human-centered, solutions-based process that fosters the ideation and development of solutions. In the online course Design Thinking and Innovation , Harvard Business School Dean Srikant Datar leverages a four-phase framework to explain design thinking.
The four stages are:
Creative problem-solving primarily operates in the ideate phase of design thinking but can be applied to others. This is because design thinking is an iterative process that moves between the stages as ideas are generated and pursued. This is normal and encouraged, as innovation requires exploring multiple ideas.
While there are many useful tools in the creative problem-solving process, here are three you should know:
One way to innovate is by creating a story about a problem to understand how it affects users and what solutions best fit their needs. Here are the steps you need to take to use this tool properly.
Create a problem story to identify the undesired phenomena (UDP). For example, consider a company that produces printers that overheat. In this case, the UDP is "our printers overheat."
To move forward in time, ask: “Why is this a problem?” For example, minor damage could be one result of the machines overheating. In more extreme cases, printers may catch fire. Don't be afraid to create multiple problem stories if you think of more than one UDP.
To move backward in time, ask: “What caused this UDP?” If you can't identify the root problem, think about what typically causes the UDP to occur. For the overheating printers, overuse could be a cause.
Following the three-step framework above helps illustrate a clear problem story:
You can extend the problem story in either direction if you think of additional cause-and-effect relationships.
By this point, you’ll have multiple UDP storylines. Take two that are similar and focus on breaking the chains connecting them. This can be accomplished through inversion or neutralization.
Even if creating a problem story doesn't provide a solution, it can offer useful context to users’ problems and additional ideas to be explored. Given that divergence is one of the fundamental practices of creative problem-solving, it’s a good idea to incorporate it into each tool you use.
Brainstorming is a tool that can be highly effective when guided by the iterative qualities of the design thinking process. It involves openly discussing and debating ideas and topics in a group setting. This facilitates idea generation and exploration as different team members consider the same concept from multiple perspectives.
Hosting brainstorming sessions can result in problems, such as groupthink or social loafing. To combat this, leverage a three-step brainstorming method involving divergence and convergence :
The alternate worlds tool is an empathetic approach to creative problem-solving. It encourages you to consider how someone in another world would approach your situation.
For example, if you’re concerned that the printers you produce overheat and catch fire, consider how a different industry would approach the problem. How would an automotive expert solve it? How would a firefighter?
Be creative as you consider and research alternate worlds. The purpose is not to nail down a solution right away but to continue the ideation process through diverging and exploring ideas.
Whether you’re an entrepreneur, marketer, or business leader, learning the ropes of design thinking can be an effective way to build your skills and foster creativity and innovation in any setting.
If you're ready to develop your design thinking and creative problem-solving skills, explore Design Thinking and Innovation , one of our online entrepreneurship and innovation courses. If you aren't sure which course is the right fit, download our free course flowchart to determine which best aligns with your goals.
In the early days of my career as a project manager, I often felt like I was juggling flaming torches while riding a unicycle—one wrong move, and everything could come crashing down. I remember a particularly challenging project where our team was tasked with launching a new product line within an impossible deadline. We were scrambling, tensions were high, and despite our best efforts, we kept hitting roadblocks. It felt like we were putting out fires rather than making any real progress.
One evening, over a much-needed cup of coffee, a mentor introduced me to the Kepner-Tregoe Problem Analysis method. Skeptical but desperate for a solution, I decided to give it a shot. Little did I know, this decision would not only save our project but also transform the way I approach problem-solving in both my professional and personal life.
The moment of realization: more than just a tool.
At first glance, Kepner-Tregoe seemed like just another analytical framework—dry, technical, and somewhat intimidating. But as I delved deeper, I realized it was much more than that. It was a systematic way to dissect complex issues, understand their root causes, and develop effective solutions. For someone like me, who often got lost in the chaos of multifaceted problems, this method was a revelation.
I began to see patterns in the problems we faced. It wasn't just about missed deadlines or budget overruns; there were underlying issues that we hadn't identified. This method provided a structured approach to peel back the layers and see the core of the problem.
The Kepner-Tregoe Problem Analysis is built on four fundamental steps:
Identifying the Problem
Analyzing the Problem
Considering Possible Solutions
Implementing the Best Solution
Each step requires meticulous attention but offers immense clarity. I found that by not skipping any stages, we could avoid the pitfalls of jumping to conclusions or implementing quick fixes that didn't last.
Identifying the problem: the first hurdle.
In our project, we initially thought the problem was the tight deadline imposed by upper management. It was easy to blame time constraints for our struggles. However, when we sat down and applied the first step of the Kepner-Tregoe method, we realized that the real issue was a lack of clear communication between departments.
I recall a meeting where team members from different departments admitted they weren't sure about their specific responsibilities. It was a lightbulb moment for all of us. The symptom was delays, but the underlying problem was ambiguity in role definitions.
With the problem identified, we moved on to analyzing it. We asked ourselves critical questions: Why was there a communication breakdown? Were there existing protocols that weren't being followed? Was there a cultural barrier between teams?
We used tools like cause-and-effect diagrams to map out potential factors. It turned out that recent organizational changes had altered reporting lines, and not everyone was updated. This gap led to confusion and duplicated efforts.
I felt a mix of frustration and relief. Frustration because the issue seemed so basic, and relief because we finally knew what we were dealing with.
The next step was to consider possible solutions . We gathered representatives from all departments for a brainstorming session. No idea was off the table. Some suggested regular inter-departmental meetings, others proposed a shared online platform for updates.
One of my colleagues, known for her creative flair, suggested we create an internal newsletter highlighting each team's progress. At first, it seemed unconventional, but the more we discussed it, the more it made sense. It would not only keep everyone informed but also foster a sense of community.
After evaluating all options, we decided on a multi-faceted approach:
Establishing a shared project management tool accessible to all relevant parties.
Scheduling weekly coordination meetings with clear agendas.
Launching the internal newsletter as a pilot project.
Implementing these solutions required commitment. There were initial hiccups—some team members were resistant to change, and there was a learning curve with the new software. But with persistence and open communication, we gradually saw improvements.
Deadlines were met, misunderstandings decreased, and there was a noticeable boost in team morale. Witnessing these positive changes reinforced my belief in the effectiveness of the Kepner-Tregoe method.
The benefits i've witnessed firsthand.
Adopting the Kepner-Tregoe Problem Analysis has been a game-changer. It provides a clear roadmap, reducing the overwhelming feeling that often accompanies complex problems. By breaking down issues into manageable steps, it becomes easier to tackle them systematically.
I've also found that this method promotes team collaboration. Everyone gets a chance to contribute, leading to more comprehensive solutions. It's not just about fixing a problem but also about enhancing overall team dynamics.
However, it's important to acknowledge that this approach isn't a one-size-fits-all solution. In crisis situations where immediate action is required, going through each step may not be feasible. I've been in scenarios where quick decision-making was essential, and lengthy analysis wasn't an option.
Additionally, the method relies heavily on accurate information. If the data collected is flawed, the analysis will be off-target. It's crucial to ensure that all information is verified and that team members are honest and open during discussions.
Personal life applications: more than a professional tool.
Interestingly, I've started applying the Kepner-Tregoe method to personal challenges as well. When faced with a significant financial decision, like buying a new home, my partner and I used this approach to weigh our options. We identified our needs, analyzed the housing market, considered various neighborhoods, and ultimately made a choice that we're happy with.
Another instance was when I was training for a marathon. After a minor injury, I had to reassess my training plan. Using the method, I identified the problem (overtraining), analyzed why it happened, considered solutions (rest, adjust the training schedule, consult a trainer), and implemented the best course of action.
I've become somewhat of an advocate for the Kepner-Tregoe method. Whenever colleagues or friends express frustration over complex issues, I share my experiences. Recently, a friend struggling with launching his startup applied this method and found clarity he hadn't achieved before.
It's rewarding to see others benefit from a tool that has had such a positive impact on my life. I believe that with the right guidance, anyone can adopt this approach to improve their decision-making skills.
The journey with Kepner-Tregoe Problem Analysis has taught me the value of patience, thoroughness, and collaboration. In a world that often demands quick fixes, taking the time to systematically address problems can lead to more sustainable solutions.
For anyone feeling overwhelmed by complex challenges—whether in business, personal projects, or daily life—I highly recommend exploring this method. It might require an initial investment of time and effort, but the long-term benefits are well worth it.
Helpful Resources:
Kepner-Tregoe Official Website : Offers detailed information and training options.
Fishbone Diagram Guide: A useful tool for root cause analysis.
Understanding kepner-tregoe problem analysis.
Kepner-Tregoe Problem Analysis stands on structured problem solving. It offers a comprehensive stepwise method. Businesses leverage it to pinpoint and resolve issues effectively. Four key principles form its foundation.
One must state the problem clearly. Ambiguity has no place here. A well-defined problem guides towards a solution. This involves describing what we observe. We avoid assumptions and generalizations.
Break the problem into smaller components. Analyze each piece individually. This simplification aids in managing complexity. It facilitates a more focused investigation. Understanding of each part becomes critical.
Seek the problem's origin. We gather and evaluate data methodically. It's about asking the right questions. Hypotheses form through this inquiry process. Each is tested against the facts.
We must consider potential solutions. Each option requires careful evaluation. Risks and benefits receive equal attention. The decision-making process is deliberate and logical. It leads to selecting the best solution.
Application in Real-World Scenarios
In practice, teams apply these principles systematically. They start by gathering information. Detail is key. Inferring causes happens next. It involves critical thinking. Potential solutions emerge through brainstorming. Decision-making follows. It sets action plans in motion. Monitoring outcomes forms the final step.
The success of Kepner-Tregoe Problem Analysis lies in its rigor. It demands discipline from practitioners. Structured problem-solving replaces intuition. Each step builds on the previous. This results in a robust solution process.
- Clarity : Define the problem precisely.
- Dissection : Break down complex issues.
- Root Cause : Search for underlying causes.
- Decision Analysis : Weigh all possible solutions.
These principles provide a lens for viewing problems. They force a systematic approach. Intuition blends with logic. This yields better decisions. Organizations that adopt these principles often see improved outcomes.
Kepner-Tregoe Problem Analysis reshapes how we approach challenges. The methodology instills a disciplined thinking process. Problems represent opportunities for improvement. The structured framework assists in capitalizing on these opportunities.
The analysis is not about quick fixes. It focuses on sustainable solutions. Teams become adept at identifying actionable intelligence. Insight replaces guesswork.
This strategy's adoption spans industries. It enhances capabilities in problem-solving. As a result, it contributes to organizational resilience. Effective problem resolution becomes a competitive advantage.
Kepner-Tregoe's principles guide us towards objective analysis. They champion a rational approach in chaotic environments. In essence, these principles encourage a mindset pivot. Problems change from stumbling blocks to stepping stones. They guide teams in navigating the complexities of business issues. The goal is to reach logical, data-driven conclusions every time.
In business and management, decision-makers confront complex challenges daily. These require structured methods to tackle effectively. Among these methods stands the Kepner-Tregoe Problem Analysis. It aids in streamlining and organizing the problem-solving process.
The Kepner-Tregoe approach comprises four key stages. These stages are Situation Appraisal , Problem Analysis , Decision Analysis , and Potential Problem Analysis .
- Situation Appraisal - Identify the issue .
- Problem Analysis - Clarify the problem .
- Decision Analysis - Evaluate alternatives .
- Potential Problem Analysis - Anticipate future issues .
This structured sequence prevents haphazard decision-making. It encourages methodical progression through problems.
Each stage in the Kepner-Tregoe model serves to simplify decisions. Here's how:
- Clarify concerns. Essential for mastering complex situations.
- Establish priorities. Critical in focusing efforts and resources.
- Evaluate information. Ensures decisions rely on factual data.
- Generate solutions. Opens avenues for innovative thinking and solutions.
- Assess risks. Prepares for potential future complications.
The Kepner-Tregoe method promotes incremental learning. Decision-makers build on foundational knowledge. Each problem teaches new lessons. Each decision draws on past experiences.
Clear communication is fundamental in complex scenarios. The Kepner-Tregoe process requires clear articulation of issues. It mandates detailed discussion of potential solutions. As a result, it enhances team understanding and synergy.
The method strives for actionable outcomes. It avoids indecision and theoretical loops. It leans on pragmatic steps towards solution implementation.
Logical sequencing.
The approach enforces logical order in addressing problems. It detangles complexities through systematic analysis. This logical sequence guides decision-makers and reduces the risk of oversight.
Each step requires thorough examination of present elements. This scrutiny reveals root causes. It avoids superficial judgments common in hurried decisions.
With its focus on priorities, the method ensures efficient resource allocation. It aids in distinguishing critical issues from less urgent ones. This ensures the most significant concerns receive needed attention.
The final stage, Potential Problem Analysis, prepares for future uncertainties. It strengthens strategies and renders them more robust.
Employing the Kepner-Tregoe Problem Analysis leads to structured, simplified decision-making. It equips decision-makers to untangle complexities. It provides a blueprint guiding them to judicious, informed choices.
Introduction to kepner-tregoe problem analysis.
Kepner-Tregoe Problem Analysis offers a systematic method. It aids in solving complex issues. Organizations widely apply this method. It structures the problem-solving process effectively. Here, we dissect this technique into sequential steps.
Step 1: describe the problem.
Begin by stating the issue clearly. Focus on what you observe. Detail what , where , when , and extent . Each factor helps in understanding the issue's scope.
- Identify what is wrong
- Specify where the issue occurs
- Note when it happens
- Quantify the issue's extent
Determining urgency is vital. Consider the problem's effect on operations. Ask which issue to tackle first. Prioritize based on impact and urgency.
- Assess the problem's impact
- Rank based on urgency
List all potential causes. Think broadly and creatively. Consider every possible source. Your goal is to not miss any potential cause.
- Brainstorm all possible causes
- Be inclusive and creative
Examine each cause critically. Collect data and evidence. Contrast each cause against your problem description. Look for patterns that match.
- Gather data on causes
- Compare against problem specifics
Now, verify the likely cause. Create an experiment or a test. Ensure the test is controlled. Gather results diligently.
- Conduct a controlled test
- Collect and record results
Assess your test findings. Check if the cause and effect align. Confirm if the cause explains all the problem aspects. Ensure no contradiction exists.
- Review test outcomes
- Ensure cause-effect consistency
After confirming the cause, act on it. Develop a plan to address the issue. Implement your solution with care. Monitor the results closely.
- Develop an action plan
- Execute and observe
Monitoring is a critical follow-up. Check if the problem resolves. Note any unforeseen effects. Adjust your actions as required.
- Track the problem resolution
- Adjust as needed
Kepner-Tregoe Problem Analysis is a disciplined approach. It ensures effective issue resolution. It demands clear thinking and precise action. Employing this method offers a higher probability of solving complex problems efficiently.
He is a content producer who specializes in blog content. He has a master's degree in business administration and he lives in the Netherlands.
Department of Psychological and Brain Sciences, University of California, Santa Barbara
Problem solving refers to cognitive processing directed at achieving a goal when the problem solver does not initially know a solution method. A problem exists when someone has a goal but does not know how to achieve it. Problems can be classified as routine or nonroutine, and as well defined or ill defined. The major cognitive processes in problem solving are representing, planning, executing, and monitoring. The major kinds of knowledge required for problem solving are facts, concepts, procedures, strategies, and beliefs. Classic theoretical approaches to the study of problem solving are associationism, Gestalt, and information processing. Current issues and suggested future issues include decision making, intelligence and creativity, teaching of thinking skills, expert problem solving, analogical reasoning, mathematical and scientific thinking, everyday thinking, and the cognitive neuroscience of problem solving. Common themes concern the domain specificity of problem solving and a focus on problem solving in authentic contexts.
Sign in with a library card.
Access to content on Oxford Academic is often provided through institutional subscriptions and purchases. If you are a member of an institution with an active account, you may be able to access content in one of the following ways:
Typically, access is provided across an institutional network to a range of IP addresses. This authentication occurs automatically, and it is not possible to sign out of an IP authenticated account.
Choose this option to get remote access when outside your institution. Shibboleth/Open Athens technology is used to provide single sign-on between your institution’s website and Oxford Academic.
If your institution is not listed or you cannot sign in to your institution’s website, please contact your librarian or administrator.
Enter your library card number to sign in. If you cannot sign in, please contact your librarian.
Society member access to a journal is achieved in one of the following ways:
Many societies offer single sign-on between the society website and Oxford Academic. If you see ‘Sign in through society site’ in the sign in pane within a journal:
If you do not have a society account or have forgotten your username or password, please contact your society.
Some societies use Oxford Academic personal accounts to provide access to their members. See below.
A personal account can be used to get email alerts, save searches, purchase content, and activate subscriptions.
Some societies use Oxford Academic personal accounts to provide access to their members.
Click the account icon in the top right to:
Oxford Academic is home to a wide variety of products. The institutional subscription may not cover the content that you are trying to access. If you believe you should have access to that content, please contact your librarian.
For librarians and administrators, your personal account also provides access to institutional account management. Here you will find options to view and activate subscriptions, manage institutional settings and access options, access usage statistics, and more.
Our books are available by subscription or purchase to libraries and institutions.
Month: | Total Views: |
---|---|
October 2022 | 13 |
November 2022 | 25 |
December 2022 | 17 |
January 2023 | 10 |
February 2023 | 20 |
March 2023 | 43 |
April 2023 | 24 |
May 2023 | 89 |
June 2023 | 78 |
July 2023 | 7 |
August 2023 | 10 |
September 2023 | 9 |
October 2023 | 13 |
November 2023 | 34 |
December 2023 | 18 |
January 2024 | 6 |
February 2024 | 28 |
March 2024 | 27 |
April 2024 | 95 |
May 2024 | 72 |
June 2024 | 98 |
July 2024 | 9 |
August 2024 | 17 |
September 2024 | 20 |
Oxford University Press is a department of the University of Oxford. It furthers the University's objective of excellence in research, scholarship, and education by publishing worldwide
Sign In or Create an Account
This PDF is available to Subscribers Only
For full access to this pdf, sign in to an existing account, or purchase an annual subscription.
The Center for High Throughput Computing's (CHTC) Research Computing Facilitation team introduces researchers to large-scale computational approaches and enables their use of large-scale computing systems like CHTC's in-house clusters and the Open Science Pool and PATh Facility (operated by the NSF Partnership to Advance Throughput Computing project). This role provides support in many forms, including one-on-one consultation, collaborative problem-solving, documentation and training, and community building. There are also opportunities to provide feedback within collaborating teams to continuously improve the user experience of system features. The preferred applicant will be able to learn unfamiliar technologies and successfully collaborate with their teammates and other teams in the organization. They will also be able to communicate about technical concepts to a general audience, have prior experience and interest in enabling the work of others, and have a desire for continuous learning. New team members will be supported in learning about high-throughput technologies and supporting High-Throughput Computing workloads.
Diversity is a source of strength, creativity, and innovation for UW-Madison. We value the contributions of each person and respect the profound ways their identity, culture, background, experience, status, abilities, and opinion enrich the university community. We commit ourselves to the pursuit of excellence in teaching, research, outreach, and diversity as inextricably linked goals. The University of Wisconsin-Madison fulfills its public mission by creating a welcoming and inclusive community for people from every background - people who as students, faculty, and staff serve Wisconsin and the world. For more information on diversity and inclusion on campus, please visit: Diversity and Inclusion
Required Master's Degree with research experience OR a Bachelor's degree with at least 2 years working in a research environment.
Required: - Experience using the Unix shell. - Familiarity with at least one scripting or programming language besides Unix, i.e. Python, or R. - One year of experience in communicating complex research or technical topics to a novice audience, as an instructor, teaching assistant, research computing facilitator, or similar roles. - Demonstrated interest and prior experience in facilitating education of others to enable their work. Preferred: - Teaching experience in a research or compute-intensive area, contributions to computation focused training efforts (for example: Software Carpentry) or experience in research computing facilitation. - Experience and demonstrated interest in teaching, curriculum development, and/or formal communication activities. - Experience and demonstrated interest in community building and mentoring. - Experience using version control software (Git, GitHub, GitLab). - Prior usage of large-scale, batch computing systems. - Familiarity with campus research computing centers/services or the OSG Consortium. - Experience using computation in a research domain, especially climate science, bioinformatics, social sciences or humanities - Significant experience with applications of computing for research purposes. Examples include: Data pipeline development and execution, Installing and running scientific software on Linux, Executing machine learning workloads on GPUs
Full Time: 100% It is anticipated this position requires work be performed in-person, onsite, at a designated campus work location.
Ongoing/Renewable
Minimum $71,994 ANNUAL (12 months) Depending on Qualifications Actual salary will depend on experience and qualifications. Employees in this position can expect to receive benefits such as generous vacation, holidays and paid time off; competitive insurances and saving accounts; and retirement benefits.
The Center for High Throughput Computing (CHTC) seeks a Research Computing Facilitator to support the goals of a diverse set of researchers who use computing for their research. This is an ideal position for an academic researcher who has used computational approaches in their own work and is strongly motivated to support and empower the work of other researchers through access to large-scale computing resources.
At UW-Madison, we are dedicated to building a diverse, inclusive, and authentic workplace, so if you're excited about this role, we encourage you to apply.
Please click on the "Apply Now" button to start the application process. Applications must be submitted by 11:55 pm on the deadline date. To apply, please upload a cover letter and resume. Your cover letter and resume should address how your skills, knowledge, and abilities are transferrable to the qualifications of this role. Additional materials submitted other than your cover letter and resume will not be considered. This position will have a two-step interview process. Once final applicants are identified, they will be asked to provide names and contact information for at least three professional references, including a current/most recent supervisor. We are committed to reducing bias in the recruitment process and utilize a redacted application process, which is the practice of removing personally identifiable information from application materials, before the screening of applicants begins. This may include, but is not limited to, name, gender, age, address, and photos. For questions on the position, contact: Christina Koch, [email protected]
Christina Koch [email protected] 608-316-4041 Relay Access (WTRS): 7-1-1. See RELAY_SERVICE for further information.
Research CI Facilitator II(RE078)
A48-COL OF LETTERS & SCIENCE/COMPUTER SCI/COMP SCI
Academic Staff-Renewable
The university of wisconsin-madison is an equal opportunity and affirmative action employer..
You will be redirected to the application to launch your career momentarily. Thank you!
Frequently Asked Questions
Applicant Tutorial
Disability Accommodations
Pay Transparency Policy Statement
You've sent this job to a friend!
Website feedback, questions or accessibility issues: [email protected] .
Learn more about accessibility at UW–Madison .
© 2016–2024 Board of Regents of the University of Wisconsin System • Privacy Statement
Would you like to sign-up for job alerts.
Thank you for subscribing to UW–Madison job alerts!
By Alexa Vazquez
Mingxi Tang studied finance at The Chinese University of Hong Kong, Shenzhen, and had plans to pursue a career in the industry after graduation. Her path took a sudden turn the day she discovered a video on the UC Berkeley website — an introduction to the Master of Development Engineering program.
The video showcased MDevEng professors working in under-resourced regions across the world, striving to improve the lives of people living in low-income communities using technology to measure soil nutrients for crop growth. Inspired by the various student projects she saw on the website, Tang applied, was accepted, and packed her bags for Berkeley.
“Honestly, I was really moved. I knew I had to apply to the program, because I wanted to learn the technical skills I need to help people live better lives,” Tang said.
Tang is now one of the 28 students that make up the fourth MDevEng cohort. The class of 2025 comes from all over the world, with students hailing from China, Uganda, Ireland, and beyond, and having academic backgrounds ranging from mechanical engineering to applied languages. On August 22, Tang met up with the rest of her classmates — each pursuing their own concentrations such as sustainable design and AI and data analytics — at Blum Hall for the start of MDevEng orientation.
“We’re all coming from different disciplines and communities, and now we’ll learn how to work together,” MDevEng Program Director Yael Perez said to the new cohort to kick off orientation.
The MDevEng program is a 15-month experience merging in-depth technology studies with human development courses to prepare students for careers in social impact, social entrepreneurship, and sustainability. Over three semesters, students engage in technical problem solving, cross-cultural collaboration, and community development, including a summer internship and a final capstone project.
Previous MDevEng students have played a pivotal role in developing solutions to social initiatives across the world, including assessing the effectiveness of health clinics’ off-grid power systems in rural Rwanda; developing FireTools, a platform designed to support local decision-makers in improving disaster preparedness for low-resource communities; and empowering women in English-speaking African countries by offering training in advanced digital skills, helping to boost female employment opportunities in technology fields.
During the reception for the incoming cohort, Blum Chancellor’s Chair in Development Engineering and Professor Kara Nelson offered advice on how to make the most of the three-semester program, drawing from her own career pathway to share her experience with students. Nelson described how she was often told to stick to a single field of study, reflecting on the limitations of engineering programs of the past.
“This program did not exist when I was a student. Professors would meet with me [about my project ideas] and tell me ‘you can’t do that!’ But today, we’re here to tell you that ‘you can do that!’” Nelson said. “You all have your own interests, your own backgrounds, and you know what your vision is. We’re here to support you and help you paint that path.”
Among the cohort, many students share the common goal of applying AI and emerging technologies to create sustainable solutions for improving quality of life. Tang, for instance, aims to develop her skills in supervised machine learning to create technology that can improve the lives of people with disabilities.
“I want to acquire a lot of skills during my time here and use my knowledge about AI and machines to help improve people’s lives,” Tang said. “With the kind of experience this program can offer me, I feel like I can definitely achieve that.”
Throughout orientation, many students vocalized similar aspirations to serve underprivileged communities, among them Pratiyush Singh, a Berkeley graduate who studied civil engineering and is passionate about addressing climate adaptation and water quality issues in India and Africa.
After two years in industry, Singh saw a disconnect between his work and the communities he aimed to serve. This pushed him to apply to the MDevEng program, where he wanted to employ his expertise in a more impactful way. Singh found the program unique in that it allowed him greater control over the kind of projects he would work on, and a focus on practical application rather than traditional learning methods.
“Through this program, I want to learn more about using AI and data to scale technologies for low-resource communities,” he said. “I’m going to continue my past work that focused on addressing water quality challenges, and hopefully I’ll improve along the way.”
During orientation, students participated in an activity where they answered what Development Engineering meant to them using a single word. Common responses displayed on the projector screen included “sustainable,” “solutions,” and “community.” However, Singh’s choice of the word “minority” stood out to the cohort.
“I think of it as justice engineering at the end of the day, because the solutions we’re creating are taken to and impacting minority communities,” Singh explained. “I feel like when you address those problems, it’s a form of social justice.”
Orientation concluded with an alumni panel featuring Morris Chang , Kaavya “Kavi” Reddy , and Kangogo Sogomo from previous MDevEng cohorts, followed by a social mixer that brought together past and current cohorts, as well as MDevEng faculty and staff. It was the first event of its kind for an MDevEng orientation.
Reddy, an alum from the first MDevEng class, invited students interested in working with climate change and government organizations to talk to her during the mixer and exchange ideas. Now working with the science-entrepreneurship nonprofit ACTIVATE, Reddy, who started her own concentration while at Berkeley, encouraged the class to pursue projects they were passionate about.
She concluded with a powerful piece of advice: “Take Development Engineering and make it work for you!”
She elaborated, “If you go out [into the workforce] and you’re not really sure where you fit in [as a DevEnger,] then you’re feeling exactly what you’re supposed to,” Reddy said. “We’re so brand new that we’re bringing this entire discipline to the world.”
Kevin Kung, co-founder of Takachar, began his climate innovation journey at UC Berkeley’s Blum Center through the 2015 Big Ideas Contest. Now hosting California Climate Action Fellows, Takachar helps transform agricultural waste into bioproducts, emphasizing a human-centered approach that addresses environmental challenges and supports underserved communities.
We are thrilled to welcome Dr. Doll as our new lecturer for GPP 115. This course serves students all across campus, introducing them to historical and contemporary debates on addressing poverty and inequality in the world. Dr. Doll’s extensive experience in the disciplines of critical development studies, political ecology, and cultural geography will bring a valuable perspective to this course.
Last month, the Global Poverty and Practice minor’s Class of 2024 celebrated a hard-earned and well-deserved commencement with an intimate ceremony in Sutardja Dai Hall’s Banatao Auditorium.
USAID Digital Workforce Development program, which launched in 2022, has strengthened the information and technology (ICT) skills of Cambodian faculty, developed career centers at their universities, overseen skills training for students, and provided scholarships in the digital and ICT fields, particularly for rural, female students.
Host organizations.
IMAGES
VIDEO
COMMENTS
Here are the seven steps of the rational approach: Define the problem. Identify possible causes. 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.
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 ...
1. Define the problem. Diagnose the situation so that your focus is on the problem, not just its symptoms. Helpful problem-solving techniques include using flowcharts to identify the expected steps of a process and cause-and-effect diagrams to define and analyze root causes.. The sections below help explain key problem-solving steps.
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.
Problem-solving is a mental process that involves discovering, analyzing, and solving problems. The ultimate goal of problem-solving is to overcome obstacles and find a solution that best resolves the issue. The best strategy for solving a problem depends largely on the unique situation. In some cases, people are better off learning everything ...
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 involves taking certain steps and using psychological strategies. Learn problem-solving techniques and how to overcome obstacles to solving problems. ... If you have time, you can take advantage of the algorithm approach to problem-solving by sitting down and making a flow chart of each potential solution, its consequences, and ...
BROWSE ALL POSTS. In a volatile world, one thing's certain: there will never be a shortage of problems to solve. McKinsey Global Institute director and senior partner Chris Bradley, a coauthor of Strategy Beyond the Hockey Stick, observed that "it's a mistake to think that on your team you have the smartest people in the room.
Tried-and-tested problem-solving techniques can be useful. However, they don't teach you how to innovate and develop your own problem-solving approaches. Sometimes, an unconventional approach can lead to the development of a brilliant new idea or strategy. So don't be afraid to suggest your most "out there" ideas. 7.
In our 2013 classic from the Quarterly, senior partner Olivier Leclerc highlights the value of taking a number of different approaches simultaneously to solve difficult problems. Read on to discover the five flexons, or problem-solving languages, that can be applied to the same problem to generate richer insights and more innovative solutions.
Each problem-solving strategy includes multiple steps to provide you with helpful guidelines on how to resolve a business problem or industry challenge. Effective problem-solving requires you to identify the problem, select the right process to approach it and follow a plan tailored to the specific issue you are trying to solve.
4. Implement the Solution. At this stage of problem solving, be prepared for feedback, and plan for this. When you roll out the solution, request feedback on the success of the change made. 5. Review, Iterate, and Improve. Making a change shouldn't be a one time action.
Creative problem solving (CPS) is a method of problem solving in which you approach a problem or challenge in an imaginative, innovative way. The goal of CPS is to come up with innovative solutions, make a decision, and take action quickly. Sidney Parnes and Alex Osborn are credited with developing the creative problem solving process in the 1950s.
The 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:
How to Solve Problems. To bring the best ideas forward, teams must build psychological safety. Teams today aren't just asked to execute tasks: They're called upon to solve problems. You'd ...
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.
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.
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 ...
Phase 4: Elevate. This phase involves exploring how the problem connects to broader organizational issues. It's like zooming out on a map to understand where a city lies in relation to the whole ...
• Approach a problem with curiosity, openness and fewer certainties. • Investigate before solving and treat certainties as doubts that need to be proven. • Learn to listen genuinely.
Planning skills are vital in order to structure, deliver and follow-through on a problem solving workshop and ensure your solutions are intelligently deployed. Planning skills include the ability to organize tasks and a team, plan and design the process and take into account any potential challenges.
Creative Problem-Solving and Design Thinking. Whereas creative problem-solving facilitates developing innovative ideas through a less structured workflow, design thinking takes a far more organized approach. Design thinking is a human-centered, solutions-based process that fosters the ideation and development of solutions.
This method provided a structured approach to peel back the layers and see the core of the problem. Breaking Down the Method: Four Essential Steps. The Kepner-Tregoe Problem Analysis is built on four fundamental steps: Identifying the Problem. Analyzing the Problem. Considering Possible Solutions. Implementing the Best Solution
The major cognitive processes in problem solving are representing, planning, executing, and monitoring. The major kinds of knowledge required for problem solving are facts, concepts, procedures, strategies, and beliefs. Classic theoretical approaches to the study of problem solving are associationism, Gestalt, and information processing.
Job Summary: The Center for High Throughput Computing's (CHTC) Research Computing Facilitation team introduces researchers to large-scale computational approaches and enables their use of large-scale computing systems like CHTC's in-house clusters and the Open Science Pool and PATh Facility (operated by the NSF Partnership to Advance Throughput Computing project). This role provides support in ...
To optimize the DFLP using dynamic programming (DP), the DP state space should be restricted as the problem is NP-hard. Therefore, a two-phased hybridized solution algorithm is being proposed and developed in this article. In the first phase, a heuristic approach is used to determine the set of layouts to be considered in each period.
The Blum Center for Developing Economies leverages the talent, enthusiasm, and energy of the University of California, Berkeley community to address the grand challenge of global poverty. Our interdisciplinary problem-solving approach draws on students and faculty dedicated to facing this challenge through innovative initiatives, education, and research.