problem solving methods consulting

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.

Resources >

Mckinsey approach to problem solving.

McKinsey and Company is recognized for its rigorous approach to problem solving. They train their consultants on their seven-step process that anyone can learn.

This resource guides you through that process, largely informed by the McKinsey Staff Paper 66. It also includes a PowerPoint Toolkit with slide templates of each step of the process that you can download and customize for your own use.

You can click any section to go directly there:

Overview of the McKinsey Approach to Problem Solving

Problem solving process.

Problem Definition & Problem Statement Worksheet

Stakeholder Analysis Worksheet

Hypothesis trees, issue trees, analyses and workplan, synthesize findings, craft recommendations, distinctiveness practices, harness the power of collaboration, sources and additional reading, download the umbrex toolkit on the mckinsey approach to problem solving.

Problem solving — finding the optimal solution to a given business opportunity or challenge — is the very heart of how consultants create client impact, and considered the most important skill for success at McKinsey.

The characteristic “McKinsey method” of problem solving is a structured, inductive approach that can be used to solve any problem. Using this standardized process saves us from reinventing the problem-solving wheel, and allows for greater focus on distinctiveness in the solution. Every new McKinsey associate must learn this method on his or her first day with the firm.

There are four fundamental disciplines of the McKinsey method:

1. Problem definition

A thorough understanding and crisp definition of the problem.

2. The problem-solving process

Structuring the problem, prioritizing the issues, planning analyses, conducting analyses, synthesizing findings, and developing recommendations.

3. Distinctiveness practices

Constructing alternative perspectives; identifying relationships; distilling the essence of an issue, analysis, or recommendation; and staying ahead of others in the problem-solving process.

4. Collaboratio n

Actively seeking out client, customer, and supplier perspectives, as well as internal and external expert insight and knowledge.

Once the problem has been defined, the problem-solving process proceeds with a series of steps:

Structure the problem
Prioritize the issues
Plan analyses
Conduct analyses
Synthesize findings
Develop recommendations

Not all problems require strict adherence to the process. Some steps may be truncated, such as when specific knowledge or analogies from other industries make it possible to construct hypotheses and associated workplans earlier than their formal place in the process. Nonetheless, it remains important to be capable of executing every step in the basic process.

When confronted with a new and complex problem, this process establishes a path to defining and disaggregating the problem in a way that will allow the team to move to a solution. The process also ensures nothing is missed and concentrates efforts on the highest-impact areas. Adhering to the process gives the client clear steps to follow, building confidence, credibility, and long-term capability.

Problem Definition & Problem Statement Worksheet

The most important step in your entire project is to first carefully define the problem. The problem definition will serve the guide all of the team’s work, so it is critical to ensure that all key stakeholders agree that it is the right problem to be solving.

Problem Statement Worksheet

This is a helpful tool to use to clearly define the problem. There are often dozens of issues that a team could focus on, and it is often not obvious how to define the problem. In any real-life situation, there are many possible problem statements. Your choice of problem statement will serve to constrain the range of possible solutions.

Use a question . The problem statement should be phrased as a question, such that the answer will be the solution. Make the question SMART: specific, measurable, action-oriented, relevant, and time-bound. Example: “How can XYZ Bank close the $100 million profitability gap in two years?”
Context . What are the internal and external situations and complications facing the client, such as industry trends, relative position within the industry, capability gaps, financial flexibility, and so on?
Success criteria . Understand how the client and the team define success and failure. In addition to any quantitative measures identified in the basic question, identify other important quantitative or qualitative measures of success, including timing of impact, visibility of improvement, client capability building required, necessary mindset shifts, and so on.
Scope and constraints . Scope most commonly covers the markets or segments of interest, whereas constraints govern restrictions on the nature of solutions within those markets or segments.
Stakeholders . Explore who really makes the decisions — who decides, who can help, and who can block.
Key sources of insight . What best-practice expertise, knowledge, and engagement approaches already exist? What knowledge from the client, suppliers, and customers needs to be accessed? Be as specific as possible: who, what, when, how, and why.

The problem definition should not be vague, without clear measures of success. Rather, it should be a SMART definition:

Action-oriented

Example situation – A family on Friday evening

Scenario: A mother, a father, and their two teenage children have all arrived home on a Friday at 6 p.m. The family has not prepared dinner for Friday evening. The daughter has lacrosse practice on Saturday and an essay to write for English class due on Monday. The son has theatre rehearsal on both Saturday and Sunday and will need one parent to drive him to the high school both days, though he can get a ride home with a friend. The family dog, a poodle, must be taken to the groomer on Saturday morning. The mother will need to spend time this weekend working on assignments for her finance class she is taking as part of her Executive MBA. The father plans to go on a 100-mile bike ride, which he can do either Saturday or Sunday. The family has two cars, but one is at the body shop. They are trying to save money to pay for an addition to their house.

What is the problem definition?

A statement of facts does not focus the problem solving:

It is 6 p.m. The family has not made plans for dinner, and they are hungry.

A question guides the team towards a solution:

1. What should the family do for dinner on Friday night?

2. Should the family cook dinner or order delivery?

3. What should the family cook for dinner?

4. What should the family cook for dinner that will not require spending more than $40 on groceries?

5. To cook dinner, what do they need to pick up from the supermarket?

6. How can the family prepare dinner within the next hour using ingredients they already have in the house?

In completing the Problem Statement Worksheet, you are prompted to define the key stakeholders.

As you become involved in the problem-solving process, you should expand the question of key stakeholders to include what the team wants from them and what they want from the team, their values and motivations (helpful and unhelpful), and the communications mechanisms that will be most effective for each of them.

Using the Stakeholder Analysis Worksheet allows you to comprehensively identify:

Stakeholders
What you need from them
Where they are
What they need from you

The two most helpful techniques for rigorously structuring any problem are hypothesis trees and issue trees. Each of these techniques disaggregates the primary question into a cascade of issues or hypotheses that, when addressed, will together answer the primary question.

A hypothesis tree might break down the same question into two or more hypotheses.

Example: Alpha Manufacturing, Inc.

Problem Statement: How can Alpha increase EBITDA by $13M (to $50M) by 2025?

The hypotheses might be:

Alpha can add $125M revenues by expanding to new customers, adding $8M of EBITDA
Alpha can reduce costs to improve EBITDA by $5M

These hypotheses will be further disaggregated into subsidiary hypotheses at the next level of the tree.

The aim at this stage is to structure the problem into discrete, mutually exclusive pieces that are small enough to yield to analysis and that, taken together, are collectively exhaustive.

Articulating the problem as hypotheses, rather than issues, is the preferred approach because it leads to a more focused analysis of the problem. Questions to ask include:

Is it testable – can you prove or disprove it?
It is open to debate? If it cannot be wrong, it is simply a statement of fact and unlikely to produce keen insight.
If you reversed your hypothesis – literally, hypothesized that the exact opposite were true – would you care about the difference it would make to your overall logic?
If you shared your hypothesis with the CEO, would it sound naive or obvious?
Does it point directly to an action or actions that the client might take?

Quickly developing a powerful hypothesis tree enables us to develop solutions more rapidly that will have real impact. This can sometimes seem premature to clients, who might find the “solution” reached too quickly and want to see the analysis behind it.

Take care to explain the approach (most important, that a hypothesis is not an answer) and its benefits (that a good hypothesis is the basis of a proven means of successful problem solving and avoids “boiling the ocean”).

Often, the team has insufficient knowledge to build a complete hypothesis tree at the start of an engagement. In these cases, it is best to begin by structuring the problem using an issue tree.

An issue tree is best set out as a series of open questions in sentence form. For example, “How can the client minimize its tax burden?” is more useful than “Tax.” Open questions – those that begin with what, how, or why– produce deeper insights than closed ones. In some cases, an issue tree can be sharpened by toggling between issue and hypothesis – working forward from an issue to identify the hypothesis, and back from the hypothesis to sharpen the relevant open question.

Once the problem has been structured, the next step is to prioritize the issues or hypotheses on which the team will focus its work. When prioritizing, it is common to use a two-by-two matrix – e.g., a matrix featuring “impact” and “ease of impact” as the two axes.

Applying some of these prioritization criteria will knock out portions of the issue tree altogether. Consider testing the issues against them all, albeit quickly, to help drive the prioritization process.

Once the criteria are defined, prioritizing should be straightforward: Simply map the issues to the framework and focus on those that score highest against the criteria.

As the team conducts analysis and learns more about the problem and the potential solution, make sure to revisit the prioritization matrix so as to remain focused on the highest-priority issues.

The issues might be:

How can Alpha increase revenue?
How can Alpha reduce cost?

Each of these issues is then further broken down into deeper insights to solutions.

If the prioritization has been carried out effectively, the team will have clarified the key issues or hypotheses that must be subjected to analysis. The aim of these analyses is to prove the hypotheses true or false, or to develop useful perspectives on each key issue. Now the task is to design an effective and efficient workplan for conducting the analyses.

Transforming the prioritized problem structure into a workplan involves two main tasks:

Define the blocks of work that need to be undertaken. Articulate as clearly as possible the desired end products and the analysis necessary to produce them, and estimate the resources and time required.
Sequence the work blocks in a way that matches the available resources to the need to deliver against key engagement milestones (e.g., important meetings, progress reviews), as well as to the overall pacing of the engagement (i.e., weekly or twice-weekly meetings, and so on).

A good workplan will detail the following for each issue or hypothesis: analyses, end products, sources, and timing and responsibility. Developing the workplan takes time; doing it well requires working through the definition of each element of the workplan in a rigorous and methodical fashion.

This is the most difficult element of the problem-solving process. After a period of being immersed in the details, it is crucial to step back and distinguish the important from the merely interesting. Distinctive problem solvers seek the essence of the story that will underpin a crisp recommendation for action.

Although synthesis appears, formally speaking, as the penultimate step in the process, it should happen throughout. Ideally, after you have made almost any analytical progress, you should attempt to articulate the “Day 1” or “Week 1” answer. Continue to synthesize as you go along. This will remind the team of the question you are trying to answer, assist prioritization, highlight the logical links of the emerging solution, and ensure that you have a story ready to articulate at all times during the study.

McKinsey’s primary tool for synthesizing is the pyramid principle. Essentially, this principle asserts that every synthesis should explain a single concept, per the “governing thought.” The supporting ideas in the synthesis form a thought hierarchy proceeding in a logical structure from the most detailed facts to the governing thought, ruthlessly excluding the interesting but irrelevant.

While this hierarchy can be laid out as a tree (like with issue and hypothesis trees), the best problem solvers capture it by creating dot-dash storylines — the Pyramid Structure for Grouping Arguments.

Pyramid Structure for Grouping Arguments

Focus on action. Articulate the thoughts at each level of the pyramid as declarative sentences, not as topics. For example, “expansion” is a topic; “We need to expand into the European market” is a declarative sentence.
Use storylines. PowerPoint is poor at highlighting logical connections, therefore is not a good tool for synthesis. A storyline will clarify elements that may be ambiguous in the PowerPoint presentation.
Keep the emerging storyline visible. Many teams find that posting the storyline or story- board on the team-room wall helps keep the thinking focused. It also helps in bringing the client along.
Use the situation-complication-resolution structure. The situation is the reason there is action to be taken. The com- plication is why the situation needs thinking through – typically an industry or client challenge. The resolution is the answer.
Down the pyramid: does each governing thought pose a single question that is answered completely by the group of boxes below it?
Across: is each level within the pyramid MECE?
Up: does each group of boxes, taken together, provide one answer – one “so what?” – that is essentially the governing thought above it?
Test the solution. What would it mean if your hypotheses all came true?

Three Horizons of Engagement Planning

It’s useful to match the workplan to three horizons:

What is expected at the end of the engagement
What is expected at key progress reviews
What is due at daily and/or weekly team meetings

The detail in the workplan will typically be greater for the near term (the next week) than for the long term (the study horizon), especially early in a new engagement when considerable ambiguity about the end state remains.

It is at this point that we address the client’s questions: “What do I do, and how do I do it?” This means not offering actionable recommendations, along with a plan and client commitment for implementation.

The essence of this step is to translate the overall solution into the actions required to deliver sustained impact. A pragmatic action plan should include:

Relevant initiatives, along with a clear sequence, timing, and mapping of activities required
Clear owners for each initiative
Key success factors and the challenges involved in delivering on the initiatives

Crucial questions to ask as you build recommendations for organizational change are:

Does each person who needs to change (from the CEO to the front line) understand what he or she needs to change and why, and is he or she committed to it?
Are key leaders and role models throughout the organization personally committed to behaving differently?
Has the client set in place the necessary formal mechanisms to reinforce the desired change?
Does the client have the skills and confidence to behave in the desired new way?

Great problem solvers identify unique disruptions and discontinuities, novel insights, and step-out opportunities that lead to truly distinctive impact. This is done by applying a number of practices throughout the problem-solving process to help develop these insights.

Expand: Construct multiple perspectives

Identifying alternative ways of looking at the problem expands the range of possibilities, opens you up to innovative ideas, and allows you to formulate more powerful hypotheses. Questions that help here include:

What changes if I think from the perspective of a customer, or a supplier, or a frontline employee, or a competitor?
How have other industries viewed and addressed this same problem?
What would it mean if the client sought to run the company like a low-cost airline or a cosmetics manufacturer?

Link: Identify relationships

Strong problem solvers discern connections and recognize patterns in two different ways:

They seek out the ways in which different problem elements – issues, hypotheses, analyses, work elements, findings, answers, and recommendations – relate to one another.
They use these relationships throughout the basic problem-solving process to identify efficient problem-solving approaches, novel solutions, and more powerful syntheses.

Distill: Find the essence

Cutting through complexity to identify the heart of the problem and its solution is a critical skill.

Identify the critical problem elements. Are there some issues, approaches, or options that can be eliminated completely because they won’t make a significant difference to the solution?
Consider how complex the different elements are and how long it will take to complete them. Wherever possible, quickly advance simpler parts of the problem that can inform more complex or time-consuming elements.

