structured problem solving examples

How to master the seven-step problem-solving process

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.

Want to subscribe to The McKinsey Podcast ?

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.

Would you like to learn more about our Strategy & Corporate Finance Practice ?

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.

Want better strategies? Become a bulletproof problem solver

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.

Explore a career with us

Strategy to beat the odds

Five routes to more innovative problem solving

McKinsey Problem Solving: Six steps to solve any problem and tell a persuasive story

The McKinsey problem solving process is a series of mindset shifts and structured approaches to thinking about and solving challenging problems. It is a useful approach for anyone working in the knowledge and information economy and needs to communicate ideas to other people.

Over the past several years of creating StrategyU, advising an undergraduates consulting group and running workshops for clients, I have found over and over again that the principles taught on this site and in this guide are a powerful way to improve the type of work and communication you do in a business setting.

When I first set out to teach these skills to the undergraduate consulting group at my alma mater, I was still working at BCG. I was spending my day building compelling presentations, yet was at a loss for how to teach these principles to the students I would talk with at night.

Through many rounds of iteration, I was able to land on a structured process and way of framing some of these principles such that people could immediately apply them to their work.

While the “official” McKinsey problem solving process is seven steps, I have outline my own spin on things – from experience at McKinsey and Boston Consulting Group. Here are six steps that will help you solve problems like a McKinsey Consultant:

Step #1: School is over, stop worrying about “what” to make and worry about the process, or the “how”

When I reflect back on my first role at McKinsey, I realize that my biggest challenge was unlearning everything I had learned over the previous 23 years. Throughout school you are asked to do specific things. For example, you are asked to write a 5 page paper on Benjamin Franklin — double spaced, 12 font and answering two or three specific questions.

In school, to be successful you follow these rules as close as you can. However, in consulting there are no rules on the “what.” Typically the problem you are asked to solve is ambiguous and complex — exactly why they hire you. In consulting, you are taught the rules around the “how” and have to then fill in the what.

The “how” can be taught and this entire site is founded on that belief. Here are some principles to get started:

Step #2: Thinking like a consultant requires a mindset shift

There are two pre-requisites to thinking like a consultant. Without these two traits you will struggle:

A healthy obsession looking for a “better way” to do things
Being open minded to shifting ideas and other approaches

In business school, I was sitting in one class when I noticed that all my classmates were doing the same thing — everyone was coming up with reasons why something should should not be done.

As I’ve spent more time working, I’ve realized this is a common phenomenon. The more you learn, the easier it becomes to come up with reasons to support the current state of affairs — likely driven by the status quo bias — an emotional state that favors not changing things. Even the best consultants will experience this emotion, but they are good at identifying it and pushing forward.

Key point : Creating an effective and persuasive consulting like presentation requires a comfort with uncertainty combined with a slightly delusional belief that you can figure anything out.

Step #3: Define the problem and make sure you are not solving a symptom

Before doing the work, time should be spent on defining the actual problem. Too often, people are solutions focused when they think about fixing something. Let’s say a company is struggling with profitability. Someone might define the problem as “we do not have enough growth.” This is jumping ahead to solutions — the goal may be to drive more growth, but this is not the actual issue. It is a symptom of a deeper problem.

Consider the following information:

Costs have remained relatively constant and are actually below industry average so revenue must be the issue
Revenue has been increasing, but at a slowing rate
This company sells widgets and have had no slowdown on the number of units it has sold over the last five years
However, the price per widget is actually below where it was five years ago
There have been new entrants in the market in the last three years that have been backed by Venture Capital money and are aggressively pricing their products below costs

In a real-life project there will definitely be much more information and a team may take a full week coming up with a problem statement . Given the information above, we may come up with the following problem statement:

Problem Statement : The company is struggling to increase profitability due to decreasing prices driven by new entrants in the market. The company does not have a clear strategy to respond to the price pressure from competitors and lacks an overall product strategy to compete in this market.

Step 4: Dive in, make hypotheses and try to figure out how to “solve” the problem

Now the fun starts!

There are generally two approaches to thinking about information in a structured way and going back and forth between the two modes is what the consulting process is founded on.

First is top-down . This is what you should start with, especially for a newer “consultant.” This involves taking the problem statement and structuring an approach. This means developing multiple hypotheses — key questions you can either prove or disprove.

Given our problem statement, you may develop the following three hypotheses:

Company X has room to improve its pricing strategy to increase profitability
Company X can explore new market opportunities unlocked by new entrants
Company X can explore new business models or operating models due to advances in technology

As you can see, these three statements identify different areas you can research and either prove or disprove. In a consulting team, you may have a “workstream leader” for each statement.

Once you establish the structure you you may shift to the second type of analysis: a bottom-up approach . This involves doing deep research around your problem statement, testing your hypotheses, running different analysis and continuing to ask more questions. As you do the analysis, you will begin to see different patterns that may unlock new questions, change your thinking or even confirm your existing hypotheses. You may need to tweak your hypotheses and structure as you learn new information.

A project vacillates many times between these two approaches. Here is a hypothetical timeline of a project:

Step 5: Make a slides like a consultant

The next step is taking the structure and research and turning it into a slide. When people see slides from McKinsey and BCG, they see something that is compelling and unique, but don’t really understand all the work that goes into those slides. Both companies have a healthy obsession (maybe not to some people!) with how things look, how things are structured and how they are presented.

They also don’t understand how much work is spent on telling a compelling “story.” The biggest mistake people make in the business world is mistaking showing a lot of information versus telling a compelling story. This is an easy mistake to make — especially if you are the one that did hours of analysis. It may seem important, but when it comes down to making a slide and a presentation, you end up deleting more information rather than adding. You really need to remember the following:

Data matters, but stories change hearts and minds

Here are four quick ways to improve your presentations:

Tip #1 — Format, format, format

Both McKinsey and BCG had style templates that were obsessively followed. Some key rules I like to follow:

Make sure all text within your slide body is the same font size (harder than you would think)
Do not go outside of the margins into the white space on the side
All titles throughout the presentation should be 2 lines or less and stay the same font size
Each slide should typically only make one strong point

Tip #2 — Titles are the takeaway

The title of the slide should be the key insight or takeaway and the slide area should prove the point. The below slide is an oversimplification of this:

Even in consulting, I found that people struggled with simplifying a message to one key theme per slide. If something is going to be presented live, the simpler the better. In reality, you are often giving someone presentations that they will read in depth and more information may make sense.

To go deeper, check out these 20 presentation and powerpoint tips .

Tip #3 — Have “MECE” Ideas for max persuasion

“MECE” means mutually exclusive, collectively exhaustive — meaning all points listed cover the entire range of ideas while also being unique and differentiated from each other.

An extreme example would be this:

Slide title: There are seven continents
Slide content: The seven continents are North America, South America, Europe, Africa Asia, Antarctica, Australia

The list of continents provides seven distinct points that when taken together are mutually exclusive and collectively exhaustive . The MECE principle is not perfect — it is more of an ideal to push your logic in the right direction. Use it to continually improve and refine your story.

Applying this to a profitability problem at the highest level would look like this:

Goal: Increase profitability

2nd level: We can increase revenue or decrease costs

3rd level: We can increase revenue by selling more or increasing prices

Each level is MECE. It is almost impossible to argue against any of this (unless you are willing to commit accounting fraud!).

Tip #4 — Leveraging the Pyramid Principle

The pyramid principle is an approach popularized by Barbara Minto and essential to the structured problem solving approach I learned at McKinsey. Learning this approach has changed the way I look at any presentation since.

Here is a rough outline of how you can think about the pyramid principle as a way to structure a presentation:

As you build a presentation, you may have three sections for each hypothesis. As you think about the overall story, the three hypothesis (and the supporting evidence) will build on each other as a “story” to answer the defined problem. There are two ways to think about doing this — using inductive or deductive reasoning:

deductive versus inductive reasoning in powerpoint arguments

If we go back to our profitability example from above, you would say that increasing profitability was the core issue we developed. Lets assume that through research we found that our three hypotheses were true. Given this, you may start to build a high level presentation around the following three points:

example of hypotheses confirmed as part of consulting problem solving

These three ideas not only are distinct but they also build on each other. Combined, they tell a story of what the company should do and how they should react. Each of these three “points” may be a separate section in the presentation followed by several pages of detailed analysis. There may also be a shorter executive summary version of 5–10 pages that gives the high level story without as much data and analysis.

Step 6: The only way to improve is to get feedback and continue to practice

Ultimately, this process is not something you will master overnight. I’ve been consulting, either working for a firm or on my own for more than 10 years and am still looking for ways to make better presentations, become more persuasive and get feedback on individual slides.

The process never ends.

The best way to improve fast is to be working on a great team . Look for people around you that do this well and ask them for feedback. The more feedback, the more iterations and more presentations you make, the better you will become. Good luck!

If you enjoyed this post, you’ll get a kick out of all the free lessons I’ve shared that go a bit deeper. Check them out here .

Do you have a toolkit for business problem solving? I created Think Like a Strategy Consultant as an online course to make the tools of strategy consultants accessible to driven professionals, executives, and consultants. This course teaches you how to synthesize information into compelling insights, structure your information in ways that help you solve problems, and develop presentations that resonate at the C-Level. Click here to learn more or if you are interested in getting started now, enroll in the self-paced version ($497) or hands-on coaching version ($997). Both versions include lifetime access and all future updates.

The Complete Guide to Structured Problem Solving

When you are looking to thoroughly solve a pesky problem, structured problem solving is the way to go. Structured problem solving allows you to explore the problem, get to the heart of the issue, and develop a creative solution that finally solves the issue.

To illustrate this example, Takashi Amano was a nature photographer and avid aquarist. He started developing art in the form of fish tanks – which he called nature aquariums. The problem was algae would grow in his tanks and ruin his art. Not deterred, Mr. Amano found a shrimp distributor who bred, small, and clear micro-shrimp which were various algae eaters. Mr. Amano ordered thousands of them and promoted them in the hobby – to the point where the shrimp are now called Amano Shrimp.

He got creative. Knowing he needed a lasting solution to his algae problem, a clear shrimp that would eat the algae and not detract from his art was perfect.

The Basic idea of Structured Problem Solving

Professionals who solve complex problems for a living all start from the same place. They need to understand the actual problem they are solving. They ask themselves questions to get to the heart of the problem.

Usually promoting thinking with questions like what is the real problem, how can we gather data about the root problem, brainstorm solutions, test a solution and monitor it?

Why Structured Problem-Solving Works

Often, we are eager to jump into solving the first apparent problem with a variety of solutions. Why structured problem-solving works is because it forces us to slow down. By slowing down, we understand the problem first, without leaping into “fix-it” mode with preconceived notions of how the problem should be solved.

Studies have also found that having explicit techniques (methods for problem-solving) in the structured problem-solving workflow not only improves the problem-solving process but also increases the knowledge base all individuals can pull from. Basically, using structured problem solving allows better solutions to be developed while ensuring everyone participates in sharing their own unique knowledge.

The two ideas translate into the problem-solving principles of:

Seek to understand before we seek to solve
Search early, search often

By understanding the problem inside and out, the individual, or team can make more informed decisions and generate appropriate solutions.

There are a variety of techniques to work through the process. Below are some sample ways to do structured problem solving before getting into the walk-through further down in the article.

Multiple Ways of Structured Problem Solving

There are many techniques to perform structured problem solving, or at least get more in-depth in certain aspects of the process. Some of my favorite ones include

Pre-mortem analysis: Instead of working through a project and assessing what went wrong at the end, run through a simulation of the project to see where the project could fail before you even start. Where and why did it fail? Then brainstorm solutions to avoid those issues without creating new ones.

The Hat Technique: There are 6 colored hats, all with different roles. Whether alone or in a group, assign some time or a specific person to that role. Having a person designated to each role means that all ideas are validated through six different lenses. Plus, everyone has a designated role which helps keep people engaged, and limits feelings getting hurt since everyone is simply doing their assigned role.

PDCA Cycle: An easy way to remember the process is the PDCA cycle. Which stands for Plan-Do-Check-Act. PDCA is a high-level way to remember how the structured problem-solving process works.

You can also use the PDCA Model to manage your personal development too !

Get the Creative Juices Flowing

I like to start all my structured problem-solving sessions with some fun at the beginning of the session to get everyone’s creative juices flowing. By taking the 5 minutes to have a little fun, it is surprising how much more creative and engaged people are with the structured problem-solving process!

Problem-solving can be a stressful process, and it can even be high-stakes with the future of the group’s work hanging in the balance. However, laughing together helps relieve stress, makes people more creative, and improves social bonding.

The New Idea: One creative thinking exercise to start your session in a fun way, the goal is to split into two groups. Each group generates two dissimilar words. Then they swap words. For instance, “bug” & “sky-diving” and “winter” and “bikinis” for the other. Then the groups must devise the best ideas for those two words. For the bugs, you could make parachute designs that are themed after a different butterfly, and for the other, you could make a winter work-out with the goal have bikini-ready bodies by the summer. Silly ideas but shows there is a solution to even the weirdest problems.

Horrible idea challenge: Think of your problem. Then have everyone compete to come up with the worst idea. The practical part is that it helps to see what not to do – plus, part of the fun is seeing how creative people can be!

Beyond the two creative ideas, there are also 13 mental models which make work easier overall as well.

The Structured Problem Solving Process

1. define the problem statement.

The first step is defining what the real problem is. Below are some prompts to get the right decision-makers and problem-solvers sent in the right direction to tackle the challenge.

Is the problem many problems?
What requirements must a solution meet?
Which problem solvers should we engage?
What information and language should the problem statement include?
Tip: To engage the largest number of solvers from the widest variety of fields, a problem statement must meet the twin goals of being extremely specific but not necessarily technical.
What do solvers need to submit?
What incentive do solvers need?
How will solutions be evaluated, and success measured?

Problem statements are a statement of a current issue or problem. For example , Problem: Voter turnout in the southwest region of Florida has been significantly decreasing over the past decade, while other areas of the state continue to see increasing numbers of voters at the polls.

Writing one or two sentences takes the whole issue and makes it very clear what the issue is.

2. Root Cause Analysis

After getting the foundation set, an understanding of the root problem is critical. If you want to go through all the effort of structured problem solving, you might as well get to the real problem in the end.

Think of weeds in a garden. A potential solution is to mow over the weeds and they are gone. However, every few days the weeds keep coming back. That is because the root is the root issue in this scenario. You need to get the whole root system of the weed out to stop those pesky weeds in your garden.

Below are three techniques to help with Root-Cause Analysis

5 whys: When a problem occurs, drill down to its root cause by asking “Why?” five or more times. Then, when a counter-measure becomes apparent, you follow it through to prevent the issues from recurring.

Fishbone diagram: (Also called Ishikawa diagram named after Kaoru Ishikawa) is a cause-and-effect diagram that helps managers track down the reasons for imperfections, variations, defects, or failures.

Cause mapping: a cause map provides a visual explanation of why an incident occurred. It connects individual cause-and-effect relationships to reveal the system of cause within an issue.

3. Gather Data

After analyzing the problem and getting to the root cause – you need to gather information to understand why the problem and situation are happening. Doing the research and understanding how the different forces are interacting lets you understand why the problem is happening and how the overall solution is occurring.

Below are three different methods for gathering data to understand the context and interplaying forces in the current problem.

Gemba walk: The purpose is to allow managers and leaders to observe actual work process, engage with employees, gain knowledge about the work process, and explore opportunities for continuous improvement

Process mapping: A process map is a planning and management tool that visually describes the flow of work. Allowing you to see hiccups, bottlenecks, or high-failure points in the process.

Focus groups : Asking open-ended questions to a group of individuals ranging from 6-10 people. Letting you get different perspectives on the same issue.

4. Develop Potential Solutions

The next part is the fun part. You take all the research you’ve gathered in the first three aspects and put them together to come up with a solution to solve the problem. The common way is do Brainstorming.

Harvard Business Review sites that traditional brainstorming, in groups trying to answer the question, isn’t as effective as individuals coming up with ideas on their own first. Working in a big group doesn’t work for many reasons. Working in groups encourages social loafing (coasting on other’s ideas), some members experience social anxiety (introverted members feeling self-conscious of throwing in ideas), and it focuses too much on the solutions over the problem.

The better way to brainstorm is to have everyone work on the main problems and their solutions alone, and then reconvene after twenty minutes. Then everyone shares their top one or two ideas and what features of the problem it tackles.

This method gives everyone time to think about their solutions, present their ideas, and lets all the voices be heard. Plus, all the ideas can then smashed together to come up with a solution based on everyone’s input.

Remember, the solution has to solve the core of the issue and get to the root cause. Plus, it must be feasible in terms of the money, time, and manpower allocated to the project. Use the constraints as a guide to direct the project!

5. Implement a Solution

After running through the potential solutions – pick one and trial run it. Think of the minimum viable product to get to the root cause. You won’t know if you are alleviating the problem until a potential solution is out in the field.

For example , Airbnb founders, Brian Chesky and Joe Gebbia could not afford the rent for their apartment (the problem). They decided to put an air mattress in their living room and turn it into a bed and breakfast (MVP solution). The goal was to make a few bucks, but instead, they discovered the idea the connect Bed and Breakfasts to people looking for renters. They started advertising on Craiglist, then their website, and the story continues.

The point of the story is to illustrate that small tests can be done to see if you are solving the main issue! Their issue was not that someone needed to stay in their apartment for them to make rent – the issue was there was no service that easily let Bed and Breakfasts work with potential clients.

6. Monitor for Success

Once a solution is implemented, that is not the end. You must make sure the solution works. Keeping in mind the below questions

Who is responsible for the solution?
What are the risks of implementing the solution?

Some ways to monitor for success are:

Failure mode and effect analysis: A step-by-step approach for identifying all possible failures in a design, a manufacturing process, product, or service.

Impact analysis: A detailed study of business activities, dependencies, and infrastructure. It reveals how critical products and services are delivered and examines the potential impact of a disruptive (or additive solution) event over time

Kaizen : The Japanese term for “continuous improvement”. It is a business philosophy regarding the process that continuously improves operations and involves all employees.

Illustrated Example

A often find it helpful to see someone do the process as well. Here is a great video of IDEO re-working the shopping cart.

Key Take-Aways

What sets apart okay problem solvers from great problem solvers is the ability to think in repeatable, useful frameworks.

Structured Problem Solving is a general concept used to solve challenging problems, and there are hundreds of different methods that fall underneath it.

Action Item

Think of a tough challenge you are facing at work or in your personal life. Test run your problem through the structured problem-solving process with a few of the above techniques, and see what solution you can generate to get to the root of the issue!

The Basics of Structured Problem-Solving Methodologies: DMAIC & 8D

Topics: Minitab Engage

When it comes to solving a problem, organizations want to get to the root cause of the problem, as quickly as possible. They also want to ensure that they find the most effective solution to that problem, make sure the solution is implemented fully, and is sustained into the future so that the problem no longer occurs. The best way to do this is by implementing structured problem-solving. In this blog post, we’ll briefly cover structured problem-solving and the best improvement methodologies to achieve operational excellence. Before we dive into ways Minitab can help, let’s first cover the basics of problem-solving.

WHAT IS STRUCTURED PROBLEM-SOLVING?

Structured problem-solving is a disciplined approach that breaks down the problem-solving process into discrete steps with clear objectives. This method enables you to tackle complex problems, while ensuring you’re resolving the right ones. It also ensures that you fully understand those problems, you've considered the reasonable solutions, and are effectively implementing and sustaining them.

WHAT IS A STRUCTURED PROBLEM-SOLVING METHODOLOGY?

A structured problem-solving methodology is a technique that consists of a series of phases that a project must pass through before it gets completed. The goal of a methodology is to highlight the intention behind solving a particular problem and offers a strategic way to resolve it. WHAT ARE THE BEST PROBLEM-SOLVING METHODOLOGIES?

That depends on the problem you’re trying to solve for your improvement initiative. The structure and discipline of completing all the steps in each methodology is more important than the specific methodology chosen. To help you easily visualize these methodologies, we’ve created the Periodic Table of Problem-Solving Methodologies. Now let’s cover two important methodologies for successful process improvement and problem prevention: DMAIC and 8D .

8D is known as the Eight Disciplines of problem-solving. It consists of eight steps to solve difficult, recurring, or critical problems. The methodology consists of problem-solving tools to help you identify, correct, and eliminate the source of problems within your organization. If the problem you’re trying to solve is complex and needs to be resolved quickly, 8D might be the right methodology to implement for your organization. Each methodology could be supported with a project template, where its roadmap corresponds to the set of phases in that methodology. It is a best practice to complete each step of a given methodology, before moving on to the next one.

MINITAB ENGAGE, YOUR SOLUTION TO EFFECTIVE PROBLEM-SOLVING

Minitab Engage TM was built to help organizations drive innovation and improvement initiatives. What makes our solution unique is that it combines structured problem-solving methodologies with tools and dashboards to help you plan, execute, and measure your innovation initiatives! There are many problem-solving methodologies and tools to help you get started. We have the ultimate end-to-end improvement solution to help you reach innovation success.

Ready to explore structured problem-solving?

Download our free eBook to discover the top methodologies and tools to help you accelerate your innovation programs.

See how our experts can train your company to better understand and utilize data. Find out more about our Training Services today!

Trust Center

Terms of Use
Privacy Policy
Cookies Settings

Publications
Processing Theories
Alkaline Protective Coatings
Photosensitive Protective coatings
Bonding Materials
Debonding Materials
Anti-reflective Coatings
Directed Self-Assembly
Multilayer Systems
Flex Sensors
Moisture Sensors
Manufacturing
Executive Advisory Board
Quality, Environmental and Safety
Community Giving
Partnerships
Press Releases

Posts by Topic

Brewer Science (22)
company (22)
wafer-level packaging (21)
lithography (15)
Leadership (14)
sensors (14)
Internships (9)
Technology (9)
innovation (7)
printed electronics (7)
Internet of Things (6)
Sustainability (6)
community (6)
new business developement (6)
Directed Self-Assembly (5)
Engineering (5)
Predictive Maintenance (5)
Science, (5)
development (5)
research (5)
zero defects (5)
Integrated Circuits (4)
coat uniformity (4)
culture (4)
spin coat (4)
technology advancement (4)
thin wafer handling (4)
workplace safety (4)
3D packaging (3)
Datastream (3)
Future Leaders (3)
GreenCircle Certified (3)
Manufacturing (3)
Pillars of Impact (3)
Problem Solving (3)
STEM Jobs (3)
business (3)
education (3)
moisture sensors (3)
nanosensors (3)
planarization (3)
processing equipment (3)
quality (3)
quality control (3)
semiconductor manufacturing (3)
semiconductors (3)
temporary bonding materials (3)
wearable electronics (3)
3D Stacking (2)
BrewerBOND (2)
CS ManTech (2)
Children (2)
Convanta (2)
Corning (2)
Creativity (2)
Energy Management (2)
Fan-Out Wafer Level Packaging (2)
LED manufacturing (2)
Nanotechnology (2)
Polymers (2)
Potential (2)
R & D (2)
SEMICON Japan (2)
Walter Barnes (2)
Zero Waste to Landfill (2)
advanced materials (2)
advanced packaging (2)
advanced technology (2)
advanved lithography (2)
benchtop equipment (2)
carbon nanotubes (2)
disruptive materials (2)
entrepreneurs (2)
environment (2)
environmental monitoring (2)
etch protection (2)
human resources (2)
inflect sensors (2)
infrastructure management (2)
integration (2)
mems and sensors (2)
moore's law (2)
multilayer (2)
nanoscience (2)
oculus rift (2)
olympics (2)
scratch-resistant (2)
smart manufacturing (2)
spin process (2)
spincoat (2)
supply chain (2)
thermal slide debonding (2)
thick-film (2)
wet etching (2)
3-D Stacking (1)
3D printing (1)
Adhesives (1)
Anniversary (1)
Artifical Intelligence (1)
Becky Rich (1)
Biometric Sensors (1)
BrewerBOND 220 (1)
Building and Home Automation (1)
Compound Semiconductor Manufacturing (1)
Covanta Energy (1)
Debonding Process (1)
Electronics (1)
Farming (1)
GaN roughening (1)
Gartner Hype Scale (1)
Gartner Inc. (1)
Geothermal (1)
Inflect Moisture Sensor (1)
Lateral Force (1)
Medical and Health-Care Systems (1)
National Chemistry Week (1)
National Guardsman (1)
National Manufacturing Day (1)
RDL-first (1)
Rama Puligadda (1)
Ray Kurzweil (1)
SEMICON Taiwan (1)
SOC Materials (1)
Scratch-resistant sensors (1)
Selective Surface Modification (1)
Semuconductors (1)
Small Molecule Analysis (1)
Strategic Materials Conference (1)
Temporary Bonding (1)
Testing Services (1)
Thermal Stability (1)
Transportation (1)
Truck Drivers (1)
Vehicle (1)
ZoneBOND (1)
adafruit (1)
analytical group (1)
anti-reflective coating (1)
anti-reflective coatings (1)
arc materials (1)
autonomous car (1)
back-end processes (1)
batteries (1)
bureau veritas certifications (1)
chemical engineering (1)
chemical stability (1)
data logging (1)
debonder (1)
debonding (1)
debonding materials (1)
depth-of-focus (1)
devices (1)
digitsole (1)
eco-friendly (1)
economics (1)
embedded wafer-level (1)
energy-from-waste (1)
environmental (1)
environmental standards (1)
etching (1)
facial recognition (1)
flexible electronics (1)
flexible sensors (1)
fossil fuel (1)
grid array (1)
hardmask (1)
higher education (1)
hybrid bonding (1)
idtechex (1)
industry 4.0 (1)
inflect flex sensor (1)
insoluble (1)
intellectual property (1)
inventors day (1)
landfill (1)
laser debonding (1)
laser release (1)
lithographic (1)
lithographic composition (1)
management (1)
mechanical release (1)
multi-layer (1)
nano technologies (1)
optical simulations (1)
pebble watch (1)
personality traits (1)
photolithography (1)
pixie scientific (1)
planarized substrates (1)
powerlifting (1)
process engineer (1)
prolith (1)
protective coatings (1)
pure enjoyment (1)
purification (1)
recycling (1)
research and development (1)
scientific computing (1)
silicon wafers (1)
smart technology (1)
smart watches (1)
sms audio biosport earbuds (1)
solar energy (1)
soluble (1)
spin bowl (1)
spin coaters (1)
spin-on carbon (1)
square substrate (1)
substrate size (1)
surface modification (1)
temperature sensors (1)
temporary wafer bonding (1)
trilayer (1)
trilayer resist process (1)
ultrathin wafers (1)
unilayer processing (1)
unplugged (1)
wafer problems (1)
wearable devices (1)
wearable solar (1)
wireless headphones (1)
zero landfill (1)

