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.
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:.
A proactive approach to technical debt leads to faster recovery, better performance, and a healthier product. With the right strategies, you can manage it without sacrificing innovation.
Product management and product marketing both contribute to the success of a product in their own capacity.
Ravit Danino talks about how knowing where customers are aiming helps you better frame the discussion around your roadmap.
Microservices architecture transforms how we build applications, but what does that mean for a product manager? In this blog, I talk about why mastering microservices is essential for modern product management.
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.
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.
Methodology of 8D (Eight Discipline) Problem Solving:
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.
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.
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.
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.
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.
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.
You’ll be able to tell which solutions are likely to succeed and which aren’t by assessing their feasibility and practicability.
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.
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.
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.
Daniel croft, 14 principles of the toyota production system: a comprehensive guide, understanding the cost of good quality: investing in quality pays off, understanding process performance: pp and ppk.
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…
What is problem-solving and how to do it right steps, processes, exercises.
The better your problem-solving skills are, the better (and easier!) your life will be. Organized problem-solving is a killer career skill - learn all about it here.
Whether we’re trying to solve a technical problem at work, or trying to navigate around a roadblock that Google Maps doesn’t see – most people are problem-solving every single day .
But how effective are you at tackling the challenges in your life? Do you have a bullet-proof process you follow that ensures solid outcomes, or... Do you act on a whim of inspiration (or lack thereof) to resolve your pressing problems?
Here’s the thing: the better your problem-solving skills are - the better (and easier!) your life will be (both professionally and personally). Organized problem-solving is a killer career (and life!) skill, so if you want to learn how to do it in the most efficient way possible, you’ve come to the right place.
Read along to learn more about the steps, techniques and exercises of the problem-solving process.
We’re faced with the reality of having to solve problems every day, both in our private and professional lives. So why do we even need to learn about problem-solving? Aren’t we versed in it well enough already?
Well, what separates problem-solving from dealing with the usual day-to-day issues is that it’s a distinct process that allows you to go beyond the standard approaches to solving a problem and allows you to come up with more effective and efficient solutions. Or in other words, problem-solving allows you to knock out those problems with less effort.
Just like with any other skill, there’s an efficient way to solve problems, and a non-efficient one. While it might be tempting to go for the quickest fix for your challenge without giving it much thought, it will only end up costing you more time down the road. Quick fixes are rarely (if ever!) effective and end up being massive time wasters.
What separates problem-solving from dealing with the usual day-to-day issues is that it’s a distinct process that allows you to go beyond the standard approaches to solving a problem and allows you to come up with more effective and efficient solutions.
On the other hand, following a systemized clear process for problem-solving allows you to shortcut inefficiencies and time-wasters, turn your challenges into opportunities, and tackle problems of any scope without the usual stress and hassle.
What is the process that you need to follow, then? We’re glad you asked...
So what’s the best way to move through the problem-solving process? There’s a 5-step process that you can follow that will allow you to solve your challenges more efficiently and effectively. In short, you need to move through these 5 steps:
Let’s look at each of those stages in detail.
The first step might sound obvious, but trust us, you don’t want to skip it! Clearly defining and framing your challenge will help you guide your efforts and make sure you’re focussing on the things that matter, instead of being distracted by a myriad of other options, problems and issues that come up.
For once, you have to make sure you’re trying to solve the root cause, and not trying to mend the symptoms of it. For instance, if you keep losing users during your app onboarding process, you might jump to the conclusion that you need to tweak the process itself: change the copy, the screens, or the sequence of steps.
But unless you have clear evidence that confirms your hypothesis, your challenge might have an entirely different root cause, e.g. in confusing marketing communication prior to the app download.
Clearly defining and framing your challenge will help you guide your efforts and make sure you’re focussing on the things that matter, all the while ensuring that you’re trying to solve the root cause, and not trying to mend the symptoms of it
That’s why it’s essential you take a close look at the entire problem, not just at a fraction of it.
There are several exercises that can help you get a broader, more holistic view of the problem, some of our all-time favorites include Expert Interviews, How Might We, or The Map. Check out the step-by-step instructions on how to run them (along with 5 more exercises for framing your challenge!) here.
When in doubt, map out your challenge, and always try to tackle the bottlenecks that are more upstream - it’s likely that solving them will solve a couple of other challenges down the flow.
You also have to be mindful of how you frame the challenge: resist the urge to include a pre-defined solution into your problem statement. Priming your solutions to a predestined outcome destroys the purpose of following a step-by-step process in the first place!
Steer clear of formulations like:
We need to change the onboarding process... or We need to improve ad copy to increase conversions.
Instead, opt for more neutral, problem-oriented statements that don’t include a solution suggestion in them:
The drop off rate during the onboarding process is too high or Our ad conversion rates are below the norm.
Pro tip: Reframing your challenge as a ‘How Might We’ statement is a great way to spark up new ideas, opening your problem to a broader set of solutions, and is just a great way to reframe your problem into a more positive statement (without implying the possible solution!)
For example, following the onboarding drop-off rate problem we mentioned earlier, instead of framing it as a problem, you could opt for:
How Might We decrease the drop-off rate during the onboarding process?
Find out more about the best exercises for problem framing here!
Now that you have a clear idea of what you’re trying to solve, it’s move on to the next phase of the problem-solving process.
Step 2: ideating a solution.
Get ready to roll up your sleeves and challenge the status quo! This step of the problem-solving process is all about thinking outside of the box, challenging old assumptions, and thinking laterally.
This stage is the one that tends to cause the most overwhelm in teams because it requires just the right balance of creativity and critical thinking, which tends to cause a lot of friction.
Our best advice?
Let go of the pressure to produce a polished, thought-through solution at this stage. You can hash out the details at a later point. Our goal right now is to come up with a direction, a prototype if you may, of where we want to move towards.
Embrace the “quantity over quality” motto, and let your creative juices flow! Now, we’re not saying you should roll with sub-par ideas. But you shouldn’t get too fixated on feasibility and viability just yet .
Your main goal during this step is to spark ideas, kick off your thinking process in the right direction, venture out of the familiar territories and think outside the box.
For the ideation to be the most effective your team will have to feel safe to challenge the norm and wide-spread assumptions. So lay judgment by side, there is no space for “that’s the way it’s always been done” in this step.
For your ideation sessions to be as efficient as possible, we highly recommend to run them in a workshop setting: this helps reduce the usual drawbacks of open discussions in teams (i.e. groupthink & team politics!)
Our favorite exercises to run during this phase include Lightning Demos, Sketching, and variations of Brainstorming. We crafted an entire article on how to run and facilitate these exercises in a separate article, so check it out of you’re going to be running an ideation session anytime soon!
It’s time to decide which of the ideas that you generated in the last step will be the one you’ll implement.
This step is arguably the hardest one to complete smoothly: groupthink, team politics, differences in opinions and communication styles all make it very hard to align a team on a common course of action.
If you want to avoid the usual pitfalls of team decision-making, we recommend you steer clear of open unstructured discussion. While it’s useful in some scenarios, it’s a poor choice for when you need to make a decision, because it tends to reward the loudest people in the room, rather than give way to the best ideas.
It’s crucial you not only commit to a course of action but get full buy-in from the team. If your team members don’t understand the reasons for a decision, or are not fully onboard, the implementation of your decision will be half-hearted, and that’s definitely not what you want!
To achieve that, opt for anonymized, multi-layered voting, and include guided exercises like Storyboarding to prioritize your ideas.
We’ve gathered the list of our top-rated decision-making exercises, along with step-by-step instructions on how to run them in this article!
As a bonus tip, we recommend you involve a facilitator throughout the entire process. They will help align the team, and guide them through prioritizing and de-prioritizing solutions, as well as defining the next steps.
Pro tip : If you’re not the ultimate decision maker on the issue you’re trying to solve, make sure they’re in the room when the call is being made! Having a Decider in the room ensures that the decisions you come to will actually get executed on after, instead of getting shut down by your superiors after.
Step 4: implementing your solution.
Here’s a truth that might be hard to swallow: it doesn’t matter how innovative, creative, or original your idea is, if your execution is weak.
One of our favourite illustrations of how this works in practice comes from the book “ Anything you want ” by Derek Sivers. He reveals that ideas should be treated as multipliers of execution. What this means is that a mediocre, “so-so” idea could be worth millions if executed well, while a “brilliant” idea can completely flop with bad execution.
That’s why this step is crucial if you want to really master the problem-solving process.
What do we mean by execution? Everything that happens after the whiteboards are wiped clean and your team starts to action the outcomes of your sessions, be it prototyping, development, or promotion.
But don’t just take our word for it, look at the example of how execution affected Nintendo’s sales:
In the past few years, Nintendo has come up with 3 products: the Wii, the Wii U and the Switch. Check out their sales figures on the graph below - Wii is the clear-cut leader, followed by Switch, and finally Wii U lagging behind.
The Wii was unbelievably successful - it was a genuinely unique, “brilliant”-level idea and it had a “brilliant” execution (20x $10 million = $200 million). It is one of the fastest selling game consoles of all time and it completely took over the market.
The next product was called Wii U and it was a “great” concept but the execution was absolutely terrible. So even though this product was very interesting and innovative, the end result was 15x $1,000 = $15,000.
Finally, Nintendo took the Wii U concept and tried it again with the Switch. The idea was “so so” as it was already done before, but the execution was “brilliant”. So, 5x $10 million = $50 million! Much better.
Bottom line?
The same idea can either make no dent in the market and damage your share price OR become a market hit and increase your share price dramatically. The only difference between the two scenarios – execution.
So shift your focus from coming up with crazy, innovative, outlandish ideas that will disrupt the market, and concentrate on really nailing down your execution instead.
This is likely the least “workshoppy” step out of the entire problem-solving process because it requires less alignment and decision-making and more..well.. Execution!
But hey, we wouldn’t be called “Workshopper” if we didn't offer you at least one way to optimize and workshopify (yup, we’re making it a thing) your execution process.
Cue in….prototyping.
We’re huge fans of prototyping all big solutions (and testing them!) The main reason?
This saves us time AND money! Prototyping and testing your solutions (especially if they’re time and investment-demanding) is a great way to make sure you’re creating something that is actually needed.
The key with prototyping the right way is to keep it simple. Don’t invest too much time, or resources into it. The goal is to gather data for your future decisions, not to create a near-to-perfect mockup of your solution.
There are LOADS of prototyping forms and techniques, and if you’d like to learn more on the subject you should definitely check out our extensive prototyping guide.
You’re nearly done, woo! Now that you have defined the right problem to tackle, brainstormed the solutions, aligned your team on the course of action, and put your plan into action it’s time to take stock of your efforts.
Seek feedback from all involved parties, analyze the data you’ve gathered, look at the bottom line of your efforts, and take a hard look at your problem: did it get solved? And even more than that, did the process feel smoother, easier, and more efficient than it normally is?
Running a retrospective is a great way to highlight things that went well and that you should keep for your next round of problem.solving, as well as pinpoint inefficiencies that you can eliminate.
But which kind of retrospective should you run? There are loads of options, and it’s easy to feel overwhelmed by them all, so we gathered our favorite retrospective variations in this article.
And there you have it, you just completed the cycle of problem-solving. We highly recommend you follow through with all the steps, without leaving any out. They all complement and build on each other, and it’s the combination of all 5 of them that makes the process effective.
Now that you have the problem solving process down, you might be wondering…
Do I need any special skills in order to be able to move through that process?
And the answer is… sort of! More in this in the next section.
While your skill set will need to adapt and change based on the challenges you’ll be working on, most efficient problem-solvers have a solid foundation of these key skills:
Not checking every single skill of your list just yet? Not to worry, the next section will give you practical tools on how to level up and improve your problem-solving skills.
Just like with any other skill, problem-solving is not an innate talent that you either have or you don’t. There are concrete steps you can take to improve your skills.
Here are some things that will get you closer to mastering the problem-solving process:
Practice makes perfect, and problem-solving skills are no exception! Seek opportunities to utilize and develop these skills any time you can.
If you don’t know where or how to start just yet, here’s a suggestion that will get you up and running in no time: run a quick problem-solving session on a challenge that has been bothering your team for a while now.
It doesn’t need to be the big strategic decision or the issue defining the future of the company. Something easy and manageable (like optimizing office space or improving team communication) will do.
As you start feeling more comfortable with the problem-solving techniques, you can start tackling bigger challenges. Before you know it, you’ll master the art of creative problem-solving!
Facilitation is one of the essential skills for problem-solving. But here’s the thing… Facilitation skills on their own won’t lead you to a solved challenge.
While being able to shortcut aimless discussions is a great skill, you have to make sure your problem-solving session has tangible outcomes. Using a tried and tested method, a workshop, is one of the easiest ways to do that.
Our best advice is to get started with a tried and tested problem-solving workshop like the Lightning Decision Jam . The LDJ has all the right ingredients for quick, effective problem solving that leads to tangible outcomes. Give it a go!
You may have colleagues who are skilled problem solvers. Observing how those colleagues solve problems can help you improve your own skills.
If possible, ask one of your more experienced colleagues if you can observe their techniques. Ask them relevant questions and try to apply as many of the new found skills i your career as possible.
Having a toolbox of problem-solving exercises to pull from that can fit any type of challenge will make you a more versatile problem-solver and will make solving challenges that much easier for you!
Once you get used to the groove of learning how to combine them into effective sessions or workshops, there’ll be no stopping you. What are some of the most effective problem-solving exercises? Glad you asked! We’ve gathered our favorite ones here, check it out!
And there you have it, you’re now fully equipped for running creative problem-sessions with confidence and ease! Whichever method or exercise you choose, remember to keep track of your wins, and learn as much as you can from your losses!
Anastasia Ushakova
Brand Strategist, Digital Marketer, and a Workshopper.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus.
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 .
5 steps (and 4 techniques) for effective problem solving.
Problem solving is the process of reviewing every element of an issue so you can get to a solution or fix it. Problem solving steps cover multiple aspects of a problem that you can bring together to find a solution. Whether that’s in a group collaboratively or independently, the process remains the same, but the approach and the steps can differ.
To find a problem solving approach that works for you, your team, or your company, you have to take into consideration the environment you’re in and the personalities around you.
Knowing the characters in the room will help you decide on the best approach to try and ultimately get to the best solution.
5 problem solving steps, 4 techniques to encourage problem solving, the bottom line.
No matter what the problem is, to solve it, you nearly always have to follow these problem solving steps. Missing any of these steps can cause the problem to either resurface or the solution to not be implemented correctly.
Once you know these steps, you can then get creative with the approach you take to find the solutions you need.
You must define and understand the problem before you start, whether you’re solving it independently or as a group. If you don’t have a single view of what the problem is, you could be fixing something that doesn’t need fixing, or you’ll fix the wrong problem.
Spend time elaborating on the problem, write it down, and discuss everything, so you’re clear on why the problem is occurring and who it is impacting.
Once you have clarity on the problem, you then need to start thinking about every possible solution . This is where you go big and broad, as you want to come up with as many alternative solutions as possible. Don’t just take the first idea; build out as many as you can through active listening, as the more you create, the more likely you’ll find a solution that has the best impact on the team.
Whichever solution you pick individually or as a team, make sure you think about the impact on others if you implement this solution. Ask questions like:
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.
Making a change shouldn’t be a one time action. Spend time reviewing the results of the change to make sure it’s made the required impact and met the desired outcomes.
Make changes where needed so you can further improve the solution implemented.
Each individual or team is going to have different needs and may need a different technique to encourage each of the problem solving steps. Try one of these to stimulate the process.
The 1-2-4-All is a good problem solving approach that can work no matter how large the group is. Everyone is involved, and you can generate a vast amount of ideas quickly.
Ideas and solutions are discussed and organized rapidly, and what is great about this approach is the attendees own their ideas, so when it comes to implementing the solutions, you don’t have more work to gain buy-in.
As a facilitator, you first need to present the group with a question explaining the problem or situation. For example, “What actions or ideas would you recommend to solve the company’s lack of quiet working areas?”
With the question clear for all to see, the group then spends 5 minutes to reflect on the question individually. They can jot down their thoughts and ideas on Post-Its.
Now ask the participants to find one or two other people to discuss their ideas and thoughts with. Ask the group to move around to find a partner so they can mix with new people.
Ask the pairs to spend 5 minutes discussing their shared ideas and thoughts.
Next, put the group into groups of two or three pairs to make groups of 4-6. Each group shouldn’t be larger than six as the chances of everyone being able to speak reduces.
Ask the group to discuss one interesting idea they’ve heard in previous rounds, and each group member shares one each.
The group then needs to pick their preferred solution to the problem. This doesn’t have to be voted on, just one that resonated most with the group.
Then ask for three actions that could be taken to implement this change.
Bring everyone back together as a group and ask open questions like “What is the one thing you discussed that stood out for you?” or “Is there something you now see differently following these discussions?”
By the end of the session, you’ll have multiple approaches to solve the problem, and the whole group will have contributed to the future solutions and improvements.
The Lightning Decision Jam is a great way to solve problems collaboratively and agree on one solution or experiment you want to try straight away. It encourages team decision making, but at the same time, the individual can get their ideas and feedback across. [1]
If, as a team, you have a particular area you want to improve upon, like the office environment, for example, this approach is perfect to incorporate in the problem solving steps.
The approach follows a simple loop.
Make a Note – Stick It on The Wall – Vote – Prioritize
Using sticky notes, the technique identifies major problems, encourages solutions, and opens the group up for discussion. It allows each team member to play an active role in identifying both problems and ways to solve them.
Mind mapping is a fantastic visual thinking tool that allows you to bring problems to life by building out the connections and visualizing the relationships that make up the problem.
You can use a mind map to quickly expand upon the problem and give yourself the full picture of the causes of the problem, as well as solutions [2] .
The goal of a mind map is to simplify the problem and link the causes and solutions to the problem.
To create a mind map, you must first create the central topic (level 1). In this case, that’s the problem.
Next, create the linked topics (level 2) that you place around and connect to the main central topic with a simple line.
If the central topic is “The client is always changing their mind at the last minute,” then you could have linked topics like:
Adding these linking topics allows you to start building out the main causes of the problem as you can begin to see the full picture of what you need to fix. Once you’re happy that you’ve covered the breadth of the problem and its issues, you can start to ideate on how you’re going to fix it with the problem solving steps.
Now, start adding subtopics (level 3) linking to each of the level 2 topics. This is where you can start to go big on solutions and ideas to help fix the problem.
For each of the linked topics (level 2), start to think about how you can prevent them, mitigate them, or improve them. As this is just ideas on paper, write down anything that comes to mind, even if you think the client will never agree to it!
The more you write down, the more ideas you’ll have until you find one or two that could solve the main problem.
Once you run out of ideas, take a step back and highlight your favorite solutions to take forward and implement.
The five why’s can sound a little controversial, and you shouldn’t try this without prepping the team beforehand.
Asking “why” is a great way to go deep into the root of the problem to make the individual or team really think about the cause. When a problem arises, we often have preconceived ideas about why this problem has occurred, which is usually based on our experiences or beliefs.
Start with describing the problem, and then the facilitator can ask “Why?” fives time or more until you get to the root of the problem. It’s tough at first to keep being asked why, but it’s also satisfying when you get to the root of the problem [3] .
As a facilitator, although the basic approach is to ask why, you need to be careful not to guide the participant down a single route.
To help with this, you can use a mind map with the problem at the center. Then ask a why question that will result in multiple secondary topics around the central problem. Having this visual representation of the problem helps you build out more useful why questions around it.
Once you get to the root of the problem, don’t forget to be clear in the actions to put a fix in place to resolve it.
Learn more about how to use the five why’s here .
To fix a problem, you must first be in a position where you fully understand it. There are many ways to misinterpret a problem, and the best way to understand them is through conversation with the team or individuals who are experiencing it.
Once you’re aligned, you can then begin to work on the solutions that will have the greatest impact through effective problem solving steps.
For the more significant or difficult problems to solve, it’s often advisable to break the solution up into smaller actions or improvements.
Trial these improvements in short iterations, and then continue the conversations to review and improve the solution. Implementing all of these steps will help you root out the problems and find useful solutions each time.
[1] | ^ | UX Planet: |
[2] | ^ | Focus: |
[3] | ^ | Expert Program Management: |
Explore the time flow system.
Posted on May 29, 2019
Constant disruption has become a hallmark of the modern workforce and organisations want problem solving skills to combat this. Employers need people who can respond to change – be that evolving technology, new competitors, different models for doing business, or any of the other transformations that have taken place in recent years.
In addition, problem solving techniques encompass many of the other top skills employers seek . For example, LinkedIn’s list of the most in-demand soft skills of 2019 includes creativity, collaboration and adaptability, all of which fall under the problem-solving umbrella.
Despite its importance, many employees misunderstand what the problem solving method really involves.
Effective problem solving doesn’t mean going away and coming up with an answer immediately. In fact, this isn’t good problem solving at all, because you’ll be running with the first solution that comes into your mind, which often isn’t the best.
Instead, you should look at problem solving more as a process with several steps involved that will help you reach the best outcome. Those steps are:
Let’s look at each step in a little more detail.
The first step to solving a problem is defining what the problem actually is – sounds simple, right? Well no. An effective problem solver will take the thoughts of everyone involved into account, but different people might have different ideas on what the root cause of the issue really is. It’s up to you to actively listen to everyone without bringing any of your own preconceived notions to the conversation. Learning to differentiate facts from opinion is an essential part of this process.
An effective problem solver will take the opinions of everyone involved into account
The same can be said of data. Depending on what the problem is, there will be varying amounts of information available that will help you work out what’s gone wrong. There should be at least some data involved in any problem, and it’s up to you to gather as much as possible and analyse it objectively.
Once you’ve identified what the real issue is, it’s time to think of solutions. Brainstorming as many solutions as possible will help you arrive at the best answer because you’ll be considering all potential options and scenarios. You should take everyone’s thoughts into account when you’re brainstorming these ideas, as well as all the insights you’ve gleaned from your data analysis. It also helps to seek input from others at this stage, as they may come up with solutions you haven’t thought of.
Depending on the type of problem, it can be useful to think of both short-term and long-term solutions, as some of your options may take a while to implement.
Each option will have pros and cons, and it’s important you list all of these, as well as how each solution could impact key stakeholders. Once you’ve narrowed down your options to three or four, it’s often a good idea to go to other employees for feedback just in case you’ve missed something. You should also work out how each option ties in with the broader goals of the business.
There may be a way to merge two options together in order to satisfy more people.
Only now should you choose which solution you’re going to go with. What you decide should be whatever solves the problem most effectively while also taking the interests of everyone involved into account. There may be a way to merge two options together in order to satisfy more people.
At this point you might be thinking it’s time to sit back and relax – problem solved, right? There are actually two more steps involved if you want your problem solving method to be truly effective. The first is to create an implementation plan. After all, if you don’t carry out your solution effectively, you’re not really solving the problem at all.
Create an implementation plan on how you will put your solution into practice. One problem solving technique that many use here is to introduce a testing and feedback phase just to make sure the option you’ve selected really is the most viable. You’ll also want to include any changes to your solution that may occur in your implementation plan, as well as how you’ll monitor compliance and success.
There’s one last step to consider as part of the problem solving methodology, and that’s communicating your solution . Without this crucial part of the process, how is anyone going to know what you’ve decided? Make sure you communicate your decision to all the people who might be impacted by it. Not everyone is going to be 100 per cent happy with it, so when you communicate you must give them context. Explain exactly why you’ve made that decision and how the pros mean it’s better than any of the other options you came up with.
Employers are increasingly seeking soft skills, but unfortunately, while you can show that you’ve got a degree in a subject, it’s much harder to prove you’ve got proficiency in things like problem solving skills. But this is changing thanks to Deakin’s micro-credentials. These are university-level micro-credentials that provide an authoritative and third-party assessment of your capabilities in a range of areas, including problem solving. Reach out today for more information .
Published: February 13, 2023
Interview Questions and Answers
Actionable advice from real experts:
Biron Clark
Former Recruiter
Contributor
Dr. Kyle Elliott
Career Coach
Hayley Jukes
Editor-in-Chief
Biron Clark , Former Recruiter
Kyle Elliott , Career Coach
Hayley Jukes , Editor
As a recruiter , I know employers like to hire people who can solve problems and work well under pressure.
A job rarely goes 100% according to plan, so hiring managers are more likely to hire you if you seem like you can handle unexpected challenges while staying calm and logical.
But how do they measure this?
Hiring managers will ask you interview questions about your problem-solving skills, and they might also look for examples of problem-solving on your resume and cover letter.
In this article, I’m going to share a list of problem-solving examples and sample interview answers to questions like, “Give an example of a time you used logic to solve a problem?” and “Describe a time when you had to solve a problem without managerial input. How did you handle it, and what was the result?”
Problem-solving is the ability to identify a problem, prioritize based on gravity and urgency, analyze the root cause, gather relevant information, develop and evaluate viable solutions, decide on the most effective and logical solution, and plan and execute implementation.
Problem-solving encompasses other skills that can be showcased in an interview response and your resume. Problem-solving skills examples include:
Problem-solving is essential in the workplace because it directly impacts productivity and efficiency. Whenever you encounter a problem, tackling it head-on prevents minor issues from escalating into bigger ones that could disrupt the entire workflow.
Beyond maintaining smooth operations, your ability to solve problems fosters innovation. It encourages you to think creatively, finding better ways to achieve goals, which keeps the business competitive and pushes the boundaries of what you can achieve.
Effective problem-solving also contributes to a healthier work environment; it reduces stress by providing clear strategies for overcoming obstacles and builds confidence within teams.
When you answer interview questions about problem-solving scenarios, or if you decide to demonstrate your problem-solving skills in a cover letter (which is a good idea any time the job description mentions problem-solving as a necessary skill), I recommend using the STAR method.
STAR stands for:
It’s a simple way of walking the listener or reader through the story in a way that will make sense to them.
Start by briefly describing the general situation and the task at hand. After this, describe the course of action you chose and why. Ideally, show that you evaluated all the information you could given the time you had, and made a decision based on logic and fact. Finally, describe the positive result you achieved.
Note: Our sample answers below are structured following the STAR formula. Be sure to check them out!
EXPERT ADVICE
Dr. Kyle Elliott , MPA, CHES Tech & Interview Career Coach caffeinatedkyle.com
Before answering any interview question, it’s important to understand why the interviewer is asking the question in the first place.
When it comes to questions about your complex problem-solving experiences, for example, the interviewer likely wants to know about your leadership acumen, collaboration abilities, and communication skills, not the problem itself.
Therefore, your answer should be focused on highlighting how you excelled in each of these areas, not diving into the weeds of the problem itself, which is a common mistake less-experienced interviewees often make.
As a recruiter, one of the top tips I can give you when responding to the prompt “Tell us about a problem you solved,” is to tailor your answer to the specific skills and qualifications outlined in the job description.
Once you’ve pinpointed the skills and key competencies the employer is seeking, craft your response to highlight experiences where you successfully utilized or developed those particular abilities.
For instance, if the job requires strong leadership skills, focus on a problem-solving scenario where you took charge and effectively guided a team toward resolution.
By aligning your answer with the desired skills outlined in the job description, you demonstrate your suitability for the role and show the employer that you understand their needs.
Amanda Augustine expands on this by saying:
“Showcase the specific skills you used to solve the problem. Did it require critical thinking, analytical abilities, or strong collaboration? Highlight the relevant skills the employer is seeking.”
Now, let’s look at some sample interview answers to, “Give me an example of a time you used logic to solve a problem,” or “Tell me about a time you solved a problem,” since you’re likely to hear different versions of this interview question in all sorts of industries.
The example interview responses are structured using the STAR method and are categorized into the top 5 key problem-solving skills recruiters look for in a candidate.
Situation: In my previous role as a data analyst , our team encountered a significant drop in website traffic.
Task: I was tasked with identifying the root cause of the decrease.
Action: I conducted a thorough analysis of website metrics, including traffic sources, user demographics, and page performance. Through my analysis, I discovered a technical issue with our website’s loading speed, causing users to bounce.
Result: By optimizing server response time, compressing images, and minimizing redirects, we saw a 20% increase in traffic within two weeks.
Situation: During a project deadline crunch, our team encountered a major technical issue that threatened to derail our progress.
Task: My task was to assess the situation and devise a solution quickly.
Action: I immediately convened a meeting with the team to brainstorm potential solutions. Instead of panicking, I encouraged everyone to think outside the box and consider unconventional approaches. We analyzed the problem from different angles and weighed the pros and cons of each solution.
Result: By devising a workaround solution, we were able to meet the project deadline, avoiding potential delays that could have cost the company $100,000 in penalties for missing contractual obligations.
Situation: As a project manager , I was faced with a dilemma when two key team members had conflicting opinions on the project direction.
Task: My task was to make a decisive choice that would align with the project goals and maintain team cohesion.
Action: I scheduled a meeting with both team members to understand their perspectives in detail. I listened actively, asked probing questions, and encouraged open dialogue. After carefully weighing the pros and cons of each approach, I made a decision that incorporated elements from both viewpoints.
Result: The decision I made not only resolved the immediate conflict but also led to a stronger sense of collaboration within the team. By valuing input from all team members and making a well-informed decision, we were able to achieve our project objectives efficiently.
Situation: During a cross-functional project, miscommunication between departments was causing delays and misunderstandings.
Task: My task was to improve communication channels and foster better teamwork among team members.
Action: I initiated regular cross-departmental meetings to ensure that everyone was on the same page regarding project goals and timelines. I also implemented a centralized communication platform where team members could share updates, ask questions, and collaborate more effectively.
Result: Streamlining workflows and improving communication channels led to a 30% reduction in project completion time, saving the company $25,000 in operational costs.
Situation: During a challenging sales quarter, I encountered numerous rejections and setbacks while trying to close a major client deal.
Task: My task was to persistently pursue the client and overcome obstacles to secure the deal.
Action: I maintained regular communication with the client, addressing their concerns and demonstrating the value proposition of our product. Despite facing multiple rejections, I remained persistent and resilient, adjusting my approach based on feedback and market dynamics.
Result: After months of perseverance, I successfully closed the deal with the client. By closing the major client deal, I exceeded quarterly sales targets by 25%, resulting in a revenue increase of $250,000 for the company.
Throughout your career, being able to showcase and effectively communicate your problem-solving skills gives you more leverage in achieving better jobs and earning more money .
So to improve your problem-solving skills, I recommend always analyzing a problem and situation before acting.
When discussing problem-solving with employers, you never want to sound like you rush or make impulsive decisions. They want to see fact-based or data-based decisions when you solve problems.
Don’t just say you’re good at solving problems. Show it with specifics. How much did you boost efficiency? Did you save the company money? Adding numbers can really make your achievements stand out.
To get better at solving problems, analyze the outcomes of past solutions you came up with. You can recognize what works and what doesn’t.
Think about how you can improve researching and analyzing a situation, how you can get better at communicating, and deciding on the right people in the organization to talk to and “pull in” to help you if needed, etc.
Finally, practice staying calm even in stressful situations. Take a few minutes to walk outside if needed. Step away from your phone and computer to clear your head. A work problem is rarely so urgent that you cannot take five minutes to think (with the possible exception of safety problems), and you’ll get better outcomes if you solve problems by acting logically instead of rushing to react in a panic.
You can use all of the ideas above to describe your problem-solving skills when asked interview questions about the topic. If you say that you do the things above, employers will be impressed when they assess your problem-solving ability.
About the Author
Biron Clark is a former executive recruiter who has worked individually with hundreds of job seekers, reviewed thousands of resumes and LinkedIn profiles, and recruited for top venture-backed startups and Fortune 500 companies. He has been advising job seekers since 2012 to think differently in their job search and land high-paying, competitive positions. Follow on Twitter and LinkedIn .
Read more articles by Biron Clark
About the Contributor
Kyle Elliott , career coach and mental health advocate, transforms his side hustle into a notable practice, aiding Silicon Valley professionals in maximizing potential. Follow Kyle on LinkedIn .
About the Editor
Hayley Jukes is the Editor-in-Chief at CareerSidekick with five years of experience creating engaging articles, books, and transcripts for diverse platforms and audiences.
Continue Reading
15 most common pharmacist interview questions and answers, 15 most common paralegal interview questions and answers, top 30+ funny interview questions and answers, 60 hardest interview questions and answers, 100+ best ice breaker questions to ask candidates, top 20 situational interview questions (& sample answers), 15 most common physical therapist interview questions and answers.
Great businesses don’t exist to simply grow and make money. Instead, they solve the world’s problems , from tiny issues to giant dilemmas. Problem-solving is essentially the main function of organizations. An effective organization will have systems and processes in place to reach their goals and solve problems. If a company has team members and leaders who have poor problem-solving skills, that means they’re ineffective at one of the core functions of a business.
What is the general process of problem-solving, 1. define the problem, 2. brainstorm possible solutions, 3. research several options.
After you’ve come up with several possible alternative solutions, pick two or three that seem the most promising using your analytical skills. Then you’ll need to buckle down and do some research to see which one to pursue. Conduct your research using primary and secondary resources.
In order to make the most objective decision:
When the right choice is made, and the solution is placed into the overall strategy, start developing an action plan . Lay out the “who,” “what,” “when,” “why,” and “how.” Visualize exactly what success looks like with this new plan. When working through the problem-solving process, write all the details down. This helps leaders construct action items and delegate them accordingly. Never leave this part of the process empty-handed. Your team needs a clear picture of expectations so they can properly implement the solution. And if everything works, you can use this problem-solving model in the future.
One of the best ways to discover the root cause of a problem is by utilizing the 5 Whys method. This strategy was developed by Sakichi Toyoda, founder of Toyota Industries. It’s as simple as it sounds. When a problem occurs, ask why it happened five times. In theory, the last answer should get to the heart of the issue.
When one engages in first principles thinking , they end up questioning what everyone just assumes to be true. It effectively removes those assumptions , breaking things down into their most basic elements that are probably true. It’s all about getting to that core foundation of truth and building out from there. Problem-solving skills should always include first principles thinking.
What to do when a problem feels too big to solve.
Tackling a problem that feels too big to solve requires a can-do, positive mindset. In order to improve your problem-solving, you’ll need to take remember these steps. Imagine what is possible instead of focusing on what seems impossible. As you do so, you’ll become skilled in solving all sorts of problems while also improving your decision-making.
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.
Any organization offering a product or service is in the business of solving problems.
Whether providing medical care to address health issues or quick convenience to those hungry for dinner, a business’s purpose is to satisfy customer needs .
In addition to solving customers’ problems, you’ll undoubtedly encounter challenges within your organization as it evolves to meet customer needs. You’re likely to experience growing pains in the form of missed targets, unattained goals, and team disagreements.
Yet, the ubiquity of problems doesn’t have to be discouraging; with the right frameworks and tools, you can build the skills to solve consumers' and your organization’s most challenging issues.
Here’s a primer on problem-solving in business, why it’s important, the skills you need, and how to build them.
Access your free e-book today.
Problem-solving is the process of systematically removing barriers that prevent you or others from reaching goals.
Your business removes obstacles in customers’ lives through its products or services, just as you can remove obstacles that keep your team from achieving business goals.
Design thinking , as described by Harvard Business School Dean Srikant Datar in the online course Design Thinking and Innovation , is a human-centered , solutions-based approach to problem-solving and innovation. Originally created for product design, design thinking’s use case has evolved . It’s now used to solve internal business problems, too.
The design thinking process has four stages :
Using this framework, you can generate innovative ideas that wouldn’t have surfaced otherwise.
Another, less structured approach to challenges is creative problem-solving , which employs a series of exercises to explore open-ended solutions and develop new perspectives. This is especially useful when a problem’s root cause has yet to be defined.
You can use creative problem-solving tools in design thinking’s “ideate” stage, which include:
It can be tempting to fall back on how problems have been solved before, especially if they worked well. However, if you’re striving for innovation, relying on existing systems can stunt your company’s growth.
Related: How to Be a More Creative Problem-Solver at Work: 8 Tips
While obstacles’ specifics vary between industries, strong problem-solving skills are crucial for leaders in any field.
Whether building a new product or dealing with internal issues, you’re bound to come up against challenges. Having frameworks and tools at your disposal when they arise can turn issues into opportunities.
As a leader, it’s rarely your responsibility to solve a problem single-handedly, so it’s crucial to know how to empower employees to work together to find the best solution.
Your job is to guide them through each step of the framework and set the parameters and prompts within which they can be creative. Then, you can develop a list of ideas together, test the best ones, and implement the chosen solution.
Related: 5 Design Thinking Skills for Business Professionals
1. problem framing.
One key skill for any leader is framing problems in a way that makes sense for their organization. Problem framing is defined in Design Thinking and Innovation as determining the scope, context, and perspective of the problem you’re trying to solve.
“Before you begin to generate solutions for your problem, you must always think hard about how you’re going to frame that problem,” Datar says in the course.
For instance, imagine you work for a company that sells children’s sneakers, and sales have plummeted. When framing the problem, consider:
While there’s no one right way to frame a problem, how you do can impact the solutions you generate. It’s imperative to accurately frame problems to align with organizational priorities and ensure your team generates useful ideas for your firm.
To solve a problem, you need to empathize with those impacted by it. Empathy is the ability to understand others’ emotions and experiences. While many believe empathy is a fixed trait, it’s a skill you can strengthen through practice.
When confronted with a problem, consider whom it impacts. Returning to the children’s sneaker example, think of who’s affected:
Empathy is required to get to the problem’s root and consider each group’s perspective. Assuming someone’s perspective often isn’t accurate, so the best way to get that information is by collecting user feedback.
For instance, if you asked customers who typically buy your children’s sneakers why they’ve stopped, they could say, “A new brand of children’s sneakers came onto the market that have soles with more traction. I want my child to be as safe as possible, so I bought those instead.”
When someone shares their feelings and experiences, you have an opportunity to empathize with them. This can yield solutions to their problem that directly address its root and shows you care. In this case, you may design a new line of children’s sneakers with extremely grippy soles for added safety, knowing that’s what your customers care most about.
Related: 3 Effective Methods for Assessing Customer Needs
Cognitive fixedness is a state of mind in which you examine situations through the lens of past experiences. This locks you into one mindset rather than allowing you to consider alternative possibilities.
For instance, your cognitive fixedness may make you think rubber is the only material for sneaker treads. What else could you use? Is there a grippier alternative you haven’t considered?
Problem-solving is all about overcoming cognitive fixedness. You not only need to foster this skill in yourself but among your team.
As a leader, it’s your job to create an environment conducive to problem-solving. In a psychologically safe environment, all team members feel comfortable bringing ideas to the table, which are likely influenced by their personal opinions and experiences.
If employees are penalized for “bad” ideas or chastised for questioning long-held procedures and systems, innovation has no place to take root.
By employing the design thinking framework and creative problem-solving exercises, you can foster a setting in which your team feels comfortable sharing ideas and new, innovative solutions can grow.
The most obvious answer to how to build your problem-solving skills is perhaps the most intimidating: You must practice.
Again and again, you’ll encounter challenges, use creative problem-solving tools and design thinking frameworks, and assess results to learn what to do differently next time.
While most of your practice will occur within your organization, you can learn in a lower-stakes setting by taking an online course, such as Design Thinking and Innovation . Datar guides you through each tool and framework, presenting real-world business examples to help you envision how you would approach the same types of problems in your organization.
Are you interested in uncovering innovative solutions for your organization’s business problems? Explore Design Thinking and Innovation —one of our online entrepreneurship and innovation courses —to learn how to leverage proven frameworks and tools to solve challenges. Not sure which course is right for you? Download our free flowchart .
As you were browsing something about your browser made us think you were a bot. There are a few reasons this might happen:
To regain access, please make sure that cookies and JavaScript are enabled before reloading the page.
“When I hear a person talking about political solutions, I know I am not listening to a serious person.” —George Carlin
The late, great standup comic had a point: Many of the political issues we argue most vehemently about — crime, the economy, the environment, education, national defense — aren’t problems that we can ever solve. There’s no finish line to reach. Instead, it’s more akin to pain management for an achy, middle-aged back: It’s always going to be an issue, but if you stay ahead of it, you can still enjoy a pretty good quality of life.
Homelessness is, was, and will forever be an emotionally gut-wrenching societal tragedy. When you’re a child, losing the safety and security of your home — or by extension, your parents — is probably your most instinctive phobia. Other than starving to death (and/or being devoured by monsters), you couldn’t imagine anything worse. When I was a little kid, homelessness was one of the first social problems I was aware of. It was terrifying.
Rush Limbaugh noted that the homelessness crisis comes and goes depending on who’s in office: When the GOP’s in charge, it’s a major issue; when Democrats take over, it sort of gets swept under the rug. That’s because these poor, downtrodden (and often mentally ill) street people serve a higher purpose for the mainstream media: They’re flesh-and-blood props to advance the liberal agenda.
Furthermore, the more dire you perceive their plight, the more sympathetic you’ll be to a Big Government solution.
“Homeless advocates aren’t [just] satisfied with comparing the homeless to the Virgin Mary,” Limbaugh wrote in his best-selling book, “The Way Things Ought to Be.” “They want to use them as vehicles in their effort to portray America as an uncaring country.”
Still, it’s always sad when people struggle. Props or not, every single man, woman, and child living on the streets is deserving of basic human dignity. Images of large, sprawling homeless camps are just heartbreaking. (Dangerous, too — especially for women and children.)
But the problem remains unresolved: There were homeless families then, there are homeless families now, and there will undoubtedly be homeless families in the future. Clearly, none of the prior solutions were effective. And since we’re all out of good ideas, I’d like to throw my idea into the mix: Give each homeless person a camel.
First of all, camels are probably good for companionship. Everyone needs a friend. (Plus, it’ll be a funny conversation opener on Hump Days.)
Secondly — and far more importantly — this way, the entire homeless problem would vanish overnight. Seriously: Just like that!
Because instead of being homeless, now they’re nomads.
Isn’t that nice? Simply by redefining words and meanings, we can solve the ongoing, never-ending, heartbreaking problem of homelessness.
(Hey, if we can redefine gender, we can certainly redefine nomads.)
This way, whenever we encounter a homeless person on the street, we no longer need to look away, averting our eyes in sadness and shame. Instead, we can point him out to our kids, using him as a positive example: “See that man, Timmy? That’s a nomad. They’re a noble breed, proud and true. Where he goes, nobody knows! Now let’s get some pie.”
Look, we’re well beyond the point of rational solutions. It’s time to try something new, bold, and (highly) experimental. So if you truly care about the homeless people, please write to your local congressman ASAP: Tell your representative to support camels for the homeless. Those poor people have suffered enough; give ‘em a camel, for crying out loud.
Besides, what’s the worst thing that could happen?
Even if the program’s a total failure, at least the homeless could eat the camel and get a good meal out of it.
Scott Pinsker is a Public Relations, Branding and Crisis Communications Expert in Tampa Bay, Florida. His novel, "The Second Coming: A Love Story," is available for purchase on Amazon.
Join the conversation as a vip member.
As South Africa faces numerous challenges in its agricultural sector, including water scarcity, soil degradation, and inefficient farming practices, the adoption of agricultural technology (agri-tech) presents promising solutions. Here are ten innovative ways agri-tech can help solve traditional farming problems in South Africa.
Precision agriculture utilizes GPS technology and sensors to monitor crop health and soil conditions in real time. By applying fertilizers and pesticides only where needed, farmers can reduce costs and environmental impact while increasing yields. This targeted approach is especially useful in the diverse climates of South Africa.
Drones equipped with cameras and sensors can provide farmers with detailed aerial imagery of their fields. This technology enables farmers to monitor crop health, identify pest infestations, and assess irrigation needs, allowing for timely interventions that can enhance productivity.
Agri-tech solutions, such as soil sensors and data analytics, can help farmers monitor soil moisture, pH, and nutrient levels. By understanding soil health, farmers can implement sustainable practices that improve soil fertility and reduce reliance on chemical fertilizers.
Given South Africa’s water scarcity, smart irrigation systems that use weather data and soil moisture sensors can optimize water usage. These systems ensure that crops receive the right amount of water at the right time, conserving resources and improving crop resilience.
Mobile applications can provide farmers with essential information on weather forecasts, market prices, and best practices. These apps can also facilitate access to financial services, enabling smallholder farmers to manage their operations more effectively.
Blockchain technology can enhance traceability and transparency in the agricultural supply chain. By recording every transaction on a decentralized ledger, farmers can ensure fair pricing, reduce fraud, and improve food safety, ultimately benefiting both producers and consumers.
Innovative biotechnological approaches can develop crop varieties resistant to pests, diseases, and climate stresses. By investing in genetically modified organisms (GMOs) and hybrid seeds, South African farmers can improve food security and adapt to changing environmental conditions.
Agri-tech solutions can support IPM strategies by utilizing data analytics to predict pest outbreaks and recommend preventive measures. This approach minimizes chemical use and promotes sustainable pest control, safeguarding both crops and the environment.
With limited arable land and water resources, vertical farming and hydroponic systems offer alternative methods for producing food. These technologies enable year-round crop production in urban areas, reducing transportation costs and providing fresh produce to local markets.
E-learning platforms can provide farmers with access to training programs on modern farming techniques, agri-tech tools, and sustainable practices. By enhancing farmers’ skills and knowledge, these platforms can empower them to adopt innovative solutions and improve their livelihoods.
The integration of agri-tech in South African agriculture offers a pathway to overcoming traditional farming challenges. By leveraging technology to enhance productivity, sustainability, and resource management, farmers can contribute to a more resilient agricultural sector. Embracing these innovations is essential for ensuring food security and economic growth in the face of an evolving climate and demographic pressures.
Your email address will not be published. Required fields are marked *
Save my name, email, and website in this browser for the next time I comment.
- advertisement -.
Sign in to your account
Username or Email Address
Remember Me
The .gov means it’s official. Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you're on a federal government site.
The site is secure. The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
FDA News Release
Today, the U.S. Food and Drug Administration approved a new indication for use for Wegovy (semaglutide) injection to reduce the risk of cardiovascular death, heart attack and stroke in adults with cardiovascular disease and either obesity or overweight. Wegovy should be used in addition to a reduced calorie diet and increased physical activity. Cardiovascular disease is a group of diseases of the heart and blood vessels.
“Wegovy is now the first weight loss medication to also be approved to help prevent life-threatening cardiovascular events in adults with cardiovascular disease and either obesity or overweight,” said John Sharretts, M.D., director of the Division of Diabetes, Lipid Disorders, and Obesity in the FDA’s Center for Drug Evaluation and Research. “This patient population has a higher risk of cardiovascular death, heart attack and stroke. Providing a treatment option that is proven to lower this cardiovascular risk is a major advance for public health.”
Obesity or overweight affect approximately 70% of American adults. Obesity and overweight are serious health issues that increase the risk for premature death and a variety of health problems, including heart attack and stroke.
Wegovy contains semaglutide, a glucagon-like peptide-1 (GLP-1) receptor agonist. Therefore, Wegovy should not be used in combination with other semaglutide-containing products or other GLP-1 receptor agonists.
Wegovy’s efficacy and safety for this new indication were studied in a multi-national, multi-center, placebo-controlled double-blind trial that randomly assigned over 17,600 participants to receive either Wegovy or placebo. Participants in both groups also received standard-of-care medical treatment (e.g., management of blood pressure and cholesterol) and healthy lifestyle counseling (including diet and physical activity). Wegovy significantly reduced the risk of major adverse cardiovascular events (cardiovascular death, heart attack and stroke), which occurred in 6.5% of participants who received Wegovy compared to 8% of participants who received placebo.
The prescribing information for Wegovy contains a boxed warning to inform health care professionals and patients about the risk of thyroid C-cell tumors. Because of this risk, Wegovy should not be used in patients with a personal or family history of medullary thyroid carcinoma or in patients with a rare condition called Multiple Endocrine Neoplasia syndrome type 2.
Wegovy should not be used in patients with a history of a severe allergic reaction to semaglutide or to any of the other ingredients. Patients should stop Wegovy immediately and seek medical help if a severe allergic reaction is suspected.
Wegovy also contains warnings for inflammation of the pancreas (pancreatitis), gallbladder problems (including gallstones), low blood sugar, acute kidney injury, hypersensitivity reactions, diabetic retinopathy (damage to the eye's retina), increased heart rate and suicidal behavior or thinking. Patients should discuss with their health care provider if they have symptoms of pancreatitis or gallstones. If Wegovy is used with insulin or with a medication that causes insulin secretion, patients should speak to their health care provider about the risk of low blood sugar. Healthcare professionals should monitor patients for kidney disease, diabetic retinopathy and depression or suicidal behaviors or thoughts.
The most common side effects of Wegovy include nausea, diarrhea, vomiting, constipation, abdominal (stomach) pain, headache, fatigue, dyspepsia (indigestion), dizziness, abdominal distension, eructation (belching), hypoglycemia (low blood sugar) in patients with diabetes, flatulence (gas buildup) and gastroesophageal reflux disease (heartburn).
Wegovy received Priority Review designation for this indication.
The FDA granted the approval to Novo Nordisk A/S.
Wegovy is also approved to reduce excess weight and maintain weight reduction long term in certain adults with obesity or overweight and certain children with obesity, for use in addition to a reduced calorie diet and increased physical activity.
The FDA, an agency within the U.S. Department of Health and Human Services, protects the public health by assuring the safety, effectiveness, and security of human and veterinary drugs, vaccines and other biological products for human use, and medical devices. The agency also is responsible for the safety and security of our nation’s food supply, cosmetics, dietary supplements, radiation-emitting electronic products, and for regulating tobacco products.
What's on #3: skilled people solve the world’s problems.
12 September 2024
In an increasingly uncertain world marked by conflicts and disparities, WorldSkills showcases how skills are a powerful tool for creating a more equitable global society. Today’s highlights bring home the essential role that skilled young people play in solving problems and unlocking new opportunities.
Yesterday we saw Competitors exchange final words of good luck with friends and family before they set to work on their Test Projects. On day two, workshops remain a hive of activity, and the Competition intensifies. Visitors to Eurexpo can enjoy watching skills in action and then try them out for themselves in over 50 Try-a-Skills.
WorldSkills Conference 2024 continues today with a packed agenda, focusing on how skills development can address global challenges. At 13:00 CEST, the stage will host the BeChangeMaker 2024 finale, as five teams of exciting young entrepreneurs pitch their ideas to tackle issues in their communities.
Conference highlights include:
Download the Conference app, Whova, to view the full schedule and RSVP for your favourite sessions or watch some of the sessions live .
Competitors are back in the workshops and showing the world their exceptional skills. Try and catch them in action at Eurexpo’s six sector villages. And if you are unable to get there in person, we are broadcasting every day of the Competition from 11 to 14 September. Tune in for over 20 hours of live event coverage throughout the Competition [https://worldskills2024.com/en/live-streaming/#competition]
The Village des Métiers, or Skills Village, at Place Bellecour continues to showcase eight skills families, drawing curious visitors. Meanwhile at the Rhône Prefecture, the Sports & Skills exhibition remains a popular attraction for hundreds of visitors.
COMMENTS
7. Solution evaluation. 1. Problem identification. The first stage of any problem solving process is to identify the problem (s) you need to solve. This often looks like using group discussions and activities to help a group surface and effectively articulate the challenges they're facing and wish to resolve.
In general, effective problem-solving strategies include the following steps: Define the problem. Come up with alternative solutions. Decide on a solution. Implement the solution. Problem-solving ...
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 ...
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. These steps support the involvement of interested parties, the use of factual information, comparison of expectations ...
Several mental processes are at work during problem-solving. Among them are: Perceptually recognizing the problem. Representing the problem in memory. Considering relevant information that applies to the problem. Identifying different aspects of the problem. Labeling and describing the problem.
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 ...
Problem-solving strategies can be enhanced with the application of creative techniques. You can use creativity to: Approach problems from different angles. Improve your problem-solving process. Spark creativity in your employees and peers. 6. Adaptability. Adaptability is the capacity to adjust to change. When a particular solution to an issue ...
One of the best ways to improve your problem-solving skills is to learn from experts. Consider enrolling in organizational training, shadowing a mentor, or working with a coach. 2. Practice. Practice using your new problem-solving skills by applying them to smaller problems you might encounter in your daily life.
Balance divergent and convergent thinking. Ask problems as questions. Defer or suspend judgement. Focus on "Yes, and…" rather than "No, but…". According to Carella, "Creative problem solving is the mental process used for generating innovative and imaginative ideas as a solution to a problem or a challenge.
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.
Structured problem solving can be used to address almost any complex challenge in business or public policy. (PDF-255 KB) 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 ...
Step 1 - Define the Problem. The definition of the problem is the first step in effective problem solving. This may appear to be a simple task, but it is actually quite difficult. This is because problems are frequently complex and multi-layered, making it easy to confuse symptoms with the underlying cause.
There's a 5-step process that you can follow that will allow you to solve your challenges more efficiently and effectively. In short, you need to move through these 5 steps: Defining a problem. Ideating on a solution. Committing to a course of action. Implementing your solution. And finally - analyzing the results.
A problem-solving strategy is a plan used to find a solution or overcome a challenge. 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 ...
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.
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.
Brainstorm options to solve the problem. Select an option. Create an implementation plan. Execute the plan and monitor the results. Evaluate the solution. Read more: Effective Problem Solving Steps in the Workplace. 2. Collaborative. This approach involves including multiple people in the problem-solving process.
Instead, you should look at problem solving more as a process with several steps involved that will help you reach the best outcome. Those steps are: Define the problem. List all the possible solutions. Evaluate the options. Select the best solution. Create an implementation plan. Communicate your solution.
The example interview responses are structured using the STAR method and are categorized into the top 5 key problem-solving skills recruiters look for in a candidate. 1. Analytical Thinking. Situation: In my previous role as a data analyst, our team encountered a significant drop in website traffic.
Teaches Scientific Thinking and Communication. Teaches Effective and Authentic Communication. Teaches Sales and Persuasion. Teaches Buying and Selling Real Estate. Teaches Designing Your Career. Teaches Leading Winning Teams. Teaches Purposeful Communication. On the Power of Personal Branding.
The key to cultivating excellent problem-solving skills is having a distinct process designed to produce solutions. While it may seem like problem-solving involves a complex strategy, it features several steps that are easy to follow. The following steps represent a general problem-solving process you can use when you need to find a solution. 1.
Problem-solving skills are skills that enable people to handle unexpected situations or difficult challenges at work. Organisations need people who can accurately assess problems and come up with effective solutions. In this article, we explain what problem-solving skills are, provide some examples of these skills and outline how to improve them.
4 Problem-Solving Skills All Leaders Need. 1. Problem Framing. One key skill for any leader is framing problems in a way that makes sense for their organization. Problem framing is defined in Design Thinking and Innovation as determining the scope, context, and perspective of the problem you're trying to solve.
Frameworks for Mathematical Problem Solving. One widely accepted and useful definition of a mathematical problem is that a problem exists when the procedure for solving the task is unknown to the solver, the number of solutions is uncertain, and the task requires critical thinking (Schoenfeld, Citation 2011).Word problems are a type of problem that are frequently found in classroom instruction.
The students in the video use the problem-solving procedure to analyze, contribute, and communicate problem-solving strategies for mathematics. The students first read the problem, then they describe how to solve it, and last they make the connections. In the first step, the students are understanding what they read by circling their questions and creating a "what I know" chart.
Simply by redefining words and meanings, we can solve the ongoing, never-ending, heartbreaking problem of homelessness. (Hey, if we can redefine gender, we can certainly redefine nomads.)
Here are ten innovative ways agri-tech can help solve traditional farming problems in South Africa. 1. Precision Agriculture. Precision agriculture utilizes GPS technology and sensors to monitor crop health and soil conditions in real time. By applying fertilizers and pesticides only where needed, farmers can reduce costs and environmental ...
A new series of reasoning models for solving hard problems. Available starting 9.12. ... For example, o1 can be used by healthcare researchers to annotate cell sequencing data, by physicists to generate complicated mathematical formulas needed for quantum optics, and by developers in all fields to build and execute multi-step workflows. ...
Español. Today, the U.S. Food and Drug Administration approved a new indication for use for Wegovy (semaglutide) injection to reduce the risk of cardiovascular death, heart attack and stroke in ...
Today's highlights bring home the essential role that skilled young people play in solving problems and unlocking new opportunities. WorldSkills Lyon 2024 continues. Yesterday we saw Competitors exchange final words of good luck with friends and family before they set to work on their Test Projects. On day two, workshops remain a hive of ...