Lead: Stay ahead/step back

Without getting ahead of the client, you cannot be distinctive. Paradoxically, to get ahead – and stay ahead – it is often necessary to step back from the problem to validate or revalidate the approach and the solution.

Spend time thinking one or more steps ahead of the client and team.
Constantly check and challenge the rigor of the underlying data and analysis.
Stress-test the whole emerging recommendation
Challenge the solution against a set of hurdles. Does it satisfy the criteria for success as set out on the Problem Statement Worksheet?

No matter how skilled, knowledgeable, or experienced you are, you will never create the most distinctive solution on your own. The best problem solvers know how to leverage the power of their team, clients, the Firm, and outside parties. Seeking the right expertise at the right time, and leveraging it in the right way, are ultimately how we bring distinctiveness to our work, how we maximize efficiency, and how we learn.

When solving a problem, it is important to ask, “Have I accessed all the sources of insight that are available?” Here are the sources you should consider:

Your core team
The client’s suppliers and customers
Internal experts and knowledge
External sources of knowledge
Communications specialists

The key here is to think open, not closed. Opening up to varied sources of data and perspectives furthers our mission to develop truly innovative and distinctive solutions for our clients.

McKinsey Staff Paper 66 — not published by McKinsey but possibly found through an internet search
The McKinsey Way , 1999, by Ethan M. Rasiel

For consultants

Career in Consulting

Hypothesis-driven approach: the definitive guide

Imagine you are walking in one of McKinsey’s offices.

Around you, there are a dozen of busy consultants.

The word “hypothesis” would be one of the words you would hear the most.

Along with “MECE” or “what’s the so-what?”.

This would also be true in any BCG, Bain & Company office or other major consulting firms.

Because strategy consultants are trained to use a hypothesis-driven approach to solve problems.

And as a candidate, you must demonstrate your capacity to be hypothesis-driven in your case interviews .

There is no turnaround:

If you want a consulting offer, you MUST know how to use a hypothesis-driven approach .

Like a consultant would be hypothesis-driven on a real project for a real client?

Hell, no! Big mistake!

Because like any (somehow) complex topics in life, the context matters.

What is correct in one context becomes incorrect if the context changes.

And this is exactly what’s happening with using a hypothesis-driven approach in case interviews.

This should be different from the hypothesis-driven approach used by consultant solving a problem for a real client .

And that’s why many candidates get it wrong (and fail their interviews).

They use a hypothesis-driven approach like they were already a consultant.

Thus, in this article, you’ll learn the correct definition of being hypothesis-driven in the context of case interviews .

Plus, you’ll learn how to use a hypothesis in your case interviews to “crack the case”, and more importantly get the well-deserved offer!

Ready? Let’s go. It will be super interesting!

The wrong hypothesis-driven approach in case interviews.

Let’s start with a definition:

Hypothesis-driven thinking is a problem-solving method whereby you start with the answer and work back to prove or disprove that answer through fact-finding.

Concretely, here is how consultants use a hypothesis-driven approach to solve their clients’ problems:

Form an initial hypothesis, which is what they think the answer to the problem is.
Craft a logic issue tree , by asking themselves “what needs to be true for the hypothesis to be true?”
Walk their way down the issue tree and gather the necessary data to validate (or refute) the hypothesis.
Reiterate the process from step 1 – if their first hypothesis was disproved by their analysis – until they get it right.

With this answer-first approach, consultants do not gather data to fish for an answer. They seek to test their hypotheses , which is a very efficient problem-solving process.

The answer-first thinking works well if the initial hypothesis has been carefully formed.

This is why – in top consulting firms like McKinsey , BCG , or Bain & Company – the hypothesis is formed by a Partner with 20+ years of work experience.

And this is why this is NOT the right approach for case interviews.

Imagine a candidate doing a case interview at McKinsey and using answer-first thinking.

At the beginning of a case, this candidate forms a hypothesis (a potential answer to the problem), builds a logic tree, and gathers data to prove the hypothesis.

Here, there are two options:

The initial hypothesis is right

The initial hypothesis is wrong

If the hypothesis is right, what does it mean for the candidate?

That the candidate was lucky.

Nothing else.

And it certainly does not prove the problem-solving skills of this candidate (which is what is tested in case interviews).

Now, if the hypothesis is wrong, what’s happening next?

The candidate reiterates the process.

Imagine how disorganized the discussion with the interviewer can be.

Most of the time, such candidates cannot form another hypothesis, the case stops, and the candidate feels miserable.

This leads us to the right hypothesis-driven approach for case interviews.

The right hypothesis-driven approach in case interviews

To make my point clear between the wrong and right approach, I’ll take a non-business example.

Let’s imagine you want to move from point A to point B.

And for that, you have the choice among a multitude of roads.

Using the answer-first approach presented in the last section, you’d know which road to take to move from A to B (for instance the red line in the drawing below).

Again, this would not demonstrate your capacity to find the “best” road to go from A to B.

(regardless of what “best” means. It can be the fastest or the safest for instance.)

Now, a correct hypothesis-driven approach consists in drawing a map with all the potential routes between A and B, and explaining at each intersection why you want to turn left or right (” my hypothesis is that we should turn right ”).

And in the context of case interviews?

In the above analogy:

A is the problem
B is the solution
All the potential routes are the issues in your issue tree

And the explanation of why you want to take a certain road instead of another would be your hypothesis.

Is the difference between the wrong and right hypothesis-driven approach clearer?

If not, don’t worry. You’ll find many more examples below in this article.

But, next, let’s address another important question.

Why you must (always) use a hypothesis in your case interviews

You must use a hypothesis in your case interviews for two reasons.

A hypothesis helps you focus on what’s important to solve the case

Using a hypothesis-driven approach is critical to solving a problem efficiently.

In other words:

A hypothesis will limit the number of analysis you need to perform to solve a problem.

Thus, this is a way to apply the 80/20 principle and prioritize the issues (from your MECE issue tree ) you want to investigate.

And this is very important because your time with your interviewer is limited (like is the time with your client on a real project).

Let’s take a simple example of a hypothesis:

The profits of your client have dropped.

And your initial analysis shows increasing costs and stagnating revenues.

So your hypothesis can be:

“I think something happened in our cost structure, causing the profit drop. Next, I’d like to understand better the cost structure of our clients and which cost items have changed recently.”

Here the candidate is rigorously “cutting” half of his/her issue tree (the revenue side) and will focus the case discussion on the cost side.

And this is a good example of a hypothesis in case interviews.

Get 4 Complete Case Interview Courses For Free

You need 4 skills to be successful in all case interviews: Case Structuring, Case Leadership, Case Analytics, and Communication. Join this free training and learn how to ace ANY case questions.

A hypothesis tells your interviewers why you want to do an analysis

There is a road that you NEVER want to take.

On this road, the purpose of the questions asked by a candidate is not clear.

Here are a few examples:

“What’s the market size? growth?”

“Who are the main competitors? what are their market shares?”

“Have customer preferences changed in this market?”

This list of questions might be relevant to solve the problem at stake.

But how these questions help solve the problem is not addressed.

Or in other words, the logical connection between these questions and the problem needs to be included.

So, a better example would be:

“We discovered that our client’s sales have declined for the past three years. I would like to know if this is specific to our client or if the whole market has the same trend. Can you tell me how the market size has changed over the past three years? »

In the above question, the reason why the candidate wants to investigate the market is clear: to narrow down the analysis to an internal root cause or an external root cause.

Yet, I see only a few (great) candidates asking clear and purposeful questions.

You want to be one of these candidates.

How to use a hypothesis-driven approach in your case interviews?

At this stage, you understand the importance of a hypothesis-driven approach in case interviews:

You want to identify the most promising areas to analyze (remember that time is money ).

And there are two (and only two) ways to create a good hypothesis in your case interviews:

a quantitative way
a qualitative way

Let’s start with the quantitative way to develop a good hypothesis in your case interviews.

The quantitative approach: use the available data

Let’s use an example to understand this data-driven approach:

Interviewer: your client is manufacturing computers. They have been experiencing increasing costs and want to know how to address this issue.

Candidate: to begin with, I want to know the breakdown of their cost structure. Do you have information about the % breakdown of their costs?

Interviewer: their materials costs count for 30% and their manufacturing costs for 60%. The last 10% are SG&A costs.

Candidate: Given the importance of manufacturing costs, I’d like to analyze this part first. Do we know if manufacturing costs go up?

Interviewer: yes, manufacturing costs have increased by 20% over the past 2 years.

Candidate: interesting. Now, it would be interesting to understand why such an increase happened.

You can notice in this example how the candidate uses data to drive the case discussion and prioritize which analysis to perform.

The candidate made a (correct) hypothesis that the increasing costs were driven by the manufacturing costs (the biggest chunk of the cost structure).

Even if the hypothesis were incorrect, the candidate would have moved closer to the solution by eliminating an issue (manufacturing costs are not causing the overall cost increase).

That said, there is another way to develop a good hypothesis in your case interviews.

The qualitative approach: use your business acumen

Sometimes you don’t have data (yet) to make a good hypothesis.

Thus, you must use your business judgment and develop a hypothesis.

Again, let’s take an example to illustrate this approach.

Interviewer: your client manufactures computers and has been losing market shares to their direct competitors. They hired us to find the root cause of this problem.

Candidate: I think of many reasons explaining the drop in market shares. First, our client manufactures and sells not-competitive products. Secondly, we might price our products too high. Third, we need to use the right distribution channels. For instance, we might sell in brick-and-mortars stores when consumers buy their computers in e-stores like Amazon. Finally, I think of our marketing expenses. There may be too low or not used strategically.

Candidate: I see these products as commodities where consumers use price as the main buying decision criteria. That’s why I’d like to explore how our client prices their products. Do you have information about how our prices compare to competitors’?

Interviewer: this is a valid point. Here is the data you want to analyze.

Note how this candidate explains what she/he wants to analyze first (prices) and why (computers are commodities).

In this case interview, the hypothesis-driven approach looks like this:

This is a commodity industry —> consumers buying behavior is driven by pricing —> our client’s prices are too high.

Again, note how the candidate first listed the potential root causes for this situation and did not use an answer-first approach.

Want to learn more?

In this free training , I explain in detail how to use data or your business acumen to prioritize the issues to analyze and “crack the case.”

Also, you’ll learn what to do if you don’t have data or can’t use your business acumen.

Form a hypothesis in these two critical moments of your case interviews

After you’ve presented your initial structure.

The first moment to form a hypothesis in your case interview?

In the beginning, after you’ve presented your structure.

When you’ve presented your issue tree, mention which issue you want to analyze first.

Also, explain why you want to investigate this first issue.

Make clear how the outcome of the analysis of this issue will help you solve the problem.

After an analysis

The second moment to form a hypothesis in your case interview?

After you’ve derived an insight from data analysis.

This insight has proved (or disproved) your hypothesis.

Either way, after you have developed an insight, you must form a new hypothesis.

This can be the issue you want to analyze next.

Or what a solution to the problem is.

Hypothesis-driven approach in case interviews: a conclusion

Having spent about 10 years coaching candidates through the consulting recruitment process , one commonality of successful candidates is that they truly understand how to be hypothesis-driven and demonstrate efficient problem-solving.

Plus, per my experience in coaching candidates , not being able to use a hypothesis is the second cause of rejection in case interviews (the first being the lack of MECEness ).

This means you can’t afford NOT to master this concept in a case study.

So, sign up now for this free course to learn how to use a hypothesis-driven approach in your case interviews and land your dream consulting job.

More than 7,000 people have already signed up.

Don’t waste one more minute!

See you there.

SHARE THIS POST

35 problem-solving techniques and methods for solving complex problems

Design your next session with SessionLab

Join the 150,000+ facilitators  using SessionLab.

How do you identify problems?

How do you identify the right solution.

Tips for more effective problem-solving

Complete problem-solving methods

Problem-solving techniques to identify and analyze problems
Problem-solving techniques for developing solutions

Problem-solving warm-up activities

Closing activities for a problem-solving process.

Before you can move towards finding the right solution for a given problem, you first need to identify and define the problem you wish to solve.

Here, you want to clearly articulate what the problem is and allow your group to do the same. Remember that everyone in a group is likely to have differing perspectives and alignment is necessary in order to help the group move forward.

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 scary for people to stand up and contribute, especially if the problems or challenges are emotive or personal in nature. Be sure to try and create a psychologically safe space for these kinds of discussions.

Remember that problem analysis and further discussion are also important. Not taking the time to fully analyze and discuss a challenge can result in the development of solutions that are not fit for purpose or do not address the underlying issue.

Successfully identifying and then analyzing a problem means facilitating a group through activities designed to help them clearly and honestly articulate their thoughts and produce usable insight.

With this data, you might then produce a problem statement that clearly describes the problem you wish to be addressed and also state the goal of any process you undertake to tackle this issue.

Finding solutions is the end goal of any process. Complex organizational challenges can only be solved with an appropriate solution but discovering them requires using the right problem-solving tool.

After you’ve explored a problem and discussed ideas, you need to help a team discuss and choose the right solution. Consensus tools and methods such as those below help a group explore possible solutions before then voting for the best. They’re a great way to tap into the collective intelligence of the group for great results!

Remember that the process is often iterative. Great problem solvers often roadtest a viable solution in a measured way to see what works too. While you might not get the right solution on your first try, the methods below help teams land on the most likely to succeed solution while also holding space for improvement.

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

In 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!

Tips for more 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.

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!

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
Lightning Decision Jam
Problem Definition Process
Discovery & Action Dialogue

Design Sprint 2.0

Open Space Technology

1. 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.

2. 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 The problem with anything that requires creative thinking is that it’s easy to get lost—lose focus and fall into the trap of having useless, open-ended, unstructured discussions. Here’s the most effective solution I’ve found: Replace all open, unstructured discussion with a clear process. What to use this exercise for: Anything which requires a group of people to make decisions, solve problems or discuss challenges. It’s always good to frame an LDJ session with a broad topic, here are some examples: The conversion flow of our checkout Our internal design process How we organise events Keeping up with our competition Improving sales flow