Six Steps to Structured Problem Solving

Subscribe to our blog.

What happens when a big problem pops up? For most of us, our first reaction is, “Quick! Let’s fix it and make this problem go away.” However, if we rush to fix the problem too quickly, we may end up implementing a “solution” or “quick fix” that doesn’t solve anything because we didn’t take the time to truly identify and understand the root cause of the problem itself.

One way we can keep ourselves from falling into this trap is by having a formal structured problem-solving (SPS) process in place. Then, when problems do occur, we know exactly what steps to take to help ensure that our solution really will “make it go away.” While there are different variations to an SPS ( 8D , 5Why , DMAIC , etc.), they all follow the same basic steps.

1. Define the Problem

It is important to write a problem statement that is easily understood and is stated purely in terms of measurable or observable symptoms. At this point, there should be no mention of suspected causes or possible solutions. We just need to know what the problem is. A good problem statement might look something like this: “High (greater than 8 ppb) trace metals in one of our hardmask products are causing unacceptably high defect counts with our most important customer. We will lose this business if we cannot correct the problem by the end of the year.”

2. Describe the Current Situation

We do this by examining data that is readily available. In our hardmask example, we would collect batch data to identify the specific batches with the elevated defects and then study this data to see what they have in common. Were they all made in a particular manufacturing location or on the same equipment set? Did they all use the same lots of the raw materials? By identifying where the problem is occurring, and where it is not occurring, we begin to zero in on what is causing our problem.

3. Identify Possible Causes

To identify possible causes, we should gather the team and brainstorm all potential causes that come to mind. Once we’ve exhausted all possibilities, we can then start systematically ruling items out. This is the most time-consuming, but one of the most vital steps in the process as we take each potential cause and work to rule it out. We must keep working until we have eliminated everything but the root cause.

4. Verify Root Cause

When we think that we have identified the true root cause, we need verify that it is the root cause by testing out our theory. For our hardmask example, let’s say that we believe that the root cause is due to a bad batch of one of the raw materials. We can test our theory by making a new batch with everything the same except for a new batch of the suspect ingredient. If the defect levels are back to normal, that’s a good indication that we have confirmed our root cause.

5. Implement Solution

After we’ve identified the root cause, we implement a solution to remedy the issue, standardizing our solution and making the change permanent. This could mean updating specifications, writing new training materials, updating training packages or updating the FMEA. In the case of our hardmask example, we would need to create specifications and appropriate testing methods that will alert us that a batch of raw material is bad before we use it.

6. Monitor for Success

After the solution has been implemented, test data can then be created to find which solutions offer the best improvements. In the case of our hardmask example, we would run test batches to make sure that we have the correct solution in place. Measurements should also be taken on a scheduled basis to continue to confirm that the solution is still valid, making updates if and when needed.

To stay up to date on industry hot topics, subscribe to the Brewer Science blog . You can also stay up to date on Brewer Science industry events, topics and news by following us on Twitter , YouTube , LinkedIn , or Facebook .

About Author

Karen Brown, Director of Organizational Development & Relationships, has been employed with Brewer Science for over a decade. Her background in employee development and training has made her an expert for the Brewer Science team in crafting successful, problem-solving employees

Are Mental Models Limiting Your Growth? – Lessons of Leadership

Subscribe To Blog

Subscribe to email updates.

At Brewer Science, our customer relationships don’t end when you buy materials and equipment. Because we want to work hand-in-hand to get your processes perfect, we’ve empowered an extensive applications and support team to help with all your processing needs.

[email protected]

Continuous Improvement Toolkit

Effective Tools for Business and Life!

A3 Thinking: A Structured Approach to Problem Solving

5 MINUTES READ

Also known as A3 Problem Solving.

Variants include 8D and CAPA.

A significant part of a leader’s role involves addressing problems as they arise. Various approaches and tools are available to facilitate problem-solving which is the driving force behind continuous improvement. These methods range from the advanced and more complex methodologies like Six Sigma to the simpler and more straightforward A3 thinking approach.

The power of the A3 approach lies in its systematic and structured approach to problem-solving. Although it appears to be a step-by-step process, A3 is built around the PDCA philosophy. It relies on the principle that it is much better to address the real root-cause rather than trying to find a solution. Hence, it’s important not to jump to the solution when solving a problem as it is likely to be less effective.

A3 thinking provides an effective way to bring together many of the problem-solving tools into one place. For example, techniques such as the 5 Whys and fishbone analysis can be used during the ‘Analysis’ stage to help identifying the root causes. Additionally, visual aids and graphs are highly recommended in the A3 report, as they are more effective than text in communicating ideas and providing concise project updates.

A3 thinking involves the practice of consolidating the problem, analysis, countermeasures, and action plan onto a single sheet of paper, commonly an A3-sized sheet. This brief document serves as a summary of the project at hand and is regarded as a valuable storytelling tool for project communication. Utilizing the A3 approach doesn’t require any specialized software or advanced computer skills. You may however use readily available A3 templates , or rely on basic tools such as paper, pencil and an eraser as you will need to erase and rewrite several times.

One of the characteristics of the A3 approach is that it does not get into specific details. Detailed documents are usually attached to the A3 report to prevent overwhelming the reader with an excess of information.

The A3 process is typically structured in multiple stages based on the PDCA model. The primary focus is on developing understanding of the current situation and defining the desired outcome before thinking about the solution. While the exact number of stages may vary depending on the preference of the company, what truly matters is adhering to a structured approach to problem-solving.

A3 Seven Stages Model

An A3 process is often managed by an individual who should own and maintain the A3 report. This individual takes the lead in steering the process, facilitating team involvement, and preparing the A3 report with team input. One of the most common models for A3 thinking is the seven stages model which is described in the following.

1. Background – The first step is to identify the business reason for choosing this problem or opportunity. In this stage, you need to identify the gap in performance and the extent of the problem.

2. Current situation – The purpose of this stage is to document the current state of the problem. You may need to refer to the process map or go to the Gemba to truly understand the current situation.

3. Target – The purpose of this stage is to define the desired future state. Clearly identify the expected benefits from solving the problem, the scope, and the key metrics that will help measure the success of the project.

4. Analysis – The objective of this stage is to conduct an in-depth analysis of the problem and understand why it’s happening. It might involve tools like the 5 Whys and cause-and-effect analysis, as well as advanced statistical methods.

5. Countermeasures – Countermeasures are the actions to be taken to eliminate root causes or reduce their effects. The team should brainstorm and evaluate possible countermeasures based on the analysis conducted earlier.

6. Implementation Plan – To achieve the target, develop a workable plan to implement the countermeasures. Gantt charts are great ways to manage implementation plans very simply and easily. Once the action plan is finalized, the team should begin working on the activities needed to implement the countermeasures.

7. Follow-up – The final stage involves evaluating the implementation of the plan and the results achieved. Follow-up actions are important to ensure the benefits extend beyond the project’s completion.

A3 thinking is considered to be the practical form of the PDCA model.

There are many online templates that can be used to manage your problem-solving efforts. One of the simplest and most straightforward ways is to use this A3 problem solving template .

Wrapping Up

A3 thinking represents a logical and structured approach for problem solving and continuous improvement. This approach can be used for most kinds of problems and in any part of the business. Originating from the Toyota Production System (TPS), it has been adopted by many Lean organizations around the world.

A3 thinking not only provides a systematic approach for problem-solving. The development of a continuous improvement culture is at the core of A3 thinking. It has become one of the most popular Lean tools today where people and teams work together to solve problems, share results and learn from each other.

Other Formats

Do you want to use the slides in your training courses?

A3 Thinking Training Material – $18.85

Project Charter

Gantt Chart

Related Templates

A3 Problem Solving

Written by:

CIToolkit Content Team

Framework Garage Consulting

May 29, 2023

Structured Thinking 101: How to Apply It to Everything You Do

Updated: Sep 3, 2023

Do you ever face a difficult problem or a tough decision and feel overwhelmed? You’re not alone; we all go through such situations. But, there’s a powerful tool that can help you overcome any challenge with confidence and clarity. It’s called structured thinking, and you already have this skill. In fact, you’ve been using it for a long time and just need to start applying it to more areas of your life: Have you built something with Lego blocks? Assembled furniture? Searched for a job? Chosen a restaurant for dinner? Cooked a meal? All of these require structured thinking. Let’s rediscover it in the next 3 minutes.

What is structured thinking?

Structured thinking is a systematic and organized way of breaking down big problems into smaller, more manageable parts. It's like solving a puzzle: you need a clear framework to analyze the problem, gather information, and find the best solution.

Let's try it out with a common task: planning a trip.

How do you plan a trip that you enjoy? There are many possible answers, but let's keep it simple: the goal is to have a good time. That's step 1: defining the objective .

Now that we know what we want, let's list everything that we need to do to achieve our objective.

These are areas you need to make decisions on: dates, duration, things to do, flights, accommodations, transportation, meals, local events, packing, payment methods, and entry fees to places we want to visit. We also have a budget range, so let’s include that in our elements.

Information

Gather all the relevant information for each element. For example, we research flight durations, flight prices, accommodation options, proximity to places we want to visit, access to cab or public transportation, etc. This step usually takes the most effort because the research is time-consuming.

Analyze and evaluate the information for each element to narrow down your choices later. How many flight options? Can you travel by road instead? How many different experiences do you want to cover throughout your trip? Cash, credit, or debit card? Hotels or Airbnb? You will have more than one option for each element.

Based on your analysis of various options, you start deciding on each element. Your decisions are aligned with your budget and the objective of your trip. By now, you have a clear plan. For example, for a 4-day trip, you will be booking a cab to the airport. You’ll be using local transport at your destination to get to the hotel in the evening. You will then attend a concert and have dinner nearby at a top-rated restaurant. Your plan is taking shape and you can picture yourself experiencing your trip already.

Think of a timeline as a roadmap where you start sequencing your choices. What comes first, then next, and so on. You think about practically every stage. We do this already on our calendars while planning a workday or week. A visual sequence helps you quickly identify conflicts and you can react at the earliest. For example, to take a flight at 9 am, you need to reach the airport by 7 am, factor in travel time to the airport, and wake up accordingly. Day 2 of your trip has a museum visit, a meal at a popular restaurant, a visit to a recommended tourist destination, and a historical monument tour. Is it possible to fit in on day 2? Having all this on a timeline will force you to look at what’s practically possible, make a decision, and defer or abandon experiences that aren’t aligned with your trip's objective.

Execute your plan. Make the bookings and visualize your timeline.

This is where everything comes together and you see the benefits of your planning.

Let's recap: we started with a clear goal and broke it into smaller, manageable tasks. This is structured thinking, and we just created a framework for planning a trip. It's your recipe for planning an amazing trip. If you are happy with how your trip went, you can use this recipe again whenever you want to travel. You would not need to start with a blank planner. You can also improve your framework with time and experience.

You can share this framework with anyone because it's a basic guideline for planning a trip. It doesn't matter which destination, how many people, or what time of the year. It's a structure that you or anyone else can use. You just need to process new information into the same framework you created. When you simplify the concepts into basic and easy explanations, you can relate to them better. The best part? You have done all of this before many times but in your head without realizing it's actually called structured thinking.

Now imagine if you had a framework for everything you need to do regularly. That would be amazing, wouldn't it?

Take a step towards refining your thinking.

Subscribe to my newsletter if you haven't already and join me on a journey of continuous growth.

Did you find this read useful? Already brimming with ideas?

40 problem-solving techniques and processes

All teams and organizations encounter challenges. Approaching those challenges without a structured problem solving process can end up making things worse.

Proven problem solving techniques such as those outlined below can guide your group through a process of identifying problems and challenges , ideating on possible solutions , and then evaluating and implementing the most suitable .

In this post, you'll find problem-solving tools you can use to develop effective solutions. You'll also find some tips for facilitating the problem solving process and solving complex problems.

Design your next session with SessionLab

Join the 150,000+ facilitators  using SessionLab.

What is problem solving?

Problem solving is a process of finding and implementing a solution to a challenge or obstacle. In most contexts, this means going through a problem solving process that begins with identifying the issue, exploring its root causes, ideating and refining possible solutions before implementing and measuring the impact of that solution.

For simple or small problems, it can be tempting to skip straight to implementing what you believe is the right solution. The danger with this approach is that without exploring the true causes of the issue, it might just occur again or your chosen solution may cause other issues.

Particularly in the world of work, good problem solving means using data to back up each step of the process, bringing in new perspectives and effectively measuring the impact of your solution.

Effective problem solving can help ensure that your team or organization is well positioned to overcome challenges, be resilient to change and create innovation. In my experience, problem solving is a combination of skillset, mindset and process, and it’s especially vital for leaders to cultivate this skill.

A group of people looking at a poster with notes on it

What is the seven step problem solving process?

A problem solving process is a step-by-step framework from going from discovering a problem all the way through to implementing a solution.

With practice, this framework can become intuitive, and innovative companies tend to have a consistent and ongoing ability to discover and tackle challenges when they come up.

You might see everything from a four step problem solving process through to seven steps. While all these processes cover roughly the same ground, I’ve found a seven step problem solving process is helpful for making all key steps legible.

We’ll outline that process here and then follow with techniques you can use to explore and work on that step of the problem solving process with a group.

The seven-step problem solving process is:

1. Problem identification

The first stage of any problem solving process is to identify the problem(s) you need to solve. This often looks like using group discussions and activities to help a group surface and effectively articulate the challenges they’re facing and wish to resolve.

Be sure to align with your team on the exact definition and nature of the problem you’re solving. An effective process is one where everyone is pulling in the same direction – ensure clarity and alignment now to help avoid misunderstandings later.

2. Problem analysis and refinement

The process of problem analysis means ensuring that the problem you are seeking to solve is the right problem . Choosing the right problem to solve means you are on the right path to creating the right solution.

At this stage, you may look deeper at the problem you identified to try and discover the root cause at the level of people or process. You may also spend some time sourcing data, consulting relevant parties and creating and refining a problem statement.

Problem refinement means adjusting scope or focus of the problem you will be aiming to solve based on what comes up during your analysis. As you analyze data sources, you might discover that the root cause means you need to adjust your problem statement. Alternatively, you might find that your original problem statement is too big to be meaningful approached within your current project.

Remember that the goal of any problem refinement is to help set the stage for effective solution development and deployment. Set the right focus and get buy-in from your team here and you’ll be well positioned to move forward with confidence.

3. Solution generation

Once your group has nailed down the particulars of the problem you wish to solve, you want to encourage a free flow of ideas connecting to solving that problem. This can take the form of problem solving games that encourage creative thinking or techniquess designed to produce working prototypes of possible solutions.

The key to ensuring the success of this stage of the problem solving process is to encourage quick, creative thinking and create an open space where all ideas are considered. The best solutions can often come from unlikely places and by using problem solving techniques that celebrate invention, you might come up with solution gold.

4. Solution development

No solution is perfect right out of the gate. It’s important to discuss and develop the solutions your group has come up with over the course of following the previous problem solving steps in order to arrive at the best possible solution. Problem solving games used in this stage involve lots of critical thinking, measuring potential effort and impact, and looking at possible solutions analytically.

During this stage, you will often ask your team to iterate and improve upon your front-running solutions and develop them further. Remember that problem solving strategies always benefit from a multitude of voices and opinions, and not to let ego get involved when it comes to choosing which solutions to develop and take further.

Finding the best solution is the goal of all problem solving workshops and here is the place to ensure that your solution is well thought out, sufficiently robust and fit for purpose.

5. Decision making and planning

Nearly there! Once you’ve got a set of possible, you’ll need to make a decision on which to implement. This can be a consensus-based group decision or it might be for a leader or major stakeholder to decide. You’ll find a set of effective decision making methods below.

Once your group has reached consensus and selected a solution, there are some additional actions that also need to be decided upon. You’ll want to work on allocating ownership of the project, figure out who will do what, how the success of the solution will be measured and decide the next course of action.

Set clear accountabilities, actions, timeframes, and follow-ups for your chosen solution. Make these decisions and set clear next-steps in the problem solving workshop so that everyone is aligned and you can move forward effectively as a group.

Ensuring that you plan for the roll-out of a solution is one of the most important problem solving steps. Without adequate planning or oversight, it can prove impossible to measure success or iterate further if the problem was not solved.

6. Solution implementation

This is what we were waiting for! All problem solving processes have the end goal of implementing an effective and impactful solution that your group has confidence in.

Project management and communication skills are key here – your solution may need to adjust when out in the wild or you might discover new challenges along the way. For some solutions, you might also implement a test with a small group and monitor results before rolling it out to an entire company.

You should have a clear owner for your solution who will oversee the plans you made together and help ensure they’re put into place. This person will often coordinate the implementation team and set-up processes to measure the efficacy of your solution too.

7. Solution evaluation

So you and your team developed a great solution to a problem and have a gut feeling it’s been solved. Work done, right? Wrong. All problem solving strategies benefit from evaluation, consideration, and feedback.

You might find that the solution does not work for everyone, might create new problems, or is potentially so successful that you will want to roll it out to larger teams or as part of other initiatives.

None of that is possible without taking the time to evaluate the success of the solution you developed in your problem solving model and adjust if necessary.

Remember that the problem solving process is often iterative and it can be common to not solve complex issues on the first try. Even when this is the case, you and your team will have generated learning that will be important for future problem solving workshops or in other parts of the organization.

It’s also worth underlining how important record keeping is throughout the problem solving process. If a solution didn’t work, you need to have the data and records to see why that was the case. If you go back to the drawing board, notes from the previous workshop can help save time.

What does an effective problem solving process look like?

Every effective problem solving process begins with an agenda . In our experience, a well-structured problem solving workshop is one of the best methods for successfully guiding a group from exploring a problem to implementing a solution.

The format of a workshop ensures that you can get buy-in from your group, encourage free-thinking and solution exploration before making a decision on what to implement following the session.

This Design Sprint 2.0 template is an effective problem solving process from top agency AJ&Smart. It’s a great format for the entire problem solving process, with four-days of workshops designed to surface issues, explore solutions and even test a solution.

Check it for an example of how you might structure and run a problem solving process and feel free to copy and adjust it your needs!

For a shorter process you can run in a single afternoon, this remote problem solving agenda will guide you effectively in just a couple of hours.

Whatever the length of your workshop, by using SessionLab, it’s easy to go from an idea to a complete agenda . Start by dragging and dropping your core problem solving activities into place . Add timings, breaks and necessary materials before sharing your agenda with your colleagues.

The resulting agenda will be your guide to an effective and productive problem solving session that will also help you stay organized on the day!

Complete problem-solving methods

In this section, we’ll look at in-depth problem-solving methods that provide a complete end-to-end process for developing effective solutions. These will help guide your team from the discovery and definition of a problem through to delivering the right solution.

If you’re looking for an all-encompassing method or problem-solving model, these processes are a great place to start. They’ll ask your team to challenge preconceived ideas and adopt a mindset for solving problems more effectively.

Six Thinking Hats

Individual approaches to solving a problem can be very different based on what team or role an individual holds. It can be easy for existing biases or perspectives to find their way into the mix, or for internal politics to direct a conversation.

Six Thinking Hats is a classic method for identifying the problems that need to be solved and enables your team to consider them from different angles, whether that is by focusing on facts and data, creative solutions, or by considering why a particular solution might not work.

Like all problem-solving frameworks, Six Thinking Hats is effective at helping teams remove roadblocks from a conversation or discussion and come to terms with all the aspects necessary to solve complex problems.

The Six Thinking Hats #creative thinking #meeting facilitation #problem solving #issue resolution #idea generation #conflict resolution The Six Thinking Hats are used by individuals and groups to separate out conflicting styles of thinking. They enable and encourage a group of people to think constructively together in exploring and implementing change, rather than using argument to fight over who is right and who is wrong.

Lightning Decision Jam

Featured courtesy of Jonathan Courtney of AJ&Smart Berlin, Lightning Decision Jam is one of those strategies that should be in every facilitation toolbox. Exploring problems and finding solutions is often creative in nature, though as with any creative process, there is the potential to lose focus and get lost.

Unstructured discussions might get you there in the end, but it’s much more effective to use a method that creates a clear process and team focus.

In Lightning Decision Jam, participants are invited to begin by writing challenges, concerns, or mistakes on post-its without discussing them before then being invited by the moderator to present them to the group.

From there, the team vote on which problems to solve and are guided through steps that will allow them to reframe those problems, create solutions and then decide what to execute on.

By deciding the problems that need to be solved as a team before moving on, this group process is great for ensuring the whole team is aligned and can take ownership over the next stages.

Lightning Decision Jam (LDJ) #action #decision making #problem solving #issue analysis #innovation #design #remote-friendly It doesn’t matter where you work and what your job role is, if you work with other people together as a team, you will always encounter the same challenges: Unclear goals and miscommunication that cause busy work and overtime Unstructured meetings that leave attendants tired, confused and without clear outcomes. Frustration builds up because internal challenges to productivity are not addressed Sudden changes in priorities lead to a loss of focus and momentum Muddled compromise takes the place of clear decision- making, leaving everybody to come up with their own interpretation. In short, a lack of structure leads to a waste of time and effort, projects that drag on for too long and frustrated, burnt out teams. AJ&Smart has worked with some of the most innovative, productive companies in the world. What sets their teams apart from others is not better tools, bigger talent or more beautiful offices. The secret sauce to becoming a more productive, more creative and happier team is simple: Replace all open discussion or brainstorming with a structured process that leads to more ideas, clearer decisions and better outcomes. When a good process provides guardrails and a clear path to follow, it becomes easier to come up with ideas, make decisions and solve problems. This is why AJ&Smart created Lightning Decision Jam (LDJ). It’s a simple and short, but powerful group exercise that can be run either in-person, in the same room, or remotely with distributed teams.

Problem Definition Process

While problems can be complex, the problem-solving methods you use to identify and solve those problems can often be simple in design.

By taking the time to truly identify and define a problem before asking the group to reframe the challenge as an opportunity, this method is a great way to enable change.

Begin by identifying a focus question and exploring the ways in which it manifests before splitting into five teams who will each consider the problem using a different method: escape, reversal, exaggeration, distortion or wishful. Teams develop a problem objective and create ideas in line with their method before then feeding them back to the group.

This method is great for enabling in-depth discussions while also creating space for finding creative solutions too!

Problem Definition #problem solving #idea generation #creativity #online #remote-friendly A problem solving technique to define a problem, challenge or opportunity and to generate ideas.

The 5 Whys

Sometimes, a group needs to go further with their strategies and analyze the root cause at the heart of organizational issues. An RCA or root cause analysis is the process of identifying what is at the heart of business problems or recurring challenges.

The 5 Whys is a simple and effective method of helping a group go find the root cause of any problem or challenge and conduct analysis that will deliver results.

By beginning with the creation of a problem statement and going through five stages to refine it, The 5 Whys provides everything you need to truly discover the cause of an issue.

The 5 Whys #hyperisland #innovation This simple and powerful method is useful for getting to the core of a problem or challenge. As the title suggests, the group defines a problems, then asks the question “why” five times, often using the resulting explanation as a starting point for creative problem solving.

World Cafe is a simple but powerful facilitation technique to help bigger groups to focus their energy and attention on solving complex problems.

