“Do I really have no access to transport?”
“Can I really not afford to buy a car?”
The questions have to be asked, is the stated goal the real goal? Are the barriers actual barriers and what other barriers are there? In this example, the problem at first seems to be:
Goal | Barrier 1 | Barrier 2 |
Take the job | No transport | No money |
This is also a good opportunity to look at the relationships between the key elements of the problem . For example, in the 'Job-Transport-Money' problem, there are strong connections between all the elements.
By looking at all the relationships between the key elements, it appears that the problem is more about how to achieve any one of three things, i.e. job, transport or money, because solving one of these sub-problems will, in turn, solve the others.
This example shows how useful it is to have a representation of a problem.
Visual and verbal representations include:
Chain diagrams are powerful and simple ways of representing problems using a combination of diagrams and words. The elements of the problem are set out in words, usually placed in boxes, and positioned in different places on a sheet of paper, using lines to represent the relationship between them.
Chain Diagrams are the simplest type, where all the elements are presented in an ordered list, each element being connected only with the elements immediately before and after it. Chain diagrams usually represent a sequence of events needed for a solution. A simple example of a chain diagram illustrates the job-transport-money example as as follows:
TAKE JOB |
Flow charts allow for inclusion of branches, folds, loops, decision points and many other relationships between the elements. In practice, flow charts can be quite complicated and there are many conventions as to how they are drawn but, generally, simple diagrams are easier to understand and aid in 'seeing' the problem more readily.
Tree diagrams and their close relative, the Decision Tree , are ways of representing situations where there are a number of choices or different possible events to be considered. These types of diagram are particularly useful for considering all the possible consequences of solutions.
Remember that the aim of a visualisation is to make the problem clearer. Over-complicated diagrams will just confuse and make the problem harder to understand.
Listing the elements of a problem can also help to represent priorities, order and sequences in the problem. Goals can be listed in order of importance and barriers in order of difficulty. Separate lists could be made of related goals or barriers. The barriers could be listed in the order in which they need to be solved, or elements of the problem classified in a number of different ways. There are many possibilities, but the aim is to provide a clearer picture of the problem.
1. Get money |
A visual representation and a working definition together makes it far easier to describe a problem to others. Many problems will be far more complex than the example used here.
Continue to: Investigating Ideas and Possible Solutions
See also: Social Problem Solving Project Management Risk 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.
In a 2013 article published in the Journal of Cognitive Psychology , Ngar Yin Louis Lee (Chinese University of Hong Kong) and APS William James Fellow Philip N. Johnson-Laird (Princeton University) examined the ways people develop strategies to solve related problems. In a series of three experiments, the researchers asked participants to solve series of matchstick problems.
In matchstick problems, participants are presented with an array of joined squares. Each square in the array is comprised of separate pieces. Participants are asked to remove a certain number of pieces from the array while still maintaining a specific number of intact squares. Matchstick problems are considered to be fairly sophisticated, as there is generally more than one solution, several different tactics can be used to complete the task, and the types of tactics that are appropriate can change depending on the configuration of the array.
Louis Lee and Johnson-Laird began by examining what influences the tactics people use when they are first confronted with the matchstick problem. They found that initial problem-solving tactics were constrained by perceptual features of the array, with participants solving symmetrical problems and problems with salient solutions faster. Participants frequently used tactics that involved symmetry and salience even when other solutions that did not involve these features existed.
To examine how problem solving develops over time, the researchers had participants solve a series of matchstick problems while verbalizing their problem-solving thought process. The findings from this second experiment showed that people tend to go through two different stages when solving a series of problems.
People begin their problem-solving process in a generative manner during which they explore various tactics — some successful and some not. Then they use their experience to narrow down their choices of tactics, focusing on those that are the most successful. The point at which people begin to rely on this newfound tactical knowledge to create their strategic moves indicates a shift into a more evaluative stage of problem solving.
In the third and last experiment, participants completed a set of matchstick problems that could be solved using similar tactics and then solved several problems that required the use of novel tactics. The researchers found that participants often had trouble leaving their set of successful tactics behind and shifting to new strategies.
From the three studies, the researchers concluded that when people tackle a problem, their initial moves may be constrained by perceptual components of the problem. As they try out different tactics, they hone in and settle on the ones that are most efficient; however, this deduced knowledge can in turn come to constrain players’ generation of moves — something that can make it difficult to switch to new tactics when required.
These findings help expand our understanding of the role of reasoning and deduction in problem solving and of the processes involved in the shift from less to more effective problem-solving strategies.
Reference Louis Lee, N. Y., Johnson-Laird, P. N. (2013). Strategic changes in problem solving. Journal of Cognitive Psychology, 25 , 165–173. doi: 10.1080/20445911.2012.719021
good work for other researcher
APS regularly opens certain online articles for discussion on our website. Effective February 2021, you must be a logged-in APS member to post comments. By posting a comment, you agree to our Community Guidelines and the display of your profile information, including your name and affiliation. Any opinions, findings, conclusions, or recommendations present in article comments are those of the writers and do not necessarily reflect the views of APS or the article’s author. For more information, please see our Community Guidelines .
Please login with your APS account to comment.
Joel Anderson, a senior research fellow at both Australian Catholic University and La Trobe University, researches group processes, with a specific interest on prejudice, stigma, and stereotypes.
Ana Sofia Morais and Ralph Hertwig explain how experimental psychologists have painted too negative a picture of human rationality, and how their pessimism is rooted in a seemingly mundane detail: methodological choices.
In addition, an APS Rising Star receives the society’s Early Investigator Award.
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
AWSELBCORS | 5 minutes | This cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers. |
Cookie | Duration | Description |
---|---|---|
at-rand | never | AddThis sets this cookie to track page visits, sources of traffic and share counts. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
uvc | 1 year 27 days | Set by addthis.com to determine the usage of addthis.com service. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_gtag_UA_3507334_1 | 1 minute | Set by Google to distinguish users. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
loc | 1 year 27 days | AddThis sets this geolocation cookie to help understand the location of users who share the information. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
August 17, 2023 by MindManager Blog
Whether you run a business, manage a team, or work in an industry where change is the norm, it may feel like something is always going wrong. Thankfully, becoming proficient in the problem solving process can alleviate a great deal of the stress that business issues can create.
Understanding the right way to solve problems not only takes the guesswork out of how to deal with difficult, unexpected, or complex situations, it can lead to more effective long-term solutions.
In this article, we’ll walk you through the 5 steps of problem solving, and help you explore a few examples of problem solving scenarios where you can see the problem solving process in action before putting it to work.
When something isn’t working, it’s important to understand what’s at the root of the problem so you can fix it and prevent it from happening again. That’s why resolving difficult or complex issues works best when you apply proven business problem solving tools and techniques – from soft skills, to software.
The problem solving process typically includes:
While skills like active listening, collaboration, and leadership play an important role in problem solving, tools like visual mapping software make it easier to define and share problem solving objectives, play out various solutions, and even put the best fit to work.
Before you can take your first step toward solving a problem, you need to have a clear idea of what the issue is and the outcome you want to achieve by resolving it.
For example, if your company currently manufactures 50 widgets a day, but you’ve started processing orders for 75 widgets a day, you could simply say you have a production deficit.
However, the problem solving process will prove far more valuable if you define the start and end point by clarifying that production is running short by 25 widgets a day, and you need to increase daily production by 50%.
Once you know where you’re at and where you need to end up, these five steps will take you from Point A to Point B:
In practice, you might not hit a home-run with every solution you execute. But the beauty of a repeatable process like problem solving is that you can carry out steps 4 and 5 again by drawing from the brainstorm options you documented during step 2.
The best way to get a sense of how the problem solving process works before you try it for yourself is to work through some simple scenarios.
Here are three examples of how you can apply business problem solving techniques to common workplace challenges.
Building on our original manufacturing example, you determine that your company is consistently short producing 25 widgets a day and needs to increase daily production by 50%.
Since you’d like to gather data and input from both your manufacturing and sales order departments, you schedule a brainstorming session to discover the root cause of the shortage.
After examining four key production areas – machines, materials, methods, and management – you determine the cause of the problem: the material used to manufacture your widgets can only be fed into your equipment once the machinery warms up to a specific temperature for the day.
Your team comes up with three possible solutions.
After weighing the expense of the first two solutions, and conducting some online research, you decide that switching to a comparable but less expensive material that can be worked at a lower temperature is your best option.
You implement your plan, monitor your widget quality and output over the following week, and declare your solution a success when daily production increases by 100%.
Business training is booming and you’ve had to onboard new staff over the past month. Now you learn that several clients have expressed concern about the quality of your recent training sessions.
After speaking with both clients and staff, you discover there are actually two distinct factors contributing to your quality problem:
You could look for a new conference room or re-schedule upcoming training sessions until after your new equipment arrives. But your team collaboratively determines that the best way to mitigate both issues at once is by temporarily renting the high-quality sound and visual system they need.
Using benchmarks that include several weeks of feedback from session attendees, and random session spot-checks you conduct personally, you conclude the solution has worked.
You’ve invested heavily in product marketing, but still can’t meet your sales goals. Specifically, you missed your revenue target by 30% last year and would like to meet that same target this year.
After collecting and examining reams of information from your sales and accounting departments, you sit down with your marketing team to figure out what’s hindering your success in the marketplace.
Determining that your product isn’t competitively priced, you map out two viable solutions.
Since you’re in a hurry for results, you decide to immediately reduce the price of your product and market it accordingly.
When revenue figures for the following quarter show sales have declined even further – and marketing surveys show potential customers are doubting the quality of your product – you revert back to your original pricing, revisit your problem solving process, and implement the market analysis solution instead.
With the valuable information you gain, you finally arrive at just the right product price for your target market and sales begin to pick up. Although you miss your revenue target again this year, you meet it by the second quarter of the following year.
Kickstart your collaborative brainstorming sessions and try MindManager for free today !
MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster.
MindManager® helps individuals, teams, and enterprises bring greater clarity and structure to plans, projects, and processes. It provides visual productivity tools and mind mapping software to help take you and your organization to where you want to be.
Essentially every problem-solving heuristic in mathematics goes back to George Polya’s How to Solve It ; my approach is no exception. However, this cyclic description might help to keep the process cognitively present.
A few months ago, I produced a video describing this the three stages of the problem-solving cycle: Understand, Strategize, and Implement. That is, we must first understand the problem, then we think of strategies that might help solve the problem, and finally we implement those strategies and see where they lead us. During two decades of observing myself and others in the teaching and learning process, I’ve noticed that the most neglected phase is often the first one—understanding the problem.
The Three Stages Explained
I have produced videos explaining each one of these strategies individually using problems we have solved at the Chapel Hill Math Circle.
As we implement our strategies, we might not be able to solve the problem, but we might refine our understanding of the problem. As we refine our understanding of the problem, we can refine our strategy. As we refine our strategy and implement a new approach, we get closer to solving the problem, and so on. Of course, even after several iterations of this cycle spanning across hours, days, or even years, one may still not be able to solve a particular problem. That’s part of the enchanting beauty of mathematics.
I invite you to observe your own thinking—and that of your students—as you move along the problem-solving cycle!
[1] Problem-Solving Strategies in Mathematics , Posamentier and Krulik, 2015.
About the author: You may contact Hector Rosario at [email protected].
1 response to the three stages of the problem-solving cycle.
Pingback: When (Not) to Give a Hint | Chapel Hill Math Circle
on |
Problem solving is a critical skill for success in business – in fact it’s often what you are hired and paid to do. This article explains the five problem solving steps and provides strategies on how to execute each one.
Before we talk about the stages of problem solving, it’s important to have a definition of what it is. Let’s look at the two roots of problem solving — problems and solutions.
Problem – a state of desire for reaching a definite goal from a present condition [1] Solution – the management of a problem in a way that successfully meets the goals set for treating it
[1] Problem solving on Wikipedia
One important call-out is the importance of having a goal. As defined above, the solution may not completely solve problem, but it does meet the goals you establish for treating it–you may not be able to completely resolve the problem (end world hunger), but you can have a goal to help it (reduce the number of starving children by 10%).
With that understanding of problem solving, let’s talk about the steps that can get you there. The five problem solving steps are shown in the chart below:
However this chart as is a little misleading. Not all problems follow these steps linearly, especially for very challenging problems. Instead, you’ll likely move back and forth between the steps as you continue to work on the problem, as shown below:
Let’s explore of these steps in more detail, understanding what it is and the inputs and outputs of each phase.
aka What are you trying to solve? In addition to getting clear on what the problem is, defining the problem also establishes a goal for what you want to achieve.
Input: something is wrong or something could be improved. Output: a clear definition of the opportunity and a goal for fixing it.
aka What are some ways to solve the problem? The goal is to create a list of possible solutions to choose from. The harder the problem, the more solutions you may need.
Input: a goal; research of the problem and possible solutions; imagination. Output: pick-list of possible solutions that would achieve the stated goal.
aka What are you going to do? The ideal solution is effective (it will meet the goal), efficient (is affordable), and has the fewest side effects (limited consequences from implementation).
Input: pick-list of possible solutions; decision-making criteria. Output: decision of what solution you will implement.
aka What are you doing? The implementation of a solution requires planning and execution. It’s often iterative, where the focus should be on short implementation cycles with testing and feedback, not trying to get it “perfect” the first time.
Input: decision; planning; hard work. Output: resolution to the problem.
aka What did you do? To know you successfully solved the problem, it’s important to review what worked, what didn’t and what impact the solution had. It also helps you improve long-term problem solving skills and keeps you from re-inventing the wheel.
Input: resolutions; results of the implementation. Output: insights; case-studies; bullets on your resume.
Once you understand the five steps of problem solving, you can build your skill level in each one. Often we’re naturally good at a couple of the phases and not as naturally good at others. Some people are great at generating ideas but struggle implementing them. Other people have great execution skills but can’t make decisions on which solutions to use. Knowing the different problem solving steps allows you to work on your weak areas, or team-up with someone who’s strengths complement yours.
Want to improve your problem solving skills? Want to perfect the art of problem solving? Check out our training programs or try these 20 problem solving activities to improve creativity .
THIS FREE 129 SECOND QUIZ WILL SHOW YOU
what is your humor persona?
Humor is a skill that can be learned. And when used correctly, it is a superpower that can be your greatest asset for building a happier, healthier and more productive life. See for yourself...
you might also be interested in...
When I travel the country and talk with people about humor at work, they are often already aware of some […]
So you want to know how to be creative. While many assume that creativity (art, music, humor) is safe from […]
A tired audience is an impatient and distracted audience. To help ensure your presentation is actually heard, it’s important to […]
very helpful and informative training
Thank you for the information
YOU ARE AFOOL
I’m writing my 7th edition of Effective Security Management. I would like to use your circular graphic illustration in a new chapter on problem solving. You’re welcome to phone me at — with attribution.
Sure thing, shoot us an email at [email protected] .
i love your presentation. It’s very clear. I think I would use it in teaching my class problem solving procedures. Thank you
It is well defined steps, thank you.
these step can you email them to me so I can print them out these steps are very helpful
I like the content of this article, it is really helpful. I would like to know much on how PAID process (i.e. Problem statement, Analyze the problem, Identify likely causes, and Define the actual causes) works in Problem Solving.
very useful information on problem solving process.Thank you for the update.
Pingback: Let’s Look at Work Is Working with the Environment | #EnviroSociety
It makes sense that a business would want to have an effective problem solving strategy. Things could get bad if they can’t find solutions! I think one of the most important things about problem solving is communication.
Well in our school teacher teach us –
1) problem ldentification 2) structuring the problem 3) looking for possible solutions 4) lmplementation 5) monitoring or seeking feedback 6) decision making
Pleace write about it …
I teach Professional communication (Speech) and I find the 5 steps to problem solving as described here the best method. Your teacher actually uses 4 steps. The Feedback and decision making are follow up to the actual implementation and solving of the problem.
i know the steps of doing some guideline for problem solving
steps are very useful to solve my problem
The steps given are very effective. Thank you for the wonderful presentation of the cycle/steps/procedure and their connections.
I like the steps for problem solving
It is very useful for solving difficult problem i would reccomend it to a friend
this is very interesting because once u have learned you will always differentiate the right from the wrong.
I like the contents of the problem solving steps. informative.
Your email address will not be published. Required fields are marked *
I make an effort to appreciate the humor of everyday life....
This question helps us further the advancement of humor research to make it more equitable.
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 .
are processes through which a situation or issue may be analyzed and solutions implemented. Different methodologies may be optimized for specific applications. Employers seek people who can effectively identify and ask significant questions that clarify and lead to better solutions in a variety of work conditions. They require employees who can use multiple techniques to solve problems and can articulate the reason for choosing a course of action or solution. In this section you will find strategies and methods to help you solve complex problems. This includes steps for understanding a problem, brainstorming possible solutions, devising solutions, executing solutions, and evaluating the results. |
Problem solving process.
The process of problem-solving is an activity which has its ingredients as the specification of the program and the served dish is a correct program. This activity comprises of four steps : 1. Understanding the problem: To solve any problem it is very crucial to understand the problem first. What is the desired output of the code and how that output can be generated? The obvious and essential need to generate the output is an input. The input may be singular or it may be a set of inputs. A proper relationship between the input and output must be drawn in order to solve the problem efficiently. The input set should be complete and sufficient enough to draw the output. It means all the necessary inputs required to compute the output should be present at the time of computation. However, it should be kept in mind that the programmer should ensure that the minimum number of inputs should be there. Any irrelevant input only increases the size of and memory overhead of the program. Thus Identifying the minimum number of inputs required for output is a crucial element for understanding the problem.
2. Devising the plan: Once a problem has been understood, a proper action plan has to be devised to solve it. This is called devising the plan. This step usually involves computing the result from the given set of inputs. It uses the relationship drawn between inputs and outputs in the previous step. The complexity of this step depends upon the complexity of the problem at hand.
3. Executing the plan: Once the plan has been defined, it should follow the trajectory of action while ensuring the plan’s integrity at various checkpoints. If any inconsistency is found in between, the plan needs to be revised.
4. Evaluation: The final result so obtained must be evaluated and verified to see if the problem has been solved satisfactorily.
The methodology to solve a problem is defined as the most efficient solution to the problem. Although, there can be multiple ways to crack a nut, but a methodology is one where the nut is cracked in the shortest time and with minimum effort. Clearly, a sledgehammer can never be used to crack a nut. Under problem-solving methodology, we will see a step by step solution for a problem. These steps closely resemble the software life cycle . A software life cycle involves several stages in a program’s life cycle. These steps can be used by any tyro programmer to solve a problem in the most efficient way ever. The several steps of this cycle are as follows :
Step by step solution for a problem (Software Life Cycle) 1. Problem Definition/Specification: A computer program is basically a machine language solution to a real-life problem. Because programs are generally made to solve the pragmatic problems of the outside world. In order to solve the problem, it is very necessary to define the problem to get its proper understanding. For example, suppose we are asked to write a code for “ Compute the average of three numbers”. In this case, a proper definition of the problem will include questions like : “What exactly does average mean?” “How to calculate the average?”
Once, questions like these are raised, it helps to formulate the solution of the problem in a better way. Once a problem has been defined, the program’s specifications are then listed. Problem specifications describe what the program for the problem must do. It should definitely include :
what is the input set of the program
What is the desired output of the program and in what form the output is desired?
2. Problem Analysis (Breaking down the solution into simple steps): This step of solving the problem follows a modular approach to crack the nut. The problem is divided into subproblems so that designing a solution to these subproblems gets easier. The solutions to all these individual parts are then merged to get the final solution of the original problem. It is like divide and merge approach.
Modular Approach for Programming :
The process of breaking a large problem into subproblems and then treating these individual parts as different functions is called modular programming. Each function behaves independent of another and there is minimal inter-functional communication. There are two methods to implement modular programming :
3. Problem Designing: The design of a problem can be represented in either of the two forms :
The ways to execute any program are of three categories:
Identification of arithmetic and logical operations required for the solution : While writing the algorithm for a problem, the arithmetic and logical operations required for the solution are also usually identified. They help to write the code in an easier manner because the proper ordering of the arithmetic and logical symbols is necessary to determine the correct output. And when all this has been done in the algorithm writing step, it just makes the coding task a smoother one.
4. Coding: Once an algorithm is formed, it can’t be executed on the computer. Thus in this step, this algorithm has to be translated into the syntax of a particular programming language. This process is often termed as ‘coding’. Coding is one of the most important steps of the software life cycle. It is not only challenging to find a solution to a problem but to write optimized code for a solution is far more challenging.
Writing code for optimizing execution time and memory storage : A programmer writes code on his local computer. Now, suppose he writes a code which takes 5 hours to get executed. Now, this 5 hours of time is actually the idle time for the programmer. Not only it takes longer time, but it also uses the resources during that time. One of the most precious computing resources is memory. A large program is expected to utilize more memory. However, memory utilization is not a fault, but if a program is utilizing unnecessary time or memory, then it is a fault of coding. The optimized code can save both time and memory. For example, as has been discussed earlier, by using the minimum number of inputs to compute the output , one can save unnecessary memory utilization. All such techniques are very necessary to be deployed to write optimized code. The pragmatic world gives reverence not only to the solution of the problem but to the optimized solution. This art of writing the optimized code also called ‘competitive programming’.
5. Program Testing and Debugging: Program testing involves running each and every instruction of the code and check the validity of the output by a sample input. By testing a program one can also check if there’s an error in the program. If an error is detected, then program debugging is done. It is a process to locate the instruction which is causing an error in the program and then rectifying it. There are different types of error in a program : (i) Syntax Error Every programming language has its own set of rules and constructs which need to be followed to form a valid program in that particular language. If at any place in the entire code, this set of rule is violated, it results in a syntax error. Take an example in C Language
In the above program, the syntax error is in the first printf statement since the printf statement doesn’t end with a ‘;’. Now, until and unless this error is not rectified, the program will not get executed.
Once the error is rectified, one gets the desired output. Suppose the input is ‘good’ then the output is : Output:
(ii) Logical Error An error caused due to the implementation of a wrong logic in the program is called logical error. They are usually detected during the runtime. Take an example in C Language:
In the above code, the ‘for’ loop won’t get executed since n has been initialized with the value of 11 while ‘for’ loop can only print values smaller than or equal to 10. Such a code will result in incorrect output and thus errors like these are called logical errors. Once the error is rectified, one gets the desired output. Suppose n is initialised with the value ‘5’ then the output is : Output:
(iii) Runtime Error Any error which causes the unusual termination of the program is called runtime error. They are detected at the run time. Some common examples of runtime errors are : Example 1 :
If during the runtime, the user gives the input value for B as 0 then the program terminates abruptly resulting in a runtime error. The output thus appears is : Output:
Example 2 : If while executing a program, one attempts for opening an unexisting file, that is, a file which is not present in the hard disk, it also results in a runtime error.
6. Documentation : The program documentation involves :
7. Program Maintenance: Once a program has been formed, to ensure its longevity, maintenance is a must. The maintenance of a program has its own costs associated with it, which may also exceed the development cost of the program in some cases. The maintenance of a program involves the following :
There are codes which usually involve looping statements. Looping statements are statements in which instruction or a set of instructions is executed multiple times until a particular condition is satisfied. The while loop, for loop, do while loop, etc. form the basis of such looping structure. These statements are also called control structure because they determine or control the flow of instructions in a program. These looping structures are of two kinds :
In the above program, the ‘for’ loop gets executed only until the value of i is less than or equal to 10. As soon as the value of i becomes greater than 10, the while loop is terminated. Output:
In the above code, one can easily see that the value of n is not getting incremented. In such a case, the value of n will always remain 1 and hence the while loop will never get executed. Such loop is called an infinite loop. Output:
Similar reads.
JGI / Jamie Grill / Getty Images
From deciding what to eat for dinner to considering whether it's the right time to buy a house, problem-solving is a large part of our daily lives. Learn some of the problem-solving strategies that exist and how to use them in real life, along with ways to overcome obstacles that are making it harder to resolve the issues you face.
In cognitive psychology , the term 'problem-solving' refers to the mental process that people go through to discover, analyze, and solve problems.
A problem exists when there is a goal that we want to achieve but the process by which we will achieve it is not obvious to us. Put another way, there is something that we want to occur in our life, yet we are not immediately certain how to make it happen.
Maybe you want a better relationship with your spouse or another family member but you're not sure how to improve it. Or you want to start a business but are unsure what steps to take. Problem-solving helps you figure out how to achieve these desires.
The problem-solving process involves:
Before problem-solving can occur, it is important to first understand the exact nature of the problem itself. If your understanding of the issue is faulty, your attempts to resolve it will also be incorrect or flawed.
Several mental processes are at work during problem-solving. Among them are:
There are many ways to go about solving a problem. Some of these strategies might be used on their own, or you may decide to employ multiple approaches when working to figure out and fix a problem.
An algorithm is a step-by-step procedure that, by following certain "rules" produces a solution. Algorithms are commonly used in mathematics to solve division or multiplication problems. But they can be used in other fields as well.
In psychology, algorithms can be used to help identify individuals with a greater risk of mental health issues. For instance, research suggests that certain algorithms might help us recognize children with an elevated risk of suicide or self-harm.
One benefit of algorithms is that they guarantee an accurate answer. However, they aren't always the best approach to problem-solving, in part because detecting patterns can be incredibly time-consuming.
There are also concerns when machine learning is involved—also known as artificial intelligence (AI)—such as whether they can accurately predict human behaviors.
Heuristics are shortcut strategies that people can use to solve a problem at hand. These "rule of thumb" approaches allow you to simplify complex problems, reducing the total number of possible solutions to a more manageable set.
If you find yourself sitting in a traffic jam, for example, you may quickly consider other routes, taking one to get moving once again. When shopping for a new car, you might think back to a prior experience when negotiating got you a lower price, then employ the same tactics.
While heuristics may be helpful when facing smaller issues, major decisions shouldn't necessarily be made using a shortcut approach. Heuristics also don't guarantee an effective solution, such as when trying to drive around a traffic jam only to find yourself on an equally crowded route.
A trial-and-error approach to problem-solving involves trying a number of potential solutions to a particular issue, then ruling out those that do not work. If you're not sure whether to buy a shirt in blue or green, for instance, you may try on each before deciding which one to purchase.
This can be a good strategy to use if you have a limited number of solutions available. But if there are many different choices available, narrowing down the possible options using another problem-solving technique can be helpful before attempting trial and error.
In some cases, the solution to a problem can appear as a sudden insight. You are facing an issue in a relationship or your career when, out of nowhere, the solution appears in your mind and you know exactly what to do.
Insight can occur when the problem in front of you is similar to an issue that you've dealt with in the past. Although, you may not recognize what is occurring since the underlying mental processes that lead to insight often happen outside of conscious awareness .
Research indicates that insight is most likely to occur during times when you are alone—such as when going on a walk by yourself, when you're in the shower, or when lying in bed after waking up.
If you're facing a problem, you can implement one or more of these strategies to find a potential solution. Here's how to use them in real life:
Problem-solving is not a flawless process as there are a number of obstacles that can interfere with our ability to solve a problem quickly and efficiently. These obstacles include:
In the end, if your goal is to become a better problem-solver, it's helpful to remember that this is a process. Thus, if you want to improve your problem-solving skills, following these steps can help lead you to your solution:
You can find a way to solve your problems as long as you keep working toward this goal—even if the best solution is simply to let go because no other good solution exists.
Sarathy V. Real world problem-solving . Front Hum Neurosci . 2018;12:261. doi:10.3389/fnhum.2018.00261
Dunbar K. Problem solving . A Companion to Cognitive Science . 2017. doi:10.1002/9781405164535.ch20
Stewart SL, Celebre A, Hirdes JP, Poss JW. Risk of suicide and self-harm in kids: The development of an algorithm to identify high-risk individuals within the children's mental health system . Child Psychiat Human Develop . 2020;51:913-924. doi:10.1007/s10578-020-00968-9
Rosenbusch H, Soldner F, Evans AM, Zeelenberg M. Supervised machine learning methods in psychology: A practical introduction with annotated R code . Soc Personal Psychol Compass . 2021;15(2):e12579. doi:10.1111/spc3.12579
Mishra S. Decision-making under risk: Integrating perspectives from biology, economics, and psychology . Personal Soc Psychol Rev . 2014;18(3):280-307. doi:10.1177/1088868314530517
Csikszentmihalyi M, Sawyer K. Creative insight: The social dimension of a solitary moment . In: The Systems Model of Creativity . 2015:73-98. doi:10.1007/978-94-017-9085-7_7
Chrysikou EG, Motyka K, Nigro C, Yang SI, Thompson-Schill SL. Functional fixedness in creative thinking tasks depends on stimulus modality . Psychol Aesthet Creat Arts . 2016;10(4):425‐435. doi:10.1037/aca0000050
Huang F, Tang S, Hu Z. Unconditional perseveration of the short-term mental set in chunk decomposition . Front Psychol . 2018;9:2568. doi:10.3389/fpsyg.2018.02568
National Alliance on Mental Illness. Warning signs and symptoms .
Mayer RE. Thinking, problem solving, cognition, 2nd ed .
Schooler JW, Ohlsson S, Brooks K. Thoughts beyond words: When language overshadows insight. J Experiment Psychol: General . 1993;122:166-183. doi:10.1037/0096-3445.2.166
By Kendra Cherry, MSEd Kendra Cherry, MS, is a psychosocial rehabilitation specialist, psychology educator, and author of the "Everything Psychology Book."
When it comes to solving problems, getting ideas is the easy part.
But businesses often forget the other four stages of the problem-solving process that will allow them to find the best solution.
Instead of jumping straight to idea generation, your problem-solving framework should look like this:
See how idea generation doesn’t appear until stage 3?!
In this extensive resource, we provide techniques, methodologies and tools to guide you through every stage of the problem-solving process.
Once you’ve finished reading, you’ll possess an extensive problem-solving arsenal that will enable you to overcome your biggest workplace challenges.
Before we dive into more comprehensive methodologies for solving problems, there are a few basic techniques you should know.
The following techniques will set you up for a successful problem-solving session with your team, allowing you to take on your biggest challenges with clarity and confidence.
When a problem or challenge arises, it’s normal to act too quickly or rely on solutions that have worked well in the past. This is known as entrenched thinking.
But acting impulsively, without prior consideration or planning, can cause you to misunderstand the issue and overlook possible solutions to the problem.
Therefore, the first thing you should always do when you encounter a problem is: breathe in and out.
Take a step back and make a clear plan of action before you act. This will help you to take rational steps towards solving a problem.
Another common mistake people make when attempting to solve a problem is taking action before fully understanding the problem.
Before committing to a theory, ask enough questions to unearth the true root of the issue.
Later in this article, we cover The 5 Why’s problem-solving methodology which you can use to easily identify the root of your problem. Give this a go at your next meeting and see how your initial understanding of a problem can often be wrong.
A common problem-solving issue is that of myopia—a narrow-minded view or perception of the problem. Myopia can occur when you’re too involved with the problem or your team isn’t diverse enough.
To give yourself the best chance of resolving a problem, gain insight from a wide range of sources. Collaborate with key stakeholders, customers and on-the-ground employees to learn how the problem affects them and whether they have found workarounds or solutions.
To paint the broadest picture, don’t limit your problem-solving team to a specific archetype. Try to include everyone, from the chief executive to the office janitor.
If you’re working with a small team, try the Flip It! problem-solving methodology to view the issue from a fresh angle.
The environment in which your host your brainstorming sessions should maximise creativity . When your team members trust each other and feel relaxed, they’re more likely to come up with innovative ideas and solutions to a problem.
Here are a few ways to get your employees’ creative juices flowing:
World Café is a problem-solving method that creates a casual environment conducive to creative thinking.
Keep reading to learn more about how World Café can help your team solve complex organisational problems.
Because problem-solving is a creative process, it can be hard to keep it on track. As more ideas get banded around, conflicts can arise that derail the session.
That’s why problem-solving methodologies are so helpful. They offer you proven problem-solving frameworks to guide your group sessions and keep them on track.
The Six Thinking Hats problem-solving method is a popular technique that guides the process and helps your team analyse a problem from all angles.
We’re going to take a look at our favourite problem-solving methodologies in the next section of this article, XY Tried and tested problem-solving methodologies.
Sometimes, solving a different problem can help you uncover solutions to another problem!
By stripping back a complex issue and framing it as a simplified analogy , you approach a problem from a different angle, enabling you to come up with alternative ideas.
After solving practice problems, your team might be more aptly equipped to solve real-world issues.
However, coming up with an analogy that reflects your issue can be difficult, so don’t worry if this technique doesn’t work for you.
The Speed Boat diagram is a visual tool that helps your employees view existing challenges as anchors holding back a boat which represents your end goals. By assigning a “weight” to each anchor, your team can prioritise which issues to tackle first.
Constraints make a big problem more approachable.
Before you tackle a problem, establish clear boundaries and codes of conduct for the session. This allows your team to focus on the current issue without becoming distracted or veering off on a tangent.
In an article published in the Harvard Business Review, authors Oguz A. Acar, Murat Tarakci, and Daan van Knippenberg wrote, “Constraints … provide focus and a creative challenge that motivates people to search for and connect information from different sources to generate novel ideas for new products, services, or business processes.” (Why Constraints Are Good for Innovation, 2019)
Lightning Decision Jam is a prime example of how constraints can assist the creative process. Here, your team are given strict time constraints and isn’t permitted to discuss ideas until the end.
Humans are creatures of habit.
We defer to strategies that have produced positive results in the past. This is typically beneficial because recalling our previous successes means we don’t need to constantly re-learn similar tasks.
But when it comes to problem-solving, this way of thinking can trip us up. We become fixated on a solution that worked in the past, but when this fails we’re dismayed and left wondering what to do next.
To resolve problems effectively, your employees need to escape the precincts of their imaginations. This helps to eliminate functional fixedness—the belief that an item serves only its predefined function.
Alternative Application is an icebreaker game that encourages employees to think outside the box by coming up with different uses for everyday objects. Try this at your next meeting or team-building event and watch your team tap into their creativity.
Having a diverse group of employees at your brainstorming sessions is a good idea, but there’s one problem: the extroverted members of your team will be more vocal than the introverts.
To ensure you’re gaining insight from every member of your team, you need to give your quieter employees equal opportunities to contribute by eliminating personality biases.
Read more: What icebreaker games and questions work best for introverts?
The obvious solution, then, is to “silence” the louder participants (it’s not as sinister as it sounds, promise)—all you have to do is ban your team from debating suggestions during the ideation process.
The Lightning Decision Jam methodology gives your employees equal opportunities to contribute because much of the problem-solving process is carried out in silence.
Have you ever noticed how the best ideas seem to come when you’re not actively working on a problem? You may have spent hours slumped over your desk hashing out a solution, only for the “eureka!” moment to come when you’re walking your dog or taking a shower.
In James Webb Young’s book, A Technique for Producing Ideas , phase three of the process is “stepping away from the problem.” Young proclaims that after putting in the hard work, the information needs to ferment in the mind before any plausible ideas come to you.
So next time you’re in a meeting with your team trying to solve a problem, don’t panic if you don’t uncover groundbreaking ideas there and then. Allow everybody to mull over what they’ve learned, then reconvene at a later date.
The Creativity Dice methodology is a quick-fire brainstorming game that allows your team to incubate ideas while concentrating on another.
The way your team delivers feedback at the end of a successful brainstorming session is critical. Left unsupervised, excessive feedback can undo all of your hard work.
Therefore, it’s wise to put a cap on the amount of feedback your team can provide. One great way of doing this is by using the One Breath Feedback technique.
By limiting your employees to one breath, they’re taught to be concise with their final comments.
Problem-solving methodologies keep your brainstorming session on track and encourage your team to consider all angles of the issue.
Countless methods have wiggled their way into the world of business, each one with a unique strategy and end goal.
Here are 12 of our favourite problem-solving methodologies that will help you find the best-fit solution to your troubles.
Six Thinking Hats is a methodical problem-solving framework that helps your group consider all possible problems, causes, solutions and repercussions by assigning a different coloured hat to each stage of the problem-solving process.
The roles of each hat are as follows:
For Six Thinking Hats to work effectively, ensure your team acts within the confines of each role.
While wearing The Yellow Hat, for example, your team should only discuss the positives . Any negative implications should be left for the Black or Grey hat.
Note: Feel free to alter the hat colours to align with your cultural context.
Lightning Decision Jam is a nine-stage problem-solving process designed to uncover a variety of perspectives while keeping the session on track.
The process starts by defining a general topic like the internal design process, interdepartmental communication, the sales funnel, etc.
Then, armed with pens and post-it notes, your team will work through the nine stages in the following order:
The philosophy behind LDJ is that of constraint. By limiting discussion, employees can focus on compiling ideas and coming to democratic decisions that benefit the company without being distracted or going off on a tangent.
Root Cause Analysis (RCA) is the process of unearthing a problem and finding the underlying cause. To help you through this process, you can use The 5 Why’s methodology.
The idea is to ask why you’re experiencing a problem, reframe the problem based on the answer, and then ask “ why?” again. If you do this five times , you should come pretty close to the root of your original challenge.
While this might not be a comprehensive end-to-end methodology, it certainly helps you to pin down your core challenges.
If you’ve had enough of uninspiring corporate boardrooms, World Café is the solution.
This problem-solving strategy facilitates casual conversations around given topics, enabling players to speak more openly about their grievances without the pressure of a large group.
Here’s how to do it:
World Café is a useful way of uncovering hidden causes and pitfalls by having multiple simultaneous conversations about a given topic.
Discovery and Actions Dialogues are a collaborative method for employees to share and adopt personal behaviours in response to a problem.
This crowdsourcing approach provides insight into how a problem affects individuals throughout your company and whether some are better equipped than others.
A DAD session is guided by a facilitator who asks seven open-ended questions in succession. Each person is given equal time to participate while a recorder takes down notes and valuable insights.
This is a particularly effective method for uncovering preexisting ideas, behaviours and solutions from the people who face problems daily.
The Design Sprint 2.0 model by Jake Knapp helps your team to focus on finding, developing measuring a solution within four days . Because theorising is all well and good, but sometimes you can learn more by getting an idea off the ground and observing how it plays out in the real world.
Here’s the basic problem-solving framework:
This technique is great for testing the viability of new products or expanding and fixing the features of an existing product.
Open Space Technology is a method for large groups to create a problem-solving agenda around a central theme. It works best when your group is comprised of subject-matter experts and experienced individuals with a sufficient stake in the problem.
Open Space Technology works like this:
This methodology grants autonomy to your team and encourages them to take ownership of the problem-solving process.
While not an end-to-end problem-solving methodology, the Round-Robin Brainstorming Technique is an effective way of squeezing every last ounce of creativity from your ideation sessions.
Here’s how it works:
Once you’ve compiled a long list of ideas, it’s up to you how you move forward. You could, for example, borrow techniques from other methodologies, such as the “vote on solutions” phase of the Lightning Decision Jam.
Failure Modes and Effects Analysis is a method for preventing and mitigating problems within your business processes.
This technique starts by examining the process in question and asking, “What could go wrong?” From here, your team starts to brainstorm a list of potential failures.
Then, going through the list one by one, ask your participants, “Why would this failure happen?”
Once you’ve answered this question for each list item, ask yourselves, “What would the consequences be of this failure?”
This proactive method focuses on prevention rather than treatment. Instead of waiting for a problem to occur and reacting, you’re actively searching for future shortcomings.
The Flip It! Methodology teaches your team to view their concerns in a different light and frame them instead as catalysts for positive change.
The game works like this:
This brainstorming approach teaches your employees the danger of engrained thinking and helps them to reframe their fears as opportunities.
The Creativity Dice teaches your team to incubate ideas as they focus on different aspects of a problem. As we mentioned earlier in the article, giving ideas time to mature can be a highly effective problem-solving strategy. Here’s how the game works:
Choose a topic to focus on, It can be as specific or open-ended as you like. Write this down as a word or sentence. Roll the die, start a timer of three minutes and start writing down ideas within the confines of what that number resembles. The roles of each number are as follows:
Once you’ve finished the activity, review your findings and decide what you want to take with you.
The SWOT Analysis is a long-standing method for analysing the current state of your business and considering how this affects the desired end state.
The basic idea is this:
The SWOT Analysis is an intuitive method for understanding which parts of your business could be affecting your long-term goals.
When learning to cover every aspect of a story, journalists are taught to ask themselves six essential questions:
Now, this approach has been adopted by organisations to help understand every angle of a problem. All you need is a clear focus question, then you can start working through the six questions with your team until you have a 360-degree view of what has, can and needs to be done.
Gamestorming is a one-stop creative-thinking framework that uses various games to help your team come up with innovative ideas.
Originally published as a book 10 years ago, Gamestorming contained a selection of creative games used by Silicon Valley’s top-performing businesses to develop groundbreaking products and services.
This collection of resources, plucked from the minds of founders and CEOs like Jeff Bezos and Steve Jobs, allows you to tap into the potentially genius ideas lying dormant in the minds of your employees.
The Four-Step Sketch is a visual brainstorming that provides an alternative to traditional discussion-based ideation techniques .
This methodology requires prior discussion to clarify the purpose of the activity. Imagine you’re on a startup retreat , for example, and your team is taking part in a design sprint or hackathon.
Once you’ve brainstormed a list of ideas with your team, participants can look at the suggestions and take down any relevant notes. They then take these notes and turn them into rough sketches that resemble the idea.
Then, as a warm-up, give each participant eight minutes to produce eight alternative sketches (eight minutes per sketch) of the idea. These ideas are not to be shared with the group.
Finally, participants create new sketches based on their favourite ideas and share them with the group. The group can then vote on the ideas they think offer the best solution.
15% Solutions is a problem-solving strategy for motivating and inspiring your employees. By encouraging your team to gain small victories, you pave the way for bigger changes.
First, ask your participants to think about things they can personally do within the confines of their role.
Then, arrange your team into small groups of three to four and give them time to share their ideas and consult with each other.
This simple problem-solving process removes negativity and powerlessness and teaches your team to take responsibility for change.
Problem-solving tools support your meeting with easy-to-use graphs, visualisations and techniques.
By implementing a problem-solving tool, you break the cycle of mundane verbal discussion, enabling you to maintain engagement throughout the session.
The Fishbone Diagram (otherwise known as the Ishikawa Diagram or Cause and Effect Diagram), is a tool for identifying the leading causes of a problem. You can then consolidate these causes into a comprehensive “Problem Statement.”
The term “Fishbone Diagram” is derived from the diagram’s structure. The problem itself forms the tail, possible causes radiate from the sides to form the fish skeleton while the final “Problem Statement” appears as the “head” of the fish.
Example: A fast-food chain is investigating the declining quality of their food. As the team brainstorms potential causes, they come up with reasons like “poorly trained personnel”, “lack of quality control”, and “incorrect quantity of spices.” Together with other causes, the group summarises that these problems lead to “bad burgers.” They write this as the Problem Statement and set about eliminating the main contributing factors.
A Problem Tree is a useful tool for assessing the importance or relevance of challenges concerning the core topic. If you’re launching a new product, for example, gather your team and brainstorm the current issues, roadblocks and bottlenecks that are hindering the process.
Then, work together to decide which of these are most pressing. Place the most relevant issues closer to the core topic and less relevant issues farther away.
The Squid Diagram is an easy-to-use tool that charts the progress of ideas and business developments as they unfold. Your SQUID Diagram can remain on a wall for your team to add to over time.
The Speed Boat Diagram is a visual metaphor used to help your team identify and solve problems in the way of your goals.
Here’s how it works:
This is an easy-to-use tool that sparks creative solutions. If you like, your team can assign a “weight” to each anchor which determines the impact each problem has on the end goal.
LEGO is an excellent creative-thinking and problem-solving tool used regularly by event facilitators to help teams overcome challenges.
In our article 5 and 10-minute Team-Building Activities , we introduce Sneak a Peek —a collaborative team-building game that develops communication and leadership skills.
Teams aren’t always aligned when it comes to their understanding of a problem. While the problem remains the same for everyone, they might have differing opinions as to how it occurred at the implications it had.
Asking “ What? So What? Now What?” Helps you to understand different perspectives around a problem.
It goes like this:
This approach helps your team understand how problems affect individuals in different ways and uncovers a variety of ways to overcome them.
Gathering ideas is easy—but selecting the best ones? That’s a different story.
If you’ve got a bunch of ideas, try the Now-How-Wow Matrix to help you identify which ones you should implement now and which ones should wait until later.
Simply draw a two-axis graph with “implementation difficulty” on the Y axis and “idea originality” on the X axis. Divide this graph into quadrants and write “Now!” in the bottom left panel, “Wow!” in the bottom right panel, and “How?” in the top right panel. You can leave the top left panel blank.
Then, take your ideas and plot them on the graph depending on their implementation difficulty and level of originality.
By the end, you’ll have a clearer picture of which ideas to ignore, which ones to implement now, and which ones to add to the pipeline for the future.
The Impact-Effort Matrix is a variation of the Now-How-Wow Matrix where the Y axis is marked “Impact” and the X axis is marked “Effort.”
Then, divide the graph into quadrants and plot your ideas.
The Impact-Effort Matrix is a simple way for your team to weigh the benefits of an idea against the amount of investment required.
Once you’ve gathered a substantial list of ideas from your employees, you need to sort the good from the bad.
Dot voting is a simple tool used by problem-solving facilitators as a fast and effective way for large groups to vote on their favourite ideas . You’ll have seen this method used in problem-solving methods like Flip It! and Lightning Decision Jam .
This provides an easy-to-use visual representation of the best and worst ideas put forward by your team.
While working from home or at the office, your team is often too caught up in daily tasks to take on complex problems.
By escaping the office and uniting at an offsite location, you can craft a purposeful agenda of team-building activities and problem-solving sessions. This special time away from the office can prove invaluable when it comes to keeping your business on track.
If you have problems that need fixing (who doesn’t?), reach out to Surf Office and let us put together a fully-customised offsite retreat for you.
How to plan your first company retreat
Are you organising a company retreat and want to make sure you have all the costs under the control?
Get a copy of our free Budget Calculator spreadsheet.
Organize your next company retreat with surf office, 💌 join 18,000+ managers receiving insights on building company culture that people love., stay in touch, work with us.
Sometimes when you’re faced with a complex problem, it’s best to pause and take a step back. A break from…
Sometimes when you’re faced with a complex problem, it’s best to pause and take a step back. A break from routine will help you think creatively and objectively. Doing too much at the same time increases the chances of burnout.
Solving problems is easier when you align your thoughts with your actions. If you’re in multiple places at once mentally, you’re more likely to get overwhelmed under pressure. So, a problem-solving process follows specific steps to make it approachable and straightforward. This includes breaking down complex problems, understanding what you want to achieve, and allocating responsibilities to different people to ease some of the pressure.
The problem-solving process will help you measure your progress against factors like budget, timelines and deliverables. The point is to get the key stakeholders on the same page about the ‘what’, ‘why’ and ‘how’ of the process. ( Xanax ) Let’s discuss the five-step problem-solving process that you can adopt.
Problems at a workplace need not necessarily be situations that have a negative impact, such as a product failure or a change in government policy. Making a decision to alter the way your team works may also be a problem. Launching new products, technological upgrades, customer feedback collection exercises—all of these are also “problems” that need to be “solved”.
Here are the steps of a problem-solving process:
The first step in the process is often overlooked. To define the problem is to understand what it is that you’re solving for. This is also where you outline and write down your purpose—what you want to achieve and why. Making sure you know what the problem is can make it easier to follow up with the remaining steps. This will also help you identify which part of the problem needs more attention than others.
Analyze why the problem occurred and go deeper to understand the existing situation. If it’s a product that has malfunctioned, assess factors like raw material, assembly line, and people involved to identify the problem areas. This will help you figure out if the problem will persist or recur. You can measure the solution against existing factors to assess its future viability.
Once you’ve figured out what the problem is and why it occurred, you can move on to generating multiple options as solutions. You can combine your existing knowledge with research and data to come up with viable and effective solutions. Thinking objectively and getting inputs from those involved in the process will broaden your perspective of the problem. You’ll be able to come up with better options if you’re open to ideas other than your own.
Implementation will depend on the type of data at hand and other variables. Consider the big picture when you’re selecting the best option. Look at factors like how the solution will impact your budget, how soon you can implement it, and whether it can withstand setbacks or failures. If you need to make any tweaks or upgrades, make them happen in this stage.
The problem-solving process doesn’t end at implementation. It requires constant monitoring to watch out for recurrences and relapses. It’s possible that something doesn’t work out as expected on implementation. To ensure the process functions smoothly, you can make changes as soon as you catch a miscalculation. Always stay on top of things by monitoring how far you’ve come and how much farther you have to go.
You can learn to solve any problem—big or small—with experience and patience. Adopt an impartial and analytical approach that has room for multiple perspectives. In the workplace, you’re often faced with situations like an unexpected system failure or a key employee quitting in the middle of a crucial project.
Problem-solving skills will help you face these situations head-on. Harappa Education’s Structuring Problems course will show you how to classify and categorize problems to discover effective solutions. Equipping yourself with the right knowledge will help you navigate work-related problems in a calm and competent manner.
Explore topics such as Problem Solving , the PICK Chart , How to Solve Problems & the Barriers to Problem Solving from our Harappa Diaries blog section and develop your skills.
By Teach Educator
Published on: February 4, 2024
7 Steps to Problem-Solving is a systematic process that involves analyzing a situation, generating possible solutions, and implementing the best course of action. While different problem-solving models exist, a common approach often involves the following seven steps:
It’s important to note that these steps are not always linear and may involve iteration. Problem-solving is often an ongoing process, and feedback from the implementation and evaluation stages may lead to adjustments in the chosen solution or the identification of new issues that need to be addressed.
A high school has noticed a decline in student engagement and performance in mathematics classes over the past few years. Students seem disinterested, and there is a noticeable decrease in test scores. The traditional teaching methods are not effectively capturing students’ attention, and there’s a need for innovative solutions to rekindle interest in mathematics.
Identify the problem:.
This problem-solving approach in education involves a systematic process of identifying, analyzing, and addressing issues to enhance the learning experience for students.
What is the official website of the bihar board.
Bihar Board The official website of the Bihar Board is [Bihar School Examination Board | Bihar School Examination Board. This website provides information about the board, its activities, ...
Frontline Aesop Frontline Aesop is a web-based system that helps schools and districts manage employee absences and find qualified substitutes. It allows employees to report their absences online ...
Civics Civics, also known as civic education or citizenship education, is a branch of social studies that focuses on the rights and duties of citizens. As well as ...
LNMU University India LNMU University stands for Lalit Narayan Mithila University, a public university in India. The University is ranked 1 in Bihar and ranked 92 in India ...
Save my name, email, and website in this browser for the next time I comment.
Does lnmu provide distance education & how to apply for admission at lnmu, 20 reasons why education is important, teach educator.
"Teach Educator aims to empower learners and educators alike through its comprehensive services. Dedicated to bridging educational gaps, it offers a range of resources designed to enhance teaching methodologies, provide updated curriculum insights, and foster professional development. With a commitment to accessibility, Teach Educator ensures that educational tools and information are readily available to all, promoting inclusivity in learning.
© Teach Educator 2021 - 2024 | All Rights Reserved
Privacy policy
IMAGES
VIDEO
COMMENTS
1. Define the problem. Diagnose the situation so that your focus is on the problem, not just its symptoms. Helpful problem-solving techniques include using flowcharts to identify the expected steps of a process and cause-and-effect diagrams to define and analyze root causes.. The sections below help explain key problem-solving steps.
What Is Problem Solving? Definition and Importance Problem solving is the process of finding solutions to obstacles or challenges you encounter in your life or work. It is a crucial skill that allows you to tackle complex situations, adapt to changes, and overcome difficulties with ease. Mastering this ability will contribute to both your personal...
Learn about problem-solving, a mental process that involves discovering and analyzing a problem and then coming up with the best possible solution. ... At this stage, it is important to consider all of the factors that might affect the problem at hand. ... Researching different problem-solving techniques and trying out new ones;
The Stages of Problem Solving We Can All Apply. 1. Identify the problem. ... Each problem is different, so it will require a specific solution. ... is a problem-solving method that uses creativity to find original solutions. The next step is to develop a strategy, since solutions that do not materialize in concrete steps are very difficult to ...
The 8D problem solving methodology is a systematic, team-based approach to problem solving. It is a method that guides a team through eight distinct steps to solve a problem in a systematic and comprehensive manner. The 8D process consists of the following steps:
The first stage of any problem solving process is to identify the problem(s) you need to solve. ... Individual approaches to solving a problem can be very different based on what team or role an individual holds. ... Explain the ground rules to help guide the problem-solving process and then invite members to identify any issue connecting to ...
This page continues from Problem Solving an Introduction that introduces problem solving as a concept and outlines the stages used to successfully solve problems.. This page covers the first two stages in the problem solving process: Identifying the Problem and Structuring the Problem. Stage One: Identifying the Problem. Before being able to confront a problem its existence needs to be identified.
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 ...
Find new ideas and classic advice on strategy, innovation and leadership, for global leaders from the world's best business and management experts.
To examine how problem solving develops over time, the researchers had participants solve a series of matchstick problems while verbalizing their problem-solving thought process. The findings from this second experiment showed that people tend to go through two different stages when solving a series of problems.
Examples of problem solving scenarios. The best way to get a sense of how the problem solving process works before you try it for yourself is to work through some simple scenarios. Here are three examples of how you can apply business problem solving techniques to common workplace challenges. Scenario #1: Manufacturing
Essentially every problem-solving heuristic in mathematics goes back to George Polya's How to Solve It; my approach is no exception. However, this cyclic description might help to keep the process cognitively present. A few months ago, I produced a video describing this the three stages of the problem-solving cycle: Understand, Strategize, and Implement.
Working backward is a problem-solving approach often taught to help students solve problems in mathematics. However, it's useful for real-world problems as well. Working backward is when you ...
This article explains the five problem solving steps and provides strategies on how to execute each one. Defining Problem Solving. Before we talk about the stages of problem solving, it's important to have a definition of what it is. Let's look at the two roots of problem solving — problems and solutions.
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 ...
Problem Solving Methodologies are processes through which a situation or issue may be analyzed and solutions implemented. Different methodologies may be optimized for specific applications. Employers seek people who can effectively identify and ask significant questions that clarify and lead to better solutions in a variety of work conditions.
Problem Solving Process. The process of problem-solving is an activity which has its ingredients as the specification of the program and the served dish is a correct program. This activity comprises of four steps : 1. Understanding the problem: To solve any problem it is very crucial to understand the problem first. What is the desired output ...
The purpose of the 8D methodology is to identify, correct, and eliminate recurring problems, making it useful in product and process improvement. The 8D problem solving model establishes a permanent corrective action based on statistical analysis of the problem and focuses on the origin of the problem by determining its root causes.
Problem-solving is a vital skill for coping with various challenges in life. This webpage explains the different strategies and obstacles that can affect how you solve problems, and offers tips on how to improve your problem-solving skills. Learn how to identify, analyze, and overcome problems with Verywell Mind.
9 Problem-solving tools for gathering and selecting ideas. Problem-solving tools support your meeting with easy-to-use graphs, visualisations and techniques. By implementing a problem-solving tool, you break the cycle of mundane verbal discussion, enabling you to maintain engagement throughout the session. 28. Fishbone Diagram
Here are the steps of a problem-solving process: 1. Defining the Problem. The first step in the process is often overlooked. To define the problem is to understand what it is that you're solving for. This is also where you outline and write down your purpose—what you want to achieve and why.
Although problem-solving is something everyone does on a daily basis, many people lack confidence in their ability. Here we look at the basic problem-solving process to help keep you on the right track.
7 Steps to Problem-Solving. 7 Steps to Problem-Solving is a systematic process that involves analyzing a situation, generating possible solutions, and implementing the best course of action. While different problem-solving models exist, a common approach often involves the following seven steps: Define the Problem: Clearly articulate and ...