3. 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.

4. 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.

5. World Cafe

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.

6. 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.

7. 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.

8. 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!

The Creativity Dice
Fishbone Analysis
Problem Tree
SWOT Analysis
Agreement-Certainty Matrix
The Journalistic Six
LEGO Challenge
What, So What, Now What?
Journalists

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.

10. 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.

11. 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.

12. 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.

13. 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.

14. 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.

16. Speed Boat

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.

17. 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.

18. 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.

19. 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!

20. 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 developing 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 narrow down to the correct solution.

Use these problem-solving techniques when you want to help your team find consensus, compare possible solutions, and move towards taking action on a particular problem.

Improved Solutions
Four-Step Sketch
15% Solutions
How-Now-Wow matrix
Impact Effort Matrix

21. 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.

22. 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.

23. 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

24. 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.

25. 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.

26. 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.

27. Dotmocracy

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.

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
Doodling Together
Show and Tell
Constellations
Draw a Tree

28. 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.

29. 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.

30. 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.

31. 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.

32. 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.

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
Who What When Matrix
Response Cards

How do I conclude a problem-solving process?

All good things must come to an end. With the bulk of the work done, it can be tempting to conclude your workshop swiftly and without a moment to debrief and align. This can be problematic in that it doesn’t allow your team to fully process the results or reflect on the process.

At the end of an effective session, your team will have gone through a process that, while productive, can be exhausting. It’s important to give your group a moment to take a breath, ensure that they are clear on future actions, and provide short feedback before leaving the space.

The primary purpose of any problem-solving method is to generate solutions and then implement them. Be sure to take the opportunity to ensure everyone is aligned and ready to effectively implement the solutions you produced in the workshop.

Remember that every process can be improved and by giving a short moment to collect feedback in the session, you can further refine your problem-solving methods and see further success in the future too.

33. 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.

34. 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.

35. 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.

Save time and effort discovering the right solutions

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 creative 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!

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

"The McKinsey Way" Book: A Comprehensive Summary

The McKinsey Way is a book by Ethan M. Rasiel , published in 1999, about what McKinsey&Company does, how McKinsey organizes and what working at McKinsey is like.

20 years after publication, the book still holds significant value, offering timeless insights into the world’s most prestigious management consulting firm: McKinsey&Company. In this article, we’ll provide a detailed summary of all the lessons and insights from The McKinsey way . We’ll re-organize the content and occasionally insert supporting insights to make it more friendly to the reader.

The McKinsey Way has 5 Parts (Sections) with 180 pages:

Part 1: The Problem Solving Methodology of McKinsey

Part 2: Logistics of how a McKinsey project works

Part 3: insights into the actual works of consultants, part 4: how to excel as a junior consultant, part 5: exit opportunities and life after mckinsey.

Table of Contents

Part 1: The McKinsey problem-solving methodology

The McKinsey problem-solving process can be summarized in the 5 steps: define the problems, find the root cause, use “hypothesis-driven” process, analyze with “issue tree” and propose solutions.

1. Define the problem: Every consulting project revolves around a “problem”. But the “problem” is NOT always the problem!

One symptom may have different causes and we as doctors should never rely on the patient to diagnose.

So, always dig deeper. Get facts. Asks questions. Poke around. Challenge the client… until you find the real problem.

2. Find the root cause: Don’t jump straight to the solution, because you might just be fixing the symptoms. The problem will come back if the root cause is not properly dealt with.

3. Use “hypothesis-driven” process: Make educated guesses of possible root-cause A B C and test with data (a.k.a: facts). We’ll sometimes call this a fact-based process.

4. Break down and structure the analysis with the “ issue tree ” framework: A “hypothesis-driven” process may take forever as there are millions of possible root-causes. We need to test hypotheses from the top to the bottom of the issue tree – a top-down fashion. These issue trees need to be MECE.

5. Propose solutions: When the root causes are identified, consultants propose solutions targeting them directly.

A few notes when using this methodology

No.1: Don’t force the facts to say what you want.

When you propose or work extensively with a running hypothesis , it’s easy to get emotionally attached and turn the problem-solving process into a proving exercise. So keep an open mind and listen to what the data have to say.

No.2: Let the hypothesis come to you naturally.

You will not be able to form an initial hypothesis every time. The clients may not even know their problems. The scope of the project is often large and vague. So, dive in, gather facts, conduct analyses, and the hypotheses will show themselves.

No.3: Don’t reinvent the wheel.

Business problems often resemble each other more than they differ. With suitable techniques, you can apply what you and the firm learned from other projects. After all, one of the values consulting firms bring is to provide the “best practice” – what the top players in the game are doing

No.4: Make sure your solution fits your client.

The most brilliant solution is useless without proper implementation. So know your client’s weaknesses, strengths, and capabilities and tailor your solutions accordingly.

No.5: Be mindful of politics.

There are always politics in projects. Many times, McKinsey gets involved in fights between corporate factions. This creates friction that prevents you from doing your job (late data; rejected interviews, etc.).

So think about how your solutions affect the players in an organization and always build a consensus along the way. If consensus requires you to change your solution, try to compromise. It’s no good devising the ideal solution if the client refuses to accept it.

It’s highly recommended that you refer to the following video for a general view on how McKinsey organizes and a better understanding of the insights from this part.

There is a whole system behind how McKinsey solve a business problem. In this part of The McKinsey Way, Ethan Rasiel describes how the company sells their projects, builds a team and manages its hierarchy.

Selling a study/project

McKinsey typically does not sell. The firm does marketing through a constant stream of books, articles, and scholarly journals like the McKinsey Quarterly, etc. The Firm also invites organize press releases and generates quite some coverage by journalists.

These publications help McKinsey Partners build and nurture a vast network of informal contacts with potential clients. And when a problem arises, the client knows who to contact.

Assembling a team

Almost all projects need a full-time team of consultants. Typically, the process goes like this:

The ED (a.k.a: Project Owner) signs a contract with the client
The ED hires an EM from within the McKinsey network, from any offices (a.k.a: Project CEO)
The EM then hires a group of staff, consisting of BAs (a.k.a: Business Analyst) and Associates.

It’s solely the EM’s responsibility to keep the team happy and functional. McKinsey projects have a few common practices to do so:

A monthly “team-bonding”.
A “team temperature” (a.k.a: morale) weekly survey.

The hierarchy

The chain of command in McKinsey is very clear and strict. So is the responsibility funnel. In the ED’s eyes, the EM is responsible for everything in the project. In the EM eyes, the BA is responsible for everything within the assigned workstream. Even when a BA messes things up, to the ED, it’s not the BA’s fault, but the EM.

To provide the best solution for the clients, consultants need tons of skills in preparing presentations; conducting researchs and interviews; presenting the final products in a simple structure; communicating with clients; and brainstorming.

Making presentations, a.k.a: the final deliverable documents

Most consultants spend a big portion of their time making presentations (often in PowerPoint). Utilize the support team! Keep it structured, from top to bottom, from end to end.

Note that there are diminishing marginal returns to your effort, meaning that the last miles toward perfection are always much harder than the beginning. So, resist the temptation to tweak your presentation at the last minute. Try to assess its gains vs those of a good night’s sleep for you and the supporting cast.

Visualizing data with charts and exhibits

We subconsciously admire the people who talk in sophisticated language, so we make complex charts. However, simple and easy-to-follow charts go a long way in consulting. Charts are just a means of getting your messages across, not a Ph.D. project.

Also, don’t forget to:

Write clear chart titles
List out units of measurement in all axes
Mark legends and side notes
Provide data sources

Managing internal communications

Over-communication is always better. Keep that information flowing. Make sure that your team is up to date with at least the broad outlines of your workstream and your boss up to date with your team’s progress. There are many channels for this: email, voicemail, messaging, small talks during cigarette breaks, meetings, etc.
Keep your communication brief, yet comprehensive and structured.
Look over your shoulder – always. You never know who is listening. Remember that your client’s confidentiality is a must.

Working with clients

This is a big one as the true hierarchy at McKinsey is “Client -> Firm -> and then You”. The client is your biggest boss.

There are many tips on client management, but the general principle is to bring the client to your side. You never win by opposing the client. Remind them about mutual benefits. Do it everyday!

Some of the client members can be “liabilities”. There are 2 types of them:

the merely “useless”.
the hostile ones.

With both types, the number 1 option is to subtly trade them out of your realm. When that is not possible, the next best option is to play ignorant. Leak out information only with the right “secret audience”.

No matter what, engage the client members in the process. The more they feel everybody is on the same boat, the more they would support you.

You should also get buy-ins throughout the organization along the process. Every important party has to agree with you. Ideally, the final document has already been discussed many times through many rounds with the client before the official presentation.

Doing research

Don’t reinvent the wheel! Whatever you are doing, chances are that someone, somewhere has done something similar. Building upon someone’s work is the best way to save time and energy while achieving the highest standard.

Besides, here are some research tips:

Start with the annual report. All public companies have them available on their website.
Look for abnormal patterns (things that are especially good or bad). That’s where all the insights lie.
Last but not least, look for the best practice. Find out what the best performers in the field are doing and learn from them.

Conducting interviews

This is one of the most effective ways to gather qualitative facts during a project. You will find yourself interviewing multiple industry and function experts as well as key client leaders.

Here are a few tips:

Be prepared. Know exactly what you want to get out of it. Know as much as you can about the interviewee. Writing an interview brief for yourself is not a bad idea.
If possible, have the interviewee’s boss set up the meeting.
Start with some general and open-ended questions then move on to specific ones. Let the content flow naturally.
Sometimes, it’s useful to use the indirect style. Take time to make the interviewee comfortable with you and the interview process.
Include some questions you know the answer to. This gives insights into the interviewee’s style, knowledge, and honesty.
Don’t ask too much. Focus on what you really need (what you prioritize in the interview brief).
Listen and let the interviewee know you are doing so.
Paraphrase what you hear in your own words. Confirm whether you understand correctly. This also gives chances for the interviewee to add or amplify important points.
Near the end, use this last trick to flush out any possible missing insights: “Is there anything else you would like to tell or any question I forgot to ask…?”.
Adopt the Columbo tactic. Wait until a day or two passes, then drop by the interviewee’s office. “I was just passing by and remembered a question I forgot to ask”. This is a less threatening way to keep the conversation going.
Lastly, always write a thank-you note. A short and sincerely one always does the work.

Brainstorming at McKinsey

In McKinsey, we often use the word “Problem-Solving” interchangeably with brainstorming sessions. It’s a very topic-focus meeting within the McKinsey team, consisting of the consultant in-charge, the EM, and sometimes even the ED and experts.

Before the session, prepare in advance as much supporting data as possible. It will come handy in the process.Inside the White room: Start with tabula rasa — a clean slate. When you get your team into the room, leave your preconceptions at the door. Bring in only the facts, and find new ways of looking at them.

Management consulting is an interesting yet challenging job. To survive and thrive at McKinsey, here are some advices for you:

Tip 1: Find your own mentor

At McKinsey, every consultant is officially assigned a mentor, who may not be in the same office. How much you benefit from the official mentor is pretty much a matter of luck. If you want great guidance, you have to go out and get your own. Get a few too, don’t stick to just one.

Tip 2: Survive the road

Business travel can be exhausting and difficult, here are some note you can take to deal with it:

Look at business travel as an adventure.
Do proper planning. These simple logistics can make a big difference
Treat everyone with tremendous respect

Tip 3: Have a list of items to bring when traveling

Here is the list:

Clothing: extra shirts or blouses, spare ties, spare shoes, casual clothes, cashmere sweaters
Tools: writing pad, copy of whatever you send to the client, calculator
Personal care Items
Things to keep you organized and in touch

Tip 4: Treat your assistant well

Having a good assistant is a lifeline. Treat them well. Be clear about what you want. Give them room to grow. Take time to train them well. Answering their questions and showing them the ropes.

Tip 5: Have boundaries to keep your life balance

Since you have a large amount of work to cover as a consultant, there is almost no work-life balance. However, if you want a life, lay down some rules. For example:

Make one day a week to be completely free of work, both physically and mentally. Tell your boss about it! He/she will respect it. And so should you.
Don’t take work home. When you are home, you are home!
Plan long ahead, especially when you travel.

Tip 6: The 80 / 20 Rule

80% of the wealth is owned by just 20% of the population. 80% of the output can be produced by 20% of the effort. 20% of the problems can cause 80% of the trouble.

So if you wanna save time and effort. Always try to find those 20% and act upon them!

Tip 7: Don’t try to analyze everything

If you don’t take shortcuts, there is simply too much to do. Be selective. Find the key drivers. Focus on the core problem, then apply analysis. This helps avoid going down blind alleys and boiling the ocean.

Tip 8: The Elevator Test

Concise communication is crucial in consulting. Anytime the EM asks you for your workstream status, you have to be able to give him a 30 seconds summary. Short yet insightful. This skill takes practice. Try doing it every day in various contexts!

Tip 9: Pluck the Low-Hanging Fruit

Solving only part of the problem can still mean increased profits. Those little wins help you and your customers. Try to see such opportunities and grab them first.

Tip 10: Hit singles

Get your job and only your job done, don’t try to do the work of the whole team.

It’s impossible to do everything yourself all the time. Even if you manage to pull it off once, you raise unrealistic expectations and once you fail, it is difficult to get back credibility.

Tip 11: Look at the big picture

When you are feeling swamped, take a step back, figure out what you are trying to achieve, and then look at what you are doing. “Does this really matter?”

Probably not! All of these troubles will go away!

Tip 12: Just say “I don’t know”

The firm pounds the concept of professional integrity: Honesty. If you don’t know something, just say “I DON’T KNOW” in an empowering fashion. Admitting that is a lot less costly than bluffing.

“Leaving McKinsey is never a question of whether—it’s a question of when”