World Cafe enables this approach by creating a relaxed atmosphere where participants are able to self-organize and explore topics relevant and important to them which are themed around a central problem-solving purpose. Create the right atmosphere by modeling your space after a cafe and after guiding the group through the method, let them take the lead!

Making problem-solving a part of your organization’s culture in the long term can be a difficult undertaking. More approachable formats like World Cafe can be especially effective in bringing people unfamiliar with workshops into the fold.

World Cafe #hyperisland #innovation #issue analysis World Café is a simple yet powerful method, originated by Juanita Brown, for enabling meaningful conversations driven completely by participants and the topics that are relevant and important to them. Facilitators create a cafe-style space and provide simple guidelines. Participants then self-organize and explore a set of relevant topics or questions for conversation.

Discovery & Action Dialogue (DAD)

One of the best approaches is to create a safe space for a group to share and discover practices and behaviors that can help them find their own solutions.

With DAD, you can help a group choose which problems they wish to solve and which approaches they will take to do so. It’s great at helping remove resistance to change and can help get buy-in at every level too!

This process of enabling frontline ownership is great in ensuring follow-through and is one of the methods you will want in your toolbox as a facilitator.

Discovery & Action Dialogue (DAD) #idea generation #liberating structures #action #issue analysis #remote-friendly DADs make it easy for a group or community to discover practices and behaviors that enable some individuals (without access to special resources and facing the same constraints) to find better solutions than their peers to common problems. These are called positive deviant (PD) behaviors and practices. DADs make it possible for people in the group, unit, or community to discover by themselves these PD practices. DADs also create favorable conditions for stimulating participants’ creativity in spaces where they can feel safe to invent new and more effective practices. Resistance to change evaporates as participants are unleashed to choose freely which practices they will adopt or try and which problems they will tackle. DADs make it possible to achieve frontline ownership of solutions.

Design Sprint 2.0

Want to see how a team can solve big problems and move forward with prototyping and testing solutions in a few days? The Design Sprint 2.0 template from Jake Knapp, author of Sprint, is a complete agenda for a with proven results.

Developing the right agenda can involve difficult but necessary planning. Ensuring all the correct steps are followed can also be stressful or time-consuming depending on your level of experience.

Use this complete 4-day workshop template if you are finding there is no obvious solution to your challenge and want to focus your team around a specific problem that might require a shortcut to launching a minimum viable product or waiting for the organization-wide implementation of a solution.

Open space technology

Open space technology- developed by Harrison Owen – creates a space where large groups are invited to take ownership of their problem solving and lead individual sessions. Open space technology is a great format when you have a great deal of expertise and insight in the room and want to allow for different takes and approaches on a particular theme or problem you need to be solved.

Start by bringing your participants together to align around a central theme and focus their efforts. Explain the ground rules to help guide the problem-solving process and then invite members to identify any issue connecting to the central theme that they are interested in and are prepared to take responsibility for.

Once participants have decided on their approach to the core theme, they write their issue on a piece of paper, announce it to the group, pick a session time and place, and post the paper on the wall. As the wall fills up with sessions, the group is then invited to join the sessions that interest them the most and which they can contribute to, then you’re ready to begin!

Everyone joins the problem-solving group they’ve signed up to, record the discussion and if appropriate, findings can then be shared with the rest of the group afterward.

Open Space Technology #action plan #idea generation #problem solving #issue analysis #large group #online #remote-friendly Open Space is a methodology for large groups to create their agenda discerning important topics for discussion, suitable for conferences, community gatherings and whole system facilitation

Techniques to identify and analyze problems

Using a problem-solving method to help a team identify and analyze a problem can be a quick and effective addition to any workshop or meeting.

While further actions are always necessary, you can generate momentum and alignment easily, and these activities are a great place to get started.

We’ve put together this list of techniques to help you and your team with problem identification, analysis, and discussion that sets the foundation for developing effective solutions.

Let’s take a look!

Fishbone Analysis

Organizational or team challenges are rarely simple, and it’s important to remember that one problem can be an indication of something that goes deeper and may require further consideration to be solved.

Fishbone Analysis helps groups to dig deeper and understand the origins of a problem. It’s a great example of a root cause analysis method that is simple for everyone on a team to get their head around.

Participants in this activity are asked to annotate a diagram of a fish, first adding the problem or issue to be worked on at the head of a fish before then brainstorming the root causes of the problem and adding them as bones on the fish.

Using abstractions such as a diagram of a fish can really help a team break out of their regular thinking and develop a creative approach.

Fishbone Analysis #problem solving ##root cause analysis #decision making #online facilitation A process to help identify and understand the origins of problems, issues or observations.

Problem Tree

Encouraging visual thinking can be an essential part of many strategies. By simply reframing and clarifying problems, a group can move towards developing a problem solving model that works for them.

In Problem Tree, groups are asked to first brainstorm a list of problems – these can be design problems, team problems or larger business problems – and then organize them into a hierarchy. The hierarchy could be from most important to least important or abstract to practical, though the key thing with problem solving games that involve this aspect is that your group has some way of managing and sorting all the issues that are raised.

Once you have a list of problems that need to be solved and have organized them accordingly, you’re then well-positioned for the next problem solving steps.

Problem tree #define intentions #create #design #issue analysis A problem tree is a tool to clarify the hierarchy of problems addressed by the team within a design project; it represents high level problems or related sublevel problems.

SWOT Analysis

Chances are you’ve heard of the SWOT Analysis before. This problem-solving method focuses on identifying strengths, weaknesses, opportunities, and threats is a tried and tested method for both individuals and teams.

Start by creating a desired end state or outcome and bare this in mind – any process solving model is made more effective by knowing what you are moving towards. Create a quadrant made up of the four categories of a SWOT analysis and ask participants to generate ideas based on each of those quadrants.

Once you have those ideas assembled in their quadrants, cluster them together based on their affinity with other ideas. These clusters are then used to facilitate group conversations and move things forward.

SWOT analysis #gamestorming #problem solving #action #meeting facilitation The SWOT Analysis is a long-standing technique of looking at what we have, with respect to the desired end state, as well as what we could improve on. It gives us an opportunity to gauge approaching opportunities and dangers, and assess the seriousness of the conditions that affect our future. When we understand those conditions, we can influence what comes next.

Agreement-Certainty Matrix

Not every problem-solving approach is right for every challenge, and deciding on the right method for the challenge at hand is a key part of being an effective team.

The Agreement Certainty matrix helps teams align on the nature of the challenges facing them. By sorting problems from simple to chaotic, your team can understand what methods are suitable for each problem and what they can do to ensure effective results.

If you are already using Liberating Structures techniques as part of your problem-solving strategy, the Agreement-Certainty Matrix can be an invaluable addition to your process. We’ve found it particularly if you are having issues with recurring problems in your organization and want to go deeper in understanding the root cause.

Agreement-Certainty Matrix #issue analysis #liberating structures #problem solving You can help individuals or groups avoid the frequent mistake of trying to solve a problem with methods that are not adapted to the nature of their challenge. The combination of two questions makes it possible to easily sort challenges into four categories: simple, complicated, complex , and chaotic . A problem is simple when it can be solved reliably with practices that are easy to duplicate. It is complicated when experts are required to devise a sophisticated solution that will yield the desired results predictably. A problem is complex when there are several valid ways to proceed but outcomes are not predictable in detail. Chaotic is when the context is too turbulent to identify a path forward. A loose analogy may be used to describe these differences: simple is like following a recipe, complicated like sending a rocket to the moon, complex like raising a child, and chaotic is like the game “Pin the Tail on the Donkey.” The Liberating Structures Matching Matrix in Chapter 5 can be used as the first step to clarify the nature of a challenge and avoid the mismatches between problems and solutions that are frequently at the root of chronic, recurring problems.

Organizing and charting a team’s progress can be important in ensuring its success. SQUID (Sequential Question and Insight Diagram) is a great model that allows a team to effectively switch between giving questions and answers and develop the skills they need to stay on track throughout the process.

Begin with two different colored sticky notes – one for questions and one for answers – and with your central topic (the head of the squid) on the board. Ask the group to first come up with a series of questions connected to their best guess of how to approach the topic. Ask the group to come up with answers to those questions, fix them to the board and connect them with a line. After some discussion, go back to question mode by responding to the generated answers or other points on the board.

It’s rewarding to see a diagram grow throughout the exercise, and a completed SQUID can provide a visual resource for future effort and as an example for other teams.

SQUID #gamestorming #project planning #issue analysis #problem solving When exploring an information space, it’s important for a group to know where they are at any given time. By using SQUID, a group charts out the territory as they go and can navigate accordingly. SQUID stands for Sequential Question and Insight Diagram.

To continue with our nautical theme, Speed Boat is a short and sweet activity that can help a team quickly identify what employees, clients or service users might have a problem with and analyze what might be standing in the way of achieving a solution.

Methods that allow for a group to make observations, have insights and obtain those eureka moments quickly are invaluable when trying to solve complex problems.

In Speed Boat, the approach is to first consider what anchors and challenges might be holding an organization (or boat) back. Bonus points if you are able to identify any sharks in the water and develop ideas that can also deal with competitors!

Speed Boat #gamestorming #problem solving #action Speedboat is a short and sweet way to identify what your employees or clients don’t like about your product/service or what’s standing in the way of a desired goal.

The Journalistic Six

Some of the most effective ways of solving problems is by encouraging teams to be more inclusive and diverse in their thinking.

Based on the six key questions journalism students are taught to answer in articles and news stories, The Journalistic Six helps create teams to see the whole picture. By using who, what, when, where, why, and how to facilitate the conversation and encourage creative thinking, your team can make sure that the problem identification and problem analysis stages of the are covered exhaustively and thoughtfully. Reporter’s notebook and dictaphone optional.

The Journalistic Six – Who What When Where Why How #idea generation #issue analysis #problem solving #online #creative thinking #remote-friendly A questioning method for generating, explaining, investigating ideas.

Individual and group perspectives are incredibly important, but what happens if people are set in their minds and need a change of perspective in order to approach a problem more effectively?

Flip It is a method we love because it is both simple to understand and run, and allows groups to understand how their perspectives and biases are formed.

Participants in Flip It are first invited to consider concerns, issues, or problems from a perspective of fear and write them on a flip chart. Then, the group is asked to consider those same issues from a perspective of hope and flip their understanding.

No problem and solution is free from existing bias and by changing perspectives with Flip It, you can then develop a problem solving model quickly and effectively.

Flip It! #gamestorming #problem solving #action Often, a change in a problem or situation comes simply from a change in our perspectives. Flip It! is a quick game designed to show players that perspectives are made, not born.

LEGO Challenge

Now for an activity that is a little out of the (toy) box. LEGO Serious Play is a facilitation methodology that can be used to improve creative thinking and problem-solving skills.

The LEGO Challenge includes giving each member of the team an assignment that is hidden from the rest of the group while they create a structure without speaking.

What the LEGO challenge brings to the table is a fun working example of working with stakeholders who might not be on the same page to solve problems. Also, it’s LEGO! Who doesn’t love LEGO!

LEGO Challenge #hyperisland #team A team-building activity in which groups must work together to build a structure out of LEGO, but each individual has a secret “assignment” which makes the collaborative process more challenging. It emphasizes group communication, leadership dynamics, conflict, cooperation, patience and problem solving strategy.

What, So What, Now What?

If not carefully managed, the problem identification and problem analysis stages of the problem-solving process can actually create more problems and misunderstandings.

The What, So What, Now What? problem-solving activity is designed to help collect insights and move forward while also eliminating the possibility of disagreement when it comes to identifying, clarifying, and analyzing organizational or work problems.

Facilitation is all about bringing groups together so that might work on a shared goal and the best problem-solving strategies ensure that teams are aligned in purpose, if not initially in opinion or insight.

Throughout the three steps of this game, you give everyone on a team to reflect on a problem by asking what happened, why it is important, and what actions should then be taken.

This can be a great activity for bringing our individual perceptions about a problem or challenge and contextualizing it in a larger group setting. This is one of the most important problem-solving skills you can bring to your organization.

W³ – What, So What, Now What? #issue analysis #innovation #liberating structures You can help groups reflect on a shared experience in a way that builds understanding and spurs coordinated action while avoiding unproductive conflict. It is possible for every voice to be heard while simultaneously sifting for insights and shaping new direction. Progressing in stages makes this practical—from collecting facts about What Happened to making sense of these facts with So What and finally to what actions logically follow with Now What . The shared progression eliminates most of the misunderstandings that otherwise fuel disagreements about what to do. Voila!

Journalists

Problem analysis can be one of the most important and decisive stages of all problem-solving tools. Sometimes, a team can become bogged down in the details and are unable to move forward.

Journalists is an activity that can avoid a group from getting stuck in the problem identification or problem analysis stages of the process.

In Journalists, the group is invited to draft the front page of a fictional newspaper and figure out what stories deserve to be on the cover and what headlines those stories will have. By reframing how your problems and challenges are approached, you can help a team move productively through the process and be better prepared for the steps to follow.

Journalists #vision #big picture #issue analysis #remote-friendly This is an exercise to use when the group gets stuck in details and struggles to see the big picture. Also good for defining a vision.

Problem-solving techniques for brainstorming solutions

Now you have the context and background of the problem you are trying to solving, now comes the time to start ideating and thinking about how you’ll solve the issue.

Here, you’ll want to encourage creative, free thinking and speed. Get as many ideas out as possible and explore different perspectives so you have the raw material for the next step.

Looking at a problem from a new angle can be one of the most effective ways of creating an effective solution. TRIZ is a problem-solving tool that asks the group to consider what they must not do in order to solve a challenge.

By reversing the discussion, new topics and taboo subjects often emerge, allowing the group to think more deeply and create ideas that confront the status quo in a safe and meaningful way. If you’re working on a problem that you’ve tried to solve before, TRIZ is a great problem-solving method to help your team get unblocked.

Making Space with TRIZ #issue analysis #liberating structures #issue resolution You can clear space for innovation by helping a group let go of what it knows (but rarely admits) limits its success and by inviting creative destruction. TRIZ makes it possible to challenge sacred cows safely and encourages heretical thinking. The question “What must we stop doing to make progress on our deepest purpose?” induces seriously fun yet very courageous conversations. Since laughter often erupts, issues that are otherwise taboo get a chance to be aired and confronted. With creative destruction come opportunities for renewal as local action and innovation rush in to fill the vacuum. Whoosh!

Mindspin

Brainstorming is part of the bread and butter of the problem-solving process and all problem-solving strategies benefit from getting ideas out and challenging a team to generate solutions quickly.

With Mindspin, participants are encouraged not only to generate ideas but to do so under time constraints and by slamming down cards and passing them on. By doing multiple rounds, your team can begin with a free generation of possible solutions before moving on to developing those solutions and encouraging further ideation.

This is one of our favorite problem-solving activities and can be great for keeping the energy up throughout the workshop. Remember the importance of helping people become engaged in the process – energizing problem-solving techniques like Mindspin can help ensure your team stays engaged and happy, even when the problems they’re coming together to solve are complex.

MindSpin #teampedia #idea generation #problem solving #action A fast and loud method to enhance brainstorming within a team. Since this activity has more than round ideas that are repetitive can be ruled out leaving more creative and innovative answers to the challenge.

The Creativity Dice

One of the most useful problem solving skills you can teach your team is of approaching challenges with creativity, flexibility, and openness. Games like The Creativity Dice allow teams to overcome the potential hurdle of too much linear thinking and approach the process with a sense of fun and speed.

In The Creativity Dice, participants are organized around a topic and roll a dice to determine what they will work on for a period of 3 minutes at a time. They might roll a 3 and work on investigating factual information on the chosen topic. They might roll a 1 and work on identifying the specific goals, standards, or criteria for the session.

Encouraging rapid work and iteration while asking participants to be flexible are great skills to cultivate. Having a stage for idea incubation in this game is also important. Moments of pause can help ensure the ideas that are put forward are the most suitable.

The Creativity Dice #creativity #problem solving #thiagi #issue analysis Too much linear thinking is hazardous to creative problem solving. To be creative, you should approach the problem (or the opportunity) from different points of view. You should leave a thought hanging in mid-air and move to another. This skipping around prevents premature closure and lets your brain incubate one line of thought while you consciously pursue another.

Idea and Concept Development

Brainstorming without structure can quickly become chaotic or frustrating. In a problem-solving context, having an ideation framework to follow can help ensure your team is both creative and disciplined.

In this method, you’ll find an idea generation process that encourages your group to brainstorm effectively before developing their ideas and begin clustering them together. By using concepts such as Yes and…, more is more and postponing judgement, you can create the ideal conditions for brainstorming with ease.

Idea & Concept Development #hyperisland #innovation #idea generation Ideation and Concept Development is a process for groups to work creatively and collaboratively to generate creative ideas. It’s a general approach that can be adapted and customized to suit many different scenarios. It includes basic principles for idea generation and several steps for groups to work with. It also includes steps for idea selection and development.

Problem-solving techniques for developing and refining solutions

The success of any problem-solving process can be measured by the solutions it produces. After you’ve defined the issue, explored existing ideas, and ideated, it’s time to develop and refine your ideas in order to bring them closer to a solution that actually solves the problem.

Use these problem-solving techniques when you want to help your team think through their ideas and refine them as part of your problem solving process.

Improved Solutions

After a team has successfully identified a problem and come up with a few solutions, it can be tempting to call the work of the problem-solving process complete. That said, the first solution is not necessarily the best, and by including a further review and reflection activity into your problem-solving model, you can ensure your group reaches the best possible result.

One of a number of problem-solving games from Thiagi Group, Improved Solutions helps you go the extra mile and develop suggested solutions with close consideration and peer review. By supporting the discussion of several problems at once and by shifting team roles throughout, this problem-solving technique is a dynamic way of finding the best solution.

Improved Solutions #creativity #thiagi #problem solving #action #team You can improve any solution by objectively reviewing its strengths and weaknesses and making suitable adjustments. In this creativity framegame, you improve the solutions to several problems. To maintain objective detachment, you deal with a different problem during each of six rounds and assume different roles (problem owner, consultant, basher, booster, enhancer, and evaluator) during each round. At the conclusion of the activity, each player ends up with two solutions to her problem.

Four Step Sketch

Creative thinking and visual ideation does not need to be confined to the opening stages of your problem-solving strategies. Exercises that include sketching and prototyping on paper can be effective at the solution finding and development stage of the process, and can be great for keeping a team engaged.

By going from simple notes to a crazy 8s round that involves rapidly sketching 8 variations on their ideas before then producing a final solution sketch, the group is able to iterate quickly and visually. Problem-solving techniques like Four-Step Sketch are great if you have a group of different thinkers and want to change things up from a more textual or discussion-based approach.

Four-Step Sketch #design sprint #innovation #idea generation #remote-friendly The four-step sketch is an exercise that helps people to create well-formed concepts through a structured process that includes: Review key information Start design work on paper, Consider multiple variations , Create a detailed solution . This exercise is preceded by a set of other activities allowing the group to clarify the challenge they want to solve. See how the Four Step Sketch exercise fits into a Design Sprint

Ensuring that everyone in a group is able to contribute to a discussion is vital during any problem solving process. Not only does this ensure all bases are covered, but its then easier to get buy-in and accountability when people have been able to contribute to the process.

1-2-4-All is a tried and tested facilitation technique where participants are asked to first brainstorm on a topic on their own. Next, they discuss and share ideas in a pair before moving into a small group. Those groups are then asked to present the best idea from their discussion to the rest of the team.

This method can be used in many different contexts effectively, though I find it particularly shines in the idea development stage of the process. Giving each participant time to concretize their ideas and develop them in progressively larger groups can create a great space for both innovation and psychological safety.

1-2-4-All #idea generation #liberating structures #issue analysis With this facilitation technique you can immediately include everyone regardless of how large the group is. You can generate better ideas and more of them faster than ever before. You can tap the know-how and imagination that is distributed widely in places not known in advance. Open, generative conversation unfolds. Ideas and solutions are sifted in rapid fashion. Most importantly, participants own the ideas, so follow-up and implementation is simplified. No buy-in strategies needed! Simple and elegant!

15% Solutions

Some problems are simpler than others and with the right problem-solving activities, you can empower people to take immediate actions that can help create organizational change.

Part of the liberating structures toolkit, 15% solutions is a problem-solving technique that focuses on finding and implementing solutions quickly. A process of iterating and making small changes quickly can help generate momentum and an appetite for solving complex problems.

Problem-solving strategies can live and die on whether people are onboard. Getting some quick wins is a great way of getting people behind the process.

It can be extremely empowering for a team to realize that problem-solving techniques can be deployed quickly and easily and delineate between things they can positively impact and those things they cannot change.

15% Solutions #action #liberating structures #remote-friendly You can reveal the actions, however small, that everyone can do immediately. At a minimum, these will create momentum, and that may make a BIG difference. 15% Solutions show that there is no reason to wait around, feel powerless, or fearful. They help people pick it up a level. They get individuals and the group to focus on what is within their discretion instead of what they cannot change. With a very simple question, you can flip the conversation to what can be done and find solutions to big problems that are often distributed widely in places not known in advance. Shifting a few grains of sand may trigger a landslide and change the whole landscape.

Problem-solving techniques for making decisions and planning

After your group is happy with the possible solutions you’ve developed, now comes the time to choose which to implement. There’s more than one way to make a decision and the best option is often dependant on the needs and set-up of your group.

Sometimes, it’s the case that you’ll want to vote as a group on what is likely to be the most impactful solution. Other times, it might be down to a decision maker or major stakeholder to make the final decision. Whatever your process, here’s some techniques you can use to help you make a decision during your problem solving process.

How-Now-Wow Matrix

The problem-solving process is often creative, as complex problems usually require a change of thinking and creative response in order to find the best solutions. While it’s common for the first stages to encourage creative thinking, groups can often gravitate to familiar solutions when it comes to the end of the process.

When selecting solutions, you don’t want to lose your creative energy! The How-Now-Wow Matrix from Gamestorming is a great problem-solving activity that enables a group to stay creative and think out of the box when it comes to selecting the right solution for a given problem.

Problem-solving techniques that encourage creative thinking and the ideation and selection of new solutions can be the most effective in organisational change. Give the How-Now-Wow Matrix a go, and not just for how pleasant it is to say out loud.

How-Now-Wow Matrix #gamestorming #idea generation #remote-friendly When people want to develop new ideas, they most often think out of the box in the brainstorming or divergent phase. However, when it comes to convergence, people often end up picking ideas that are most familiar to them. This is called a ‘creative paradox’ or a ‘creadox’. The How-Now-Wow matrix is an idea selection tool that breaks the creadox by forcing people to weigh each idea on 2 parameters.

Impact and Effort Matrix

All problem-solving techniques hope to not only find solutions to a given problem or challenge but to find the best solution. When it comes to finding a solution, groups are invited to put on their decision-making hats and really think about how a proposed idea would work in practice.

The Impact and Effort Matrix is one of the problem-solving techniques that fall into this camp, empowering participants to first generate ideas and then categorize them into a 2×2 matrix based on impact and effort.

Activities that invite critical thinking while remaining simple are invaluable. Use the Impact and Effort Matrix to move from ideation and towards evaluating potential solutions before then committing to them.

Impact and Effort Matrix #gamestorming #decision making #action #remote-friendly In this decision-making exercise, possible actions are mapped based on two factors: effort required to implement and potential impact. Categorizing ideas along these lines is a useful technique in decision making, as it obliges contributors to balance and evaluate suggested actions before committing to them.

If you’ve followed each of the problem-solving steps with your group successfully, you should move towards the end of your process with heaps of possible solutions developed with a specific problem in mind. But how do you help a group go from ideation to putting a solution into action?

Dotmocracy – or Dot Voting -is a tried and tested method of helping a team in the problem-solving process make decisions and put actions in place with a degree of oversight and consensus.

One of the problem-solving techniques that should be in every facilitator’s toolbox, Dot Voting is fast and effective and can help identify the most popular and best solutions and help bring a group to a decision effectively.

Dotmocracy #action #decision making #group prioritization #hyperisland #remote-friendly Dotmocracy is a simple method for group prioritization or decision-making. It is not an activity on its own, but a method to use in processes where prioritization or decision-making is the aim. The method supports a group to quickly see which options are most popular or relevant. The options or ideas are written on post-its and stuck up on a wall for the whole group to see. Each person votes for the options they think are the strongest, and that information is used to inform a decision.

Straddling the gap between decision making and planning, MoSCoW is a simple and effective method that allows a group team to easily prioritize a set of possible options.

Use this method in a problem solving process by collecting and summarizing all your possible solutions and then categorize them into 4 sections: “Must have”, “Should have”, “Could have”, or “Would like but won‘t get”.

This method is particularly useful when its less about choosing one possible solution and more about prioritorizing which to do first and which may not fit in the scope of your project. In my experience, complex challenges often require multiple small fixes, and this method can be a great way to move from a pile of things you’d all like to do to a structured plan.

MoSCoW #define intentions #create #design #action #remote-friendly MoSCoW is a method that allows the team to prioritize the different features that they will work on. Features are then categorized into “Must have”, “Should have”, “Could have”, or “Would like but won‘t get”. To be used at the beginning of a timeslot (for example during Sprint planning) and when planning is needed.

When it comes to managing the rollout of a solution, clarity and accountability are key factors in ensuring the success of the project. The RAACI chart is a simple but effective model for setting roles and responsibilities as part of a planning session.

Start by listing each person involved in the project and put them into the following groups in order to make it clear who is responsible for what during the rollout of your solution.

Responsibility (Which person and/or team will be taking action?)
Authority (At what “point” must the responsible person check in before going further?)
Accountability (Who must the responsible person check in with?)
Consultation (Who must be consulted by the responsible person before decisions are made?)
Information (Who must be informed of decisions, once made?)

Ensure this information is easily accessible and use it to inform who does what and who is looped into discussions and kept up to date.

RAACI #roles and responsibility #teamwork #project management Clarifying roles and responsibilities, levels of autonomy/latitude in decision making, and levels of engagement among diverse stakeholders.

Problem-solving warm-up activities

All facilitators know that warm-ups and icebreakers are useful for any workshop or group process. Problem-solving workshops are no different.

Use these problem-solving techniques to warm up a group and prepare them for the rest of the process. Activating your group by tapping into some of the top problem-solving skills can be one of the best ways to see great outcomes from your session.

Check-in / Check-out

Solid processes are planned from beginning to end, and the best facilitators know that setting the tone and establishing a safe, open environment can be integral to a successful problem-solving process. Check-in / Check-out is a great way to begin and/or bookend a problem-solving workshop. Checking in to a session emphasizes that everyone will be seen, heard, and expected to contribute.

If you are running a series of meetings, setting a consistent pattern of checking in and checking out can really help your team get into a groove. We recommend this opening-closing activity for small to medium-sized groups though it can work with large groups if they’re disciplined!

Check-in / Check-out #team #opening #closing #hyperisland #remote-friendly Either checking-in or checking-out is a simple way for a team to open or close a process, symbolically and in a collaborative way. Checking-in/out invites each member in a group to be present, seen and heard, and to express a reflection or a feeling. Checking-in emphasizes presence, focus and group commitment; checking-out emphasizes reflection and symbolic closure.

Doodling Together

Thinking creatively and not being afraid to make suggestions are important problem-solving skills for any group or team, and warming up by encouraging these behaviors is a great way to start.

Doodling Together is one of our favorite creative ice breaker games – it’s quick, effective, and fun and can make all following problem-solving steps easier by encouraging a group to collaborate visually. By passing cards and adding additional items as they go, the workshop group gets into a groove of co-creation and idea development that is crucial to finding solutions to problems.

Doodling Together #collaboration #creativity #teamwork #fun #team #visual methods #energiser #icebreaker #remote-friendly Create wild, weird and often funny postcards together & establish a group’s creative confidence.

Show and Tell

You might remember some version of Show and Tell from being a kid in school and it’s a great problem-solving activity to kick off a session.

Asking participants to prepare a little something before a workshop by bringing an object for show and tell can help them warm up before the session has even begun! Games that include a physical object can also help encourage early engagement before moving onto more big-picture thinking.

By asking your participants to tell stories about why they chose to bring a particular item to the group, you can help teams see things from new perspectives and see both differences and similarities in the way they approach a topic. Great groundwork for approaching a problem-solving process as a team!

Show and Tell #gamestorming #action #opening #meeting facilitation Show and Tell taps into the power of metaphors to reveal players’ underlying assumptions and associations around a topic The aim of the game is to get a deeper understanding of stakeholders’ perspectives on anything—a new project, an organizational restructuring, a shift in the company’s vision or team dynamic.

Constellations

Who doesn’t love stars? Constellations is a great warm-up activity for any workshop as it gets people up off their feet, energized, and ready to engage in new ways with established topics. It’s also great for showing existing beliefs, biases, and patterns that can come into play as part of your session.

Using warm-up games that help build trust and connection while also allowing for non-verbal responses can be great for easing people into the problem-solving process and encouraging engagement from everyone in the group. Constellations is great in large spaces that allow for movement and is definitely a practical exercise to allow the group to see patterns that are otherwise invisible.

Constellations #trust #connection #opening #coaching #patterns #system Individuals express their response to a statement or idea by standing closer or further from a central object. Used with teams to reveal system, hidden patterns, perspectives.

Draw a Tree

Problem-solving games that help raise group awareness through a central, unifying metaphor can be effective ways to warm-up a group in any problem-solving model.

Draw a Tree is a simple warm-up activity you can use in any group and which can provide a quick jolt of energy. Start by asking your participants to draw a tree in just 45 seconds – they can choose whether it will be abstract or realistic.

Once the timer is up, ask the group how many people included the roots of the tree and use this as a means to discuss how we can ignore important parts of any system simply because they are not visible.

All problem-solving strategies are made more effective by thinking of problems critically and by exposing things that may not normally come to light. Warm-up games like Draw a Tree are great in that they quickly demonstrate some key problem-solving skills in an accessible and effective way.

Draw a Tree #thiagi #opening #perspectives #remote-friendly With this game you can raise awarness about being more mindful, and aware of the environment we live in.

Closing activities for a problem-solving process

Each step of the problem-solving workshop benefits from an intelligent deployment of activities, games, and techniques. Bringing your session to an effective close helps ensure that solutions are followed through on and that you also celebrate what has been achieved.

Here are some problem-solving activities you can use to effectively close a workshop or meeting and ensure the great work you’ve done can continue afterward.

One Breath Feedback

Maintaining attention and focus during the closing stages of a problem-solving workshop can be tricky and so being concise when giving feedback can be important. It’s easy to incur “death by feedback” should some team members go on for too long sharing their perspectives in a quick feedback round.

One Breath Feedback is a great closing activity for workshops. You give everyone an opportunity to provide feedback on what they’ve done but only in the space of a single breath. This keeps feedback short and to the point and means that everyone is encouraged to provide the most important piece of feedback to them.

One breath feedback #closing #feedback #action This is a feedback round in just one breath that excels in maintaining attention: each participants is able to speak during just one breath … for most people that’s around 20 to 25 seconds … unless of course you’ve been a deep sea diver in which case you’ll be able to do it for longer.

Who What When Matrix

Matrices feature as part of many effective problem-solving strategies and with good reason. They are easily recognizable, simple to use, and generate results.

The Who What When Matrix is a great tool to use when closing your problem-solving session by attributing a who, what and when to the actions and solutions you have decided upon. The resulting matrix is a simple, easy-to-follow way of ensuring your team can move forward.

Great solutions can’t be enacted without action and ownership. Your problem-solving process should include a stage for allocating tasks to individuals or teams and creating a realistic timeframe for those solutions to be implemented or checked out. Use this method to keep the solution implementation process clear and simple for all involved.

Who/What/When Matrix #gamestorming #action #project planning With Who/What/When matrix, you can connect people with clear actions they have defined and have committed to.

Response cards

Group discussion can comprise the bulk of most problem-solving activities and by the end of the process, you might find that your team is talked out!

Providing a means for your team to give feedback with short written notes can ensure everyone is head and can contribute without the need to stand up and talk. Depending on the needs of the group, giving an alternative can help ensure everyone can contribute to your problem-solving model in the way that makes the most sense for them.

Response Cards is a great way to close a workshop if you are looking for a gentle warm-down and want to get some swift discussion around some of the feedback that is raised.

Response Cards #debriefing #closing #structured sharing #questions and answers #thiagi #action It can be hard to involve everyone during a closing of a session. Some might stay in the background or get unheard because of louder participants. However, with the use of Response Cards, everyone will be involved in providing feedback or clarify questions at the end of a session.

Tips for effective problem solving

Problem-solving activities are only one part of the puzzle. While a great method can help unlock your team’s ability to solve problems, without a thoughtful approach and strong facilitation the solutions may not be fit for purpose.

Let’s take a look at some problem-solving tips you can apply to any process to help it be a success!

Clearly define the problem

Jumping straight to solutions can be tempting, though without first clearly articulating a problem, the solution might not be the right one. Many of the problem-solving activities below include sections where the problem is explored and clearly defined before moving on.

This is a vital part of the problem-solving process and taking the time to fully define an issue can save time and effort later. A clear definition helps identify irrelevant information and it also ensures that your team sets off on the right track.

Don’t jump to conclusions

It’s easy for groups to exhibit cognitive bias or have preconceived ideas about both problems and potential solutions. Be sure to back up any problem statements or potential solutions with facts, research, and adequate forethought.

The best techniques ask participants to be methodical and challenge preconceived notions. Make sure you give the group enough time and space to collect relevant information and consider the problem in a new way. By approaching the process with a clear, rational mindset, you’ll often find that better solutions are more forthcoming.

Try different approaches

Problems come in all shapes and sizes and so too should the methods you use to solve them. If you find that one approach isn’t yielding results and your team isn’t finding different solutions, try mixing it up. You’ll be surprised at how using a new creative activity can unblock your team and generate great solutions.

Don’t take it personally

Depending on the nature of your team or organizational problems, it’s easy for conversations to get heated. While it’s good for participants to be engaged in the discussions, ensure that emotions don’t run too high and that blame isn’t thrown around while finding solutions.

You’re all in it together, and even if your team or area is seeing problems, that isn’t necessarily a disparagement of you personally. Using facilitation skills to manage group dynamics is one effective method of helping conversations be more constructive.

Get the right people in the room

Your problem-solving method is often only as effective as the group using it. Getting the right people on the job and managing the number of people present is important too!

If the group is too small, you may not get enough different perspectives to effectively solve a problem. If the group is too large, you can go round and round during the ideation stages.

Creating the right group makeup is also important in ensuring you have the necessary expertise and skillset to both identify and follow up on potential solutions. Carefully consider who to include at each stage to help ensure your problem-solving method is followed and positioned for success.

Create psychologically safe spaces for discussion

Identifying a problem accurately also requires that all members of a group are able to contribute their views in an open and safe manner.

It can be tough for people to stand up and contribute if the problems or challenges are emotive or personal in nature. Try and create a psychologically safe space for these kinds of discussions and where possible, create regular opportunities for challenges to be brought up organically.

Document everything

The best solutions can take refinement, iteration, and reflection to come out. Get into a habit of documenting your process in order to keep all the learnings from the session and to allow ideas to mature and develop. Many of the methods below involve the creation of documents or shared resources. Be sure to keep and share these so everyone can benefit from the work done!

Bring a facilitator

Facilitation is all about making group processes easier. With a subject as potentially emotive and important as problem-solving, having an impartial third party in the form of a facilitator can make all the difference in finding great solutions and keeping the process moving. Consider bringing a facilitator to your problem-solving session to get better results and generate meaningful solutions!

Develop your problem-solving skills

It takes time and practice to be an effective problem solver. While some roles or participants might more naturally gravitate towards problem-solving, it can take development and planning to help everyone create better solutions.

You might develop a training program, run a problem-solving workshop or simply ask your team to practice using the techniques below. Check out our post on problem-solving skills to see how you and your group can develop the right mental process and be more resilient to issues too!

Design a great agenda

Workshops are a great format for solving problems. With the right approach, you can focus a group and help them find the solutions to their own problems. But designing a process can be time-consuming and finding the right activities can be difficult.

Check out our workshop planning guide to level-up your agenda design and start running more effective workshops. Need inspiration? Check out templates designed by expert facilitators to help you kickstart your process!

Save time and effort creating an effective problem solving process

A structured problem solving process is a surefire way of solving tough problems, discovering creative solutions and driving organizational change. But how can you design for successful outcomes?

With SessionLab, it’s easy to design engaging workshops that deliver results. Drag, drop and reorder blocks to build your agenda. When you make changes or update your agenda, your session timing adjusts automatically , saving you time on manual adjustments.

Collaborating with stakeholders or clients? Share your agenda with a single click and collaborate in real-time. No more sending documents back and forth over email.

Explore how to use SessionLab to design effective problem solving workshops or watch this five minute video to see the planner in action!

Over to you

The problem-solving process can often be as complicated and multifaceted as the problems they are set-up to solve. With the right problem-solving techniques and a mix of exercises designed to guide discussion and generate purposeful ideas, we hope we’ve given you the tools to find the best solutions as simply and easily as possible.

Is there a problem-solving technique that you are missing here? Do you have a favorite activity or method you use when facilitating? Let us know in the comments below, we’d love to hear from you!

James Smart is Head of Content at SessionLab. He’s also a creative facilitator who has run workshops and designed courses for establishments like the National Centre for Writing, UK. He especially enjoys working with young people and empowering others in their creative practice.

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

Your list of techniques for problem solving can be helpfully extended by adding TRIZ to the list of techniques. TRIZ has 40 problem solving techniques derived from methods inventros and patent holders used to get new patents. About 10-12 are general approaches. many organization sponsor classes in TRIZ that are used to solve business problems or general organiztational problems. You can take a look at TRIZ and dwonload a free internet booklet to see if you feel it shound be included per your selection process.

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Structured Problem-Solving

Available Topics
Top Documents
Recently Updated
Internal KB

Time and Effort
Instructor Prep Time	Medium
Student Activity Time	Medium
Instructor Response Time	Medium
Complexity of Activity	Medium
Room Considerations	Movable tables and chairs

Description

Structured Problem-Solving gives students a process for solving a complex, content-based problem within a specific time limit. All students must agree to a solution and be able to explain the answer and strategy used to solve the problem. The activity will help identify where students need to develop and/or improve their problem-solving skills.

Expand All | Collapse All

Use it when you want...

To break a problem-solving process into specific steps,
To have students identify, analyze, and solve problems in an organized manner,
To give students a structured format — preventing them from being overwhelmed by the magnitude of a problem or from engaging in irrelevant steps by providing manageable steps.

What students will need

There are no special requirements for this approach.

The following workflow is meant to guide you on how you can facilitate a Structured Problem-Solving learning activity within a classroom.

Create a problem that is complex enough to require students to use sophisticated problem-solving skills. Use research and current questions in the field as a resource.
Choose an identification and solving procedure appropriate to the selected problem type.
Solve the problem using the identified problem-solving procedure to uncover any difficulties or errors.
Create a handout that includes both the problem and the problem-solving steps.
Determine how groups will be formed.
Organize students into teams and assign them a complex problem to solve.
Ask students to use the specific steps you have identified as a problem-solving technique: (a) identify the problem; (b) generate possible solutions; (c) evaluate and test the various solutions; (d) decide on a mutually acceptable solution; (e) implement a plan, and (f) evaluate the results.
Teams report the steps they took and the solutions they developed.
Review reports.
Provide feedback/grades to group participants.
Discuss the results of the activity at the next class meeting.

Accessibility and Room Considerations

Technical documentation.

An Environmental Sciences professor wanted to use Structured Problem-Solving to consider the issue of air quality and air pollution. He divided students into teams and asked them to evaluate the air quality directly near the college. He asked them to consider, " What do you know? " and " Where can you go to find out? ". He then asked them to assess the air quality (recommending the environmental pollution scorecard) and to identify major and minor local and regional polluters. He also asked students to develop a presentation for community stakeholders that explained the problem and recommended specific actions (Barkley 245).

In General Chemistry , the professor developed a series of online modules to introduce concepts for the week. As an introductory course, she knew that few students would see how chemistry could be helpful in their everyday lives. She decided to use a Structured Problem-Solving activity in class to help them recognize where and how they interact with chemistry. She broke students into groups and asked them, " Select the best antacid from the list on the screen ." To help them get started, she gave them a problem-solving strategy in which they would respond to various questions that would help them identify the effectiveness of the antacid. The questions guided them to review the list of active ingredients. The questions also guided them to apply information on acids and bases found in the online modules. From the answers to these questions, groups designed an experiment to test the antacid. Each group presented their ideas to the class, the procedure they would follow, and the data they would collect. At the next class session, the professor had the materials to conduct their experiment to solve the problem and identify the best antacid available over the counter (Barkley 245-246).

Citation/Source

Barkley, Elizabeth F. et al. Collaborative Learning Techniques: A Handbook For College Faculty . Wiley, 2014. pp. 244-248.

Structured Problem-Solving (ALC)

Keywords	structured problem-solving, problem-solving, active learning, classroom ps	Doc ID	104146
Owner	Timmo D.	Group	Instructional Resources
Created	2020-07-20 10:12:24	Updated	2024-04-16 15:33:18
Sites	Center for Teaching, Learning & Mentoring
CleanURL
Feedback	2 0

A Step-by-Step Guide to A3 Problem Solving Methodology

Author: Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

Problem-solving is an important component of any business or organization. It entails identifying, analyzing, and resolving problems in order to improve processes, drive results, and foster a culture of continuous improvement. A3 Problem solving is one of the most effective problem-solving methodologies.

A3 Problem solving is a structured and systematic approach to problem-solving that originated with the lean manufacturing methodology. It visualizes the problem-solving process using a one-page document known as an A3 report. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner.

A3 Problem Solving has numerous advantages, including improved communication, better decision-making, increased efficiency, and reduced waste. It is a powerful tool for businesses of all sizes and industries, and it is especially useful for solving complex and multi-faceted problems.

In this blog post, we will walk you through the A3 Problem Solving methodology step by step. Whether you are new to A3 Problem Solving or simply want to improve your skills, this guide will help you understand and apply the process in your workplace.

What is A3 Problem Solving?

A3 Problem Solving is a structured and systematic approach to problem-solving that makes use of a one-page document called an A3 report to visually represent the process. The A3 report provides an overview of the problem, data analysis, root causes, solutions, and results in a clear and concise manner. The method was created within the framework of the Lean manufacturing methodology and is based on the principles of continuous improvement and visual management.

Looking for a A3 Problem solving template? Click here

Origin and History of A3 Problem Solving

A3 Problem Solving was developed by Toyota Motor Corporation and was first used in the manufacture of automobiles. The term “A3” refers to the size of the paper used to create the report, which is an ISO standard known as “A3”. The goal of the A3 report is to provide a visual representation of the problem-solving process that all members of the organisation can easily understand and share. A3 Problem Solving has been adopted by organisations in a variety of industries over the years, and it has become a widely used and recognised method for problem-solving.

Key Principles of A3 Problem Solving

The following are the key principles of A3 Problem Solving:

Define the problem clearly and concisely
Gather and analyze data to gain a deep understanding of the problem
Identify the root causes of the problem
Develop and implement effective solutions
Evaluate results and continuously improve

These principles serve as the foundation of the A3 Problem Solving methodology and are intended to assist organisations in continuously improving and achieving their objectives. Organizations can effectively solve problems, identify areas for improvement, and drive results by adhering to these principles.

Step 1: Define the Problem

Importance of clearly defining the problem.

The first step in the A3 Problem Solving process is critical because it lays the groundwork for the remaining steps. To define the problem clearly and accurately, you must first understand the problem and identify the underlying root cause. This step is critical because if the problem is not correctly defined, the rest of the process will be based on incorrect information, and the solution developed may not address the issue effectively.

The significance of defining the problem clearly cannot be overstated. It aids in the collection and analysis of relevant data, which is critical for developing effective solutions. When the problem is clearly defined, the data gathered is more relevant and targeted, resulting in a more comprehensive understanding of the issue. This will enable the development of solutions that are more likely to be effective because they are founded on a thorough and accurate understanding of the problem.

However, if the problem is not clearly defined, the data gathered may be irrelevant or incorrect, resulting in incorrect conclusions and ineffective solutions. Furthermore, the process of collecting and analysing data can become time-consuming and inefficient, resulting in resource waste. Furthermore, if the problem is not accurately defined, the solutions developed may fail to address the root cause of the problem, resulting in ongoing issues and a lack of improvement.

Techniques for Defining the Problem

The first step in the A3 Problem Solving process is to clearly and accurately define the problem. This is an important step because a clearly defined problem will help to ensure that the appropriate data is collected and solutions are developed. If the problem is not clearly defined, incorrect data may be collected, solutions that do not address the root cause of the problem, and time and resources may be wasted.

A problem can be defined using a variety of techniques, including brainstorming , root cause analysis , process mapping , and Ishikawa diagrams . Each of these techniques has its own advantages and disadvantages and can be used in a variety of situations depending on the nature of the problem.

Best Practice for Defining the Problem

In addition to brainstorming, root cause analysis, process mapping, and Ishikawa diagram s, best practices should be followed when defining a problem in A3 Problem Solving. Among these best practices are:

Define the issue in a specific and quantifiable way: It is critical to be specific and concise when defining the problem, as well as to quantify the problem in terms of its impact. This will help to ensure that all stakeholders understand the problem and that data collection is focused on the right areas.
Focus on the problem’s root cause: The A3 Problem Solving methodology is intended to assist organisations in identifying and addressing the root cause of a problem, rather than just the symptoms. Organizations can ensure that their solutions are effective and long-lasting by focusing on the root cause of the problem.
Ascertain that all stakeholders agree on the problem’s definition: All stakeholders must agree on the definition of the problem for the A3 Problem Solving process to be effective. This ensures that everyone is working towards the same goal and that the solutions developed are relevant and appropriate.
Consider the problem’s impact on the organisation and its stakeholders: It is critical to consider the impact of the problem on the organisation and its stakeholders when defining it. This will assist in ensuring that the appropriate data is gathered and that the solutions developed are relevant and appropriate.

Organizations can ensure that their problem is defined in a way that allows for effective data collection, analysis, and solution development by following these best practices. This will aid in the development of appropriate solutions and the effective resolution of the problem, resulting in improvements in the organization’s processes and outcomes.

Step 2: Gather Data

Gathering data in a3 problem solving.

Data collection is an important step in the A3 Problem Solving process because it allows organisations to gain a thorough understanding of the problem they are attempting to solve. This step entails gathering pertinent information about the problem, such as data on its origin, impact, and any related factors. This information is then used to help identify root causes and develop effective solutions.

One of the most important advantages of data collection in A3 Problem Solving is that it allows organisations to identify patterns and trends in data, which can be useful in determining the root cause of the problem. This information can then be used to create effective solutions that address the problem’s root cause rather than just its symptoms.

In A3 Problem Solving, data collection is a collaborative effort involving all stakeholders, including those directly impacted by the problem and those with relevant expertise or experience. Stakeholders can ensure that all relevant information is collected and that the data is accurate and complete by working together.

Overall, data collection is an important step in the A3 Problem Solving process because it serves as the foundation for effective problem-solving. Organizations can gain a deep understanding of the problem they are attempting to solve and develop effective solutions that address its root cause by collecting and analysing relevant data.

Data Collection Methods

In A3 Problem Solving, several data collection methods are available, including:

Observations
Process diagrams

The best data collection method will be determined by the problem being solved and the type of data required. To gain a complete understanding of the problem, it is critical to use multiple data collection methods.

Tools for Data Analysis and Visualization

Once the data has been collected, it must be analysed and visualised in order to gain insights into the problem. This process can be aided by the following tools:

Excel Spreadsheets
Flow diagrams
Pareto diagrams
Scatter Plots
Control diagrams

These tools can assist in organising data and making it easier to understand. They can also be used to generate visual representations of data, such as graphs and charts, to communicate the findings to others.

Finally, the data collection and analysis step is an important part of the A3 Problem Solving process. Organizations can gain a better understanding of the problem and develop effective solutions by collecting and analysing relevant data.

Step 3: Identify Root Causes

Identifying the root causes of the problem is the third step in the A3 Problem Solving process. This step is critical because it assists organisations in understanding the root causes of a problem rather than just its symptoms. Once the underlying cause of the problem is identified, it can be addressed more effectively, leading to more long-term solutions.

Overview of the Root Cause Analysis Process

The process of determining the underlying causes of a problem is known as root cause analysis. This process can assist organisations in determining why a problem is occurring and what can be done to prevent it from recurring in the future. The goal of root cause analysis is to identify the underlying cause of a problem rather than just its symptoms, allowing it to be addressed more effectively.

To understand Root cause analysis in more detail check out RCA in our Lean Six Sigma Yellow Belt Course Root Cause Analysis section

Techniques for Identifying Root Causes

There are several techniques for determining the root causes of a problem, including:

Brainstorming
Ishikawa diagrams (also known as fishbone diagrams)
Root Cause Tree Analysis

These methods can be used to investigate the issue in-depth and identify potential root causes. Organizations can gain a deeper understanding of the problem and identify the underlying causes that must be addressed by using these techniques.

Best Practices for Conducting Root Cause Analysis

It is critical to follow these best practices when conducting root cause analysis in A3 Problem Solving:

Make certain that all stakeholders participate in the root cause analysis process.
Concentrate on determining the root cause of the problem rather than just its symptoms.
Take into account all potential root causes, not just the most obvious ones.
To identify root causes, use a systematic approach, such as the 5 Whys or root cause tree analysis.

Organizations can ensure that root cause analysis is carried out effectively and that the root cause of the problem is identified by adhering to these best practises. This will aid in the development of appropriate solutions and the effective resolution of the problem.

Step 4: Develop Solutions

Developing solutions is the fourth step in the A3 Problem Solving process. This entails generating ideas and options for dealing with the problem, followed by selecting the best solution. The goal is to develop a solution that addresses the root cause of the problem and prevents it from recurring.