There are not many people who stay with McKinsey for their whole career life. In the last part of The McKinsey Way , Ethan Rasiel and other ex-McKinsey consultants share their valuable lessons and memories from working at the company.

“Structure, structure, structure. MECE, MECE, MECE. Hypothesis-driven, Hypothesis-driven, Hypothesis-driven.” – Former associate in Dusseldorf and San Francisco offices
“The quality of the people. In the corporate world, the average-caliber employee is far below McKinsey’s least intelligent.” – Wesley Sand
“What stays with me is the rigorous standard of information and analysis, the proving and double-proving of every recommendation, combined with the high standard of communication both to clients and within the Firm.” – Former associate in the Boston and New York offices
“When faced with an amorphous situation, apply structure to it.” – Kristin Asleson, New York office, 1990-93; now working in Silicon Valley
“Execution and implementation are the key. A blue book is just a blue book, unless you do something with it. Getting things done is the most important thing.” – Former EM in the New York office

Scoring in the McKinsey PSG/Digital Assessment

The scoring mechanism in the McKinsey Digital Assessment

McKinsey Comprehensive Package

Unlock all materials helping you land the next job in McKinsey!

Among MBB firms, people tend to say McKinsey is slightly better than the other two in three factors: prestige, people, practices, and offices

At McKinsey, the salary for entry-level consultants ranges from $90,000 to $110,000/year, while the figure for experienced Associates can go up to $233,000

McKinsey hiring process including 3 phases: resume screening, PST test, and case interview. Each candidate will have to undergo 4-6 interviews during 4-8 weeks

Cracked it! pp 35–52 Cite as

The 4S Method

Bernard Garrette 4 ,
Corey Phelps 5 &
Olivier Sibony 4
First Online: 09 June 2018

12k Accesses

The 4S method is an integrated, four-stage problem-solving approach that combines the tools of strategy consulting with insights from cognitive science and design thinking. The first S is to State the problem properly, identifying the core question at hand as well as its context, owner, and stakeholders. The second S is to Structure the problem, either around candidate solution(s) you will test or by splitting the core question into sub-issues that you will investigate systematically. Third, you will Solve the problem. Three distinct paths are possible through these stages: the analytical paths of hypothesis-driven and issue-driven problem solving, discussed in Chaps. 4 , 5 , 6 and 7 , and the creative path of design thinking, covered in Chaps. 8 and 9 . Finally, the fourth stage is to Sell your solution to the problem owner.

This is a preview of subscription content, log in via an institution .

Buying options

Available as EPUB and PDF
Read on any device
Instant download
Own it forever
Compact, lightweight edition
Dispatched in 3 to 5 business days
Free shipping worldwide - see info
Durable hardcover edition

Tax calculation will be finalised at checkout

Purchases are for personal use only

This doesn’t imply that the approach applies only to strategy problems. Indeed, much of the work “strategy” consulting firms do isn’t concerned, strictly speaking, with strategy. The term “strategy consulting” is shorthand for “CEO-level, premium management consulting,” and “strategy” consultants use essentially the same problem-solving approach when solving organizational, operational effectiveness, or marketing problems.

Bacon , F. (1620). Novum Organum, XLIX.

Nickerson, R.S. (1998). Confirmation Bias : A Ubiquitous Phenomenon in Many Guises. Review of General Psychology , 2 (2), 175–220.

Friedman, R.S., & Förster, J. (2001). The Effects of Promotion and Prevention Cues on Creativity . Journal of Personality and Social Psychology, 81 (6), 1001–1013.

Janis, I.L. (1982). Groupthink: Psychological Studies of Policy Decisions and Fiascoes . Boston, MA: Houghton Mifflin.

Liedtka, J. (2017). Evaluating the Impact of Design Thinking in Action. Academy of Management Best Paper Proceedings. Beckman, S.L., & Barry, M. (2007). Innovation as Learning Process: Embedding Design Thinking. California Management Review, 50 (1), 25–56.

Simon , H.A. (1969). The Sciences of the Artificial. Cambridge: MIT Press.

Martin , R.L. (2009). The Design of Business: Why Design Thinking Is the Next Competitive Advantage . Cambridge, MA: Harvard Business Press.

Porter, M.E. (1980). Competitive Strategy. New York: Free Press.

Brown, T . (2009). Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation. New York: HarperBusiness.

Heath, C., & Heath, D. (2007). Made to Stick: Why Some Ideas Survive and Others Die. New York: Random House.

Author information

Authors and affiliations.

HEC Paris School of Management, Jouy-en-Josas, France

Bernard Garrette & Olivier Sibony

Desautels Faculty of Management, McGill University, Montreal, QC, Canada

Corey Phelps

You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

About this chapter

Cite this chapter.

Garrette, B., Phelps, C., Sibony, O. (2018). The 4S Method. In: Cracked it!. Palgrave Macmillan, Cham. https://doi.org/10.1007/978-3-319-89375-4_3

Download citation

DOI : https://doi.org/10.1007/978-3-319-89375-4_3

Published : 09 June 2018

Publisher Name : Palgrave Macmillan, Cham

Print ISBN : 978-3-319-89374-7

Online ISBN : 978-3-319-89375-4

eBook Packages : Business and Management Business and Management (R0)

Share this chapter

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

Publish with us

Policies and ethics

Find a journal
Track your research

INTERPERSONAL SKILLS
Problem Solving and Decision Making

Solve Problems Like a Consultant

Search SkillsYouNeed:

Interpersonal Skills:

A - Z List of Interpersonal Skills
Interpersonal Skills Self-Assessment
Communication Skills
Emotional Intelligence
Conflict Resolution and Mediation Skills
Customer Service Skills
Team-Working, Groups and Meetings
Decision-Making and Problem-Solving
Effective Decision Making
Decision-Making Framework
Introduction to Problem Solving
Identifying and Structuring Problems
Investigating Ideas and Solutions
Implementing a Solution and Feedback
Creative Problem-Solving
Social Problem-Solving
Negotiation and Persuasion Skills
Personal and Romantic Relationship Skills

Subscribe to our FREE newsletter and start improving your life in just 5 minutes a day.

You'll get our 5 free 'One Minute Life Skills' and our weekly newsletter.

We'll never share your email address and you can unsubscribe at any time.

Learning how to break down and solve complex problems is a core skill you need in today’s business world.

The more complex and multi-faceted your problems are, the more your problem solving skills and techniques will be put to the test.

No one understands this better than some of the world's most highly paid and highly regarded problem solving professionals, the strategy consultants whose fame and fortune is dependent on their ability to quickly break down complex problems and develop effective solutions.

This page details two powerful problem solving techniques you can take from the consulting world to begin breaking down your problems and tackling them like a pro.

Problem Solving Technique #1: Focus On The Key Drivers

When analyzing a complex problem, focus your time and energy on the key drivers and big wins; don't get bogged down in the problem solving minutia. And although this sounds obvious, it is easy to inadvertently end up doing the exact opposite when first applying your problem solving techniques.

Consultants recognize that complex problems can have hundreds, if not thousands, of issues surrounding them and that can it be tempting to dig into and analyze them all for potential solutions. To fight this temptation, one problem solving technique that consultants use is to focus their time and energy on the ' key drivers ' of their problem; in other words, they focus on the largest and most salient aspects of the problem that, if solved, would have the biggest immediate impact.

When problem solving, ask yourself this:

"What are two or three 'key drivers,' or main issues, affecting the problem I am trying to solve?"

For example, if you are hired by an organization to cut costs, think of all the different ways you could potentially help them cut costs. Instead of spinning your wheels analyzing all of the potential cost saving areas, you’re better off focusing on the two or three costs that, if reduced, would have the largest overall impact on the organization.

If you're having trouble finding the key drivers of your problem, use the 80-20 rule to find your problem’s highest value components.

The 80-20 Rule: The Secret to Achieving More with Less

The 80-20 rule, or the Pareto principle, was first adopted as a problem solving technique by a management consultant who coined the phrase after Vilfredo Pareto’s 1906 research in which he observed that 20% of the pea pods in his garden produced 80% of the peas.

This principle has since become known as the 80-20 rule, and simply states that 80% of the effects, come from 20% of the causes. When applied to business, the rule can be used as follows:

80% of a company's profits come from 20% of its clients.
80% of a company's costs come from 20% of its operations.
20% of a company's clients produce 80% of its complaints.

Although this is not a universal principle, the distribution often holds true in many aspects of business and life and, as such, is one of the first problem solving techniques used by consultants to get to the heart of an issue.

For example, using the 80-20 problem solving technique for cutting costs, you could start by asking yourself questions like:

Which 20% of the company’s divisions are generating 80% of its costs? – Reduce or reorganize the company’s divisions.
Which 20% of the company’s production costs represent 80% of its cost of goods sold? – Streamline manufacturing processes.
Which 20% of the company’s marketing costs are generating 80% of its new clients? – Cut the marketing fat.