Solution Development in A3 Problem Solving

A3 solution development Problem solving is an iterative process in which options are generated and evaluated. The data gathered in the previous steps, as well as the insights and understanding gained from the root cause analysis, guide this process. The solution should be based on a thorough understanding of the problem and address the underlying cause.

Techniques for Developing Solutions

There are several techniques that can be used to develop solutions in A3 Problem Solving, including:

Brainwriting
Solution matrix
Multi voting
Force field analysis

These techniques can help to generate a range of options and to select the best solution.

Best Practice for Developing Solutions

It is critical to follow the following best practices when developing solutions in A3 Problem Solving:

Participate in the solution development process with all stakeholders.
Make certain that the solution addresses the underlying cause of the problem.
Make certain that the solution is feasible and achievable.
Consider the solution’s impact on the organisation and its stakeholders.

Organizations can ensure that the solutions they develop are effective and sustainable by adhering to these best practises. This will help to ensure that the problem is addressed effectively and that it does not reoccur.

Step 5: Implement Solutions

The final and most important step in the A3 Problem Solving methodology is solution implementation. This is the stage at which the identified and developed solutions are put into action to address the problem. This step’s goal is to ensure that the solutions are effective, efficient, and long-lasting.

The implementation Process

The implementation process entails putting the solutions developed in the previous step into action. This could include changes to processes, procedures, and systems, as well as employee training and education. To ensure that the solutions are effective, the implementation process should be well-planned and meticulously executed.

Techniques for Implementing Solutions

A3 Problem Solving solutions can be implemented using a variety of techniques, including:

Piloting the solution on a small scale before broadening its application
Participating in the implementation process with all relevant stakeholders
ensuring that the solution is in line with the goals and objectives of the organisation
Monitoring the solution to determine its effectiveness and make any necessary changes

Best Practice for Implementing Solutions

It is critical to follow these best practices when implementing solutions in A3 Problem Solving:

Make certain that all relevant stakeholders are involved and supportive of the solution. Have a clear implementation plan that outlines the steps, timeline, and resources required. Continuously monitor and evaluate the solution to determine its efficacy and make any necessary changes. Encourage all stakeholders to communicate and collaborate openly. Organizations can ensure that solutions are effectively implemented and problems are effectively addressed by adhering to these best practices. The ultimate goal is to find a long-term solution to the problem and improve the organization’s overall performance.

In conclusion, A3 Problem Solving is a comprehensive and structured methodology for problem-solving that can be applied in various industries and organisations. The A3 Problem Solving process’s five steps – Define the Problem, Gather Data, Identify Root Causes, Develop Solutions, and Implement Solutions – provide a road map for effectively addressing problems and making long-term improvements.

Organizations can improve their problem-solving skills and achieve better results by following the key principles, techniques, and best practices outlined in this guide. As a result, both the organisation and its stakeholders will benefit from increased efficiency, effectiveness, and satisfaction. So, whether you’re an experienced problem solver or just getting started, consider incorporating the A3 Problem Solving methodology into your work and start reaping the benefits right away.

Was this helpful?

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website www.learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Lean vs Six Sigma - Which is right for your business - Feature Image - Learnleansigma

Lean vs Six Sigma: Which Methodology is Right for Your Business?

Digital Standard Work Instructions - Feature Image - LearnLeanSigma

The Digital Revolution: Shifting from Paper to Digital SWIs

Free lean six sigma templates.

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

Understanding Process Performance: Pp and Ppk

Understand Process Performance (Pp) and Process Performance Index (Ppk) to assess and improve manufacturing processes.…

LIFO or FIFO for Stock Management?

Choosing between LIFO and FIFO for stock management depends on factors like product nature, market…

Are There Any Official Standards for Six Sigma?

Are there any official standards for Six Sigma? While Six Sigma is a well-defined methodology…

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

What is Problem Solving? (Steps, Techniques, Examples)

By Status.net Editorial Team on May 7, 2023 — 5 minutes to read

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 and professional growth, leading to more successful outcomes and better decision-making.

Problem-Solving Steps

The problem-solving process typically includes the following steps:

Identify the issue : Recognize the problem that needs to be solved.
Analyze the situation : Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present.
Generate potential solutions : Brainstorm a list of possible solutions to the issue, without immediately judging or evaluating them.
Evaluate options : Weigh the pros and cons of each potential solution, considering factors such as feasibility, effectiveness, and potential risks.
Select the best solution : Choose the option that best addresses the problem and aligns with your objectives.
Implement the solution : Put the selected solution into action and monitor the results to ensure it resolves the issue.
Review and learn : Reflect on the problem-solving process, identify any improvements or adjustments that can be made, and apply these learnings to future situations.

Defining the Problem

To start tackling a problem, first, identify and understand it. Analyzing the issue thoroughly helps to clarify its scope and nature. Ask questions to gather information and consider the problem from various angles. Some strategies to define the problem include:

Brainstorming with others
Asking the 5 Ws and 1 H (Who, What, When, Where, Why, and How)
Analyzing cause and effect
Creating a problem statement

Generating Solutions

Once the problem is clearly understood, brainstorm possible solutions. Think creatively and keep an open mind, as well as considering lessons from past experiences. Consider:

Creating a list of potential ideas to solve the problem
Grouping and categorizing similar solutions
Prioritizing potential solutions based on feasibility, cost, and resources required
Involving others to share diverse opinions and inputs

Evaluating and Selecting Solutions

Evaluate each potential solution, weighing its pros and cons. To facilitate decision-making, use techniques such as:

SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
Decision-making matrices
Pros and cons lists
Risk assessments

After evaluating, choose the most suitable solution based on effectiveness, cost, and time constraints.

Implementing and Monitoring the Solution

Implement the chosen solution and monitor its progress. Key actions include:

Communicating the solution to relevant parties
Setting timelines and milestones
Assigning tasks and responsibilities
Monitoring the solution and making adjustments as necessary
Evaluating the effectiveness of the solution after implementation

Utilize feedback from stakeholders and consider potential improvements. Remember that problem-solving is an ongoing process that can always be refined and enhanced.

Problem-Solving Techniques

During each step, you may find it helpful to utilize various problem-solving techniques, such as:

Brainstorming : A free-flowing, open-minded session where ideas are generated and listed without judgment, to encourage creativity and innovative thinking.
Root cause analysis : A method that explores the underlying causes of a problem to find the most effective solution rather than addressing superficial symptoms.
SWOT analysis : A tool used to evaluate the strengths, weaknesses, opportunities, and threats related to a problem or decision, providing a comprehensive view of the situation.
Mind mapping : A visual technique that uses diagrams to organize and connect ideas, helping to identify patterns, relationships, and possible solutions.

Brainstorming

When facing a problem, start by conducting a brainstorming session. Gather your team and encourage an open discussion where everyone contributes ideas, no matter how outlandish they may seem. This helps you:

Generate a diverse range of solutions
Encourage all team members to participate
Foster creative thinking

When brainstorming, remember to:

Reserve judgment until the session is over
Encourage wild ideas
Combine and improve upon ideas

Root Cause Analysis

For effective problem-solving, identifying the root cause of the issue at hand is crucial. Try these methods:

5 Whys : Ask “why” five times to get to the underlying cause.
Fishbone Diagram : Create a diagram representing the problem and break it down into categories of potential causes.
Pareto Analysis : Determine the few most significant causes underlying the majority of problems.

SWOT Analysis

SWOT analysis helps you examine the Strengths, Weaknesses, Opportunities, and Threats related to your problem. To perform a SWOT analysis:

List your problem’s strengths, such as relevant resources or strong partnerships.
Identify its weaknesses, such as knowledge gaps or limited resources.
Explore opportunities, like trends or new technologies, that could help solve the problem.
Recognize potential threats, like competition or regulatory barriers.

SWOT analysis aids in understanding the internal and external factors affecting the problem, which can help guide your solution.

Mind Mapping

A mind map is a visual representation of your problem and potential solutions. It enables you to organize information in a structured and intuitive manner. To create a mind map:

Write the problem in the center of a blank page.
Draw branches from the central problem to related sub-problems or contributing factors.
Add more branches to represent potential solutions or further ideas.

Mind mapping allows you to visually see connections between ideas and promotes creativity in problem-solving.

Examples of Problem Solving in Various Contexts

In the business world, you might encounter problems related to finances, operations, or communication. Applying problem-solving skills in these situations could look like:

Identifying areas of improvement in your company’s financial performance and implementing cost-saving measures
Resolving internal conflicts among team members by listening and understanding different perspectives, then proposing and negotiating solutions
Streamlining a process for better productivity by removing redundancies, automating tasks, or re-allocating resources

In educational contexts, problem-solving can be seen in various aspects, such as:

Addressing a gap in students’ understanding by employing diverse teaching methods to cater to different learning styles
Developing a strategy for successful time management to balance academic responsibilities and extracurricular activities
Seeking resources and support to provide equal opportunities for learners with special needs or disabilities

Everyday life is full of challenges that require problem-solving skills. Some examples include:

Overcoming a personal obstacle, such as improving your fitness level, by establishing achievable goals, measuring progress, and adjusting your approach accordingly
Navigating a new environment or city by researching your surroundings, asking for directions, or using technology like GPS to guide you
Dealing with a sudden change, like a change in your work schedule, by assessing the situation, identifying potential impacts, and adapting your plans to accommodate the change.
How to Resolve Employee Conflict at Work [Steps, Tips, Examples]
How to Write Inspiring Core Values? 5 Steps with Examples
30 Employee Feedback Examples (Positive & Negative)

The 6 steps to structured problem solving

Posted By Praveen Joshi

August 20th, 2020

Utilising a disciplined problem solving technique in bespoke software development is valuable in a few circumstances. Being able to resolve an issue for a bespoke software system can be very challenging, but at RSK BSL we work as a team or an individual to get this done. It is critical to utilise the correct way for the job that needs to be done. This is a great technique that sets aside some opportunity to plan.

1- Identifying the problem

Firstly, you are characterising the scope of the problem you need to explain. Focuses to consider at this stage include: problem starting point – whether it is the UI or something in the back end, problem affect (e.g. on clients/internally) and course of events to tackle the problem.

2- Structure the problem

Putting the problem into a detailed structure for investigation is one of the considerable bits of knowledge that an employee can bring to their work and their team around them. Structuring a problem is recognising the vital issues.

A vital issue could be that the client is unable to access the bespoke system provided for their business and not being able to complete day-to-day tasks because of this.

3- Develop solutions

Rather than bringing one solution to the table, it is always best to give yourself the option of custom software development solutions to the problem. The best way to do this is gather each possible way to resolve the main issue you’re facing.

4- Select a solution to the problem

With a list of solutions that might be possible to resolve the issue, it is presently time to choose. On the off chance that you confront an individual problem or one that exclusive effects your work, picking the alternative that strikes you as best and resolves the issue is sufficient.

5- Implement a solution

After selecting the solution, you put the arrangement into place. Implementation may turn into its very own task. With all things considered, undertaking this task with a team and project management skills will complete the task and get the problem resolved. In software development outsourcing company , a solution can always be the start of a new issue, so when putting this into place you need to be aware of what it could create and take this in to account.

6- Monitor for success

Monitoring the solution and circumstance is a key advance to guarantee the issue is resolved, particularly in the event that you have allocated the assignment to another team member. Monitoring is essential since issues can be an indication of a more profound issue. At RSK Business Solutions , we contact our clients if they ever have an issue to monitor and keep an ongoing relationship.

If you will like to find more about our software development services then Contact us .

Praveen Joshi

Praveen is a seasoned IT Solutions Leader and Director at RSK Business Solutions, a technology-driven IT Consulting Company that specializes in Bespoke Software Development, Agile Consulting, Mobile App Development, Smart Sourcing, and much more. For the last 17 years, he has been delivering quality custom IT solutions that help businesses achieve their goals.

Posted By Praveen Joshi on July 19th, 2024

In-House vs. Software Outsourcing Company: Which Is Better

Why IT Outsourcing Consulting is Essential for Modern Enterprises

Why Choose Software Development Services in the UK

Posted By Praveen Joshi on July 12th, 2024

Why Agile Software Development is Key for Modern Enterprises

Hey get in touch.

Please send us your requirements and we will get back to you at the earliest.

COOKIE INFORMATION

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking accept all you consent to the use of ALL cookies. However, you may wish to visit cookie preferences to provide a controlled consent. Read our cookie policy.

26 Expert-Backed Problem Solving Examples – Interview Answers

Published: February 13, 2023

Interview Questions and Answers

Actionable advice from real experts:

Biron Clark

Former Recruiter

Contributor

Dr. Kyle Elliott

Career Coach

Hayley Jukes

Editor-in-Chief

Biron Clark , Former Recruiter

Kyle Elliott , Career Coach

Hayley Jukes , Editor

As a recruiter , I know employers like to hire people who can solve problems and work well under pressure.

A job rarely goes 100% according to plan, so hiring managers are more likely to hire you if you seem like you can handle unexpected challenges while staying calm and logical.

But how do they measure this?

Hiring managers will ask you interview questions about your problem-solving skills, and they might also look for examples of problem-solving on your resume and cover letter.

In this article, I’m going to share a list of problem-solving examples and sample interview answers to questions like, “Give an example of a time you used logic to solve a problem?” and “Describe a time when you had to solve a problem without managerial input. How did you handle it, and what was the result?”

Problem-solving involves identifying, prioritizing, analyzing, and solving problems using a variety of skills like critical thinking, creativity, decision making, and communication.
Describe the Situation, Task, Action, and Result ( STAR method ) when discussing your problem-solving experiences.
Tailor your interview answer with the specific skills and qualifications outlined in the job description.
Provide numerical data or metrics to demonstrate the tangible impact of your problem-solving efforts.

What are Problem Solving Skills?

Problem-solving is the ability to identify a problem, prioritize based on gravity and urgency, analyze the root cause, gather relevant information, develop and evaluate viable solutions, decide on the most effective and logical solution, and plan and execute implementation.

Problem-solving encompasses other skills that can be showcased in an interview response and your resume. Problem-solving skills examples include:

Critical thinking
Analytical skills
Decision making
Research skills
Technical skills
Communication skills
Adaptability and flexibility

Why is Problem Solving Important in the Workplace?

Problem-solving is essential in the workplace because it directly impacts productivity and efficiency. Whenever you encounter a problem, tackling it head-on prevents minor issues from escalating into bigger ones that could disrupt the entire workflow.

Beyond maintaining smooth operations, your ability to solve problems fosters innovation. It encourages you to think creatively, finding better ways to achieve goals, which keeps the business competitive and pushes the boundaries of what you can achieve.

Effective problem-solving also contributes to a healthier work environment; it reduces stress by providing clear strategies for overcoming obstacles and builds confidence within teams.

Examples of Problem-Solving in the Workplace

Correcting a mistake at work, whether it was made by you or someone else
Overcoming a delay at work through problem solving and communication
Resolving an issue with a difficult or upset customer
Overcoming issues related to a limited budget, and still delivering good work through the use of creative problem solving
Overcoming a scheduling/staffing shortage in the department to still deliver excellent work
Troubleshooting and resolving technical issues
Handling and resolving a conflict with a coworker
Solving any problems related to money, customer billing, accounting and bookkeeping, etc.
Taking initiative when another team member overlooked or missed something important
Taking initiative to meet with your superior to discuss a problem before it became potentially worse
Solving a safety issue at work or reporting the issue to those who could solve it
Using problem solving abilities to reduce/eliminate a company expense
Finding a way to make the company more profitable through new service or product offerings, new pricing ideas, promotion and sale ideas, etc.
Changing how a process, team, or task is organized to make it more efficient
Using creative thinking to come up with a solution that the company hasn’t used before
Performing research to collect data and information to find a new solution to a problem
Boosting a company or team’s performance by improving some aspect of communication among employees
Finding a new piece of data that can guide a company’s decisions or strategy better in a certain area

Problem-Solving Examples for Recent Grads/Entry-Level Job Seekers

Coordinating work between team members in a class project
Reassigning a missing team member’s work to other group members in a class project
Adjusting your workflow on a project to accommodate a tight deadline
Speaking to your professor to get help when you were struggling or unsure about a project
Asking classmates, peers, or professors for help in an area of struggle
Talking to your academic advisor to brainstorm solutions to a problem you were facing
Researching solutions to an academic problem online, via Google or other methods
Using problem solving and creative thinking to obtain an internship or other work opportunity during school after struggling at first

How To Answer “Tell Us About a Problem You Solved”

When you answer interview questions about problem-solving scenarios, or if you decide to demonstrate your problem-solving skills in a cover letter (which is a good idea any time the job description mentions problem-solving as a necessary skill), I recommend using the STAR method.

STAR stands for:

It’s a simple way of walking the listener or reader through the story in a way that will make sense to them.

Start by briefly describing the general situation and the task at hand. After this, describe the course of action you chose and why. Ideally, show that you evaluated all the information you could given the time you had, and made a decision based on logic and fact. Finally, describe the positive result you achieved.

Note: Our sample answers below are structured following the STAR formula. Be sure to check them out!

EXPERT ADVICE

Dr. Kyle Elliott , MPA, CHES Tech & Interview Career Coach caffeinatedkyle.com

How can I communicate complex problem-solving experiences clearly and succinctly?

Before answering any interview question, it’s important to understand why the interviewer is asking the question in the first place.

When it comes to questions about your complex problem-solving experiences, for example, the interviewer likely wants to know about your leadership acumen, collaboration abilities, and communication skills, not the problem itself.

Therefore, your answer should be focused on highlighting how you excelled in each of these areas, not diving into the weeds of the problem itself, which is a common mistake less-experienced interviewees often make.

Tailoring Your Answer Based on the Skills Mentioned in the Job Description

As a recruiter, one of the top tips I can give you when responding to the prompt “Tell us about a problem you solved,” is to tailor your answer to the specific skills and qualifications outlined in the job description.

Once you’ve pinpointed the skills and key competencies the employer is seeking, craft your response to highlight experiences where you successfully utilized or developed those particular abilities.

For instance, if the job requires strong leadership skills, focus on a problem-solving scenario where you took charge and effectively guided a team toward resolution.

By aligning your answer with the desired skills outlined in the job description, you demonstrate your suitability for the role and show the employer that you understand their needs.

Amanda Augustine expands on this by saying:

“Showcase the specific skills you used to solve the problem. Did it require critical thinking, analytical abilities, or strong collaboration? Highlight the relevant skills the employer is seeking.”

Interview Answers to “Tell Me About a Time You Solved a Problem”

Now, let’s look at some sample interview answers to, “Give me an example of a time you used logic to solve a problem,” or “Tell me about a time you solved a problem,” since you’re likely to hear different versions of this interview question in all sorts of industries.

The example interview responses are structured using the STAR method and are categorized into the top 5 key problem-solving skills recruiters look for in a candidate.

1. Analytical Thinking

Situation: In my previous role as a data analyst , our team encountered a significant drop in website traffic.

Task: I was tasked with identifying the root cause of the decrease.

Action: I conducted a thorough analysis of website metrics, including traffic sources, user demographics, and page performance. Through my analysis, I discovered a technical issue with our website’s loading speed, causing users to bounce.

Result: By optimizing server response time, compressing images, and minimizing redirects, we saw a 20% increase in traffic within two weeks.

2. Critical Thinking

Situation: During a project deadline crunch, our team encountered a major technical issue that threatened to derail our progress.

Task: My task was to assess the situation and devise a solution quickly.

Action: I immediately convened a meeting with the team to brainstorm potential solutions. Instead of panicking, I encouraged everyone to think outside the box and consider unconventional approaches. We analyzed the problem from different angles and weighed the pros and cons of each solution.

Result: By devising a workaround solution, we were able to meet the project deadline, avoiding potential delays that could have cost the company $100,000 in penalties for missing contractual obligations.

3. Decision Making

Situation: As a project manager , I was faced with a dilemma when two key team members had conflicting opinions on the project direction.

Task: My task was to make a decisive choice that would align with the project goals and maintain team cohesion.

Action: I scheduled a meeting with both team members to understand their perspectives in detail. I listened actively, asked probing questions, and encouraged open dialogue. After carefully weighing the pros and cons of each approach, I made a decision that incorporated elements from both viewpoints.

Result: The decision I made not only resolved the immediate conflict but also led to a stronger sense of collaboration within the team. By valuing input from all team members and making a well-informed decision, we were able to achieve our project objectives efficiently.

4. Communication (Teamwork)

Situation: During a cross-functional project, miscommunication between departments was causing delays and misunderstandings.

Task: My task was to improve communication channels and foster better teamwork among team members.

Action: I initiated regular cross-departmental meetings to ensure that everyone was on the same page regarding project goals and timelines. I also implemented a centralized communication platform where team members could share updates, ask questions, and collaborate more effectively.

Result: Streamlining workflows and improving communication channels led to a 30% reduction in project completion time, saving the company $25,000 in operational costs.

5. Persistence

Situation: During a challenging sales quarter, I encountered numerous rejections and setbacks while trying to close a major client deal.

Task: My task was to persistently pursue the client and overcome obstacles to secure the deal.

Action: I maintained regular communication with the client, addressing their concerns and demonstrating the value proposition of our product. Despite facing multiple rejections, I remained persistent and resilient, adjusting my approach based on feedback and market dynamics.

Result: After months of perseverance, I successfully closed the deal with the client. By closing the major client deal, I exceeded quarterly sales targets by 25%, resulting in a revenue increase of $250,000 for the company.

Tips to Improve Your Problem-Solving Skills

Throughout your career, being able to showcase and effectively communicate your problem-solving skills gives you more leverage in achieving better jobs and earning more money .

So to improve your problem-solving skills, I recommend always analyzing a problem and situation before acting.

When discussing problem-solving with employers, you never want to sound like you rush or make impulsive decisions. They want to see fact-based or data-based decisions when you solve problems.

Don’t just say you’re good at solving problems. Show it with specifics. How much did you boost efficiency? Did you save the company money? Adding numbers can really make your achievements stand out.

To get better at solving problems, analyze the outcomes of past solutions you came up with. You can recognize what works and what doesn’t.

Think about how you can improve researching and analyzing a situation, how you can get better at communicating, and deciding on the right people in the organization to talk to and “pull in” to help you if needed, etc.

Finally, practice staying calm even in stressful situations. Take a few minutes to walk outside if needed. Step away from your phone and computer to clear your head. A work problem is rarely so urgent that you cannot take five minutes to think (with the possible exception of safety problems), and you’ll get better outcomes if you solve problems by acting logically instead of rushing to react in a panic.

You can use all of the ideas above to describe your problem-solving skills when asked interview questions about the topic. If you say that you do the things above, employers will be impressed when they assess your problem-solving ability.

More Interview Resources

3 Answers to “How Do You Handle Stress?”
How to Answer “How Do You Handle Conflict?” (Interview Question)
Sample Answers to “Tell Me About a Time You Failed”

About the Author

Biron Clark is a former executive recruiter who has worked individually with hundreds of job seekers, reviewed thousands of resumes and LinkedIn profiles, and recruited for top venture-backed startups and Fortune 500 companies. He has been advising job seekers since 2012 to think differently in their job search and land high-paying, competitive positions. Follow on Twitter and LinkedIn .

12 Expert-Approved Responses to ‘What Makes You Unique?’ in Job Interviews

15 most common pharmacist interview questions and answers, 15 most common paralegal interview questions and answers, top 30+ funny interview questions and answers, 60 hardest interview questions and answers, 100+ best ice breaker questions to ask candidates, top 20 situational interview questions (& sample answers), 15 most common physical therapist interview questions and answers.

Hacking the Case Interview

An issue tree is a structured framework used to break down and analyze complex problems or questions into smaller components. It is a visual representation of the various aspects, sub-issues, and potential solutions related to a particular problem.

Issue trees are commonly used in business, consulting, problem-solving, and decision-making processes.

If you’re looking to better understand issue trees and how to use them in consulting case interviews or in business, we have you covered.

In this comprehensive article, we’ll cover:

What is an issue tree?
Why are issue trees important?
How do I create an issue tree?
How do I use issue trees in consulting case interviews?
What are examples of issue trees?
What are tips for making effective issue trees?

If you’re looking for a step-by-step shortcut to learn case interviews quickly, enroll in our case interview course . These insider strategies from a former Bain interviewer helped 30,000+ land consulting offers while saving hundreds of hours of prep time.

What is an Issue Tree?

An issue tree is a visual representation of a complex problem or question broken down into smaller, more manageable components. It consists of a top level issue, visualized as the root question, and sub-issues, visualized as branches and sub-branches.

Top Level Issue (Root Question) : This is the main problem or question that needs to be addressed. It forms the root of the tree.
Sub-issues (Branches) : Underneath the top level issue are branches representing the major categories or dimensions of the problem. These are the high-level areas that contribute to the overall problem.
Further Sub-issues (Sub-branches) : Each branch can be broken down further into more specific sub-issues.

Issue trees generally take on the following structure.

Issue trees get their name because the primary issue that you are solving for can be broken down into smaller issues or branches. These issues can then be further broken down into even smaller issues or branches.

This can be continued until you are left with a long list of small issues that are much simpler and more manageable. No matter how complicated or difficult a problem is, an issue tree can provide a way to structure the problem to make it easier to solve.

As an example, let’s say that we are trying to help a lemonade stand increase their profits. The overall problem is determining how to increase profits.

Since profits is equal to revenue minus costs, we can break this problem down into two smaller problems:

How can we increase revenues?
How can we decrease costs?

Since revenue is equal to quantity times price, we can further break this revenue problem down into two even smaller problems:

How can we increase quantity sold?
How can we increase price?

Looking at the problem of how to increase quantity sold, we can further break that problem down:

How can we increase the quantity of lemonade sold?
How can we increase the quantity of other goods sold?

We can repeat the same procedure for the costs problem since we know that costs equal variable costs plus fixed costs.

How can we decrease variable costs?
How can we decrease fixed costs?

Looking at the problem of how to decrease variable costs, we can further break that down by the different variable cost components of lemonade:

How can we decrease costs of lemons?
How can we decrease costs of water?
How can we decrease costs of ice?
How can we decrease costs of sugar?
How can we decrease costs of cups?

The overall issue tree for this example would look like the following:

In this example, the issue tree is a special kind of issue tree known as a profit tree.

Why are Issue Trees Important?

Issue trees are helpful because they facilitate systematic analysis, managing complexity, prioritization, generating solutions, identifying root causes, work subdivision, roadmap generation, and effective communication.

Systematic analysis : Issue trees guide a systematic analysis of the problem. By dissecting the problem into its constituent parts, you can thoroughly examine each aspect and understand its implications.

Managing complexity : Complex problems often involve multiple interrelated factors. Issue trees provide a way to manage this complexity by organizing and visualizing the relationships between different components.

Prioritization : Issue trees help in prioritizing actions. By assessing the importance and impact of each sub-issue, you can determine which aspects of the problem require immediate attention.

Generating solutions : Issue trees facilitate the generation of potential solutions or strategies for each component of the problem. This allows for a more comprehensive approach to problem-solving.

Identifying root causes : Issue trees help in identifying the root causes of a problem. By drilling down through the sub-issues, you can uncover the underlying factors contributing to the main issue.

Work subdivision : Issue trees provide you with a list of smaller, distinct problems or areas to explore. This distinction makes it easy for you to divide up work.

Roadmap generation : Issue trees layout exactly all of the different areas or issues that you need to focus on in order to solve the overall problem. This gives you a clear idea of where to focus your attention and work on.

Effective communication : Issue trees are powerful communication tools. Visualizing the problem in a structured format helps in explaining it to others, including team members, stakeholders, or clients.

How Do I Create An Issue Tree?

Creating an issue tree involves several steps. Here's a step-by-step guide to help you through the process:

Step 1: Define the top-level issue

Start by clearly articulating the main problem or question that you want to address. This will form the root of your issue tree.

Step 2: Identify the branches (sub-issues)

Consider the major sub-issues that contribute to the overall problem. These will become the branches of your issue tree. Brainstorm and list them down.

There are four major ways that you can break down the root problem in an issue tree. You can break down the issue by stakeholder, process, segments, or math.

Stakeholder : Break the problem down by identifying all stakeholders involved. This may include the company, customers, competitors, suppliers, manufacturers, distributors, and retailers. Each stakeholder becomes a branch for the top-level issue.
Process : Break the problem down by identifying all of the different steps in the process. Each step becomes a branch for the top-level issue.
Segment : Break the problem down into smaller segments. This may include breaking down the problem by geography, product, customer segment, market segment, distribution channel, or time horizon. Each segment becomes a branch for the top-level issue.
Math : Break a problem down by quantifying the problem into an equation or formula . Each term in the equation is a branch for the top-level issue.

Step 3: Break down each branch

For each branch, ask yourself if there are further components that contribute to it. If so, break down each branch into more specific components. Continue this process until you've reached a level of detail that allows for meaningful analysis.

Similar to the previous step, you can break down a branch by stakeholder, process, segment, or by math.

Step 4: Review and refine

Take a step back and review your issue tree. Make sure it accurately represents the problem and its components. Look for any missing or redundant branches or sub-issues.

Step 5: Prioritize and evaluate

Consider assigning priorities to different sub-issues or potential solutions. This will help guide your decision-making process.

How Do I Use Issue Trees in Consulting Case Interviews?

Issue trees are used near the beginning of the consulting case interview to break down the business problem into smaller, more manageable components.

After the interviewer provides the case background information, you’ll be expected to quickly summarize the context of the case and verify the case objective. After asking clarifying questions, you’ll ask for a few minutes of silence to create an issue tree.

After you have created an issue tree, here’s how you would use it:

Step 1: Walk your interviewer through the issue tree

Once you’ve created an issue tree, provide a concise summary of how it's structured and how it addresses the problem at hand. Explain the different branches and sub-branches. They may ask a few follow-up questions.

As you are presenting your issue tree, periodically check in with the interviewer to ensure you're on the right track. Your interviewer may provide some input or guidance on improving your issue tree.

Step 2: Identify an area of your issue tree to start investigating

Afterwards, you’ll use the issue tree to help identify a branch to start investigating. There is generally no wrong answer here as long as you have a reason that supports why you want to start with a particular branch.

To determine which branch to start investigating, ask yourself a few questions. What is the most important sub-issue? Consider factors like urgency, impact, or feasibility. What is your best guess for how the business problem can be solved?

Step 3: Gather data and information

Collect relevant facts, data, and information for the sub-issue that you are investigating. This will provide the necessary context and evidence for your analysis.

Step 4 : Record key insights on the issue tree

After diving deeper into each sub-issue or branch on your issue tree, you may find it helpful to write a few bullets on the key takeaways or insights that you’ve gathered through your analysis.

This will help you remember all the work that you have done during the case interview so far. It’ll also help you develop a recommendation at the end of the case interview because you’ll quickly be able to read a summary of all of your analysis.

Step 5: Iterate and adjust as needed

As you work through the problem-solving process, be prepared to adjust and update the issue tree based on new information, insights, or changes in the situation.

Remember, creating an issue tree is not a one-size-fits-all process. It's a dynamic tool that can be adapted to suit the specific needs and complexity of the problem you're addressing.

Step 6: Select the next area of your issue tree to investigate

Once you have finished analyzing a branch or sub-issue on your issue tree and reached a satisfactory insight or conclusion, move onto the next branch or sub-issue.

Again, consider factors like urgency, impact, or feasibility when prioritizing which branch or sub-issue to dive deeper into. Repeat this step until the end of the case interview when you are asked for a final recommendation.

What are Examples of Issue Trees?

Below are five issue tree examples for five common types of business situations and case interviews.

If you want to learn strategies on how to create unique and tailored issue trees for any case interview, check out our comprehensive article on case interview frameworks .

Profitability Issue Tree Example

Profitability cases ask you to identify what is causing a company’s decline in profits and what can be done to address this problem.

A potential issue tree template for this case could explore four major issues:

What is causing the decline in profitability?
Is the decline due to changes among customers?
Is the decline due to changes among competitors?
Is the decline due to market trends?

Market Entry Issue Tree Example

Market entry cases ask you to determine whether a company should enter a new market.

Is the market attractive?
Are competitors strong?
Does the company have the capabilities to enter?
Will the company be profitable from entering the market?

Merger and Acquisition Issue Tree Example

Merger and acquisition cases ask you to determine whether a company or private equity firm should acquire a particular company.

Is the market that the target is in attractive?
Is the acquisition target an attractive company?
Are there any acquisition synergies?
Will the acquisition lead to high returns?

Merger and acquisition issue tree example

New Product Issue Tree Example

New product cases ask you to determine whether a company should launch a new product or service.

Will customers like the product?
Does the company have the capabilities to successfully launch the product?
Will the company be profitable from launching the product?

Pricing Issue Tree Example

Pricing cases ask you to determine how to price a particular product or service.

A potential issue tree template for this case could explore three major issues:

How should we price based on the product cost?
How should we price based on competitors’ products?
How should we price based on customer value?

What are Tips for Making Effective Issue Trees?

Issue trees are powerful tools to solve complex business problems, but they are much less effective if they don’t follow these important tips.

Issue tree tip #1: Be MECE

MECE stands for mutually exclusive and collectively exhaustive. When breaking down the overall problem in your issue tree, the final list of smaller problems needs to be mutually exclusive and collectively exhaustive.

Mutually exclusive means that none of the smaller problems in your issue tree overlap with each other. This ensures that you are working efficiently since there will be no duplicated or repeated work.

For example, let’s say that two of the issues in your issue tree are:

Determine how to increase cups of lemonade sold
Determine how to partner with local organizations to sell lemonade

This is not mutually exclusive because determining how to partner with local organizations would include determining how to increase cups of lemonade sold.

In determining how to increase cups of lemonade sold, you may be duplicating work from determining how to partner with local organizations.

Collectively exhaustive means that the list of smaller problems in your issue tree account for all possible ideas and possibilities. This ensures that your issue tree is not missing any critical areas to explore.

For example, let’s say that you break down the issue of determining how to decrease variable costs into the following issues:

This is not collectively exhaustive because you are missing two key variable costs: sugar and cups. These could be important areas that could increase profitability, which are not captured by your issue tree.

You can read a full explanation of this in our article on the MECE principle .

Issue tree tip #2: Be 80/20

The 80/20 principle states that 80% of the results come from 20% of the effort or time invested.

In other words, it is a much more efficient use of time to spend a day solving 80% of a problem and then moving onto solving the next few problems than to spend five days solving 100% of one problem.

This same principle should be applied to your issue tree. You do not need to solve every single issue that you have identified. Instead, focus on solving the issues that have the greatest impact and require the least amount of work.

Let’s return to our lemonade stand example. If we are focusing on the issue of how to decrease costs, we can consider fixed costs and variable costs.

It may be a better use of time to focus on decreasing variable costs because they are generally easier to lower than fixed costs.

Fixed costs, such as paying for a business permit or purchasing a table and display sign, typically have long purchasing periods, making them more difficult to reduce in the short-term.

Issue tree tip #3: Have three to five branches

Your issue tree needs to be both comprehensive, but also clear and easy to follow. Therefore, your issue tree should have at least three branches to be able to cover enough breadth of the key issue.

Additionally, your issue tree should have no more than five branches. Any more than this will make your issue tree too complicated and difficult to follow. By having more than five branches, you also increase the likelihood that there will be redundancies or overlap among your branches, which is not ideal.

Having three to five branches helps achieve a balance between going deep into specific sub-issues and covering a broad range of aspects. It balances breadth and depth.

Issue tree tip #4: Clearly define the top-level issue

Make sure that you clearly articulate the main problem or question. This sets the foundation for the entire issue tree. If you are addressing the wrong problem or question, your entire issue tree will be useless to you.

Issue tree tip #5: Visualize the issue tree clearly

If you're using a visual representation, make sure it's easy to follow. Use clean lines, appropriate spacing, and clear connections between components.

Keep your issue tree organized and neat. A cluttered or disorganized tree can be confusing and difficult to follow.

Ensure that each branch and sub-issue is labeled clearly and concisely. Use language that is easily understandable to your audience.

Issue tree tip #6: Order your branches logically

Whenever possible, try to organize the branches in your issue tree logically.

For example, if the branches in your issue tree are segmented by time, arrange them as short-term, medium-term, and long-term. This is a logical order that is arranged by length of time.

It does not make sense to order the branches as long-term, short-term, and medium- term. This ordering is confusing and will make the entire issue tree harder to follow.

Issue tree tip #7: Branches should be parallel

The branches on your issue tree should all be on the same logical level.

For example, if you decide to segment the branches on your issue tree by geography, your branches could be: North America, South America, Europe, Asia, Africa, and Australia. This segmentation is logical because each segment is a continent.

It would not make sense to segment the branches on your issue as United States, South America, China, India, Australia, and rest of the world. This segmentation does not follow logical consistency because it mixes continents and countries.

Issue tree tip #8: Practice and get feedback

It takes practice to create comprehensive, clear, and concise issue trees. This is a skill that takes time to develop and refine.

When you initially create your first few issue trees, it may take you a long period of time and you may be missing key sub-issues. However, with enough practice, you’ll be able to create issue trees effortlessly and effectively.

Practice creating issue trees on different problems to improve your skills. Seek feedback from peers or mentors to refine your approach.

Recommended Consulting Interview Resources

Here are the resources we recommend to land your dream consulting job:

For help landing consulting interviews

Resume Review & Editing : Transform your resume into one that will get you multiple consulting interviews

For help passing case interviews