If this problem solving technique produces too many key drivers, you can narrow them down by asking yourself which of them you can build a strong case for with hard data (see #2).

#2: Build Your Case with Hard Data

When problem solving, gathering and analyzing hard data is critical to effectively building a case for, and eventually selling, a solution.

As such, consultants focus their energy on the key drivers that they can prove or disprove, by gathering and analyzing hard factual data.

Executives are not going to give you the time of day unless you can prove your point with convincing facts and figures. As such, assume that no one will listen to you, or your message, unless you have strong factual evidence to back it up.

Arguably the most famous consulting firm in the world, McKinsey, is notorious for its rigorous data gathering methodologies and problem solving analysis. Why such a focus on hard data? As Ethan Rasiel notes in his book, " The McKinsey Way ", hard data allows McKinsey consultants to quickly achieve two things:

Make Up For Lack Of Gut Instinct

Consultants are typically generalists, which means they lack the 30 or 40 years of in-depth industry experience that their clients often have. Whereas a client might have a “gut” instinct for how to solve a specific problem based on their experience, McKinsey consultants will dig for hard data to prove or disprove their clients' “gut” instinct before moving forward.

Bridge The Credibility Gap

Hard data is objective and tends to be less prone to argument. As such, hard data allows McKinsey consultants, who are typically much younger and greener than their clients, to quickly establish credibility and authority when presenting their problem’s solutions.

Recognizing that hard data will be critical to the success of your problem solving, focus on key drivers that you can back up with hard data given your time constraints.

For example, if your solution to the problem of needing to cut an organization's costs was to reorganize all of its divisions into one location, ask yourself whether or not you can get access to enough hard data to thoroughly prove or disprove your solution. If not, ask for a project extension, break your key driver down into smaller pieces, or pick another key driver to focus on.

Two Data Analysis Tips From McKinsey

A common challenge when problem solving complex issues is knowing where to start and when to stop.

Here are two problem solving tips straight from McKinsey:

Problem Solving Tip #1 – Start With The Outliers:

A great problem solving technique when analyzing large sets of data is to calculate a performance metric around your key drivers and focus on the outliers.

For example, costs per unit per region:

Positive outliers (low cost per unit) will surface potential best practices you can mimic.
Negative outliers (high cost per unit) will give you something to immediately figure out and fix.

Problem Solving Tip #2 - Don’t Boil The Ocean:

It’s important to realize that when figuring out how to solve a problem, there is always an enormous amount of research and data analysis you could potentially do.

Instead of trying to perform all of it, which is the equivalent of trying to boil the ocean, McKinsey consultants focus on doing enough research and analysis to thoroughly prove or disprove their key drivers and ignore everything else.

Six problem-solving mindsets for very uncertain times

Great problem solvers are made, not born. That’s what we’ve found after decades of problem solving with leaders across business, nonprofit, and policy sectors. These leaders learn to adopt a particularly open and curious mindset, and adhere to a systematic process for cracking even the most inscrutable problems. They’re terrific problem solvers under any conditions. And when conditions of uncertainty are at their peak, they’re at their brilliant best.

Six mutually reinforcing approaches underly their success: (1) being ever-curious about every element of a problem; (2) being imperfectionists , with a high tolerance for ambiguity; (3) having a “dragonfly eye” view of the world, to see through multiple lenses; (4) pursuing occurrent behavior and experimenting relentlessly; (5) tapping into the collective intelligence , acknowledging that the smartest people are not in the room; and (6) practicing “show and tell” because storytelling begets action (exhibit).

Here’s how they do it.

1. Be ever-curious

As any parent knows, four-year-olds are unceasing askers. Think of the never-ending “whys” that make little children so delightful—and relentless. For the very young, everything is new and wildly uncertain. But they’re on a mission of discovery, and they’re determined to figure things out. And they’re good at it! That high-energy inquisitiveness is why we have high shelves and childproof bottles.

When you face radical uncertainty, remember your four-year-old or channel the four-year-old within you. Relentlessly ask, “Why is this so?” Unfortunately, somewhere between preschool and the boardroom, we tend to stop asking. Our brains make sense of massive numbers of data points by imposing patterns that have worked for us and other humans in the past. That’s why a simple technique, worth employing at the beginning of problem solving, is simply to pause and ask why conditions or assumptions are so until you arrive at the root of the problem. 1 This approach was originally developed by Sakichi Toyoda, the founder of Toyota.

Natural human biases in decision making, including confirmation, availability, and anchoring biases, often cause us to shut down the range of solutions too early. 2 Daniel Kahneman, Thinking, Fast and Slow , New York, NY: Farrar, Straus and Giroux, 2011. Better—and more creative—solutions come from being curious about the broader range of potential answers.

One simple suggestion from author and economist Caroline Webb to generate more curiosity in team problem solving is to put a question mark behind your initial hypotheses or first-cut answers. This small artifice is surprisingly powerful: it tends to encourage multiple solution paths and puts the focus, correctly, on assembling evidence. We also like thesis/antithesis, or red team/blue team, sessions, in which you divide a group into opposing teams that argue against the early answers—typically, more traditional conclusions that are more likely to come from a conventional pattern. Why is this solution better? Why not that one? We’ve found that better results come from embracing uncertainty. Curiosity is the engine of creativity.

We have to be comfortable with estimating probabilities to make good decisions, even when these guesses are imperfect. Unfortunately, we have truckloads of evidence showing that human beings aren’t good intuitive statisticians.

2. Tolerate ambiguity—and stay humble!

When we think of problem solvers, many of us tend to picture a poised and brilliant engineer. We may imagine a mastermind who knows what she’s doing and approaches a problem with purpose. The reality, though, is that most good problem solving has a lot of trial and error; it’s more like the apparent randomness of rugby than the precision of linear programming. We form hypotheses, porpoise into the data, and then surface and refine (or throw out) our initial guess at the answer. This above all requires an embrace of imperfection and a tolerance for ambiguity—and a gambler’s sense of probabilities.

The real world is highly uncertain. Reality unfolds as the complex product of stochastic events and human reactions. The impact of COVID-19 is but one example: we address the health and economic effects of the disease, and their complex interactions, with almost no prior knowledge. We have to be comfortable with estimating probabilities to make good decisions, even when these guesses are imperfect. Unfortunately, we have truckloads of evidence showing that human beings aren’t good intuitive statisticians. Guesses based on gut instinct can be wildly wrong. That’s why one of the keys to operating in uncertain environments is epistemic humility, which Erik Angner defines as “the realization that our knowledge is always provisional and incomplete—and that it might require revision in light of new evidence.” 3 Erik Angner, “Epistemic humility—knowing your limits in a pandemic,” Behavioral Scientist , April 13, 2020, behavioralscientist.org.

Recent research shows that we are better at solving problems when we think in terms of odds rather than certainties. 4 Annie Duke, Thinking in Terms of Bets: Making Smarter Decisions When You Don’t Have All the Facts , New York, NY: Portfolio/Penguin, 2018. For example, when the Australian research body Commonwealth Scientific and Industrial Research Organisation (CSIRO), which owned a core patent on the wireless internet protocol, sought royalties from major companies, it was initially rebuffed. The CSIRO bet that it could go to court to protect its intellectual property because it estimated that it needed only 10 percent odds of success for this to be a good wager, given the legal costs and likely payoff. It improved its odds by picking the weakest of the IP violators and selecting a legal jurisdiction that favored plaintiffs. This probabilistic thinking paid off and eventually led to settlements to CSIRO exceeding $500 million. 5 CSIRO briefing to US Government, December 5, 2006. A tolerance for ambiguity and a willingness to play the odds helped the organization feel its way to a good solution path.

To embrace imperfectionism with epistemic humility, start by challenging solutions that imply certainty. You can do that in the nicest way by asking questions such as “What would we have to believe for this to be true?” This brings to the surface implicit assumptions about probabilities and makes it easier to assess alternatives. When uncertainty is high, see if you can make small moves or acquire information at a reasonable cost to edge out into a solution set. Perfect knowledge is in short supply, particularly for complex business and societal problems. Embracing imperfection can lead to more effective problem solving. It’s practically a must in situations of high uncertainty, such as the beginning of a problem-solving process or during an emergency.

Good problem solving typically involves designing experiments to reduce key uncertainties. Each move provides additional information and builds capabilities.

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

3. take a dragonfly-eye view.

Dragonfly-eye perception is common to great problem solvers. Dragonflies have large, compound eyes, with thousands of lenses and photoreceptors sensitive to different wavelengths of light. Although we don’t know exactly how their insect brains process all this visual information, by analogy they see multiple perspectives not available to humans. The idea of a dragonfly eye taking in 360 degrees of perception 6 Philip Tetlock and Dan Gardner, Superforecasting: The Art and Science of Prediction , New York, NY: Crown, 2015. is an attribute of “superforecasters”—people, often without domain expertise, who are the best at forecasting events.

Think of this as widening the aperture on a problem or viewing it through multiple lenses. The object is to see beyond the familiar tropes into which our pattern-recognizing brains want to assemble perceptions. By widening the aperture, we can identify threats or opportunities beyond the periphery of vision.

Consider the outbreak of HIV in India in the early 1990s—a major public-health threat. Ashok Alexander, director of the Bill & Melinda Gates Foundation’s India Aids Initiative, provided a brilliant example of not just vision but also dragonfly vision. Facing a complex social map with a rapidly increasing infection rate, he widened the problem’s definition, from a traditional epidemiological HIV transmission model at known “hot spots,” to one in which sex workers facing violence were made the centerpiece.

This approach led to the “Avahan solution,” which addressed a broader set of leverage points by including the sociocultural context of sex work. The solution was rolled out to more than 600 communities and eventually credited with preventing 600,000 infections. The narrow medical perspective was sensible and expected, but it didn’t tap into the related issue of violence against sex workers, which yielded a richer solution set. Often, a secret unlocks itself only when one looks at a problem from multiple perspectives, including some that initially seem orthogonal.

The secret to developing a dragonfly-eye view is to “anchor outside” rather than inside when faced with problems of uncertainty and opportunity. Take the broader ecosystem as a starting point. That will encourage you to talk with customers, suppliers, or, better yet, players in a different but related industry or space. Going through the customer journey with design-thinking in mind is another powerful way to get a 360-degree view of a problem. But take note: when decision makers face highly constrained time frames or resources, they may have to narrow the aperture and deliver a tight, conventional answer.

Want better strategies? Become a bulletproof problem solver

4. pursue occurrent behavior.

Occurrent behavior is what actually happens in a time and place, not what was potential or predicted behavior. Complex problems don’t give up their secrets easily. But that shouldn’t deter problem solvers from exploring whether evidence on the facets of a solution can be observed, or running experiments to test hypotheses. You can think of this approach as creating data rather than just looking for what has been collected already. It’s critical for new market entry—or new market creation. It also comes in handy should you find that crunching old data is leading to stale solutions.

Most of the problem-solving teams we are involved with have twin dilemmas of uncertainty and complexity, at times combined as truly “wicked problems.” 7 A term coined in a now famous 1973 article: Horst W. J. Rittel and Melvin Webber, “Dilemmas in a general theory of planning,” Policy Sciences , 1973, Number 4, pp. 155–69. For companies ambitious to win in the great unknown in an emerging segment—such as electric cars or autonomous vehicles, where the market isn’t fully established—good problem solving typically involves designing experiments to reduce key uncertainties, not just relying on existing data. Each move (such as buying IP or acquiring a component supplier) and each experiment (including on-road closed tests) not only provides additional information to make decisions but also builds capabilities and assets that support further steps. Over time, their experiments, including alliances and acquisitions, come to resemble staircases that lead to either the goal or to abandonment of the goal. Problem-solving organizations can “bootstrap” themselves into highly uncertain new spaces, building information, foundational assets, and confidence as they take steps forward.

Risk-embracing problem solvers find a solution path by constantly experimenting. Statisticians use the abbreviation EVPI—the expected value of perfect information—to show the value of gaining additional information that typically comes from samples and experiments, such as responses to price changes in particular markets. A/B testing is a powerful tool for experimenting with prices, promotions, and other features and is particularly useful for digital marketplaces and consumer goods. Online marketplaces make A/B testing easy. Yet most conventional markets also offer opportunities to mimic the market’s segmentation and use it to test different approaches.

The mindset required to be a restless experimenter is consistent with the notion in start-ups of “failing fast.” It means that you get product and customer affirmation or rejection quickly through beta tests and trial offerings. Don’t take a lack of external data as an impediment—it may actually be a gift, since purchasable data is almost always from a conventional way of meeting needs, and is available to your competitors too. Your own experiments allow you to generate your own data; this gives you insights that others don’t have. If it is difficult (or unethical) to experiment, look for the “natural experiments” provided by different policies in similar locations. An example would be to compare outcomes in twin cities, such as Minneapolis–St. Paul.

It’s a mistake to think that your team has the smartest people in the room. They aren’t there. They’re invariably somewhere else. Nor do they need to be there if you can access their intelligence via other means.

5. Tap into collective intelligence and the wisdom of the crowd

Chris Bradley, a coauthor of Strategy Beyond the Hockey Stick , 8 Chris Bradley, Marin Hirt, and Sven Smit, Strategy Beyond the Hockey Stick: People, Probabilities, and Big Moves to Beat the Odds , Hoboken, NJ: Wiley, 2018. observed that “it’s a mistake to think that on your team you have the smartest people in the room. They aren’t there. They’re invariably somewhere else.” 9 For more from Chris Bradley, in a conversation with Rob McLean, see “ Want better strategies? Become a bulletproof problem solver ,” August 2019. Nor do they need to be there if you can access their intelligence via other means. In an ever-changing world where conditions can evolve unpredictably, crowdsourcing invites the smartest people in the world to work with you. For example, in seeking a machine-learning algorithm to identify fish catch species and quantities on fishing boats, the Nature Conservancy (TNC) turned to Kaggle and offered a $150,000 prize for the best algorithm. This offer attracted 2,293 teams from all over the world. TNC now uses the winning algorithm to identify fish types and sizes caught on fishing boats in Asia to protect endangered Pacific tuna and other species.

Crowdsourced problem solving is familiar in another guise: benchmarking. When Sir Rod Carnegie was CEO of Conzinc Riotinto Australia (CRA), he was concerned about the costs of unscheduled downtime with heavy trucks, particularly those requiring tire changes. He asked his management team who was best in the world at changing tires; their answer was Formula One, the auto racing competition. A team traveled to the United Kingdom to learn best practice for tire changes in racetrack pits and then implemented what it learned thousands of miles away, in the Pilbara region of Western Australia. The smartest team for this problem wasn’t in the mining industry at all.

Of course, while crowdsourcing can be useful when conventional thinking yields solutions that are too expensive or incomplete for the challenge at hand, it has its limitations. Good crowdsourcing takes time to set up, can be expensive, and may signal to your competitors what you are up to. Beware of hidden costs, such as inadvertently divulging information and having to sieve through huge volumes of irrelevant, inferior suggestions to find the rare gem of a solution.

Accept that it’s OK to draw on diverse experiences and expertise other than your own. Start with brainstorming sessions that engage people from outside your team. Try broader crowdsourcing competitions to generate ideas. Or bring in deep-learning talent to see what insights exist in your data that conventional approaches haven’t brought to light. The broader the circles of information you access, the more likely it is that your solutions will be novel and creative.

Rookie problem solvers show you their analytic process and math to convince you they are clever. Seasoned problem solvers show you differently.

6. Show and tell to drive action

We started our list of mindsets with a reference to children, and we return to children now, with “show and tell.” As you no doubt remember—back when you were more curious!—show and tell is an elementary-school activity. It’s not usually associated with problem solving, but it probably piqued your interest. In fact, this approach is critical to problem solving. Show and tell is how you connect your audience with the problem and then use combinations of logic and persuasion to get action.

The show-and-tell mindset aims to bring decision makers into a problem-solving domain you have created. A team from the Nature Conservancy, for instance, was presenting a proposal asking a philanthropic foundation to support the restoration of oyster reefs. Before the presentation, the team brought 17 plastic buckets of water into the boardroom and placed them around the perimeter. When the foundation’s staff members entered the room, they immediately wanted to know what the buckets were for. The team explained that oyster-reef restoration massively improves water quality because each oyster filters 17 buckets of water per day. Fish stocks improve, and oysters can also be harvested to help make the economics work. The decision makers were brought into the problem-solving domain through show and tell. They approved the funding requested and loved the physical dimension of the problem they were part of solving.

Rookie problem solvers show you their analytic process and mathematics to convince you that they are clever. That’s sometimes called APK, the anxious parade of knowledge. But seasoned problem solvers show you differently. The most elegant problem solving is that which makes the solution obvious. The late economist Herb Simon put it this way: “Solving a problem simply means representing it so as to make the solution transparent.” 10 Herbert Simon, The Sciences of the Artificial , Cambridge, MA: MIT Press, 1969.

To get better at show and tell, start by being clear about the action that should flow from your problem solving and findings: the governing idea for change. Then find a way to present your logic visually so that the path to answers can be debated and embraced. Present the argument emotionally as well as logically, and show why the preferred action offers an attractive balance between risks and rewards. But don’t stop there. Spell out the risks of inaction, which often have a higher cost than imperfect actions have.

The mindsets of great problem solvers are just as important as the methods they employ. A mindset that encourages curiosity, embraces imperfection, rewards a dragonfly-eye view of the problem, creates new data from experiments and collective intelligence, and drives action through compelling show-and-tell storytelling creates radical new possibilities under high levels of unpredictability. Of course, these approaches can be helpful in a broad range of circumstances, but in times of massive uncertainty, they are essential.

Charles Conn is an alumnus of McKinsey’s Sydney office and is a board member of Patagonia and former CEO of the Rhodes Trust. Robert McLean is an alumnus of the Sydney office and is the advisory-board chair of the Nature Conservancy Australia. They are the authors of Bulletproof Problem Solving: The One Skill That Changes Everything (Wiley, 2018).

This article was edited by David Schwartz, an executive editor in the Tel Aviv office.

Explore a career with us

Strategy to beat the odds

Dwight Eisenhower: Lessons from the ‘balancer in chief’

Back to All Programs /

The Consultant’s Toolkit: Consulting Training

Refine your consulting abilities through proven techniques to improve organizational effectiveness.

All Start Dates

8:30 AM – 4:30 PM ET

2 consecutive days

Registration Deadline

April 14, 2024

11:00 AM – 2:30 PM ET

4 consecutive Tuesdays

July 1, 2024

Live Online: $2,750 On-Campus: $2,990

September 15, 2024

November 24, 2024

The Consultant’s Toolkit Overview

Organizations look to consultants to provide necessary guidance on important business decisions. Designed for internal consultants with less than seven years of experience, The Consultant’s Toolkit program explores a variety of consulting tools to teach you how to diagnose organizational problems and evaluate potential solutions, enhancing your ability to confidently present recommendations to your clients and drive successful outcomes.

Some of the topics you’ll cover in the program include:

Strategic frameworks for the consulting process
Operational diagnostic tools
Hypothesis trees
Research methods
Presenting recommendations

Through a combination of lecture, case discussions, and interactive group exercises, this program focuses on teaching analytic techniques that can be applied in diverse settings, ranging from small and large companies to for-profit and nonprofit organizations.

Who Should Take the Consultant’s Toolkit Training?

This program is designed to offer significant benefits to internal consultants and individuals who are currently collaborating with consultants or seeking to integrate consulting tools and techniques into their organizations.

Participants with less than seven years of consulting experience can expect to discover additional tools to enhance their expanding toolkit. However, those with over seven years of experience may find the content too foundational.

Program participants hold positions such as:

Financial consultant
Project manager
Human Resources manager
Business Analyst
Solutions consultant
Political strategist

Individuals working within small or medium-sized consulting firms, as well as internal and independent consultants, will find this program most beneficial. This program is not recommended for consultants from the largest consulting firms.

Benefits of the Consultant’s Toolkit Training

The Consultant’s Toolkit program offers the opportunity to develop a strong knowledge base and skills required to complete successful consulting projects.

Participants will learn:

The baseline for success in a consulting role and an understanding of the consulting process
Various consulting techniques in areas of strategic formulation, market research, operations, performance management, and project management
Effective methods for achieving impactful implementation
Essential consulting skills for collecting, analyzing, and presenting data
How to engage more effectively with independent consultants working for your organization

Upon completion of the program, you will receive a Certificate of Participation from the Harvard Division of Continuing Education recognizing your achievement.

In The Consultant’s Toolkit, you will learn through a combination of lecture, case studies, and interactive group exercises. Topics covered include:

An overview of the consulting industry, trends, and the role of consultants
Problem definition
Discovery and data collection
Recommendation and presentation
Implementation
Dealing with resistance

The Consultant’s Toolkit Program is offered in on-campus or online formats. On-campus courses are held at our state-of-the-art classroom space in the heart of historic Harvard University. Online courses are held live via Zoom for 3.5 hours one day per week for four weeks.

Considering this program?

Send yourself the details.

Related Programs

Advanced Business Strategy Training: Gaining a Competitive Edge
Beyond Strategic Planning: From Implementation to Sustainment
Negotiation Skills: Strategies for Increased Effectiveness

April Schedule

The Consulting Industry Today
Defining the Problem
Structuring and Solving the Problem
Essential Consulting Frameworks
Persuading the Decisionmakers
Keys for Impactful Implementation

July Schedule

September schedule.

Participate live online or on campus.

Join us this September for a unique hybrid offering of this popular program, with participants attending simultaneously on campus and live online (over Zoom).

Register for live online: Enter our state-of-the-art classroom from the comfort of your home or office. You will be fully integrated into the program experience, with the ability to see, hear, contribute, and network alongside your in-person counterparts.
Register for on campus: Learn and collaborate in our classroom space in the heart of the historic Harvard campus. Your experience will be augmented by the opportunity to network—both in-person and virtually—with colleagues from around the country and the world.

December Schedule

Shawn o’connor, david mcintosh, expand your network.

With participants from more than 100 different countries and a variety of industries, Harvard Professional & Executive Development programs provide you the opportunity to gain fresh perspectives and unique insights as you learn alongside peers with similar roles who face like business challenges.

How do I know if the Consultant’s Toolkit program is right for me?

This program is designed for internal consultants and those who work with consultants. If you are looking at training courses to improve the consulting process within your organization, this program is right for you.

The Consultant’s Toolkit will provide internal consultants with the valuable consulting skills they need to succeed. However, if you have more than seven years of experience or work in one of the larger consulting firms, you may find this program to be too fundamental.

How will the Consultant’s Toolkit program help me improve my career or company?

Participating in The Consultant’s Toolkit program demonstrates your proficiency in consulting tools and techniques, making you a valuable asset to your current or future organization. With this program, you can upskill or reskill to show initiative and develop new strengths, which you can demonstrate in your next consulting project.

Harvard Division of Continuing Education

The Division of Continuing Education (DCE) at Harvard University is dedicated to bringing rigorous academics and innovative teaching capabilities to those seeking to improve their lives through education. We make Harvard education accessible to lifelong learners from high school to retirement.

Hypothesis-Driven Approach: Crack Your Case Like a Consultant

Last Updated June, 2023

A hypothesis-driven approach in consulting is a structured method of problem-solving. Consultants formulate a hypothesis for the solution to a business problem, then gather data to support or disprove it.

Cracking a case interview can be a daunting task, with a wide range of potential solutions and approaches to consider. However, using a hypothesis-driven approach is a systematic and effective problem-solving method. It will impress your interviewer and demonstrate your readiness for a career in consulting.

In this article, we will talk about:

The definitions of a hypothesis and a hypothesis-driven approach
The differences between a hypothesis-driven approach and a non-hypothesis-driven approach
An example of how to solve a case using both approaches
Our 5-step process for using a hypothesis-driven approach to solve consulting cases

Let’s get started!

What Is a Hypothesis & a Hypothesis-Driven Approach?

Differences between a hypothesis-driven approach vs. non-hypothesis-driven approach, our 5-step process for using the hypothesis-driven mindset to solve cases, other consulting tools that will strengthen your problem-solving.

In the realm of science, the term “hypothesis” is used to describe a proposed explanation for a question or phenomenon, based on limited evidence, as a starting point for further investigation. Similarly, consultants act as scientists or as doctors solving their clients’ business problems, constantly forming and testing hypotheses to identify the best solutions.

The key phrase here is “starting point,” as a hypothesis is an educated guess at the solution, formed from currently available information. As more data is gathered, the hypothesis may be adjusted or even discarded entirely.

Nail the case & fit interview with strategies from former MBB Interviewers that have helped 89.6% of our clients pass the case interview.

Hypothesis-Driven Approach

Consultants are engaged to efficiently and effectively solve their clients’ problems and assist in making critical business decisions. With the vast amount of data available and an array of options to consider, it can be overwhelming to examine everything. Time constraints on projects make it imperative that consultants avoid getting bogged down in excessive analysis and questioning, without making meaningful progress toward a recommendation.

Instead, consultants begin by forming a hypothesis after gaining an understanding of the client’s problem and high-level range of possibilities. Then, they gather data to test the initial hypothesis. If the data disproves the hypothesis, the consultants repeat the process with the next best hypothesis. This method of problem-solving is commonly used by top consulting firms, such as McKinsey.

A non-hypothesis-driven approach is the opposite of a hypothesis-driven approach. Instead of forming a hypothesis, the individual makes a recommendation only after thoroughly evaluating all data and possibilities. This approach may rely on intuition, trial and error, or exhaustively exploring all options to solve the problem. This is not an efficient method for a case interview, where time is limited.

An analogy that illustrates the distinction between the two methods is to look at problem-solving as trying to find a needle in a haystack. A non-hypothesis-driven approach would involve randomly searching through the entire stack without any clear strategy.

On the other hand, a hypothesis-driven approach would involve dividing the haystack into smaller piles, and systematically searching through one section at a time. The searcher would gather information from the person who lost the needle, such as their location when it was lost, to identify the most likely pile to search first. This not only saves time but also increases the likelihood of finding the needle. If the needle is not found in the initial pile, the search can then move on to the next most probable pile.

Solving a Case Interview Using the Hypothesis-Driven Approach vs. the Non-Hypothesis-Driven Approach

To further illustrate the advantages of a hypothesis-driven approach, let’s examine two different approaches to the same case interview example. We’ll compare and contrast these approaches, highlighting the key distinctions between them. By the end, you’ll have a clear understanding of the benefits of using a hypothesis-driven approach in problem-solving.

The client is SnackCo, a consumer goods company that manufactures and sells trail mixes in the United States. Over the past decade, SnackCo has seen significant growth following the launch of premium trail mix products, capitalizing on the trend toward healthier snacking options. Despite this success, the company’s operations have remained unchanged for the past decade. SnackCo is asking for your help to improve its bottom line.

Let’s look at how two candidates, Alex and Julie, solve the same case.

The Non-Hypothesis-Driven Approach

After hearing this prompt, Alex jumps right into listing possible questions related to how to improve the bottom line.

Alex: I understand SnackCo wants to improve profitability. Here are some questions I want to look into. Has SnackCo’s retail prices remained the same in recent years?

Interviewer: No, SnackCo has adjusted prices quite closely to what competitive products are selling at.

Alex: Oh interesting. Are consumers willing to pay more for premium trail mix? Do we know if we are underpricing?

Interviewer: SnackCo’s Director of Sales strongly believes that they should not change product prices. He believes the consumers love the product and it is priced fairly.

Alex: Got it. Has the client’s market share decreased?

Interviewer: No, the market share has increased over the years.

Alex: In that case, it seems like our growth is fine. Have the costs increased?

Interviewer: SnackCo has not made many changes to its costs and operations in the last decade. What are some ways we can help them look at their cost savings opportunities?

Although Alex is making progress and may eventually solve the case, his communication style gives the impression that he is randomly guessing at the sources of the problem, rather than using logical reasoning and structure to pinpoint the solution.

The Hypothesis-Driven Approach

Julie has prepared for her case interviews with My Consulting Offer’s coaches so she is well-versed in the hypothesis-driven approach.

After hearing the same prompt, she takes a moment to write down the key issues she wants to dig into to solve this case and organizes her thoughts.

Julie: For the goal of improving profitability, we could look at how to improve revenue or decrease costs. For revenue, we could look at if prices or volumes have changed. Since the client said they haven’t made any changes to the business operations in the last decade, I would like to start with a better understanding of their costs. However, before we begin, I want to confirm if there have been any changes to prices or volumes recently.

Interviewer: SnackCo’s Director of Sales strongly believes that they should not change product prices. They also believe the volumes have grown well as SnackCo is one of the market leaders now.

Julie: Great. That confirms what I was thinking. It’s likely a cost problem. We could look at their variable costs, such as ingredients, or fixed costs, such as manufacturing facilities. Given that this is an established business, I would assume their fixed costs are likely consistent. Therefore, let’s start with their variable costs.

Interviewer: How should we think about variable costs?

Julie: Variable costs for SnackCo likely include ingredients, packaging, and freight. The levers they could pull to reduce these costs would be through supplier relationships or changing the product composition.

Julie quickly identifies that variable costs are likely the problem and has a structured approach to understanding which opportunities to explore.

Key Differences

The interviewer is looking for candidates with strong problem-solving and communication skills, which are the qualities of a good consultant. Let’s look at how the two candidates performed.

Problem-Solving

Alex’s approach to solving the client’s problem was haphazard, as he posed a series of seemingly unrelated questions in no particular order. This method felt more like a rapid-fire Q&A session rather than a structured problem-solving approach.

On the other hand, Julie takes a structured and analytical approach to address profitability concerns. She quickly realizes that while revenue is one factor of profitability, it is likely costs that are the main concern, as they haven’t changed much in the last decade. She then breaks down the major cost categories and concludes that variable costs are the most likely opportunity for cost reduction. Julie is laser-focused on the client’s goal and efficiently gets to a solution.

Communication

Alex is not making a positive initial impression. If this were an actual client interaction, his questioning would appear disorganized and unprofessional.

On the other hand, Julie appears more organized through her clear communication style. She only considers the most pertinent issues at hand (i.e., the client’s business operations and costs) and avoids going down irrelevant rabbit holes.

Understand the client’s problem; ask clarifying questions if needed.
Formulate an issue tree to break down the problem into smaller parts.
State the initial hypothesis and key assumptions to be tested.
Gather and analyze information to prove or disprove the hypothesis; do not panic if the hypothesis is disproven.
Pivot the hypothesis if necessary and repeat step 4. Otherwise, make your recommendation on what the client can do to solve their problem.

Other helpful tips to remember when using the hypothesis-driven approach:

Stay focused on the client’s problem and remember what the end goal is.
Think outside the box and consider new perspectives beyond traditional frameworks. The basic case interview frameworks are useful to understand but interviewers expect candidates to tailor to the specific client situation.
Clearly communicate assumptions and implications throughout the interview; don’t assume the interviewer can read your mind.

A hypothesis-driven approach is closely tied to other key consulting concepts, such as issue trees, MECE, and 80/20. Let’s take a closer look at these topics and how they relate.

Issue Trees

Issue trees, also known as decision trees, are visual tools that break down complex business problems into smaller, more manageable parts. In a consulting interview, candidates use the issue tree to outline key issues and potential factors in the client’s problem, demonstrating their understanding of the situation. This structure is then used to guide the case discussion, starting with the candidate’s best hypothesis, represented as one branch of the issue tree. For more information and examples of issue trees, check out our i ssue tree post.

During the interview process, consulting firms look for candidates who can demonstrate a MECE (mutually exclusive and collectively exhaustive) approach to problem-solving, which involves breaking down complex issues into distinct, non-overlapping components.

A MECE approach in case interviews involves identifying all potential paths to solving a client’s problem at a high level. This allows the candidate to form an initial hypothesis with confidence that no potential solutions have been overlooked. To gain a deeper understanding, read our comprehensive guide on the MECE case structure .

Consultants use the 80/20 rule, also known as the Pareto principle, to prioritize their efforts and focus on the most important things. This principle states that 80% of effects come from 20% of causes, which means a small number of issues often drive a large portion of the problem. By identifying and focusing on the key issues, consultants can achieve significant results with relatively minimal resources.

By following these tips and developing a solid understanding of the hypothesis-driven approach to case-solving, you will have the necessary tools to excel in your case interview. For more interview resources, check out Our Ultimate Guide to Case Interview Prep .

– – – – –

In this article, we’ve covered:

Explanations of a hypothesis and hypothesis-driven approach
Comparison between a hypothesis-driven approach and a non-hypothesis-driven approach
Examples of the same case using both approaches and the key differences
Practical tips on how to develop a hypothesis-driven mindset to ace the case

Still have questions?

If you have more questions about the best degrees for a career in consulting, leave them in the comments below. One of My Consulting Offer’s recruiters will answer them.

Other people preparing to apply to consulting firms found the following pages helpful:

Our Ultimate Guide to Case Interview Prep
Types of Case Interviews
Case Frameworks
Hypothesis Trees

Help with Your Consulting Application

Thanks for turning to My Consulting Offer for advice on the best majors for consulting. My Consulting Offer has helped almost 89.6% of the people we’ve worked with to get a job in management consulting. We want you to be successful in your consulting interviews too. For example, here is how Misha was able to get his offer from BCG.

3 Top Strategies to Master the Case Interview in Under a Week

We are sharing our powerful strategies to pass the case interview even if you have no business background, zero casing experience, or only have a week to prepare.

No thanks, I don't want free strategies to get into consulting.

We are excited to invite you to the online event., where should we send you the calendar invite and login information.

SUGGESTED TOPICS
The Magazine
Newsletters
Managing Yourself
Managing Teams
Work-life Balance
The Big Idea
Data & Visuals
Reading Lists
Case Selections
HBR Learning
Topic Feeds
Account Settings
Email Preferences

Share Podcast

Do You Understand the Problem You’re Trying to Solve?

To solve tough problems at work, first ask these questions.

Apple Podcasts
Google Podcasts

Problem solving skills are invaluable in any job. But all too often, we jump to find solutions to a problem without taking time to really understand the dilemma we face, according to Thomas Wedell-Wedellsborg , an expert in innovation and the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

In this episode, you’ll learn how to reframe tough problems by asking questions that reveal all the factors and assumptions that contribute to the situation. You’ll also learn why searching for just one root cause can be misleading.

Key episode topics include: leadership, decision making and problem solving, power and influence, business management.

HBR On Leadership curates the best case studies and conversations with the world’s top business and management experts, to help you unlock the best in those around you. New episodes every week.

Listen to the original HBR IdeaCast episode: The Secret to Better Problem Solving (2016)
Find more episodes of HBR IdeaCast
Discover 100 years of Harvard Business Review articles, case studies, podcasts, and more at HBR.org .

HANNAH BATES: Welcome to HBR on Leadership , case studies and conversations with the world’s top business and management experts, hand-selected to help you unlock the best in those around you.

Problem solving skills are invaluable in any job. But even the most experienced among us can fall into the trap of solving the wrong problem.

Thomas Wedell-Wedellsborg says that all too often, we jump to find solutions to a problem – without taking time to really understand what we’re facing.

He’s an expert in innovation, and he’s the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

In this episode, you’ll learn how to reframe tough problems, by asking questions that reveal all the factors and assumptions that contribute to the situation. You’ll also learn why searching for one root cause can be misleading. And you’ll learn how to use experimentation and rapid prototyping as problem-solving tools.

This episode originally aired on HBR IdeaCast in December 2016. Here it is.

SARAH GREEN CARMICHAEL: Welcome to the HBR IdeaCast from Harvard Business Review. I’m Sarah Green Carmichael.

Problem solving is popular. People put it on their resumes. Managers believe they excel at it. Companies count it as a key proficiency. We solve customers’ problems.

The problem is we often solve the wrong problems. Albert Einstein and Peter Drucker alike have discussed the difficulty of effective diagnosis. There are great frameworks for getting teams to attack true problems, but they’re often hard to do daily and on the fly. That’s where our guest comes in.

Thomas Wedell-Wedellsborg is a consultant who helps companies and managers reframe their problems so they can come up with an effective solution faster. He asks the question “Are You Solving The Right Problems?” in the January-February 2017 issue of Harvard Business Review. Thomas, thank you so much for coming on the HBR IdeaCast .

THOMAS WEDELL-WEDELLSBORG: Thanks for inviting me.

SARAH GREEN CARMICHAEL: So, I thought maybe we could start by talking about the problem of talking about problem reframing. What is that exactly?

THOMAS WEDELL-WEDELLSBORG: Basically, when people face a problem, they tend to jump into solution mode to rapidly, and very often that means that they don’t really understand, necessarily, the problem they’re trying to solve. And so, reframing is really a– at heart, it’s a method that helps you avoid that by taking a second to go in and ask two questions, basically saying, first of all, wait. What is the problem we’re trying to solve? And then crucially asking, is there a different way to think about what the problem actually is?

SARAH GREEN CARMICHAEL: So, I feel like so often when this comes up in meetings, you know, someone says that, and maybe they throw out the Einstein quote about you spend an hour of problem solving, you spend 55 minutes to find the problem. And then everyone else in the room kind of gets irritated. So, maybe just give us an example of maybe how this would work in practice in a way that would not, sort of, set people’s teeth on edge, like oh, here Sarah goes again, reframing the whole problem instead of just solving it.

THOMAS WEDELL-WEDELLSBORG: I mean, you’re bringing up something that’s, I think is crucial, which is to create legitimacy for the method. So, one of the reasons why I put out the article is to give people a tool to say actually, this thing is still important, and we need to do it. But I think the really critical thing in order to make this work in a meeting is actually to learn how to do it fast, because if you have the idea that you need to spend 30 minutes in a meeting delving deeply into the problem, I mean, that’s going to be uphill for most problems. So, the critical thing here is really to try to make it a practice you can implement very, very rapidly.

There’s an example that I would suggest memorizing. This is the example that I use to explain very rapidly what it is. And it’s basically, I call it the slow elevator problem. You imagine that you are the owner of an office building, and that your tenants are complaining that the elevator’s slow.

Now, if you take that problem framing for granted, you’re going to start thinking creatively around how do we make the elevator faster. Do we install a new motor? Do we have to buy a new lift somewhere?

The thing is, though, if you ask people who actually work with facilities management, well, they’re going to have a different solution for you, which is put up a mirror next to the elevator. That’s what happens is, of course, that people go oh, I’m busy. I’m busy. I’m– oh, a mirror. Oh, that’s beautiful.

And then they forget time. What’s interesting about that example is that the idea with a mirror is actually a solution to a different problem than the one you first proposed. And so, the whole idea here is once you get good at using reframing, you can quickly identify other aspects of the problem that might be much better to try to solve than the original one you found. It’s not necessarily that the first one is wrong. It’s just that there might be better problems out there to attack that we can, means we can do things much faster, cheaper, or better.

SARAH GREEN CARMICHAEL: So, in that example, I can understand how A, it’s probably expensive to make the elevator faster, so it’s much cheaper just to put up a mirror. And B, maybe the real problem people are actually feeling, even though they’re not articulating it right, is like, I hate waiting for the elevator. But if you let them sort of fix their hair or check their teeth, they’re suddenly distracted and don’t notice.

But if you have, this is sort of a pedestrian example, but say you have a roommate or a spouse who doesn’t clean up the kitchen. Facing that problem and not having your elegant solution already there to highlight the contrast between the perceived problem and the real problem, how would you take a problem like that and attack it using this method so that you can see what some of the other options might be?

THOMAS WEDELL-WEDELLSBORG: Right. So, I mean, let’s say it’s you who have that problem. I would go in and say, first of all, what would you say the problem is? Like, if you were to describe your view of the problem, what would that be?

SARAH GREEN CARMICHAEL: I hate cleaning the kitchen, and I want someone else to clean it up.

THOMAS WEDELL-WEDELLSBORG: OK. So, my first observation, you know, that somebody else might not necessarily be your spouse. So, already there, there’s an inbuilt assumption in your question around oh, it has to be my husband who does the cleaning. So, it might actually be worth, already there to say, is that really the only problem you have? That you hate cleaning the kitchen, and you want to avoid it? Or might there be something around, as well, getting a better relationship in terms of how you solve problems in general or establishing a better way to handle small problems when dealing with your spouse?

SARAH GREEN CARMICHAEL: Or maybe, now that I’m thinking that, maybe the problem is that you just can’t find the stuff in the kitchen when you need to find it.

THOMAS WEDELL-WEDELLSBORG: Right, and so that’s an example of a reframing, that actually why is it a problem that the kitchen is not clean? Is it only because you hate the act of cleaning, or does it actually mean that it just takes you a lot longer and gets a lot messier to actually use the kitchen, which is a different problem. The way you describe this problem now, is there anything that’s missing from that description?

SARAH GREEN CARMICHAEL: That is a really good question.

THOMAS WEDELL-WEDELLSBORG: Other, basically asking other factors that we are not talking about right now, and I say those because people tend to, when given a problem, they tend to delve deeper into the detail. What often is missing is actually an element outside of the initial description of the problem that might be really relevant to what’s going on. Like, why does the kitchen get messy in the first place? Is it something about the way you use it or your cooking habits? Is it because the neighbor’s kids, kind of, use it all the time?

There might, very often, there might be issues that you’re not really thinking about when you first describe the problem that actually has a big effect on it.

SARAH GREEN CARMICHAEL: I think at this point it would be helpful to maybe get another business example, and I’m wondering if you could tell us the story of the dog adoption problem.

THOMAS WEDELL-WEDELLSBORG: Yeah. This is a big problem in the US. If you work in the shelter industry, basically because dogs are so popular, more than 3 million dogs every year enter a shelter, and currently only about half of those actually find a new home and get adopted. And so, this is a problem that has persisted. It’s been, like, a structural problem for decades in this space. In the last three years, where people found new ways to address it.

So a woman called Lori Weise who runs a rescue organization in South LA, and she actually went in and challenged the very idea of what we were trying to do. She said, no, no. The problem we’re trying to solve is not about how to get more people to adopt dogs. It is about keeping the dogs with their first family so they never enter the shelter system in the first place.

In 2013, she started what’s called a Shelter Intervention Program that basically works like this. If a family comes and wants to hand over their dog, these are called owner surrenders. It’s about 30% of all dogs that come into a shelter. All they would do is go up and ask, if you could, would you like to keep your animal? And if they said yes, they would try to fix whatever helped them fix the problem, but that made them turn over this.

And sometimes that might be that they moved into a new building. The landlord required a deposit, and they simply didn’t have the money to put down a deposit. Or the dog might need a $10 rabies shot, but they didn’t know how to get access to a vet.

And so, by instigating that program, just in the first year, she took her, basically the amount of dollars they spent per animal they helped went from something like $85 down to around $60. Just an immediate impact, and her program now is being rolled out, is being supported by the ASPCA, which is one of the big animal welfare stations, and it’s being rolled out to various other places.

And I think what really struck me with that example was this was not dependent on having the internet. This was not, oh, we needed to have everybody mobile before we could come up with this. This, conceivably, we could have done 20 years ago. Only, it only happened when somebody, like in this case Lori, went in and actually rethought what the problem they were trying to solve was in the first place.

SARAH GREEN CARMICHAEL: So, what I also think is so interesting about that example is that when you talk about it, it doesn’t sound like the kind of thing that would have been thought of through other kinds of problem solving methods. There wasn’t necessarily an After Action Review or a 5 Whys exercise or a Six Sigma type intervention. I don’t want to throw those other methods under the bus, but how can you get such powerful results with such a very simple way of thinking about something?

THOMAS WEDELL-WEDELLSBORG: That was something that struck me as well. This, in a way, reframing and the idea of the problem diagnosis is important is something we’ve known for a long, long time. And we’ve actually have built some tools to help out. If you worked with us professionally, you are familiar with, like, Six Sigma, TRIZ, and so on. You mentioned 5 Whys. A root cause analysis is another one that a lot of people are familiar with.

Those are our good tools, and they’re definitely better than nothing. But what I notice when I work with the companies applying those was those tools tend to make you dig deeper into the first understanding of the problem we have. If it’s the elevator example, people start asking, well, is that the cable strength, or is the capacity of the elevator? That they kind of get caught by the details.

That, in a way, is a bad way to work on problems because it really assumes that there’s like a, you can almost hear it, a root cause. That you have to dig down and find the one true problem, and everything else was just symptoms. That’s a bad way to think about problems because problems tend to be multicausal.

There tend to be lots of causes or levers you can potentially press to address a problem. And if you think there’s only one, if that’s the right problem, that’s actually a dangerous way. And so I think that’s why, that this is a method I’ve worked with over the last five years, trying to basically refine how to make people better at this, and the key tends to be this thing about shifting out and saying, is there a totally different way of thinking about the problem versus getting too caught up in the mechanistic details of what happens.

SARAH GREEN CARMICHAEL: What about experimentation? Because that’s another method that’s become really popular with the rise of Lean Startup and lots of other innovation methodologies. Why wouldn’t it have worked to, say, experiment with many different types of fixing the dog adoption problem, and then just pick the one that works the best?

THOMAS WEDELL-WEDELLSBORG: You could say in the dog space, that’s what’s been going on. I mean, there is, in this industry and a lot of, it’s largely volunteer driven. People have experimented, and they found different ways of trying to cope. And that has definitely made the problem better. So, I wouldn’t say that experimentation is bad, quite the contrary. Rapid prototyping, quickly putting something out into the world and learning from it, that’s a fantastic way to learn more and to move forward.

My point is, though, that I feel we’ve come to rely too much on that. There’s like, if you look at the start up space, the wisdom is now just to put something quickly into the market, and then if it doesn’t work, pivot and just do more stuff. What reframing really is, I think of it as the cognitive counterpoint to prototyping. So, this is really a way of seeing very quickly, like not just working on the solution, but also working on our understanding of the problem and trying to see is there a different way to think about that.

If you only stick with experimentation, again, you tend to sometimes stay too much in the same space trying minute variations of something instead of taking a step back and saying, wait a minute. What is this telling us about what the real issue is?

SARAH GREEN CARMICHAEL: So, to go back to something that we touched on earlier, when we were talking about the completely hypothetical example of a spouse who does not clean the kitchen–

THOMAS WEDELL-WEDELLSBORG: Completely, completely hypothetical.

SARAH GREEN CARMICHAEL: Yes. For the record, my husband is a great kitchen cleaner.

You started asking me some questions that I could see immediately were helping me rethink that problem. Is that kind of the key, just having a checklist of questions to ask yourself? How do you really start to put this into practice?

THOMAS WEDELL-WEDELLSBORG: I think there are two steps in that. The first one is just to make yourself better at the method. Yes, you should kind of work with a checklist. In the article, I kind of outlined seven practices that you can use to do this.

But importantly, I would say you have to consider that as, basically, a set of training wheels. I think there’s a big, big danger in getting caught in a checklist. This is something I work with.

My co-author Paddy Miller, it’s one of his insights. That if you start giving people a checklist for things like this, they start following it. And that’s actually a problem, because what you really want them to do is start challenging their thinking.

So the way to handle this is to get some practice using it. Do use the checklist initially, but then try to step away from it and try to see if you can organically make– it’s almost a habit of mind. When you run into a colleague in the hallway and she has a problem and you have five minutes, like, delving in and just starting asking some of those questions and using your intuition to say, wait, how is she talking about this problem? And is there a question or two I can ask her about the problem that can help her rethink it?

SARAH GREEN CARMICHAEL: Well, that is also just a very different approach, because I think in that situation, most of us can’t go 30 seconds without jumping in and offering solutions.

THOMAS WEDELL-WEDELLSBORG: Very true. The drive toward solutions is very strong. And to be clear, I mean, there’s nothing wrong with that if the solutions work. So, many problems are just solved by oh, you know, oh, here’s the way to do that. Great.

But this is really a powerful method for those problems where either it’s something we’ve been banging our heads against tons of times without making progress, or when you need to come up with a really creative solution. When you’re facing a competitor with a much bigger budget, and you know, if you solve the same problem later, you’re not going to win. So, that basic idea of taking that approach to problems can often help you move forward in a different way than just like, oh, I have a solution.

I would say there’s also, there’s some interesting psychological stuff going on, right? Where you may have tried this, but if somebody tries to serve up a solution to a problem I have, I’m often resistant towards them. Kind if like, no, no, no, no, no, no. That solution is not going to work in my world. Whereas if you get them to discuss and analyze what the problem really is, you might actually dig something up.

Let’s go back to the kitchen example. One powerful question is just to say, what’s your own part in creating this problem? It’s very often, like, people, they describe problems as if it’s something that’s inflicted upon them from the external world, and they are innocent bystanders in that.

SARAH GREEN CARMICHAEL: Right, or crazy customers with unreasonable demands.

THOMAS WEDELL-WEDELLSBORG: Exactly, right. I don’t think I’ve ever met an agency or consultancy that didn’t, like, gossip about their customers. Oh, my god, they’re horrible. That, you know, classic thing, why don’t they want to take more risk? Well, risk is bad.

It’s their business that’s on the line, not the consultancy’s, right? So, absolutely, that’s one of the things when you step into a different mindset and kind of, wait. Oh yeah, maybe I actually am part of creating this problem in a sense, as well. That tends to open some new doors for you to move forward, in a way, with stuff that you may have been struggling with for years.

SARAH GREEN CARMICHAEL: So, we’ve surfaced a couple of questions that are useful. I’m curious to know, what are some of the other questions that you find yourself asking in these situations, given that you have made this sort of mental habit that you do? What are the questions that people seem to find really useful?

THOMAS WEDELL-WEDELLSBORG: One easy one is just to ask if there are any positive exceptions to the problem. So, was there day where your kitchen was actually spotlessly clean? And then asking, what was different about that day? Like, what happened there that didn’t happen the other days? That can very often point people towards a factor that they hadn’t considered previously.

SARAH GREEN CARMICHAEL: We got take-out.

THOMAS WEDELL-WEDELLSBORG: S,o that is your solution. Take-out from [INAUDIBLE]. That might have other problems.

Another good question, and this is a little bit more high level. It’s actually more making an observation about labeling how that person thinks about the problem. And what I mean with that is, we have problem categories in our head. So, if I say, let’s say that you describe a problem to me and say, well, we have a really great product and are, it’s much better than our previous product, but people aren’t buying it. I think we need to put more marketing dollars into this.

Now you can go in and say, that’s interesting. This sounds like you’re thinking of this as a communications problem. Is there a different way of thinking about that? Because you can almost tell how, when the second you say communications, there are some ideas about how do you solve a communications problem. Typically with more communication.

And what you might do is go in and suggest, well, have you considered that it might be, say, an incentive problem? Are there incentives on behalf of the purchasing manager at your clients that are obstructing you? Might there be incentive issues with your own sales force that makes them want to sell the old product instead of the new one?

So literally, just identifying what type of problem does this person think about, and is there different potential way of thinking about it? Might it be an emotional problem, a timing problem, an expectations management problem? Thinking about what label of what type of problem that person is kind of thinking as it of.

SARAH GREEN CARMICHAEL: That’s really interesting, too, because I think so many of us get requests for advice that we’re really not qualified to give. So, maybe the next time that happens, instead of muddying my way through, I will just ask some of those questions that we talked about instead.

THOMAS WEDELL-WEDELLSBORG: That sounds like a good idea.

SARAH GREEN CARMICHAEL: So, Thomas, this has really helped me reframe the way I think about a couple of problems in my own life, and I’m just wondering. I know you do this professionally, but is there a problem in your life that thinking this way has helped you solve?

THOMAS WEDELL-WEDELLSBORG: I’ve, of course, I’ve been swallowing my own medicine on this, too, and I think I have, well, maybe two different examples, and in one case somebody else did the reframing for me. But in one case, when I was younger, I often kind of struggled a little bit. I mean, this is my teenage years, kind of hanging out with my parents. I thought they were pretty annoying people. That’s not really fair, because they’re quite wonderful, but that’s what life is when you’re a teenager.

And one of the things that struck me, suddenly, and this was kind of the positive exception was, there was actually an evening where we really had a good time, and there wasn’t a conflict. And the core thing was, I wasn’t just seeing them in their old house where I grew up. It was, actually, we were at a restaurant. And it suddenly struck me that so much of the sometimes, kind of, a little bit, you love them but they’re annoying kind of dynamic, is tied to the place, is tied to the setting you are in.

And of course, if– you know, I live abroad now, if I visit my parents and I stay in my old bedroom, you know, my mother comes in and wants to wake me up in the morning. Stuff like that, right? And it just struck me so, so clearly that it’s– when I change this setting, if I go out and have dinner with them at a different place, that the dynamic, just that dynamic disappears.

SARAH GREEN CARMICHAEL: Well, Thomas, this has been really, really helpful. Thank you for talking with me today.

THOMAS WEDELL-WEDELLSBORG: Thank you, Sarah.

HANNAH BATES: That was Thomas Wedell-Wedellsborg in conversation with Sarah Green Carmichael on the HBR IdeaCast. He’s an expert in problem solving and innovation, and he’s the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

We’ll be back next Wednesday with another hand-picked conversation about leadership from the Harvard Business Review. If you found this episode helpful, share it with your friends and colleagues, and follow our show on Apple Podcasts, Spotify, or wherever you get your podcasts. While you’re there, be sure to leave us a review.

We’re a production of Harvard Business Review. If you want more podcasts, articles, case studies, books, and videos like this, find it all at HBR dot org.

This episode was produced by Anne Saini, and me, Hannah Bates. Ian Fox is our editor. Music by Coma Media. Special thanks to Maureen Hoch, Adi Ignatius, Karen Player, Ramsey Khabbaz, Nicole Smith, Anne Bartholomew, and you – our listener.

See you next week.

Subscribe On:

Latest in this series

This article is about leadership.

Decision making and problem solving
Power and influence
Business management

Partner Center

IMAGES

7 steps to master problem solving methodology
What Is Problem-Solving? Steps, Processes, Exercises to do it Right
5 Problem Solving Strategies to Become a Better Problem Solver
Problem Solving Strategies [EFFECTIVE STRATEGIES] SmallBusinessify.com
8 Steps For Effective Problem Solving
Problem Solving Cycle

VIDEO

Limiting Reagent Problem Solving Methods
Problem Solving Techniques
3 problem solving methods that can be converted into business
Problem Solving II: Solving Problems at the Lowest Level
Customer Support Specialist :Problem-Solving Techniques: Mastering Strategies 9
Problem Solving Presentation

COMMENTS

How to master the seven-step problem-solving process
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 ...
The McKinsey guide to problem solving
The McKinsey guide to problem solving. Become a better problem solver with insights and advice from leaders around the world on topics including developing a problem-solving mindset, solving problems in uncertain times, problem solving with AI, and much more.
McKinsey Problem Solving: Six Steps To Think Like A ...
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.
Problem Solving: Essential Consulting Skills
This will help you tap into your creative energy when a job is on the line. Interpersonal skills, such as emotional intelligence, empathy, teamwork, communication skills, and even mood management/mindfulness are all necessary components of professional problem solving. A significant share of professional problems that need solving involve human ...
Adopting the right problem-solving approach
In our 2013 classic from the Quarterly, senior partner Olivier Leclerc highlights the value of taking a number of different approaches simultaneously to solve difficult problems. Read on to discover the five flexons, or problem-solving languages, that can be applied to the same problem to generate richer insights and more innovative solutions.
McKinsey Approach to Problem Solving
There are four fundamental disciplines of the McKinsey method: 1. Problem definition. A thorough understanding and crisp definition of the problem. 2. The problem-solving process. Structuring the problem, prioritizing the issues, planning analyses, conducting analyses, synthesizing findings, and developing recommendations. 3. Distinctiveness ...
How to Solve Problems Effectively as a Consultant
1. Define the problem. Be the first to add your personal experience. 2. Gather and analyze data. Be the first to add your personal experience. 3. Generate and evaluate alternatives. 4.
How to Improve Your Problem-Solving Skills in Consulting
6 Practice and develop. The best way to build your problem-solving skills in consulting is to practice and develop them regularly. You can do this by taking on different types of problems, both in ...
Hypothesis-driven approach: the definitive guide
Hypothesis-driven thinking is a problem-solving method whereby you start with the answer and work back to prove or disprove that answer through fact-finding. Concretely, here is how consultants use a hypothesis-driven approach to solve their clients' problems: Form an initial hypothesis, which is what they think the answer to the problem is.
Consulting Approach to Problem Solving
Module 1 • 1 hour to complete. Problem definition may sound abstract or boring, but it's incredibly important to solve the RIGHT PROBLEM. Like a detective at a crime scene, a consultant needs to stay open-minded; think broadly about the problem and "look around" for obvious (and missing) clues.
35 problem-solving techniques and methods for solving complex problems
6. 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.
Home
Methods; Consulting; Training; About; Contact ; Shop Courses; PROBLEM SOLVED. Every problem has a solution. Ready to solve with Lean Methods? We are a global problem-solving firm specializing in. the application of highly collaborative and methodical. approaches to business performance improvement. We solve with you. Consulting &
How to Develop Problem-Solving Skill as a Consultant
Problem-solving is the core of consulting and the skill that clients value the most. Add your perspective ... be data-driven and evidence-based by using quantitative and qualitative methods to ...
"The McKinsey Way" Book: A Comprehensive Summary
The McKinsey problem-solving process can be summarized in the 5 steps: define the problems, find the root cause, use "hypothesis-driven" process, analyze with "issue tree" and propose solutions. 1. Define the problem: Every consulting project revolves around a "problem". But the "problem" is NOT always the problem!
The 4S Method
The 4S method is an integrated, four-stage problem-solving approach that combines the tools of strategy consulting with insights from cognitive science and design thinking. The first S is to State the problem properly, identifying the core question at hand as well as its context, owner, and stakeholders.
How to Solve Problems
Teams today aren't just asked to execute tasks: They're called upon to solve problems. You'd think that many brains working together would mean better solutions, but the reality is that too ...
Solve Problems Like a Consultant
The 80-20 rule, or the Pareto principle, was first adopted as a problem solving technique by a management consultant who coined the phrase after Vilfredo Pareto's 1906 research in which he observed that 20% of the pea pods in his garden produced 80% of the peas. This principle has since become known as the 80-20 rule, and simply states that ...
Business problem solving
That's what we've found after decades of problem solving with leaders across business, nonprofit, and policy sectors. These leaders learn to adopt a particularly open and curious mindset, and adhere to a systematic process for cracking even the most inscrutable problems. They're terrific problem solvers under any conditions.
The Consultant's Toolkit: Consulting Training
In The Consultant's Toolkit, you will learn through a combination of lecture, case studies, and interactive group exercises. Topics covered include: An overview of the consulting industry, trends, and the role of consultants. Step by step strategic frameworks for the consulting process: Problem definition. Discovery and data collection.
Four Problem-Solving Techniques for HR Consultants
1 Identify the problem. The first step in any problem-solving process is to clearly define the problem you are trying to solve. This may seem obvious, but many HR consultants skip this step or ...
Hypothesis-Driven Approach: Crack Your Case Like a Consultant
A hypothesis-driven approach in consulting is a structured method of problem-solving. Consultants formulate a hypothesis for the solution to a business problem, then gather data to support or disprove it. Cracking a case interview can be a daunting task, with a wide range of potential solutions and approaches to consider.
8-Step Framework to Problem-Solving from McKinsey
8 Steps to Problem-Solving from McKinsey. Solve at the first meeting with a hypothesis. Intuition is as important as facts. Do your research but don't reinvent the wheel. Tell the story behind ...
Consulting & Facilitating
Lean Methods consulting services are delivered using proven approaches applied in a highly collaborative fashion. We bring unique perspectives and skills to the table. ... This approach allows us to pivot to the style of our clients while drawing from an extensive suite of problem-solving tools and methods that ensure we choose the best ...
12 Approaches To Problem-Solving for Every Situation
Brainstorm options to solve the problem. Select an option. Create an implementation plan. Execute the plan and monitor the results. Evaluate the solution. Read more: Effective Problem Solving Steps in the Workplace. 2. Collaborative. This approach involves including multiple people in the problem-solving process.
Do You Understand the Problem You're Trying to Solve?
To solve tough problems at work, first ask these questions. Problem solving skills are invaluable in any job. But all too often, we jump to find solutions to a problem without taking time to ...