Comprehensive Case Interview Course (our #1 recommendation): The only resource you need. Whether you have no business background, rusty math skills, or are short on time, this step-by-step course will transform you into a top 1% caser that lands multiple consulting offers.
Case Interview Coaching : Personalized, one-on-one coaching with a former Bain interviewer.
Hacking the Case Interview Book (available on Amazon): Perfect for beginners that are short on time. Transform yourself from a stressed-out case interview newbie to a confident intermediate in under a week. Some readers finish this book in a day and can already tackle tough cases.
The Ultimate Case Interview Workbook (available on Amazon): Perfect for intermediates struggling with frameworks, case math, or generating business insights. No need to find a case partner – these drills, practice problems, and full-length cases can all be done by yourself.

For help passing consulting behavioral & fit interviews

Behavioral & Fit Interview Course : Be prepared for 98% of behavioral and fit questions in just a few hours. We'll teach you exactly how to draft answers that will impress your interviewer.

Land Multiple Consulting Offers

Complete, step-by-step case interview course. 30,000+ happy customers.

7 Examples of Problem-Solving Scenarios in the Workplace (With Solutions)

What is problem-solving anyway, problem-solving scenario #1: tight deadlines and heavy workload.

Problem-solving Scenario #2: Handling a Product Launch

Problem-solving Scenario #3: Internal Conflicts in the Team

Problem-solving scenario #4: team not meeting targets, problem-solving scenario #5: team facing high turnover, problem-solving scenario #6: team member facing discrimination, problem-solving scenario #7: new manager unable to motivate a team, building an effective problem-solving framework, wrapping up, frequently asked questions for managers.

Other Related Blogs

Problem-Solving Scenarios for Managers

Talk to the team members: John begins by asking what’s holding them back. Based on their responses, he realizes that he needs to delegate better. Immediately, John schedules meetings to clarify each member’s expectations , priorities, and roles and ensure everyone is on the same page. He also makes a note to work on his delegation skills.
Plan things: John creates a project timeline or task list that outlines the deadlines and deliverables for each team member and shares this with the team to ensure that everyone is aware of what is expected of them.
Support the team: The team sits together to establish regular check-ins or progress updates to ensure members can ask questions or raise concerns.

Problem-solving Scenario # 2 : Handling a Product Launch

Review and redraw plans: Emily revisited the project plan and identified areas where the team could reduce the scope or prioritize features to meet the budget constraints.
Go for alternatives: The team then explored alternative resources or suppliers to find cost-effective options. Are there any underutilized resources, equipment, or personnel from other projects or departments that can be temporarily assigned to this project? Moreover, they revisited their suppliers and negotiated further.
Outsourcing parts of the project: Emily considered outsourcing some project functions to external contractors or freelancers. Eventually, they outsourced the marketing to another team and continued working on the core features.
Upgrade the available capacity: Emily and her team invested in upskilling the present workforce with additional skills. It allowed some team members to explore exciting areas and supplemented the team.
Get both sides onboard: Taylor begins the conflict resolution process by talking to both team members. She recognizes the issue and first goes into individual discussions with both. Later, she sets up a meeting for both to share their perspectives.
Mediation: In the next step, the manager encourages the two team members to talk to each other and resolve the conflict independently. Taylor describes how the optimal contribution can look different for different team members. Additionally, she encourages them to be more open and collaborative so that they understand what the other one does.
Preventing mistakes again: The team holds a meeting to discuss the issue and allow other team members to express their thoughts and feelings. By not hiding the problem that happened in front of everyone, Taylor acknowledges the issues and shows that she cares about the things happening inside the team. Further, by discussing and sharing, they can build a healthy relationship to prevent similar issues in the future.
Use formal tools: Lastly, they establish clear guidelines and expectations for behavior and communication within the team to prevent future conflicts. Training and coaching are also added to help team members improve their communication and conflict-resolution skills.
Discussions with the Sales Representatives: Donna starts by having one-on-one conversations with each team member to understand their perspectives on why the targets are not being met. After gathering insights from personal discussions, Donna calls for a team meeting. During the session, she allows team members to share their experiences, challenges, and suggestions openly.
Analysis of Sales Process: Donna conducts a detailed sales process analysis, from lead generation to closing deals. She identifies bottlenecks and areas where the team might be facing difficulties. This analysis helps her pinpoint specific stages that need improvement.
Setting Realistic Targets: Donna understands that overly ambitious targets might be demotivating. She collaborates with her team to develop more achievable yet challenging sales targets based on their current performance and market conditions. She organizes training sessions and workshops to help team members develop the necessary skills and knowledge to excel.
Recognition and Incentives: Donna introduces a recognition program and incentives for meeting and exceeding targets to motivate the team. This helps boost morale and encourages healthy competition within the team. She closely monitors the team’s progress toward the revised targets.
Conduct Exit Interviews: As the stream of resignation continues, Neil adopts a realistic approach and starts by attempting to understand the issues his former team members face. He conducts exit interviews with the people leaving and tries to determine what’s wrong.
Understand the current team: In the next step, Neil tries to learn the perspectives of staying people. Through surveys and conversations, he lists the good parts of working in his team and emphasizes them. He also finds the challenges and works on reducing them.
Change and adapt to employee needs: These conversations help Neil enable a better work environment to help him contain turnover and attract top talent. Moving forward, he ensures that pay is competitive and work is aligned with the employee’s goals. He also involves stakeholders to create development and growth opportunities for his team.
Be approachable and open: Erica first ensures she can gather all the details from the team members. She provides them with a safe space and comfort to express their concern and ensures that action will be taken. She supports the targeted team members, such as access to counselling or other resources.
Adopt and follow an official policy: Developing and enforcing anti-discrimination policies that clearly state the organization’s commitment to diversity and inclusion is the first step to creating a safe workplace. Erica refers to the policy and takes immediate action accordingly, including a thorough investigation.
Reiterating commitment and goals: Providing diversity and inclusion training to all team members to help them understand the impact of discrimination and how to prevent it is essential to create a safe workplace. Erica ensures that the team members are aware of the provisions, the DEI goals set by the organization, and
Connect with the team: Andrew starts by conducting one-on-one meetings with team members to understand their personal and professional goals, challenges, and strengths. Observing team dynamics and identifying any issues or obstacles hindering motivation and productivity also helps.
Involving team members in the process: Seeking feedback from team members on what motivates them and what they want to see from their manager to feel more inspired.
Enabling and empowering: Offering opportunities for growth and development, such as training, mentoring, or leadership roles, helped Andrew contribute to his team’s development.
Take help from Merlin: Andrew reached out to Merlin, the AI chatbot of Risely, to get tips whenever he got stuck. Merlin sought details about his issues and shared some tips to help out Andrew. Here is what it looked like:

Develop a problem-solving process: To get problem-solving right for multiple scenarios repeatedly, the key is to remember and set a problem-solving approach that works across the board. A wide-ranged problem-solving process that begins with identification and concludes at the resolution helps managers navigate various challenges the profession throws us.
Learn to identify problems: The key to solving problems is placing them at the right moment. If you let some problems pester for long, they can become more significant issues for the teams. Hence, building the understanding to identify issues is essential for managers.
Think from multiple perspectives: As a problem-solver, you must care for various parties and stakeholders. Thus, thinking from numerous perspectives and considering ideas from a broad spectrum of people is a core skill.
Consistently work on skills: Like other managerial skills, problem-solving skills need constant practice and review. Over time, your skills can become more robust with the help of assessments and toolkits. Tools like Risely can help you with resources and constant guidance to overcome managerial challenges. Check out Risely today to start reaching your true potential.

Suprabha Sharma

Suprabha, a versatile professional who blends expertise in human resources and psychology, bridges the divide between people management and personal growth with her novel perspectives at Risely. Her experience as a human resource professional has empowered her to visualize practical solutions for frequent managerial challenges that form the pivot of her writings.

How well do you perform in different problem-solving scenarios?

Learn more about your problem-solving skills with the help of a free assessment now.

What are some problem-solving scenarios?

What are problem scenarios, what is one example of problem-solving.

Top 15 Tips for Effective Conflict Mediation at Work

Top 10 games for negotiation skills to make you a better leader, manager effectiveness: a complete guide for managers in 2024, 5 proven ways managers can build collaboration in a team.

39 Best Problem-Solving Examples

Chris Drew (PhD)

Dr. Chris Drew is the founder of the Helpful Professor. He holds a PhD in education and has published over 20 articles in scholarly journals. He is the former editor of the Journal of Learning Development in Higher Education. [Image Descriptor: Photo of Chris]

Learn about our Editorial Process

problem-solving examples and definition, explained below

Problem-solving is a process where you’re tasked with identifying an issue and coming up with the most practical and effective solution.

This indispensable skill is necessary in several aspects of life, from personal relationships to education to business decisions.

Problem-solving aptitude boosts rational thinking, creativity, and the ability to cooperate with others. It’s also considered essential in 21st Century workplaces.

If explaining your problem-solving skills in an interview, remember that the employer is trying to determine your ability to handle difficulties. Focus on explaining exactly how you solve problems, including by introducing your thoughts on some of the following frameworks and how you’ve applied them in the past.

Problem-Solving Examples

1. divergent thinking.

Divergent thinking refers to the process of coming up with multiple different answers to a single problem. It’s the opposite of convergent thinking, which would involve coming up with a singular answer .

The benefit of a divergent thinking approach is that it can help us achieve blue skies thinking – it lets us generate several possible solutions that we can then critique and analyze .

In the realm of problem-solving, divergent thinking acts as the initial spark. You’re working to create an array of potential solutions, even those that seem outwardly unrelated or unconventional, to get your brain turning and unlock out-of-the-box ideas.

This process paves the way for the decision-making stage, where the most promising ideas are selected and refined.

Go Deeper: Divervent Thinking Examples

2. Convergent Thinking

Next comes convergent thinking, the process of narrowing down multiple possibilities to arrive at a single solution.

This involves using your analytical skills to identify the best, most practical, or most economical solution from the pool of ideas that you generated in the divergent thinking stage.

In a way, convergent thinking shapes the “roadmap” to solve a problem after divergent thinking has supplied the “destinations.”

Have a think about which of these problem-solving skills you’re more adept at: divergent or convergent thinking?

Go Deeper: Convergent Thinking Examples

3. Brainstorming

Brainstorming is a group activity designed to generate a multitude of ideas regarding a specific problem. It’s divergent thinking as a group , which helps unlock even more possibilities.

A typical brainstorming session involves uninhibited and spontaneous ideation, encouraging participants to voice any possible solutions, no matter how unconventional they might appear.

It’s important in a brainstorming session to suspend judgment and be as inclusive as possible, allowing all participants to get involved.

By widening the scope of potential solutions, brainstorming allows better problem definition, more creative solutions, and helps to avoid thinking “traps” that might limit your perspective.

Go Deeper: Brainstorming Examples

4. Thinking Outside the Box

The concept of “thinking outside the box” encourages a shift in perspective, urging you to approach problems from an entirely new angle.

Rather than sticking to traditional methods and processes, it involves breaking away from conventional norms to cultivate unique solutions.

In problem-solving, this mindset can bypass established hurdles and bring you to fresh ideas that might otherwise remain undiscovered.

Think of it as going off the beaten track when regular routes present roadblocks to effective resolution.

5. Case Study Analysis

Analyzing case studies involves a detailed examination of real-life situations that bear relevance to the current problem at hand.

For example, if you’re facing a problem, you could go to another environment that has faced a similar problem and examine how they solved it. You’d then bring the insights from that case study back to your own problem.

This approach provides a practical backdrop against which theories and assumptions can be tested, offering valuable insights into how similar problems have been approached and resolved in the past.

See a Broader Range of Analysis Examples Here

6. Action Research

Action research involves a repetitive process of identifying a problem, formulating a plan to address it, implementing the plan, and then analyzing the results. It’s common in educational research contexts.

The objective is to promote continuous learning and improvement through reflection and action. You conduct research into your problem, attempt to apply a solution, then assess how well the solution worked. This becomes an iterative process of continual improvement over time.

For problem-solving, this method offers a way to test solutions in real-time and allows for changes and refinements along the way, based on feedback or observed outcomes. It’s a form of active problem-solving that integrates lessons learned into the next cycle of action.

Go Deeper: Action Research Examples

7. Information Gathering

Fundamental to solving any problem is the process of information gathering.

This involves collecting relevant data , facts, and details about the issue at hand, significantly aiding in the understanding and conceptualization of the problem.

In problem-solving, information gathering underpins every decision you make.

This process ensures your actions are based on concrete information and evidence, allowing for an informed approach to tackle the problem effectively.

8. Seeking Advice

Seeking advice implies turning to knowledgeable and experienced individuals or entities to gain insights on problem-solving.

It could include mentors, industry experts, peers, or even specialized literature.

The value in this process lies in leveraging different perspectives and proven strategies when dealing with a problem. Moreover, it aids you in avoiding pitfalls, saving time, and learning from others’ experiences.

9. Creative Thinking

Creative thinking refers to the ability to perceive a problem in a new way, identify unconventional patterns, or produce original solutions.

It encourages innovation and uniqueness, often leading to the most effective results.

When applied to problem-solving, creative thinking can help you break free from traditional constraints, ideal for potentially complex or unusual problems.

Go Deeper: Creative Thinking Examples

10. Conflict Resolution

Conflict resolution is a strategy developed to resolve disagreements and arguments, often involving communication, negotiation, and compromise.

When employed as a problem-solving technique, it can diffuse tension, clear bottlenecks, and create a collaborative environment.

Effective conflict resolution ensures that differing views or disagreements do not become roadblocks in the process of problem-solving.

Go Deeper: Conflict Resolution Examples

11. Addressing Bottlenecks

Bottlenecks refer to obstacles or hindrances that slow down or even halt a process.

In problem-solving, addressing bottlenecks involves identifying these impediments and finding ways to eliminate them.

This effort not only smooths the path to resolution but also enhances the overall efficiency of the problem-solving process.

For example, if your workflow is not working well, you’d go to the bottleneck – that one point that is most time consuming – and focus on that. Once you ‘break’ this bottleneck, the entire process will run more smoothly.

12. Market Research

Market research involves gathering and analyzing information about target markets, consumers, and competitors.

In sales and marketing, this is one of the most effective problem-solving methods. The research collected from your market (e.g. from consumer surveys) generates data that can help identify market trends, customer preferences, and competitor strategies.

In this sense, it allows a company to make informed decisions, solve existing problems, and even predict and prevent future ones.

13. Root Cause Analysis

Root cause analysis is a method used to identify the origin or the fundamental reason for a problem.

Once the root cause is determined, you can implement corrective actions to prevent the problem from recurring.

As a problem-solving procedure, root cause analysis helps you to tackle the problem at its source, rather than dealing with its surface symptoms.

Go Deeper: Root Cause Analysis Examples

14. Mind Mapping

Mind mapping is a visual tool used to structure information, helping you better analyze, comprehend and generate new ideas.

By laying out your thoughts visually, it can lead you to solutions that might not have been apparent with linear thinking.

In problem-solving, mind mapping helps in organizing ideas and identifying connections between them, providing a holistic view of the situation and potential solutions.

15. Trial and Error

The trial and error method involves attempting various solutions until you find one that resolves the problem.

It’s an empirical technique that relies on practical actions instead of theories or rules.

In the context of problem-solving, trial and error allows you the flexibility to test different strategies in real situations, gaining insights about what works and what doesn’t.

16. SWOT Analysis

SWOT is an acronym standing for Strengths, Weaknesses, Opportunities, and Threats.

It’s an analytic framework used to evaluate these aspects in relation to a particular objective or problem.

In problem-solving, SWOT Analysis helps you to identify favorable and unfavorable internal and external factors. It helps to craft strategies that make best use of your strengths and opportunities, whilst addressing weaknesses and threats.

Go Deeper: SWOT Analysis Examples

17. Scenario Planning

Scenario planning is a strategic planning method used to make flexible long-term plans.

It involves imagining, and then planning for, multiple likely future scenarios.

By forecasting various directions a problem could take, scenario planning helps manage uncertainty and is an effective tool for problem-solving in volatile conditions.

18. Six Thinking Hats

The Six Thinking Hats is a concept devised by Edward de Bono that proposes six different directions or modes of thinking, symbolized by six different hat colors.

Each hat signifies a different perspective, encouraging you to switch ‘thinking modes’ as you switch hats. This method can help remove bias and broaden perspectives when dealing with a problem.

19. Decision Matrix Analysis

Decision Matrix Analysis is a technique that allows you to weigh different factors when faced with several possible solutions.

After listing down the options and determining the factors of importance, each option is scored based on each factor.

Revealing a clear winner that both serves your objectives and reflects your values, Decision Matrix Analysis grounds your problem-solving process in objectivity and comprehensiveness.

20. Pareto Analysis

Also known as the 80/20 rule, Pareto Analysis is a decision-making technique.

It’s based on the principle that 80% of problems are typically caused by 20% of the causes, making it a handy tool for identifying the most significant issues in a situation.

Using this analysis, you’re likely to direct your problem-solving efforts more effectively, tackling the root causes producing most of the problem’s impact.

21. Critical Thinking

Critical thinking refers to the ability to analyze facts to form a judgment objectively.

It involves logical, disciplined thinking that is clear, rational, open-minded, and informed by evidence.

For problem-solving, critical thinking helps evaluate options and decide the most effective solution. It ensures your decisions are grounded in reason and facts, and not biased or irrational assumptions.

Go Deeper: Critical Thinking Examples

22. Hypothesis Testing

Hypothesis testing usually involves formulating a claim, testing it against actual data, and deciding whether to accept or reject the claim based on the results.

In problem-solving, hypotheses often represent potential solutions. Hypothesis testing provides verification, giving a statistical basis for decision-making and problem resolution.

Usually, this will require research methods and a scientific approach to see whether the hypothesis stands up or not.

Go Deeper: Types of Hypothesis Testing

23. Cost-Benefit Analysis

A cost-benefit analysis (CBA) is a systematic process of weighing the pros and cons of different solutions in terms of their potential costs and benefits.

It allows you to measure the positive effects against the negatives and informs your problem-solving strategy.

By using CBA, you can identify which solution offers the greatest benefit for the least cost, significantly improving efficacy and efficiency in your problem-solving process.

Go Deeper: Cost-Benefit Analysis Examples

24. Simulation and Modeling

Simulations and models allow you to create a simplified replica of real-world systems to test outcomes under controlled conditions.

In problem-solving, you can broadly understand potential repercussions of different solutions before implementation.

It offers a cost-effective way to predict the impacts of your decisions, minimizing potential risks associated with various solutions.

25. Delphi Method

The Delphi Method is a structured communication technique used to gather expert opinions.

The method involves a group of experts who respond to questionnaires about a problem. The responses are aggregated and shared with the group, and the process repeats until a consensus is reached.

This method of problem solving can provide a diverse range of insights and solutions, shaped by the wisdom of a collective expert group.

26. Cross-functional Team Collaboration

Cross-functional team collaboration involves individuals from different departments or areas of expertise coming together to solve a common problem or achieve a shared goal.

When you bring diverse skills, knowledge, and perspectives to a problem, it can lead to a more comprehensive and innovative solution.

In problem-solving, this promotes communal thinking and ensures that solutions are inclusive and holistic, with various aspects of the problem being addressed.

27. Benchmarking

Benchmarking involves comparing one’s business processes and performance metrics to the best practices from other companies or industries.

In problem-solving, it allows you to identify gaps in your own processes, determine how others have solved similar problems, and apply those solutions that have proven to be successful.

It also allows you to compare yourself to the best (the benchmark) and assess where you’re not as good.

28. Pros-Cons Lists

A pro-con analysis aids in problem-solving by weighing the advantages (pros) and disadvantages (cons) of various possible solutions.

This simple but powerful tool helps in making a balanced, informed decision.

When confronted with a problem, a pro-con analysis can guide you through the decision-making process, ensuring all possible outcomes and implications are scrutinized before arriving at the optimal solution. Thus, it helps to make the problem-solving process both methodical and comprehensive.

29. 5 Whys Analysis

The 5 Whys Analysis involves repeatedly asking the question ‘why’ (around five times) to peel away the layers of an issue and discover the root cause of a problem.

As a problem-solving technique, it enables you to delve into details that you might otherwise overlook and offers a simple, yet powerful, approach to uncover the origin of a problem.

For example, if your task is to find out why a product isn’t selling your first answer might be: “because customers don’t want it”, then you ask why again – “they don’t want it because it doesn’t solve their problem”, then why again – “because the product is missing a certain feature” … and so on, until you get to the root “why”.

30. Gap Analysis

Gap analysis entails comparing current performance with potential or desired performance.

You’re identifying the ‘gaps’, or the differences, between where you are and where you want to be.

In terms of problem-solving, a Gap Analysis can help identify key areas for improvement and design a roadmap of how to get from the current state to the desired one.

31. Design Thinking

Design thinking is a problem-solving approach that involves empathy, experimentation, and iteration.

The process focuses on understanding user needs, challenging assumptions , and redefining problems from a user-centric perspective.

In problem-solving, design thinking uncovers innovative solutions that may not have been initially apparent and ensures the solution is tailored to the needs of those affected by the issue.

32. Analogical Thinking

Analogical thinking involves the transfer of information from a particular subject (the analogue or source) to another particular subject (the target).

In problem-solving, you’re drawing parallels between similar situations and applying the problem-solving techniques used in one situation to the other.

Thus, it allows you to apply proven strategies to new, but related problems.

33. Lateral Thinking

Lateral thinking requires looking at a situation or problem from a unique, sometimes abstract, often non-sequential viewpoint.

Unlike traditional logical thinking methods, lateral thinking encourages you to employ creative and out-of-the-box techniques.

In solving problems, this type of thinking boosts ingenuity and drives innovation, often leading to novel and effective solutions.

Go Deeper: Lateral Thinking Examples

34. Flowcharting

Flowcharting is the process of visually mapping a process or procedure.

This form of diagram can show every step of a system, process, or workflow, enabling an easy tracking of the progress.

As a problem-solving tool, flowcharts help identify bottlenecks or inefficiencies in a process, guiding improved strategies and providing clarity on task ownership and process outcomes.

35. Multivoting

Multivoting, or N/3 voting, is a method where participants reduce a large list of ideas to a prioritized shortlist by casting multiple votes.

This voting system elevates the most preferred options for further consideration and decision-making.

As a problem-solving technique, multivoting allows a group to narrow options and focus on the most promising solutions, ensuring more effective and democratic decision-making.

36. Force Field Analysis

Force Field Analysis is a decision-making technique that identifies the forces for and against change when contemplating a decision.

The ‘forces’ represent the differing factors that can drive or hinder change.

In problem-solving, Force Field Analysis allows you to understand the entirety of the context, favoring a balanced view over a one-sided perspective. A comprehensive view of all the forces at play can lead to better-informed problem-solving decisions.

TRIZ, which stands for “The Theory of Inventive Problem Solving,” is a problem-solving, analysis, and forecasting methodology.

It focuses on finding contradictions inherent in a scenario. Then, you work toward eliminating the contraditions through finding innovative solutions.

So, when you’re tackling a problem, TRIZ provides a disciplined, systematic approach that aims for ideal solutions and not just acceptable ones. Using TRIZ, you can leverage patterns of problem-solving that have proven effective in different cases, pivoting them to solve the problem at hand.

38. A3 Problem Solving

A3 Problem Solving, derived from Lean Management, is a structured method that uses a single sheet of A3-sized paper to document knowledge from a problem-solving process.

Named after the international paper size standard of A3 (or 11-inch by 17-inch paper), it succinctly records all key details of the problem-solving process from problem description to the root cause and corrective actions.

Used in problem-solving, this provides a straightforward and logical structure for addressing the problem, facilitating communication between team members, ensuring all critical details are included, and providing a record of decisions made.

39. Scenario Analysis

Scenario Analysis is all about predicting different possible future events depending upon your decision.

To do this, you look at each course of action and try to identify the most likely outcomes or scenarios down the track if you take that course of action.

This technique helps forecast the impacts of various strategies, playing each out to their (logical or potential) end. It’s a good strategy for project managers who need to keep a firm eye on the horizon at all times.

When solving problems, Scenario Analysis assists in preparing for uncertainties, making sure your solution remains viable, regardless of changes in circumstances.

How to Answer “Demonstrate Problem-Solving Skills” in an Interview

When asked to demonstrate your problem-solving skills in an interview, the STAR method often proves useful. STAR stands for Situation, Task, Action, and Result.

Situation: Begin by describing a specific circumstance or challenge you encountered. Make sure to provide enough detail to allow the interviewer a clear understanding. You should select an event that adequately showcases your problem-solving abilities.

For instance, “In my previous role as a project manager, we faced a significant issue when our key supplier abruptly went out of business.”

Task: Explain what your responsibilities were in that situation. This serves to provide context, allowing the interviewer to understand your role and the expectations placed upon you.

For instance, “It was my task to ensure the project remained on track despite this setback. Alternative suppliers needed to be found without sacrificing quality or significantly increasing costs.”

Action: Describe the steps you took to manage the problem. Highlight your problem-solving process. Mention any creative approaches or techniques that you used.

For instance, “I conducted thorough research to identify potential new suppliers. After creating a shortlist, I initiated contact, negotiated terms, assessed samples for quality and made a selection. I also worked closely with the team to re-adjust the project timeline.”

Result: Share the outcomes of your actions. How did the situation end? Did your actions lead to success? It’s particularly effective if you can quantify these results.

For instance, “As a result of my active problem solving, we were able to secure a new supplier whose costs were actually 10% cheaper and whose quality was comparable. We adjusted the project plan and managed to complete the project just two weeks later than originally planned, despite the major vendor setback.”

Remember, when you’re explaining your problem-solving skills to an interviewer, what they’re really interested in is your approach to handling difficulties, your creativity and persistence in seeking a resolution, and your ability to carry your solution through to fruition. Tailoring your story to highlight these aspects will help exemplify your problem-solving prowess.

Go Deeper: STAR Interview Method Examples

Benefits of Problem-Solving

Problem-solving is beneficial for the following reasons (among others):

It can help you to overcome challenges, roadblocks, and bottlenecks in your life.
It can save a company money.
It can help you to achieve clarity in your thinking.
It can make procedures more efficient and save time.
It can strengthen your decision-making capacities.
It can lead to better risk management.

Whether for a job interview or school, problem-solving helps you to become a better thinking, solve your problems more effectively, and achieve your goals. Build up your problem-solving frameworks (I presented over 40 in this piece for you!) and work on applying them in real-life situations.

Chris Drew (PhD) https://helpfulprofessor.com/author/chris-drew-phd-2/ 25 Number Games for Kids (Free and Easy)
Chris Drew (PhD) https://helpfulprofessor.com/author/chris-drew-phd-2/ 25 Word Games for Kids (Free and Easy)
Chris Drew (PhD) https://helpfulprofessor.com/author/chris-drew-phd-2/ 25 Outdoor Games for Kids
Chris Drew (PhD) https://helpfulprofessor.com/author/chris-drew-phd-2/ 50 Incentives to Give to Students

The differences between structured and unstructured problems

Here you will find three differences between structured and unstructured problems, each described with appropriate examples:

Difference 1: Clarity of the problem

Structured problems are clearly defined and usually well understood. They have a clear problem, known variables, and can usually be well described. Structured problems are often easier to solve because they are based on established rules, processes, or algorithms.

Example: A company wants to calculate the break-even point for a certain product. It knows the variable costs, the fixed costs and the selling price of the product. The problem is clearly defined and the calculation of the break-even point can be performed using a known formula.

Unstructured problems , on the other hand, are often unclear, vague, or poorly defined. They contain many unknown or difficult-to-measure variables and may change over time. Unstructured problems are usually more difficult to solve because they are not based on established rules or processes and often require creative or innovative approaches.

Example: A company notices that employee motivation has dropped recently, but cannot identify the exact reasons. This problem is unclear and requires in-depth study to identify the factors contributing to declining motivation and to develop appropriate measures to improve the situation.

Difference 2: Complexity

Structured problems are usually less complex because they are based on known parameters and a fixed solution path. They can usually be broken down into smaller, more easily detachable parts. Example: A company has a limited number of advertising spaces in various media and wants to allocate the optimal advertising budget among these media to achieve the highest possible reach. This problem can be solved using linear programming techniques based on known data and goals.

Unstructured problems are often more complex because they are influenced by multiple, interrelated factors and do not have a unique solution. They require a high level of critical thinking, analysis, and creative problem solving to arrive at a solution. Example: A company wants to develop a completely new business idea in order to survive in a competitive market. This problem is complex because there are many unknown variables and factors that can affect the success of the business idea. It takes creativity, market research and experimentation to develop a promising business idea.

Difference 3: Solution approaches

Structured problems can usually be solved by standardized, linear solution approaches based on established rules or algorithms. These include mathematical models, process diagrams, and other systematic approaches. Example: A company wants to optimize its inventories to avoid both overstocks and delivery bottlenecks. There are standardized solution approaches that can be applied to optimize inventories.

Unstructured problems , on the other hand, require creative, innovative and often unconventional approaches to solving them. These include brainstorming, design thinking, and other collaborative, experimental methods. Unstructured problems may also require a combination of different approaches and interdisciplinary thinking to find a successful solution. Example: A company wants to improve its corporate culture in order to increase employee satisfaction and retention. There is no set solution or formula to solve this problem. Instead, different approaches need to be tried, such as improving internal communication, introducing flexible working hours or creating opportunities for professional development.

Reasons for the increase in unstructured problems

There are different reasons for the increase of unstructured problems, especially in the business context. Some of them are:

Growing complexity

The world is becoming increasingly interconnected and complex, and companies must deal with a variety of factors such as global markets, new technologies and changing customer needs. These factors can lead to unstructured problems as it becomes more difficult to find clear solutions to complex challenges.

Faster change

Technological advances and globalization have led to an increased pace of change in many industries. Companies need to adapt quickly to new trends and developments, which can lead to unstructured problems for which there are no defined solutions.

Competitive pressure

Increasing competition in global markets is forcing companies to constantly evolve and find new ways to stand out from the competition. This can lead to companies facing unstructured problems when trying to develop innovative products, services or business models.

Information overload

The abundance of information available in today’s world can make it difficult to distinguish relevant information from unimportant information and make informed decisions based on that information. This can exacerbate unstructured problems, as solving such problems often requires the ability to effectively analyze and use a variety of information.

Increasing customer demands

Customers today are better informed and have higher expectations of products and services. Companies must meet these increasing demands and develop innovative solutions to satisfy their customers. This can create unstructured problems as there are no set solutions to meet the different needs and wants of all customers.

Unstructured problems as a challenge in the daily work routine

Many people have difficulty coping with unstructured problems. Especially when they occur in high-pressure situations, the following behaviors can be observed:

Individuals who have difficulty tackling unstructured problems tend to be indecisive. They have a hard time making decisions. This leads them to endlessly collect and analyze information without ever arriving at a solution or decision (also known as “analysis paralysis”).

Inflexibility

Some people are less open to change and new ideas and have difficulty adapting their thinking and approaches in complex situations. This inflexibility can make it difficult to effectively manage unstructured problems, as such problems often require creative and unconventional solutions. Here, brainstorming methods often help to expand the corridor of thought.

Frustration and stress

Unstructured problems can be overwhelming for some people because they bring uncertainty and complexity. This often leads to stress and frustration when confronted with such problems, which in turn can further impair their problem-solving abilities. A spiral of frustration can develop.

Quick judgment

Some people are quick to jump to conclusions and commit to a particular solution without thoroughly analyzing the problem and considering different approaches. This behavior can lead them to find less effective solutions to unstructured problems.

Some people prefer to work on problems alone rather than seek collaboration and exchange with others. However, this can be less effective for unstructured problems, as sharing knowledge and experience often helps to find better solutions. While there are ideation methods like the Lateral Map that produce good results on their own, the quality of the solutions is always improved by the different perspectives in a multidisciplinary team.

Focus on details

Some people tend to focus on details and particulars instead of seeing the big picture. For unstructured problems, this focus on detail can cause them to lose track of the underlying problem and have difficulty prioritizing. Helpful here is often a method such as the well-known mind mapping , which brings information coherently into an overview.

Risk aversion

Some people shy away from experimentation and unconventional approaches that can be helpful in dealing with unstructured problems. This risk aversion can lead them to focus on proven and known solutions that may be less effective at solving complex and unstructured problems.

Thinking and behavioral approaches to solving unstructured problems.

Problem analysis: At the beginning, try to analyze the problem in detail and identify all relevant factors and variables. Use methods like the mind map to make all information visible. Write down questions, gather information, and look for connections to better understand the problem. The Ishikawa diagram can help to understand causes and effects. If you don’t like the problem, use the Problem Tackler , which turns difficult problems into exciting challenges.

Creative thinking: When working with unstructured problems, it helps to think creatively and innovatively to find new solutions. Unstructured problems require a great openness to unconventional ideas and approaches that go beyond the traditional framework. Exciting methods for your team here are the stimulus image method , SCAMPER or even the Force Fit Game . Often referred to in this context is lateral thinking, an approach that aims to find unusual or unconventional solutions to problems by exploring new perspectives and ways of thinking. Lateral thinking encourages thinking outside the box and discovering unexpected connections or ideas that can lead to innovative solutions.

Critical Thinking: Critical thinking helps to think logically and in a structured way about a problem, questioning hypotheses, assumptions, and conclusions. This approach encourages a thorough analysis of the problem and evaluation of alternative solutions based on facts and evidence.

Hypothesis-based thinking: This approach involves making hypotheses or assumptions about the problem and then systematically testing them to determine their validity. This can help reduce uncertainty in unstructured problems and speed up problem solving.

Adaptability: In the face of unstructured problems, flexibility and adaptability is an important personality trait. Your willingness is needed to change strategies and approaches as new information or circumstances arise. Be open to learning from mistakes and setbacks, thinking approaches like the Lean Startup Method can help.

Collaboration: When faced with unstructured problems, many people seek collaboration and exchange with others. Working together and sharing knowledge and experience can lead to better solutions in many cases. Methods such as the team thermometer help to understand team dynamics and make them visible.

Perseverance: Unstructured problems can be frustrating and difficult. A high level of perseverance and persistence is necessary for the solution. You must be willing to continue to deal with the problem even if you encounter difficulties or do not find an immediate solution.

Experimenting and testing: When tackling unstructured problems, experimenting and testing different approaches and solutions is an important activity. To do this, it is important to be willing to take risks and analyze the results of experiments in order to continuously learn and adapt your strategies. Retrospectives or techniques like the AAR review are helpful here.

Focus on the big picture: try to see the big picture and look at the problem in the context of its environment and its long-term impact. Prioritize and focus on the most important aspects of the problem without getting lost in details.

Design Thinking: Design thinking is a user-centered approach that aims to solve problems by understanding the needs and wants of users or customers. This approach includes various phases such as empathy, problem definition, ideation, prototyping, and testing to iteratively arrive at solutions that meet user needs.

Sammelpunkt für Innovations-Know-How. Toolbox für Innnovationsprofis.

Get Started

Innovation Wiki
verrocchio Institute
Innovation Coaching
Kostenfreie Tools

My Account (Pro User)

Subscription
Passwort ändern
Deutsch ( German )

Regularized and Structured Tensor Total Least Squares Methods with Applications

Published: 12 August 2024

Cite this article

Feiyang Han 1 ,
Yimin Wei ORCID: orcid.org/0000-0001-6192-0546 2 &
Pengpeng Xie 3

Total least squares (TLS), also named as errors in variables in statistical analysis, is an effective method for solving linear equations with the situations, when noise is not just in observation data but also in mapping operations. Besides, the Tikhonov regularization is widely considered in plenty of ill-posed problems. Moreover, the structure of mapping operator plays a crucial role in solving the TLS problem. Tensor operators have some advantages over the characterization of models, which requires us to build the corresponding theory on the tensor TLS. This paper proposes tensor regularized TLS and structured tensor TLS methods for solving ill-conditioned and structured tensor equations, respectively, adopting a tensor-tensor-product. Properties and algorithms for the solution of these approaches are also presented and proved. Based on this method, some applications in image and video deblurring are explored. Numerical examples illustrate the effectiveness of our methods, compared with some existing methods.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save.

Get 10 units per month
Download Article/Chapter or eBook
1 Unit = 1 Article or 1 Chapter
Cancel anytime

Price includes VAT (Russian Federation)

Instant access to the full article PDF.

Rent this article via DeepDyve

Institutional subscriptions

A Tensor Regularized Nuclear Norm Method for Image and Video Completion

A faster tensor robust PCA via tensor factorization

Augmented Lagrangian method for tensor low-rank and sparsity models in multi-dimensional image recovery

Data availibility.

All datasets are publicly available.

Badeau, R., Boyer, R.: Fast multilinear singular value decomposition for structured tensors. SIAM J. Matrix Anal. Appl. 30 , 1008–1021 (2008)

Article MathSciNet Google Scholar

Beck, A., Ben-Tal, A.: A global solution for the structured total least squares problem with block circulant matrices. SIAM J. Matrix Anal. Appl. 27 , 238–255 (2005)

Beck, A., Ben-Tal, A.: On the solution of the Tikhonov regularization of the total least squares problem. SIAM J. Optim. 17 , 98–118 (2006)

Beik, F.P.A., El Ichi, A., Jbilou, K., Sadaka, R.: Tensor extrapolation methods with applications. Numer. Algorithms 87 , 1421–1444 (2021)

Beik, F.P.A., Jbilou, K., Najafi-Kalyani, M., Reichel, L.: Golub-Kahan bidiagonalization for ill-conditioned tensor equations with applications. Numer. Algorithms 84 , 1535–1563 (2020)

Bentbib, A.H., Hachimi, A.E., Jbilou, K., Ratnani, A.: A tensor regularized nuclear norm method for image and video completion. J. Optim. Theory Appl. 192 , 401–425 (2022)

Betcke, T., Higham, N.J., Mehrmann, V., Schröder, C., Tisseur, F.: NLEVP: a collection of nonlinear eigenvalue problems. ACM Trans. Math. Softw. TOMS 39 , 1–28 (2013)

Cai, Y., Zhang, L.-H., Bai, Z., Li, R.-C.: On an eigenvector-dependent nonlinear eigenvalue problem. SIAM J. Matrix Anal. Appl. 39 , 1360–1382 (2018)

Che, M., Wang, X., Wei, Y., Zhao, X.: Fast randomized tensor singular value thresholding for low-rank tensor optimization. Numer. Linear Algebra Appl. 29 , e24441 (2022)

Che, M., Wei, Y.: An efficient algorithm for computing the approximate t-URV and its applications. J. Sci. Comput. 92 , 93 (2022)

Chen, X., Qin, J.: Regularized Kaczmarz algorithms for tensor recovery. SIAM J. Imaging Sci. 14 , 1439–1471 (2021)

De Lathauwer, L., de Baynast, A.: Blind deconvolution of DS-CDMA signals by means of decomposition in rank-(1, l, l) terms. IEEE Trans. Signal Process. 56 , 1562–1571 (2008)

De Moor, B.: Structured total least squares and $l_2$ approximation problems. Linear Algebra Appl. 188 (189), 163–207 (1993)

Doicu, A., Trautmann, T., Schreier, F.: Numerical Regularization for Atmospheric Inverse Problems. Springer Science & Business Media, Berlin (2010)

Book Google Scholar

El Guide, M., El Ichi, A., Jbilou, K., Sadaka, R.: On tensor GMRES and Golub-Kahan methods via the t-product for color image processing. Electron. J. Linear Algebra 37 , 524–543 (2021)

El Guide, M., Jbilou, K., Ratnani, A.: RBF approximation of three dimensional PDEs using tensor Krylov subspace methods. Eng. Anal. Bound. Elem. 139 , 77–85 (2022)

Fierro, R.D., Golub, G.H., Hansen, P.C., O’Leary, D.P.: Regularization by truncated total least squares. SIAM J. Sci. Comput. 18 , 1223–1241 (1997)

Gazagnadou, N., Ibrahim, M., Gower, R.M.: RidgeSketch: a fast sketching based solver for large scale ridge regression. SIAM J. Matrix Anal. Appl. 43 , 1440–1468 (2022)

Golub, G.H., Hansen, P.C., O’Leary, D.P.: Tikhonov regularization and total least squares. SIAM J. Matrix Anal. Appl. 21 , 185–194 (1999)

Golub, G.H., Van Loan, C.F.: An analysis of the total least squares problem. SIAM J. Numer. Anal. 17 , 883–893 (1980)

Golub, G.H., Van Loan, C.F.: Matrix Computations, 4th edn. The Johns Hopkins University Press, Baltimore (2013)

Gratton, S., Titley-Peloquin, D., Ilunga, J.T.: Sensitivity and conditioning of the truncated total least squares solution. SIAM J. Matrix Anal. Appl. 34 , 1257–1276 (2013)

Guhaniyogi, R., Qamar, S., Dunson, D.B.: Bayesian tensor regression. J. Mach. Learn. Res. 18 , 2733–2763 (2017)

MathSciNet Google Scholar

Guo, H., Renaut, R.A.: A regularized total least squares algorithm. In: Total Least Squares and Errors-in-Variables Modeling, pp. 57–66. Springer, Berlin (2002)

Chapter Google Scholar

Han, F., Wei, Y.: TLS-EM algorithm of mixture density models for exponential families. J. Comput. Appl. Math. 403 , 113829 (2022)

Hao, N., Kilmer, M.E., Braman, K., Hoover, R.C.: Facial recognition using tensor-tensor decompositions. SIAM J. Imaging Sci. 6 , 437–463 (2013)

Hnětynková, I., Plešinger, M., Žáková, J.: TLS formulation and core reduction for problems with structured right-hand sides. Linear Algebra Appl. 555 , 241–265 (2018)

Hnětynková, I., Plešinger, M., Žáková, J.: On TLS formulation and core reduction for data fitting with generalized models. Linear Algebra Appl. 577 , 1–20 (2019)

Hnětynková, I., Plešinger, M., Žáková, J.: Krylov subspace approach to core problems within multilinear approximation problems: a unifying framework. SIAM J. Matrix Anal. Appl. 44 , 53–79 (2023)

Ichi, A.E., Jbilou, K., Sadaka, R.: On tensor tubal-Krylov subspace methods. Linear Multilinear Algebra 70 , 7575–7598 (2022)

Jarlebring, E., Kvaal, S., Michiels, W.: An inverse iteration method for eigenvalue problems with eigenvector nonlinearities. SIAM J. Sci. Comput. 36 , A1978–A2001 (2014)

Kilmer, M.E., Braman, K., Hao, N., Hoover, R.C.: Third-order tensors as operators on matrices: a theoretical and computational framework with applications in imaging. SIAM J. Matrix Anal. Appl. 34 , 148–172 (2013)

Kilmer, M.E., Martin, C.D.: Factorization strategies for third-order tensors. Linear Algebra Appl. 435 , 641–658 (2011)

Li, N., Kindermann, S., Navasca, C.: Some convergence results on the regularized alternating least-squares method for tensor decomposition. Linear Algebra Appl. 438 , 796–812 (2013)

Li, X., Ng, M.K.: Solving sparse non-negative tensor equations: algorithms and applications. Front. Math. China 10 , 649–680 (2015)

Lock, E.F.: Tensor-on-tensor regression. J. Comput. Graph. Stat. 27 , 638–647 (2018)

Lu, C., Feng, J., Chen, Y., Liu, W., Lin, Z., Yan, S.: Tensor robust principal component analysis: exact recovery of corrupted low-rank tensors via convex optimization. In: Proceedings of the IEEE Conference on Computer Vision and Pattern Recognition, pp. 5249–5257 (2016)

Lu, C., Feng, J., Chen, Y., Liu, W., Lin, Z., Yan, S.: Tensor robust principal component analysis with a new tensor nuclear norm. IEEE Trans. Pattern Anal. Mach. Intell. 42 , 925–938 (2019)

Article Google Scholar

Lu, S., Pereverzev, S.V., Tautenhahn, U.: Regularized total least squares: computational aspects and error bounds. SIAM J. Matrix Anal. Appl. 31 , 918–941 (2010)

Lund, K.: The tensor t-function: a definition for functions of third-order tensors. Numer. Linear Algebra Appl. 27 , e2288 (2020)

Ma, A., Molitor, D.: Randomized Kaczmarz for tensor linear systems. BIT Numer. Math. 62 , 171–194 (2022)

Martin, C.D., Shafer, R., LaRue, B.: An order-p tensor factorization with applications in imaging. SIAM J. Sci. Comput. 35 , A474–A490 (2013)

Mastronardi, N., Lemmerling, P., Van Huffel, S.: Fast structured total least squares algorithm for solving the basic deconvolution problem. SIAM J. Matrix Anal. Appl. 22 , 533–553 (2000)

Mehrmann, V., Voss, H.: Nonlinear eigenvalue problems: a challenge for modern eigenvalue methods. GAMM Mitt. 27 , 121–152 (2004)

Miao, Y., Qi, L., Wei, Y.: Generalized tensor function via the tensor singular value decomposition based on the T-product. Linear Algebra Appl. 590 , 258–303 (2020)

Miao, Y., Qi, L., Wei, Y.: T-Jordan canonical form and T-Drazin inverse based on the T-product. Commun. Appl. Math. Comput. 3 , 201–220 (2021)

Miao, Y., Wang, T., Wei, Y.: Stochastic conditioning of tensor functions based on the tensor-tensor product. Pac. J. Optim. 19 , 205–235 (2023)

Newman, E., Horesh, L., Avron, H., Kilmer, M.: Stable tensor neural networks for rapid deep learning. arXiv preprint arXiv:1811.06569 (2018)

Newman, E., Kilmer, M., Horesh, L.: Image classification using local tensor singular value decompositions. In: 2017 IEEE 7th International Workshop on Computational Advances in Multi-Sensor Adaptive Processing (CAMSAP), pp. 1–5 (2017)

Reichel, L., Ugwu, U.O.: Tensor Krylov subspace methods with an invertible linear transform product applied to image processing. Appl. Numer. Math. 166 , 186–207 (2021)

Reichel, L., Ugwu, U.O.: The tensor Golub-Kahan-Tikhonov method applied to the solution of ill-posed problems with a t-product structure. Numer. Linear Algebra Appl. 29 , e2412 (2022)

Reichel, L., Ugwu, U.O.: Weighted tensor Golub–Kahan–Tikhonov-type methods applied to image processing using a T-product. J. Comput. Appl. Math. 415 , 114488 (2022)

Renaut, R.A., Guo, H.: Efficient algorithms for solution of regularized total least squares. SIAM J. Matrix Anal. Appl. 26 , 457–476 (2004)

Rosen, J.B., Park, H., Glick, J.: Total least norm formulation and solution for structured problems. SIAM J. Matrix Anal. Appl. 17 , 110–126 (1996)

Sima, D.M., Van Huffel, S., Golub, G.H.: Regularized total least squares based on quadratic eigenvalue problem solvers. BIT Numer. Math. 44 , 793–812 (2004)

Stewart, G.W.: Updating a rank-revealing ULV decomposition. SIAM J. Matrix Anal. Appl. 14 , 494–499 (1993)

Van Huffel, S. (ed.): Recent Advances in Total Least Squares Techniques and Errors-in-Variables Modeling. Society for Industrial and Applied Mathematics, Philadelphia (1997)

Google Scholar

Van Huffel, S., Lemmerling, P. (eds.): Total Least Squares and Errors-in-Variables Modeling: Analysis, Algorithms and Applications. Kluwer Academic Publishers, Dordrecht (2002)

Van Huffel, S., Vandewalle, J.: Algebraic relationships between classical regression and total least-squares estimation. Linear Algebra Appl. 93 , 149–160 (1987)

Van Huffel, S., Vandewalle, J.: The Total Least Squares Problem: Computational Aspects and Analysis. SIAM, Philadelphia (1991)

Vasilescu, M.A.O., Terzopoulos, D.: Multilinear analysis of image ensembles: TensorFaces. In: European Conference on Computer Vision, pp. 447–460. Springer (2002)

Voss, H.: Nonlinear eigenvalue problems. In: Hogben, L. (ed.) Handbook of Linear Algebra, 2nd edn. CRC Press, Boca Raton (2014)

Wang, X., Che, M., Wei, Y.: Tensor neural network models for tensor singular value decompositions. Comput. Optim. Appl. 75 , 753–777 (2020)

Wang, X., Wei, P., Wei, Y.: A fixed point iterative method for third-order tensor linear complementarity problems. J. Optim. Theory Appl. 197 , 334–357 (2023)

Wei, P., Wang, X., Wei, Y.: Neural network models for time-varying tensor complementarity problems. Neurocomputing 523 , 18–32 (2023)

Xie, P., Xiang, H., Wei, Y.: Randomized algorithms for total least squares problems. Numer. Linear Algebra Appl. 26 , e2219 (2019)

Zare, H., Hajarian, M.: An efficient Gauss-Newton algorithm for solving regularized total least squares problems. Numer. Algorithms 89 , 1049–1073 (2022)

Zhang, Z., Aeron, S.: Exact tensor completion using t-SVD. IEEE Trans. Signal Process. 65 , 1511–1526 (2016)

Zhang, Z., Ely, G., Aeron, S., Hao, N., Kilmer, M.: Novel methods for multilinear data completion and de-noising based on tensor-SVD. In: Proceedings of the IEEE Conference on Computer Vision and Pattern Recognition, pp. 3842–3849 (2014)

Zhou, H., Li, L., Zhu, H.: Tensor regression with applications in neuroimaging data analysis. J. Am. Stat. Assoc. 108 , 540–552 (2013)

Zhou, P., Lu, C., Lin, Z., Zhang, C.: Tensor factorization for low-rank tensor completion. IEEE Trans. Image Process. 27 , 1152–1163 (2017)

Download references

Acknowledgements

We would like to thank the handling editor and two referees for their detailed comments. We also thank Professors Ren-cang Li, Tie-xiang Li, Wen-wei Lin, Qiang Ye and Lei-hong Zhang for their useful suggestions. F. Han is supported by the Science and Technology Commission of Shanghai Municipality under Grant 23JC1400501 and Joint Research Project between China and Serbia under the Grant 2024-6-7. Y. Wei is supported by the National Natural Science Foundation of China under Grant 12271108 and the Ministry of Science and Technology of China under Grant G2023132005L. P. Xie is supported by the National Natural Science Foundation of China under Grant 12271108. Partial work is finished when he visited Fudan University during 2023–2024.

Author information

Authors and affiliations.

School of Mathematical Sciences, Fudan University, Shanghai, 200433, People’s Republic of China

Feiyang Han

School of Mathematical Sciences and Key Laboratory of Mathematics for Nonlinear Sciences, Fudan University, Shanghai, 200433, People’s Republic of China

School of Mathematical Sciences, Ocean University of China, Qingdao, 266100, People’s Republic of China

Pengpeng Xie

You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Yimin Wei .

Ethics declarations

Conflict of interest.

The authors declare that they have no known competing financial interests or personal relationships that could have appeared to influence the work reported in this paper.

Additional information

Communicated by Charles Dossal.

Publisher's Note

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Rights and permissions

Springer Nature or its licensor (e.g. a society or other partner) holds exclusive rights to this article under a publishing agreement with the author(s) or other rightsholder(s); author self-archiving of the accepted manuscript version of this article is solely governed by the terms of such publishing agreement and applicable law.

Reprints and permissions

About this article

Han, F., Wei, Y. & Xie, P. Regularized and Structured Tensor Total Least Squares Methods with Applications. J Optim Theory Appl (2024). https://doi.org/10.1007/s10957-024-02507-1

Download citation

Received : 17 February 2023

Accepted : 20 July 2024

Published : 12 August 2024

DOI : https://doi.org/10.1007/s10957-024-02507-1

Share this article

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

Total least squares
Tikhonov regularization
Structure modeling
Tensor T-product
Image deblurring

Mathematics Subject Classification

Find a journal
Publish with us
Track your research

IMAGES

structured problem solving techniques
Structured Problem Solving Examples In Powerpoint And Google Slides Cpb
Problem-Solving Strategies: Definition and 5 Techniques to Try
Structured Problem-Solving
The Complete Guide to Structured Problem Solving
Technique 6.1: Structured Problem Solving

COMMENTS

Structured problem solving strategies can help break down problems to
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 ...
McKinsey Problem Solving: Six Steps To Think Like A ...
For example, you are asked to write a 5 page paper on Benjamin Franklin — double spaced, 12 font and answering two or three specific questions. ... The pyramid principle is an approach popularized by Barbara Minto and essential to the structured problem solving approach I learned at McKinsey. Learning this approach has changed the way I look ...
Guide: A3 Problem Solving
The A3 is a problem-solving tool that encourages a collaborative and systematic approach to problem-solving. The term A3 comes from the paper size which is roughly 11″ by 17″ and used to map out the problem-solving process on a single sheet of paper. The A3 paper size is used as a single-page constraint that ensures the team focus on the ...
The Complete Guide to Structured Problem Solving
Structured problem solving allows you to explore the problem, get to the heart of the issue, and develop a creative solution that finally solves the issue. Photo by Kaleidico on Unsplash. To illustrate this example, Takashi Amano was a nature photographer and avid aquarist. He started developing art in the form of fish tanks - which he called ...
The Basics of Structured Problem-Solving Methodologies: DMAIC & 8D
This methodology provides a structured five-phase framework when working on an improvement project. It focuses on improving an existing process, rather than creating a new product or process. DMAIC is best suited for a complex problem, or if the risk is high. 8D. 8D is known as the Eight Disciplines of problem-solving.
Six Steps to Structured Problem Solving
This is the most time-consuming, but one of the most vital steps in the process as we take each potential cause and work to rule it out. We must keep working until we have eliminated everything but the root cause. 4. Verify Root Cause. When we think that we have identified the true root cause, we need verify that it is the root cause by testing ...
A3 Thinking: A Structured Approach to Problem Solving
A3 thinking involves the practice of consolidating the problem, analysis, countermeasures, and action plan onto a single sheet of paper, commonly an A3-sized sheet. This brief document serves as a summary of the project at hand and is regarded as a valuable storytelling tool for project communication. Utilizing the A3 approach doesn't require ...
Structured Approach to Problem Solving
By the end of this course, you will be able to: 1. Explain the different stages of a data science project 2. Discuss some of the tools and techniques used in data science. 3. Apply structured thinking to solving problems and avoid the common traps while doing so 4. Apply human-centric design in problem-solving.
Structured Thinking 101: How to Apply It to Everything You Do
Execute your plan. Make the bookings and visualize your timeline. This is where everything comes together and you see the benefits of your planning. Let's recap: we started with a clear goal and broke it into smaller, manageable tasks. This is structured thinking, and we just created a framework for planning a trip.
Structured Problem Solving Methods : eLearning Skills 2030
2. DMAIC. The DMAIC process is a data-driven structured problem-solving approach used to identify bottlenecks and improve processes. While the DMAIC process originated in the Six Sigma methodology, it can be used as a stand-alone process to solve a problem. DMAIC includes five steps: define, measure, analyze, improve, and control.
40 problem-solving techniques and processes
7. Solution evaluation. 1. Problem identification. The first stage of any problem solving process is to identify the problem (s) you need to solve. This often looks like using group discussions and activities to help a group surface and effectively articulate the challenges they're facing and wish to resolve.
PDF Structured Problem Solving
In contrast, problem solving is when we spend some time thinking about what we can do to solve (or partially solve) a specific problem. Structured Problem Solving can help you focus on what you can do to make things better, rather than worrying. It's a useful way of defining problems, identifying potential solutions, and figuring out how you ...
Structured Problem-Solving
Structured Problem-Solving gives students a process for solving a complex, content-based problem within a specific time limit. All students must agree to a solution and be able to explain the answer and strategy used to solve the problem. ... Example 1. An Environmental Sciences professor wanted to use Structured Problem-Solving to consider the ...
A Step-by-Step Guide to A3 Problem Solving Methodology
Problem-solving is an important component of any business or organization. It entails identifying, analyzing, and resolving problems in order to improve processes, drive results, and foster a culture of continuous improvement. A3 Problem solving is one of the most effective problem-solving methodologies. A3 Problem solving is a structured and systematic approach to problem-solving that ...
What is Problem Solving? (Steps, Techniques, Examples)
The problem-solving process typically includes the following steps: Identify the issue: Recognize the problem that needs to be solved. Analyze the situation: Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present. Generate potential solutions: Brainstorm a list of possible ...
Repenning Structured Problem Solving
composition of a good problem statement and summarize the most common failure modes. Then we introduce a simple structured problem-solving method, based on the "A3" developed by Toyota. Finally, we finish with two examples from recent projects that show the power of Mr. Oba's insight. The Associative Machine
The 6 steps to structured problem solving
The 6 steps to structured problem solving Utilising a disciplined problem solving technique in bespoke software development is valuable in a few circumstances. Being able to resolve an issue for a bespoke software system can be very challenging, but at RSK BSL we work as a team or an individual to get this done. It is critical to utilise the correct way for the job that needs to be done.
26 Expert-Backed Problem Solving Examples
The example interview responses are structured using the STAR method and are categorized into the top 5 key problem-solving skills recruiters look for in a candidate. 1. Analytical Thinking. Situation: In my previous role as a data analyst, our team encountered a significant drop in website traffic.
A Structured Approach to Problem Solving
A disciplined approach ensures that essential guidelines and rules are followed. The steps offer a way to replicate success for similar problems in other areas. There are five components to the framework for structured problem solving. Understand the problem. This is the most important step in assessing the extent of the problem.
Issue Trees: Step-By-Step Guide with Examples (2024)
An issue tree is a structured framework used to break down and analyze complex problems or questions into smaller components. It is a visual representation of the various aspects, sub-issues, and potential solutions related to a particular problem. Issue trees are commonly used in business, consulting, problem-solving, and decision-making ...
7 Examples of Problem-Solving Scenarios in the Workplace (With ...
Here is an example of a problem-solving: A small business owner is experiencing a decline in sales and profitability. The owner needs to identify the reasons for the decline and develop a plan to turn the business around. To solve this problem, the owner could analyze sales data, conduct market research, identify areas of inefficiency in the ...
39 Best Problem-Solving Examples (2024)
A3 Problem Solving, derived from Lean Management, is a structured method that uses a single sheet of A3-sized paper to document knowledge from a problem-solving process. Named after the international paper size standard of A3 (or 11-inch by 17-inch paper), it succinctly records all key details of the problem-solving process from problem ...
Structured vs. unstructured problems
Difference 1: Clarity of the problem. Structured problems are clearly defined and usually well understood. They have a clear problem, known variables, and can usually be well described. Structured problems are often easier to solve because they are based on established rules, processes, or algorithms. Example: A company wants to calculate the ...
Silky Gogna
With Kaizen, we empower our teams to identify and implement daily improvements. The PDCA cycle—Plan, Do, Check, Act—guides us through structured problem-solving, ensuring sustainable results. For example, by applying Kaizen in our production line, we reduced setup times by 30%, speeding up delivery to our customers.
Regularized and Structured Tensor Total Least Squares ...
Total least squares (TLS), also named as errors in variables in statistical analysis, is an effective method for solving linear equations with the situations, when noise is not just in observation data but also in mapping operations. Besides, the Tikhonov regularization is widely considered in plenty of ill-posed problems. Moreover, the structure of mapping operator plays a crucial role in ...

How to master the seven-step problem-solving process

Want to subscribe to The McKinsey Podcast ?

Would you like to learn more about our Strategy & Corporate Finance Practice ?

Want better strategies? Become a bulletproof problem solver

Explore a career with us

Strategy to beat the odds

Five routes to more innovative problem solving

McKinsey Problem Solving: Six steps to solve any problem and tell a persuasive story

Step #1: School is over, stop worrying about “what” to make and worry about the process, or the “how”

Step #2: Thinking like a consultant requires a mindset shift

Step #3: Define the problem and make sure you are not solving a symptom

Step 4: Dive in, make hypotheses and try to figure out how to “solve” the problem

Step 5: Make a slides like a consultant

Tip #1 — Format, format, format

Tip #2 — Titles are the takeaway

Tip #3 — Have “MECE” Ideas for max persuasion

Tip #4 — Leveraging the Pyramid Principle

Step 6: The only way to improve is to get feedback and continue to practice

Share this:

The Complete Guide to Structured Problem Solving

The Basic idea of Structured Problem Solving

Why Structured Problem-Solving Works

Multiple Ways of Structured Problem Solving

Get the Creative Juices Flowing

The Structured Problem Solving Process

2. Root Cause Analysis

3. Gather Data

4. Develop Potential Solutions

5. Implement a Solution

6. Monitor for Success

Illustrated Example

Key Take-Aways

Action Item

Share this:

Post navigation

Leave a Reply Cancel reply

The Basics of Structured Problem-Solving Methodologies: DMAIC & 8D

WHAT IS STRUCTURED PROBLEM-SOLVING?

WHAT IS A STRUCTURED PROBLEM-SOLVING METHODOLOGY?

MINITAB ENGAGE, YOUR SOLUTION TO EFFECTIVE PROBLEM-SOLVING

Ready to explore structured problem-solving?

You Might Also Like

Posts by Topic

Six Steps to Structured Problem Solving

About Author

Subscribe To Blog

Recent Posts

Continuous Improvement Toolkit

A3 Thinking: A Structured Approach to Problem Solving

A3 Seven Stages Model

Wrapping Up

Project Charter

Gantt Chart

A3 Problem Solving

Structured Thinking 101: How to Apply It to Everything You Do

What is structured thinking?

Information

Recent Posts

40 problem-solving techniques and processes

Design your next session with SessionLab

Recommended Articles

What is problem solving?

What is the seven step problem solving process?

1. Problem identification

2. Problem analysis and refinement

3. Solution generation

4. Solution development

5. Decision making and planning

6. Solution implementation

7. Solution evaluation

What does an effective problem solving process look like?

Complete problem-solving methods

Six Thinking Hats

Lightning Decision Jam

Problem Definition Process

The 5 Whys

Discovery & Action Dialogue (DAD)

Open space technology

Techniques to identify and analyze problems

Fishbone Analysis